The email output of amreport seems to have been broken somewhere between
2.4.1p1 and 2.4.2.
The column widths are incorrectly determined and the output is particularly
messy with large file systems (and/or large lengths of time, etc).
It would also make more sense (to me, at least) for the
The email output of amreport seems to have been broken somewhere between
2.4.1p1 and 2.4.2.
What you call "broken", others call a new "feature" :-).
Look for "columnspec" in "man amanda". FYI, here's what I use:
columnspec "OrigKB=1:8,OutKB=1:8,DumpRate=0:7,TapeRate=0:7"
It would also make
I have always wondered .. why does amanda pipe ufsdump output to ufsrestore
before sending it to the tape device?
It's collecting the index data.
The dump (or tar) output pipeline is rather complicated. The image data
goes back to sendbackup who in turn tee's it to the restore program
to
I have always wondered .. why does amanda pipe ufsdump output to
ufsrestore
before sending it to the tape device?
It's collecting the index data.
John, thanks for clarifying...
If amanda is dumping direct to tape (file systems that are
bigger than the
holding disk), I'm lucky if i get
On Sat, 27 Jan 2001, Jason Winchell wrote:
Does anyone know the parameters for DDS4, 150m, 20GB/40GB tapes?
I can offer the following:
define tapetype DDS4 {
comment "DDS 4 tapes 150 m"
length 19400 mbytes
filemark 32 kbytes
speed 2700 kbytes
}
This has been
