Skip to content

AWS Backup EFS restore jobs stuck in PENDING status for 4+ hours

0

Account: 857960617987 Region: us-east-2 Issue: All AWS Backup EFS restore jobs stuck in PENDING status for 4+ hours

Stuck Job IDs:

  • a787f8aa-8e81-4d59-9988-ef42d2526eef (restore to original, started 16:20 UTC)
  • e4b6572f-622e-4976-bf35-421a7cb1125c (restore to new EFS, started 17:58 UTC)
  • e32ae304-47b4-45db-843b-41333b4f2ece (restore to new EFS, started 17:01 UTC)
  • [NEW JOB ID] (restore to new EFS, also stuck)

All jobs show 0% progress. No logs, no error, nothing

Verified:

  • IAM permissions correct (AWSBackupDefaultServiceRole)
  • KMS key policy updated
  • No service health issues reported
  • EFS file system healthy
asked 2 months ago36 views
1 Answer
0

Based on the information provided, you're experiencing an issue with multiple AWS Backup restore jobs for EFS that are stuck in PENDING status for over 4 hours with 0% progress.

This appears to be an unusual situation that requires AWS Support intervention. While your verification steps (checking IAM permissions, KMS key policy, service health, and EFS health) are appropriate troubleshooting measures, the persistent PENDING status across multiple restore jobs suggests a potential underlying service issue.

You can try the following additional troubleshooting steps:

  1. Check if there are any restore job summaries available using the ListRestoreJobSummaries API, which provides information about restore jobs created or running within the last 30 days.

  2. Attempt to create a new restore job with different parameters to see if the issue persists.

  3. If possible, try a restore in a different AWS region to determine if the issue is region-specific.

  4. Since this appears to be affecting multiple restore jobs and you've already verified the common configuration elements, I recommend opening an AWS Support case with the details you've provided, including all the job IDs and timestamps. Make sure to set the severity as high given the business impact of not being able to restore your EFS backups.

If you have Business or Enterprise Support, you should be able to get assistance relatively quickly for this type of service-impacting issue.
Sources
ListRestoreJobSummaries - AWS Backup
URGENT: Instance Down for 4 Days, No Response from AWS Support (Case IDs: 17nnnnnnnnnnnnn & 17nnnnnnnnnnnnn) | AWS re:Post

answered 2 months ago
  • There are no logs anywhere, Already tried to create new restore job... thats how I ended up with. 4 ... tried old FS, new FS and what not ... I agree that its likely some issue on AWS side but we dont have technical support plan

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.