Recently i worked on migrating sql server databases running on amazon EC2 instances to Amazon RDS instances. Starting from 27th Jul 2016 Amazon announced you can ship your databases from ec2 to rds using native backup and restore method. Let’s see how it works.
- Assume you have RDS Instance ready with default setting
- Create a custom option group “NativeBackup” and enable S3 bucket full access. You may use the below IAM rule
- Right click on Custom option group and then click on Add option –> Select SQLSERVER_BACKUP_RESTORE option — > Apply Immediately
- Now you have custom group setup with native backup and restore feature and correct permissions to S3 bucket. Now, Add this group to RDS instance. Right click on RDS instance –> Click on Modify –> Navigate to Option group —> Assign the NativeBackup group which was created in the step 2 –> Click Modify instance
- Now, Copy the backup of EC2 instances to S3 bucket. You may use AWS CLI command line tool to copy from one EC2 instance to S3 bucket
Aws s3 cp \\ec2backuplocations <a href="s3://Infra_Bucket" target="_blank" rel="noreferrer" data-mce-href="s3://Infra_Bucket">s3:<wbr>/<wbr>/</a>Buket_Name --profile “your profilename"
- Once you are done with copying the backup to S3 location, then you may use the below script to restore the database from backup
- Restore will begin, you may use the below stored procedure to get the status of the restore process
- That’s all about the restore! Below are the possible errors you may encounter while migrating to RDS instance
Aborted the task because of a task failure or a concurrent RESTORE_DB request.
Database TestDB cannot be restored because there is already an existing database wih the same family_guid on the instance.
Reason: If you have same file guid for data or log file exists then you cannot restore to rds instance. The file guid’s are unique to each database. There is a possibility to get the same fileguid based on the name.
You may use sys.master_files view to get the details of file guid
Another reason for this error is you have already restored the same database and trying to restore, hence the error. RDS has the limitation that you cannot restore the same database file names on the same instance.
Resolution: Do not restore the same database names on the same RDS instance
Msg 229, Level 14, State 5, Procedure rds_restore_database, Line 1 [Batch Start Line 45]
The EXECUTE permission was denied on the object ‘rds_restore_database’, database ‘msdb’, schema ‘dbo’.
Reason: You do not have permission to perform the restore
Please make sure the login you used have execute permission for the stored procedure rds_restore_database. If you are using master credentials and you still getting the same error then you have not granted full permission to S3 bucket or missing IAM roles for the S3 bucket. Please grant the access and re-try
Msg 50000, Level 16, State 0, Procedure rds_restore_database, Line 73 [Batch Start Line 22]
A task has already been issued for database:TestDB with task Id: 3, please try again later.
Reason: You have issued the restore command multiple times and hence the error.
Resolution: Do not issue the restore command twice for the same database. Kill the multiple restore processes and re-issue the command
Hope you enjoyed the post!