Hi Kern, Thanks for the update on that. Looks like I missed that one (your update _and_ the documentation, while I haven't read release notes though).
Kind regards, Erik On Thu, Feb 20, 2020 at 3:46 PM Kern Sibbald <k...@sibbald.com> wrote: > Hello, > > Concerning lack of documentation as you noted below: yes, we can always > improve documentation. In this case, the need for special libraries is > documented. For example in the ReleaseNotes file, it > is documented under 3 releases. The most recent one states: > > ===== > Release 9.4.3 > > This is a bug fix release for version 9.4.2. It includes a number of bug > fixes and patches. > > [snip] ... > > S3 driver: If you are trying to build the S3 drivers, please remember to > use the > community supplied (from Bacula Enterprise) version of libs3.so found at: > > https://www.bacula.org/downloads/libs3-20181010.tar.gz > ====== > > Not > > > > On 2/17/20 3:27 PM, Erik Geiger wrote: > > > On Mon, Feb 17, 2020 at 1:41 PM Radosław Korzeniewski < > rados...@korzeniewski.net> wrote: > >> 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. >> > > Hi Radoslaw, > > Turned out that I was able to build when using the libs3 provided by > bacula [https://www.bacula.org/downloads/libs3-20181010.tar.gz] > Sadly that wasn't really documented. > > >> >>> 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. >> > > I do have the cloud backup running, now. All works even better than > expected regarding the S3 upload. I also realised that I can use "Cache > Retention" so the local disk won't run out of disk pace while still > allowing fast restores within the "Cache Retention" period. > > Tanks again, > > Erik > >> best regards >> -- >> Radosław Korzeniewski >> rados...@korzeniewski.net >> > > > _______________________________________________ > Bacula-users mailing > listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users > > >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
