Within a single recovery task, you can recover multiple databases. The databases are automatically mapped to their original instances. You can select a target instance for each database, if necessary.
System databases are recovered in the same way as user databases. When recovering the master database, the software automatically restarts the destination instance in the single-user mode. After the recovery completes, the software restarts the instance and recovers other databases (if any). Other things to consider when recovering a system database:
A system database can only be recovered to an instance of the same version as the original instance.
A system database is always recovered in the "ready to use" state.
Because the master database records information about all databases of the instance, you may need to perform additional actions after the database is recovered. For details, see "Actions after a master database recovery".
To recover databases to instances
On the Recover data page:
Under What to recover, click Select data and select the databases.
If the console is connected to the management server, select the registered machine where you want to recover the databases. Otherwise, skip this step.
Select Recover the databases to instances.
Acronis Backup tries to specify the target instances for the selected databases by taking the original paths from the backup. If the target instance is not selected for some database or if you want to recover the database to another instance, specify the target instance manually.
If your current account does not have enough privileges to access the target SQL Server instance, you will be asked to provide the credentials.
If the target instance contains a database that has the same name as the one being recovered, the software displays a warning: The target database already exists. You have the following options:
Overwrite existing database
This is the default setting that fits most situations. The database in the target instance will be overwritten with the database from the backup.
Rename the recovered database
This setting lets you retain the existing database. A recovered database will have the following name: <original database name>-Recovered. If a database with this name already exists, the recovered database will be named as follows: <original database name>-Recovered (<sequence number>).
For each database being recovered, you can select its state after recovery. To do so, click the icon to the left of the database name, and then select one of the following values:
Ready to use (RESTORE WITH RECOVERY) (by 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.
You can change the paths to where the database files will be saved. To access these settings, click the icon to the left of the database name.
icon to the left of the database name, and then select one of the following values: