EBS Snapshot DR Gap / Durability Risk Diagnostic Troubleshooter (Part 1)
Use the interactive troubleshooter below to identify your EBS snapshot DR gap or durability risk symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | Incomplete Snapshots (Incremental Chain Broken) | { "SnapshotId": "snap-0aaEXAMPLEe306d62", "Status": "pending", "VolumeSize": 8 } | The incremental snapshot moves to an error state if there are no put or complete requests made within the specified 60-minute timeout period. | aws ebs complete-snapshot --snapshot-id snap-0aaEXAMPLEe306d62 --changed-blocks-count 5 --checksum 6D3nmwi5f2F0wlh7xX8QprrJBFzDX8aacdOcA3KCM3c= --checksum-algorithm SHA256 --checksum-aggregation-method LINEAR |
| 2 | Snapshots Auto-Deleted (Data Lifecycle Manager) | aws dlm delete-lifecycle-policy --policy-id policy-0123456789abcdef0 | If you delete a policy with an archive-enabled, age-based schedule, the snapshots scheduled to be archived are permanently deleted at the scheduled archive date and time. | N/A |
| 3 | EBS Snapshot Restoration Latency (RTO Risk) | warning state in the I/O Performance status check | For volumes created from snapshots, storage blocks must be pulled down from Amazon S3, causing a significant increase in I/O latency the first time each block is accessed. | sudo dd if=/dev/xvdf of=/dev/null bs=1M |