Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installing NetBackup for SQL Server
- Managing SQL Server objects for use with SQL Server Intelligent Policies
- About the Applications utility
- About autodiscovery of SQL Server objects
- Using the Applications utility to view SQL Server objects
- About registering SQL Server instances and availability group replicas
- 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
- Registering a SQL Server instance or availability replica
- Registering instances or availability replicas with an instance group
- Registering instances or availability replicas automatically
- Authorizing a DBA to register instances or availability replicas with the nbsqladm command
- Deleting SQL Server objects from the Applications utility
- Manually adding a SQL Server instance in the Applications utility
- Deactivating or activating an instance
- Cleaning up instances
- Configuring SQL Server backups with SQL Server Intelligent Policy
- About SQL Server Intelligent Policies
- 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
- 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
- About using bplist to retrieve SQL Server backups
- About NetBackup for SQL Server backup names
- 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 availability groups
- About using NetBackup to protect 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)
- Prerequisites for protecting SQL Server availability groups
- Configuring an automatic backup policy for the preferred or the primary replica of a SQL Server availability group
- Creating batch files for the policy that protects the preferred or the primary replica
- Adding the batch files to the policy that protects the preferred or the primary replica
- About protecting a specific node in a SQL Server availability group (legacy backup policies)
- Configuring an automatic backup policy for a specific replica of a SQL Server availability group
- Creating a batch file for the policy that protects a specific availability replica in an availability group
- Adding the batch files to the policy that protects a specific replica in the availability group
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- Configuring SQL Server backups when an availability group crosses NetBackup domains
- Browsing for SQL Server availability group backup images
- Restoring a SQL Server availability database to a secondary replica
- Restoring a SQL Server availability database to the primary and the secondary replicas
- Restoring an availability database when an availability group crosses NetBackup domains
- Protecting SQL Server in a cluster environment
- 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
- 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
- Performing user-directed backups of SQL Server transaction logs
- Performing user-directed backups of SQL Server database filegroups
- Performing user-directed backups of read-only filegroups
- Performing user-directed backups of read-write filegroups
- Performing user-directed backups of 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
- 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
- Protecting SQL Server a log-shipping configuration
- 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
- 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
- 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 in the Applications utility
- 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
How does NetBackup resolve SQL Server host and instance names?
Normally SQL Server identifies its installations with a combination that includes the name of the host on which the installation resides plus an instance name. If you omit the instance name then NetBackup assumes that the installation is the default installation on the host. For example, a single host may contain several SQL Server installations, such as, TIGER, TIGER\ACCOUNTING, and TIGER\WAREHOUSE. A clustered instance of SQL Server resides jointly on multiple hosts and is identified with a virtual name.
When you use SQL Server Intelligent Policies, backups are cataloged as follows:
| Environment | Catalog name | Example |
|---|---|---|
Instances or databases | Host name that is registered in instance management Usually NetBackup discovers an instance automatically and you register the instance with the NetBackup client name. | sqlhost1 |
SQL Server cluster | Virtual name of SQL Server | virtsql |
Multi-NIC | Private interface name of SQL Server host | sqlhost1-NB |
SQL Server cluster in a multi-NIC environment | Private interface name of the virtual SQL Server | virtsql-NB |
SQL Server advanced and basic availability groups | Fully qualified domain name (FQDN) of the Windows Server Failover Cluster (WSFC) | wincluster-SQL.mycompany.com |
SQL Server read-scale availability group | Name of the host on which the backup was performed. | sqlhost1 |
| Environment | Catalog name | Example |
|---|---|---|
Instances or databases | NetBackup client name Usually, host name on which SQL Server resides or the host's NetBIOS name. May also be the IP name (for example, | sqlhost1 |
SQL Server cluster | Virtual name of SQL Server | virtsql |
Multi-NIC | Private interface name of SQL Server host | sqlhost1-NB |
SQL Server cluster in a multi-NIC environment | Private interface name of the virtual SQL Server | virtsql-NB |
SQL Server advanced and basic availability groups | Fully qualified domain name (FQDN) of the Windows Server Failover Cluster (WSFC) | wincluster-SQL.mycompany.com |
SQL Server read-scale availability group | Name of the host on which the backup was performed. | sqlhost1 |
In most cases when you browse for backup images using the NetBackup Microsoft SQL Client, you only need to specify the name.
NetBackup then displays the backup images for all of the instances on that host. However, to ensure that NetBackup displays the backup images you want, consider the following special cases:
Backups on a network interface that do not have the same name as the host name (such as tiger1 or tiger.apexworks.com)
In this case, the backup images are stored under the network interface name and not the NetBIOS name. To retrieve these images, see the following instructions:
See Performing restores of SQL Server when you have multiple NICs.
Backups from a UNIX (or Linux) server
This scenario may present a problem because UNIX names are case-sensitive, whereas Windows names are not. In this case, NetBackup tries to retrieve the backup images by specifying the client name with all upper case characters or all lower case characters. If the UNIX client name has mixed uppercase and lowercase characters, you must provide the client name in the box field.
SQL Host: TIGER
Source Client: Tiger
The NetBackup client name is a qualified domain name. The SQL Server host name or registered host name (Intelligent Policies) is the NetBIOS name.
To retrieve backup images specify the as the NetBIOS name and the as the fully qualified domain name.
SQL Host: Tiger
Source Client: tiger.apexworks.com
The NetBackup client name is an IP address. The SQL Server host name or registered host name (Intelligent Policies) is the NetBIOS name.
To retrieve backup images specify the as the NetBIOS name and the as the IP address:
SQL Host: Tiger
Source Client: 10.80.136.68