For those
with limited financial resources using SQL Server 2000, it??™s probably best to use a manual
log-shipping scenario.
Manual Log Shipping
To use log shipping, you don??™t need any additional software, tools, or built-in functionality.
Ultimately, all you need are two or more servers, a central location they can both
access, and scheduled jobs to back up the transaction log on the primary server and
restore the log (without recovery) on the standby server.
Let??™s look at each step in detail:
1. Create a central location for each server to use: This can be a network share that
both can use, or a network share for one server and an FTP server for another that
ultimately resolve to the same physical location. It??™s very flexible; the only requirement
is that both must be able to access it. Figure 6-3 shows the file-sharing
dialog, which you can access by simply right-clicking on the folder.
Figure 6-3. Using a file share for log backups assumes that all SQL Servers involved
in log shipping are in the same Windows domain structure.
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 152
If your standby server isn??™t on your local network and in the same Windows
domain, or is on a completely different networking environment entirely (such as
Unix or an NFS-based system), you??™ll need to access the primary server log backups
either directly from an HTTP or HTTPS site or from an FTP or FTPS/SFTP site.
Pages:
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305