Wasabi Veeam Object Lock Integration FAQ

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

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

Please see the Veeam Object Lock Integration Guide.

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

Object Lock can only be enabled during bucket creation.

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

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

4. 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.

5. 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.

6. Can I store non-Object Lock data in an object lock enabled bucket?

Yes, you can specify the objects which are locked within an Object Lock enabled bucket.

7. Can I delete non-object lock data from an object lock bucket?

Yes, you can delete an object as long as there is no object lock, and no legal hold on it.

8. How can I tell if an object is locked or not, or when the lock expires?

In the Wasabi Console, you can 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 pane.

9. 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 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 which are not locked, or have multiple versions of an object which are all locked.

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

You can view the retention details on objects using the Wasabi Console, 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 the button "Set HTTP Headers", and this will pop open a window that allows you to see the headers of an object.

11. If I make a change in the object locking settings (via the API or via the Console) how does that affect my Veeam backup jobs?

It is not recommended to modify the Object Locking settings manually 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.

12. 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.

Please refer to the Veeam Considerations and Limitations for Immutability.

13. 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.

Please refer to the Veeam Considerations and Limitations for Immutability.

14. Can I use Wasabi Ball with Object Lock?

The Wasabi Ball does not support Object Lock at this time.




Have more questions? Submit a request