Backup Central

Hi,

is there a way, I can tell amanda not to collect data and then transfer it
to tape? Currently there is mostly 1 DLE direclty send to tape and then
it's collecting data before the rest is also written:

SUMMARY part real estimated
size size
....
wait for dumping: 23 140114m ( 33.57%)
dumping to tape : 0 0m ( 0.00%)
dumping : 3 100738m 236457m ( 42.60%) ( 24.14%)
dumped : 95 42799m 40796m (104.91%) ( 10.25%)
wait for writing: 94 42799m 40796m (104.91%) ( 10.25%)
wait to flush : 0 0m 0m (100.00%) ( 0.00%)
writing to tape : 0 0m 0m ( 0.00%) ( 0.00%)
failed to tape : 0 0m 0m ( 0.00%) ( 0.00%)
taped : 1 0m 0m (100.00%) ( 0.00%)
tape 1 : 1 0m 0m ( 0.00%) KDD055 (2 chunks)

How can I configure amanda to write to tape when a DLE is fully in the
holdingdisk ?

(Amanda 3.2.0)

Regards,
Marc

On Fri, Dec 10, 2010 at 10:02:40PM +0100, Marc Muehlfeld wrote:
Hi,

is there a way, I can tell amanda not to collect data and then transfer it
to tape? Currently there is mostly 1 DLE direclty send to tape and then
it's collecting data before the rest is also written:

Not certain I understand the question(s). Assuming there is
a usable holding disk available, amanda will dump one or more
(depending on the configured number of dumpers) DLEs simultaneously
to the holding disk. No DLE collecting on the holding disk is
transfered to tape unless it has finished dumping successfully.

If there is no holding disk available, then one DLE, and only one
at a time, are dumped directly to tape (possibly buffered for
tape spanning).

I collect some of my DLEs on the holding disk without taping
by dumping them with the --no-taper option. They are later
flushed to tape with amflush or amdump with the autoflush
option.


SUMMARY part real estimated
size size
....
wait for dumping: 23 140114m ( 33.57%)
dumping to tape : 0 0m ( 0.00%)
dumping : 3 100738m 236457m ( 42.60%) ( 24.14%)
dumped : 95 42799m 40796m (104.91%) ( 10.25%)
wait for writing: 94 42799m 40796m (104.91%) ( 10.25%)
wait to flush : 0 0m 0m (100.00%) ( 0.00%)
writing to tape : 0 0m 0m ( 0.00%) ( 0.00%)
failed to tape : 0 0m 0m ( 0.00%) ( 0.00%)
taped : 1 0m 0m (100.00%) ( 0.00%)
tape 1 : 1 0m 0m ( 0.00%) KDD055 (2 chunks)

How can I configure amanda to write to tape when a DLE is fully in the
holdingdisk ?

That is the normal operation of amanda.

Jon
--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)

Jon LaBadie schrieb:
Not certain I understand the question(s).

What I mean:

When amanda is working here, first a lot of the DLEs that have been dumped
are put on the holding disk first, while amanda is dumping other DLEs.
Later amanda is putting them to tape. Why not earlier?

In my amstatus output you can see, that 95 of 121 DLEs had already been
dumped. 1 of the 95 was allready put to tape. The other 94 DLEs are still
in the holdingdisk at the time I grabbed this output. Later they are all
send to tape.

And what I want is, that amanda put DLEs to tape, when the dump to the
holdingdisk is finished. Currently this waste time, because many DLEs are
collected at the holding disk and and the taper is idle. The whole backup
could be finished earlier, if this delay wouldn't be there.

When I directly dump to tape, only one DLE can be backuped at the same time.



Regards,
Marc

On Sat, Dec 11, 2010 at 11:12:44PM +0100, Marc Muehlfeld wrote:
Jon LaBadie schrieb:
Not certain I understand the question(s).

What I mean:

When amanda is working here, first a lot of the DLEs that have been dumped
are put on the holding disk first, while amanda is dumping other DLEs.
Later amanda is putting them to tape. Why not earlier?

In my amstatus output you can see, that 95 of 121 DLEs had already been
dumped. 1 of the 95 was allready put to tape. The other 94 DLEs are still
in the holdingdisk at the time I grabbed this output. Later they are all
send to tape.

Are you certain that the taper was idle during this period? Might one
DLE being dumped directly to tape? If that DLE took a long time to
dump (and tape) then all the other DLEs could be doing is collecting
on the holding disk.

I've not used them, but several amanda.conf parameters could cause the
behavior you see. They specify to not begin taping until a condition
is met. For example, flush-threshold-dumped set to 75, will not tape
until the amount of completed DLE data available on the holding disk is
enough to fill a tape at least 75%.

When I directly dump to tape, only one DLE can be backuped at the same time.

DLEs should still be able to be dumped to the holding disk at the same
time as the one going direct to tape.

--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)

Jon LaBadie schrieb:
Are you certain that the taper was idle during this period?

Yes, it is:


SUMMARY part real estimated
size size
partition : 121
estimated : 121 375374m
flush : 0 0m
failed : 0 0m ( 0.00%)
wait for dumping: 50 212037m ( 56.49%)
dumping to tape : 0 0m ( 0.00%)
dumping : 10 1913m 160783m ( 1.19%) ( 0.51%)
dumped : 61 2268m 2552m ( 88.86%) ( 0.60%)
wait for writing: 60 2268m 2552m ( 88.86%) ( 0.60%)
wait to flush : 0 0m 0m (100.00%) ( 0.00%)
writing to tape : 0 0m 0m ( 0.00%) ( 0.00%)
failed to tape : 0 0m 0m ( 0.00%) ( 0.00%)
taped : 1 0m 0m (100.00%) ( 0.00%)
tape 1 : 1 0m 0m ( 0.00%) KDD073 (2 chunks)
all dumpers active
taper status: Idle
....



For example, flush-threshold-dumped set to 75, will not tape
until the amount of completed DLE data available on the holding disk is
enough to fill a tape at least 75%.

flush-threshold-dumped, flush-threshold-scheduled and taperflush are not
set. Default for all is 0.

On Sun, Dec 12, 2010 at 04:22:26PM +0100, Marc Muehlfeld wrote:
Jon LaBadie schrieb:
Are you certain that the taper was idle during this period?

Yes, it is:

...
taper status: Idle
....

For example, flush-threshold-dumped set to 75, will not tape
until the amount of completed DLE data available on the holding disk is
enough to fill a tape at least 75%.

flush-threshold-dumped, flush-threshold-scheduled and taperflush are not
set. Default for all is 0.
...

Sorry, I'm out of ideas.

jl
--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)

First I thought, amanda would collect n% of my tape space (66 GB here for my
vtape) before writing to tape. But at the moment I have 415 GB "wait for
writing" and the taper is idle:

...
dumping : 2 122758m 9958m (1232.72%) ( 29.69%)
dumped : 119 1227826m 403578m (304.23%) (296.96%)
wait for writing: 3 415386m 15947m (2604.70%) (100.46%)
...
writing to tape : 0 0m 0m ( 0.00%) ( 0.00%)
...
8 dumpers idle : no-dumpers
taper status: Idle

Im not really sure, when amanda decides to put dumped data to tape. Maybe
someone has a hint for me.


Regards,
Marc


--
Marc Muehlfeld (IT-Leiter)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780
http://www.medizinische-genetik.de

Marc,

Post the 'amdump' or 'amdump.1' log file.

Jean-Louis

Marc Muehlfeld wrote:
First I thought, amanda would collect n% of my tape space (66 GB here
for my vtape) before writing to tape. But at the moment I have 415 GB
"wait for writing" and the taper is idle:

...
dumping : 2 122758m 9958m (1232.72%) ( 29.69%)
dumped : 119 1227826m 403578m (304.23%) (296.96%)
wait for writing: 3 415386m 15947m (2604.70%) (100.46%)
...
writing to tape : 0 0m 0m ( 0.00%) ( 0.00%)
...
8 dumpers idle : no-dumpers
taper status: Idle

Im not really sure, when amanda decides to put dumped data to tape.
Maybe someone has a hint for me.


Regards,
Marc