October 12, 2015 at 9:49 am
FYI - All VMWare.......
For VLDBs, I'd prefer not to use pure AAG between 2 DCs, as that normally leads to 3 copies+. If we were to setup an FCI for HA, with AAG async to DR, can that third DR server just use normal local disks? And would that therefore mean I could use for backups using the likes of Veeam?
October 12, 2015 at 12:45 pm
gingerdazza (10/12/2015)
FYI - All VMWare.......For VLDBs, I'd prefer not to use pure AAG between 2 DCs, as that normally leads to 3 copies+.
How you working that out, you have 2 DCs and one replica in each that equals an AlwaysOn group with 1 primary and 1 secondary
gingerdazza (10/12/2015)
If we were to setup an FCI for HA, with AAG async to DR, can that third DR server just use normal local disks? And would that therefore mean I could use for backups using the likes of Veeam?
yes the third server could use local disks and would be a standalone instance participating as a replica in the AlwaysOn group. This would have to be asynch as an FCI does not support automatic failover. Still begs the question why you dont just use 2 nodes, 1 at each site.
For more detail on all of this check my stairway to HA on this site starting at this link
http://www.sqlservercentral.com/articles/Failover+Clustered+Instance+(FCI)/107536/[/url]
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 12, 2015 at 1:43 pm
The site links are pretty good (1Gbps and 1-2ms latency), but there of course times when the link can get higher saturation, and running cross link synchronous for SQL then makes me cautious.
Any thoughts on it?
Also, anyone know if there's a way to tag synchronous replication between two SQL VMs? ....as I could perhaps lay QoS on the sync traffic in order to mitigate the risks.
October 12, 2015 at 3:11 pm
gingerdazza (10/12/2015)
The site links are pretty good (1Gbps and 1-2ms latency), but there of course times when the link can get higher saturation, and running cross link synchronous for SQL then makes me cautious.Any thoughts on it?
Also, anyone know if there's a way to tag synchronous replication between two SQL VMs? ....as I could perhaps lay QoS on the sync traffic in order to mitigate the risks.
Do you mean segregate the mirror traffic to a particular network?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply