ARCHIVED - Wasabi Object Lock

Refer to: WASABI CLOUD STORAGE (Console) > Product Guide (Advanced Usage) > Buckets and Objects > Immutability: Compliance and Object Locking https://docs.wasabi.com/docs/immutability-compliance-and-object-locking Refer to: WASABI CLOUD STORAGE (Console) > Product Guide (Advanced Usage) > Buckets and Objects > Object Locking https://docs.wasabi.com/docs/object-locking Refer to: WASABI CLOUD STORAGE (Console) > Product Guide (Advanced Usage) > Buckets Settings > Object Locking https://docs.wasabi.com/docs/object-locking-enable

Wasabi Object Locking is a feature that prohibits modification or deletion of specific object versions during a configured retention period. Object locking is a method that can be used to achieve WORM or a form of airgapped storage . The retention policy can be specified on each object placed into a bucket. Additionally, bucket level settings can be applied so that new objects placed in a bucket will have the default settings applied. Versioning must be enabled on a bucket with object locking enabled.

There are two modes of object locking:

• Governance Mode will lock the object for the configured retention policy. However, the root user or any user with the IAM permission “s3:BypassGovernanceRetention” can bypass the retention policy and modify or delete files.

• Compliance Mode will lock the object for the configured retention policy, and no user can modify or delete the object until that retention policy has passed.

Legal Hold

Legal hold is an additional locking mechanism that can be placed on an object in a bucket with object locking enabled. A legal hold will prevent the modification or deletion of an object indefinitely until the legal hold has been removed. A legal hold overrides both Governance Mode and Compliance Mode retention policies, but it does not remove them. After removing the legal hold, the existing Governance Mode or Compliance Mode retention policy will still be in effect.

Enabling Object Locking

Object locking must be enabled on a bucket before you can use the functionality. Enabling object locking can only be done during bucket creation. You are unable to enable object locking on existing buckets of data.

Creating a bucket that has object locking enabled will automatically disable the use of Wasabi Bucket Lock (Wasabi Compliance). For more information, review How to create an Object Lock enabled bucket?

Bucket Level Default Configuration

Bucket level configuration for object locking allows you to automatically configure a retention mode and retention time in days or years for new objects placed into a bucket. This optional configuration is disabled by default. Configuring object locking on a bucket does not effect objects that are already in the bucket. When an object is uploaded without an object locking configuration, the object will have the bucket level defaults applied to it. Changing or disabling object locking default settings on the bucket will not affect any existing objects in a bucket. For more information, review Using Bucket Level Default Settings for Object Lock .

Viewing Object Locking Status on a File

For more detail, review How to verify your objects are locked with Wasabi Object Lock?

Determining Wasabi Object Locking versus Wasabi Compliance

For more detail, review How can I tell if a bucket is using Wasabi Object Lock or Wasabi Compliance?

Wasabi Ball Support

For more detail, review Can I use Wasabi Ball with Object Lock?

Third-Party Integrations

• Arcserve UDP

• Arcserve Cloud Console  

• Arq Backup

• Atempo Miria

• Atempo Tina

• BackupAssist Classic

• BackupAssist ER

• Catalogic DPX

• Comet Enterprise Backup

• Commvault

• HornetSecurity VM Backup (Altaro VM Backup)

• HYCU

• Kasten K10

• Marquis Project Parking

• Marquis Workspace Backup

• MSP360  

• Nakivo

• SEP sesam

• Veeam Object Lock Integration

• Veritas NetBackup

• Veritas Backup Exec

• Zerto