Please enter search query.
Search <book_title>...
NetBackup™ for Microsoft SQL Server Administrator's Guide
Last Published:
2024-09-30
Product(s):
NetBackup & Alta Data Protection (10.5)
- About NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Installing the Veritas VSS provider for vSphere
- Configuring RBAC for SQL Server administrators
- Managing SQL Server assets and their credentials
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Configuring backups with SQL Server Intelligent Policy
- Performance tuning and configuration options
- 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)
- 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)
- Protecting SQL Server with VMware backups
- About protecting an application database with VMware backups
- Create a protection plan to protect SQL Server data with a VMware backup
- Configuring backup policies with Snapshot Client
- 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
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Configuring batch-file based policies for SQL Server backups
- Requirements to use batch files with NetBackup for SQL Server
- Schedule properties for SQL Server batch file-based policies
- Configure a batch file-based policy for a user-directed backup of read-only filegroups
- Performing backups and restores with the NetBackup MS SQL Client
- Redirect a SQL Server database to a different host (NetBackup MS SQL Client)
- Restoring multistreamed SQL Server backups
- Using NetBackup for SQL Server with multiple NICs
- Performance and troubleshooting
- About debug logging for SQL Server troubleshooting
- About disaster recovery of SQL Server
- Appendix A. Other configurations
- About SQL Server backups and restores in an SAP environment
- About NetBackup for SQL Server with database mirroring
- Appendix B. Register authorized locations
Configure NetBackup to support database mirroring
To use database mirroring with NetBackup, both the principal and the mirror should be set up as clients of the same primary server.
To configure NetBackup to support database mirroring
- The hosts that contain both databases should specify the same primary server in their server lists.
- Any policy that is used to back up the principal should also specify the host that contains the mirror database.
- On the primary server, configure permissions for a redirected restored for both mirroring partners.
- (Conditional) If you specify the fully-qualified domain name (FQDN) for the client in the backup policy, you need to create an alias for the short client name. This alias lets you successfully browse for a backup image and restore it in a mirrored environment. NetBackup attempts to find a mirrored partner backup image using the short name of the client host (for example,
client1
). However, the backup image in this case is stored using the FQDN (for example,client1.domain.com
).You can create an alias in one of the following ways:
On the NetBackup client, create the following touch file:
install_path\dbext\mssql\ClientNameMapping.txt
Add an entry
<short name of client host> <FQDN of client host>
. For example:client1 client1.domain.com
On the NetBackup primary server, use the bpclient command to create the alias:
bpclient -client client_name -M master_server -add_alias alias_name
For example:
bpclient -client client1.domain.com -M primary.domain.com -add_alias hpe013-vm02
You must use the FQDN for the -client argument.