I cut separate repo instances on their own volumes without issue so that should work okay. Issue could be cert config or ports. I’d double check both to start. Do you have any of the logging snips handy?>

Thanks - yes I’m trying to find the log for a rescan of host discovery. Not only the backup job fails.

The server is red under managed servers and also backup repository is red.

Hi @Edy,

If i understand you correctly, you have 1 Immutable Backup Repository on Ubuntu 22.04.
You then have Client A with his own VBR and Client B with his own VBR. Is that correct?

If that is correct, you might run into the issue that 1x Linux Hardened repository cannot be shared between multiple VBR servers.

“You must add the Linux machine to the Veeam Backup & Replication console as a managed server. The hardened repository cannot be shared between different Veeam Backup & Replication servers.”
- https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_limitations.html?ver=120

If i understand you correctly, you have 1 Immutable Backup Repository on Ubuntu 22.04.
You then have Client A with his own VBR and Client B with his own VBR. Is that correct?

Hi @gregersen 

Yes this is correct.

I added first on both VBR server the Linux machine as a managed server. After that the mount points (different partition) to a hardened repository.

The hardened repository cannot be shared between different Veeam Backup & Replication servers.

I believe that is not the case in my scenario. I’m not sharing the repository.

@Edy

It is not sharing the individual mounts in your Ubuntu I’m trying to look at. It is sharing the Ubuntu server itself with 2x VBR servers, which I think is the problem. 

Did you add the hardened repository to both VBR under managed server? And did you use the option for “single use credentials”?

If so, I would think that, that could be the problem. To my knowledge Veeam uses certificate instead of user/password in that scenario and that is why when you add the Linux hardened repository to another VBR it messes up the already created credential or somehow overwrites it. I think that is why you get that error with certificate. But I could be wrong, this is just a thought.

Hi @gregersen 

Many thanks for your inputs and thoughts. It’s very helpful.

Did you add the hardened repository to both VBR under managed server? And did you use the option for “single use credentials”?

Yes I did,

I think you are right about the certificate and this setup cannot work. I also believe the second VBR servers messed up the config for the first VBR server.

I also posted in the Veeam subreddit and someone mentioned and here is the answer

No. Not in the way you have it setup. A repository can only be added to a single VBR server. The only way it would work, is if its not added as a hardened repository. You can have SMB or NFS shares presented off that Ubuntu server, and then shares added to the individual VBR Servers, however, you cannot use immutability in that case.

You could create a cloud connect environment to point your clients to and the hardened repository would be in your "Service Provider" VBR server and their backups would point to that. Not sure if that's feasible or not for you though...probably easier to just create a dedicated ubuntu repository for Client B.

Cloud connect is indeed a possibility for us. Not sure what the pros and cons are. We use cloud connect for veeam agent clients.

Hi @Edy 

Just glad that you could use my input.

I also posted in the Veeam subreddit and someone mentioned and here is the answer

Yeah, I saw that in the subreddit and good to have others opinions as well. 

Cloud connect is indeed a possibility for us. Not sure what the pros and cons are. We use cloud connect for veeam agent clients.

I have no experience myself with Cloud Connect, but i would look into the documentation here, for pros and cons comparing it with the setup you want to run
https://helpcenter.veeam.com/docs/backup/cloud/cloud_overview.html?ver=120
And also VCSP best practices:
https://bp.veeam.com/sp/