Kern Sibbald schrieb:
> > I created differnt pools for regular backups and long term archival. I
> > think the retention times are reasonable. We are aware that we can't handle
> > a _real_ long time archival (copy to new media, verify...), but we want to
> > keep the volumes for 30 years.
>
> Be sure to archive the conf files as well as the full source for Bacula with
> each major archive that you do.
Yes and keeping the right hardware in case of a restore might be a problem in
the future too.
> > So far so good. But I'm bit unsure about the "right" File and Job Retention
> > periods. I can set these times only in the client resource, but I would
> > like to differ the period if the job is a regular backup or an long term
> > archival job. For the regular backup I would choose 6 months for File/Job
> > Retention, because that's the longest period until a tape will be recycled
> > again (full monthly tape). For the archival job I would like to keep the
> > file/job information longer, not 30 years, but maybe 5 years for the file
> > records.
> >
> > How can I accomplish this? Any thoughts about this setup or configuration?
>
> 1. You might want to use two different databases, one for regular backups and
> one for archives. This will clearly separate your archive data from your
> regular data.
I changed the bacula db init scripts to create a new database bacula_archive
and can connect with a password to it with psql.
pg_hba.conf
# TYPE DATABASE USER CIDR-ADDRESS METHOD
local bacula bacula md5
local bacula_archive bacula md5
# psql -U bacula bacula_archive
Passwort f?r Benutzer bacula:
Dies ist psql 8.1.7, das interaktive PostgreSQL-Terminal.
[...]
But now bacula-dir does not start with the second catalog:
20-Feb 22:07 bacula-dir: Fatal error: Database not created or server not
running.
20-Feb 22:07 bacula-dir: Fatal error: Could not open Catalog "ArchiveCatalog",
database "bacula_archive".
20-Feb 22:07 bacula-dir: Fatal error: Database not created or server not
running.
20-Feb 22:07 bacula-dir ERROR TERMINATION
Please correct configuration file: /opt/bacula/etc/bacula-dir.conf
This is from the postgres log:
2007-02-20 22:07:28 CET FEHLER: keine Berechtigung f?r Relation version
2007-02-20 22:07:28 CET LOG: unerwartetes EOF auf Client-Verbindung
# Generic catalog service
Catalog {
Name = MyCatalog
dbname = bacula; user = bacula; password = "xxxx"
}
Catalog {
Name = ArchiveCatalog
dbname = bacula_archive
user = bacula
password = "xxxx"
}
I don't know what is wrong with the additional catalog.
> 2. You might want to define two separate jobs/clients for each job to be
> archived. One uses the normal backup database and retention periods. The
> other uses the archive database and has appropriate archival retention
> periods -- why not 30 years in the beginning if you don't do archives very
> often; you can always reduce it later if your archive database grows too
> large.
If I can solve the above problem - and two bacula db's are are good to handle -
this will be a good solution.
Ralf
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
