librelist archives

« back to archive

one global repository or one repository per host

one global repository or one repository per host

From:
Leon Bogaert
Date:
2015-10-12 @ 13:21
I'm just setting up borg backup on our servers to test with it. We have 
about 15 servers with about 100GB to backup per server.

Should I create one repository on the backupserver per host or should I 
create one global repository and prefix every archive with the hostname?

Thanks in advance!

-- 
Tim_online B.V.
Axelsestraat 4
4543CJ, Zaamslag
tel.: (+31) 115 851 851
www.tim-online.nl

Re: [borgbackup] one global repository or one repository per host

From:
Thomas Waldmann
Date:
2015-10-12 @ 14:57
> I'm just setting up borg backup on our servers to test with it. We have 
> about 15 servers with about 100GB to backup per server.
> 
> Should I create one repository on the backupserver per host or should I 
> create one global repository and prefix every archive with the hostname?

If you want to take advantage of deduplication AND you do not want to
backup simultaneously AND you can live with cache resyncs happening
regularly and taking some time, then you can store into same repo. Use a
different prefix for the archives (e.g. hostname-date) and be careful to
use that prefix also when pruning.

If above does not apply (or there isn't much inter-server duplication,
use different repos.

---

GPG Fingerprint: 6D5B EF9A DD20 7580 5747  B70F 9F88 FB52 FAF7 B393
Encrypted E-Mail is preferred / Verschluesselte E-Mail wird bevorzugt.

Re: [borgbackup] one global repository or one repository per host

From:
Leon Bogaert
Date:
2015-10-13 @ 09:15
>> I'm just setting up borg backup on our servers to test with it. We have
>> about 15 servers with about 100GB to backup per server.
>>
>> Should I create one repository on the backupserver per host or should I
>> create one global repository and prefix every archive with the hostname?
>
> If you want to take advantage of deduplication AND you do not want to
> backup simultaneously AND you can live with cache resyncs happening
> regularly and taking some time, then you can store into same repo. Use a
> different prefix for the archives (e.g. hostname-date) and be careful to
> use that prefix also when pruning.
>
> If above does not apply (or there isn't much inter-server duplication,
> use different repos.

Thanks for the great explanation Thomas. There is quite a bit 
inter-server duplication but that usually are smaller files. I think I'm 
going to have to experiment what would be most beneficial for us. Maybe 
use a different repository for each group of servers.

-- 
Tim_online B.V.
Axelsestraat 4
4543CJ, Zaamslag
tel.: (+31) 115 851 851
www.tim-online.nl