NetVault Plug-in for SQL Server 12.2


	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.

Important considerations restoring data to a Virtual Client for an AlwaysOn Availability Group

Use the following guidelines when you restore data that resides in an AlwaysOn Availability Group.

•

You can restore data from the backup of an AlwaysOn Availability Group to the same group. You cannot restore an AlwaysOn Availability Group to an alternate SQL Server Instance, standalone deployment, or a different 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.

If you do not remove the secondary replicas before completing the restore, it might prevent the plug-in from removing the primary replica or the restore might complete with warnings. Also, failing to remove the secondary replicas might prevent you from adding the secondary replicas during the subsequent backup of the primary replica.


	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.

•

You cannot use the same job to restore databases from multiple AlwaysOn Availability Groups.

•

You cannot use the same job to restore a database that belongs to an AlwaysOn Availability Group and a different database that does not belong to a group.

•

If you use SQL Server's named instances for your AlwaysOn Availability Group nodes on a Windows Server, the restore process requires that any database that is backed up using the Virtual Client must belong to the same named instance on each node of the group.

•

You must create separate jobs to restore databases from an AlwaysOn Availability Group and databases that are not included in a group. Also, use the same job to restore databases from an AlwaysOn Availability Group if they reside in the same group.

Restoring data to a Virtual Client in an AlwaysOn Availability Group

The following topics list the high-level steps for restoring data in AlwaysOn Availability Group deployments and provide examples of different restores.

•

High-level restore steps for restoring data to a Virtual Client in an AlwaysOn Availability Groups

•

Example of restoring a database that was added to all replicas in an AlwaysOn Availability Group

•

Example of restoring a secondary replica and converting it to a primary replica

•

Example of restoring a VDI backup of an AlwaysOn Availability Group

•

Example of restoring a database that does not exist on the primary replica

High-level restore steps for restoring data to a Virtual Client in an AlwaysOn Availability Groups

These topics describe the general steps that you must take to complete a restore.

Performing a VSS restore of an AlwaysOn Availability Group

When restoring a VSS-based backup, be aware of the following:

•

VSS is a generic interface that requires objects included in the snapshot comply with certain requirements. For example, SQL Server databases that have a status of Restoring conflict with the creation of VSS backup snapshots.

•

SQL Server databases participating in an AlwaysOn Availability Group cannot be included in a VSS restore snapshot, and some operations are not available for databases that are joined in a group.

•

If you use the Copy Database Files to Target Directory option, do not remove the database from the group.

•

As noted previously, a disadvantage of VSS backups is that the SQL Server VSS Writer does not support the ability to restore a database to an alternate instance whether that instance is on the same server and host or an alternate server and host.

•

The following procedure applies if you are restoring the group to its original destination or if you are restoring the group using the Rename/Relocate option. However, if you are performing a restore with rename or relocate, or both, the original database cannot be joined in an AlwaysOn Availability Group.

Use SQL Server Management Studio to remove the database from the AlwaysOn Group.

On the primary replica, select Suspend Data Movement for the database.

On all secondary replicas, remove the database from the group.

On the primary replica, remove the database from the group.

Restore the primary from the applicable backups.

Add the database to the AlwaysOn Availability Group on the primary replica.

Add the database to the AlwaysOn Availability Group on each secondary replica.

Performing a VDI restore of an AlwaysOn Availability Group

Remove the secondary replicas.

Remove the primary replica.

Restore the primary from the applicable backups.

Using the process for a standalone deployment, perform Full and Differential Transaction Log backups of the primary replica.

Using the process for a standalone deployment, perform Full and Differential Transaction Log restores of each secondary replica.

These restores set the secondary replicas to match the primary replica.

Add the database to the AlwaysOn Availability Group on the primary replica.

Add the database to the AlwaysOn Availability Group on each secondary replica.

Example of restoring a database that was added to all replicas in an AlwaysOn Availability Group

The following procedure describes how to restore a database that was added to the primary replica and all secondary replicas in the AlwaysOn Availability Group.

Select the data to restore.

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.

As described previously, you cannot use the same job to restore databases from multiple groups. Nor can you use the same job to restore a database that belongs to a group and a different database that does not.

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.

In the AlwaysOn Availability Groups section, select the applicable check box (es):

•

Remove Primary Database from the AlwaysOn Availability Group Before Restore

•

Add Primary Database to the AlwaysOn Availability Group After Restore

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.

If you previously removed the database from the AlwaysOn Availability Group on the primary node, complete the following fields:

•

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.

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.

Complete the steps outlined in Finalizing and submitting an Online VDI restore job under Restoring data from Online VDI backups.

Perform a Full Database backup from the primary replica.

Perform a restore from each secondary replica that was backed up by the Full Database backup performed in Step 7.

Complete a separate restore operation for each secondary replica that makes up the primary replica.

Use SQL Server Management Studio to add the secondary replicas to the AlwaysOn Availability Group.

Example of restoring a secondary replica and converting it to a primary replica

The following procedure describes how to restore a secondary replica to a backup taken from the Virtual Client and then convert the secondary replica to function as the primary replica.

On the secondary replica, remove the database from the AlwaysOn Availability Group.

Select the data to restore.

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.

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.

In the Target Instance field in the Restore Options section, enter the name of the client running on the secondary replica.

In the AlwaysOn Availability Groups section, select the applicable check boxes:

•

Remove Primary Database from the AlwaysOn Availability Group Before Restore

•

Add Primary Database to the AlwaysOn Availability Group After Restore

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.

In Restore to the following AlwaysOn Availability Group, enter the name of the group.

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.

Complete the steps outlined in Finalizing and submitting an Online VDI restore job under Restoring data from Online VDI backups.

Perform a failover to the secondary replica.

Use SQL Server Management Studio to identify the secondary replica as the primary replica for all databases assigned to the AlwaysOn Availability Group.

Use SQL Server Management Studio to add the database back to the group on the new primary replica.


	IMPORTANT: To complete this step, you might need to remove the database from the remaining secondary replicas and postpone adding the database to the new primary replica until the process is finished.

Perform Full Database and Transaction Log backups of the new primary replica.

Perform a restore of each secondary replica using the Full and Transaction Log backups completed in the previous step.

For each secondary replica, remove the database on that node from the AlwaysOn Availability Group, and complete the Full and Transaction Log restores.

Use SQL Server Management Studio to add the secondary replicas to the AlwaysOn Availability Group.

Example of restoring a VDI backup of an AlwaysOn Availability Group

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.

In the Navigation pane, click Create Restore Job.

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.

On the Create Selection Set page, select the AlwaysOn Availability Group that you want to restore.

Include all databases included in the saveset.

Click Edit Plugin Options.

In the Restore Type section, select With NO RECOVERY.

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.

Click OK to save the settings, and then click Next.

In Job Name, specify a name for the job if you do not want to use the default setting.

In the Target Client list, select the same Virtual Client that was the target of the backup.

Click Save & Submit, and use the Job Status page to monitor progress.

You might see a “Waiting for secondaries” status for up to 20 minutes. Do not proceed until the Run Status is “Restore Completed.”

In the Navigation pane, click Create Restore Job.

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.

On the Create Selection Set page, select the same AlwaysOn Availability Group and databases that you selected during the restore of the Full Backup.

Click Edit Plugin Options.

In the Restore Type section, select With RECOVERY.

In the AlwaysOn Availability Groups section, select the Add Primary Database to the AlwaysOn Availability Group After Restore check box.

Do not select the other check boxes.

In the Restore to the following AlwaysOn Availability Group field, enter the name of the group.

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.

Check that you entered the NetVault Backup Virtual Client name; do not enter a different name, such as the host name or SQL Server Instance.

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.

Click OK to save the settings, and then click Next.

In Job Name, specify a name for the job if you do not want to use the default setting.

In the Target Client list, select the same Virtual Client that was the target of the backup.

Click Save & Submit, and use the Job Status page to monitor progress.

Do not proceed until the Run Status is “Restore Completed.”

After the restore of the primary replica is finished, create a backup of the primary replica. After the backup is finished, use the new backup to restore each secondary replica.

In the Navigation pane, click Create Backup Job.

In Job Name, specify a name for the job.

Next to the Selections list, click Create New.

In the selection tree, open the first secondary replica that you are restoring, and then open the All Instances node.

The databases that were part of the AlwaysOn Availability Group showing “(Restoring)” after their names.

Select the All Instances node, and select Configure from the context menu.

Enter the security information, enter the applicable login information, such as (local), for the Instance Name, and click OK.

Repeat Step 27 through Step 29 for each secondary replica.

In the selection tree for the primary replica, select that databases that you are backing up.

These databases are the same ones identified as “(Restoring)” on the secondary replica.

Run a VDI-based, Full Database backup.

Using the same Selections set that you used for the Full Database backup, run an Incremental Transaction Log backup.

In the Navigation pane, click Create Restore Job.

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.

On the Create Selection Set page, select the databases that you want to restore, and click Edit Plugin Options.

In the Restore Type section, select With NO RECOVERY, click OK, and then click Next.

In Job Name, specify a name for the job if you do not want to use the default setting.

In the Target Client list, select the Virtual Client name of the secondary replica.

Click Save & Submit, and use the Job Status page to monitor progress.

Repeat Step 34 through Step 40 to restore the Incremental Transaction Log backup from the primary replica to the secondary replica.

From the secondary replica, use SQL Server Management Studio to add each applicable database to the AlwaysOn Availability Group.

Perform this step locally on the applicable secondary node.

Repeat Step 34 through Step 42 for each secondary replica that is part of the group.

Example of restoring a database that does not exist on the primary replica

The following procedure describes how to restore a database to an AlwaysOn Availability Group if the database was removed from the primary replica before the restore.

Select the data to restore.

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.

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.