Hi, 07.08.2007 13:27,, Radek Hladik wrote:: > Hi, > > Arno Lehmann napsal(a): >> Hi, >> >> 07.08.2007 11:39,, Mike Follwerk - T²BF wrote:: >>> Radek Hladik schrieb: >>>> Till now I came up with this ideas: >>>> * Backup catalog and bootstrap files with the data >>>> * Disable jobs/files/volumes autopruning >>>> * maybe modify some livecd to contain current version of bacula or at >>>> least bscan (do not know, maybe such a CD exists) >>>> * Create SQL query to list which jobs is on which tape and print it on >>>> the paper with the tapes >>>> >>>> Do you think this is enough or am I overseeing something? >> I didn't actually read your original mail, but going from the subject, >> this sounds good already. Having the job lists on paper is definitely >> helpful sometimes, but I'd mainly make sure to know where the current >> catalog dump is stored, though. The catalog has all the information >> you will need, readily accessible by Bacula. If you only have your >> printout, you'll probably need some time for bscanning, but >> bextracting the catalog dump, loading it and starting Bacula itself >> might be faster. > > I'm planning to have catalog backup on last tape or on some other media > (flashdisk, cd?)
If your complete catalog dump fits onto one of these (perhaps compressed), that would make recreating the catalog simpler. I typically recommend to send the catalog dump to another file server in the network, which reduces the risk to lose all catalog dumps greatly, and is really easily done. > with the backups, so only bscan of last tape would be > needed at worst. Ok, you seem to know the major points already :-) > But what I am a little affraid of is: I restore catalog > and bacula says: "Wow, such an old catalog, you forget to disable XY > type pruning, I am going to delete old files from catalog" :-) Obviously, that can happen, and has happend... There are two ways to avoid that problem. Either make sure no pruning takes place until your restores are completed. This is more or less impossible, though. Or, and that is the better approach, make sure the necessary data will never be pruned. Thus my recommendations to set up extra job and client definitions for the archival backups. These would include longer retention times for jobs and files, but use the regular client addresses and file sets. >>> since no one has answered this yet, I feel free to voice a blind guess: >>> doesn't bacula have some kind of "archive" flag for volumes for >>> precisely this reason? I seem to remember something like that from the >>> documentation. >> Well, the something includes a "not implemented" remark, unfortunately :-) > > I know and thus I didn't mention it in my previous email. And it still > is not what I'm looking for as it should delete files from catlaog. > >> But you don't really need that, anyway: Just make sure your long term >> volumes are not automatically pruned and you're already half the way >> where you want to go... the other half of the way is usually deciding >> if you need complete file lists for your archives (then you probably >> want to set up separate job and client entries for these, so you can >> have different retention times for normal production backups) or if >> the fact that the data exists and on which volumes it's stored is >> enough (Then just make sure the jobs are not pruned from the catalog). >> > >> For real long-term storage, you'll have to find ways to move data to >> new tapes from time to time, probably keeping the catalog up to date, >> and so on, so that you can restore when the original tapes can't any >> longer be read. Migration might be helpful for this, but that's a >> different story... > > I am thinking of year or two, maximum three years. And after this period > the backups will be done again completely. There will meybe be the need > to recycle really old backups but it should be done manually. Tapes should be good after that time, if stored properly. And manually recycling them would always be possible. Arno >> Arno >> >> >>> Regards >>> Mike Follwerk >>> > Radek > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
