NetVault Plug-in for SQL Server 10.0.6

Complete database restore: With a Simple Recovery Model database, the goal of a complete database restore is to restore the entire database. This type of restore typically involves restoring a Full Database backup or a Full Database backup followed by a Differential Database backup. The entire database is offline during a complete database restore.

•

File restore: In a file restore for a Simple Recovery Model database, the goal is to restore one or more damaged read-only files without restoring the entire database. This type of restore involves a Full File and Filegroup backup.

•

Partial database restore: A partial restore for a Simple Recovery Model database includes restoring the primary filegroup and all read-write filegroups that were included in a Partial Database or Differential Partial Database backup. Restores of the read-only filegroups with a Full File and Filegroup backup are required only if the read-only filegroups are damaged.

Restoring databases under Full and Bulk-Logged Recovery Models

The following restore scenarios are supported under the Full and Bulk-Logged Recovery Models:

•

Complete database restore: Under the Full and Bulk-Logged Recovery Models, the goal is to restore the entire database to the point-of-failure. A complete restore sequence typically includes:

Perform Tail-Log backup.

Restore Full Database or Full File and Filegroup backup while selecting With NO RECOVERY restore option.

Restore Differential Database or Differential File and Filegroup backup while selecting With NO RECOVERY restore option.

Restore all subsequent Incremental Transaction Log backups in order while selecting the With NO RECOVERY restore option.

Restore and recover the Tail-Log backup by selecting the With RECOVERY restore option.

•

File restore: In a file restore for a Full or Bulk-Logged Recovery Model database, the goal is to restore the entire database while leaving the option available to restore damaged files without restoring the entire database. This type of restore involves the following restore sequence:

Perform Tail-Log backup.

Restore Full File and Filegroup backup using the With NO RECOVERY restore option.

Restore Differential File and Filegroup backup using the With NO RECOVERY restore option.

Restore all subsequent Incremental Transaction Log backups in order while selecting the With NO RECOVERY restore option.

Restore and recover the Tail-Log backup while selecting the With RECOVERY restore option.

•

Point-in-time (PIT) recovery: You can perform a PIT recovery on the transaction logs that are restored during an Incremental Transaction Log restore. Plug‑in for SQL Server supports both time-based (using hours:minutes:seconds) and marked-transaction-based PIT recovery. PIT recovery options are available when restoring Incremental Transaction Log and Tail-Log backups.

•

Time-Based Point-in-Time Recovery: Time-based PIT recovery is useful when the time that the data corruption occurred is known. For example, if a developer dropped a table at 6:00:00 A.M., PIT recovery can be performed with a stop time of 5:55:00 A.M. Time-based PIT recovery can only be used for unrelated databases; therefore, when multiple SQL Server® databases are required to be logically consistent, marked-transaction PIT recovery should be used.

•

Marked-Transaction-Based Point-in-Time Recovery: SQL Server 2005 and later support the ability to insert named marks into a transaction log to allow recovery to a specific mark. This functionality is beneficial if you have two or more databases that must be logically consistent. You can implement special procedures to ensure the recoverability of these databases after a restore. Because you can only recover related databases to a marked transaction, your application must be configured to insert named marks into the transaction log before performing backups. For more information, see Ensuring Recoverability of Related Databases and the Recovering to a Marked Transaction in the SQL Server Books Online.

Restoring system databases

You can only restore system databases from backups that are created on the version of SQL Server® that the instance is running. For example, to restore a system database on an instance that is running on SQL Server 2005 SP1, use a backup that was created after the instance was upgraded to SQL Server 2005 SP1.

Restoring the master database

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

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. Dell also recommends that you shut down applications, because the restore procedure disconnects users when necessary.

Restoring databases involved in replication

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 sections:

•

Selecting data for a restore

•

Setting restore options

•

Finalizing and submitting the job

Selecting data for a restore

To select data to 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, name of the NetVault Backup Server, name of the client from which the data was backed up, plug-in used to create the saveset, saveset creation date and time, saveset retirement setting, whether it is an Incremental Backup, whether it is an Archive, and saveset size.

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.