Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Creating a Virtual Client

As noted earlier, the Virtual Client creation process is not plug-in-specific, and you can find complete details in the Quest NetVault Backup Administrator’s Guide. However, consider the following points during the Virtual Client creation process:

•
Assign a name to the Virtual Client: Quest strongly recommends that you use the Virtual Server network name (that is, the Fully Qualified Domain Name [FQDN]) assigned to the SQL Server® as the NetVault Backup Virtual Client name. When you browse a Virtual Client, NetVault Backup locates the node currently in control of the clustered application, and reveals the SQL Server Instance, for example, on the NetVault Backup Selections page. With a Virtual Client name set up as the SQL Server Virtual Server network name, you can recognize the SQL Server Instance for which the Virtual Client was created.
•
Only include relevant cluster nodes in the Virtual Client: Include only the hosts that are relevant to the SQL Server Virtual Server that is to be backed up and restored.

After the creation of the Virtual Client, the plug-in is transferred to all designated cluster nodes and installed locally. You use the installed plug-in by using the Virtual Client to back up and restore shared data; you can only perform backups and restores of data shared within the cluster.

Using multiple SQL Server® Virtual Servers in the same cluster

SQL Server supports the ability to create multiple Virtual Servers in a cluster. However, each Virtual Server can have only one instance of SQL Server running. In addition to the provisions outlined earlier, account for the following provisions when using Plug‑in for SQL Server in this configuration.

Create a NetVault Backup Virtual Client for each SQL Server® Virtual Server. Each Virtual Server has its own network name and IP address, and it is displayed as a separate Virtual Client in NetVault Backup.

•
Create an individual NetVault Backup Virtual Client for each SQL Server Virtual Server: For each SQL Server Virtual Server in the cluster, create a separate Virtual Client. During the creation process, ensure that the following are included:
•
IP Address of the SQL Server Virtual Server: In the Virtual Client Address field of the Virtual Client page, enter the IP Address assigned to the appropriate SQL Server Virtual Server. For example, if you are creating the first of the two SQL Server Virtual Servers in a failover cluster, enter the IP address assigned to the first Virtual Server.
•
Give a name to the Virtual Client that corresponds to the network name of the SQL Server Virtual Server: Enter the network name associated with the SQL Server Virtual Server in the Virtual Client Name field.
Figure 3. Creation of Virtual Client for first SQL Server Virtual Server in clustered environment that contains Virtual Servers
•
Copy the “nvsqlserver.cfg” file before creating the next NetVault Backup Virtual Client: Because creating a new Virtual Client overwrites the configuration file, which includes the Logon Detail information, Quest recommends that you perform the following steps:
1
Store a copy of the first “nvsqlserver.cfg” file in a safe location.
You can find this file in: \\<NetVaultBackupInstallDirectory>\config
2
Create the next Virtual Client, store a copy of its “nvsqlserver.cfg” file in a safe location, and repeat this step for every new Virtual Client that you need to create.
Ensure that the correct network name for the SQL Server Virtual Server and IP address is provided for each.
3
When you have finished creating Virtual Clients, copy the information from the [Security-<instanceName>] and [ServerList:List] sections in each “nvsqlserver.cfg” file to the same sections in the “nvsqlserver.cfg” file on the primary node.
4
If you have browsed the Virtual Client, close and reopen the NetVault Backup Selections page.

Licensing the plug-in

The plug-in supports backup and restore of shared data only. For a SQL Server® Failover Cluster or AlwaysOn environment, only a single license is needed — a clustered application license for the Virtual Client.

For information on the licensing process, including how to obtain the proper license keys, see the Quest NetVault Backup Installation Guide.

Removing the plug-in from a standalone deployment

For details on removing the Plug‑in for SQL Server in high-availability deployment, see the applicable topic on working with client clusters in the Quest NetVault Backup Administrator’s Guide.

 
* 
CAUTION: Removing the plug-in does not remove the configuration settings that you created. If you reinstall the plug-in or install a newer version, the plug-in typically uses the same configuration settings from the previous installation unless otherwise indicated in the release notes.
1
In the Navigation pane, click Manage Clients.
2
On the Manage Clients page, select the applicable client, and click Manage.
3
In the Installed Software table on the View Client page, select Plug‑in for SQL Server, and click the Remove Plugin button ().
4
In the Confirm dialog box, click Remove.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation