One repo to rule them all?

Getting Help
1

Hi all,

I’ve been using restic for a few years to backup our infrastructure. The way I’ve been doing this is by having a single S3 bucket in which I create a restic repo (dir in bucket) for each app (k8s pod).

In the restic documentation, “Working with repositories”, it seems to hint at a single repo for multiple boxes (or pods?).

The way I have it setup allows me to restore an entire snapshot without having to filter on host or specify a path. It makes it easy to automate restores and simplifies restores in general by simply restoring an entire snapshot.

I was wondering what your thoughts were on the matter and what solution you have. I am trying to way the pros and cons.

Thanks for your help!
Ed

2

IMHO, the main advantage of using a single repo is that you get deduplication across multiple hosts. Other that I would say it doesn’t really matter.

2 Likes
3

From a reliability perspective single repositories for each app is better than using one single repository. Also keep in mind that all clients that use the same backup repository can read everything in that repository.

1 Like
4

@nicnab Thanks a lot for your reply. I had not thought about deduplication.

2 Likes
5

@MichaelEischer Thanks for your reply. It seems I made the right call in using a restic repo per backup.

Thank you all who work on restic for this great piece of software!

2 Likes