Review the Restore Prerequisites and Considerations

Verify that the following prerequisites exist before performing a restore:

You must have Microsoft SQL Server instance before performing the SQL Application restore.
Review the Compatibility Matrix that provides the supported operating systems, databases, and browsers.

Review the following restore considerations:

If the jobs are not for the same VM, Arcserve UDP allows multiple restore jobs to run at the same time. If you attempt to launch a restore job while another restore job is running for the same VM, an alert message informs you that another job is running and requests you to try again later.
Arcserve UDP Agent Windows only allows one restore job to run at the same time. If you attempt to launch a restore job manually while another restore job is running, an alert message opens informing you that another job is running and requests you to try again later.

Microsoft SQL Server Restore to Alternate Location Considerations

When you specify to restore a Microsoft SQL Server application to an alternate location, you can restore it to an alternate location on the same machine to same instance or a different instance, or on a different machine to same instance or a different instance.

Prior to performing an Arcserve UDP Agent (Windows) restore of a Microsoft SQL Server application to an alternate location, you must consider the following:

If alternate location is on the same machine

For this option, you can restore a database to a new location (with the same name) or restore with a new name (to the same location):

Same Name - New Location - Same Instance
For example, if Database A is installed in the current SQL Server at "C:\DB_A" and has been backed up. You can use this option and specify "Alternate File Location" to restore Database A to an alternate location such as "D:\Alternate_A.
After the database has been restored, the database file located at the new location to same instance "D:\Alternate_A" will then be used.

Important! During restore, if you change the database location but retain the database name, then the previous database gets deleted after the restore is complete. The restored database file will be pointed to the new location.

Same Location - New Name - Different Instance
For example, if you have two databases (Database A and Database B) installed in the current SQL Server and both have been backed up. You can use this option and specify "New database Name" to restore Database A to same location as Database A_New to a different instance.
After the databases have been restored, this location will now have three databases (Database A, Database B, and Database A_New) to a different instance.

If alternate location is on the different machine

The SQL Server version on the Arcserve UDP Agent (Windows) server must be backwards compatible to the version of the SQL Server used during the backup session.
For example, you can restore a SQL Server 2008 machine to a SQL Server 2010 machine; however, you cannot restore a SQL Server 2010 machine to a SQL Server 2008 machine.

Restoring a database of 64-bit instance to 32-bit instance is not supported.
The Restore to original location option is supported only if the source instance and the destination instance have the same name with the same or higher SQL version.

Microsoft SQL Server 2012/2014 AAG Restore Considerations

When restoring a Microsoft SQL Server 2012/2014 database that is part of an AlwaysOn Availability Group (AAG), you must be aware of some considerations.

If the MS SQL database is part of the MS SQL 2012/2014 Always On Availability Group (AAG), and restoring to the original location fails, perform the following tasks:

Remove the database to be restored away from the Availability Group. For more information, see the link.
Share the backup session to Arcserve UDP Agent (Windows)on every Availability Group node and then restore the session by Arcserve UDP Agent (Windows)on every Availability Group node.
Add the database back to an Availability Group. For more information, see the link.

Microsoft SQL Server 2016 or later versions AAG Restore Considerations

When restoring a Microsoft SQL Server 2016 or later versions database that is part of an Always On Availability Group (AAG), you must be aware of some considerations.

If MS SQL database is part of the MS SQL 2016 or later versions Always On Availability Group (AAG), and restoring to the original location fails, perform the following tasks:

Remove the database to be restored away from the Availability Group. For more information, see the link.
Share the backup session to Arcserve UDP Agent (Windows) on Primary Availability Group node and then restore the session by Arcserve UDP Agent (Windows) on Primary Availability Group node.
Add the database back to Secondary Node Availability Group. For more information, see the link.

Microsoft SQL Server Cluster Shared Volume (CSV) Restore Considerations

If the Microsoft SQL server Master database is part of the Cluster Shared Volume (CSV) environment, and restoring to the original location fails, enable the registry key. For more information, see Restore Considerations.