NetBackup™ for Microsoft SQL Server Administrator's Guide
- About NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Installing the Veritas VSS provider for vSphere
- Configuring RBAC for SQL Server administrators
- Managing SQL Server assets and their credentials
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Configuring backups with SQL Server Intelligent Policy
- Performance tuning and configuration options
- Protecting SQL Server availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with batch file-based policies
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- About protecting a specific node in a SQL Server availability group (batch file-based policies)
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- Protecting SQL Server with VMware backups
- About protecting an application database with VMware backups
- Create a protection plan to protect SQL Server data with a VMware backup
- Configuring backup policies with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped snapshots
- Protecting SQL Server in a cluster environment
- Managing protection plans for SQL Server
- Restoring SQL Server with the NetBackup web UI
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Configuring batch-file based policies for SQL Server backups
- Requirements to use batch files with NetBackup for SQL Server
- Schedule properties for SQL Server batch file-based policies
- Configure a batch file-based policy for a user-directed backup of read-only filegroups
- Performing backups and restores with the NetBackup MS SQL Client
- Redirect a SQL Server database to a different host (NetBackup MS SQL Client)
- Restoring multistreamed SQL Server backups
- 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
- About NetBackup for SQL Server with database mirroring
- Appendix B. Register authorized locations
Restoring multistreamed SQL Server backups
When you perform a restore from a backup that used multiple stripes, NetBackup automatically performs the restore using the same number of stripes. Select the object you want to restore and NetBackup finds all of the related backups and restore them. Upon restore, all of the streams must also be available at the same time.
If you specified multiple stripes for a non-snapshot backup, then the number of backup streams that you specified were created. NetBackup names these streams, for example:
juneberry.MSSQL7.COLE.db.pubs.~.7.001of003.20140908200234..C juneberry.MSSQL7.COLE.db.pubs.~.7.002of003.20140908200234..C juneberry.MSSQL7.COLE.db.pubs.~.7.003of003.20140908200234..C
To create your own batch file to restore a striped object, specify only the first stripe name with the NBIMAGE keyword. NetBackup for SQL Server finds the remaining ones automatically. More information is available about the backup names that are used for SQL Server objects.
If you specified multiple stripes for any Snapshot Client backup, then NetBackup divides the number of component files equally among the number of stripes. (A Snapshot Client backup streams the frozen image to tape.) If the number of files is less than the specified number of stripes, then the agent performs the backup using only as many stripes as there are files.
Note:
NetBackup ignores the multistream directive for Instant Recovery backups.
With SQL Server backups that are performed with Snapshot Client, NetBackup identifies all of the backup streams by the same name. They are differentiated by NetBackup by their backup IDs.
juneberry.MSSQL7.COLE.db.Northwind.~.7.001of003.20141012131132..C
In your recovery environment, you may have fewer drives available for restores than you used for backups. In this situation, SQL Server times out while it waits for the additional backup images to be mounted. To prevent this time out, modify the number of drives that are available for restore.
Consider, for example, if you had performed a backup using 5 drives, and only 2 are available for recovery. In the policy, change the STRIPES 5 to STRIPES 2. This change causes SQL Server to request two backup images at a time until all five images are restored.
value from to . If you use batch files, change the stripes parameter fromMore Information