Am 26.02.2014 15:31, schrieb Markus Iturriaga Woelfel: > Here is what we do: > > We use vtapes in our Amanda setup. I wrote a small script that finds > the most recent level 0 backups and uses amvault to dump those to > physical tapes. I run this once a month and then archive those tapes. > The script was hacked together and if I get the time I'd like to > change it to use Amanda's Perl API rather than calling Amanda > commands directly, but it has been working for us. Basically, it > constructs a command line for amvault that looks like this: > > /usr/sbin/amvault -otapetype="DellPV124-DLT4" -otapecycle=1 > -osend-amreport-on=never --dst-changer robot --label-template > EECS-VAULT-%%% CONGIG HOST DISK DATE LEVEL HOST DISK DATE LEVEL ... > > After the vault, it constructs an email that contains an amreport > (with -otapetype set to our VAULT tapes) and attaches a PDF with the > 2-hole punch label version of the report. We slightly modified the > template provided. We then archive the tapes and file the report. > This should allow us to do a restore using just standard Unix tools > even if we somehow lost our entire amanda server.
Thanks a lot for your reply and the description of your setup. Maybe someday you share your script? ;-) For my current job I need/should use external hdds as target media, so I wonder if should simply define a separate changer "vault" in parallel, with vtapes on these disks. A script could check: if week-number is even, make sure to mount disk2 ... if week-number is not even, mount disk1 ... disk1 contains vtapes 1-10 ... (as example), disk2 contains vtapes 11-20 ... then amvault stuff from config daily to changer vault ... Would that work? Does anyone do it like that? Additional question (yes, I am amvault-newbie): how to get back stuff from these vault-tapes? I somehow miss a nice howto-document for this ... Stefan
