Effect on recovery

When you restore a mirrored database, you must run the NetBackup SQL Client from the host that contains the mirroring partner. The mirroring partner is in the principal role. See SQL Server 2005 Books Online for information on how to determine which partner is the principal.

Backup images may have been created on either or both of the mirroring partners. However, they appear as a unified tree view in the Restore Database dialog box irrespective of the partner from which they had been backed up. In addition, the recovery script that is created for the database is created from images from both partners as appropriate. To determine which partner the backup was taken from, look at the property page for the image.

To view backup images you may look on the hosts that contains either of the mirroring partners, provided that backups were done for that partner.

For example, suppose that mirroring partners are as follows:

Moreover, suppose that all of the backups were done on HostB, though the principal is currently on HostA. To browse backup images for the Accounting database, take the following steps:

To browse for backup images

  1. On HostA, open the NetBackup SQL Client.

  2. From the File menu, select Restore SQL Server Objects.

  3. In the Backup History Options dialog box, select HostB in the SQL Host dropdown.

  4. Click OK.

    Note:

    In this example, if backup images had been created exclusively on HostA or on both HostA and HostB, then all of the images from both partners would be viewable. They are viewable by selecting HostA in the SQL Host dropdown.

    You can browse and restore the mirrored database and expand the Accounting database as usual. Restore operations that are created within a recovery script are created with the redirected script. The redirected script is used as necessary to the extent that any such operation identifies an image backed up from the mirroring partner.

    When you are ready to restore a mirrored database, you must remove the mirroring attribute and then restore the database as usual.