Figure 6-1 illustrates what you should have after following these steps.
Figure 6-1. A simple standby database scenario
The standby server then picks up the transaction log from the central location,
copies it locally, and restores it (but leaves the database in an unrecovered state). This
process repeats until a failure or a break in the LSN chain occurs??”for example, if someone
accidentally deletes a log backup before it??™s restored.
Note that there must be an equivalent and uninterrupted LSN chain on the primary
and secondary servers. You can create separate full backups, file/filegroup backups, and
differential backups. A transaction log backup truncates committed transactions from
the active log, which means you may only maintain one transaction log backup chain.
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 149
The instant you create a new log backup on the primary server that doesn??™t get placed in
the central log backup location, log shipping ceases to function.
nTip You can maintain multiple log backups and deploy log shipping by using either the MIRROR TO
clause, which makes copies to locations other than the log shipping pickup point, or the WITH COPY_ONLY
clause, which tells SQL Server not to reset the LSN chain.
Pages:
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302