Overview
This document explains why AWS storage charges may occur when using Druva CloudRanger for AWS EC2 backups and how enabling Air-Gapped Backup redirects backup storage to Druva Cloud to avoid unexpected AWS storage costs.
Frequently Asked Questions
Why am I seeing AWS storage charges for my EC2 backups?
AWS storage charges occur when CloudRanger backups are stored as snapshots within your AWS account. If Air-Gapped Backup is not enabled, backup data remains in AWS-managed storage, and the associated storage costs are billed directly by AWS.
What caused the unexpected AWS charges in this case?
The Air-Gapped Backup feature was not enabled in the CloudRanger environment. As a result:
EC2 backups were stored in the customer's AWS account.
AWS snapshot storage costs accumulated over time.
Backup data was not being transferred to Druva Cloud's air-gapped storage.
What is Air-Gapped Backup?
Air-Gapped Backup is a CloudRanger feature that copies backup recovery points to Druva Cloud's secure, isolated storage environment. This provides:
Protection against ransomware and accidental deletion
Long-term retention in Druva-managed storage
Reduced dependence on AWS snapshot storage
Consumption tracking through Druva licensing and reporting
How can I enable Air-Gapped Backup in CloudRanger?
Step 1: Configure a Storage Rule
Navigate to Settings → Storage Rules and Encryption.
Click Add Storage Rule.
Select the desired Druva Cloud region (for example, AP Southeast 1 - Singapore).
Save the configuration.
Step 2: Authorize Encryption Keys
Open the Encryption tab.
Click Authorize.
Grant CloudRanger permission to access AWS Parameter Store for encryption key creation and management.
Step 3: Enable Air-Gapped Backup in Policies
Navigate to Policies.
Select the applicable backup policies.
Click Save and Continue.
Enable the Air Gap Backup option.
Enable Move all existing recovery points to air-gapped storage if historical backups should also be migrated.
Configure Retain Local Snapshot to the minimum required value (typically 1 day) to reduce AWS storage consumption during migration.
What happens to existing recovery points after enabling Air-Gapped Backup?
If the Move all existing recovery points to air-gapped storage option is enabled, CloudRanger begins migrating historical recovery points from AWS snapshot storage to Druva Cloud according to policy settings.
During migration, local snapshots may be temporarily retained based on the configured retention period.
How can I verify that backups are being stored in Druva Cloud?
You can verify successful air-gapped backups by:
Navigating to Monitor → Jobs in CloudRanger.
Confirming that backup jobs are completing successfully and transferring data to Druva Cloud.
Reviewing storage usage and credit consumption reports in:
Druva Console
CloudRanger Console