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
About credentials used with SQL Server Intelligent Policy
To protect an instance group or instance with a SQL Server Intelligent Policy, you must register the group or instance with credentials. Refer to Table: Options to register credentials to determine the best option for your environment.
SQL Server instances must be registered with Windows credentials that have the proper permissions to perform backup and restore operations. Intelligent Policy supports Windows authentication and Windows Active Directory authentication. It does not support Mixed Mode or SQL Server authentication. Credentials are not supported at the database level.
Table: Options to register credentials
Option to register credentials | Environment or configuration | Notes |
|---|---|---|
|
Use these specific credentials |
| (Recommended) Veritas recommends that you use this option to register credentials. See Requirements when you register instances using specific credentials. |
Use credentials that are defined locally on the client |
| The NetBackup services run as a privileged SQL Server user on the client. See Requirements when you register instances using locally defined credentials. |
Add to group and register using group credentials | You want to be able to do one or more of the following:
| A group's credentials can be configured to use a specific set of credentials (each instance uses the same credentials). Or a group can be configured to use locally defined credentials (each instance uses the credentials that are defined for that instance). |
Command line |
|
The following requirements apply when you use the option to register an instance or instances in an instance group:
The user must have the SQL Server "sysadmin" role.
The user must be a member of the Windows Administrators group.
The logon account for the NetBackup Client Service and the NetBackup Legacy Network Service can be either the SQL System administrator or Local System. The services do not have to use the same logon account.
See Configuring the NetBackup services for SQL Server backups and restores.
The logon account for the NetBackup Client Service and the NetBackup Legacy Network Service must have the privileges to and .
When you use the option to register an instance or instances in an instance group, NetBackup uses the credentials for the user that installed NetBackup. The following requirements apply with this option:
The user must have the SQL Server "sysadmin" role.
The user must be a member of the Windows Administrators group.
The logon account for the NetBackup Client Service and the NetBackup Legacy Network Service can be either the SQL System administrator or Local System. The services must use the same logon account.
See Configuring the NetBackup services for SQL Server backups and restores.
To register an instance from the command line, the following configuration is required:
The NetBackup administrator must authorize the nbsqladm command for a specific DBA or user on a specific host.
On the NetBackup master server, use nbsqladm to authorize the user:
nbsqladm [-S master_server] -add_dba host_name user_name
If you have multiple NICs, authorize the DBA using the private interface name of the SQL Server host. For a SQL Server cluster, authorize the DBA for each node in the cluster. (Do not authorize a DBA using the virtual name of the SQL Server cluster.) For the -host name provide one of the node names in the SQL cluster. For a SQL Server cluster with multiple NICs, authorize the DBA using the private interface name for each of the nodes in the SQL Server cluster.
Once a DBA is authorized to use the nbsqladm command, the DBA can register instances with the local credentials (-local_credentials) or other specific credentials (-user name -domain name).
For complete details on the nbsqladm command, see the NetBackup Commands Reference Guide.
When NetBackup discovers a SQL Server cluster, it adds a single entry to instance management. This instance represents all nodes in the cluster. The host name is the virtual name of the SQL Server cluster. When you register this instance NetBackup validates the credentials on the active node. The credentials must be valid for all nodes in the cluster.
When NetBackup discovers a SQL Server host that uses multiple NICs, it adds an entry using the NetBackup client name to instance management. If you installed the NetBackup client using the public interface name, you must configure the NetBackup client name as the private interface name. Then register the instance with its private interface name. For a SQL Server cluster that uses multiple NICs, add and register the instance with the private virtual name of the SQL Server cluster.
See Configuring the NetBackup client with the private interface name.
More details are available troubleshooting the validation of credentials.
See Troubleshooting credential validation with instance management.