Using CA ARCserve D2D On Demand › Perform a Restore › Application Restore › Application Restore - MS SQL Server › MS SQL Server Restore to Alternate Location Considerations

MS SQL Server Restore to Alternate Location Considerations

When you specify to restore a Microsoft SQL Server application to an alternate location, you can either restore it to an alternate location on the same machine or on a different machine. Prior to performing a CA ARCserve D2D On Demand restore of a Microsoft SQL Server application to an alternate location, you should consider the following:

If alternate location is on the same machine

For this option, you can either 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

  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 "D:\Alternate_A" will then be used.

• Same Location - New Name

  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.

  After the databases have been restored, this location will now have three databases (Database A, Database B, and Database A_New).

If alternate location is on the different machine

• The SQL Server installation path must be the same as the path that existed when the backup was performed.

  For example, if the backup of the SQL Server is installed at "C:\SQLServer", then the SQL Server on the new CA ARCserve D2D On Demand server must also be installed at C:\SQLServer.

• The same instance name for the database that existed when the backup was performed must be installed on CA ARCserve D2D On Demand server, otherwise the database associated with that instance will be skipped from the restore.

  For example, if the backup of the SQL Server contained "Instance_1" with Database A and Database B and "Instance_2" with Database C, but the CA ARCserve D2D On Demand server only has "Instance_1". After the restore is complete, Database A and Database B will be restored, but Database C will not be restored.

• The SQL Server version on the CA ARCserve D2D On Demand 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 2005 machine to a SQL Server 2008 machine; however, you cannot restore a SQL Server 2008 machine to a SQL Server 2005 machine.

• Restoring a database of 64-bit instance to 32-bit instance is not supported.