Skip to main content

S3 Backup Fails with "Files missed/skipped from backup"

S3 Backup Fails with "Files missed/skipped from backup"

Problem Description

Druva CloudRanger S3 backup jobs finish with a status of "Completed with Errors" and display the following message:

Files missed/skipped from backup

This issue occurs even if no exclusion rules are active in the backup policy. It specifically affects Amazon S3 buckets containing objects that have transitioned to archival storage tiers.

Error Details:

  • Status: Completed with Errors

  • Error Code: 4294967666

Cause

  • The skipped files reside in the Amazon S3 Glacier storage class.

  • Druva AWS Workloads does not support the direct backup of objects stored in S3 Glacier. Because Glacier objects are archived and require a retrieval process to become accessible, the backup agent automatically bypasses them. Any files transitioned to Glacier via AWS Lifecycle policies prior to the backup window will be skipped.

Traceback / Logs

2026-05-04 02:07:34 | Starting backup operation 2026-05-04 02:07:36 | Starting data upload for fset: '<REDACTED_FILESET>' 2026-05-04 02:07:38 | Finished data upload for fset: '<REDACTED_FILESET>' 2026-05-04 02:07:40 | Files missed/skipped from backup 2026-05-04 02:07:41 | Finishing backup operation with status: Completed with errors  File = processed/<REDACTED_FILENAME_01>.csv, Error = Skipping object with unsupported storage class [GLACIER] File = processed/<REDACTED_FILENAME_02>.csv, Error = Skipping object with unsupported storage class [GLACIER] File = processed/<REDACTED_FILENAME_03>.csv, Error = Skipping object with unsupported storage class [GLACIER]

Resolution

To ensure all objects are included in the backup, use one of the following approaches:

  • Review AWS Lifecycle Policies: Update your Amazon S3 Lifecycle configuration to ensure objects remain in a supported storage class, such as S3 Standard, S3 Intelligent-Tiering, or S3 Standard-IA, until the Druva backup has completed.

  • Restore Archived Objects: If archived (Glacier) objects need to be backed up, restore them to an accessible state before running the Druva backup. Refer to the AWS documentation for detailed instructions: Restoring an archived object - Amazon Simple Storage Service

Note: Consult your AWS administrator before making changes to lifecycle policies or restoring archived objects.

Did this answer your question?