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
Redirecting a SQL Server database to a different host
You can use a database move operation to redirect a backup to a client that is different from the client that performed the backup. NetBackup creates a template that you edit to indicate the host and location where you want to redirect the restore. The new location can be a different instance on the same host, a different host, or a different file path. The move operation also lets you restore the database under a different name than the original one.
Note:
The destination host and instance of a move or restore operation is the one that you log into. For move or restore operations designate the source (or browse) host and the instance when you select
.To redirect a database to another location on a different host
- Establish permissions for redirected restores on the master server.
- The server that backed up the database you want to restore must appear in the server list of the destination host. If the server is not in the list, add it.
- Select File > Set SQL Server connection properties.
- From the Host list, select the host you want to restore to.
- From the Instance list, select the database instance.
To select the default instance, either select <default> or leave the field empty.
- Click Apply and then Close.
- Select File > Set NetBackup client properties.
- From the Current NetBackup Server list, select the NetBackup master server.
This server contains the SQL Server backup images that you want to restore on the destination host. The clients must both use the same master server.
- Click OK.
- Browse for the backup images you want to restore.
For the SQL Host list, select the host that has the database you want to restore.
- Browse for the database that you want to move.
- From the Scripting list, select Create a move template.
- Click Restore.
- Enter a file name and click Save > Yes.
- Edit the template to designate the name that you want to use for the destination database. Also include the file paths that you want to use for each of the database files.