Solved

Sharepoint 2010 SQL 2008 R2 Mirroring over WAN link

Posted on 2011-03-23
4
776 Views
Last Modified: 2012-06-21
Has anyone experience of Sharepoint 2010 SQL 2008 R2 database mirroring over a WAN link ? I know the supported scenarios, our WAN link will be average anything from about 2ms-20ms round trip, and there will be a limited number of low-usage, smallish (less than 20GB) databases and ideally, would like to do High-Availability with automatic failover, but probably more realistically, to avoid spurious failovers due to loss of connection to witness, High Availability with manual failover. It is essentially for business continuance in the event that a WAN link goes down, or that we lose the SQL server in the primary site. We would also like to be able to use full failover and run completely from the other site (will install another WFE server in DR site for this).
So really looking for experiences, advice etc.

Thank you
0
Comment
Question by:TheGeezer2010
  • 2
  • 2
4 Comments
 
LVL 15

Expert Comment

by:sharepointguru14
Comment Utility
I would say if you were 10ms or less than you wouldn't have any issues at all. Although then clustering would work as well. 20ms and small transactional data to be replicated I think you should be fine.

you issue will be if you lose the wan link for any extended period of time and replicating the backlog.
0
 
LVL 11

Author Comment

by:TheGeezer2010
Comment Utility
Hi Sharepointguru14

Have you actually tried this yourself ? Regarding the backlog, if we were to lose the link a judgement call would need to be made on whether to suspend or stop the mirroring depending on likely time to fix.

The plan now is to get this up and running in synchronous - no auto failover mode, test full failover on the SQL back-end, if this works OK, will then introduce a WFE in DR site and try failover using the new FE. I am not sure however if you can span a WFE over different AD sites - suspect not, so this would have to be a DNS change to effect this failover - and hence some delay.

I have one lother question - if I then include all of the databases which CAN be mirrored (all content, service (with the exceptions shown in Microsoft documentation e.g. SyncDB), config), if the link goes down when all is synced and we failover, is there anything else which needs to be done in terms of backing up/restoring other databases etc, and indeed, if the link goes down are you actually ABLE to failover ?

Sorry for questions but this whole topic seems to get more confusing the deeper you delve !!
0
 
LVL 15

Accepted Solution

by:
sharepointguru14 earned 300 total points
Comment Utility
mirroring I have not done myself. Typically I have implemented clustered backend and then you either SAN replication or Log shipping for the DR solution. I'm not a huge fan of mirroring in the same datacenter so I'm not going to tell you I like the idea over a wan. The good news is...it really doesn't take much to setup and test. I don't know what your links are and actually how much you are going to be mirroring to tell you whether or not it is going to work. Really you need to just set it up and test it. If its not much change and less than 20ms I expect that it will work but I wouldn't count on it being a completely seamless or automatic solution but it would be a viable DR strategy.
0
 
LVL 11

Author Comment

by:TheGeezer2010
Comment Utility
Hi SPG and thanks for your input

Can you describe how your DR solution works as we also would have the possibility of using SAN replication + log shipping. The issue I have with log shipping is that you cannot use it for any service or config databases.

Am I right then that this will only be a useful DR solution if the server/database fails. If the link fails we will have to break mirroring and maybe lose small amount of data.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Finally comes the third version of VMware Virtual SAN, whose name is 6.1, and comes loaded with new features many of which really are excellent and even surprising.
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now