Amanda-Users

Label Printing. Resolution

2002-09-03 12:39:03
Subject: Label Printing. Resolution
From: "Alex Specogna" <alex.specogna AT cryptologic DOT com>
To: <amanda-users AT amanda DOT org>
Date: Tue, 3 Sep 2002 12:26:22 -0400
Good Day all,

I wanted to thank those of you that assisted in my struggle with label
printing and Amanda.  After some hand to hand combat with amreport I
have managed to get the labels printing.

Originally I was under the impression that amdump ran amreport for me
and just wasn't outputting anything.  Wrong, amreport needs to be run
separately. flaw in logic number 1
After I cleared that hurdle I defined the correct lbl-templ directive
and started running amreport as follows:

amreport Backups -l /usr/adm/Backups/<logfile name> -f /dev/null -p
test.ps

I noticed that nothing was being created.. until today when I stumbled
upon a Backupstest.ps file which contained a sexy looking label with all
of my file system information in it. I jumped for joy and asked "WTF did
I do?".  The answer is as follows:

>From my experimentation amreport APPENDS the text after the -p flag (in
this case "test.ps") to the current directory name you are in and places
the file one directory above your current location.  e.g. if you are in
/usr/home and you run the command line mentioned above you would get a
file called /usr/hometest.ps.
I also noticed that if you do not include the Set name in the output
name of the -p flag it behaves similarly. Hence to correctly get the
labels working do the following:

1) Define the lbl-temp directive in your tapetype definition.
2) Run the amreport command as follows:
amreport <Set Name> -l <full path to log file> -f /dev/null -p <output
file inc. set name>

e.g.
amreport Backups -l /usr/adm/amanda/Backups/log.20020903.0 -f
/dev/null -p /tmp/Backups-0903.ps

This will put the file in a predictable location of /tmp and solve a lot
of headaches.

This is one thing that the Amanda application is really bad at..
documentation.  The application is fabulous.. all it needs is someone to
champion the cause of making it easy to use (through documentation).



<Prev in Thread] Current Thread [Next in Thread>