If you have a direct but slow network connection
to Guam, you can set the frequency of the backup and restore SQL Agent jobs to
a much slower frequency so that the network can keep up properly with the backup and
restore jobs.
After going through all of the setup for the primary and secondary servers, be sure to
script out the log-shipping creation process, as shown in Figure 6-16. Once you finish configuring
a log-shipping scenario, SQL Server attempts to generate that scenario in one go.
If that generation fails, you??™ll have to correct the problem and restart manually. If you don??™t
have a creation script to modify (perhaps a directory was named incorrectly or NTFS permissions
weren??™t set), you must start over from scratch. Starting over isn??™t the end of the
world if you??™re trying to configure only a single secondary server, but starting over can be a
huge waste of time when configuring multiple secondary servers, each with different configurations.
In any event, a script of the log-shipping topology creation is a good thing to
have on hand.
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 163
Figure 6-16.
Pages:
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319