Hi Alex, I'm trying to build exactly the same setup you're describing in your post. Unfortunately I couldn't find a good solution yet to accomplish this, I'd be very happy if you can share your solution once you found anything useful. I'll keep trying myself and will provide an upadate here in case I can accomplish this.
Thanks Leo On Monday, January 3, 2022 at 1:02:45 PM UTC+1 [email protected] wrote: > Hi, > > I’m currently working to setup Bareos in a multi-site redundant fashion. > The plan is to basically follow a 3-2-1 strategy with > > a) 3 copies of the data > b) 2 different medias > c) 1 offsite copy > > To accomplish this, I use 3 bareos storage engines > > a) File based on Site A (retention of 2 months) > b) File based on Site B (retention of 2 months) > c) LTO based on Site A (retention of 12 months) > > Replicating data between the File storages is pretty easy, I can use a > “PoolUncopiedJobs” copy job. However, copying the jobs to LTO is a bit more > complicate. > > With backups taken on Site A, I would have the following replication > strategy with two copy jobs : > > File Site A —> File Site B > File Site A —> LTO5 Site A > > Question 1 : If I lose File Site A, how do I know which copy Bareos will > make active? > Question 2 : Can I force a restore to use a particular copy (storage)? > > With backups taken on Site B, to reduce on bandwidth costs between sites, > I would create sequential copy jobs and create the LTO copy from the > initial copy : > > File Site B —> File Site A —> LTO5 Site A > > Question 3 : If I lose File Site A and File Site B, can Bareos promote a > copy of a copy job? > > Thanks, > > Alex > -- 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/6808598e-3c47-4935-a914-e4bfd5a090f8n%40googlegroups.com.
