On Friday 16 February 2007 19:29, Kel Raywood wrote: At first I must apologize for not answering earlier. I had to test all your suggestions and so I wasn't able to respond earlier
> To ensure that I understand, here's what I think you want to do. > > Use bacula for backups to disk-based volumes. > Create backups of these volumes to a tape library. > Tapes are taken offsite. You exactly hit the point :-) > > I think that the feature of bacula you want is copying jobs, which is > currenly in development. However, I can think of a couple of things you > can do. That was my guess too, yes. > > (1) Bacula can use multiple catalogues. Use a second catalogue for > backing up (or archiving) the disk volumes to tape. You can set the > priority of the archiving job to ensure that it doesn't start until > after the backups have completed. You could also have a pre-flight > script that dumps the first catalogue and include it in the > tape-archiving. You could have a final (after archiving) job that dumps > the second catalogue. This won't be very large since the archive will > contain a small number of large files. You could probably save it to CD > or transfer it somewhere else for disaster recovery. Didn't take that into further consideration yet, because I prefer an approach in some matter of (2) (so does the customer). > > (2) Instead of tar use star. It can use different header types that > enable it to store ACLs and files larger than 2G. It also has a > multi-volume mode and a new-volume-script option. You can write your > own scripts to operate the tape-library using the mtx command. If you > are using multiple drives, you will need to use lockfiles or semaphores > to avoid conflicts with the user of the changer. As a matter of fact, the library isn't there yet. At the moment, we are using a single tapedrive as we are still in our pilot. Nevertheless I am already able to test this procedure, as the volumefiles of our pilot don't fit to one tape anymore. So I was able to test tar with multiple volumes. As I didn't know star before, I did some further research with tar. tar knows two options which may suite my needs, which are --info-script and --new-volumescript. What I am doing now, is to call a script, which ejects the volume, does a "mt -f /dev/st0 status" and waits until the next volume is inserted and so tar doesn't wait for someone pressing enterkey. It is in testingstage since friday and it looks as if it works (will verify that on wednesday). My plan is, to use tar with a modified script which takes the next tape in the library. As one of the last questions: What I don't get yet, is the difference of --info-script and --new-volume-script. It is kind of hard to search google for examples, so I hope that anyone on this list may provide some knowledge. > > Hope this helps. > It really did, thanks a lot. > Kel Raywood > Greetings, Benni -- Benjamin E. Zeller Ing.-Büro Hohmann Bahnhofstr. 34 D-82515 Wolfratshausen Tel.: +49 (0)8171 347 88 12 Mobil: +49 (0)160 99 11 55 23 Fax: +49 (0)8171 910 778 mailto: [EMAIL PROTECTED] www.ibh-wor.de
pgpFp2XMW3Mi0.pgp
Description: PGP signature
------------------------------------------------------------------------- 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
