Hi
I have been tasked at making sure we have a valid backup of a box that i
know nothing about! Its in a corner of one of our IDC's, has been up for
about 3 years and no-one knows anything about it.
uname -a gives me
dgux hostname R4.20MU07 generic AViiON PentiumPro
does anyone know what i
The backup devices I am
evaluating are
1. HP Ultrium 448 Tape Drive
2. HP DLT VS160 Tape Drive
3. HP SDLT 320
4. HP SDLT 600
I would like to know whether these backup devices are fully compatible
with Amanda. Does anybody on this list use these backup devices in
his/her setup ? Suggestions
I am familiar with the Amrestore command.
But the problem I am facing is that the Amanda server which also holds
other applications crushed. So I have to restore data from another
server - I have Solaris 9 and and or Solaris 10 servers that I can
connect to the tape drive...
I also saved
We got this unit delivered and it has been installed. I need to start
reading the amanda documentation this weekend. Meanwhile, I was wondering
if anyone using this unit or anything comparable would mind sharing some
of their experiences and/or any setup warnings.
Yes i have this unit
Hi
Amanda 2.4.5p1 on CentOS 4
Samba 3.0.21b
Windows 2003 SP1
The above setup worked fine 'out of the box' and has been running for
about 6 months or so. Came in to find that one of the backups was taking
ages and when it did finish the samba shares were failing. Looking in
the debug i can
Note the time betwen the first message (0.477) and the next and final
messages (24570.113).
This seems like the problem (solution) described here:
http://wiki.zmanda.com/index.php/Amdump:_mesg_read:_Connection_reset_by_peer
thanks - will see if that helps - There is no firewall between
Hi
Using 2.4.5p1 on linux and wondering if its possible to exclude a
directory from the backup using dump? I presume not and if not what
would be the inpact of not having a holding disk?
Scenerio is that i'm backing up a box and one of the partitions contains
data that has to be backed up
Hi
Testing a restore on the above config i have found this error. Backups
run fine but this is the error when trying to do a restore on it -
Anyone seen it before as i have not come accross this - Restore is being
attempted NOT on the same server that did the backup
amrestore: 53:
What OS and dump version was the data backed up from? What OS and dump version
are you trying to restore to?
In general, the dump type (xfsdump, vdump, etc.) and sometimes even the
version must be the same for backup and restore. This is an unfortunate
consequence of Amanda's use of native
What OS and dump version was the data backed up from? What OS and dump version
are you trying to restore to?
In general, the dump type (xfsdump, vdump, etc.) and sometimes even the
version must be the same for backup and restore. This is an unfortunate
consequence of Amanda's use of native
server that ran the backup
Linux 2.4.21-27.0.2.ELsmp
dump 0.4b37
client that got backed up
Linux 2.6.9-22.ELsmp
dump 0.4b39
sorry to reply to myself here but on another test
client
Linux 2.4.20
dump 0.4b27
and the same server did a succesful restore so it seems that if the
client version
and the same server did a succesful restore so it seems that if the
client version of dump is higher than the server the restore barfs
however the opposite appears to give a good restore -
Looks like i'm going to have to install myself a new server box with
dump 0.4b39 so get around this
OK thanks - I have increased the etimeout to 2400 seconds and also
changed the udp timeout within checkpoint to also be 2400 seconds so
i'll see how the run goes tonight
everything was fine today - no estimate timeout
thanks for the pointer
Hi
Server is 2.4.5 and client is now 2.4.5p1 both on CentOS
I use Amanda and have done for years with no issues setting up etc - I
can pretty much set up with my eyes closed now!! Amanda rocks...
But i'm getting a slightly strange error with a large partition. The
partition in question is
Look in /tmp/amanda/sendsize*debug and/or amandad*debug to see how long
the estimate is actually taking. Also, what do your iptables rules look
like on the server?
thanks - iptables are not being used, local firewall is off
sendsize degug is below and looks OK
# more
Yep. So you can just increase etimeout and/or figure out why
/sbin/dump 1Ssf 1048576 - /dev/sda5 is taking so long.
OK thanks - I have increased the etimeout to 2400 seconds and also
changed the udp timeout within checkpoint to also be 2400 seconds so
i'll see how the run goes tonight
Anyone got a tape type for an LTO-2 please?
thanks
PROTECTED] conto di Tom Brown
Inviato: mercoledì 29 giugno 2005 10.25
A: amanda-users
Oggetto: LTO-2 - Tape Type
Anyone got a tape type for an LTO-2 please?
thanks
Geert Uytterhoeven wrote:
On Wed, 8 Jun 2005, Jon LaBadie wrote:
On Wed, Jun 08, 2005 at 01:43:25PM +0100, Tom Brown wrote:
Not entirely and only related to amanda but i'm sure people have done
this before so here we go ;)
Linux amanda server (WBEL4) and its using filedriver for virtual
Hi
Not entirely and only related to amanda but i'm sure people have done
this before so here we go ;)
Linux amanda server (WBEL4) and its using filedriver for virtual tapes
as client does not want to spend $$$ on an LTO3 drive - a LOT of data here.
So anyone used USB2/Firewire external
I tried this:
--- client-src/sendbackup-gnutar.c.orig 2005-05-20 12:46:49.0 +0200
+++ client-src/sendbackup-gnutar.c 2005-05-20 12:31:03.0 +0200
@@ -73,6 +73,7 @@
AM_NORMAL_RE(^[Aa]dded interface),
AM_NORMAL_RE(^session request to ),
AM_NORMAL_RE(^tar: dumped
Type something on the client: you should see the letters on the other
side. Wait some time, and type something on the other program, and
see if the letters appear on the opposite program again.
Some experiment with how long to wait before answering should give
you an idea if it is a timing
Hi
Clients are all RH 7.3 or WhiteBox respin 2
Server is 2.4.4p4 running on whitebox respin 2
My amchecks un fine and without issue however i have come in on 2
morning snow to find that some of the clients failed. The actual fails
have occurred on different clients, ie some that failed 2 nights
Have a look on that client in /tmp/amanda, look for the files
sendsize.DATETIME.debug and see how long the estimate did take.
The first line of the file is the start time and the last line is the
finish time. How long did it really take? You many have to
change the etimeout parameter in
thanks all!
Tom
:
On Sat, May 14, 2005 at 05:29:10PM -0400, Joshua Baker-LePain enlightened us:
For the first time ever i have to backup a machine over the 'internet' -
This client is using iptables as its firewall. Does anyone have an iptables
rule they would like to share that would allow amanda
Hi
For the first time ever i have to backup a machine over the 'internet' -
This client is using iptables as its firewall. Does anyone have an iptables
rule they would like to share that would allow amanda through to be able to
backup this client?
thanks
Jack$on wrote:
hi.
Thankx to everyone!
currently I'm recompile my amanda, with my tar script.
shutdown/startup schema good working now I'm replace start/shop of
my Oracle DB to a switching DB in switching out hot backup mode...
I'm reconfigure my Oracle DB, change archive_log_dest to another
Hi
Using the above fine for ann Unix type hosts and of these tar and dump
based backups work fine.
Just tried to backup my first windows partition last night and it seems
to have worked but the dump ran with 'strange' - Can anyone point me in
the direction of what might be wrong?
FAILED AND
Hi
Posted earlier about a 'strange' report to do with a windows partition.
I'm trying to restore this partition to see what made it onto tape.
The issue i'm having is that amanda is ignoring this partition and
skipping it.
eg
amrestore -p /dev/nst0 titan \\printserver\hyperion | tar xvfp -
--
try titan //printserver/hyperion
Ah yes - its been a long week!
Thanks!
FAILED AND STRANGE DUMP DETAILS:
/-- titan //printserver/hyperion lev 0 STRANGE
sendbackup: start [titan://printserver/hyperion level 0]
sendbackup: info BACKUP=/opt/samba/bin/smbclient
sendbackup: info RECOVER_CMD=/opt/samba/bin/smbclient -f... -
sendbackup: info end
? [2005/02/24 00:46:52,
We're looking at increasing our backup capacity, and I'm wondering if
anyone
has any recommendations for a rackable tape changer, with about a 9 tape
capacity (I'm thinking LTO tapes) and a SCSI interface.
Anything at all would help; I'm especially interested in such devices that
you are
So, does anyone have any suggestions, good (or bad) experiences, or
other advice? Reliability is obviously by far the most important
thing... I'm also curious as to whether people favour internal or
external drives?
we moved from DDS4 to LTO when we outgrew our needs - IMHO LTO rocks and i
Actually Gene, for this drive disabling hardware compression isn't
necessary. It's an LTO/Ultrium drive, and those are actually smart enough
to not compress already compressed data. Notice (below) how he still gets
the full 100GB native capacity? With those drives, you get the best of
both
Does anyone know of any step by step how-to's that deal with using the
exclude file option with amanda on tar based backups?
thanks
have 2 seperate amanda configs and run some of the DLE's on one config to
one drive and the rest on the other config on the other drive
that way you can have the whole lot backup to both drives on its own.
I do this and it works great
- Original Message -
From: FXbio MendonXa
Hi,
2.4.4 server
2.4.4p2 client
Both on RedHat 7.3
I'm trying to get a new checkpoint firewall of mine backed up in the manner
i have many times before. I have installed Amanda server and client at least
50 times now with minimal fuss.
However i'm getting the following error and am wondering if
Amanda compiles in the location of the tar that it finds first at
configure time, so it must be finding that one. You can override that
with a command line option (to configure, I mean).
ah OK - In that case then i will recompile amanda
thanks
I came to my weekly autoloader change and noticed 'Clean Required' on the
panel. The changer is a 8 slot DDS4 changer and slot 8 houses the cleaning
tape.
I ran
$ amtape clean
and got
amtape: device 8 not clean: Cleaning Cartridge Installed and Ejected
I'm not actually there now, did
Rather than doing a lot more trial and error, I was hoping someone here
could quickly tell me what values I need or what documentation to look
at so amanda does a full backup every night.
use comp-lev0 as your dump type.
define dumptype comp-lev0 {
global
comment very important
Hi list
Is it possible to have amanda allways do a level 0 to a particular tape?
say i have 7 tapes i would like the normal run on 6 of them shich may
include level 0's but when it comes to one tape allways do a level 0 to this
tape?
Is that possible?
thanks
I don't understand why amcheck is saying amdump or amflush is running when
no process related to amanda is running
Can anybody suggest me what to do?
kill the processes and then run amcleanup
Title: tapes looking their Amanda labels
Did you use that tape to do an amtapetype at
all?
If so that would wipe the label
Tom
- Original Message -
From:
Henson, George Mr JMLFDC
To: Amanda List (E-mail)
Sent: Friday, January 16, 2004 2:33
PM
Subject: tapes
Hi,
I'm trying to restore from one machine onto another - The backup was created
on a linux box running 2.4.4p1 and the backup runs fine from what i can
tell.
If i transfer one of the tapes from the autochanger and put it into a
different machine with another tape drive attached and try and
IIRC, amrestore, having no idea about the original config ..., reads the
32KB amanda header (the 32768 offset noted above) to see if tar or dump
was used and if compression was used.
I'd look at that header. You can use mt to position at the start of
file 3 on the tape, then dd a 32K chunk
However i just tried to restore onto another box that uses the same
autoloader as the machine that made the backup.
The restore worked without issue - I therefore think this is actually a
hardware issue with either the drive or cable.
I should have said same make and model of autoloader -
$amflush config
or alter the config/tapelist file so that the required OurName-C-Mon is at
the bottom (although this is less desirable)
thanks
Hello,
We have a four-week, five days per week cycle:
dumpcycle 7 days
runspercycle 5
tapecycle 20 tapes
These twenty tapes are
We are building an amanda backup server and have a question regarding
memory requirements. My guess is that Amanda is more processor
intensive than memory intensive. Is this correct? For a dedicated
backup server that won't be doing much of anything else, is 512MB of
memory enough?
i
and if I try mt -f /dev/sg0 offline
/dev/sg0: Permission denied
Thanks for the help. Bye
what happens if you ls -l /dev/sg*
who owns and what perms are on /dev/sg0?
thanks
Hi,
My amanda server for my DMZ ate its HDD today so i've been busy rebuilding
it - It has a HP autoloader and a single AIT-2 drive in it to run 2
different a,anda configs.
The single drive seems fine - I'm having issues with the changer.
when i run an amcheck on this config i get..
Hi,
My amanda server for my DMZ ate its HDD today so i've been busy rebuilding
it - It has a HP autoloader and a single AIT-2 drive in it to run 2
different a,anda configs.
The single drive seems fine - I'm having issues with the changer.
when i run an amcheck on this config i get..
I recently posted a question about my attempts to get 2.4.4p1 running on a
RedHat 7.0 box. I probably didn't mention that the plan was to go
tapeless.
This project didn't work and I can explain exactly why so others won't
bump
into the same wall I did.
2.4.4p1 compiles just fine on RedHat
st0: Error with sense data: Current st09:00: sense key
Medium Error
Additional sense indicates Write error
mt: /dev/tape: Input/Output error
If I try: mt erase /dev/st0, it return me:
st0: Error with sense data: Current st09:00: sense key
amrestore: could not open /dev/nst0: Permission denied
amidxtaped: time 0.010: amrestore terminated normally with status: 2
amidxtaped: time 0.010: rewinding tape ...
amidxtaped: time 0.010: tape_rewind: tape open: /dev/nst0: Permission
denied
amidxtaped: time 0.010: pid 31743 finish time
I put this device and controller in a Windows2000 machine and it
worked fine. When I used it on Windows, it asked me to format the media
so,
I think I need to format the media on Linux too but, how to do it ?
did you use exactly the same cables etc?
whats the output from dmesg that
Yes, the same cables, controller and device. The dmesg identify the drive.
can you show us please
thanks
Hi,
I've been backing up and restoring with a mix of tar and dump for about 3
years now without any major issues.
I am currently testing the restore of a system prior to me deploying into
production.
I'm backing up this box with tar as i only want a couple of directorys to
end up on tape.
I am
Any suggestions on why it is not recognising the label ?
is your drive new/old/dirty/clean?
what about SCSI termination? have you tried a different cable?
has this drive/cable setup ever worked?
Tom
In case anyone requires this in the future
define tapetype AIT-2 {
comment just produced by tapetype prog (hardware compression off)
length 48898 mbytes
filemark 2788 kbytes
speed 7710 kps
}
Tom
tapecycle 20 tapes:
number of tapes to use per dumpcycle of 2 weeks. 10 tapes X 2 dumpcycles
=
20 tapes.
Yes, but you really should have an extra tape or two in there to lessen
the chance of a failed backup overwriting your last full backup. You
should really consider doubling that
Tom,
you don't have it as dumpcycle*runspercycle.
In your two examples you have it as runspercycle period.
To demostrate the problem consider the simplest situation.
A dumpcycle of 1 day, a runspercycle of 1, and a tapecycle of 1.
Each amdump uses the ONLY tape containing the last level
Hi,
I have a machine that does a DMZ backup with a DDS4 autoloader on it. I now
also need to use this machine to backup a single machine onto a AIT2 single
drive.
I have installed the drive and it is recognised.
dmesg says..
Vendor: SONY Model: SDX-500C Rev: 010c
Type:
I have a machine that does a DMZ backup with a DDS4 autoloader on it. I
now
also need to use this machine to backup a single machine onto a AIT2
single
drive.
I have installed the drive and it is recognised.
dmesg says..
Vendor: SONY Model: SDX-500C Rev: 010c
Type:
Make sure that each amanda.conf specifies a different changerfile.
Each changerfile needs chgtapedev set to a different tape drive
(just use the single digit [0,1,2...]).
If both tape drives are in the same changer, you need to specify a
different
range of slots for each amanda config.
On Mon, Oct 13, 2003 at 04:18:28PM +0100, Tom Brown enlightened us:
Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full
Storage Element 2:Full
Storage Element 3:Full
Storage Element 4:Full
- Original Message -
From: Frank Smith [EMAIL PROTECTED]
To: Tom Brown [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, October 13, 2003 4:26 PM
Subject: Re: 2 devices on one machine
--On Monday, October 13, 2003 16:18:28 +0100 Tom Brown
[EMAIL PROTECTED] wrote:
to follow up
Hi group,
As subject - which version of tar should i specify when building my clients?
I'm getting a timeout error occasionally on one of my clients using tar and
just want to eliminate the tar version as i know one is broken with amanda.
thanks
Tom
As subject - which version of tar should i specify when building my
clients?
I'm getting a timeout error occasionally on one of my clients using tar
and
just want to eliminate the tar version as i know one is broken with
amanda.
gnutar 1.13.19 or 1.13.25. The latter is the latest alpha
When I run the configure script I get the following error:
[EMAIL PROTECTED] ./configure
checking build system type... hppa2.0w-hp-hpux11.00
checking host system type... hppa2.0w-hp-hpux11.00
checking target system type... hppa2.0w-hp-hpux11.00
checking for a BSD-compatible install...
Hi,
One of my systems that backs up 4 clients last night failed on 1 of the
clients. The other 3 were ok. I have gone through and checked everything,
restarted xinetd on the client, but still the same error.
Has anyone seen
WARNING: : selfcheck reply timed out
This is on amanda-2.4.4 on
I have been useing amanda for a few weeks now and am pleased with the
results. Though I have had some problems with the labels on the amanda
tapes. I have a VXA tape drive and V17 tapes and the labels are
getting erased at random times???
Is this a faulty tape issue or one of my settings?
- Original Message -
From: Mikkel Gadegaard
To: [EMAIL PROTECTED]
Sent: Friday, July 04, 2003 3:20 PM
Subject: repost (still need some help) :-)
I had amanda up and running only to discover that the machine acting as host
didn't have enough HD capacity to run Amanda smoothly. The
can anyone advise me how to determine the block size of this tape?
mt -f /dev/... status
reports the blocksize that the device is configured (not that tape
that is in it).
If you read a tape, specify a blocksize larger than then one on
tape (maybe it has to be an exact multiple of it,
Hi,
Trying to label a set of 6 tapes in a DDS4 autoloader. For some reason
after
i load the first tape into the slot and try and do a amlabel the tape is
unloaded and another one loaded into the slot instead. See below.
Any idea why this might be?
Tom
$ mtx -f /dev/sg2 status
Storage
Hi,
This is the third amanda installation i have been working on in the last 2
weeks so apology for all the problems i've been posting to the list.
I'm currently installing a system to backup our local LAN to a single LTO-1
drive so no changer config to worry about.
I have configured amanda and
When i run amtapetype i get the following
$ amtapetype -e 100gig -f /dev/nst0
Writing 1024 Mbyte compresseable data: 47 sec
Estimate phase 2...amtapetype: could not write any data in this pass:
short
write
and i've just found this in the messages for this machine.
Jun 24 14:24:20
cannot read/write /usr/local/var/Amanda/gnutar-lists: No such file or
directory
Indeed there is no such file or directory. My gnutar-lists is located
in /var/lib/Amanda. What shall I do? I am also guessing that Amanda is
going to want read/write other files and folders in the
Hi,
I have just transferred my kit over to the production env. All was working
fine on dev.
This is on a RedHat machine with a 2.4.18 kernel and amanda 2.4.4
dmesg says
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4
Adaptec 2940 Ultra SCSI adapter
aic7880:
Has that kernel been recompiled to 'scan all luns'?
it was yes - and it is now running on 2.4.28
dmesg says
There should be a few more lines below the above clip that show what
st* devices were assigned. From the above, I'd guess the changer
device is now /dev/sg3 maybe. Experiment a bit,
Does anyone have a tapetype for this drive? I'm running amtapetype but its
been running for about 20 hours and has not yet finished!
The drive is a
Vendor: IBM Model: ULTRIUM-TD1 Rev: 1CSG
thanks
Tom
in 9687 files in 27409 seconds (short write)
wrote 2930929 32Kb blocks in 17898 files..
so i think it might be nearly finished?
Tom
Tom Brown wrote:
Does anyone have a tapetype for this drive? I'm running amtapetype but
its
been running for about 20 hours and has not yet finished!
Did you
its finished!
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression on)
length 104017 mbytes
filemark 532 kbytes
speed 2894 kps
}
does that look right for LTO1?
Tom
Tom Brown wrote:
I didn't give it an estimate no - If i were
what kind of speed should it be and how can i increase this write speed?
speed should be much higher
regards,
gregor
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Tom Brown
Sent: Thursday, June 19, 2003 11:37 AM
To: Paul Bijnens
Cc: AMANDA
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Tom Brown
Sent: Thursday, June 19, 2003 12:31 PM
To: Gregor Ibic; AMANDA Users
Subject: Re: LTO1 tapetype
what kind of speed should it be and how can i increase this write speed?
Mbyte uncompresseable data: 77 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 102400 Mbyte: 3112 sec = 0 h 51 min
wrote 1966080 32Kb blocks in 60 files
Tom Brown wrote:
do you know what settings on the drive can effect this? Its preyy much
as it
was shipped
Possibly rerun amtapetype (as Paul suggested) with an reasonable
estimate
so
that it writes 100x fewer separate files and writes much larger files
that
stream for a longer time at full write speed.
From amanda's perspective it doesn't matter. The speed parameter is
printed for
Fuji's documentation for tapes shows two IBM models, the rated
speeds for the models are 7.5 and 15 MB/s.
Your 12.9 seems reasonable. Far cry from the previous 2.9 :)
Is the comment correct, was HW compression ON? Should not have been.
A tapetype report should show the native capacity.
I've got a bit of a strage issue here. All tapes have been labelled and i
did a couple of test runs with all disks in the disklist commented out so it
just ran through its cycle and all 7 tapes were fine.
that was yesterday
today doing an amcheck i am told that tape01 is not am amanda tape when
ISTR you saying this is Linux? If so, then 'mt compression 0' should do
it. You can check the status by pointing 'tapeinfo' (from the mtx
distribution) at the generic device associated with your tape drive.
It is linux yes - will amanda use this command before writing to this device
when
I had to rip my drive out to change some dip switches - have a look at the
spec for the drive before you do anything as drastic as that.
I have used Joshua's suggestion of putting a mt -f /dev/nst0 compression 0
at the very top of my script that runs amdump.
So far so good
Tom
I am probably missing a clue in the configuration file. After trying
to get any of the changers to work with both drives AND Barcode
reader AND the robot my brain has been slowly oozing from my
ears.perhaps you need BOTH
offlinestatus=1OFFLINE_BEFORE_UNLOAD=1
Was that the tape in the drive when you did your tapetypes?
ahhh - erm i can't remember actually yes i can and no it wasn't -
the last tape was as...
amcheck-server: slot 7: date 20030618 label gthost07 (first labelstr match)
amcheck-server: slot 1: not an amanda tape
the tape 07 was
Many drives have an led tally on the front to indicate when the
comnpressor is active.
And no, amanda will not use it, and in fact cannot because once a lock
on the drive is obtained, its not released until done. Turning it
off is best done via the dip switch or jumper settings programming
I also have such a situation!
if I try to relabel it, it say that the tape is already labeled. But this
is
probably
read from tapelist file and not really from the tape.
version 2.4.4-20030605
chg-zd-mtx
i have a theory to my problem but not 100% certain yet.
i have, today, run a
Hi,
NEC autloader with 10 slots and IBM ultrium tape drive.
mtx version 1.2.17
amanda-2.4.4
dmesg -
Vendor: IBM Model: ULTRIUM-TD1 Rev: 1CSG
Type: Sequential-Access ANSI SCSI revision: 03
(scsi0:A:2): 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Hi Tom,
Your changer file is not use.
What is the full path of your changer file?
What's your changerfile in amanda.conf?
Hi,
It seems i made a silly mistake! Everything was as it should be in
amanda.conf e.g.
runtapes 1 # number of tapes to be used in a single run of
amdump
I had a similar problem with a Sony SDX-500C drive. I found the changer
script wasn't waiting for the tape to really become ready. Using 2.4.4,
chg-zd-mtx and adding this to changer.conf solved the problem:
offlinestatus=1 Set to 0 if 'mt status' gives an
#
I had a similar problem with a Sony SDX-500C drive. I found the changer
script wasn't waiting for the tape to really become ready. Using 2.4.4,
chg-zd-mtx and adding this to changer.conf solved the problem:
offlinestatus=1 Set to 0 if 'mt status' gives an
#
$ more chg-zd-mtx.20030617110112.debug
chg-zd-mtx: debug 1 pid 2176 ruid 11 euid 11: start at Tue Jun 17 11:01:12
2003
11:01:12 Arg info:
$# = 2
$0 = /opt/amanda-2.4.4/libexec/chg-zd-mtx
$1 = -slot
$2 = next
11:01:12 Running: /opt/mtx/sbin/mtx status
Hi,
Trying to label a set of 6 tapes in a DDS4 autoloader. For some reason after
i load the first tape into the slot and try and do a amlabel the tape is
unloaded and another one loaded into the slot instead. See below.
Any idea why this might be?
Tom
$ mtx -f /dev/sg2 status
Storage Changer
1 - 100 of 115 matches
Mail list logo
