AnyBackup-Microsoft SQL Server recovery fails with error:As the existing database is not to be covered and database stu exists

2020-06-15 1101 0


existing databasecannot be restored


Applied Versions

· AnyBackup 6.0.x

· AnyBackup 5.0.x

· EBackup 5.0.x



AnyBackup SQL Server recovery job execution failed. And under Execution Output window, you can see the errors:

As the existing database is not to be covered and database stu exists, this database cannot be restored.(Error provider: sqlBackup, error value: e0346017, error location: ncMSSQLRestoreExec.cpp:1186).




AnyBackup fails to recover Microsoft SQL Server database.



AnyBackup executes the recovery job without enabling 'Replace existing databases' option, if the recovery destination has the same database name as the original database, this recovery operation is unable to execute. This is by design for AnyBackup to ensure data security.



To resolve this issue, enable the 'Replace existing databases' option or set the database name after recovery, when creating a recovery job.

Resolution 1 Set the database name after recovery as the original database name, enable the 'Replace existing databases' option.

Warning: Enabling the option Replace existing databases will cause the coverage of destination database.

1.    Enable the Original database name option when selecting the recovery path.


2.    Enable the Replace existing databases option in 3.Select Recovery Policy, when selecting recovery policy.


Resolution 2 Set the database name after recovery as a new target database name, when creating a Microsoft SQL Server recovery job.

Enable the 'Target database name' option, input a new database name when selecting the recovery path.

Note: The target database name cannot exist on the recovery destination. Only one database can be recovered in one recovery job, when enabling the 'Target database name' option. In the following example, the original database name is 'stu', the target database name is 'stu_new'.



More Information

AnyBackup software is designed to check security policies before database recovery, this can avoid the target database be covered by incorrect operation. & Korea)