How
much is lost depends on how often the transaction log is backed up on the primary
server, how often the secondary servers check for new transaction logs, how long it takes
to copy the transaction log file over the network, and how long it takes to restore it. You
could configure log shipping to back up the log on the main machine, copy it over the
network, and restore it every five minutes, or you could configure log shipping to execute
every two hours. If data is continually being entered into the main system, you??™re guaranteed
to have a certain amount of lost data. Depending on the frequency of the log shipping,
as well as the activity on the primary database, it??™s likely that there will be data loss.
The upside is that you should at least know exactly how much data you??™ve lost.
nNote Data loss is often not so large a problem as you might think. In many environments, there is already
a means in place to identify and reenter lost data. So long as the amount of data to be reentered is minimal,
the price of reentering it might be far lower than the cost of ensuring that no loss at all occurs.
Pages:
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295