673
Chapter 26: Log Shipping
26
Delaying restores on secondary database can be extremely useful in case there is an unexpected data change on the
primary database that you wish to recover. For example, say a user executes a delete statement and forgets a WHERE
clause in their query and accidently deletes all the data from a table. If you delay log restores up to an hour on the
secondary server, you’d be able to recover data that was accidently deleted on the primary from the secondary by
querying or copying those rows out from the secondary, for up to an hour after the initial transaction occurred on the
primary database. After that delay period, however, you’ll need to rely on your backups in order to recover your data.- The option for more granularities on restores and when they are applied are set in
the Restore job by clicking the Schedule button. By default, transaction log back-
ups are restored every 15 minutes on the secondary server. - Click OK to complete the secondary database setup, and return to the database’s
Properties tab. - After the secondary database confi guration has been completed, a monitor server
can be confi gured on the primary database’s Properties page by checking Use
a Monitor Server Instance and clicking the Settings button. The Log Shipping
Monitor settings page is shown in Figure 26-7.
FIGURE 26-7
Confi guring the monitor server for log shipping.
c26.indd 673c26.indd 673 7/31/2012 9:49:19 AM7/31/2012 9:49:19 AM
http://www.it-ebooks.info