Re: disklist and hw compression
When you are using hardware compression on the tape drive, the
backup image cached on disk is of course not yet compressed.
If it thinks the dump won't fit on the tape, did you pick
a different tapetype for the compressed device?
On Tue, 2 Apr 2002, Matthew Boeckman wrote:
I have two (hopefully) quick questions.
I'm running an ultra5, and trying to level0 a 60+gig filesystem. Using
software compression took over 22 hours (i killed it at that point) so I
decided to use hardware, specifying /dev/rmt/0cn as the tape device in
amanda.conf. When I tried to run amdump, it failed saying that dumps
too large for disk, which is true if you don't count the hardware
compression I was trying to use. The tapes are AIT2 50GB tapes. Is there
a way to force amanda to do this? I assume perhaps amadmin csd force
diskname ? I wanted to know for sure before kicking off another
20+hour backup cycle. Or is there something that I have to configure in
amanda to let it know i'm using hardware compression and to ignore tape
warnings?
The second and sort-of corollary to that is what is the exact syntax of
exclude files referenced from disklist? I can't seem to find an exact
answer in the documentation/FAQOMATIC. The examples/disklist file has
the following:
slowsrv /usr {
user-tar
exclude list .exclude
compress server fast
} 2 le0 # no line break before spindle and interface
Does that mean that .exclude is in /usr ? Is it exclude absolute
pathnames or any pattern match? In other words if I want to exclude
/usr/bob, and in the exclude I have /bob, will that exclude any match
for bob, or only subdirs of the mount being backed up? Likewise, what
are the compress server fast lines about?
Thanks!
--
-
Marc Mengel [EMAIL PROTECTED]
disklist and hw compression
I have two (hopefully) quick questions.
I'm running an ultra5, and trying to level0 a 60+gig filesystem. Using
software compression took over 22 hours (i killed it at that point) so I
decided to use hardware, specifying /dev/rmt/0cn as the tape device in
amanda.conf. When I tried to run amdump, it failed saying that dumps
too large for disk, which is true if you don't count the hardware
compression I was trying to use. The tapes are AIT2 50GB tapes. Is there
a way to force amanda to do this? I assume perhaps amadmin csd force
diskname ? I wanted to know for sure before kicking off another
20+hour backup cycle. Or is there something that I have to configure in
amanda to let it know i'm using hardware compression and to ignore tape
warnings?
The second and sort-of corollary to that is what is the exact syntax of
exclude files referenced from disklist? I can't seem to find an exact
answer in the documentation/FAQOMATIC. The examples/disklist file has
the following:
slowsrv /usr {
user-tar
exclude list .exclude
compress server fast
} 2 le0 # no line break before spindle and interface
Does that mean that .exclude is in /usr ? Is it exclude absolute
pathnames or any pattern match? In other words if I want to exclude
/usr/bob, and in the exclude I have /bob, will that exclude any match
for bob, or only subdirs of the mount being backed up? Likewise, what
are the compress server fast lines about?
Thanks!
--
Matthew Boeckman(816) 777-2160
Manager - Systems Integration Saepio Technologies
==
==
/earth is 98% full ... please delete anyone you can.
Re: disklist and hw compression
On Tue, 2 Apr 2002 at 7:59am, Matthew Boeckman wrote
20+hour backup cycle. Or is there something that I have to configure in
amanda to let it know i'm using hardware compression and to ignore tape
warnings?
To use hardware compression, you fib to amanda about your tapelength. In
your tapetype, put a reasonable guess, based upon your data, as to how
much you can get on tape. If it's all code and text files, 90-100GB
wouldn't be far off. If it's all jpgs, well, 50GB may be about right.
You may need to adjust if you keep hitting EOT.
slowsrv /usr {
user-tar
exclude list .exclude
compress server fast
} 2 le0 # no line break before spindle and interface
Does that mean that .exclude is in /usr ? Is it exclude absolute
I believe so.
pathnames or any pattern match? In other words if I want to exclude
/usr/bob, and in the exclude I have /bob, will that exclude any match
for bob, or only subdirs of the mount being backed up? Likewise, what
./bob would exclude /usr/bob.
are the compress server fast lines about?
That's software (gzip) compression being done on the amanda server (rather
than the client). If you turn hardware compression on, be sure to turn
software off.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: disklist and hw compression
On Tue, 2 Apr 2002, Matthew Boeckman wrote: I'm running an ultra5, and trying to level0 a 60+gig filesystem. Using software compression took over 22 hours (i killed it at that point) so I decided to use hardware, specifying /dev/rmt/0cn as the tape device in amanda.conf. When I tried to run amdump, it failed saying that dumps too large for disk, which is true if you don't count the hardware compression I was trying to use. The tapes are AIT2 50GB tapes. Is there a way to force amanda to do this? I assume perhaps amadmin csd force diskname ? I wanted to know for sure before kicking off another 20+hour backup cycle. Or is there something that I have to configure in amanda to let it know i'm using hardware compression and to ignore tape warnings? Make sure that you configure the tape length in amanda.conf to specify what you think it is that you'll be able to get on a tape counting hardware compression. When I used (note past tense) hardware compression with our systems, I was using 40 GB DLT tapes. With regular, unzipped data I was getting close to 70 GB on a tape, so I set the tape length to 65000 Mb. It worked fine with several partitions and combinations, anywhere from 45 to 65 GB in size. Unfortunately, one particular partition, only 45-50 GB in size, was loaded with small directories containing nothing but gzips. I was not able to get that on a tape until I used GNUTAR to break it up. I stopped using hardware compression because the general attitude among the experts here was that amanda is better off doing her own packing. I haven't really noticed a significant difference, but, as always, YMMV, etc. - - - -- Eric Trager
Re: disklist and hw compression
The second and sort-of corollary to that is what is the exact syntax of exclude files referenced from disklist? ... Andrew Hall wrote a nice description of exclusion patterns. It is part of the 2.4.3 docs directory, so you could grab a recent beta from www.amanda.org. Matthew Boeckman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
