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
Reviewing the auto-discovered mappings in Host Management
In certain scenarios, a NetBackup host shares a particular name with other hosts or has a name that is associated with a cluster. To successfully perform backups and restores with NetBackup for SQL Server, you must approve each valid Auto-Discovered Mapping that NetBackup discovers in your environment. These mappings appear in the Host Management properties on the master server. You can also use the nbhostmgmt command to manage the mappings. See the Security and Encryption Guide for more details on Host Management properties.
Examples of the configurations that have multiple host names include:
A host is associated with its fully qualified domain name (FQDN) and its short name or its IP address.
If the SQL Server is clustered, the host is associated with its node name and the virtual name of the cluster.
In a SQL Server cluster environment, you must map the node names to the virtual name of the cluster if the following apply:
If the backup policy includes the cluster name (or virtual name)
If the NetBackup client is installed on more than one node in the cluster
If the NetBackup Client is only installed on one node, then no mapping is necessary.
To approve the auto-discovered mappings for a cluster
- In the NetBackup Administration Console, expand Security Management > Host Management.
- At the bottom of the Hosts pane, click the Mappings for Approval tab.
The list displays the hosts in your environment and the mappings or additional host names that NetBackup discovered for those hosts. A host has one entry for each mapping or name that is associated with it.
For example, for a cluster with hosts
client01.lab04.comandclient02.lab04.com, you may see the following entries:Host
Auto-discovered Mapping
client01.lab04.com
client01
client01.lab04.com
clustername
client01.lab04.com
clustername.lab04.com
client02.lab04.com
client02
client02.lab04.com
clustername
client02.lab04.com
clustername.lab04.com
- If a mapping is valid, right-click on a host entry and click Approve.
For example, if the following mappings are valid for
client01.lab04.com, then you approve them.Auto-discovered Mapping
Valid name for
client01
The short name of the client
clustername
The virtual name of the cluster
clustername.lab04.com
The FQDN of the virtual name of the cluster
- When you finish approving the valid mappings for the hosts, click on the Hosts tab at the bottom of the Hosts pane.
For hosts
client01.lab04.comandclient02.lab04.com, you see Mapped Host Names/IP Addresses that are similar to the following:Host
Mapped Host Names/IP Addresses
client01.lab04.com
client01.lab04.com, client01, clustername, clustername.lab04.com
client02.lab04.com
client02.lab04.com, client02, clustername, clustername.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Click on the Hosts tab, then right-click in the Hosts pane and click Add Shared or Cluster Mappings. For example, provide the name of the virtual name of the cluster. Then click Select Hosts to choose the node names in the cluster to which you want to map that virtual name.
In Table: Example mapped host names for SQL Server environments, FCI is a SQL Server failover cluster instance. AG is an availability group. WSFC is Windows Server Failover Cluster.
Table: Example mapped host names for SQL Server environments
Environment | ||
|---|---|---|
FCI (cluster with two nodes) | Physical name of Node 1 | Virtual name of the SQL Server cluster |
Physical name of Node 2 | Virtual name of the SQL Server cluster | |
AG (primary and secondary) | Primary name | WSFC name |
Secondary name | WSFC name | |
AG with an FCI (primary FCI and secondary FCI) | Primary FCI name | WSFC name |
Secondary FCI name | WSFC name | |
Physical name of Node 1 | Virtual name of the SQL Server cluster | |
Physical name of Node 2 | Virtual name of the SQL Server cluster |
If you have a SQL Server cluster in a multi-NIC environment, you need to approve each valid Auto-Discovered Mapping for the hosts in that environment. You must map the virtual name of the SQL Server cluster on the private network to the private name of each SQL Server cluster node.
To approve the auto-discovered mappings for a SQL Server cluster in a multiple NIC environment
- In the NetBackup Administration Console, expand Security Management > Host Management.
- At the bottom of the Hosts pane, click the Mappings for Approval tab.
The list displays the hosts in your environment and the mappings or additional host names that NetBackup discovered for those hosts. A host has one entry for each mapping or name that is associated with it.
For example, for a cluster in a multi-NIC environment with hosts
client01-bk.lab04.comandclient02-bk.lab04.com, you may see the following entries:Host
Auto-discovered Mapping
client01-bk.lab04.com
clustername-bk.lab04.com
client02-bk.lab04.com
clustername-bk.lab04.com
- If a mapping is valid, right-click on a host entry and click Approve.
For example, if following mapping is valid for
client01-bk.lab04.com, then you approve it.Auto-discovered Mapping
Valid name for
clustername-bk.lab04.com
The virtual name of the SQL Server cluster on the private network
- When you finish approving the valid mappings for the hosts, click on the Hosts tab at the bottom of the Hosts pane.
For hosts
client01-bk.lab04.comandclient02-bk.lab04.com, you may see the following Mapped Host Names/IP Addresses.Host
Mapped Host Names/IP Addresses
client01-bk.lab04.com
clustername-bk.lab04.com
client02-bk.lab04.com
clustername-bk.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Click on the Hosts tab, then right-click in the Hosts pane and click Add Shared or Cluster Mappings. For example, provide the name of the virtual name of the cluster. Then click Select Hosts to choose the hosts to which you want to map that virtual name.
Table: Example mapped host names for a SQL Server cluster in a multi-NIC environment
Private name of Node 1 | Virtual name of the SQL Server cluster on the private network |
Private name of Node 2 | Virtual name of the SQL Server cluster on the private network |