Re: linux, lvm, and snapshots
Hi, Solaris keeps a file tracking changes that the docs say can grow quite large. As you keep your snapshots for a full day, what types of sizes do you see; any problems? Any problems at all. To get an idea of how much additional space is needed for the snapshot, just have a look at an amanda level 1 dump, one day after a level 0 dump. We have changes less than 10% of the filesystem size. So: We have a home-share which should be backed up: /dev/dsk/c1t2d0s67741365 5844894 150940380%/home We added an extra drive for tracking the changes: /dev/dsk/c1t2d0s7 961623 70794 842748 8%/backingstore The snapshot is then mounted: /dev/fssnap/07741365 5842323 151197480%/snapshot/home The home is shared via nfs as /homes/pooh and via samba ([homes]-share). The snapshot is shared equally as /snapshots/homes/pooh. This has the great advantage that it's now easy to share the snapshot via samba: We use 'path = /snapshots/%H'. Also, what do you do for names in the disklist and during recovery. Of course, they differ. We back up the snapshot, but we want to restore into the normal filesystem. This requires one extra command: - cd /home - start amrecover - enter 'setdisk /snapshot/home' and that's it. Are the names unique to the mountpoint of the snapshot or still refer to the original locations. How about recoveries directly to the original directory tree, is that possible as you are backing up a different mount point than the active FS. See the above. Greetings, Christopher -- == Dipl.-Ing. Christopher Odenbach HNI Rechnerbetrieb [EMAIL PROTECTED] Tel.: +49 5251 60 6215 ==
[no subject]
subscribe [EMAIL PROTECTED]
'insert'-error
hi all, i have installed and configured amanda-2.4.3 for seagate-travan tapes but i get the following looping error when i try to use any of amanda commands. while getting these messages on the console, 'kernel: ide-tape: Reached idetape_chrdev_open' is recorded in /var/log/messages. i have search the archive but couldn't find help. by the way, i can write to and read from the tapes by using cat. so, the problem is not with the tape or the medium, but with amanda. with tapetype program, the resulting type seems to be very slow and the length is much smaller than the specification of the tape ( 1 gb vs 10 gb ). so, there also seems to be some problem out of amanda. i have used /dev/ht0 and /dev/nth0, but the result is the same. in dmesg, tape is claimed to be connected to /dev/ht0. thanks for any help/comments
Solaris 8 Overland Tape changer config
Hi I know this is well trodden ground, believe me I've scanned the emails, please could someone tell me where I'm going wrong? I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda 2.4.3 mtx 1.2.17 I've identified the correct tape device, tested by :- $mt -f /dev/rmt/1n status Quantum DLT7000 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 I've used sgen to get a device for the changer :- $./mtx status Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full The changer has a cleaning tape in slot 10. amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do I created a file chg-zd-mtx.conf containing :- firstslot=1 lastslot=9 cleanslot=10 Trying to follow the chg-zd-mtx instructions, I try :- $ ./chg-zd-mtx -info none could not determine current slot Logfile contains :- chg-zd-mtx: debug 1 pid 11255 ruid 0 euid 0: start at Mon Mar 3 14:31:47 2003 14:31:47 Arg info: $# = 1 $0 = ./chg-zd-mtx $1 = -info 14:31:47 Running: mtx status 14:31:47 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full 14:31:47 Config info: firstslot = 1 lastslot = 9 cleanslot = 10 cleancycle = 120 offline_before_unload = 0 unloadpause = 0 autoclean = 0 autocleancount = 99 havereader = 0 driveslot = 1 poll_drive_ready = 3 max_drive_wait = 120 14:31:47 WARNING - current slot 1 not available, setting current slot to next slot (2) 14:31:47 Exit (2) - none could not determine current slot chg-zd-mtx: pid 11340 finish time Mon Mar 3 14:31:47 2003 Now, checking chg-zd-mtx-slot, it contains 1, and doesn't change! (I then verified that the file was owned by backup, the amanda user, which it is, and that backup owns the entire config directory. Any help would be MUCH appreciated. Many thanks Nigel Barker
Re: 'insert'-error
[Posted and Cc'ed] On Mon, Mar 03, 2003 at 03:58:08PM +0200, Sinan KALKAN wrote: i have installed and configured amanda-2.4.3 for seagate-travan tapes but i get the following looping error when i try to use any of amanda commands. while getting these messages on the console, 'kernel: ide-tape: Reached idetape_chrdev_open' is recorded in /var/log/messages. by the way, i can write to and read from the tapes by using cat. so, the problem is not with the tape or the medium, but with amanda. Not clear yet. Reading/writing your tapes with cat(1) is a little unconventional. Try reading/writing your tapes with GNU tar/dd(1), and manipulating them with mt(1) (status, fsf, rewind). If that all works flawlessly, then maybe you've got an Amanda problem. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
RE: Mtx and chg-zd-mtx
A little more information. I f I put one tape in the last slot, then the chg-zd-mtx -info show the right values, but if I change it back to another slot, then it stop working again, and show the number of the last slot use, for example, if I put the last tape into slot 7 I receive: 1 7 1 and if I put the last one into 6 I receive: 1 6 1 Any thoughts? Kind Regards. _ Pablo Jejcic Smartweb Senior system Administrator School of Computing - Robert Gordon University [EMAIL PROTECTED] T:44-(0)1224-262797 F:44-(0)1224-262790 _ ``The nice thing about standards is that there are so many to choose from. And if you really don't like all the standards you just have to wait another year until the one arises you are looking for.'' A. Tanenbaum, ``Introduction to Computer Networks' _ -Original Message- From: Pablo Jejcic [mailto:[EMAIL PROTECTED] Sent: 28 February 2003 16:09 To: 'Joshua Baker-LePain' Cc: '[EMAIL PROTECTED]' Subject: RE: Mtx and chg-zd-mtx If I unload all of them, nothing change:( Kind Regards. _ Pablo Jejcic Smartweb Senior system Administrator School of Computing - Robert Gordon University [EMAIL PROTECTED] T:44-(0)1224-262797 F:44-(0)1224-262790 _ ``The nice thing about standards is that there are so many to choose from. And if you really don't like all the standards you just have to wait another year until the one arises you are looking for.'' A. Tanenbaum, ``Introduction to Computer Networks' _ -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] Sent: 28 February 2003 16:05 To: Pablo Jejcic Cc: [EMAIL PROTECTED] Subject: RE: Mtx and chg-zd-mtx On Fri, 28 Feb 2003 at 3:58pm, Pablo Jejcic wrote firstslot=1 First storage slot (element) -- required lastslot=9 Last storage slot (element) -- required cleanslot=-1 Slot with cleaner tape -- default is -1 # driveslot=0 Drive slot number. Defaults to the On Fri, 28 Feb 2003 at 3:07pm, Pablo Jejcic wrote bash-2.05# mtx status Storage Changer /dev/changer:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 5 Loaded):VolumeTag = Storage Element 1:Full :VolumeTag= Storage Element 2:Full :VolumeTag= Storage Element 3:Full :VolumeTag= Storage Element 4:Full :VolumeTag= Storage Element 5:Empty:VolumeTag= Storage Element 6:Full :VolumeTag= Storage Element 7:Empty:VolumeTag= Storage Element 8:Empty:VolumeTag= Storage Element 9:Empty:VolumeTag= But if I use chg-zd-mtx, I get: bash-2.05# /usr/local/libexec/chg-zd-mtx -info 5 6 1 It's rather suspicious that the second number, rather than corresponding to the number of slots you have, corresponds to the number of tapes you have loaded. What happens if you load one more tape (or take one out)? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
More stupid n00bie questions....maybe
Hi all, I searched the faq-o-matic and googled this, but there didnt seem to be any definitive answers. My amdumps seem to be working fine, but when I try to do an amrecover and extract a single file, I get the errors below. As a side note, I have tried using amrestore, to dump the entire backup that contains the file I was extracting, and that works just fine...no problem.(I might mention that this is a rather large dumpif that makes any difference...I will try a single file recover from a smaller dump as a test). Any ideas from the vets? John When I run the amrecover proggy: ## Added /vsmhii.dat amrecover extract Extracting files using tape drive /dev/nst0 on host localhost. The following tapes are needed: UBS-GAM002 Restoring files into directory /tmp/foo Continue? [Y/n]: y Load tape UBS-GAM002 now Continue? [Y/n]: y EOF, check amidxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue? [Y/n]: n amrecover quit 200 Good bye. # From dmesg I get this: ## st0: Error with sense data: Current st09:00: sense key Illegal Request Additional sense indicates End-of-data detected ## And in the debug output file amidxtaped.X.debug: ## amidxtaped: debug 1 pid 5339 ruid 34 euid 34 start time Mon Mar 3 11:12:47 2003 amidxtaped: version 2.4.2p2 SECURITY USER root bsd security: remote host localhost user root local user backup amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/nst0 stlucia ^/nfsbackups/eros$ 20030227 Ready to execv amrestore with: path = /usr/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = /dev/nst0 argv[4] = stlucia argv[5] = ^/nfsbackups/eros$ argv[6] = 20030227 amrestore: error reading file header: Input/output error amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: done amidxtaped: pid 5339 finish time Mon Mar 3 11:13:21 2003 ## ___ This e-mail, and any attachments, are confidential and access by anyone other than the addressee(s) is unauthorized. The security of e-mail communication cannot be guaranteed and neither UBS AG, nor any of its affiliates, accepts liability for claims arising as a result of the use of this medium to transmit messages from or to UBS AG, or any of its affiliates. If you are not the intended recipient, any disclosure, copying, forwarding or distribution of this e-mail is prohibited. We would be grateful if you would notify the sender of any instances where this occurs.
Re: Solaris 8 Overland Tape changer config
The first to do is to set your driveslot correctly, yours is 0. Jean-Louis On Mon, Mar 03, 2003 at 02:54:11PM -, Nigel Barker wrote: Hi I know this is well trodden ground, believe me I've scanned the emails, please could someone tell me where I'm going wrong? I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda2.4.3 mtx 1.2.17 I've identified the correct tape device, tested by :- $mt -f /dev/rmt/1n status Quantum DLT7000 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 I've used sgen to get a device for the changer :- $./mtx status Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full The changer has a cleaning tape in slot 10. amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do I created a file chg-zd-mtx.conf containing :- firstslot=1 lastslot=9 cleanslot=10 Trying to follow the chg-zd-mtx instructions, I try :- $ ./chg-zd-mtx -info none could not determine current slot Logfile contains :- chg-zd-mtx: debug 1 pid 11255 ruid 0 euid 0: start at Mon Mar 3 14:31:47 2003 14:31:47 Arg info: $# = 1 $0 = ./chg-zd-mtx $1 = -info 14:31:47 Running: mtx status 14:31:47 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full 14:31:47 Config info: firstslot = 1 lastslot = 9 cleanslot = 10 cleancycle = 120 offline_before_unload = 0 unloadpause = 0 autoclean = 0 autocleancount = 99 havereader = 0 driveslot = 1 poll_drive_ready = 3 max_drive_wait = 120 14:31:47 WARNING - current slot 1 not available, setting current slot to next slot (2) 14:31:47 Exit (2) - none could not determine current slot chg-zd-mtx: pid 11340 finish time Mon Mar 3 14:31:47 2003 Now, checking chg-zd-mtx-slot, it contains 1, and doesn't change! (I then verified that the file was owned by backup, the amanda user, which it is, and that backup owns the entire config directory. Any help would be MUCH appreciated. Many thanks Nigel Barker -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Solaris 8 Overland Tape changer config
[Posted and Cc'ed] On Mon, Mar 03, 2003 at 02:54:11PM -, Nigel Barker wrote: I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda2.4.3 mtx 1.2.17 amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do ^ I assume the real amanda.conf doesn't have this typo. Trying to follow the chg-zd-mtx instructions, I try :- $ ./chg-zd-mtx -info none could not determine current slot You seem to have installed mtx and chg-zd-mtx in /usr/local/share/amanda/Daily, make sure they are also installed where amanda's $PATH can find them. Then take the debugging to the next level with: $ sh -x chg-zd-mtx -info -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
RE: Solaris 8 Overland Tape changer config
Jean-Louis Thanks for that :) I can now run through the mtx tests, as per chg-zd-mtx, which feels like a big step in the right direction. Moving onto amtape... $ amtape Daily reset amtape: could not reset changer: no slots available I'm looking through the script, but struggling to see what's wrong with my config. Cheers Nige -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: 03 March 2003 16:29 To: Nigel Barker Cc: [EMAIL PROTECTED] Subject: Re: Solaris 8 Overland Tape changer config The first to do is to set your driveslot correctly, yours is 0. Jean-Louis On Mon, Mar 03, 2003 at 02:54:11PM -, Nigel Barker wrote: Hi I know this is well trodden ground, believe me I've scanned the emails, please could someone tell me where I'm going wrong? I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda2.4.3 mtx 1.2.17 I've identified the correct tape device, tested by :- $mt -f /dev/rmt/1n status Quantum DLT7000 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 I've used sgen to get a device for the changer :- $./mtx status Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full The changer has a cleaning tape in slot 10. amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do I created a file chg-zd-mtx.conf containing :- firstslot=1 lastslot=9 cleanslot=10 Trying to follow the chg-zd-mtx instructions, I try :- $ ./chg-zd-mtx -info none could not determine current slot Logfile contains :- chg-zd-mtx: debug 1 pid 11255 ruid 0 euid 0: start at Mon Mar 3 14:31:47 2003 14:31:47 Arg info: $# = 1 $0 = ./chg-zd-mtx $1 = -info 14:31:47 Running: mtx status 14:31:47 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full 14:31:47 Config info: firstslot = 1 lastslot = 9 cleanslot = 10 cleancycle = 120 offline_before_unload = 0 unloadpause = 0 autoclean = 0 autocleancount = 99 havereader = 0 driveslot = 1 poll_drive_ready = 3 max_drive_wait = 120 14:31:47 WARNING - current slot 1 not available, setting current slot to next slot (2) 14:31:47 Exit (2) - none could not determine current slot chg-zd-mtx: pid 11340 finish time Mon Mar 3 14:31:47 2003 Now, checking chg-zd-mtx-slot, it contains 1, and doesn't change! (I then verified that the file was owned by backup, the amanda user, which it is, and that backup owns the entire config directory. Any help would be MUCH appreciated. Many thanks Nigel Barker -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
amanda having trouble choosing next tape
The dumps were flushed to tape Indyme014. The next tape Amanda expects to use is: a new tape. [EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist 20030303 Indyme014 reuse 20030228 Indyme013 reuse 20030227 Indyme012 reuse 20030227 Indyme011 reuse 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse [EMAIL PROTECTED] root]# Why isn't it telling me it wants 001? -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
RE: Solaris 8 Overland Tape changer config
Jay
On Mon, Mar 03, 2003 at 02:54:11PM -, Nigel Barker wrote:
I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive.
Amanda 2.4.3
mtx 1.2.17
amanda.conf contains :-
tpchanger chg-zd-mtx
tapedev /dev/rmt/1n
changerfile /usr/local/share/amanda/Daily/chg-zd-mtx
changerdev /dev/scsi/cganger/c1t6do
^
I assume the real amanda.conf doesn't have this typo.
I copied it from the file, the typo was there, I've corrected it but it
hasn't changed the behaviour at all (which feels like a clue to me...)
Trying to follow the chg-zd-mtx instructions, I try :-
$ ./chg-zd-mtx -info
none could not determine current slot
You seem to have installed mtx and chg-zd-mtx in
/usr/local/share/amanda/Daily,
make sure they are also installed where amanda's $PATH can find them.
Where would these normally be installed?
mtx was in the user backup's PATH, chg-zd-mtx wasn't, but is now, no change)
Then take the debugging to the next level with:
$ sh -x chg-zd-mtx -info
Well, it produced a lot more info (attached), but having had a quick look
through I don't see what's going wrong.
Cheers
Nige
MT=//usr/bin/mt
MTF=-f
MTX=mtx
+ test -n
TMPDIR=/tmp/amanda
DBGDIR=/tmp/amanda
argv0=chg-zd-mtx
+ expr chg-zd-mtx : .*/\(.*\)
myname=
+ pwd
config=/usr/local/share/amanda/Daily
+ expr /usr/local/share/amanda/Daily : .*/\(.*\)
config=Daily
+ date +%H:%M:%S
ds=17:06:01
+ [ 0 -eq 0 -a -n 17:06:01 ]
+ echo 17:06:01
+ sed s/./ /g
logprefix=
internal_call=0
mtx_status_valid=0
slot_list=
prefix=/usr/local
exec_prefix=/usr/local
sbindir=/usr/local/sbin
libexecdir=/usr/local/libexec
PATH=/usr/local/sbin:/usr/local/libexec:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ucb:/usr/local/bin
+ export PATH
USE_VERSION_SUFFIXES=no
+ test no = yes
SUF=
+ amgetconf dbopen.chg-zd-mtx
+ grep -v BUGGY
DBGFILE=/tmp/amanda/chg-zd-mtx.20030303170601.debug
+ [ -z /tmp/amanda/chg-zd-mtx.20030303170601.debug ]
+ amgetconf changerfile
+ grep -v BUGGY
changerfile=/usr/local/share/amanda/Daily/chg-zd-mtx
+ [ -z /usr/local/share/amanda/Daily/chg-zd-mtx ]
+ amgetconf tapedev
+ grep -v BUGGY
tape=/dev/rmt/1n
+ [ -z /dev/rmt/1n ]
+ expr /dev/rmt/1n : null:
+ [ /dev/rmt/1n = /dev/null -o 0 -eq 5 ]
+ amgetconf changerdev
+ grep -v BUGGY
TAPE=/dev/scsi/changer/c1t6do
+ [ -z /dev/scsi/changer/c1t6do ]
+ [ /dev/scsi/changer/c1t6do = /dev/null ]
+ export TAPE
configfile=/usr/local/share/amanda/Daily/chg-zd-mtx.conf
cleanfile=/usr/local/share/amanda/Daily/chg-zd-mtx-clean
accessfile=/usr/local/share/amanda/Daily/chg-zd-mtx-access
slotfile=/usr/local/share/amanda/Daily/chg-zd-mtx-slot
labelfile=/usr/local/share/amanda/Daily/chg-zd-mtx-barcodes
+ [ ! -s /usr/local/share/amanda/Daily/chg-zd-mtx-clean ]
+ [ ! -s /usr/local/share/amanda/Daily/chg-zd-mtx-access ]
+ [ ! -s /usr/local/share/amanda/Daily/chg-zd-mtx-slot ]
+ [ ! -f /usr/local/share/amanda/Daily/chg-zd-mtx-barcodes ]
+ cat /usr/local/share/amanda/Daily/chg-zd-mtx-clean
cleancount=0
+ cat /usr/local/share/amanda/Daily/chg-zd-mtx-access
accesscount=2
varlist=
varlist= firstslot
varlist= firstslot lastslot
varlist= firstslot lastslot cleanslot
varlist= firstslot lastslot cleanslot cleancycle
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN autoclean
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN autoclean autocleancount
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN autoclean autocleancount havereader
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN autoclean autocleancount havereader
driveslot
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN autoclean autocleancount havereader
driveslot poll_drive_ready
varlist= firstslot lastslot cleanslot cleancycle OFFLINE_BEFORE_UNLOAD
offline_before_unload unloadpause AUTOCLEAN autoclean autocleancount havereader
driveslot poll_drive_ready max_drive_wait
+ cat /usr/local/share/amanda/Daily/chg-zd-mtx.conf
+ sed -n
# Ignore comment lines (anything starting with a #).
/^[ ]*#/d
# Find the first var=val line in the file, print the value and quit.
/^[ ]*firstslot[]*=[]*\([^ ][^ ]*\).*/ {
s/^[]*firstslot[]*=[]*\([^ ][^ ]*\).*/\1/p
q
}
val=1
+ eval firstslot=1
firstslot=1
+ sed -n
# Ignore comment lines (anything starting with
Re: amanda having trouble choosing next tape
[Posted and Cc'ed] On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote: The dumps were flushed to tape Indyme014. The next tape Amanda expects to use is: a new tape. [EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist 20030303 Indyme014 reuse 20030228 Indyme013 reuse 20030227 Indyme012 reuse 20030227 Indyme011 reuse 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse [EMAIL PROTECTED] root]# Why isn't it telling me it wants 001? Because tapecycle 14? -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: amanda having trouble choosing next tape
On Mon, 3 Mar 2003 at 9:20am, John Oliver wrote The dumps were flushed to tape Indyme014. The next tape Amanda expects to use is: a new tape. [EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist 20030303 Indyme014 reuse 20030228 Indyme013 reuse 20030227 Indyme012 reuse 20030227 Indyme011 reuse 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse [EMAIL PROTECTED] root]# Why isn't it telling me it wants 001? How big is your tapecycle? What does 'amadmin $CONFIG tape' say? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Solaris 8 Overland Tape changer config
On Mon, Mar 03, 2003 at 05:10:45PM -, Nigel Barker wrote: $ sh -x chg-zd-mtx -info Well, it produced a lot more info (attached), but having had a quick look through I don't see what's going wrong. + echo 17:06:02 Exit (0) - 2 9 1 + echo 2 9 1 2 9 1 Looks to me like it worked: Current slot = 2 Total slots = 9 Can go backwards = 1 (true) -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: amanda having trouble choosing next tape
On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote: The dumps were flushed to tape Indyme014. The next tape Amanda expects to use is: a new tape. [EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist 20030303 Indyme014 reuse 20030228 Indyme013 reuse 20030227 Indyme012 reuse 20030227 Indyme011 reuse 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse [EMAIL PROTECTED] root]# Why isn't it telling me it wants 001? I would reckon it's because you have tapecycle set to a number greater than 14 in your amanda.conf - If this is the case, amanda's going to ask for a new tape until it reaches this number. Looking back at one of your previous posts, you said: dumpcycle 1 week runspercycle 5 tapecycle 15 tapes If you set tapecycle to 14, amanda should ask for tape 001. Hope that helps, Simon.
Re: amanda having trouble choosing next tape
On Mon, Mar 03, 2003 at 05:57:14PM +, Simon Young wrote: On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote: The dumps were flushed to tape Indyme014. The next tape Amanda expects to use is: a new tape. [EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist 20030303 Indyme014 reuse 20030228 Indyme013 reuse 20030227 Indyme012 reuse 20030227 Indyme011 reuse 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse [EMAIL PROTECTED] root]# Why isn't it telling me it wants 001? I would reckon it's because you have tapecycle set to a number greater than 14 in your amanda.conf - If this is the case, amanda's going to ask for a new tape until it reaches this number. D'OH! Thanks... :-) -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Solaris 8 Overland Tape changer config
I may have been missing something in my config - something like an environmental variable, but I found that I wasn't able to run chg-zd-mtx successfully unless I was in the directory with the data information. That is, I configured amanda such that the chg-zd-mtx.* files where in the amanda config directory (/usr/local/etc/amanda/config) but the script was in the default /usr/local/libexec directory. In my case it was a matter of not locating the config files and I see from your execution line that you where probably in .../libexec. Hi I know this is well trodden ground, believe me I've scanned the emails, please could someone tell me where I'm going wrong? I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda2.4.3 mtx 1.2.17 I've identified the correct tape device, tested by :- $mt -f /dev/rmt/1n status Quantum DLT7000 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 I've used sgen to get a device for the changer :- $./mtx status Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full The changer has a cleaning tape in slot 10. amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do I created a file chg-zd-mtx.conf containing :- firstslot=1 lastslot=9 cleanslot=10 Trying to follow the chg-zd-mtx instructions, I try :- $ ./chg-zd-mtx -info none could not determine current slot Logfile contains :- chg-zd-mtx: debug 1 pid 11255 ruid 0 euid 0: start at Mon Mar 3 14:31:47 2003 14:31:47 Arg info: $# = 1 $0 = ./chg-zd-mtx $1 = -info 14:31:47 Running: mtx status 14:31:47 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c1t6d0:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full 14:31:47 Config info: firstslot = 1 lastslot = 9 cleanslot = 10 cleancycle = 120 offline_before_unload = 0 unloadpause = 0 autoclean = 0 autocleancount = 99 havereader = 0 driveslot = 1 poll_drive_ready = 3 max_drive_wait = 120 14:31:47 WARNING - current slot 1 not available, setting current slot to next slot (2) 14:31:47 Exit (2) - none could not determine current slot chg-zd-mtx: pid 11340 finish time Mon Mar 3 14:31:47 2003 Now, checking chg-zd-mtx-slot, it contains 1, and doesn't change! (I then verified that the file was owned by backup, the amanda user, which it is, and that backup owns the entire config directory. Any help would be MUCH appreciated. Many thanks Nigel Barker
Re: Excluding more than one file when backing up a windows client
On Sat, 1 Mar 2003 at 9:03am, Amanda wrote I'd love to hear how other folks are backing up windows machines using amanda. 2.4.4 includes support for running under cygwin. Doing it this way you could use exclude list. Check the (recent) archives for some discussions of this. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Solaris 8 Overland Tape changer config
Jay On Mon, Mar 03, 2003 at 02:54:11PM -, Nigel Barker wrote: I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda 2.4.3 mtx 1.2.17 amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do ^ I assume the real amanda.conf doesn't have this typo. I copied it from the file, the typo was there, I've corrected it but it hasn't changed the behaviour at all (which feels like a clue to me...) Did you catch the 2nd typo ? You have an o rather than a 0 as the last character of the device name.
Re: EOF, check amidxtaped.debug file [..]
I just got a similar problem to what Odd Rune Dahle described, with a slightly different message. In the amidxtaped.timestamp.debug file, almost everything went fine until: amrestore: error reading file header: Is a directory amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 30.102: tape_rewind tape: /home/amanda/testSet1: Inappropriate ioctl for device amidxtaped: time 30.102: pid 25439 finish blah blah blah 1. The Inappropriate... must be because I use tapeless back up on a second hard drive. 2. Is amrestore capable of restoring a whole directory tree??? And what goes wrong here? Thanks, Odd Rune Dahle wrote: Joshua Baker-LePain: EOF, check amidxtaped.debug file on ns1. And did you do this? What's in that file? I'm sorry. I forgot to mention that this file doesn't exist. First off, what user you running that command as? If it's not root or amanda, then it's not going to pick up /tmp/amanda (where the debug files live), b/c /tmp/amanda has 700 permissions. It was as root. But now that you mention /tmp/amanda, I checked there. amrestore refer to amidxtaped.debug, but the file is named amidxtaped.timestamp.debug.. no wonder the locate command didn't find it :-) Things made a bit more sense once I found the debug-file: amrestore: could not open /dev/tape: Permission denied amidxtaped: time 0.003: amrestore terminated normally with status: 2 amidxtaped: time 0.003: rewinding tape ... amidxtaped: time 0.003: tape_rewind: tape open: /dev/tape: Permission denied amidxtaped: time 0.003: pid 10103 finish time Fri Feb 28 07:19:30 2003 My xinetd-setup specified the wrong group for amidxtaped (bin), when I use 'disk' as owner of the tape-device. Unfortunately there are nobody on-site until monday morning, but we'll run a new test then. Thanks for the help :-)
Re: [amanda@fractal.Mines.EDU: DDS4backup AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE]
On Thu, Feb 13, 2003 at 10:41:40AM -0500, Jon LaBadie wrote: Gene Heskett wrote: It can take a very short time to read 32KB, that is all that is done. Does your tapelist file show all the tapes you labeled? Can you manually do manipulate the changer, load each slot in turn and run amtape config current. This should show what is really in each slot. I can manipulate the changer with amtape and mtx just fine, but when I run amtape config current it always shows the information from the last tape that was labeled, even if I completely eject the magazine, power everything off and put in a brand new tape when everything is back up. I have even tested this using dd instead of amtape, so at this point I know that it is not an AMANDA problem at all. Assuming there is the correct tape in each slot I'd then guess something in the changer hardware/software (likely the latter) is reporting that the changer is changing but not actually doing the job properly. Though you say you do see the mechanism working, maybe something in the changer status files is not being updated. Any ideas on debugging the hardware/software to find out which one is the problem. This drive/changer worked fine in another machine running off an older Adaptec card and it is now running off an Adaptec AIC7899 that came with my Dell tape changer. Both drives are running off the same card, different channels. Right now I am thinking that the drive is returned cached information when you try to pull data from it and my boss has suggested that the driver isn't sending a close() system call to the device and that may be a reason for retrieving the wrong info. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Michael Murph Robbert System Administrator for Math/CS Colorado School of Mines, Golden, CO 80401-1887 Office: SH220 Office phone: 303-273-3786 Pager: 303-461-6543 or Text messages: [EMAIL PROTECTED] Email: [EMAIL PROTECTED]
Re: EOF, check amidxtaped.debug file [..]
On Mon, Mar 03, 2003 at 12:54:40PM -0800, bao wrote: I just got a similar problem to what Odd Rune Dahle described, with a slightly different message. In the amidxtaped.timestamp.debug file, almost everything went fine until: amrestore: error reading file header: Is a directory amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 30.102: tape_rewind tape: /home/amanda/testSet1: Inappropriate ioctl for device amidxtaped: time 30.102: pid 25439 finish blah blah blah 1. The Inappropriate... must be because I use tapeless back up on a second hard drive. What's your tapedev in amanda.conf? You should use it. Maybe it's 'file:/home/amanda/testSet1'. Jean-Louis 2. Is amrestore capable of restoring a whole directory tree??? And what goes wrong here? Thanks, Odd Rune Dahle wrote: Joshua Baker-LePain: EOF, check amidxtaped.debug file on ns1. And did you do this? What's in that file? I'm sorry. I forgot to mention that this file doesn't exist. First off, what user you running that command as? If it's not root or amanda, then it's not going to pick up /tmp/amanda (where the debug files live), b/c /tmp/amanda has 700 permissions. It was as root. But now that you mention /tmp/amanda, I checked there. amrestore refer to amidxtaped.debug, but the file is named amidxtaped.timestamp.debug.. no wonder the locate command didn't find it :-) Things made a bit more sense once I found the debug-file: amrestore: could not open /dev/tape: Permission denied amidxtaped: time 0.003: amrestore terminated normally with status: 2 amidxtaped: time 0.003: rewinding tape ... amidxtaped: time 0.003: tape_rewind: tape open: /dev/tape: Permission denied amidxtaped: time 0.003: pid 10103 finish time Fri Feb 28 07:19:30 2003 My xinetd-setup specified the wrong group for amidxtaped (bin), when I use 'disk' as owner of the tape-device. Unfortunately there are nobody on-site until monday morning, but we'll run a new test then. Thanks for the help :-) -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amplot question
On Sat, Mar 01, 2003 at 02:22:05PM -0500, Gene Heskett wrote:
On Fri February 28 2003 17:58, Jean-Louis Martineau wrote:
On Fri, Feb 28, 2003 at 02:04:45PM -0700, Broderick Wood wrote:
Except that the ps file(s) generate by amplot -p -l amdump*
is a B/W ps file.
Is there an option is the amplot that I am missing?
Try this patch.
Jean-Louis
I tried this patch with amanda-2.4.4/amplot, and it worked as I
reported earlier. Unforch, then I tried to apply it to
amanda/2.4.4-20030228/amplot, but got a message from patch that
this patch had already been applied. But I got a bw printout when
I tried it this morning.
The patch is not yet on a snapshot.
If and when you do incorporate it into amplot, may I suggest the use
of the pure yellow be changed to orange so that those portions can
be easier seen under warm incandescent or a Lights Of America CCFL
lamp, whose color is also extremely warm, possibly containing even
less blue than a normal incandescent lamp?
Try this new patch, it also add a '-b' flag for people that want a
b/w postscript.
Jean-Louis
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
diff -u amanda-2.4.3.orig/amplot/amplot.awk amanda-2.4.3.new/amplot/amplot.awk
--- amanda-2.4.3.orig/amplot/amplot.awk 2002-12-30 11:23:47.0 -0500
+++ amanda-2.4.3.new/amplot/amplot.awk 2003-03-03 14:23:47.0 -0500
@@ -485,8 +485,14 @@
if (gnuplot==0) {
printf set output \%s.ps\\n,fil title;
- if(paper==1) printf set term postscript landscape \Times-Roman\
10\n title;
- else printf set term postscript portrait \Times-Roman\ 10\n
title;
+ if(bw==1) {
+ if(paper==1) printf set term postscript landscape
\Times-Roman\ 10\n title;
+ else printf set term postscript portrait \Times-Roman\
10\n title;
+ }
+ else {
+ if(paper==1) printf set term postscript landscape color
\Times-Roman\ 10\n title;
+ else printf set term postscript portrait color
\Times-Roman\ 10\n title;
+ }
}
printf set ylabel ; title;# make sure there is no ylabel
fmt= set label %d \%s\ at third_col, %d\n;
diff -u amanda-2.4.3.orig/amplot/amplot.g amanda-2.4.3.new/amplot/amplot.g
--- amanda-2.4.3.orig/amplot/amplot.g 2002-11-04 20:37:52.0 -0500
+++ amanda-2.4.3.new/amplot/amplot.g2003-03-03 14:28:42.0 -0500
@@ -62,7 +62,7 @@
plot run_queue title Run Queue with line 3,\
tape_queue title Tape Queue with line 2,\
finished title Dumps Finished with line 4,\
- bandw_free title Bandwidth Allocated with line 6, \
+ bandw_free title Bandwidth Allocated with line 8, \
disk_alloc title %Disk Allocated with line 1, \
tape_wait title %Tape Wait with line 5,\
tape_idle title Taper Idle with line 1,\
diff -u amanda-2.4.3.orig/amplot/amplot.sh.in amanda-2.4.3.new/amplot/amplot.sh.in
--- amanda-2.4.3.orig/amplot/amplot.sh.in 2002-11-04 20:37:52.0 -0500
+++ amanda-2.4.3.new/amplot/amplot.sh.in2003-03-03 14:24:18.0 -0500
@@ -58,7 +58,8 @@
echo -e Extends x (time) axes if needed
echo -g Run gnuplot directly no postscript file generated DEFAULT
echo -l Landscape mode suitable for printing
- echo -p Postscript output
+ echo -p Postscript output (color)
+ echo -b The postscipt will be b/w
echo -t TSet the right edge of the plot to be T hours
exit 1
fi
@@ -75,6 +76,7 @@
cmpres=0
para=
maxtime=4
+bw=0
# setting up the parameters to pass to [gn]awk
while :; do
@@ -84,6 +86,7 @@
-g) gnuplot=1; shift;;
-l) paper=1; para=$para$AVARFLAG paper=1 ; shift;;
-p) gnuplot=0; shift;;
+ -b) bw=1; shift;;
-t) shift
if test $# -eq 0; then
echo amplot: no argument for -t option 12
@@ -109,6 +112,14 @@
echo amplot: -l requires -p flag at the same time 12
exit 6
fi
+ if [ $bw -eq 1 ] ; then
+ echo amplot: -b requires -p flag at the same time 12
+ exit 6
+ fi
+fi
+
+if [ $bw -eq 1 ]; then
+ para=$para bw=1
fi
list=; # files to compress at the end
Re: Using only one tape, full dump delayed
On Mon, Mar 03, 2003 at 04:39:05PM +0100, Urs Forster wrote: Dear Jon Since you found out anyway, I give up lying; I gonna tell you frankly: I don't know exactly what I have. 'dmesg' says: st18: HP DDS-3 4mm DAT loader 'inquire' says: [EMAIL PROTECTED]:HP C1557A U709|Tape, /dev/rmt/0mbn OK, so the same unit I have. I did believe that this is similar to a Surestore 12000e. Is there a 12000? I think the 1200 is a DDS-2. Also I remember that somewhere it said the 'b' (berkley) option was a good idea for amanda. I trust my sources and experience to skip the 'b'. The '72-144 Gbyte 4mm DDS-3 Autoloader Installation and User's Guide' says that a DDS-3 125m tape would hold 72GB uncompressed and 144GB compressed. Not a tape, but the entire magazine of 6 tapes. The tape itselfes says: 12GB native Capacity. And 6x12 == 72. There is no switch inside the drive to enable/disable compression, You're Lying again :)) so I assume when not using the 'c,u' option, it wont compress. With my internal switch settings to power up in no compression, allow software selection, and the driver in my Solaris 89 system, c/u give HW compression, h seems to be the same, at least I have not detected any difference, l gives HW compression off, and m gives leave it as it was. Then there is the density switch (l,m,h) for low, medium and high. I don't think this has to do with compression. I believe this depends on the made of the tape? (I am not using any) Sorry about the 'n' option. That was a lie ;-) What do you mean by made of the tape? make? mode? ??? Get to the HP support pages for the 24x6 surestore changers. Look for manuals and the like. Specifically for anything to do with installation and unix. They have very distinct setting suggestions for several flavors of unix for both the back panel switches and that 8 place, non-existant, internal DIP switch. If you follow their settings AND edit /kernel/drv/st.conf to look at lun 1 as well as lun 0, then you will reconfigure reboot into two /dev/rmt devices, one for the tape drive, one for the changer. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Solaris 8 Overland Tape changer config
On Mon, Mar 03, 2003 at 03:28:54PM -0500, Brian Cuttler wrote: Jay On Mon, Mar 03, 2003 at 02:54:11PM -, Nigel Barker wrote: I'm using Solaris 8, with an OverlandXB 10 slot changer and a DLT drive. Amanda 2.4.3 mtx 1.2.17 amanda.conf contains :- tpchanger chg-zd-mtx tapedev /dev/rmt/1n changerfile /usr/local/share/amanda/Daily/chg-zd-mtx changerdev /dev/scsi/cganger/c1t6do ^ I assume the real amanda.conf doesn't have this typo. I copied it from the file, the typo was there, I've corrected it but it hasn't changed the behaviour at all (which feels like a clue to me...) Did you catch the 2nd typo ? You have an o rather than a 0 as the last character of the device name. And shouldn't the changer filename end with .conf as per your earlier post? jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Solaris 8 Overland Tape changer config
On Mon, Mar 03, 2003 at 01:37:12PM -0500, Brian Cuttler wrote: I may have been missing something in my config - something like an environmental variable, but I found that I wasn't able to run chg-zd-mtx successfully unless I was in the directory with the data information. That is normal. From docs/TAPE.CHANGERS: 3. DEVICE-SPECIFIC TAPE CHANGER SCRIPT The tape changer script/program is always run* from the directory with amanda.conf. It is never passed the configuration name it is running on behalf of, but since amgetconf works without a name from the current directory, that should be sufficient. * the word run was assumed to be missing and added for this email; do I need to submit a patch? :) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
