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
- Configuring local security privileges for SQL Server
- About the NetBackup Discovery Service
- 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
- About schedule properties
- Schedule backup types for SQL Server Intelligent Policies
- Adding instances to a policy
- Adding databases to a policy
- Instance properties
- Backup Selections tab
- Adding filegroups or files to the backup selections list
- Manually adding files or filegroups to the backup selections list
- Adding instance groups to a backup policy
- About tuning parameters for SQL Server backups
- Backing up read-only filegroups
- Backing up read-write filegroups
- 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
- Performing restores of SQL Server
- Starting the NetBackup MS SQL Client for the first time
- Selecting the SQL Server host and instance
- 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
- Installing the Veritas VSS provider for vSphere
- 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
- 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
- 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
- Adding clients to a policy
- Adding batch files to the backup selections list
- Selecting the SQL Server host and instance
- 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
- Backing up read-write filegroups
- Backing up SQL Server database files
- Performing partial database backups
- 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 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
- 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
- Appendix A. Sample batch files
- About sample backup batch files for legacy SQL Server policies
- Script to back up a database
- Script to perform a striped database backup and allow multiple internal buffers per stripe
- Script to perform an operation and specify the user ID and password to use to SQL Server
- Script to perform multiple operations in sequence
- Script to perform a set of operations in parallel
- Script to specify the maximum transfer size and block size for a backup
- Script that uses environment variables to exclude instances and databases from backup
- About sample restore batch files
- Script to restore a database
- Script to restore a database from multiple stripes
- Script to stage a database restore from a filegroup backup, several file backups, and transaction log backups
- Script to restore a database transaction log up to a point in time
- Script to stage a database restore from a database backup, a differential backup, and a series of transaction backups
- About sample backup batch files for legacy SQL Server policies
- Appendix B. Multiplexed backups
- Appendix C. Register authorized locations
Converting differential backups to full backups
If a differential backup runs and a full backup does not already exist for the database or filegroup, NetBackup can convert the backup to a full backup. Similarly, NetBackup can convert transaction log backups if a full backup does not already exist for the database. Enable this behavior with the keyword CONVERTBACKUP.
See Keywords and values used in batch files.
NetBackup only converts a differential backup if a full backup was never performed on the database or filegroup. If a full backup does not exist in the NetBackup catalog but SQL Server detects an existing full LSN, NetBackup performs a differential backup and not a full. In this situation, you can restore the full backup with native tools and any differentials with the NetBackup MS SQL Client. Or, if NetBackup expired the backup, you can import the full backups into the NetBackup catalog. Then you can restore both the full and the differential backups with the NetBackup MS SQL Client.
The agent checks to determine if a full backup was ever performed for each database. If no previous full backup exists, the backup is converted to a full as follows:
If you select a database for backup, the backup is converted to a full database backup.
If you select for the , the backup is converted to a full read/write filegroup backup.
If you select a filegroup for backup, NetBackup does the following:
If the filegroup is the default database filegroup, NetBackup converts the backup to a full filegroup backup.
If the filegroup is a secondary filegroup and a backup of the primary filegroup does not exist, NetBackup converts the backup to a partial full database backup. This backup contains the selected filegroup and default filegroup.
If the filegroup is a secondary filegroup and a backup of the primary filegroup does exist, NetBackup converts the backup to a full filegroup backup of the selected filegroup.
If you perform a partial differential backup, NetBackup does the following:
If no previous full backup exists for the default filegroup, NetBackup adds the filegroup to the backup and converts the operation to a full partial backup.
If a previous full backup exists for the default filegroup but a secondary filegroup in the files list does not have a full backup, NetBackup converts the operation to a full partial backup.
The CONVERTBACKUP option also detects if a full recovery database was switched to the simple recovery model and back to the full recovery model. In this scenario, the log chain is broken and SQL Server requires a differential backup before a subsequent log backup can be created. If NetBackup detects this situation, the backup is converted to a differential database backup.