My solution (tm): - Set up a second bareos-dir and bareos-sd on the second site - specify two directors in the bareos-fd / Client
I'm sure there are at least a handful other solutions involving two directors + catalogs, but i roll this way.
-- Florian Panzer ----------------------------------- PLUSTECH GmbH Jäckstraße 35 96052 Bamberg Telefon: +49 951 299 09 716 https://plustech.de/ Geschäftsführung: Florian Panzer Amtsgericht Bamberg - HRB 9680 ----------------------------------- AWS Certified Solution Architect - Associate AWS APN Consulting Partner Mitglied in der Allianz für Cybersicherheit des Bundesamtes für Sicherheit in der Informationstechnik Am 21.08.20 um 09:05 schrieb [email protected]:
Hello, We have a working bareos setup using 19.2.7. It's all file storage but is located at one single location. To reduce risk losing data because of a major incident we would like to clone all data to a second location. We have setup a second server, but keep struggling with what the best practice would be for cloning all data to a second location. We run backups daily. Some of them are full be we also have always incremental jobs. Does anyone have a good solution for this? Regards, Matthijs
-- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/c39e8d33-3619-0c47-4c2c-da58a0f4d2dc%40plustech.de.
