Does anyone know of any issues with using Active/Passive or Active/Active clusters and log shipping. Will log shipping still work if a failover occurs?
Thanks
Yes, log shipping still works after a cluster failover. A failover in a cluster is basically the same as restarting your SQL Service. Assuming you have log shipping configured correctly (i.e. using the virtual instance name, which would be the case if you configured log shipping using the built-in wizards/plans), log shipping will pick up where it left off before the failover occured (i.e. the next time the t-log is backed up, it will be shipped to your shared log location for application to the standby server).
HTH
|||Setting up log-shipping between two clusters gets a little more intricate because you have to establish the file shares log-shipping needs and although the shared disk fails over, the shares have to be setup in advance, and the node has to be the active node in order to setup the "shared disk" shares.
No comments:
Post a Comment