Chatee ahora con Soporte
Chat con el soporte

NetVault Plug-in for SQL Server 11.2 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for SQL Server® Planning your SQL Server deployment Installing and removing the plug-in Configuring the plug-in Backing up data
Defining a backup strategy Reviewing the compression features Performing Online VDI backups Performing VSS backups in SQL Server® Example of creating a full VDI backup of an AlwaysOn Availability Group
Restoring data Troubleshooting

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.

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.

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

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

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

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.

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.

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.
3
In the AlwaysOn Availability Groups section, select the applicable check boxes:
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 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
Perform a restore from each secondary replica that was backed up by the Full Database backup performed in Step 7.

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.

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.
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:
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 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.
13
Perform a restore of each secondary replica using the Full and Transaction Log backups completed in the previous step.

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. The following procedure also requires that you restore Transaction Log backups, a process that was not included in the previous backup example.

1
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
In the Restore Type section, select With NO RECOVERY.
6
In the AlwaysOn Availability Groups sections, select the Remove Database Secondary Copies from the AlwaysOn Availability Group Before Restore and Remove Primary Database from the AlwaysOn Availability Group Before Restore check boxes.
Do not select the Add Primary Database to the AlwaysOn Availability Group After Restore because you selected the With NO RECOVERY option.
7
Click OK to save the settings, and then click Next.
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
Click Save & Submit, and use the Job Status page to monitor progress.
11
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
In the Restore Type section, select With RECOVERY.
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.
TIP: Only enter the name of the instance. If you enter the fully qualified name, <HostName>\<InstanceName>, the plug-in ignores the hostname.
20
Click OK to save the settings, and then click Next.
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
Click Save & Submit, and use the Job Status page to monitor progress.
24
In the Navigation pane, click Create Backup Job.
25
In Job Name, specify a name for the job.
26
Next to the Selections list, click Create New.
27
In the selection tree, open the first secondary replica that you are restoring, and then open the All Instances node.
28
Select the All Instances node, and select Configure from the Actions menu.
30
Repeat Step 27 through Step 29 for each secondary replica.
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
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
In the Restore Type section, select With NO RECOVERY, click OK, and then click Next.
38
In Job Name, specify a name for the job if you do not want to use the default setting.
39
In the Target Client list, select the Virtual Client name of the secondary replica.
40
Click Save & Submit, and use the Job Status page to monitor progress.
41
Repeat Step 34 through Step 40 to restore the Incremental Transaction Log backup from the primary replica to the secondary replica.
43
Repeat Step 34 through Step 42 for each secondary replica that is part of the group.

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.

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.
3
In the AlwaysOn Availability Groups section, clear the following check boxes:
4
Select or clear the Add Primary Database to the AlwaysOn Availability Group After Restore check box, whichever is applicable.
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.
TIP: Only enter the name of the instance. If you enter the fully qualified name, <HostName>\<InstanceName>, the plug-in ignores the hostname.
9
Perform a restore from each secondary replica that was backed up by the Full Database backup performed in Step 7.

Renaming or relocating a database

The plug-in lets you restore a database to a different name during restore. The renaming of a database can be useful if you do not want to overwrite the existing version and want to create a copy of the database. You can also relocate the database to a different directory while restoring it with the plug-in.

IMPORTANT: To make a copy of a database using the Full File and Filegroup Backup method, available only for VDI, it must be restored to a different SQL Server® Instance.

When renaming a database during a VSS-based restore, the database files must also be relocated to an alternate directory. If the database files are not relocated to an alternate directory, the restore fails. This failure is because VSS does not let you rename the database without moving the data and log files to a different directory. When relocating data and log files for VSS-based restores, you can relocate the data files to one directory and the log files to a separate directory if both directories are different than the original.
1
In the Navigation pane, click Create Restore Job, select Plug‑in for SQL Server from the Plugin Type list, select the applicable saveset, and click Next.
2
With the database selected on the Create Selection Set page, select Rename from the Actions list.
3
In the Rename/Relocate dialog box, enter the applicable information:
Rename: Enter the new name.
Relocate: Enter the new path.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación