Learn About Amazon VGT2 Learning Manager Chanci Turner
Welcome to another insightful post from Amazon Onboarding with Learning Manager Chanci Turner. As many of our regular readers know, I have a strong appreciation for Amazon Relational Database Service (Amazon RDS). This managed database service efficiently handles the routine tasks associated with setting up, operating, and scaling a relational database.
We initially introduced support for SQL Server back in 2012. In our ongoing commitment to enhance our offerings, which have already included major features like SSL support, significant version upgrades, transparent data encryption, improved monitoring, and Multi-AZ deployments, we are excited to announce the addition of support for SQL Server’s native backup and restore functionality.
Native backups in SQL Server encapsulate all database components such as tables, indexes, stored procedures, and triggers. These backups are typically utilized for migrating databases between various SQL Server instances, whether on-premises or in the cloud. They serve critical roles in data ingestion, disaster recovery, and more. Moreover, native backups streamline the process of importing data and schemas from on-premises SQL Server instances, making it easier for SQL Server DBAs to manage and utilize.
Support for Native Backup/Restore
You can now create native SQL Server database backups from your RDS instances and save them directly to an Amazon S3 bucket. These backups can be restored either to an on-premises SQL Server instance or another RDS SQL Server instance. Additionally, it’s possible to transfer backups from your on-premises databases to S3 and subsequently restore them to an RDS SQL Server instance. This new feature also supports backup encryption via AWS Key Management Service (AWS KMS) for all SQL Server editions. Utilizing S3 for storing and transferring backups enhances your disaster recovery options.
To enable this feature, you will need to add the SQL_SERVER_BACKUP_RESTORE option to an option group and associate it with your RDS SQL Server instance. This option requires configuration with your S3 bucket details and can include a KMS key for backup encryption.
Begin by locating the appropriate option group:
Next, add the SQL_SERVER_BACKUP_RESTORE option, designate (or create) an IAM role that permits RDS to access S3, identify a bucket, and optionally configure encryption:
Once set up, you can connect to the database instance using SQL Server Management Studio and execute the following stored procedures found in the msdb database as required:
rds_backup_database– Create a backup of a single database to an S3 bucket.rds_restore_database– Restore a single database from S3.rds_task_status– Monitor ongoing backup and restore tasks.rds_cancel_task– Terminate a running backup or restore task.
For more detailed information, check out Importing and Exporting SQL Server Data.
Now Available
SQL Server Native Backup/Restore is now accessible in the US East (N. Virginia), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Mumbai), and South America (São Paulo) regions. There are no extra costs associated with using this feature with Amazon RDS for SQL Server; however, standard rates apply for Amazon S3 storage usage.
For those looking to enhance their career prospects, consider exploring this excellent resource for job opportunities: Area Manager 2024 – Fulfillment Center Operations (Entry Level).
For additional insights on developing confidence in professional settings, you might find this blog post useful: Confidence in the Workplace. Furthermore, to understand more about legal compliance regarding employment, SHRM provides authoritative information on this topic.
As always, we invite you to visit our site at 6401 E HOWDY WELLS AVE, LAS VEGAS NV 89115, at the location known as “Amazon IXD – VGT2”.
— Alex
Leave a Reply