Hi,
i am about to setup a bacula system (actually its allready running) to
backup several server systems. while thinking about real desasters like
fire etc., i found that i would loose a maximum of 2 weeks of data with my
current configuration. so started thinking about another concept and i think
i have something better. but before i try to implement it, i thought it
would be
a good idea to ask more experienced users for their comments, as i am new
into this kind of problems.
so, what i have is
- a bacula running on a debian sarge system (mysql-backend)
- connected to this system is HP Ultrium LTO Autochanger (20 Slots)
there are some premisses for the concept:
1) the physical location of the backupsystem is different from that of
the technical staff
2) a staff-member will visit the backup site once a week to change tapes.
3) it should always be possible to restore files without maintaining the
tapedevice physically (to change tapes
or something)
what i have at the moment is something like this.
1) full backup is done on sat.
2) differential backups are done from mon-fri
3) on next sat staff member removes fullbackup done at 1) and inserts
new tapes
so its always possible to restore files without changing tapes, because
all data is always
availble in the autochanger. if the location of the backupsystem burns
down we'll loose
a max of two weeks of data.
now my, hopefully better, concepts would look like this:
1) fullbackup is done on sat (A)
2) differential backups SINCE A are done from mon-fri
3) on next sat another fullbackup is done (B) and removed from the changer
4) differential backups SINCE A (not SINCE B like in the concept above)
are done from mon-fri
5) on next sat fullbackup is done (C) and removed; instead of these
tapes, backup B is inserted
6) differential backups SINCE B are done from mon-fri.
7) on next sat the A-Tapes are recycled for a full backup and removed;
instead of these tapes, backup C is inserted
8) and so on...
now, its always possible to restore files, because all data is always
available in the changer; if desaster strikes
and the site burns down only one week of data is lost!
is this correct ? is there a logical mistake somewhere ? and finally, do
you think something like this
could be implemented with bacula ? as far as i know from reading the
docs, there is no possibilty to
give a backup a marker to say "make a differential backup SINCE backup
XYZ"; instead, differential
backups always use _the last_ fullbackup, which would break my concepts...
thank you very much for your comments!
Philipp
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
