On Thursday 14 December 2006 20:01, [EMAIL PROTECTED] wrote:
> 
> In the message dated: Thu, 14 Dec 2006 18:31:35 +0100,
> The pithy ruminations from Kern Sibbald on 
> <Re: [Bacula-users] avoid promotion of incremental backups to full, based on 
cl
> ient name?> were:
> => On Thursday 14 December 2006 18:05, [EMAIL PROTECTED] wrote:
> => > 
> => > Based on recent discussions the list, I'm experimenting with cleaning 
up the 
> => > bacula-dir.conf, and defining one job for each client instead of 
defining 
> => > "Full" and "Incremental" jobs with different names and hard-coded 
levels.
> => > 
> 
>       [SNIP!]
> 
> => > 
> => > Is there any way to instruct Bacula to base it's idea of whether a Full 
> => backup
> => > exists on the combination of the client name and the fileset, not on 
the job
> => > name? Essentially, can the new "snickers" job be an alias for both
> => > "snickers-full" and "snickers-inc"?
> => > 
> => > 
> => > Also, if I do go ahead with the change to the job names, will the 
existing
> => > job (and file and volume) records be purged according to their existing
> => > retention periods, even if those jobs are no longer being run?
> => 
> => This *could* be fixed up by manually tweaking the database.  However, 
given 
> 
> That's kind of what I figured.
> 
> => where you are and your general knowledge of Bacula, I would recommend 
> => completely starting from scratch (re-initialize your database, relabel 
your 
> => Volumes)  I'd suggest not to relable or overwrite or re-use any full 
backup 
> => tapes until you have a new set though.
> 
> Thanks for the response.
> 
> I may not be very experienced with Bacula, but I have somehow managed to 
backup 
> about 24TB on about 80 tapes already, so "completely starting from scratch" 
is
> not very appealing.
> 
> I guess I'll just leave my config--fully functional, but complicated to 
> read--as it is.

Leaving your setup as it is, from what I see, you are very unlikely to be able 
to do any reasonable kind of restore.  If you have a hard disk crash I cannot 
imagine how you will be able to recover to the most recent backup of your 
system without a lot of pain.

An alternative would be to simpy rename the job, run a full backup and 
manually purge the oldest of your current tapes as they are needed to run the 
new system.

> 
> Thanks,
> 
> Mark
> 
> => 
> => > 
> => > Thanks,
> => > 
> => > Mark
> => > 
> => > 
> => > 
> => > ----
> => > Mark Bergman                      [EMAIL PROTECTED]
> => > System Administrator
> => > Section of Biomedical Image Analysis             215-662-7310
> => > Department of Radiology,           University of Pennsylvania
> => > 
> => > 
> => 
http://pgpkeys.pca.dfn.de:11371/pks/lookup?search=mark.bergman%40.uphs.upenn.edu
> => > 
> 
> 
> 
> The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. If the reader 
of this message is not the intended recipient or an agent responsible for 
delivering it to the intended recipient, you are hereby notified that you 
have received this document in error and that any review, dissemination, 
distribution, or copying of this message is strictly prohibited. If you have 
received this communication in error, please notify us immediately by e-mail, 
and delete the original message.
> 

-------------------------------------------------------------------------
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

Reply via email to