Cannot Restore DB to RDS Instance
I am getting below error when trying to restore DB from S3 Bak file -
100 percent processed.
[2018-11-12 19:32:21.677] Processed 32980832 pages for
database 'RDSBackup', file 'SourceDB_NEW' on file 1.
[2018-11-12 19:32:21.680]
Processed 4547 pages for database
'RDSBackup', file 'SourceDB_NEW_log' on file 1.
[2018-11-12 19:32:22.013]
RDSBackup_FULL_COPY_ONLY_20181112_010009.bak:
S3 processing has been aborted.
Error started after the source DB version changed from SQL2012 Enterprise to SQL2016 Standard.
sql-server amazon-web-services amazon-s3 amazon-rds restore edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
asked Nov 12 '18 at 20:58
cindy
6924
add a comment |
I am getting below error when trying to restore DB from S3 Bak file -
100 percent processed.
[2018-11-12 19:32:21.677] Processed 32980832 pages for
database 'RDSBackup', file 'SourceDB_NEW' on file 1.
[2018-11-12 19:32:21.680]
Processed 4547 pages for database
'RDSBackup', file 'SourceDB_NEW_log' on file 1.
[2018-11-12 19:32:22.013]
RDSBackup_FULL_COPY_ONLY_20181112_010009.bak:
S3 processing has been aborted.
Error started after the source DB version changed from SQL2012 Enterprise to SQL2016 Standard.
sql-server amazon-web-services amazon-s3 amazon-rds restore edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
asked Nov 12 '18 at 20:58
cindy
6924
"processing has been aborted" is not enough information for your peers to help you solve. Unless the instance you're restoring to is not SQL Server 2016 or above (checkSELECT @@VERSION;), you should contact RDS support. If the version is 2012 or 2014, you're going to have to upgrade or migrate to a different server with a newer version. You will never be able to restore a 2016 backup to a 2012 or 2014 server.
– Aaron Bertrand
Nov 12 '18 at 21:03
Might be that the database is using an enterprise feature of 2012 that is still an enterprise feature in 2016; hence the error.
– Larnu
Nov 12 '18 at 23:58
I get This when I run select @@version Microsoft SQL Server 2017 (RTM-CU9-GDR) (KB4293805) - 14.0.3035.2 (X64) Jul 6 2018 18:24:36 Copyright (C) 2017 Microsoft Corporation Web Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
– cindy
Nov 13 '18 at 14:33
add a comment |
I am getting below error when trying to restore DB from S3 Bak file -
100 percent processed.
[2018-11-12 19:32:21.677] Processed 32980832 pages for
database 'RDSBackup', file 'SourceDB_NEW' on file 1.
[2018-11-12 19:32:21.680]
Processed 4547 pages for database
'RDSBackup', file 'SourceDB_NEW_log' on file 1.
[2018-11-12 19:32:22.013]
RDSBackup_FULL_COPY_ONLY_20181112_010009.bak:
S3 processing has been aborted.
Error started after the source DB version changed from SQL2012 Enterprise to SQL2016 Standard.
sql-server amazon-web-services amazon-s3 amazon-rds restore edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
asked Nov 12 '18 at 20:58
cindy
6924
I am getting below error when trying to restore DB from S3 Bak file -
100 percent processed.
[2018-11-12 19:32:21.677] Processed 32980832 pages for
database 'RDSBackup', file 'SourceDB_NEW' on file 1.
[2018-11-12 19:32:21.680]
Processed 4547 pages for database
'RDSBackup', file 'SourceDB_NEW_log' on file 1.
[2018-11-12 19:32:22.013]
RDSBackup_FULL_COPY_ONLY_20181112_010009.bak:
S3 processing has been aborted.
Error started after the source DB version changed from SQL2012 Enterprise to SQL2016 Standard.
sql-server amazon-web-services amazon-s3 amazon-rds restore sql-server amazon-web-services amazon-s3 amazon-rds restore edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
asked Nov 12 '18 at 20:58
cindy
6924
edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
asked Nov 12 '18 at 20:58
cindy
6924
edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
edited Nov 13 '18 at 6:59
John Rotenstein
68.1k775119
68.1k775119
asked Nov 12 '18 at 20:58
cindy
6924
asked Nov 12 '18 at 20:58
cindy
6924
asked Nov 12 '18 at 20:58
cindy
6924
6924
"processing has been aborted" is not enough information for your peers to help you solve. Unless the instance you're restoring to is not SQL Server 2016 or above (checkSELECT @@VERSION;), you should contact RDS support. If the version is 2012 or 2014, you're going to have to upgrade or migrate to a different server with a newer version. You will never be able to restore a 2016 backup to a 2012 or 2014 server.
– Aaron Bertrand
Nov 12 '18 at 21:03
Might be that the database is using an enterprise feature of 2012 that is still an enterprise feature in 2016; hence the error.
– Larnu
Nov 12 '18 at 23:58
I get This when I run select @@version Microsoft SQL Server 2017 (RTM-CU9-GDR) (KB4293805) - 14.0.3035.2 (X64) Jul 6 2018 18:24:36 Copyright (C) 2017 Microsoft Corporation Web Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
– cindy
Nov 13 '18 at 14:33
add a comment |
"processing has been aborted" is not enough information for your peers to help you solve. Unless the instance you're restoring to is not SQL Server 2016 or above (checkSELECT @@VERSION;), you should contact RDS support. If the version is 2012 or 2014, you're going to have to upgrade or migrate to a different server with a newer version. You will never be able to restore a 2016 backup to a 2012 or 2014 server.
– Aaron Bertrand
Nov 12 '18 at 21:03
Might be that the database is using an enterprise feature of 2012 that is still an enterprise feature in 2016; hence the error.
– Larnu
Nov 12 '18 at 23:58
I get This when I run select @@version Microsoft SQL Server 2017 (RTM-CU9-GDR) (KB4293805) - 14.0.3035.2 (X64) Jul 6 2018 18:24:36 Copyright (C) 2017 Microsoft Corporation Web Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
– cindy
Nov 13 '18 at 14:33
"processing has been aborted" is not enough information for your peers to help you solve. Unless the instance you're restoring to is not SQL Server 2016 or above (check
SELECT @@VERSION;), you should contact RDS support. If the version is 2012 or 2014, you're going to have to upgrade or migrate to a different server with a newer version. You will never be able to restore a 2016 backup to a 2012 or 2014 server.– Aaron Bertrand
Nov 12 '18 at 21:03
"processing has been aborted" is not enough information for your peers to help you solve. Unless the instance you're restoring to is not SQL Server 2016 or above (check
SELECT @@VERSION;), you should contact RDS support. If the version is 2012 or 2014, you're going to have to upgrade or migrate to a different server with a newer version. You will never be able to restore a 2016 backup to a 2012 or 2014 server.– Aaron Bertrand
Nov 12 '18 at 21:03
Might be that the database is using an enterprise feature of 2012 that is still an enterprise feature in 2016; hence the error.
– Larnu
Nov 12 '18 at 23:58
Might be that the database is using an enterprise feature of 2012 that is still an enterprise feature in 2016; hence the error.
– Larnu
Nov 12 '18 at 23:58
I get This when I run select @@version Microsoft SQL Server 2017 (RTM-CU9-GDR) (KB4293805) - 14.0.3035.2 (X64) Jul 6 2018 18:24:36 Copyright (C) 2017 Microsoft Corporation Web Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
– cindy
Nov 13 '18 at 14:33
I get This when I run select @@version Microsoft SQL Server 2017 (RTM-CU9-GDR) (KB4293805) - 14.0.3035.2 (X64) Jul 6 2018 18:24:36 Copyright (C) 2017 Microsoft Corporation Web Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
– cindy
Nov 13 '18 at 14:33
add a comment |
1 Answer
1
active
oldest
votes
I escalated this issue to AWS. As per the latest update, they have made some changes to RDS and I could restore the DB even with a large log file (300GB).
Link for the newest update details is below -
https://aws.amazon.com/blogs/database/rds-sql-server-has-two-new-exciting-backup-and-restore-enhancements/
Alternate solution - At first, I was asked to try to restore with a smaller log file. I shrunk the logs and the restore worked.
Although AWS engineers asked me to keep a check on the logfile size, they made some changes to RDS so as to accommodate S3 bak files with relatively large size as well.
answered Dec 10 '18 at 14:48
cindy
6924
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270000%2fcannot-restore-db-to-rds-instance%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I escalated this issue to AWS. As per the latest update, they have made some changes to RDS and I could restore the DB even with a large log file (300GB).
Link for the newest update details is below -
https://aws.amazon.com/blogs/database/rds-sql-server-has-two-new-exciting-backup-and-restore-enhancements/
Alternate solution - At first, I was asked to try to restore with a smaller log file. I shrunk the logs and the restore worked.
Although AWS engineers asked me to keep a check on the logfile size, they made some changes to RDS so as to accommodate S3 bak files with relatively large size as well.
answered Dec 10 '18 at 14:48
cindy
6924
add a comment |
I escalated this issue to AWS. As per the latest update, they have made some changes to RDS and I could restore the DB even with a large log file (300GB).
Link for the newest update details is below -
https://aws.amazon.com/blogs/database/rds-sql-server-has-two-new-exciting-backup-and-restore-enhancements/
Alternate solution - At first, I was asked to try to restore with a smaller log file. I shrunk the logs and the restore worked.
Although AWS engineers asked me to keep a check on the logfile size, they made some changes to RDS so as to accommodate S3 bak files with relatively large size as well.
answered Dec 10 '18 at 14:48
cindy
6924
add a comment |
I escalated this issue to AWS. As per the latest update, they have made some changes to RDS and I could restore the DB even with a large log file (300GB).
Link for the newest update details is below -
https://aws.amazon.com/blogs/database/rds-sql-server-has-two-new-exciting-backup-and-restore-enhancements/
Alternate solution - At first, I was asked to try to restore with a smaller log file. I shrunk the logs and the restore worked.
Although AWS engineers asked me to keep a check on the logfile size, they made some changes to RDS so as to accommodate S3 bak files with relatively large size as well.
answered Dec 10 '18 at 14:48
cindy
6924
I escalated this issue to AWS. As per the latest update, they have made some changes to RDS and I could restore the DB even with a large log file (300GB).
Link for the newest update details is below -
https://aws.amazon.com/blogs/database/rds-sql-server-has-two-new-exciting-backup-and-restore-enhancements/
Alternate solution - At first, I was asked to try to restore with a smaller log file. I shrunk the logs and the restore worked.
Although AWS engineers asked me to keep a check on the logfile size, they made some changes to RDS so as to accommodate S3 bak files with relatively large size as well.
answered Dec 10 '18 at 14:48
cindy
6924
answered Dec 10 '18 at 14:48
cindy
6924
answered Dec 10 '18 at 14:48
cindy
6924
answered Dec 10 '18 at 14:48
cindy
6924
6924
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270000%2fcannot-restore-db-to-rds-instance%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"processing has been aborted" is not enough information for your peers to help you solve. Unless the instance you're restoring to is not SQL Server 2016 or above (check
SELECT @@VERSION;), you should contact RDS support. If the version is 2012 or 2014, you're going to have to upgrade or migrate to a different server with a newer version. You will never be able to restore a 2016 backup to a 2012 or 2014 server.– Aaron Bertrand
Nov 12 '18 at 21:03
Might be that the database is using an enterprise feature of 2012 that is still an enterprise feature in 2016; hence the error.
– Larnu
Nov 12 '18 at 23:58
I get This when I run select @@version Microsoft SQL Server 2017 (RTM-CU9-GDR) (KB4293805) - 14.0.3035.2 (X64) Jul 6 2018 18:24:36 Copyright (C) 2017 Microsoft Corporation Web Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
– cindy
Nov 13 '18 at 14:33