Just recently upgraded to v12 and had been eyeing the immutable option for a while but put off enabling it until after upgrading to v12.
But to my surprise and consternation the option is now nowhere to be found.
I am running multiple Ubuntu 20.04 servers in multiple Scale Out Storage Clusters, all with fast cloning XFS and they are all "hardened".
The backup jobs are all forward incrementals with periodical fulls. All the backup copy jobs are GFS.
The option was just under the "Use fast cloning on XFS" and now it's not. Am I missing something?
/dennis
-
- Novice
- Posts: 9
- Liked: 4 times
- Joined: Oct 17, 2023 8:31 am
- Full Name: Dennis Lundkvist
- Contact:
-
- Product Manager
- Posts: 10110
- Liked: 2696 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Immutable option missing after update
Hi Dennis
To have a immutable repository in V12, you need to have added your repository with single use credentials (not root) as a new repository type "hardened". If you had used user "root" or a non-immutable Linux repository in v11, this repository wasn't upgraded to a "hardened repository" in V12.
You can migrate a Linux repository to a Hardened repository following this user guide:
https://helpcenter.veeam.com/docs/backu ... repository
If you had a hardened repository, but with user "root", then you have to follow our kb article:
https://www.veeam.com/kb4348
Best,
Fabian
To have a immutable repository in V12, you need to have added your repository with single use credentials (not root) as a new repository type "hardened". If you had used user "root" or a non-immutable Linux repository in v11, this repository wasn't upgraded to a "hardened repository" in V12.
You can migrate a Linux repository to a Hardened repository following this user guide:
https://helpcenter.veeam.com/docs/backu ... repository
If you had a hardened repository, but with user "root", then you have to follow our kb article:
https://www.veeam.com/kb4348
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Novice
- Posts: 9
- Liked: 4 times
- Joined: Oct 17, 2023 8:31 am
- Full Name: Dennis Lundkvist
- Contact:
Re: Immutable option missing after update
Ok, but since I surmised that the upgrade procedure would require updating the proxy/agents on the repos (they were all hardened) I set the credentials to a "normal" login and after the update was complete I "re-hardened" with a single-use credential.
And these are Ubuntu boxen, so root is disabled.
So not sure what's going on. Can I check if the repos are considered hardened?
And these are Ubuntu boxen, so root is disabled.
So not sure what's going on. Can I check if the repos are considered hardened?
-
- Novice
- Posts: 9
- Liked: 4 times
- Joined: Oct 17, 2023 8:31 am
- Full Name: Dennis Lundkvist
- Contact:
Re: Immutable option missing after update
Ok, I think I got it, that means my methodology of changing to normal credentials on the repos before the update is what put me in this situation. Sigh.
And just setting a single-use credential isn't going to convince anyone that it's actually a hardened repo. Dang.
And just setting a single-use credential isn't going to convince anyone that it's actually a hardened repo. Dang.
Who is online
Users browsing this forum: Amazon [Bot], Bing [Bot], chaesli, Google [Bot], Semrush [Bot] and 83 guests