❗ Important
File Level Search and File Level Restore are currently not supported directly from Druva Cloud. You will first have to restore the AMI snapshot and then proceed with File Level Search on the new snapshot.
Druva CloudRanger’s granular search feature can prove to be invaluable when recovering files that have been accidentally deleted or lost due to migration errors. You can use this functionality to recover files that may have been deleted, or to confirm whether a file exists, as part of compliance and governance.
📝 Note
File Indexing is an optional setting that can be enabled from your Account Settings page. The indexing settings will help define the accuracy of file search within backups. A higher indexing frequency will ensure accurate search results, while also impacting costs.
Before you Begin
The File Level Search feature is optional and will need to be enabled from your Account Settings page.
Log into your management console and navigate to the account on which you wish to enable file search.
Click the Settings icon on the left navigation menu and navigate to File Level Search Settings to enable File Indexing.
Enable File Indexing. You may also set the Backup Index Options to Index all backups on Druva CloudRanger.
📝 Note
File Level Search feature when enabled will create an S3 Bucket per user account to store the file system metadata of the target backups. The CloudFormation scripts may need to be updated to allow access to the S3 bucket.
Perform File Level Search
Step 1: Execute Backup Policy and Index for Search
Once File Search is enabled, you can execute a backup policy and then choose to Index specific backups for File Search.
Log into your management console, navigate to Resources and select the Backups tab.
Select the backup to be indexed and click Index for search.
📝 Note
The file icon remains grey prior to indexing of a backup. Once the backup is complete and indexed to make it searchable for files, the file icon changes to blue.
3. Click the blue file icon to be redirected to the File Search page.
Druva CloudRanger automatically enters the snapshot selected into the In Backups textbox. You can specify other search criteria, as relevant before initiating search.
Step 2: Browsable Indexed Snapshots
Navigate to File Search from the left navigation menu.
Specify the search criteria such as File Type, File Size, Date modified, or initiate search within a specific Resource or Backup.
Click Search.
Step 3: Retrieve File from Search Results
Once the target file(s) have been identified, the Search Results displays the files within the backup versions that match the criteria specified.
Select the file and click Retrieve files, and then click Start File Retrieval.
Alternatively, click the link under Versions to download the files.
This initiates the download of the selected file to the user’s desktop.
Frequently Asked Questions
What are the minimum Security Group rules (inbound and outbound) required for the FLS index instances to function?
What are the minimum Security Group rules (inbound and outbound) required for the FLS index instances to function?
Ensure that the Security Groups do not block access to the S3 Buckets. You can locate the S3 Bucket created for FLS within the Account Settings for each AWS Workloads (CloudRanger) account under the FLS Network Settings section.
How are the Security Groups selected for the FLS Index job?
How are the Security Groups selected for the FLS Index job?
AWS Workloads (CloudRanger) uses the run-instances AWS command to run the indexer. If a Subnet is selected under the FLS Network Settings, then the VPC corresponding to this Subnet is chosen to launch the Indexer Instance in. The Security Groups are then selected in one of the following ways:
If a Security Group within the selected VPC has the tag key ‘druva_cr_fls_sg’, then these are attached to a NetworkInterface for the run-instances call.
If there are no Security Groups with this tag, the run-instances AWS command will attempt to use the default Security Group, if applicable.