Compatibility between Encrypted and Unencrypted Volumes

The Volume contains a flag in the header of the first block which indicates whether the Volume is encrypted or not. This status is represented by the VolEncrypted field in the Catalog.

Volumes initialized using Bacula Enterprise Edition version 14.0 or earlier, characterized by the BB02 label format, can be read and appended in version 16 and later.

Volumes initialized or appended using version 16.0 and later, characterized by the BB03 label format, cannot be read with version 14.0 or prior versions.

Note

Bacula does not mix encrypted and unencrypted data inside the same Volume.

Volumes that have been labeled or relabeled on a Device with the directive Volume Encryption are classified as encrypted. Other Volumes, including those initialized with the BB02 format using version 14.0 or earlier, are regarded as unencrypted.

See also

Go back to:

• What Is Encrypted

Go to:

• New Storage Daemon Directives

• key-manager Script and Using Master Key

• Best Practices

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.