NetVault Plug-in for SQL Server 11.2

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

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.

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.

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.

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.

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.

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.

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.

After restoring the master database, restart the server.

Restore and recover each individual database.

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.

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.

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.

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.

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 Windows®, there is no length restriction; however, a maximum of 40 characters is recommended.

In the Target Client list, select the new restore target.

Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options.

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.

Troubleshooting

This topic describes some common errors and their solutions. If an error occurs that is not described in this table, obtain the SQL Server® error number from the NetVault Backup Logs, and then see the relevant SQL Server documentation for the resolution.

Table 1. Troubleshooting

Symptom

Reason/symptom

Solution

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows®

Check the Windows Event Viewer to see if it displays the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.quest.com/netvault-backup/kb/122475.

Transaction Log backup failed

Transaction Log backups are not allowed for Simple Recovery Model databases.

For taking Transaction Log backups, the recovery model for the database must be set to Full Recovery Model.

Or clear the Simple Recovery Model databases.

Backup failed

The File and Filegroup backup fails and the following error message appears in the logs:

“The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.”

Either modify the Selection Set to include only secondary filegroups for the Simple Recovery Model databases or select the Partial Database or Differential Partial Database backup type.

Backup failed

Verify that the password for the plug-in has been entered correctly.

Backup Completed with warnings

After this status is revealed for backup, check the NetVault Backup Log entries for the job to see if they display one or both of the following messages:

•

“Failed to add backup record”

•

“Failed to write index of backup to the database”

These messages indicate that the selected data was backed up, but the job’s index information was not properly added by NetVault Backup to its database. Without this index information, the data cannot be properly restored.

Method 1:

Open the Manage Devices page, select the backup media, and click Scan. NetVault Backup stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. Performing this scan adds the index information to the NetVault Database. To verify that the information was added, open the Manage Job Definitions page, and locate the specific job. If you can run the job now, the scan process has corrected the problem.

Method 2:

If the scan has failed, run the backup job again.

VSS Restore fails from a NetVault Backup Server installed on Linux® or UNIX®.

By default, the plug-in assumes that the media format for backup tapes is MTF, which is typically used for Windows. However, Linux and UNIX use CPIO.

Configure the plug-in to set the Media Format to use CPIO during VSS Restores. For more information, see Configuring plug-in options.

AlwaysOn Availability Group not displayed under the Virtual Client

If a group is not listed under a Virtual Client, it might indicate that the services for the SQL Server Instances are not running. It might also indicate that valid login credentials were not set up for the plug-in at the All Instances level.

•

Use SQL Server Configuration Manager to verify that services are running.

•

Verify that you set up valid credentials for the All Instances node located under the applicable Virtual Client in the selection tree. For more information, see Configuring the plug-in.

Nodes take a long time to open

To populate the next level of the node, the plug-in queries SQL Server for instance and cluster information. If the plug-in queries or logs in to an instance whose Windows service is not running, a lengthy timeout imposed by SQL Server might occur. NetVault Backup uses a five-minute timeout. If the NetVault Backup timeout is exceeded, the plug-in displays an error message and the node is not opened. Address the issues that are causing a delay in the login and query processes.

•

Use SQL Server Configuration Manager to verify that services are running.

•

Enter default credentials for plug-in logins to SQL Server. For more information, see Entering logon credentials for all instances on a client.

•

If different credentials are required for some of the instances, enter the login credentials for those instances using the applicable instance or AlwaysOn Availability Group node in selection tree. For more information, see Entering default logon credentials for a specific SQL Server Instance.

•

If you must open the All Instances node to configure login credentials for specific instances or AlwaysOn Availability Groups, but the NetVault Backup timeout setting is preventing the All Instances node from opening, use the Physical Client Long Timeout option to change the timeout value for the node. For more information, see the topic on configuring the timeout period in the Quest NetVault Backup Administrator’s Guide.

VSS backup and restore jobs might fail due to concurrent backup jobs running on the OS from NVBU.

If two backup/restore jobs utilizing snapshots are scheduled to run at the same time, one of the jobs might fail with a VSS_E_SNAPSHOT_SET_IN_PROGRESS error in the log. This message indicates that VSS will not support taking two different snapshot sets at the same time.