Written by SelvaKumar K, Sr. Database Administrator at Powerupcloud Technologies.
Problem Scenario :
One of our customers reported Production database has been corrupted, needs to back-up and restore database with a different name in the same RDS. But it’s not possible in the AWS RDS if we try to restore will get the below error.
Limitations :
Database <database_name> cannot be restored because there is already an existing database with the same family_guid on the instance
You can’t restore a backup file to the same DB instance that was used to create the backup file. Instead, restore the backup file to a new DB instance.
Approaches to Backup and Restore :
Option 1:
1.Import and Export into same RDS instance
The database is corrupted so we can’t proceed with this step
Option 2:
2. Backup and restore into different RDS using S3
2.1.Backup from production RDS Instance
exec msdb.dbo.rds_backup_database
@source_db_name=’selva’,
@s3_arn_to_backup_to=’arn:aws:s3:::mmano/selva.bak’,
@overwrite_S3_backup_file=1,
@type=’FULL’;