That means that in order to use SQL Server 2005??™s builtin
log shipping, the primary, secondary, and monitoring servers must be on the same
Active Directory domain or be within trusted domains within the same Active Directory
forest. If you need or want to use FTP or HTTP, you must configure the log shipping manually.
Don??™t worry if some of this sounds a bit Greek to you: I??™ll spend more time on
networking issues in Chapter 10.
The primary server uses the local location shown in Figure 6-10 as the location for
transaction log backup files. This local location should be the same location used by the
network share. Even though both ultimately point to the same location, the secondary
servers use the network share location, while the primary server uses the local path.
Figure 6-10. This dialog box actually creates multiple SQL Agent jobs.
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 158
nTip Whenever you need to set up a network share, make it a hidden share by appending $ to the name.
If a share is flagged as hidden, no one can browse the network to find it.
Pages:
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312