❗Important
The availability of this feature may be limited based on the license type, region, and other criteria. To access this feature, contact Support.
AWS_EFS 8
Error Message: Backup window expired
Error Description: The backup job failed to complete because its duration exceeded the timeframe defined in the backup policy.
Error Solution: Ensure that the backup job starts and completes within the configured backup window in the backup policy. To resolve the error:
Schedule the Start time to an earlier slot to ensure maximum available uptime.
Extend the Backup Window in the backup policy settings to accommodate the new baseline duration.
AWS_EFS 9
Error Message: Failed to initiate backup due to misconfigured content rules
Error Description: The backup job could not start because the EFS (Elastic File System) resource contains invalid or unreachable file paths.
Error Solution: Log into your Druva management console, and verify the configured Include and Exclude rules for the EFS file system. Ensure that the directory paths used are accurate and currently exist on the source.
AWS_EFS 10
Error Message: No files were restored during the restore job
Error Description:
Error Solution: To resolve this issue:
Validate paths: Confirm that the source paths still exist in the backup index and that the destination path is valid and accessible.
Check Permissions: Verify that the required Write and Modify permissions for the destination folder have been granted.
AWS_EFS 12
Error Message: Operation failed due to insufficient permissions
Error Description: The IAM role associated with the backup service has not been granted permissions to write data or pass the required roles during backup execution.
Error Solution:
Verify that the IAM policy attached to the backup service role includes the following permissions:
elasticfilesystem:ClientMount:Access to mount the file system.
elasticfilesystem:ClientWrite: Write access required to back up date.
iam:PassRole: Required for the EC2 instance to assume the necessary permissions for the operation.
AWS_EFS 14
Error Message: Failed to mount EFS share due to connection timeout
Error Description: The client is unable to establish a handshake with the Amazon EFS endpoint, owing to network configuration issues.
Error Solution:
Ensure the Inbound rules of the EFS Security Group and the Outbound rules of the Security Group allow traffic over TCP Port 2049.
Verify that the EFS mount target is reachable from the agent.
For more information, refer to the Prerequisites for EFS protection.
AWS_EFS 16
Error Message: Failed to convert path (UNC long path)
Error Description: The system encountered a UNC (Universal Naming Convention) long path that exceeds the supported character limit.
Error Solution: Verify the restore destination path length:
Reduce the depth of the folder hierarchy or use shorter folder names at the restore destination.
Ensure that the path adheres to the supported limits, with no prohibited symbols or trailing spaces in the directory names.
AWS_EFS 18
Error Message: Failed to unmount because mount path is already in use.
Error Description: The unmount operation failed because the Amazon EFS mount point is currently locked by one or more active processes.
Error Solution:
To resolve this issue:
Ensure no other processes are accessing the EFS mount point. Identify processes using the EFS mount and terminate them, then retry the unmount. I
You may need to force unmount If the mount is hung and standard unmounting fails.
For more information, refer to the AWS documentation.
AWS_EFS 19
Error Message: Failed to mount EFS share due to access denied by server
Error Description:
Error Solution: To resolve this, verify and update the following permissions:
IAM Policy: Ensure the agent’s IAM role explicitly allows the following actions:
elasticfilesystem:ClientMount (to connect)
elasticfilesystem:ClientWrite (if write access is required)
EFS File System Policy: Verify the resource-based policy on the EFS console to ensure it doesn't have a Deny statement overriding your IAM permissions.
AWS_EFS 21
Error Message: Failed to mount EFS share
Error Description: This typically occurs when the EFS mount helper cannot authenticate the request, or due to network-level restrictions.
Error Solution:
Review the agent logs for specific system-level error messages. Validate the IAM permissions and verify the EFS mount configuration on your AWS console. For more information, refer to the AWS documentation.
AWS_EFS 22
Error Message: Failed to mount EFS share as no logon servers available.
Error Description: This error occurs due to network connectivity issues between the EC2 instance and the EFS mount target.
Error Solution:
Ensure that the instance can reach AWS IAM or other authentication endpoints.
Update the Security Group configuration allow outbound traffic (Port 443) to the relevant AWS service ranges
Verify network connectivity or associated DNS resolution issues.
AWS_EFS 24
Error Message: Failed to mount EFS share due to DNS resolution failure
Error Description: This error occurs when the Amazon EC2 instance cannot map the EFS DNS name to an IP address.
Error Solution:
Verify VPC settings: Navigate to the AWS VPC Dashboard, select your VPC, and ensure both DNS hostnames and DNS support are set to Enabled.
Verify DNS resolution: Ensure the EFS DNS name is resolvable from within the VPC.
AWS_EFS 25
Error Message:Failed to mount EFS share
Error Description: This error occurs when the connection to the Elastic File System cannot be established due to network issues or client configuration.
Error Solution: To resolve a general mount failure, review the system logs or the Mount Command output for underlying issues.
AWS_EFS 266
Error Message: Resource not found
Error Description: This occurs when the requested EFS resource, such as the file system, backupset, or mount target, does not exist or is not accessible.
Error Solution: On your AWS console, verify the Resource ID (file system, backup set, mount target, etc.) is correct and available within the selected AWS Account/Region. If the resource is unavailable or deleted, select a different resource and retry the operation.
AWS_EFS 269
Error Message: Subnet and security group not found with required ports open
Error Description: No suitable subnet or security group was identified that allows the EFS backup or restore operation.
Error Solution:
Verify the Security Group attached to mount target allows:
Inbound: NFS (TCP 2049)
Outbound: NFS (TCP 2049) , HTTPS (TCP 443)
Ensure the Security Group is explicitly associated with the Mount Target in each Availability Zone where the EFS is deployed.
For more information, refer to the Prerequisites for EFS protection.
AWS_EFS 270
Error Message: Destination file system selected for restore is deleted
Error Description: The EFS file system chosen as the restore destination has been deleted in AWS.
Error Solution:
To resolve this, you must map the restore job to an active resource:
On your EFS Restore destination settings, select a File System ID that is accessible.
Alternatively, create a new EFS file system in the target region/VPC and select that as the destination file system. Retry the restore operation once a valid resource is selected.
AWS_EFS 271
Error Message: Source file system selected for backup is deleted
Error Description: The Amazon Elastic File System configured as the source for this backup job no longer exists within your AWS environment.
Error Solution: Disable or delete backup sets linked to the decommissioned File System. This ensures the backup scheduler no longer attempts to locate the non-existent resource.
AWS_EFS 272
Error Message: Source file system selected for backup don't have any mount targets
Error Description: This occurs because the file system has not been assigned a mount target within the VPC.
Error Solution:
Verify Mount Target: Navigate to your file system settings and ensure a mount target is created for the specific Subnet/Availability Zone where your backup service resides.
Verify Security Groups: Ensure the Security Group associated with the mount target allows inbound traffic on the required ports.
For more information, refer to the Prerequisites for EFS protection.