NetVault Plug-in for SQL Server 12.0

The master database must be accessible and at least partly usable for starting a SQL Server Instance. If the master database becomes unusable, you can return the database to a usable state by either restoring the master from a current database backup or rebuilding the master.

You can restore the master database from a Full Database backup only if you are able to start the server instance. If severe damage to the master database prevents you from starting the SQL Server, rebuilding the master is the only option left. For more information, see Rebuilding the master Database in the SQL Server Books Online.

The restoration of the master database includes:

•

Start the server instance in single-user mode.

•

Restore a Full Database backup of the master database.

The SQL Server Instance is stopped automatically on completion of the data restoration process.

•

Because the changes made to master since the last backup were lost, re‑create them by performing those steps again.

•

After the master has been restored and changes reapplied, back up the master immediately.

For more information, see Restoring data to an alternate SQL Server.

Restoring the model or msdb databases for Online VDI restore

Restoring the model or msdb database from a backup is required under the following circumstances:

•

The master database has been rebuilt. In this case, restore model from a backup because rebuilding master re-creates model.

•

The model or msdb database has been damaged, for example, due to media failure.

Restoring model or msdb is the same as performing a Complete Database restore of a user database.

Before restoring msdb, the SQL Server Agent Service in the Control Panel must be stopped. Quest also recommends that you shut down applications, because the restore procedure disconnects users when necessary.

Restoring databases involved in replication for Online VDI restore

You can restore all databases in a replication topology if recent backups are available and the proper steps are followed. The restore steps for the publication database depend on the type of replication and options used, but the steps for all other databases are independent of the type and options.

Replication supports restoring replicated databases to the same SQL Server Instance and database from which the backup was created. If you restore a replicated database from a backup to a different instance, replication settings cannot be preserved. In this case, re-create all publications and subscriptions after backups are restored.

For more information, see Strategies for Backing Up and Restoring Snapshot and Transactional Replication and Strategies for Backing Up and Restoring Merge Replication sections in the SQL Server Books Online.

Restoring data from Online VDI backups

A standard restore with Plug‑in for SQL Server in SQL Server includes the steps outlined in the following topics:

•

Selecting Online VDI data for restore

•

Setting Online VDI restore options

•

Finalizing and submitting an Online VDI restore job

Selecting Online VDI data for restore

In the Navigation pane, click Create Restore Job.

On the Create Restore Job — Choose Saveset page, select Plug‑in for SQL Server from the Plugin Type list.

To filter the items displayed in the saveset table further, use the Client, Date, and Job ID lists.

The table displays the saveset name (job title and saveset ID), creation date and time, and size. By default, the list is sorted alphabetically by saveset name.

The following table outlines the backup-type identifiers:


Backup type	Backup type identifier
Full Database	VDI FULL
Differential Database	VDI DIFFERENTIAL
Copy - Only	VDI Copy - ONLY
Incremental Transaction Log	VDI INCREMENTAL
Transaction Log	VDI INCREMENTAL
Tail-Log	VDI TAIL-LOG
Full File and Filegroup	VDI FILEGROUP
Differential File and Filegroup	VDI FILEGROUP DIFFERENTIAL
Partial Database	VDI PARTIAL
Differential Partial Database	VDI PARTIAL DIFFERENTIAL

In the saveset table, select the applicable item.

When you select a saveset, the following details are displayed in the Saveset Information area: Job ID, job title, server name, client name, plug-in name, saveset date and time, retirement setting, Incremental Backup or not, Archive or not, saveset size, and snapshot-based backup or not.

Click Next.

On the Create Selection Set page, select the data that you want to restore.

The database name is displayed when you open this node. For the Full File and Filegroup, Differential File and Filegroup, Partial Database, and Differential Partial Database backup types, you can open the database node and select the individual files or filegroups. For other backup types, further drill-down shows items but you cannot select them.


	IMPORTANT: When restoring a read-only filegroup, the filegroup must be explicitly selected in the selection tree. Though a green check mark appears for the read-only filegroup when you select the parent-level database, the filegroup is not restored. When including a read-only filegroup in a restore, select the individual items instead of selecting the parent-level database.

Select the applicable instance or the database for inclusion in the restore procedure.


	IMPORTANT: If you are restoring an AlwaysOn Availability Group, select only databases that either belong to one specific group or to one specific SQL Server Instance; you cannot select a mixture.