❗Important
The availability of this feature may be limited based on the license type, region, and other criteria. To access this feature, contact Support.
How does Druva handle the temporary resources created during backup?
How does Druva handle the temporary resources created during backup?
Druva leverages a fully ephemeral architecture to streamline data protection while minimizing infrastructure costs. A temporary Druva Quantum Bridge instance is provisioned in your environment, and the Druva agent on this instance mounts your target file system, enabling data scan and backup to cloud. Once the backup completes successfully, Druva automatically terminates the Druva Quantum Bridge instance, ensuring you aren't charged for unnecessary compute resources.
Are there hidden costs associated with the Amazon EFS backup solution?
Are there hidden costs associated with the Amazon EFS backup solution?
The standard ephemeral compute instances are created within your AWS environment while the backup job is active, which would incur standard consumption charges. Druva automatically deletes these temporary resources as soon as the backup job finishes to minimize costs. These resources are tagged for easy identification in your AWS Cost Management reports.
Why does Druva require both Inbound and Outbound traffic on Port 2049?
Why does Druva require both Inbound and Outbound traffic on Port 2049?
Druva simplifies the backup process by utilizing the same Security Group assigned to your Amazon EFS mount targets for the temporary EC2 worker instances it spawns. To ensure a successful backup or restore, the following communication must occur over Port 2049 (NFS):
Inbound: Allows the EFS mount target to accept connection requests from the Druva backup proxy.
Outbound: Allows the Druva backup proxy to initiate connection with the EFS file system and mount it.
📝 Note
By reusing the existing EFS Security Group, Druva ensures the necessary permissions to access data without requiring a separate, complex set of network rules.
What is Druva Quantum Bridge
What is Druva Quantum Bridge
To manage backup and restore operations, Druva dynamically orchestrates a temporary EC2 instance, the Druva Quantum Bridge, directly within your AWS environment. The Bridge acts as a secure intermediary, facilitating the data transfer between your Amazon Elastic File System (EFS) and Druva Cloud Storage.
This architecture ensures that data is processed efficiently while remaining within your controlled environment during the transit phase. For security, auditing, and cost tracking, each instance is automatically tagged with the following metadata:
Key | Value | Description |
Owner | Druva | Identifies the resource as managed by the Druva service. |
DruvaJobID | [Job ID] | Links the instance to a specific backup or restore task. |