October 25, 2016 at 5:25 pm
Hi,
We are planning for a sql server disaster recovery plan with Always on availabilty groups for sql server 2016.
Can we have a sql server failover cluster with the shared drive for this setup at the primary location and disaster location?
Thanks.
October 26, 2016 at 12:57 am
This was removed by the editor as SPAM
October 26, 2016 at 12:08 pm
If you're planning to use Availability Groups, then you don't need a shared drive. Shared drives are needed for Always On Failover Cluster, not Availability Groups. Each node in the AG will have its own, local storage.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 26, 2016 at 12:37 pm
sql_2005_fan (10/25/2016)
Hi,We are planning for a sql server disaster recovery plan with Always on availabilty groups for sql server 2016.
Can we have a sql server failover cluster with the shared drive for this setup at the primary location and disaster location?
Thanks.
sounds like you may be confused with failover cluster instance and availability groups, check my stairway to HA starting at this link
http://www.sqlservercentral.com/stairway/112556/[/url]
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 27, 2016 at 10:59 pm
Hi,
I would like share the AG setup.
I recently deployed alwayson availability group one of the OLTP database for DR requirment with MultiSubNet failover.
OS: Win 2012 R2 standard edition, DB: SQL 2012 Enterprise edition
I am not used shared storage in this AG setup,
1. Total three nodes involved and HyperV virtual server and Each nodes are local virtual Hard disk
2. Primary datacenter total two nodes
3. One node for remote datacenter
4. Files hare witness for voting nodes (FSW was created at remote datacenter side)
5. The whole setup was made in same domain environment.
I am not facing any glitch since last two months after deployment.
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply