Hello, wt., 11 lut 2020 o 18:41 Erik Geiger <e...@frontify.com> napisał(a):
> You are referring to this documentation? > https://www.bacula.org/9.4.x-manuals/en/main/New_Features_in_9_4_0.html#SECTION00300100000000000000 > Yes. > I wasn't able to build bacula with cloud support and I can't use the rpm > packages from bacula as they aren't supported by the puppet module I'm > using. So I was looking for something like an "after" job syncing to S3 > with aws cli or the like. > Sorry for that. You should create a ticket at bugs.bacula.org to show that something is wrong about it. > But if the Cloud Storage functionality is the way to go I'll figure out > how to compile with S3 support. > So if I get the documentation right the backup is first stored to the > local disk and afterwards moved to the cloud while I could still do a > restore from local disk as long as I configure the configure the "cache > Retention", right? > The default local disk backup for cloud storage works as a cache only with fully configurable behavior and retention. You can use it as the single archive storage, so during backup all your data will be saved on local disks and then synced into S3 as configured. You can use it as a DR storage using Copy Jobs where your local disks will be your main storage which will be copied into a storage cloud after a local backup. All possible configurations depends on your requirements. I hope it helps. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
