Interoperability between Encrypted and Unencrypted Volumes

The volume has a flag in the header of the first block which indicated whether the volume is encrypted or not. The field VolEncrypted in the Catalog reflects this state.

Note

Bacula does not mix encrypted and unencrypted data inside a volume.

Volumes that have been labeled or re-labeled on a Device with the directive VolumeEncryption are encrypted volumes. Other volumes, including volumes which have been initialized with a BB02 format using version 14.0 or older, are seen as unencrypted volumes.

You can change the value of the directive VolumeEncryption to Yes or Strong at any time. Volumes that are not encrypted can be read on this device but cannot be appended until they are recycled. Switching between Yes and Strong is fine, because the difference is only in the unencrypted label and not in the blocks that come after the label.

Changing the value of the directive back to No will deactivate the encryption and make all encrypted volumes unreadable and useless on this device until they are recycled.

See also

Go back to:

• New Storage Daemon Directives

• Encryption Command

• Compatibility between Volumes Using BB02 and BB03 Formats

Go to:

• Using Master Key

• Master Key Implementation

• key-manager.conf File Format

• Backup Your Keys

• What Is Encrypted

Go back to the Storage Daemon Data Encryption chapter.

Go back to the main Data Encryption chapter.

Go back to the main Advanced Features Usage page.