Chatee ahora con Soporte
Chat con el soporte

NetVault Plug-in for SQL Server 12.2 - User Guide

Introducing 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 Understanding snapshot-based backups 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 on Windows
Restoring data Using the CLI with the plug-in Troubleshooting

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.
Select the database to restore from the backup saveset by following the instructions outlined in Restoring data from Online VDI backups.
2
With the database selected on the Create Selection Set page, select Rename from the context menu.
3
In the Rename/Relocate dialog box, enter the applicable information:
•
Rename: Enter the new name.
 
* 
IMPORTANT: 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 from the original.
•
Relocate: Enter the new path.
The plug-in lets you relocate the log files to a directory other than the data files directory. To restore to separate directories, type in the paths to the directories where the data files and log files are to be restored. Enter the data file directory first, and then enter the path to the log file directory. Separate the two directory paths using a comma — no space must exist before or after the comma. The directory specified in this field must exist at job run-time.
4
To apply your changes, click OK.
 
* 
NOTE: In the WebUI, the database name is accompanied by the rename and relocate information in parentheses. The database files are renamed using a concatenation of the new name and the original name, that is, <NewName>_<OriginalName>.
5
Continue with the restore procedure as explained in Restoring data from Online VDI backups.

Restoring a database to an alternate instance

With the plug-in’s VDI-based backup method, you can restore a database to an alternate instance of SQL Server running on the database server. The procedure for performing this type of a restore is outlined in the following topic. This process does not support the use of AlwaysOn Availability Groups.

 
* 
IMPORTANT: If you intend to restore a database to an alternate instance that resides on the same server and the original database still exists, use the Rename/Relocate option described previously in Renaming or relocating a database. Use this option to rename or move the datafiles to ensure that they do not overwrite or conflict with the same files in the original database.
Figure 4. Restoring to alternate instance

1
Before initiating this type of restore, check that the following prerequisites are met:
•
Same version of SQL Server: Both the source instance from which the data was backed up and the target instance to which the data is to be restored must be running the same version of SQL Server.
•
Instance configured for access: The instance to which the database is to be restored must be accessible to the plug-in. To set up the instance for access, see Configuring authentication details.
2
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.
Select the database to restore from the backup saveset by following the instructions outlined in Restoring data from Online VDI backups.
3
On the Create Selection Set page, click Edit Plugin Options, and configure the restore options by following the instructions outlined in Restoring data from Online VDI backups.
4
In addition, set the Target Instance parameter.
To do so, specify the name of the instance to which the selected database is to be restored. You can either specify the fully qualified name, that is, <HostName>\<InstanceName> — for example, WIN2K3\SQLINSTANCE2 or the instance name, for example, SQLINSTANCE2, in this field.
5
Complete the procedure by following the instructions outlined in Restoring data from Online VDI backups.
 
* 
IMPORTANT: You can also rename or relocate a database while performing this type of restore for VDI-based backups. For more information, see Renaming or relocating a database.

Restoring data to an alternate SQL Server

Similar to the plug-in’s ability to restore databases to a different SQL Server Instance on the same database server, you can target a different SQL Server during the restore process. This process does not support the use of AlwaysOn Availability Groups.

Figure 5. Restoring to alternate SQL Server

This functionality is useful during disaster recovery operations. You can restore a database to a different SQL Server by using the steps provided in the following topics. You can also use this process to restore a NetVault Backup Virtual Client to a standalone NetVault Backup Client.

 
* 
IMPORTANT: Microsoft’s VSS backup method does not support restoring a VSS-based backup to an alternate instance; therefore, restoring VSS-based backups to an alternate instance with Plug‑in for SQL Server is not supported.

In a disaster recovery scenario, use this procedure to restore the master and the msdb database backups. After restoring the master database, restart the server. Restore and recover each individual database.
1
Before initiating this type of restore, check that the following prerequisites are met on the new restore target:
•
Same version of SQL Server installed: The SQL Server version must be the same as the version running on the existing database server.
•
NetVault Backup software and the Plug‑in for SQL Server installed: The same version of NetVault Backup software and the plug-in must be installed and configured on the new restore target.
•
Client added to the NetVault Backup Server: The target machine must be added to the NetVault Backup Server by using the Manage Clients page of the NetVault Backup WebUI.
•
Instance of SQL Server must exist on the new restore target: An instance of SQL Server must exist on the new restore target. This instance serves as the target of the relocation restore. Not only must this instance be properly set up and configured in SQL Server, it must also be accessible to the plug-in on the new restore target. To set up the instance for access, see Configuring authentication details.
2
Restore the master and the msdb database backups.
 
* 
IMPORTANT: When you perform a restore to an alternate server, you cannot modify the name or destination of the restored master database. The master database is restored to the location of the current master database in the target for the restore.
3
After restoring the master database, restart the server.
4
Restore and recover each individual database.
a
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.
Select the database to be restored from the backup saveset by following the instructions outlined in Restoring data from Online VDI backups.
b
On the Create Selection Set page, click Edit Plugin Options, and configure the restore options by following the instructions outlined in Restoring data from Online VDI backups.
c
In addition, set the Target Instance parameter.
To do so, specify the name of the instance to which the selected database is to be restored on the new database server. Enter only the instance name in this field; the restore fails if the server name is included.
 
* 
NOTE: If you are restoring the default SQL Server Instance to the alternate server, you can enter the name of the destination server, for example, MSSQLSERVER, for the Target Instance.
d
Click OK to save the settings, and then click Next.
e
In Job Name, specify a name for the job if you do not want to use the default setting.
Assign a descriptive name that lets you easily identify the job when monitoring its progress. The job name can contain alphanumeric and non-alphanumeric characters, but it cannot contain non-Latin characters. On Linux, the name can have a maximum of 200 characters. On Windows, there is no length restriction; however, a maximum of 40 characters is recommended.
f
In the Target Client list, select the new restore target.
g
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options.
h
Click Save or Save & Submit, whichever is applicable.
You can monitor progress on the Job Status page and view the logs on the View Logs page. For more information, see the Quest NetVault Backup Administrator’s Guide.

Using the CLI with the plug-in

•
About the NetVault Backup CLI
•
Performing tasks using the CLI

 

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación