Re: Amanda not scheduling dumps properly
2003-02-12 14:23:24
On Wed, 12 Feb 2003 at 8:50am, John Oliver wrote
> I'm still having a problem with one partition that amanda keeps trying
> to do a level 0 backup for, and fails. Why will it not back up this
> partition all by itself, or with just a couple of other things?
How big is your tapetype? How big is hda2 on cm? How well does it
compress (what are the contents of curinfo/cm/_dev_hda2/info)?
Amanda is only going to schedule things it thinks can fit.
> STATISTICS:
> Total Full Daily
> -------- -------- --------
> Estimate Time (hrs:min) 0:04
> Run Time (hrs:min) 4:08
> Dump Time (hrs:min) 0:18 0:07 0:11
> Output Size (meg) 564.1 553.4 10.8
> Original Size (meg) 1905.4 1683.6 221.8
> Avg Compressed Size (%) 29.6 32.9 4.9 (level:#disks
> ...)
> Filesystems Dumped 17 2 15 (1:15)
> Avg Dump Rate (k/s) 531.0 1304.4 16.9
>
> Tape Time (hrs:min) 0:08 0:07 0:00
> Tape Size (meg) 564.9 553.5 11.5
> Tape Used (%) 3.0 2.8 0.2 (level:#disks
> ...)
> Filesystems Taped 17 2 15 (1:15)
> Avg Tp Write Rate (k/s) 1263.6 1322.5 401.5
OK, from this all we know that amanda was dumping hda2 straight to tape
(no holding disk involved). You don't mention what type of tape drive you
have, but if cm can't crank out the (compressed) bits and put them over
the network at the tape's streaming speed, your tape won't be streaming
and will have reduced capacity.
> NOTES:
> planner: Last full dump of cm:/dev/hda2 on tape overwritten in 1 run.
> taper: tape Indyme001 kb 18078912 fm 18 writing file: No space left on
> device
And from this we know that it wrote, in total, ~18GB worth of stuff to
tape before it EOT. How big do you expect your tapes to be? Hardware
compression is *off*, right?
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
|
|
|