Aws Log in Failed If This Instance Has Just Started Up Try Again in a Minute or Two
Amazon RDS - Common Problems with native SQL Server fill-in and restore
One Click Feedback
Delight help us to improve the site by rating the quality of this article by clicking a button below.
Summary
In my introductory commodity (link) I outlined details of how to create and restore SQL Server backup files to and from on-premise SQL Servers.
In this follow up article I'm going to discuss some common issues I've experienced when both backing upwardly and restoring RDS databases.
Amazon Web Services (AWS) have also published a useful article list some of the limitations hither : http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/SQLServer.Procedural.Importing.html
Effect ane : RDS Server not Configured Correctly
The post-obit error tin occur when running the rds_restore_database stored procedure.
Msg 50000, Level 16, State 0, Procedure rds_restore_database, Line 38 @restore_db_name : Name of the database existence restored.
Database fill-in/restore option is not enabled yet or is in the procedure of being enabled. Please try again after.
USAGE:
EXECUTE msdb.dbo.rds_restore_database @restore_db_name, @S3_arn_to_restore_from, [@KMS_master_key_arn]
@S3_arn_to_restore_from : S3 ARN of the fill-in file used to restore database from.
@KMS_master_key_arn : KMS client chief primal ARN to decrypt the fill-in file with.
The above fault occurs if the SQLSERVER_BACKUP_RESTORE choice has not been applied to the server (see the original article for details of how to practise this).
Issue ii : Cannot Restore a Database and Supplant an Existing Database
The following error tin also occur when running the rds_restore_database stored process.
Msg 50000, Level xvi, Land 0, Procedure rds_restore_database, Line 71 @restore_db_name : Name of the database being restored.
Database SQLMatters already exists. Cannot restore database with the same name.
USAGE:
EXECUTE msdb.dbo.rds_restore_database @restore_db_name, @S3_arn_to_restore_from, [@KMS_master_key_arn]
@S3_arn_to_restore_from : S3 ARN of the fill-in file used to restore database from.
@KMS_master_key_arn : KMS customer main key ARN to decrypt the fill-in file with.
In this instance this has occurred because information technology'south not possible to overwrite an existing database while restoring a backup, unlike a normal SQL Server restore. In other words, there's no equivalent of the 'WITH Supervene upon' pick in RDS. Instead you have to delete the database yourself, before running the restore command above.
Issue 3 : Trying to Restore more than One Database from the Same Source
Sometimes the post-obit error is reported when checking on the progress of the restore using the rds_task_status stored procedure (the restore appears to start correctly as no error is returned by rds_restore_database).
[2017-11-13 15:32:22.277] Aborted the job because of a task failure or a concurrent RESTORE_DB request.
[2017-11-thirteen xv:32:22.310] Task ID 22 (RESTORE_DB) exception: Database SQLMattersNew cannot exist restored because there is already an existing database with the aforementioned file_guids on the case.
This error occurs when trying to create more than one database on an RDS server from the same backup. This will occur fifty-fifty if the new database has a different proper name, so renaming the database is not a workaround.
The only manner (that I know of) to create a new set of file GUIDs is to create a make new database from scratch, i.east.one that isn't created from a restore. Once the new database is created you'd then need to re-create schema, data, stored procs, permissions etc using some sort of scripting, eastward.one thousand. the 'Generate Scripts' option in SSMS. Alternatively there is also the AWS Data Migration Service (DMS).
Issue four : Exceeding the Limit of 30 Databases per Instance
RDS limits yous to 30 user databases per instance. If you lot try and exceed that limit and then yous'll get the SQL error below (if trying to create the database using SQL).
Msg 50000, Level 15, State ane, Procedure rds_create_database_trigger, Line 33
Database creation would exceed quota of xxx
Msg 3609, Level 16, Country 2, Line 1
The transaction ended in the trigger. The batch has been aborted.
If yous effort and exercise this via the GUI then you'll get a like mistake : 
Source: https://sqlmatters.com/Articles/Amazon%20RDS%20-%20Common%20Issues%20with%20native%20SQL%20Server%20backup%20and%20restore.aspx
0 Response to "Aws Log in Failed If This Instance Has Just Started Up Try Again in a Minute or Two"
Post a Comment