How do I troubleshoot EFS file system restore issues for AWS Backup?

Short description

When an EFS access point mounts the file system, you might not find the restored folder in the EFS file system. This is because the access point can enforce a different root directory for the file system. Amazon EFS clients can access data only in the specified directory or its sub-directories. After you complete the restore and mount an EFS file system, you must get the data from the aws-backup-restore_datetime restored directory that's in the root directory.

Resolution

"Insufficient privileges" error

When you use the AWS Backup console to start an EFS restore job, you get the following error message:

"Insufficient privileges to perform this action. Please consult with the account administrator for necessary permissions."

To resolve this issue, see How do I resolve "insufficient privileges" and "access denied" errors when I use AWS Backup to perform an Amazon EFS restore? Make sure that you grant the iam:PassRole permission to the IAM role that you use as the restore role.

Slow restore jobs

AWS Backup doesn't provide service-level agreements (SLAs) for a restore time. Restore times can vary based on system load and capacity, even for restores that contain the same resources. You can expect an EFS restore time of 1,500 files per second or 200 MBps, whichever is slower.

To check the progress of your slow restore jobs, see How can I check the progress of an AWS Backup restore job for Amazon EFS?

Note: A restore from cold storage typically takes 4 hours more than a restore from warm storage.

"Some of the specified directories or files were not found" error

When an EFS item-level restore job fails because of an incorrect file path or missing file, you get the following error message:

"Some of the specified directories or files were not found"

To resolve this issue, take the following actions:

• Make sure that the file paths are correct and relative to the mount point. For example, if you mount the file system to /apps/efs and the file path is apps/efs/file1, then you must enter /file1. In this example, /file1 is relative to /apps/efs.
• After you back up your resources, don't delete or move the files that you restore. You can't find missing files during the restore process.
  Note: Paths are case sensitive and can't contain special characters, wildcard characters, or regular expression (regex) strings.

Related information

Use the AWS Backup console to restore an Amazon EFS recovery point