[SAC] Bacula Config for Trac Server

[christopher.schmidt at nokia.com]

Hi all,

I have taken the liberty of configuring Bacula this morning on the backup.osgeo.org
VM. Bacula is now configured with a Storage Device in /backup/bacula on that machine,
and a job configured to backup a file (/osgeo/trac_backup.sh) from trac.osgeo.osuosl.org.

The file is created by /osgeo/backup.sh, which is set in cron to run every morning at 
1:37AM, via root's crontab.

The backup command takes about 90 seconds to run, and does a hotcopy of each trac
environment, followed by a pg_dump of the corresponding database to a file, then
zipping the result up. The zip file is ~500MB, and currently it is set to be
removed after 2 days. (So we will have 1GB of trac backups. I think.)

I have also tested restoring from bacula; the following steps:

 sudo bconsole
 restore
 5 (Select the most recent backup for a client)
 2 (trac.osgeo.osuosl.org-fd)
 add /osgeo
 done
 yes

After approximately two minutes, the zipfile was restored to:

  /backup/bacula/osgeo/trac_backup.zip

on the trac server.

To add more backups to the Bacula system, we should be able to do something
similar to this for each host:

Job {
  Name = "BackupTrac"
  Level = Full
  FileSet = "TracFile"
  Type = Backup
  Schedule = TracSchedule
  Storage = File
  Where = /backup/bacula/trac
  Pool = Default
  Messages = Standard
  Client=trac.osgeo.osuosl.org-fd
}
FileSet {
  Name = "TracFile"
  Include {
    File = /osgeo/trac_backup.zip
  }
}
Schedule {
  Name = "TracSchedule"
  Run = Full sun-sat at 2:03
}
Client {
  Name = trac.osgeo.osuosl.org-fd
  Address = 140.211.15.71
  FDPort = 9102
  Catalog = MyCatalog
  Password = "blahblah"         # password for FileDaemon 2
  File Retention = 3 days            # 30 days
  Job Retention = 6 months            # six months
  AutoPrune = yes                     # Prune expired Jobs/Files
} 

This is pulled directly from /etc/bacula/bacula-dir.conf.

I don't know much about Bacula, so there may be problems I've
created here. I have not implemented any partial/incremental backup
strategy at this time. (I'm not really sure how I'd do it for 
trac anyway.)

Combined with the existing SVNMirror infrastructure, I believe
that this completes the task of backing up the important aspects of
the Trac/SVN server. 

Regards,
-- 
Christopher Schmidt
Nokia