Typically you would use
this option for large databases in which the time required for creating a new backup file
would creep into production usage hours.
The final option in Figure 6-12 assumes that you??™ve already restored the backup
with the NO RECOVERY clause on the secondary server. Typically, you??™d use this option if
the backup file has to traverse a long distance or is just too large to copy over the network
in a reasonable amount of time. Usually backup tapes are transported to the
secondary site, and the database is restored by hand.
The next step in automating log shipping is to copy the transaction log backups to
the secondary servers. As you can see in Figure 6-14, you need to choose a destination
folder that will be a local drive reference on the secondary server. You don??™t need to
specify where the files are copied from: you already did that when you specified the
backup options when you chose a network location for the backup files. The initial
step of specifying that network location for the backup files is done precisely for the
purpose of making it easy for each secondary server to locate a new transaction log
backup to copy.
Pages:
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316