asked on Microsoft Storage Replica not working
I have a storage replica that initialized without error, but now when I check Perfmon stats I have nothing happening. It has been up for three days. The Primary server that holds the 9 Terabytes of data is in production and being used by my people.
I have a message now that states "Storage replica source entered wait-for-quorum state"
Is this a red hearing? The source server and the target server are in the same LAN and within the same domain. There isn't any sort of Firewalling options installed on either Servers, and the servers are actually in the same rack. Also, there isn't any sort of Antivirus application installed.
Does anyone have any thoughts?
I have a message now that states "Storage replica source entered wait-for-quorum state"
Is this a red hearing? The source server and the target server are in the same LAN and within the same domain. There isn't any sort of Firewalling options installed on either Servers, and the servers are actually in the same rack. Also, there isn't any sort of Antivirus application installed.
Does anyone have any thoughts?
Storage
Last Comment
Philip Elder
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Ahh, yeah!
Man, I'm listed as a basic user and I paid my $24.95 Now there is a case afoot to fix my membership.
I sure would have had a better response to my question had I been listed as a premium user.
As it stands the answer I got was simply garbage! But in the absence of any other answer sure it was the best, but garbage.
Man, I'm listed as a basic user and I paid my $24.95 Now there is a case afoot to fix my membership.
I sure would have had a better response to my question had I been listed as a premium user.
As it stands the answer I got was simply garbage! But in the absence of any other answer sure it was the best, but garbage.
ASKER
The real solution: Make sure that every bios upate is installed. Assure that any firmware for any subsystem is updated as in an Idrac from Dell.
Then make sure Windows is using the right drivers. but the key here is you need to redeploy the server operating system. Then everything apparently binds correctly and then you will replicate!!!!!! So Update, Update Update!!!!
Then make sure Windows is using the right drivers. but the key here is you need to redeploy the server operating system. Then everything apparently binds correctly and then you will replicate!!!!!! So Update, Update Update!!!!
A basic assumption in my case is that the firmware setup on the host(s) is up to date as of deployment date. It's Standard Operating Procedure (SOP) in our I.T. firm. As a result, the thought did not cross my mind to ask.
My EE article: Some Hyper-V Hardware & Software Best Practices.
My EE article: Some Hyper-V Hardware & Software Best Practices.
ASKER
Sorry,
I wasn't in the best of moods when I made that statement. I do wish you would have looked at my follow up as I had indicated that I had infact ran the test as its a requirement to bringing up the replica. I will try and delete the response. Did you see my response back about using that command already? Thanks
I wasn't in the best of moods when I made that statement. I do wish you would have looked at my follow up as I had indicated that I had infact ran the test as its a requirement to bringing up the replica. I will try and delete the response. Did you see my response back about using that command already? Thanks
ASKER
Sorry, I cant delete it.... Maybe you know of a way?
ASKER
Oh, as for it being SOP. I would have it as SOP myself, but the gear, and software is on a couple of servers in Florida. I was being paid to offer solutions. My very first suggestion was just that, make sure everything be tween the target and the source server was 100% in agreement if not completely up todate. One of the basic criteria is to assure that everything matches. Now the client, in fact, did update and upgrade everything, but still he failed. As we poured through further suggested efforts I kept coming back to this one issue, the servers were not in agreement, but now they were. Hence, why was it still failing. There wasn't a single diagnostic message. Only out comes of nothing. Perfmon remained dead.
The client then reloaded the OS with all the updates applied. Then he replicated and everything worked. There will be many more complex clients to address!!!! It is my Life!!!
The client then reloaded the OS with all the updates applied. Then he replicated and everything worked. There will be many more complex clients to address!!!! It is my Life!!!
ASKER
And I am in Pittsburgh. I remote to Florida, Texas, California, and others most of the day through as a consultant.
We're in the same boat. We have iDRAC Enterprise, iLO Advanced, and Intel RMM configured for us to access the host(s) if required. A VPN connection or special rule on the firewall gives us access to a standalone machine for the purpose.
Besides the BIOS and firmware making sure the OS is up to date is also critical. Server 2016 was not the most stable of OS releases from Microsoft.
The latest November update addressed a _lot_ of issues with several features. It's best to make sure it gets installed on both ends.
Besides the BIOS and firmware making sure the OS is up to date is also critical. Server 2016 was not the most stable of OS releases from Microsoft.
The latest November update addressed a _lot_ of issues with several features. It's best to make sure it gets installed on both ends.
ASKER
These are the things I wondered. Is it a stable release? And replica, is it used often, or do people look for third party solutions? Lastly, I saw some things pointing to uefi settings needing to be set correctly. Just some thoughts? And thanks. I did give you the 1000 points. I'm not sure how much that matters. I am hopeful that my membership gets strait end. I have a DAG installation that's going to beat the heat out of me.
It's definitely better now. There are a number of known issues.
As far as it being a relevant feature, look to SAN. To run a similar setup we need two SAN units. That's six or seven figures right there. Then, we need the replication license. That's easily another five to six or more figures. Then, on top of that we need the support contract(s).
Two Storage Spaces Direct (S2D) clusters set up and 5ms to 7ms apart and we have a stretch cluster via Storage Replica. That's pretty slick.
As far as uEFI on servers with Secure Boot we've had some issues with getting the server OS in so we've stuck with the legacy BIOS setup for now. All of our servers now get TPM v2 so we're encrypting everything via BitLocker in-guest anyway.
As far as it being a relevant feature, look to SAN. To run a similar setup we need two SAN units. That's six or seven figures right there. Then, we need the replication license. That's easily another five to six or more figures. Then, on top of that we need the support contract(s).
Two Storage Spaces Direct (S2D) clusters set up and 5ms to 7ms apart and we have a stretch cluster via Storage Replica. That's pretty slick.
As far as uEFI on servers with Secure Boot we've had some issues with getting the server OS in so we've stuck with the legacy BIOS setup for now. All of our servers now get TPM v2 so we're encrypting everything via BitLocker in-guest anyway.
I have used that command and the site passed. At which time I have brought on line my source and destination computers.
My replication came up days ago. re you asking me to run the site test again? It passed the last time.
The problem is that my volumes are not syncing even though they say that they are up and running. Perfmon shoes no activity.
Please advise