How can I check the progress of an AWS Backup restore job for Amazon EFS?

3 minute read

I want to check when my AWS Backup restore job for Amazon Elastic File System (Amazon EFS) is complete.


Stages of a restore job

An AWS Backup restore job for Amazon EFS goes through the following stages:

  • Created: This is the initial state. The AWS Backup restore job is about to enter into the system.
  • Pending: Initial checks passed, and the job is now waiting to start.
  • Running: The restore is in progress.
  • Completed: The restore job is completed.
  • Failed: The restore job failed. Restore jobs can fail for a number of reasons. These include missing permissions on the restore role and source control policy (SCP) or a vault access policy preventing the restore.

Restore job duration

The duration of an AWS Backup restore job depends on a number of factors. These include the size of the file system, size of the files, and the number of files being restored. There's no set duration for an AWS Backup restore job to complete.

Note: AWS Support can't speed up an Amazon EFS restore job.

Amazon EFS restore performance

You can't track the progress of a restore job for Amazon EFS. But, you can expect Amazon EFS backup jobs to run at the following rates:

  • 500 files for file systems that are composed of mostly small files
  • 100 MBs for file systems that are composed of mostly large files

Note: Amazon EFS restore operations can often take longer than the corresponding Amazon EFS backup jobs.

Splitting larger restore jobs into smaller restore jobs

You might want to restore an Amazon EFS file system that contains a large number of small files. Use item-level restore to break down the restore job into multiple smaller restore jobs. It's a best practice to use this approach when the item-level restore evenly partitions the file system. This approach also creates multiple restore directories in the root directory of your Amazon EFS where restore files are stored. You must manually merge the directories into the required folder.

Additional features and limitations

Note the following features and limitations when using AWS Backup with Amazon EFS:

  • Using AWS Backup doesn't consume accumulated burst credits, and it doesn't count against the General Purpose mode file operation limits.
  • After your Amazon EFS restore is complete, it asynchronously loads files. If you're monitoring Amazon EFS or Amazon CloudWatch metrics, then the metrics might not show the actual size of the restored file system. When you mount on a client to start using the file system, the files are loaded and you can see the actual file system size. For more information, see Metered size of an Amazon EFS file system.
  • AWS Backup supports non-destructive restores with Amazon EFS. A non-destructive restore means that a restored file system doesn't delete or overwrite the source or existing file system. Instead, AWS Backup restores your file system to a recovery directory that's off the root directory.

For more information on restoring Amazon EFS file systems with AWS Backup, see Restoring an Amazon EFS file system.

Related information

Feature availability by resource

AWS OFFICIALUpdated 10 months ago