Using NetBackup for SQL Server with database mirroring Impact on backup
Any policy used to back up the principal should also specify the host that contains the mirror database.
Permission for a redirected restore must be established between both mirroring partners.
To establish redirected restore permission between two hosts
On the master server, create a file called: install_path\NetBackup\db\altnames\No.Restrictions
Create each of the files on the master server: install_path\NetBackup\db\altnames\hostA install_path\NetBackup\db\altnames\hostB
Note: When you create the No.Restrictions file it allows all clients to perform redirected restores to different clients. This file may need to be added and removed according to your site policies.
Impact on backup
Since backups can occur only on the principal, you must take steps to ensure that you don't miss any scheduled backups due to failover. Establish a procedure to simultaneously initiate backups for both partners, but suppress the operation on the mirror.
To achieve this objective, first create a backup schedule for the principal. See “Configuring a backup policy for a database” on page 26. Then take the following steps:
To simultaneously initiate backups for both partners
Add the host containing the mirroring partner to the client list of the policy that you created for the principal.
Create a batch file on the mirroring partner that has the same name as the batch file specified in the backup selections policy.
The batch file on the mirroring partner should be identical to the one used on the principal except that the value supplied for SQLHOST and SQLINSTANCE are different.
When you follow these steps, it ensures that any scheduled backup for a mirrored database is launched on both the principal and the mirror. The backup on the principal should run normally. The backup on the mirror is inhibited. You