Recovering SQL Databases

Recovering SQL databases

The backup service enables you to recover SQL databases to a SQL Server instance, if Agent for SQL is installed on the machine running the instance. You will need to provide credentials for an account that is a member of the Backup Operators or Administrators group on the machine and a member of the sysadmin role on the target instance.

Alternatively, you can recover the databases as files. This can be useful if you need to recover databases to a machine where Agent for SQL is not installed, or you need to extract data for data mining, audit, or further processing by third-party tools.

System databases are basically recovered in the same way as user databases. The peculiarities of system database recovery are described in "Recovering system databases".


To recover SQL databases


1. Click Microsoft SQL.
Machines with Agent for SQL installed are shown.

2. Select the machine which originally contained the data that you want to recover.

3. Click Recovery.

4. Select a recovery point. Note that recovery points are filtered by location.

5. Click Recover database.

6. Select the data that you want to recover. Double-click an instance to view the databases it contains.

7. If you want to recover the databases as files, click Recover as files, select a local or a network folder to save the files to, and then click Recover. Otherwise, skip this step.

8. Click Recover.

9. By default, the databases are recovered to the original ones. If the original database does not exist, it will be recreated. You can select another machine or another SQL Server instance to recover the databases to.To recover a database as a different one to the same instance:

a. Click the database name.

b. In Recover to, select New database.

c. Specify the new database name.

d. Specify the new database path and log path. The folder you specify must not contain the original database and log files.

10.[Optional] To change the database state after recovery, click the database name, and then choose one of the following states:

Ready to use (RESTORE WITH RECOVERY) (default)

 

  • After the recovery completes, the database will be ready for use. Users will have full access to it. The software will roll back all uncommitted transactions of the recovered database that are stored in the transaction logs. You will not be able to recover additional transaction logs from the native Microsoft SQL backups.

Non-operational (RESTORE WITH NORECOVERY)

 

  • After the recovery completes, the database will be non-operational. Users will have no access to it. The software will keep all uncommitted transactions of the recovered database. You will be able to recover additional transaction logs from the native Microsoft SQL backups and thus reach the necessary recovery point.

Read-only (RESTORE WITH STANDBY)

  • After the recovery completes, users will have read-only access to the database. The software will undo any uncommitted transactions. However, it will save the undo actions in a temporary standby file so that the recovery effects can be reverted.
  • This value is primarily used to detect the point in time when a SQL Server error occurred.

11. Click Recover.

12. If the original databases were selected as the destination, confirm overwriting the databases with their backed-up versions.

The recovery progress is shown in the Status column for the machine.

 

  • 7 Users Found This Useful
Was this answer helpful?

Related Articles

Recovering System Databases

Recovering system databases   All system databases of an instance are recovered at once. When...

Selecting system state

Selecting system state   System state backup is available for machines running Windows Vista...

Mounting Exchange Server Databases

Mounting Exchange Server databases After recovering the database files, you can bring the...

Selecting a Destination

Selecting a destination Click Where to back up, and then select one of the following: Cloud...

Backup

Backup A backup plan is a set of rules that specify how the given data will be protected on a...