is it possible to force an active tape to be use??
Because i have 3 tapes in rotation(dump everyday on
HD with one flush per week) and during few week i
have only just one (my boss has gone on holiday with
2 tapes :pp).
thx for advance.
Amanda users,
Looking at the amanda.conf file on one of my servers I see this
diskdir /usr4/amanda/work # added temporary holding area to speed
disksize 3000 MB # things up ... -ck 10-12-00
diskdir /usr22/amanda/work# where the holding disk is
disksize 2000 MB
Hello amanda users,
We have been supporting our DLT8000 by treating it as a DLT7000
under IRIX 6.5.(3-7)m and modifying the scsi device tables.
We recently upgraded to 6.5.12m which supports DLT8000 via
the new ts class device driver.
Unfortunately we are unable to label the tape # amlabel -f
Unfortunately we are unable to label the tape # amlabel -f
at any either 35gig or 40 gig density. ...
Ummm, that's not anywhere near enough information to go on. What version
of Amanda? What, exactly did you put on the command line? What did
it say? Why do you think it didn't work?
I do
Looking at the amanda.conf file on one of my servers I see this
diskdir /usr4/amanda/work # added temporary holding area to speed
disksize 3000 MB # things up ... -ck 10-12-00
diskdir /usr22/amanda/work# where the holding disk is
disksize 2000 MB # how much
is it possible to force an active tape to be use??
I'm sure you already realize the bad situation you're in with only one
tape. If that tape fails, or if anything at all bad happens during the
Amanda run, you will have lost all chance of recovering anything that
didn't make it to tape on that
John,
We have been carrying the amanda.conf foward from one version
to the next. I don't know what the initial version was, perhaps
2.6 ? This server (a different server from the 6.5.12 upgrade
problem) is also running 2.4.2p2.
What are the correct entries ?
Looking at the amanda.conf file
John,
We are seeing bus errors and timeouts that we didn't see
under the earlier version of IRIX.
I can pull the errors from the SYSLOG file if you'd like.
I was trying though to figure out, and relay the info to SGI,
why label was failing and writing the dumps was working. I
don't have enough
I meant I believe that our version which is 2.4.2p2 was current.
The query was on current rather than the version number I reported.
If I understand what you're asking, yes, 2.4.2p2 is the current stable
release. There have been some patches since then, but nothing in the
tape area (or at
* John R. Jackson [EMAIL PROTECTED] (Tue, Jul 31, 2001 at 12:44:19PM -0500)
the thing is that it's a taperobot/tapechanger, and I remember reading
discussions that getting that to work is not always a trivial issue.
That's going to be true no matter what. Any time software comes in
contact
10 matches
Mail list logo