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- About Instance management for a SQL Server Intelligent Policy
- About credentials used with SQL Server Intelligent Policy
- Configuring the NetBackup services for SQL Server backups and restores (SQL Server Intelligent Policy)
- Configuring local security privileges for SQL Server (SQL Server Intelligent Policy)
- About the NetBackup Discovery Service (NetBackup for SQL)
- Viewing the SQL Server instances and instance groups in instance management
- About registering SQL Server instances
- Manually adding a SQL Server instance in instance management
 
- Configuring SQL Server backups with SQL Server Intelligent Policy- About SQL Server Intelligent Policies
- About configuring SQL Server backups with SQL Server Intelligent Policy
- Adding a new SQL Server Intelligent Policy
- About policy attributes for NetBackup for SQL Server
- About schedule properties (SQL Server Intelligent Policy)
- Schedule backup types for SQL Server Intelligent Policies
- Adding instances to a policy (SQL Server Intelligent Policy)
- Adding databases to a policy (SQL Server Intelligent Policy)
- Instance properties
- Backup Selections tab
- Adding SQL Server filegroups or files to the backup selections list
- Manually adding SQL Server files or filegroups to the backup selections list (SQL Server Intelligent Policy)
- Adding instance groups to a SQL Server Intelligent Policy
- About tuning parameters for SQL Server backups
- Backing up read-only filegroups (SQL Server Intelligent Policies)
- Backing up read-write filegroups (SQL Server Intelligent Policies)
 
- Configuring NetBackup for SQL Server- Configuring mappings for restores of a distributed application, cluster, or virtual machine
- Reviewing the auto-discovered mappings in Host Management
- About NetBackup for SQL performance factors
- Configuring the number of jobs allowed for backup operations
- Configuring the Maximum jobs per client setting
- Configuring multistriped backups of SQL Server
- Performing a manual backup (NetBackup for SQL Server)
 
- Performing restores of SQL Server- Starting the NetBackup MS SQL Client for the first time (legacy SQL Server policies)
- Selecting the SQL Server host and instance (SQL Server restores)
- Browsing for SQL Server backup images
- Options for NetBackup for SQL Server restores
- Restoring a SQL Server database backup
- Staging a full SQL Server database recovery
- Restoring SQL Server filegroup backups
- Recovering a SQL Server database from read-write filegroup backups
- Restoring SQL Server read-only filegroups
- Restoring SQL Server database files
- Restoring a SQL Server transaction log image without staging a full recovery
- Performing a SQL Server database move
- About performing a SQL Server page-level restore
- Configuring permissions for redirected restores
- Redirecting a SQL Server database to a different host
- Performing a restore of a remote SQL Server installation
- About restores of a database that contain full-text catalog
- Restoring multistreamed SQL Server backups
 
- Protecting SQL Server data with VMware backups- About protecting SQL Server data with VMware backups
- About configuring NetBackup for VMware backups that protect SQL Server
- Using NetBackup Accelerator to increase speed of full VMware backups (NetBackup for SQL Server)
- Installing the Veritas VSS provider for vSphere (NetBackup for SQL)
- Configuring the NetBackup services for VMware backups that protect SQL Server
- Configuring a VMware backup policy to protect SQL Server
- Configuring a VMware policy to protect SQL Server using Replication Director to manage snapshot replication
- About truncating logs with a VMware backup that protects SQL Server
- Restoring SQL Server databases from a VMware backup
 
- Using NetBackup for SQL Server with Snapshot Client- About NetBackup Snapshot Client for SQL Server
- How SQL Server operations use Snapshot Client
- Configuration requirements for SQL Server snapshot and Instant Recovery backups
- Configuring a snapshot policy for SQL Server
- Configuring a policy for Instant Recovery backups of SQL Server
- 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 SQL Server high availability (HA) environments
- About using NetBackup to protect SQL Server availability groups- Limitations of backups of 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 (legacy backup policies)
- Configuring SQL Server backups when an availability group crosses NetBackup domains
- Restoring a SQL Server availability group database to the primary and the secondary replicas
- Restoring a SQL Server availability group database to a secondary replica
- Restoring an availability group database when an availability group crosses NetBackup domains
 
- Configuring backups of clustered SQL Server instances (SQL Server Intelligent Policy)
- Configuring backups of clustered SQL Server instances (legacy SQL Server policies)
- Performing a restore of a virtual SQL Server instance
- About NetBackup for SQL Server with database mirroring
- Configuring NetBackup to support database log-shipping
- Backing up SQL Server in an environment with log shipping
 
- Backup and recovery concepts- Overview of SQL Server backup and recovery concepts
- What are the components of NetBackup for SQL Server?
- How does NetBackup resolve SQL Server host and instance names?
- How does NetBackup for SQL Server back up a database?
- How does NetBackup for SQL Server recover a database?
- Protecting SQL Server files and filegroups
- About recovery considerations for SQL Server files and filegroups
- Reducing backup size and time by using read-only filegroups
- What factors affect the data transfer rate during a SQL Server backup or restore operation?
- About recovery factors for SQL Server
 
- Using NetBackup for SQL Server with multiple NICs- About configuration of SQL Server backups with multiple NICs
- Configuring the NetBackup client with the private interface name
- Configuring backups of SQL Server when you have multiple NICs (SQL Server Intelligent Policies)
- Configuring backups for SQL Server when you have multiple NICs (legacy SQL Server policies)
- Performing restores of SQL Server when you have multiple NICs
- Configuring backups of a SQL Server cluster when you have multiple NICs (SQL Server Intelligent Policies)
- Configuring backups of a SQL Server cluster when you have multiple NICs (legacy SQL Server policies)
- Creating a batch file for backups of a SQL Server cluster when you have multiple NICs (legacy SQL Server policies)
- Performing restores of a SQL Server cluster when you have multiple NICs
 
- Configuring backups with legacy SQL Server policies using clients and batch files- About legacy SQL Server policies
- About configuring backups with legacy SQL Server policies
- Configuring the NetBackup services for SQL Server backups and restores (legacy SQL Server policies)
- About SQL Server security with NetBackup legacy backup policies
- About using batch files with NetBackup for SQL Server
- Adding a new SQL Server legacy policy
- About schedule properties (legacy SQL Server policies)- SQL Server backup types (for legacy policies)
- Converting differential backups to full backups
- Configuring an application backup schedule (NetBackup for SQL Server)
- Example application backup schedule (NetBackup for SQL Server)
- Configuring automatic backup schedules (NetBackup for SQL Server)
- Example automatic backup schedule (NetBackup for SQL Server)
 
- Adding clients to a policy
- Adding batch files to the backup selections list (NetBackup for SQL Server legacy policy)
- Selecting the SQL Server host and instance (SQL Server backups with legacy backup policies)
- Options for SQL Server backup operations
- About viewing the properties of the objects selected for backup
- Performing user-directed backups of SQL Server databases
- Backing up SQL Server transaction logs
- Backing up SQL Server database filegroups
- Backing up read-only filegroups (legacy SQL Server backup policies)
- Backing up read-write filegroups (legacy SQL Server backup policies)
- Backing up SQL Server database files
- Performing partial database backups (SQL Server legacy backup policies)
- Performing a backup of a remote SQL Server installation
- About file checkpointing with NetBackup for SQL Server
- About automatic retry of unsuccessful SQL Server backups
 
- 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
- About manual backups of SQL Server in an SAP environmentAbout manual backups of SQL Server in an SAP environment
- About policy configuration for SQL Server in an SAP environment
 
- Troubleshooting- About monitoring NetBackup for SQL Server operations
- About NetBackup reports for SQL Server troubleshooting
- About debug logging for SQL Server troubleshooting
- Setting the maximum trace level for NetBackup for SQL Server
- Troubleshooting credential validation with instance management (NetBackup for SQL Server)
- About minimizing timeout failures on large SQL Server database restores
- Troubleshooting VMware backups and restores of SQL Server
- Delays in completion of backup jobs
- SQL Server log truncation failure during VMware backups of SQL Server
- SQL Server restore fails when you restore a SQL Server compressed backup image as a single stripe or with multiple stripes
- Incorrect backup images are displayed for availability group clusters
- A restore of a SQL Server database fails with Status Code 5, or Error (-1), when the host name of the SQL Server or the SQL Server database name has trailing spaces
- A move operation fails with Status Code 5, or Error (-1), when the SQL Server host name, the database name, or the database logical name has trailing spaces
 
- Disaster recovery of a SQL Server
- NetBackup for SQL dialog box topics
- NetBackup for SQL dialog box fields- Backup History Options field descriptions
- Manage Scripts field descriptions
- NetBackup client properties field descriptions
- Viewing properties of objects selected for restore
- About selecting database objects for restore
- SQL Server connection properties
- SQL Server connection properties field descriptions
 
- Appendix A. Sample batch files- About sample backup batch files for legacy SQL Server policies- Script to back up a database (NetBackup for SQL Server)
- Script to perform a striped database backup and allow multiple internal buffers per stripe (NetBackup for SQL Server)
- Script to perform an operation and specify the user ID and password to use to SQL Server (NetBackup for SQL Server)
- Script to perform multiple operations in sequence (NetBackup for SQL Server)
- Script to perform a set of operations in parallel (NetBackup for SQL Server)
- Script to specify the maximum transfer size and block size for a backup (NetBackup for SQL Server)
- Script that uses environment variables to exclude instances and databases from backup(NetBackup for SQL Server)
 
- About sample restore batch files- Script to restore a database (NetBackup for SQL Server)
- Script to restore a database from multiple stripes (NetBackup for SQL Server)
- Script to stage a database restore from a filegroup backup, several file backups, and transaction log backups (NetBackup for SQL Server)
- Script to restore a database transaction log up to a point in time (NetBackup for SQL Server)
- Script to stage a database restore from a database backup, a differential backup, and a series of transaction backups (NetBackup for SQL Server)
 
 
- About sample backup batch files for legacy SQL Server policies
- Appendix B. Multiplexed backups
- Appendix C. Register authorized locations
About performing a SQL Server page-level restore
Note:
Page-level restores are only applicable for SQL Server legacy backup policies.
If a portion of a SQL Server database is corrupted due to hardware failure, you may be able to use page-level restore. Use page-level restore to recover only the pages that were corrupted. Page-level restore can reduce the total downtime if you only need to restore a relatively small number of pages. If many pages are corrupt, then a full database recovery may be faster.
When you select the page restore option, NetBackup for SQL Server creates a page restore template.
This template includes the following parts:
- A page restore operation that you can modify by inserting the IDs of the pages that you want to restore. 
- A series of transaction log images for recovering the database to the current point in time. 
- A tail-log backup and recovery operation, which is required to bring the database online. 
The following requirements and limitations exist when you perform SQL Server page-level restores:
- Pages can be restored from the following backup types: Database, filegroup, file, read-write filegroups, and partial database. 
- Your SQL Server must use either the full or bulk-logged recovery model. 
- SQL Server sometimes cannot recover the specific pages that you request if they contain critical information about the definition of the database itself. For example, you cannot use page-level restore for the first page in a database file. When you detect that page-level restore does not work, you need to use full database recovery. 
- A maximum of 1000 pages can be recovered from a backup image through a page-level restore. 
This topic describes how to perform page-level restores. Note that the Microsoft SQL Server service must have full access permission to the folder install_path\netbackup\dbext\mssql\temp.
To perform a page-level restore
- Obtain a list of corrupt pages in the database.SQL Server Books Online suggests several methods for obtaining a list of corrupt pages. One of these methods is to run the command DBCC checkdb from the SQL Server Management Studio. 
- Browse for the backup images you want to restore.
- In the Restore Microsoft SQL Server Objects dialog box, expand the database instance.
- Expand the database.
- Select the database backup image that contains pages you want to restore.
- From the Scripting list, select Create a page restore template.
- Click Restore.
- In the Save Script As dialog box, type a file name for the page restore script and click Save.
- Click Yes to open the template in Notepad.
- Edit the page first operation the page IDs that you want to replace.For example, replace: # # Create one or more page restore requests. These use the following format #PAGE file-id:page-id with # # Create one or more page restore requests. These use the following format PAGE 1:14 PAGE 1:20 
- When you finish modifying the template, save it.
- To run the restore, select File > Manage script files, select the script you created, and click Start.
- Click Yes to start the restore.
More Information