NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Configuring SQL Server hosts and user permissions
- Installing the Veritas VSS provider for vSphere
- Disabling the SQL Server VSS Writer service
- Configuring the NetBackup services for SQL Server backups and restores
- Configure local security privileges for SQL Server
- Reviewing the auto-discovered mappings
- Configuring mappings for restores of a distributed applications, clusters, or virtual machines
- Configuring the ODBC connection
- Configure NetBackup for the SQL Server non-readable secondary instances that are hidden
- Configuring the primary server host name for the SQL Server agent
- Configure the number of jobs allowed for backup operations
- Configure the Maximum jobs per client setting
- Managing SQL Server objects for use with SQL Server Intelligent Policies
- About the Applications utility
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- About SQL Server credentials
- 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 add a SQL Server instance
- Deactivating or activating an instance
- Cleaning up instances
- Configuring backups with SQL Server Intelligent Policy
- About SQL Server Intelligent Policies
- Creating a 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
- 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
- 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 an application database with VMware backups
- About configuring NetBackup for VMware backups that protect SQL Server
- Configuring the NetBackup services for a VMware backup that protects 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
- Restore SQL Server databases from a VMware backup
- Configuring backups with Snapshot Client
- About NetBackup Snapshot Client for SQL Server
- How SQL Server operations use Snapshot Client
- Snapshot methods
- 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 snapshots
- Protecting SQL Server availability groups
- About protecting 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)
- Protect a SQL Server availability group that 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 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
- Performance and troubleshooting
- What are the components of NetBackup for SQL Server?
- How does NetBackup for SQL Server back up a database?
- How does NetBackup for SQL Server recover a database?
- Performing a manual backup
- About debug logging for SQL Server troubleshooting
- NetBackup for SQL Server performance factors
- About monitoring NetBackup for SQL Server operations
- Setting the maximum trace level for NetBackup for SQL Server
- Troubleshooting credential validation
- Reporting of unsuccessful filegroup or file backups
- About minimizing timeout failures on large SQL Server database restores
- Troubleshooting VMware backups
- 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
- Unable to discover or browse availability group replicas
- About disaster recovery of SQL Server
- Appendix A. Other configurations
- Configuring multiplexed backups of SQL Server
- Restoring a multiplexed SQL Server backup
- About SQL Server backups and restores in an SAP environment
- Configuring NetBackup to support database log-shipping
- Backing up SQL Server in an environment with log shipping
- About NetBackup for SQL Server with database mirroring
- Appendix B. Register authorized locations
Reviewing the auto-discovered mappings
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. Or, manually add the mappings.
See Approve the auto-discovered mappings for a cluster.
See Auto-discovered mappings for a SQL Server cluster in a multiple NIC environment.
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.
These mappings are configured in the node in the NetBackup web UI. You can also use the nbhostmgmt command to manage the mappings. See the NetBackup Security and Encryption Guide and NetBackup Web UI Administrator's Guide for more details.
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, the virtual name must be mapped to each node.
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 web UI, expand Security > Host mappings.
- Click the Mappings to approve 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
- Click the name of the host.
- Review the mappings for the host and click Approve if you want to use the discovered mappings.
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.
For hosts
client01.lab04.comandclient02.lab04.com, you see entries for Mapped host or IP address 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.
In Table: Example mapped host names for SQL Server environments, FCI is a SQL Server failover cluster instance. 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 | |
Basic or advanced availability group (primary and secondary) | Primary name | WSFC name |
Secondary name | WSFC name | |
Basic or advanced availability group, 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 web UI, expand Security > Host mappings.
- Click the Mappings to approve 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
- Click the name of the host.
- Review the mappings for the host and click Approve if you want to use the discovered mappings.
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.
For hosts
client01-bk.lab04.comandclient02-bk.lab04.com, you may see the following Mapped host or IP address.Host
Mapped host or IP address
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.
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 |
To approve the auto-discovered mappings for a SharePoint SQL availability group
- In the NetBackup web UI, expand Security > Host mappings.
- Click the Mappings to approve 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 SharePoint SQL with hosts
client01.lab04.comandclient02.lab04.com, you may see the following entries:Host
Auto-discovered mapping
client01.lab04.com
client01, clustername, clustername.lab04.com
client01.lab04.com
aglistenername
client01.lab04.com
aglistenername.lab04.com
client02.lab04.com
client02, clustername, clustername.lab04.com
client02.lab04.com
aglistenername
client02.lab04.com
aglistenername.lab04.com
- Click the name of the host.
- Review the mappings for the host and click Approve if you want to use the discovered mappings.
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
aglistenername
The listener name of the SharePoint SQL availability group
aglistenername.lab04.com
The FQDN of the listener name of the SharePoint SQL availability group.
- When you finish approving the valid mappings for the hosts, click on the Hosts tab.
For hosts
client01.lab04.comandclient02.lab04.com, you see entries for Mapped host or IP address that are similar to the following:Host
Mapped host names/IP addresses
client01.lab04.com
client01.lab04.com, client01, aglistenername, aglistenername.lab04.com
client02.lab04.com
client02.lab04.com, client02, aglistenername, aglistenername.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
To manually map host names
- In the NetBackup web UI, expand Security > Host mappings.
- Click on the Hosts tab.
- Click Add shared or cluster mappings.
For example, type the name of the virtual name of the cluster. Then click Add to choose the hosts to which you want to map that virtual name.