How to know immutability applied

[matteu]

Hello,

I would like to know how can I know if immutability is applied for NAS backup job without trying to delete and lost data if it's not on linux hardened repository...

I had several NAS backup job from V11 and I guess I need to perform new FULL with CTRL + right click on the job to have immutability applied right ?

Thanks for your answer

[chris.childerhose]

If you have just pointed them to an Immutable repository, I would suggest running a full backup if it is not on a hardened repository not sure how it would be immutable anyway.

[matteu]

I mean :
There is no method to know if this is immutable without trying to delete it ?

Then, there is no process to migrate from v11 backup job nas to v12 and add immutability without performing new job right ?

[chris.childerhose]

Yes, that is correct. You need to move to the immutable repository and run a full backup.

[matteu]

Thanks for the migration path.

If I nestor know on new customer if the backup job is illutable or not, I need to test to remove a rétention point to know it ?
No information is in the database ?

[chris.childerhose]

If you need to test, you can go to the Disk section and try to delete a restore point. Keep in mind if it is not immutable, it will be gone. If it is immutable, you will get an error about deleting it due to immutability.

[Net Runner]

Depends on what you are using as immutable storage. If it is an AWS S3 immutable storage, you can try to use AWS CLI and command like s3:GetBucketObjectLockConfiguration on the bucket to get the ObjectLock config. If it is any kind of Linux + XFS you can check backup files flags under the root user and determine whether they are WORM or not.

[matteu]

@Chris : thanks to confirm what I was thinking

@NetRunner : Unfortunately it's on Hardened linux repository and it's vblob for NAS backup and not vib or vbk file... I don't know really what file will be tag as "immutable"

[EShutov]

NAS Backup protects the whole backup with immutability. While there are a few exceptions, the general rule is that everything in the "data" and "metabackup" folders should be immutable.
The immutability period is not extended for files that are no longer required in the backup. When the immutability period expires for these files, they are automatically removed during the next backup run.

[matteu]

@Eshutov thanks to point on the repository content I have to check Data + metabackup !

[matteu]

Finally, I test to remove data from the NAS job and data are protected.
That means when you create job from V11 and target hardening repository, there is no need to create new backup chain after V12 migration (or maybe Veeam did it itself)