Yesterday I wrote:
So it seems that once a dumper is started, Amanda waits for it to
finish and only then checks if there is another DLE for the taper to
tape. So the current behaviour of taper sitting idle much of the
time is caused by combination of 'dumporder sssS' and 'taperalgo
first' that I currently have in my config.
I changed to 'taperalgo largest', but this didn't cause the change I
expected. As you can see from amstatus snippet below, taken 4 hours
after the start of amdump, only one 9kb DLE has been taped and 11 are
waiting for writing to tape.
host:/ 1 36k dump done (4:21:04), waiting for
writing to tape
host:/db 1 168k dump done (4:21:13), waiting for
writing to tape
host:/storage/cruise 1 42940k dump done (4:53:47), waiting for
writing to tape
host:/storage/dumps 1 16637270k dump done (5:52:08), waiting for
writing to tape
host:/storage/home 1 2534k dump done (4:29:19), waiting for
writing to tape
host:/storage/mail 0 9578411k dump done (5:36:01), waiting for
writing to tape
host:/storage/trac 1 9k finished (4:21:25)
host:/usr 1 13141k dump done (4:35:27), waiting for
writing to tape
host:/var 1 375604k dump done (4:55:25), waiting for
writing to tape
host:KVA 2 5923k dump done (4:52:57), waiting for
writing to tape
host:Kaardiarhiiv 1 1110k dump done (4:22:17), waiting for
writing to tape
host:failidAN 1 268k dump done (4:22:03), waiting for
writing to tape
host:failidOZ 0 60770369k waiting for dumping
host:wwwAN 0 60432635k dumping 19339520k ( 32.00%) (5:52:09)
host:wwwOZ 0 81877773k waiting for dumping
--
Toomas Aas
