Wasabi Veeam Object Lock Integration FAQs

Wasabi Veeam Object Lock Integration FAQ

If you are going to leverage immutable Veeam backups, review Object Lock: Enabling.

Enabling bucket versioning is not a proper configuration for immutable Veeam backups and can cause problems. If you are simply going to use regular Veeam backups with Wasabi buckets, bucket versioning is not required.

Below are frequently asked questions about Veeam's Object Lock integration with Wasabi.

How do I make my Veeam backup data immutable on Wasabi Cloud storage?

For more information, review Veeam Object Lock Integration Guide.

Can I convert existing backups stored on Wasabi to be immutable?

Object Lock can only be enabled during bucket creation.

Can I convert my existing Veeam Backup Repository for Wasabi to immutable?

This is not possible. A new Backup Repository must be made.

What happens if I made a mistake and locked a file for longer than I wanted?

The specific objects are locked until the RetainUntilDate has passed. Once the object is locked, it is unable to be modified to a previous date, altered, or deleted until the retention policy has expired.

Can I use object lock on a bucket that does not have it enabled?

Object lock can only be utilized on a bucket that was created with object lock enabled.

Can I store data without object lock enabled in a bucket with object lock enabled?

Yes. You can specify the objects that are locked within a bucket with object lock enabled.

Can I delete data without object lock enabled from a bucket with object lock enabled?

Yes. You can delete an object as long as object lock is not enabled for it and no legal hold is placed on it.

How can I tell if an object has object lock enabled or not, or when the lock expires?

In the Wasabi Console, navigate to your object, select the versioning icon (icon with the folder and clock), then select your object. You should be able to see the retention details on the bottom of the File Details panel.

Why does my bucket show Versioning enabled? / Why must I have versioning enabled to make use of object lock?

Object lock requires versioning to be enabled because the Object Lock feature is placed on a specific version of an object. Wasabi keeps track of these versions and does not allow modification/deletion of the object version. However, you are able to place and delete different versions of the object that are not locked, or have multiple versions of an object that are all locked.

How can I compare or validate the settings for my Veeam backup job using the Wasabi Management Console/Wasabi Explorer/S3 Browser?

You can view the retention details on objects using the Wasabi Console. For more detail, refer to question #8.

With the S3 Browser, you are able to select your file and click the Headers tab to see the Retention details.

Using Wasabi Explorer, you can select your file, then select Set HTTP Headers. This will open a window that enables you to see the headers of an object.

If I make a change in the object lock settings (through the API or via the Console) how does that effect my Veeam backup jobs?

Wasabi does not recommend manually modifying the object lock settings for a Veeam Backup. Veeam manages the immutability duration in the VBR Application. Any changes can result in unpredictable Veeam system behavior and data loss.

Does the default object lock setting for a bucket mean I do not have to set anything on the Veeam backup jobs? 

Using bucket default object lock settings can result in unpredictable data loss.

For more information, review Veeam Considerations and Limitations for Immutability.

Can I use Veeam NAS/File Share Backup with Immutability?

Only Veeam version 12 supports Immutability for NAS/File Share Backup. Previous versions do not support Immutability for NAS/File Share Backup.

For more information, review Veeam Considerations and Limitations for Immutability.

Can I use Wasabi Ball with the object lock feature?

At this time, the Wasabi Ball does not support object locking.