Yes,
network latency has an effect on the entire process, but it does not stop the shipping
from occurring. Let??™s say you have a primary server in Chicago, a standby in New York,
and another standby in Shanghai. The server in Shanghai is likely to be slightly behind
the server in New York, but the logs will eventually get shipped.
Even with network latency factors, the lack of location boundaries is a huge benefit.
You could have a standby server on every continent (yes, even Antarctica). Is there any
surer way to mitigate environmental disaster?
Low Resource Overhead Is Incurred
Without getting too deep into the specifics yet, you can enable log shipping by creating
a log backup job on the primary server (log shipping works in Full Recovery and Bulk-
Logged Recovery modes only) and placing those backup files in a location accessible
over a network. On the secondary server, you restore a full backup of the databases but
leave it in standby mode, ready for log restores. You then create a job to pick up the primary
server??™s transaction logs, copy them locally, and then restore them while leaving
the database in a standby mode.
Pages:
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293