Hi Stefan,
/usr/libexec/chg-zd-mtx -info
I get
none no slots available
do you already have labled tapes in your tapelist available? And
assigned them to slots via amlabel? If not, chg-zd-mtx won't show any
available slots...
Currently I access the library via /dev/nst1 (another tapedrive
Kai Zimmer schrieb:
Hi Stefan,
/usr/libexec/chg-zd-mtx -info
I get
none no slots available
do you already have labled tapes in your tapelist available? And
assigned them to slots via amlabel? If not, chg-zd-mtx won't show any
available slots...
Oh, a very good information ...
Sure,
On Tuesday, 23.01.2007 at 22:01 -0800, Yogesh Hasabnis wrote:
If the original poster's full backup fits on to a single tape, and
backs up in a reasonable period of time, you could just do a full
backup every day, perhaps?
At the moment, full backup of my data fits on a single tape, but it
Hi everyone,
I have installed amanda. amchack works fine as well as amdump. When I
try to restore using amrecover I get :
AMRECOVER Version 2.5.1p2. Contacting server on kinshasa ...
[request failed: timeout waiting for ACK]
In the logs on the client
Stefan G. Weichinger schrieb:
Kai Zimmer schrieb:
Hi Stefan,
/usr/libexec/chg-zd-mtx -info
I get
none no slots available
do you already have labled tapes in your tapelist available? And
assigned them to slots via amlabel? If not, chg-zd-mtx won't show any
available slots...
Oh, a
Does anyone happen to know how to make use of the MIC information on an
AIT tape (AIT5) using mtx?
I found something called micinfo at
http://www.sony.net/Products/storagesolution/documents/download03.html,
but it is a lengthy patch to mtx 1.2.11, and I find no updates. A google
search for
Stefan G. Weichinger schrieb:
it should be
mtx -f /dev/$changerdev status
errm
mtx -f $changerdev status
to be correct.
S
Chris,
From my research on MIC technology about a year ago, it appears the drive will
automatically take advantage of the information if you issue an ASF and ASB
mt system calls. The MIC information allows the drive to seek directly to the
file or block requested, but this feature is
Axel Seguin wrote:
Obviously the client tries to contact the server on port 10080,
shouldn't it try to reach the server on port 10082? How can I change
that?
In ~/.amandahosts on the client I have :
server fqdn amanda user on the server amdump
Any help would be greatly appreciated.
Hi,
device priority use by mtx:
the -f argument
CHANGER environment variable
TAPE environment variable
/dev/changer
chg-zd-mtx set the TAPE environment variable, mtx use it unless you have
the CHANGER variable set.
maybe we should set CHANGER too.
I don't know why it doesn't use -f, but
Jean-Louis Martineau schrieb:
device priority use by mtx:
the -f argument
CHANGER environment variable
TAPE environment variable
/dev/changer
chg-zd-mtx set the TAPE environment variable, mtx use it unless you have
the CHANGER variable set.
maybe we should set CHANGER too.
Stefan G. Weichinger schrieb:
googled a bit and found notes about a bug in 2.4.4, but I am unsure if I
hit this particular one.
Could anyone *please* let me know if this problem would be avoided with
a more recent release of Amanda?
Thank you, Stefan.
12 matches
Mail list logo