The Script Configuration button scripts out the entire log-shipping
configuration for both primary and all secondary servers.
Dealing with Failover to a Secondary Server
Does log shipping sound too good to be true so far? Well, there??™s a catch??”actually, two
catches. The first is the process of failover, and the second is the process of failback. Let??™s
discuss failover first. It isn??™t an automatic process, and there are multiple ways to perform
it. That means documenting what technique you??™re going to use (ack!) and practicing that
procedure thoroughly (double ack!).
Log shipping is a bit optimistic when it comes to failover. In other words, it assumes
that failover will never occur. Fast failover is more of a high-availability goal than it is disaster
recovery. The primary purpose of log shipping is the protection of data from local
disaster. Don??™t rely on log shipping if your primary need is one of quick failover. Database
mirroring, covered in Chapter 8, is much better suited for that purpose.
If you do use log shipping as a failover solution, you must incorporate a number of
fixed steps into the entire log-shipping solution.
Pages:
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320