Problem description
Backup jobs in Druva CloudRanger may fail during their final stages when the Index all Backups feature is enabled within the global Account Settings.
While the actual backup snapshots are successfully created and stored on Amazon S3, the subsequent indexing phase required for File-Level Search (FLS) triggers a failure.
This task automation forces CloudRanger to attempt to catalog file systems across all volumes, including those that are unsupported, leading to an overall backup task failure status.
Cause
The FLS Indexing Job fails because the target instance being backed up is an AWS Marketplace Instance. Druva CloudRanger does not currently support File-Level Search (FLS) indexing for instances launched directly from the AWS Marketplace.
Resolution
To resolve these failures and ensure your automated backup schedules complete successfully, you must disable the global automatic indexing policy.
Recommended Action: Disable Global Indexing
Log into your Druva CloudRanger Management Console.
Navigate to Account Settings.
Locate the Index all Backups checkbox option.
Uncheck the box to disable the automated global indexing process.
Click Save.
š Note: Disabling this setting stops CloudRanger from automatically attempting to index all backups account-wide. Since File-Level Search is an optional metadata feature, disabling it does not impact your ability to perform standard File-Level Restores (FLR) or snapshot recoveries when needed.
Workaround for Non-Marketplace Instances
If your workflow still requires File-Level Search for standard (non-marketplace) instances within the same account, you can initiate indexing manually:
Navigate to the specific backup snapshot of a supported instance.
Manually trigger the indexing process on a per-backup basis.
This allows you to leverage search functionality for supported environments without causing failures on marketplace-derived resources.
Verification
To verify that the configuration change successfully resolved the issue:
Trigger an on-demand backup or wait for the next scheduled backup cycle of the affected AWS Marketplace instance.
Confirm that the backup job transitions completely to a Success or Completed state without triggering post-backup FLS indexing errors.