As long as your clients are running SNAC, they should revert to the new primary
database when it comes back online??”that is, if it has the same name. You may have to
stop a client application and restart it, or point it to a new server name if a new server
name was required in the repair of the primary failure. Other than that, the clients should
have no problems (or at least they won??™t complain as they might with log shipping).
Mirroring Mode:High Protection
In High Protection mode, all changes are synchronous, but no mirror is available to provide
automated failover. In the event that the principal fails, no automatic failover occurs.
That??™s right, no automatic failover. It??™s already slowed down by being synchronous, plus
you have no automated failover, so what??™s the benefit?
When the mirror fails, the DBA has to make the decision to abandon mirroring altogether
to make the principal a standalone server. Actually, you need to make this decision
CHAPTER 8 n DATABASE MIRRORING 207
in conjunction with the business owners of the application (more on that in Chapters 11
and 12).
Pages:
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397