Introducing NetVault Backup Plug-in for SQL Server
NetVault Backup Plug-in for SQL Server: at a glance
Key benefits
Feature summary
Target audience
Recommended additional reading
Planning your SQL Server deployment
Deployment overview
Standalone deployment
High-availability deployments on Windows
NetVault Backup Policy Management
Installing and removing the plug-in
Installation prerequisites
Configuring the plug-in
Prerequisites for a standalone deployment
Additional prerequisites for a high-availability deployment
Prerequisites for Linux
Installing or upgrading the plug-in in a standalone environment
Installing or upgrading the plug-in in a high-availability environment
Licensing the plug-in
Removing the plug-in from a standalone deployment
Removing a SQL Server Instance
Configuring authentication details
Configuring the NetVault Backup Virtual Client on Windows
Configuring plug-in options
Entering logon credentials for all instances on a client
Configuring an instance at the All Instances level on a client
Entering default logon credentials for a specific SQL Server Instance
Changing the TCP/IP port for SQL Server
Setting up SQL Server Authentication for SQL Server 2012 or later (Windows only)
Configuring domain administrator account for service exploration
Backing up data
Defining a backup strategy
Restoring data
Reviewing the available backup methods
Reviewing SQL Server recovery models
Defining an Online VDI backup strategy and reviewing types
Understanding snapshot-based backups
Reviewing the compression features
Performing Online VDI backups
Full Database backup for Online VDI
Differential Database backup for Online VDI
Copy-Only backup for Online VDI
Incremental Transaction Log backup for Online VDI
Tail-Log backup for Online VDI
Full File and Filegroup backup for Online VDI
Differential File and Filegroup backup for Online VDI
Partial Database backup for Online VDI
Differential Partial Database Backup for Online VDI
Examples of VDI online backup sequences
Defining a VSS backup strategy and reviewing types
Examples of VSS backup sequences
Selecting data for an Online VDI backup
Setting backup options for an Online VDI backup
Finalizing and submitting an Online VDI backup job
Performing VSS backups in SQL Server
Selecting data for a VSS backup
Setting backup options for a VSS backup
Finalizing and submitting a VSS backup job
Example of creating a full VDI backup of an AlwaysOn Availability Group on Windows
Restoring data: an overview
Using the CLI with the plug-in
Troubleshooting
Reviewing the phases of the VDI restore sequence
Understanding the available types of Online VDI restores
Restoring system databases for Online VDI restore with Plug-in for SQL Server
Restoring databases involved in replication for Online VDI restore
Restoring data from Online VDI backups
Selecting Online VDI data for restore
Setting Online VDI restore options
Finalizing and submitting an Online VDI restore job
Restoring data from VSS backups
Selecting data for a VSS restore
Setting VSS restore options
Finalizing and submitting a VSS restore job
Using other restore procedures
Finalizing and submitting a VSS restore job
Complete the steps outlined in Finalizing and submitting an Online VDI restore job under Restoring data from Online VDI backups.
Using other restore procedures
This topic describes other restore operations that you can perform with the plug-in:
Restoring data to a Virtual Client
All options available for a restore with the plug-in are also available in high-availability — SQL Server Failover Cluster and AlwaysOn Availability Group — environments. Data selection is performed the same way. The difference is that restorable backups of a Virtual Client are displayed on the Create Restore Job — Choose Saveset page under the name of the Virtual Client, not the specific NetVault Backup Client or node that was active during each backup. When a restore job is initiated, NetVault Backup communicates with all member Clients to determine which machine controls the cluster, and then targets this machine for the restore.
|
NOTE: During a restore, run the process using the node for the Virtual Client. Do not use one of the nodes for an individual client in the cluster to run the process. If you open or expand one of the nodes and drill down through the hierarchy, you might see a dimmed SQL Server Instance identified as local. While the system might use this instance in maintaining log information, do not run any processes at this level. |
Use the following guidelines when you restore data that resides in an AlwaysOn Availability Group.
|
• |
If you complete multiple sequential restores of the primary replica and you want to omit the primary replica after the first restore, Quest recommends that you complete the Enter the NetVault Backup Client Name on the AlwaysOn Availability Groups Primary Node field. |
|
• |
Unless you want to use SQL Server Management Studio to add the primary replica to the group, select the Add Primary Database to the AlwaysOn Availability Group After Restore check box. |
|
• |
Ensure that the secondary replicas are always removed from the group before restoring the primary replica. You can do this manually using SQL Server Management Studio or by selecting the Remove Primary Database from the AlwaysOn Availability Group Before Restore check box. |
|
NOTE: While restoring the backups that are created on Plug‑in for SQL Server version 11.2 or earlier, the option Remove Database Secondary Copies from the AlwaysOn Availability Group Before Restore is visible on 'AlwaysOn Availability Groups' section. However, you should not select this option. This option is not displayed if the backup job is created on Plug‑in for SQL Server version 11.4.5 or later. |
|
• |
If you select With NO RECOVERY for the Restore Type of the primary replica, do not select the Add Primary Database to the AlwaysOn Availability Group After Restore check box. You must complete the recovery before you can add the database to the group. |
Restoring data to a Virtual Client in an AlwaysOn Availability Group
|
• |
These topics describe the general steps that you must take to complete a restore.
When restoring a VSS-based backup, be aware of the following:
|
• |
If you use the Copy Database Files to Target Directory option, do not remove the database from the group. |
|
a |
On the primary replica, select Suspend Data Movement for the database. |
For more information, see Selecting Online VDI data for restore under Restoring data from Online VDI backups or Selecting data for a VSS restore under Restoring data from VSS backups.
|
2 |
On the Create Selection Set page, click Edit Plugin Options, and configure the applicable parameters depending on whether you are performing a VSS or VDI restore. |
For information on the options that are common to all restore jobs, see Setting Online VDI restore options under Restoring data from Online VDI backups or Setting VSS restore options under Restoring data from VSS backups.
|
3 |
In the AlwaysOn Availability Groups section, select the applicable check box (es): |
Where you are in the process determines which check box (es) you should select. For example, when you run the restore of the Full Backup, select both check boxes. When you run the restore of the Transaction Logs, do not select the check boxes. Also, do not select Add Primary Database to the AlwaysOn Availability Group After Restore if you selected the With NO RECOVERY option.
|
• |
Restore to the following AlwaysOn Availability Group: Enter the name of the group. |
|
• |
Enter the NetVault Backup Client Name on the AlwaysOn Availability Groups Primary Node (optional): Enter the name of the client that is running on the primary node. If you enter a name for a different node, the restore fails. If you are unsure which client is running on the primary node, use SQL Server Management Studio to determine which node is the primary node in the group. |
|
IMPORTANT: Although the second field is labeled optional, it is required in this scenario. If you enter the correct information and the database is already part of the group, but you do not select the Remove Primary Database from the AlwaysOn Availability Group Before Restore check box, the restore fails. If the database is not part of the group, you specify an incorrect name, and the plug-in is unable to check that the client resides on the primary replica, the plug-in restores the database. However, you cannot add the database to the group. If a failover to a different node occurs after the restore job is run and you have entered the primary client and group names, update the information stored in Restore Options to reflect the name of the new client. Otherwise, subsequent runs of the same restore job fail. |
|
5 |
In the Instance Name, If Restoring to an AlwaysOn Named Instance (Windows only) field, enter the name of the instance. |
|
TIP: Only enter the name of the instance. If you enter the fully qualified name, <HostName>\<InstanceName>, the plug-in ignores the hostname. |
|
6 |
|
8 |
Perform a restore from each secondary replica that was backed up by the Full Database backup performed in Step 7. |
|
9 |
For more information, see Selecting Online VDI data for restore under Restoring data from Online VDI backups or Selecting data for a VSS restore under Restoring data from VSS backups.
|
3 |
On the Create Selection Set page, click Edit Plugin Options, and configure the applicable parameters depending on whether you are performing a VSS or VDI restore. |
For information on the options that are common to all restore jobs, see Setting Online VDI restore options under Restoring data from Online VDI backups or Setting VSS restore options under Restoring data from VSS backups.
|
4 |
In the Target Instance field in the Restore Options section, enter the name of the client running on the secondary replica. |
|
5 |
In the AlwaysOn Availability Groups section, select the applicable check boxes: |
Where you are in the process determines which check boxes you should select. For example, when you run the restore of the Full Backup, select all the check boxes. When you run the restore of the Transaction Logs, do not select the check boxes. Also, do not select Add Primary Database to the AlwaysOn Availability Group After Restore if you selected the With NO RECOVERY option.
|
6 |
In Restore to the following AlwaysOn Availability Group, enter the name of the group. |
|
7 |
In the Instance Name, If Restoring to an AlwaysOn Named Instance (Windows only) field, enter the name of the instance. |
|
TIP: Only enter the name of the instance. If you enter the fully qualified name, <HostName>\<InstanceName>, the plug-in ignores the hostname. |
|
8 |
|
11 |
|
13 |
Perform a restore of each secondary replica using the Full and Transaction Log backups completed in the previous step. |
|
14 |
The following procedure describes how to restore a VDI backup. This procedure is based on the example described in Example of creating a full VDI backup of an AlwaysOn Availability Group on Windows. The following procedure also requires that you restore Transaction Log backups, a process that was not included in the previous backup example.
|
1 |
In the Navigation pane, click Create Restore Job. |
|
2 |
In the saveset table on the Create Restore Job — Choose Saveset page, select the Full Backup of the primary replica that you are restoring, and click Next. |
|
3 |
On the Create Selection Set page, select the AlwaysOn Availability Group that you want to restore. |
|
4 |
Click Edit Plugin Options. |
|
5 |
|
6 |
In the AlwaysOn Availability Groups sections, select the Remove Primary Database from the AlwaysOn Availability Group Before Restore check box. |
Do not select the Add Primary Database to the AlwaysOn Availability Group After Restore because you selected the With NO RECOVERY option.
|
7 |
|
8 |
In Job Name, specify a name for the job if you do not want to use the default setting. |
|
9 |
In the Target Client list, select the same Virtual Client that was the target of the backup. |
|
10 |
|
11 |
In the Navigation pane, click Create Restore Job. |
|
12 |
In the saveset table on the Create Restore Job — Choose Saveset page, select the Incremental Transaction Log backup of the primary replica that you are restoring, and click Next. |
|
13 |
On the Create Selection Set page, select the same AlwaysOn Availability Group and databases that you selected during the restore of the Full Backup. |
|
14 |
Click Edit Plugin Options. |
|
15 |
|
16 |
In the AlwaysOn Availability Groups section, select the Add Primary Database to the AlwaysOn Availability Group After Restore check box. |
|
17 |
In the Restore to the following AlwaysOn Availability Group field, enter the name of the group. |
|
18 |
In the Enter the NetVault Backup Client Name on the AlwaysOn Availability Groups Primary Node field, enter the name of the client on the primary node. |
|
19 |
If you are restoring the backup to a named SQL Server Instance on a Windows Server, not the default instance, enter the name of the instance in the Instance Name, If Restoring to an AlwaysOn Named Instance field. |
|
TIP: Only enter the name of the instance. If you enter the fully qualified name, <HostName>\<InstanceName>, the plug-in ignores the hostname. |
|
20 |
|
21 |
In Job Name, specify a name for the job if you do not want to use the default setting. |
|
22 |
In the Target Client list, select the same Virtual Client that was the target of the backup. |
|
23 |
|
24 |
|
25 |
In Job Name, specify a name for the job. |
|
26 |
|
27 |
In the selection tree, open the first secondary replica that you are restoring, and then open the All Instances node. |
|
28 |
|
29 |
Enter the security information, enter the applicable login information, such as (local), for the Instance Name, and click OK. |
|
31 |
In the selection tree for the primary replica, select that databases that you are backing up. |
|
32 |
Run a VDI-based, Full Database backup. |
|
33 |
Using the same Selections set that you used for the Full Database backup, run an Incremental Transaction Log backup. |
|
34 |
In the Navigation pane, click Create Restore Job. |
|
35 |
In the saveset table on the Create Restore Job — Choose Saveset page, select the Full Backup of the primary replica that you completed Step 32, and click Next. |
|
36 |
On the Create Selection Set page, select the databases that you want to restore, and click Edit Plugin Options. |
|
37 |
|
38 |
In Job Name, specify a name for the job if you do not want to use the default setting. |
|
39 |
|
40 |
|
41 |
For more information, see Selecting Online VDI data for restore under Restoring data from Online VDI backups or Selecting data for a VSS restore under Restoring data from VSS backups.
|
2 |
On the Create Selection Set page, click Edit Plugin Options, and configure the applicable parameters depending on whether you are performing a VSS or VDI restore. |
For information on the options that are common to all restore jobs, see Setting Online VDI restore options under Restoring data from Online VDI backups or Setting VSS restore options under Restoring data from VSS backups.
|
3 |
In the AlwaysOn Availability Groups section, clear the check box Remove Primary Database from the AlwaysOn Availability Group Before Restore. |
|
4 |
Select or clear the Add Primary Database to the AlwaysOn Availability Group After Restore check box, whichever is applicable. |
|
• |
Restore to the following AlwaysOn Availability Group: Enter the name of the group. |
|
• |
Enter the NetVault Backup Client Name on the AlwaysOn Availability Groups Primary Node (optional): Enter the name of the client that is running on the primary node. If you enter a name for a different node, the restore fails. If you are unsure which client is running on the primary node, use SQL Server Management Studio to determine which node is the primary node in the group. |
|
6 |
If you are restoring the backup to a named SQL Server Instance, not the default instance, enter the name of the instance in the Instance Name, If Restoring to an AlwaysOn Named Instance (Windows only) field. |
|
TIP: Only enter the name of the instance. If you enter the fully qualified name, <HostName>\<InstanceName>, the plug-in ignores the hostname. |
|
7 |
|
9 |
Perform a restore from each secondary replica that was backed up by the Full Database backup performed in Step 7. |
|
10 |