#1 Global Leader in Data Resilience

Linux Hardened Repository Unable to Update Immutability or Remove Restore Points due to SGID

KB ID: 4631
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2024-06-21
Last Modified: 2024-06-21
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Article Applicability

The errors in this article may occur for other reasons, this article is specifically relevant to a situation in which these errors occur because the folder where the backup files are stored has an SGID (Set-Group ID) configured.

Example:

[backupsvc@rhel9]$ ls -l
total 1
drwxr-sr-x. 2 backupsvc backupsvc    1 Jan 1 00:00  repo

Challenge

A job targetting a Hardened Linux Repository (Immutable) fails with an error about being unable to remove restore points or update immutability (examples below).

  • Failed to delete file '/path/to/storage.vbk': Operation not permitted
    
  • Failed to perform setting immutability for backup Error: Agent: Failed to process method
    
  • Failed to delete '.vbk' per retention policy
    
  • Error: boost::filesystem::remove: Operation not permitted: "/path/to/restorepoint.vib" Agent failed to process method {FileSystem.FileRemove}.
    

Cause

This problem is caused by the SGID bit set on the backup directory.

Due to the SGID bit, all files created within this directory inherit the directory's group ownership. This conflicts with the verification routine in VBR that ensures the .veeam.lock file belongs to the root user and root group.

As a result of this conflict, errors arise during the processing of the .veeam.lock file.

Solution

In the command examples below, the placeholder '/path/to/repository/' is used to represent the path to the root folder that was specified when the repository was created in Veeam Backup & Replication.  You can confirm the path needed by checking the Path column listed for the repository within the Backup Repositories list in the Veeam Backup & Replication Console.

  1. Open the Backup Infrastructure view.
  2. In the inventory pane, select the Backup Repositories node.

To resolve this issue, the Linux Administrator must remove the SGID bit from the backup directory and rerun the job to force new .veeam.lock files to be created.

  1. Disable all jobs targetting the affected Linux repository.
  2. Connect to the Linux server that hosts the Repository.
  3. Remove the SGID from the backup directory using this command:
sudo chmod g-s /path/to/repository/
  1. Enable all disabled jobs from Step 1 and rerun them.

    With SGID no longer set for the backup folder, new .veeam.lock files will be created with the correct user (root) during the next job run.

If the issue continues after you complete the steps above, please collect logs and create a Veeam Support case.
While rare, the existing .veeam.local files may need to be removed, a process that requires the immutability attribute to be removed from each .veeam.lock file.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.