Articles on: Object storage

LEVIIA Configuration for Immutability with VEEAM Backup and Replication

1) INTRODUCTION TO OBJECT LOCKING
Object locking prevents objects from being deleted or replaced for a specified period of time.
Your objects will then be stored using a WORM model (write-one-read-many).

2) BENEFITS OF OBJECT LOCKING
Object locking has many benefits:
For data integrity reasons.
For regulatory compliance reasons: if you need to store data in WORM format or for legal proceedings.
To add an extra layer of protection against modification and deletion of objects.
It is the best defense against ransomware attacks: cybercriminals attack backups and archives but they will be powerless against an object lock in compliance mode (explained below).
Avoid accidental or intentional deletion of data.

3) VEEAM SPECIFIC SETTING FOR IMMUABILITY

In order to benefit from immutability on your bucket with VEEAM software, you must configure it in a specific way. Indeed, it is VEEAM that will determine the retention period directly in the backup job.

If you enable a duration in the LEVIIA dashboard, VEEAM will not be able to determine the retention itself and will therefore display this error message :

VEEAM lock error

In order to benefit from immutable backup via VEEAM, you must not select a default retention period in your bucket.

Here is the correct configuration to perform an immutable backup with VEEAM software.

Leviia bucket configuration for VEEAM immutability

You can therefore configure your S3 LEVIIA - VEEAM repository according to your needs.

Updated on: 10/10/2024

Was this article helpful?

Share your feedback

Cancel

Thank you!