Linux Repository for multiple customers

[Moebius]

Hello,

I am working on a project where a cloud service provider would host a Linux server + repository to hold offsite backup copies for several small customers.
Each customer would have his VBR server installed in his premises and register the same Linux server and repository over the internet.
The Linux server would of course provide different partitions to keep each customer's data separate from the others.

The first test "customer" setup worked fine and the backups went quick and easy. This "customer" has root privileges on the Linux server so it also did the deployment of the data mover on that server.

The question is, is it possible for other VBR servers of subsequent customers to log into that Linux server with reduced (non root) privileges, so that they have only R/W rights on the partition that they will be assigned?

(My knowledge of the Linux world is pretty limited, so apologies for any nonsenses.)

[Egor Yakovlev]

Hi Lucio,

Sharing a server between customers in a direct way(aka VBR > Add Linux Repository) is a very bad idea in many shapes and forms. Veeam puts a transport service on top of a linux server to interract with it, thus customers will fight for access to it. If one customer clicks to remove Data Mover, others will lose connectivity.

You need to use Veeam Cloud Connect to safely share service provider resources across multiple customer infrastructures in a secure, isolated, scalable way.

/Thanks!

[StanoSedliak]

Hi Egor,

could you please write some negative experience or why its bad idea to user one linux repo for more VBR in direct way?
I understand the problem if you remove it from one VBR that other lose connection but are there any other problems?
We tested it in our PoC and it was working.

Thank you!

Br, Stano

[bct44]

Hello,

Becareful of load management when sharing a repo between many VBRs (split brain). I think it's not possible to have multiple user for veeam repo, even if Veeam Transport is running as a root. Some forks process will run on basic user used by Veeam. I'm not sure but it could be possible your customers could access files to other lv/repo through the files menu.

The best solution for this case will be Veeam Transport running on a container so you can run many on the server but i think it's not supported.

[Mildur]

I'm not sure but it could be possible your customers could access files to other lv/repo through the files menu.

Possible. Repository server should never be shared between different customers
They may be encrypted, but the file name of the backup chains and Jobs are still readable.

Best,
Fabian