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
- 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
Configure the NetBackup services for SQL Server backups and restores (batch file-based policies)
NetBackup uses the NetBackup Client Service and the NetBackup Legacy Network Service to access the SQL Server when it performs backups and restores. With the proper configuration, these services can log on with the Local System account or another account that has the necessary privileges.
The logon account for the services requires the following:
Both services must use the same logon account.
The SQL Server "sysadmin" role.
Apply the sysadmin role manually to the NT AUTHORITY\SYSTEM or the BUILTIN\Administrators group.
For a SQL Server cluster or SQL Server availability group, configure the NetBackup services on each node in the cluster or availability group.
For VMware backups, different configuration is required for logon account for the services.
See Configure the NetBackup services for SQL Server backups and restores.
To configure the NetBackup services for SQL Server backups and restores
- Log on to the Windows host with the account that has the sysadmin role.
- If the SQL Server instance uses standard or mixed security, perform the following steps:
Open the NetBackup MS SQL Client.
Select File > Set SQL Server connection properties.
Provide the SQL Server Userid and Password.
Click Apply > Close.
- In the Windows Services application, open the NetBackup Client Service entry and click the Log On tab.
- Confirm that Local System account is selected.
If you selected a different logon account, stop and restart the service.
- Open the NetBackup Legacy Network Service entry and click the Log On tab.
- Confirm that Local System account.
If you selected a different logon account, stop and restart the service.