I would like to use amverify to make
sure that data written to tape is also readable.
Could anybody clarify the following
issues:
1) What kind of errors can amverify
detect?
2) What kind of errors *cannot* amverify
detect?
3) Does it make sense to schedule amverify
after amdump every day?
4)
if some of your DLEs contain lots of data that
is random
(compressed iso images, mp3 files, images, zip
archives, ...)
they will expand when taped
So the advantage of using SW compression instead of
HW compression is that we can selectively choose on which DLEs compression
should be enabled
The server and the client in question are directly connected via
second ethernet jacks and a crossover cable.
First, I would check if the crossover
connection is perfectly working with some network test tool.
So, my question would be: is there a way to tell
amdump to execute one or
several scripts just before the backup begins (and of course, wait
that these
scripts complete)?
IMHO, I think this is a quite common problem.
Moreover, a tar wrapper is not practical
when there are several DLEs for
Paul, thanks for your suggestions.
On our machines, all network masks appear
to be consistent. We'll try to configure different client instance on xinetd.
Another frequent message error I didn't
mention in my first post is:
aborted:nak error: amandad busy
which may sometimes lead to:
use the interface (aka bind) option in xinetd
to run multiple
instances of the amanda client each responding
on a different address
TESTED. Configuring multiple amanda client seems to
solve this issue!
My new /etc/xinet.d/amanda file has three entries:
- The first entry binds to node
