Figure 8-4. This error that refers to a failure of the mirroring process appears on the
principal. Because the error is logged, it can also be triggered as an alert.
Even though the mirroring session is stopped, you may still access the properties of
the database-mirroring configuration through the SSMS GUI on the principal to make
modifications. If the principal were to fail (or if you were to attempt to make changes to
mirroring on the mirror node while it??™s in a failed state), the database mirroring options
won??™t be available through SSMS. You can still use T-SQL to make some changes, though.
Mirror
The database on the receiving end of a mirroring session is called the mirror database.
You can create it by restoring a backup of the principal database and leaving that
restored version in an unrecovered state (just like with log shipping). The mirror continually
receives transaction data (not transaction log backups) and restores it as
quickly as it can or as quickly as it is told to do.
In normal operation, a database that is acting as a mirror should appear as it does in
Figure 8-5.
Pages:
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381