Does the backup process of my EBS volumes depend on the encryption state of the source volume?
Does the backup process of my EBS volumes depend on the encryption state of the source volume?
No, Druva backs up EBS volumes regardless of their encryption state. The backup process itself does not depend on whether the source volume is encrypted or unencrypted.
Are encrypted EBS volumes backed up as encrypted snapshots, and unencrypted ones as unencrypted snapshots?
Are encrypted EBS volumes backed up as encrypted snapshots, and unencrypted ones as unencrypted snapshots?
Yes. Druva uses AWS-native EBS snapshots that retain the encryption state of their source volumes. Encrypted volumes are backed up as encrypted snapshots, while unencrypted source volumes result in unencrypted snapshots.
If an EBS volume is encrypted using a Customer Managed Key (CMK), does Druva preserve that encryption in the snapshot?
If an EBS volume is encrypted using a Customer Managed Key (CMK), does Druva preserve that encryption in the snapshot?
Yes. When the source EBS volume is encrypted with a CMK, Druva preserves the same encryption and uses the same CMK during snapshot creation.
Is there a backup configuration setting to enforce encrypted snapshots or use of a specific CMK?
Is there a backup configuration setting to enforce encrypted snapshots or use of a specific CMK?
No. Druva does not offer options to enforce encryption or specify a CMK during snapshot creation. The encryption state is inherited from the source volume.
Can Druva enable or enforce encryption for snapshots if the source volume is unencrypted?
Can Druva enable or enforce encryption for snapshots if the source volume is unencrypted?
No. If the source EBS volume is unencrypted, Druva will create unencrypted snapshots. Druva does not modify or enforce encryption during the backup process.