NetBackup™ for Microsoft SQL Server Administrator's Guide
- About NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Configuring SQL Server hosts and user permissions
- Installing the Veritas VSS provider for vSphere
- Configure 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
- Configure the ODBC connection
- Configure NetBackup for the SQL Server non-readable secondary instances that are hidden
- Configure 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
- Configuring RBAC for SQL Server administrators
- Managing SQL Server assets and their credentials
- About the Workloads > Microsoft SQL Server utility
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- About options to register SQL Server credentials
- Register a SQL Server instance or replica with an existing credential
- Register a SQL Server instance or replica with a new credential
- Add a credential for SQL Server
- View the credential name that is applied to an asset
- Edit or delete a named credential
- Browse SQL Server assets
- View the protection status of databases, instances, or availability groups
- Use Backup now to back up a SQL Server asset
- Remove SQL Server instances
- Remove SQL Server databases
- Manually add a SQL Server instance
- Deactivate or activate an instance
- Configuring backups with SQL Server Intelligent Policy
- About SQL Server Intelligent Policies
- Create a SQL Server Intelligent Policy
- About policy attributes
- Schedule properties for SQL Server Intelligent Policies
- Schedule backup types for SQL Server Intelligent Policies
- Add instances to a policy
- Add databases to a policy
- Add filegroups or files to the backup selections list
- Add instance groups to a backup policy
- Performance tuning and configuration options
- Back up read-only filegroups
- Back up read-write filegroups
- Perform a manual backup
- 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 batch file-based policies
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- Prerequisites for protecting SQL Server availability groups
- Configure an automatic backup policy for the preferred or the primary replica of a SQL Server availability group
- Create batch files for the policy that protects the preferred or the primary replica
- Add 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 (batch file-based policies)
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- Protect a SQL Server availability group that crosses NetBackup domains
- Protecting SQL Server with VMware backups
- About protecting an application database with VMware backups
- About configuring NetBackup 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
- Create a protection plan to protect SQL Server data with a VMware backup
- Protect SQL Server data with a VMware backup
- Configuring backup policies 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
- Configure a snapshot policy for SQL Server
- Configure 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 in a cluster environment
- Managing protection plans for SQL Server
- Restoring SQL Server with the NetBackup web UI
- Requirements for restores of SQL Server
- Perform a complete database recovery
- Recover a single recovery point
- Options for SQL Server restores
- Restore a database (non-administrator users)
- Select a different backup copy for recovery
- Configuring permissions for redirected restores
- Restore SQL Server databases from a VMware backup
- Restore a SQL Server availability database to a secondary replica
- Restore a SQL Server availability database to the primary and the secondary replicas
- Restoring an availability database when an availability group crosses NetBackup domains
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Things to consider before you configure an instant access database
- Configure Samba users for SQL Server instant access
- Configure an instant access database
- View the livemount details of an instant access database
- Delete an instant access database
- Options for NetBackup for SQL Server instant access
- NetBackup for SQL Server terms
- Frequently asked questions
- Configuring batch-file based policies for SQL Server backups
- About batch file-based policies for SQL Server backups
- Overview of configuring SQL Server backups with batch file-based policies
- Configure the NetBackup services for SQL Server backups and restores (batch file-based policies)
- About SQL Server security with batch file-based policies
- Requirements to use batch files with NetBackup for SQL Server
- Add a batch file-based policy
- Schedule properties for SQL Server batch file-based policies
- Add clients to a policy
- Add batch files to the backup selections list
- Options for SQL Server backup operations
- Create a script to backup a remote SQL Server installation
- About automatic retry of unsuccessful SQL Server backups
- Configure a batch file-based policy for a user-directed backup of read-only filegroups
- Configure a batch file-based policy for a user-directed backup of read-write filegroups
- Performing backups and restores with the NetBackup MS SQL Client
- About the NetBackup MS SQL Client
- Start the NetBackup MS SQL Client for the first time
- Select the SQL Server host and instance (NetBackup MS SQL Client)
- About viewing the properties of the objects selected for backup
- Perform a user-directed backup of SQL Server databases (NetBackup MS SQL Client)
- Perform a user-directed backup of SQL Server transaction logs (NetBackup MS SQL Client)
- Perform a user-directed backup of SQL Server database filegroups (NetBackup MS SQL Client)
- Perform a user-directed backup of SQL Server database files (NetBackup MS SQL Client)
- Perform a partial database backup (NetBackup MS SQL Client)
- Options for NetBackup for SQL Server restores
- Browsing for SQL Server backup images (NetBackup MS SQL Client)
- Restore a SQL Server database backup (NetBackup MS SQL Client)
- Stage a full SQL Server database recovery (NetBackup MS SQL Client)
- Restore SQL Server filegroup backups (NetBackup MS SQL Client)
- Recover a SQL Server database from read-write filegroup backups (NetBackup MS SQL Client)
- Restore SQL Server read-only filegroups (NetBackup MS SQL Client)
- Restore SQL Server database files (NetBackup MS SQL Client)
- Restore a SQL Server transaction log image without staging a full recovery (NetBackup MS SQL Client)
- Perform a SQL Server database move (NetBackup MS SQL Client)
- About performing a SQL Server page-level restore (NetBackup MS SQL Client)
- Redirect a SQL Server database to a different host (NetBackup MS SQL Client)
- Perform a restore of a remote SQL Server installation (NetBackup MS SQL Client)
- Restoring multistreamed SQL Server backups
- About using bplist to retrieve SQL Server backups
- About NetBackup for SQL Server backup names
- Using NetBackup for SQL Server with multiple NICs
- Configuration and requirements for SQL Server backups with multiple NICs
- Configure the NetBackup client with the private interface name
- Configure backups of SQL Server when you have multiple NICs (SQL Server Intelligent Policies)
- Configure backups for SQL Server when you have multiple NICs (batch file-based policies)
- Restore SQL Server when you have multiple NICs (NetBackup MS SQL Client)
- Configure backups of a SQL Server cluster when you have multiple NICs (SQL Server Intelligent Policies)
- Configure backups of a SQL Server cluster when you have multiple NICs (batch file-based policies)
- Create a batch file for backups of a SQL Server cluster when you have multiple NICs (batch file-based policies)
- Restore a SQL Server cluster when you have multiple NICs (NetBackup MS SQL Client)
- Performance and troubleshooting
- NetBackup for SQL Server performance factors
- About debug logging for SQL Server troubleshooting
- Troubleshooting credential validation
- Troubleshooting VMware backups
- SQL Server log truncation failure during VMware backups of SQL Server
- About monitoring NetBackup for SQL Server operations
- Set the maximum trace level for NetBackup for SQL Server
- Reporting of unsuccessful filegroup or file backups
- About minimizing timeout failures on large SQL Server database restores
- 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
- Configure 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 |
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.