SQL Server Performance

Log Shipping - pausing?

Discussion in 'SQL Server Log Shipping' started by fenster, Oct 28, 2004.

  1. fenster New Member

    From what I've read there is no way to pause log shipping. What are the recommended practices for planned outages on the secondary server to prevent the transactions logs getting out of sync? The copy/load frequency is 5 minutes.

    Can rebooting the primary or secondary server cause the transaction logs to get out of sync?

    Thanks

  2. satya Moderator

    Disable the maintenance plan jobs until the resync is finished and re-enable it once the process is finished.

    If you do so ensure to reload complete database from primary to secondary server before you re-enable the log shipping.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. SQL_Guess New Member

    Are you saying that after he disables, and before he re-enables, he will need to manually copy required log files, or that a new full backup will need to be taken and moved across?

    Panic, Chaos, Disorder ... my work here is done --unknown
  4. satya Moderator

    Assume the last transaction log restore is completed and the scheduled job is paused and then started to execute, then the job itself will take care of file copy in order to restore the Tlog on secondary server.

    But in order to re-sync the primary and secondary with full backups, you may need to perform the manual file copy operation or whichever way you follow to copy the database backups between the servers.

    If you stop the secondary server during the schedule of Log shipping Tlog restore, then the LS schedule will be disturbed and in order to retain the LSNs you may needto apply full backup from primary to secondary and then log shipping schedule to continue the process.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page