Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installation and host configuration
- Host configuration and job settings
- Managing SQL Server objects for use with SQL Server Intelligent Policies
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Registering instances or availability replicas with an instance group
- Configuring backups with SQL Server Intelligent Policy
- About tuning parameters for SQL Server backups
- Performing restores of SQL Server
- Redirecting a SQL Server database to a different host
- Protecting SQL Server data with VMware backups
- About protecting an application database with VMware backups
- Configuring backups 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 availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with legacy policies
- 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 (legacy backup policies)
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- Protecting SQL Server in a cluster environment
- Configuring backups with legacy SQL Server policies using clients and batch files
- About using batch files with NetBackup for SQL Server
- About schedule properties
- Performing user-directed backups of SQL Server databases
- Performing user-directed backups of read-only filegroups
- Using NetBackup for SQL Server with multiple NICs
- Performance and troubleshooting
- About debug logging for SQL Server troubleshooting
- About disaster recovery of SQL Server
- Appendix A. Other configurations
- About SQL Server backups and restores in an SAP environment
- Appendix B. Register authorized locations
Recovering SQL Server databases after disaster recovery
For the purposes of disaster recovery, you should only restore to a new installation of SQL Server. However, you can restore an existing installation of SQL Server with other active databases. The server should be running the same version of Windows on the same hardware platform. It also should be running the same version of SQL Server with the same service pack as the original server.
To recover SQL Server databases
- If you want to restore to an existing SQL Server, choose from one of the following:
- Refer to the following article for instructions on how to rebuild the master database. Click the "Other Versions" drop-down list to select the correct SQL Server version.
http://msdn.microsoft.com/en-us/library/ms144259.aspx
Look for the information that describes how to rebuild system databases for a default instance from the command prompt.
- When the rebuild is complete, restart the SQL Server services if necessary.
- To begin the restore of the master database, start SQL Server in single-user mode.
The procedure to start SQL Server in single-user mode is described in the following article:
http://msdn.microsoft.com/en-AU/library/ms188236.aspx
Click the "Other Versions" drop-down list to select the correct SQL Server version.
- Open the NetBackup MS SQL Client interface.
- Locate all the media that is required to perform the restore operations.
- Select File > Restore SQL Server objects.
- Select the backup image that contains the copy of the master database you want to restore.
Select only the master database at this time.
- Click Restore.
- Restart the SQL Server service after the restore completes.
- Continue with the restore of the remaining SQL Server databases.
Follow the instructions for restoring SQL databases, differentials, transaction logs, files, and filegroups.
When all of the restore operations have completed successfully, then the recovery of the SQL Server databases is complete.
After the recovery is complete, Veritas recommends that you perform a full database backup as soon as possible.