We have received some reports of clients enabling S3 Bucket settings. Due to the design of Incremental Backups in JetBackup 5, you should never enable any of the below bucket settings. These settings are NOT SUPPORTED and will likely cause problems with your backups and/or restores.
Bucket Settings - Not Supported:
- Bucket Versioning - May lead to excess storage use. Only usable with specific object lock configuration. See Note Below.
- Object Lock: Governance Mode - May lead to objects being retained even after your schedule retention or another backup TTL is exceeded, resulting in excess storage use. Governance Mode is not supported with the Object Lock Support in v5.4.2+, See Note Below.
- Object Lifecycle - May lead to BACKUP CORRUPTION - JetBackup manages the files objects that should exist in your backup. Use of this setting is EXTREMELY DANGEROUS and should not be enabled. "No Such Key" (
Error: The specified key does not exist. (NoSuchKey)) errors while restoring backups are normally attributed to this bucket setting.
*Note: Object Lock: Compliance Mode is supported in v5.4.2+. See Changelogs and our documentation for more information on this feature.
Bucket Settings - Supported with Specific Configuration:
- Object Lock (Compliance Mode) + Bucket Versioning: Only supported in v5.4.2+ with Object Lock enabled on the JB5 Destination upon creation. Object Lock cannot be enabled for existing destinations, please create a new bucket in Object Lock - Compliance Mode by referring to your storage providers' documentation. For more information on this feature, see the JetBackup 5 Immutable Backups documentation.
If you have a particular S3 Bucket Setting you'd like to see supported, please submit a feature request so we can gauge the demand and prioritize on our roadmap accordingly:
https://request.jetbackup.com/
Before enabling any Bucket setting not listed above, please contact us if you're not sure whether it can be used with JetBackup by opening a ticket.
