I am trying to encourage the use of Bacula in our office, with an aim of using it in place of other backup solutions at our clients too, but I'm pretty much the only one in our office with any experience with Linux or Bacula.
So obviously our implementation needs to be documented well enough that someone else can fix minor problems, and do restores when I'm not available. Does anyone have any example documentation for either their own or their clients sites that they'd like to share? (as a side note, does anyone have any bat packages for Debian?) The tasks I can think of that will need documenting are: . A summary of the backup strategy (eg pools, incremental, differential, etc) for that site . Checking that services are running, and starting and stopping them. . Labelling new media . Purging existing media, and when that should and shouldn't be done (eg if someone forgot to bring a tape in from offsite and they want to run tonights backup on last nights tape). . Cancelling a job (any when that might be required) . Basic status stuff from the director (eg is a job in progress?, list of media, etc) Thanks James ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
