Log Shipping - SQL Clustering environment

Hi all,
I have configured two node SQL cluster with default instance and SAN as shared disk.
I have also configured log shipping on primary server which uses maintenance plan to
backup, copy and restore transaction logs to secondary server in remote location.
My questions are:
1) If failover happens, what would be the impact on log shipping?
2) How would i accomplish the log shipping automation without any interruption even if
the cluster failover occurs?
Dear Sentil,
Setting up Log Shipping involves using a share to backup the transaction
logs to. The share will be used by the copy job to pick up the transaction
log backup file and save it to the default backup directory on the restore
(or secondary) server. The files will then be used by the load job. The
file share has to be accessible at all times for the copy job to continue
copying the transaction log backup files.
In a Cluster environment, file shares are cluster resources and hence if
they are not setup as such, they will be not available when the cluster
resources failover to a different node causing log shipping copy job on the
secondary server to not copy any files.
Consider a situation where we have
Server1 -- Node 1
Server2 -- Node 2
VirtualServerName ServerV
If we create a share on a shared disk drive E owned by Server1 and called
"logshipping", the share can be accessed using the unc name
\\ServerV\logshipping. IF the shared disk is now failed over to Server2 for
any reason, the share \\ServerV\logshipping will not be available as a file
share because it was local to the Server1.
Hence, to get around this, please follow KB article "224967 How to Create
File Shares on a Cluster http://support.microsoft.com/?id=224967" to setup
file share resources and use it for log shipping.
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.