What are the challenges you face when working across database platforms? Take the survey

Log Shipping and Reboots

saratatumsaratatum Posts: 2
edited February 25, 2008 10:20PM in SQL Backup Previous Versions
O/S patches are applied at least once a month. The servers must be rebooted. This is done on a schedule. What is the proper way to reboot servers using log shipping? Should the log shipping jobs be disabled on each server and enabled after the reboot? Will log shipping recover without stopping the jobs after a reboot?


  • Options
    peteypetey Posts: 2,358 New member
    Log shipping involves making a backup on the production server, copying it over to the standby server(s), and restoring the backup files. Interrupting any of the above processes while they are running could cause one of many inconveniences e.g. unusable backup files or incomplete files.

    So yes, stopping the backup/restore jobs after ensuring no processes are running, prior to rebooting the server is a good idea. You can run

    EXEC master..sqbstatus

    to check if any SQL Backup processes are currently active. Note that this only displays processes ran using the extended stored procedures. Processes ran using the command line interface are not displayed.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.