August 26, 2025 at 3:43 pm
Having real fun with this.
It isn't possible to set the option group, to enable the AWS SQL backup routines, because you can't execute the CloudShell command to assign an options group (aws rds modify-db-instance), in RDS Custom.
I can't restore an RDS Custom snapshot, because that will just create another RDS Custom, and I want RDS Standard.
It looks like I have to backup to a local drive (SQL Server 2019. 2022 will allow a non-Azure URL, but we aren't using 2022), then copy it to an S3 bucket and then restore it to RDS Standard.
Does anybody have an opinion on this, before I disappear down another rabbit-hole and find something won't actually work?
Thanks for your time,
Steve.
August 27, 2025 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
September 1, 2025 at 3:59 pm
you can backup and restore, too and from an S3 bucket, will that help?
you need to set up a few things in rds first, and make sure of permissions on the S3 bucket. you can even stripe the backup to up to ten files to speed things up; it feels strange compared to on prem, because it's more like an async job you can monitor, and not an actual backup command.
then , it can be backup and restored, same or different names.
--back it up
exec msdb.dbo.rds_backup_database
@source_db_name='StackOverflow',
@s3_arn_to_backup_to='arn:aws:s3::BrainDonor/StackOverflow-Full.bak',
@overwrite_S3_backup_file=1;
--monitor it over and over
EXEC msdb.dbo.rds_task_status
--RESTORE it some where else
EXEC msdb.dbo.rds_restore_database
@restore_db_name='StackOverflow2',
@s3_arn_to_restore_from='arn:aws:s3:::BrainDonor/StackOverflow-Full.bak',
@with_norecovery = 1;
EXEC msdb.dbo.rds_task_status
Lowell
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply