AWS sql-server-ec2 documentation change
Summary
Added troubleshooting section for SQL Server database restore failures and updated navigation links
Security assessment
The changes focus on operational troubleshooting steps for database restoration failures. There is no mention of vulnerabilities, security patches, or access controls. The added content helps diagnose technical failures but doesn't address security weaknesses.
Diff
diff --git a/sql-server-ec2/latest/userguide/ms-ssdb-ec2-vss-restore-from-snap.md b/sql-server-ec2/latest/userguide/ms-ssdb-ec2-vss-restore-from-snap.md index 8eb62422b..c345f046c 100644 --- a//sql-server-ec2/latest/userguide/ms-ssdb-ec2-vss-restore-from-snap.md +++ b//sql-server-ec2/latest/userguide/ms-ssdb-ec2-vss-restore-from-snap.md @@ -5 +5 @@ -Runbook parametersRun the restore process +Runbook parametersRun the restore processTroubleshoot restoring your SQL Server database using AWS VSS solution @@ -123 +123 @@ To run the restore in the AWS Management Console, follow these steps: -To review the execution status, navigate to the **Executed Steps** section within the automation execution details. This section displays all of the steps that ran, along with their runtime status. If the automation execution failed, follow the troubleshooting steps outlined in [](./ms-ssdb-ec2-vss-restore-troubleshoot.html). +To review the execution status, navigate to the **Executed Steps** section within the automation execution details. This section displays all of the steps that ran, along with their runtime status. If the automation execution failed, follow the troubleshooting steps outlined in . @@ -178,0 +179,47 @@ If volume mapping metadata was not used for your restore operation, follow these +## Troubleshoot restoring your SQL Server database from AWS VSS solution snapshots using the Systems Manager console + +Before you try any troubleshooting steps, we recommend that you verify that you've met all [VSS snapshot restore prerequisites](./ms-ssdb-ec2-vss-restore-prereq.html). + +In the Systems Manager console, the **Failure details** section in the automation runbook **Execution Details** page includes the following information: + + * **Failure Message** + + * **Failure Type** + + * **Failure Stage** + + + + +Together, these details offer a general overview of the cause of the failure. For a more comprehensive understanding, you must examine the specific step execution that failed. + +The steps in `AWSEC2-RestoreSqlServerDatabaseWithVss` can be classified into three main categories: + +**Script Execution Steps** + + +These use the `aws:executeScript` action and include the following steps. + + * `ExtractPrepareVssRestoreOutput` + + * `PrepareForVolumeCreation` + + * `ExtractCurrIterValues` + + * `ConcatVolumeIds` + + + + +If one of these steps fails, investigate the step execution and review the execution logs found under **OutputPayload** in the **Outputs** section to determine what caused the issue. + +**EC2 API Interaction Steps** + + +These interact with Amazon EC2 APIs to create volumes from snapshots, attach them to instances, and monitor volume status. Many of these steps are performed within loop steps. If a loop step fails, identify the specific step within the loop that caused the failure to pinpoint the root cause. The **Failure details** section in the step execution details page provides relevant information for debugging. + +**Run Command Execution Steps** + + +These use the `aws:RunCommand` action to execute commands on the target instance. If a failure occurs due to a run command execution, examine the step execution details. Under **Outputs** , select the **CommandId** link for the command to access the **Run command execution** page, where you can view the complete log for debugging purposes. + @@ -187 +234 @@ Prerequisites -Troubleshoot VSS snapshot restore +Evaluate downgrading your SQL Server edition