On Mon, Jul 12, 2021 at 06:05:49PM +0200, Kern Sibbald wrote: > Hello again, > > I can see bacula installation placement is just as hot a topic as it has > always been. However, I sense a trend toward accepting the /opt/bacula > concept. I do wish we could convince a distro such as Debian, but they have > their point of view, and I for one do not plan to argue with them.
Dear all, we've been using bacula since version 3.x or thereabouts (maybe even earlier but my memory might be fading here cause it's been a really long time :-)) on a wild variety of platforms and I've never even bothered with the prepackaged stuff and always compiled bacula from source. It doesn't have that many dependencies, you can choose to keep all your files / eggs in one directory / basket and upgrades between minor versions (usually involving no DB / catalog upgrade) are a beeze as this enables you to keep as many versions around alongside each other as you deem fit or prudent. Also, this tends to keep your installation lean and small with only the stuff compiled in that you really need as it doesn't pull in the dependencies of a "full blown" bacula installation that might be required by a prepackaged version from your OS vendor of choice. We install bacula into /server/bacula-x.yz using a --configure argument, then softlink the currently "active" installation to /server/bacula. Following the "make install", I simply rsync the var directory and the conf and query.sql files in etc over to the new install and that's it. As our init / systemd scripts only reference "/server/bacula", the changes are transparent to them. Should things go pear-shaped with the new install we can simply point /server/bacula to the previous version, no harm done. Also it makes a bare-metal recovery quite uncomplicated as you can simply copy back the active bacula install to a newly installed "fresh" backup machine, set up the catalog and you're done (we keep a few copies of the "/server/bacula-x.yz" directories and catalog dumps from our bacula servers around on servers all around our various networks in a sort of "cross-site" redundancy setup). This might not be the most elegant solution but it's worked great for the decades we've been using bacula now. Thanks Kern & team and all the contributors to bacula for your hard work over the many years, it's much appreciated! All the best, Uwe -- Uwe Schürkamp | email: <uwe.schuerk...@nionex.net> Arvato Systems S4M GmbH | Sitz Köln | Amtsgericht Köln HRB 27038 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
