NetVault Plug-in for SQL Server 12.0

On the Create Selection Set page, click Edit Plugin Options, and configure the following parameters — these options are available for all VSS backup types:

•

Backup Method: This field displays the backup method used for the selected saveset.

•

Backup Type: This field displays the type of backup used for the selected saveset.

•

Restore Method: Select one of the following options:

•

VSS Restore: Select this option if to complete a restore to the same machine from which the backup was created.

•

Copy Database Files to Target Directory: Select this option to restore database files to a specified location. You can specify a directory on the local machine where the backups were taken. You can also specify a directory on any machine that has NetVault Backup and the plug-in installed and is reachable from the NetVault Backup Server, even if the machine does not have SQL Server installed. To restore a VSS backup to a different machine, use the Target Client list to select the NetVault Backup Client of the corresponding target machine.


	IMPORTANT: Because the maximum path length in Windows is 260 characters, check that the combination of the filenames and target path does not exceed 260 characters; otherwise, the restore fails. If the backup contains FILESTREAM data, the restore process does not retain folder structure; the plug-in restores all files to the same folder. Because the folder structure of the database is not recreated, a file-activation error appears if you try to access the database. To avoid this issue, restore the backup to the original location.

•

Restore Type: This section lets you specify the action that must be performed after the restore operation. You can select from the following options:

•

With RECOVERY: Select this option if you do not intend to apply additional Transaction Log or Differential Database backups after the restore of the selected data has completed.

•

With NO RECOVERY: Select this option if you intend to apply a different Transaction Log or Differential Database backup after this restore has completed.

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

•

Renaming or relocating a database

•

Restoring a database to an alternate instance

•

Restoring data to an alternate SQL Server

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.

Also, you can restore a NetVault Backup Virtual Client to a non-clustered (standalone) NetVault Backup Client.


	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, 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.