Restoring an Amazon RDS for SQL Server Instance to a Different Amazon RDS for SQL Server Instance

You can restore an Amazon RDS for SQL Server instance to a different Amazon RDS for SQL Server instance. This is an out-of-place restore.

When you perform this type of restore, you don't need to edit the physical path, because the restore uses the default path. If you edit the database name to perform an out-of-place restore to the same instance, AWS internally modifies the datafiles, since a database with the same data file names already exists. If a database with the same name already exists on the destination instance, it is deleted and recreated.

Procedure

From the Command Center navigation pane, go to Protect > Databases.

The Overview page appears.
On the Instances tab, click the instance.

The instance properties page appears.
On the Overview tab, in the Recovery points section, choose the date and time for the backup you want to use, and then click RESTORE.

The Backup content page appears.
Select the content to restore, and then click RESTORE.

The Restore options dialog box appears.
From the Restore type list, select Cross instance restore.
From the Destination server list, select the server to restore the data to.
From the Destination instance list, select the instance to restore the data to.
Configure options related to the Destination server and the Destination instance you have selected.

The following three fields may or may not appear, depending on your destination server and destination instance selections.
1. To specify the access node, from the Access node list, select an access node.
2. To specify the staging instance, from the Staging instance list, select an instance.
3. To specify a staging path, in the Staging path box, enter the staging path on the access node or the destination server.
To change a database name, do the following:
1. Under Redirect options, which is under Data files, click the Edit (pencil) button in the row for the database.
  
  The Edit database options dialog box appears.
2. In the Database name box, enter the new name.
To specify pre or post commands, under Pre or Post options, which are under Advanced options, do the following:
1. In the Pre recovery command box, enter the path of the process to run before the restore.
2. In the Post recovery command box, enter the path of the process to run after the restore.
3. To run a post process for all restore operation attempts of a job phase, whether it is successful, interrupted, suspended, or when the job fails, select Run post restore process for all attempts.
4. To specify the user to run the pre and post commands, move the Run as User toggle button to the right and type the user name and password.
To select a MediaAgent to use for the recovery, under Data path, from the Select MediaAgent list, select a MediaAgent server.
To start the database in a suspended state, under Startup options, move the Start up in suspended state toggle to the right and type the Dependent job ID.
You can configure a schedule to repeat this restore operation. To create a schedule, do the following:
1. Click Schedule.
  
  The Add schedule dialog box appears.
2. In the Name box, type a name for the schedule.
3. Configure the Frequency and Repeat parameters.
4. To specify exceptions to the schedule, click Exceptions.
  
  The Exceptions dialog box appears.
5. Configure the exception parameters:
  - You can click Add Exception to save a set of exception parameters and continue adding sets of exception parameters.
  - Click Save when you have finished configuring the exception parameters.
6. Under the Range of recurrence section, specify the Start date and End date to schedule the recurrence range of the restore operation.
7. To save the schedule and return to the restore dialog box, click Schedule.
Click SUBMIT.