Linux hardened repository settings - Changes from V11 to V12

[KaptenP]

Hello

In Veeam V11 when creating a linux repo where we didn't want immutable backups/hardened repo to be activated right away, we chose Direct Attached Storage and after that Linux as the type of server to use as a backup repository. We also unticked the boxes for "Use fast cloning on XFS volumes" and "Make recent backups immutable for X days".

Now in V12 you have to chose between "Linux" or "Linux (Hardened repository)" when choosing your operating system that will be used as a backup repository.
We pick Linux hardened repo as this repo will be used as an hardened repo in the future, but in V12 there is no check box next to "Make recent backups immutable for: X days" as it was before.
Which of the following will setting 0 days on Make recent backups immutable for result in?
- 0 days equals no backups being immutable, the same as unticking the box next to it in V11
- 0 days equals backups being immutable forever
Or do we have to create a non-hardened Linux repo in V12 for backups to not be immutable?

The goal is to have no backups being immutable when setting it up and later on to activate it.

Hope this makes sense - Thanks in advance!

[Mildur]

Hello Per

If you don't want to use immutability, use it as a Linux repository.
When you are ready to use immutability, follow this user guide to migrate your Linux repository to a hardened repository.
https://helpcenter.veeam.com/docs/backu ... repository

Please also note, hardened repository has a minimum immutability period of 7 days. You cannot configure 0.
And the new repository type "Hardened" was introduced to remove the option to uncheck "immutability" in the repository properties.

We also unticked the boxes for "Use fast cloning on XFS volumes"

May I ask, why did you have unchecked that option? Without it, you cannot leverage our Fast Clone technology which gives you space less and faster synthetic full backups. A lot of other operations also will benefit from using fast cloning.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[KaptenP]

Hi Fabian

Thank you for the information. Now we know how to proceed

In the cases when we are running GFS or immutable backups we have Fast Clone ticked for these particular repositories.
We were unsure how Veeam would handle a repository with fast clone activated when we run forever forward incremental backups and do not make use of the fast clone technology.
It felt like the safest alternative to have it unticked in these cases.
Also due to previous problems with ReFS where the merge process took longer and longer time after a while when more data block pointers existed and it got fragmented.