0

We are in the process of moving datacenters so we want to properly failover our Primary server to an Asynchronous Server in our new datacenter so we can drive the existing gear out there. Here is my setup

Datacenter Old SQL01 (Primary) (Current Vote 1) SQL02 (Secondary) (Current Vote 1)

Datacenter New SQL03 (Secondary Asynchronous) (Current Vote 1)

I also have a File Share Witness configured on a domain controller in our Office that both networks can see. So this also has a vote.

On our cut over day we are going to failover our Primary to SQL03 so we can run our system in the New Datacenter while we drive the existing gear out.

Once I failover I need to shut down SQL01 and SQL02, drive them out to new location, change their IP's and bring them online.

Questions:

Should I remove SQL01 and SQL02 from the availability group first then re-add them once I bring them online at the new location?

Secondly How will this work with my voting seeing I currently have 4 vote and will be going down to 2?

Will this effect the majority vote?

1 Answer 1

0

On our cut over day we are going to failover our Primary to SQL03 so we can run our system in the New Datacenter

Before you do this, change the synchronization type to be synchronous and let the secondary catch up. Then, when the secondary is synchronized you can failover without issue.

Should you failover while the replica is still set to be asynchronous it will not guarantee that the databases in the AGs are all caught up to the same time. Additionally it'll cause you more issues as all database replicas will have their data movement suspended.

Should I remove SQL01 and SQL02 from the availability group first then re-add them once I bring them online at the new location?

If it were me, I would. Even though driving them there doesn't "sound" like it's very far away - who knows what else will happen. When you remove the replicas the databases will go back into a restoring state so it should be fairly easy to add them back in.

Secondly How will this work with my voting seeing I currently have 4 vote and will be going down to 2?

If you're using Windows Server 2012+ then dynamic quorum will be enabled by default. If you shut the servers down one by one in a controlled fashion then dynamic quorum will kick in and automatically readjust the votes. You won't have to do anything.

Additionally if you're using Windows Server 2012R2+ dynamic witness will also be on by default, thus giving or taking away witness votes as needed. Again, because you're doing this in a controlled fashion there shouldn't need to be any extra involvement or customization for the short period of time.

1
  • Excellent info. That should about cover everything. This is all pretty much what I figured I just wanted to run it by someone else to make sure. Thanks for all your input. Yes everything is Windows Server 2012 R2 and SQL Server 2016 Enterprise so I should be covered.
    – P3Jeff
    Commented Oct 28, 2016 at 14:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.