Using Mirroring with Log shipping

Question

Using Mirroring with Log shipping

blakmk

Ten Centuries

Points: 1160
More actions
December 10, 2009 at 10:59 am

#156489

Can anyone tell me the correct way to configure the log backup destination when using logshipping with mirrroring in sql 2005?
In this microsoft document, http://msdn.microsoft.com/en-us/library/ms187016.aspx
the recommendation is:
"To maximize availability of the primary server, we recommend that you establish the backup folder in a shared backup location on a separate host computer. Ensure that all the log shipping servers, including the mirror/primary server, can access the shared backup location (known as a backup share)."
However im not sure how to implement this. I know Microsoft do not recommend backing up using CIFS on unc paths because of delayed write failures however this is the only way I can think of implementing the solution.
any ideas?
Sql Server Blog
Sql Server Consultancy

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Jonathan Kehayias One Orange Chip Points: 26778 More actions · Answer 1

What I'd do is have a dedicated NIC on the SQL Server to handle pushing the backups to the UNC path. This would segregate the Network IO from the other traffic to the SQL Server. I backup to UNC paths everyday, and on a properly configured network it isn't necessarily a problem.

blakmk Ten Centuries Points: 1160 More actions · Answer 2

Thanks for this advice however I have experienced lost write conditions and a number of corrupt databases when using log shipping with UNC paths. This has only happened once albeit under heavy load but it has still happened and microsoft dont generally recommend it.

Sql Server Blog
Sql Server Consultancy

Jonathan Kehayias One Orange Chip Points: 26778 More actions · Answer 3

I missed that you said CIFS in conjunction with UNC. The supported way for doing this would be a IPSEC tunnel or point to point VPN between the machines, essentially creating your own private network over the internet between the two machines.