Multiple server, one or many repositories?

[sughenji]

Hi! I’ve read this:

B2 - multiple hosts to single repository bucket?

Any key gives full access to the repo, so it’s not a form of ACL in that sense @x572b - two points to consider regarding backing up to the same repo: When pruning that repo from one of the machines, no machine will be able to back up to that until the prune is finished (which can be time consuming with B2) If you ever need to recover all the data of one machine, and it’s infeasible to mount over fuse, then keep in mind that you’d have to download the archive of the whole bucket…

My understanding is that it is possible to revoke access for a specific client (since every client uses a different key), but my concern is a bit different: I don’t want that server1 can browse/restore data which belongs to a server2.

Is this leading to one repository for each server?

Of course, this way, I would’t take any advantage of deduplication among different servers.

Thank you!

[rawtaz]

@sughenji

I don’t want that server1 can browse/restore data which belongs to a server2. Is this leading to one repository for each server?

Yes, if you have two clients backing up to the same repository, then they will be able to read each other’s data. If you want to prevent them from doing so, you need to put them in separate repositories.