Fix Repository time shift detected: Immutability flag cannot be set

In this article, we shall discuss how to fix Repository time shift detected: Immutability flag cannot be set. This warning occurs when a time shift is detected in the Hardened Repository regardless of the deployment type used. This is a safeguard against immutability manipulation that can also be triggered by intentional time changes. Please see how to deploy and integrate VHR with VBR, and how to Disable Hardware Acceleration in Browsers and Windows.

Also, extended power-offs, stopping the VeeamTransport service, or reusing a repository with an existing timeLog file also trigger this behavior.

Here is how to Fix missing path and delete a Veeam Backup Repository, How to detect who disabled a user in Active Directory, and “Best Storage for Veeam: Comparing OOTBI by ObjectFirst to VHR“.

Jobs Completed with Warning

As you can see below, the following job completed with warning.

In order to determine the root cause, we will have to take a look at the logs. In my case, I will be using the Windows Event Viewer. As you can see from the error below.

A problem occurred during setting the immutable flag: repository time shift detected, immutability flag cannot be set. Please refer to KB4482 for more details.

You can also, see that it was reported with warning here. This was immediately shown on the Veeam ONE dashboard. Please, see Install Veeam ONE and Add VBR: Fix failed to connect to VBR, and Install Splunk and Veeam App on Windows Server to monitor VBR.

Resolution: Fix Repository time shift detected

If you are using the Veeam Hardened Repository ISO, this solution is very easy to implement. All you need to do is connect to the VHR and in the in the Configurator Main Menu, use the Reset time lock option as shown below.

As you can see, the “TimeShift detection reset” was successful.

You can also take a look at the time settings as shown below to see if it is correct.

Also, see How to Disable Open File Security Warnings on Windows, and how to fix “The action cannot be completed because the folder or file is open in another program: Determine where a file is open in Windows“.

Optional: Apply Updates

This steps has nothing with fixing the ‘Repository time shift detected: Immutability flag cannot be set’. I just want to perform an update.

Now that you have nothing to do, please logout.

Rerun Backup Job: Immutability flag cannot be set Eliminated

We are running the job once more.

As you can see, we have rerun the backup job and it completed successfully.

I hope you found this guide very useful on how to fix Repository time shift detected: Immutability flag cannot be set. Please feel free to leave a comment below.