Random Post: show_colors.sh
RSS .92| RSS 2.0| ATOM 0.3
  • Home
  •  

    Bacula 2.4.2 for Mac OS X

    August 19th, 2008

    Yet another update to the bacula client (and bconsole) for Mac OS X. System requirements and upgrade process are the same as with 2.4.0.

    Enjoy!
    bacula-client-242-1


    Bacula 2.4.0-1 for Mac OS X

    June 26th, 2008

    Binaries for the latest bacula-fd and bconsole have been updated. Upgrades from previous versions should be handled in an intelligent fashion.

    Please report any issues and I will resolve them ASAP. Thanks and enjoy!

    bacula-client-240-1


    Bacula Client 2.2.7 for Mac OS X

    January 9th, 2008

    Binaries for the latest bacula-fd are now available for PowerPC and Intel.
    Enjoy!

    Bacula Client 2.2.7 Intel
    Bacula Client 2.2.7 PowerPC


    bacula-2.2.5-1 etch backport

    December 6th, 2007

    After multiple attempts and not enough time to make it happen, I’ve officially shelved my backport projects for etch. The guys over at backports.org not only do a better job but seem to have more time to devote to the project than I do.

    For those of you who may have been waiting for me to backport bacula 2.2.6 to etch I would to direct you to backports.org. They have a pretty great setup for picking and choosing newer packages that you’d like to install on your etch system. As of this writing, bacula 2.2.5 is available for installation.

    Be aware that I do plan on continuing to make binaries for Mac OS X available since I still dont know of a reliable source to get them.


    Bacula Client 2.2.5 for Mac OS X

    October 24th, 2007

    Binaries for the latest bacula-fd are now available for PowerPC and Intel.

    Enjoy!

    Bacula Client 2.2.5 Intel
    Bacula Client 2.2.5 PowerPC


    Bacula Client 2.2.2 for Mac OS X

    September 7th, 2007

    I’ve posted yet another update to the Bacula Client for Mac OS X.

    Changes from 2.2.0:

    - Fixed bugs #921, 930, and 923.
    - More portable timezone offset in bsmtp thaks to Attila Fülöp.
    - Fix several bat issues.
    - Use GTK+ calls instead of egg files in tray-monitor.
    - Win32 service routines rewritten
    - Updated projects file

    Changes from 2.2.1:

    - Detect if new PosgreSQL batch insert API is present.
    - Correct incorrect mempool call causing Director crash.
    - Update spec files for 2.2.1 release


    Bacula Client 2.2.2 Intel
    Bacula Client 2.2.2 PowerPC


    Bacula Client 2.2.0-1 for Mac OS X

    August 24th, 2007

    I’ve posted a minor update to my Bacula client packages for Mac OS X. Just some config file tweaks. If you’re already running my 2.2.0 version, there is no need to upgrade.

    Bacula Client 2.2.0-1 Intel
    Bacula Client 2.2.0-1 PowerPC


    Bacula Client 2.2.0 for Mac OS X

    August 15th, 2007

    I’ve posted some updated binary installers (zipped .pkg files) for bacula 2.2.0 for Mac OS X (the file daemon only). There are installers for both PowerPC and Intel. Be aware that they are statically linked for Mac OS X 10.4 only.

    Please also note that these installers will overwrite your bacula-fd.conf file so make a backup before running. I hope you all find them useful.

    Bacula 2.2.0 Intel
    Bacula 2.2.0 PowerPC


    bacula-2.0.3-4 Etch Backport

    June 29th, 2007

    For a lot of (good) reasons, I run Debian Stable (etch) on all my servers. For various other reasons, I need to run a newer version of bacula than what is included in the etch tree (1.38.11).

    With that in mind, I have backported bacula-2.0.3-4 from Debian Testing (lenny) and set up an apt repository for anyone else who needs it.

    Read the rest of this entry »


    Permanent Device Nodes with udev

    June 21st, 2007

    I recently converted from Arkeia (a horribly overpriced and buggy piece of software) to Bacula (a free, stable, higher performance alternative). At the same time I upgraded my backup server to Debian Etch and started having a problem where my tape library would alternatively show up as either /dev/sg0 or /dev/sg2 depending on what order things were powered up. Obviously that presents a problem if certain pieces of software expect your auto changer to located at a certain device node in /dev.

    This can be fixed by making a custom udev rule…

    Read the rest of this entry »