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 resolve this warning and ensure complete data protection, implement one of the following solutions:

  • Adjust AWS Lifecycle Policies: Review and modify your Amazon S3 Lifecycle configurations to ensure that objects remain in a supported tier—such as Standard, Intelligent-Tiering, or Standard-IA—until the scheduled Druva backup job has completed.

  • Restore Archived Objects: If the skipped Glacier objects must be backed up, initiate an AWS restoration process to move them back to the S3 Standard or S3 Standard-IA tier before the Druva backup job runs.

Did this answer your question?