Hi all,
I've got question which already appear here, but none of answers were
not suitable for me.
I have configure my backup system and all works fine, except one
server. On this server I've got large partition - aprox. 25Gb. I set
etimeout to 6000 and dtimeout to 18000 - I thought this should be
enough.
In log on client side (sendsize.debug) it is written as directory was
finished, but in my amanda e-mail report I've got Request timed out
anyway.
I think that this might be result of one of two problems:
- simply tar of directory was made, but couldn't be send to
server in time. This could be solved with setting even
higher etimeout value
- problems are with holding disks - I've got two holding
disks. On first I don't have enough place to store backup
of that directory - but on second one there is planty of
room. Does amanda know what holding disk to take, or
should I configure it manually.
Holding disks are sized:
/spool1 - 60 Gb
/spool2 - 40 Gb
This client otherwise works fine, because I tried to backup it,
without problematic directory - so I think it is not configuration
problem.
Does Amanda have any limitations with etimeout, dtimeout, max.
directory sizes?
I read about manually backup partition for the first time, and then
configure to only incremental backup it everytime - do you think
this could be the solution? Which is the easiest way to backup
directory by hand?
Well, I thank you in advance.
Goodbye, Jure
