Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installing NetBackup for SQL Server
- Instance Management for SQL Server Intelligent Policies
- Viewing the SQL Server instances and instance groups in instance management
- About registering SQL Server instances
- Configuring SQL Server backups with SQL Server Intelligent Policy
- Configuring NetBackup for SQL Server
- Performing restores of SQL Server
- Redirecting a SQL Server database to a different host
- Restoring multistreamed SQL Server backups
- Protecting SQL Server data with VMware backups
- About protecting SQL Server data with VMware backups
- Using NetBackup for SQL Server with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped backups (legacy SQL Server policies)
- Protecting SQL Server in high availability (HA) environments
- About using NetBackup to protect SQL Server availability groups
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- About protecting a specific node in a SQL Server availability group
- About NetBackup for SQL Server with database mirroring
- Backup and recovery concepts
- Overview of SQL Server backup and recovery concepts
- About recovery factors for SQL Server
- Using NetBackup for SQL Server with multiple NICs
- Configuring backups with legacy SQL Server policies using clients and batch files
- About using batch files with NetBackup for SQL Server
- About schedule properties
- Backing up read-only filegroups
- Performing user-directed operations with dbbackex
- Using bplist to retrieve a list of SQL Server backups
- SQL Server backups and restores in an SAP environment (legacy SQL Server policies)
- About SQL Server backups and restores in an SAP environment
- Troubleshooting
- About debug logging for SQL Server troubleshooting
- Disaster recovery of a SQL Server
- Appendix A. Sample batch files
- About sample backup batch files for legacy SQL Server policies
- About sample restore batch files
- About sample backup batch files for legacy SQL Server policies
- Appendix B. Multiplexed backups
- Appendix C. Register authorized locations
Restoring a mirrored database backup image
Note:
Before you restore a mirrored database, you must remove the mirroring attribute.
For mirrored databases, NetBackup can create backup images on either or on both the principal and the mirror server. The Restore Database dialog box displays any backups images from both servers. To determine which partner the backup was taken from, look at the property page for the image. To view backup images you can select the that contains either of the mirroring partners, provided that NetBackup performed backups for that partner.
For example, assume that mirroring partners are as follows. All of the backups were done on HostB, though the principal is currently on HostA:
Principal
Host name: HostA
SQL Server instance: Solaria
Database: Accounting
Mirror
Host name: HostB
SQL Server instance: Moonbeam
Database: Accounting
If backup images were created exclusively on HostA or on both HostA and HostB, you can view the images from both partners. Select HostA in the list.
To restore a mirrored backup image
- Disable mirroring on the principal mirror.
You can use the appropriate commands in SQL Server Management Studio or use ALTER DATABASE directly.
- On the principal server, open the NetBackup MS SQL Client.
When you restore a mirror database, you must run the NetBackup MS SQL Client from the principal server. See SQL Server Books Online for information on how to determine which partner is the principal.
In the previous example, the principal is
HostA
. - On the File menu, select Restore SQL Server Objects.
- In the Backup History Options dialog box, from the SQL host list select the mirror server.
In the previous example, the mirror is
HostB
. - Click OK.
- Proceed with the restore as normal.
NetBackup creates a recovery script for the database that includes images from both partners, as appropriate.