Re: amcheck not returning anything

[Gordon Ewasiuk]

On Mon, 10 Feb 2003, Rebecca Pakish Crum wrote:

> Hi all...I have been using amanda for quite some time and never encountered this 
>problem before...
>
> Installed 2.4.2p2 on a RH8.0 box...
> When I run su amanda -c "amcheck isymmdaily"
> I just get the prompt back at me. No errors in /var/log/messages, nothing in 
>/tmp/amanda.
> Very strange.
>

Hi Rebecca,

Do you have a "mailto" line in your amanda.conf?  I do and my amcheck
results are sent to root and my local amanda user.

Regards,

-gordon

Re: Problems with full backups

[Jon LaBadie]

On Tue, Feb 11, 2003 at 09:00:16AM +1000, Bradley Marshall wrote:
> On Mon, Feb 10, 2003 at 07:28:39AM -0500, Joshua Baker-LePain wrote:
> > >   FAILURE AND STRANGE DUMP SUMMARY:
> > > driver: FATAL driver received unexpected token (2) from taper
> > OS, version, and amanda version would be helpful.  Also, look in your 
> > system logs for any error messages around the time of the failed backups.  
> > Finally, look in the amdump.N file for exactly what taper told driver.
> 
> Linux 2.2.21, Debian 2.2, amanda 2.4.2p2.  There is nothing I can find
> in the system logs about this problem.  The extract from the amdump.N
> looks like:
> 
> changer: opening pipe to: /usr/lib/amanda/chg-zd-mtx -slot next
> changer: got exit: 0 str: 2 /dev/nst0
> taper: slot 2: date Xlabel FullPlugged2003011702 (first labelstr match)
> taper: read label `FullPlugged2003011702' date `X'
> taper: wrote label `FullPlugged2003011702' date `20030208'
> driver: result time 20788.194 from taper: QUITTING 00-00052 [writing file: No space 
>left on device]

Don't think this is hd or mem, but tape.
Looks like the message is coming from "taper".

> driver: driver received unexpected token (2) from taper
> taper: DONE [idle wait: 9003.563 secs]
> taper: writing end marker. [FullPlugged2003011702 OK kb 0 fm 0]

But taper never wrote anything, a total of 0 KB of data written (kb 0),
with a total of 0 files (or filemarks -- fm 0).

Consider why it may not be writing to tape.


-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: The Old Selfcheck Issue

[Gene Heskett]

On Monday 10 February 2003 14:17, Brad wrote:
>Hello,
>
>
>We change the IP address on our amanda server because we moved to
> a new building. Now, when we run "su amanda -c "amcheck daily" we
> continually get the 'selfcheck request timed out' error, but the
> server can still check the other hosts it backs up. No other
> changes were made to the server. It was up and running for
> several months before the move w/o any problems. Here's what I've
> verified:
>
>amanda can write to /var/tmp/amanda
>there are no firewalls in place
>according to lsof, all amanda services are still running
>I can ping the server from itself and from other clients on the
> network Restarting xinetd or rebooting does not correct the
> problem The server has entries for itself in
> /var/lib/amanda/.amandahosts
>
>Any ideas? We're using version 2.4.2p2-7 on a RH 7.3 server (it
> was installed with RH's default rpms). Like I said earlier, it
> worked perfectly for several months before we moved to the new
> building and changed IPs, but that doesn't seem like it should
> cause this.
>
>Thanks

Is there no way you can restore the ip address to the original?

I ask because the ip is one of the items thats configured and built 
into the executables at compile time, or is when built the way I 
build amanda here.

You may have to rebuild amanda with the new ip's being specified in 
the configuration script.

Having that as a script rather than trying to remember all the 
options when you upgrade makes for consistency because you will 
then know that each newer version has been built with the exact 
same set of options.

I can post my script if you are interested.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

Re: Amflush failing silently

[Gene Heskett]

On Saturday 08 February 2003 13:20, Gene Heskett wrote:
>On Saturday 08 February 2003 07:27, Christoph Scheeder wrote:

Sheesh, 2 days to echo this message back to me? Somethings not up to 
snuff here.

>[...]
>
>From Jean-Louis:
>>> Do you have the same problem with 2.4.4b1?
>>
>>this is the main production-server of a customer of us, and i'm a
>> bit scared about installing "beta"-software on it, so i haven't
>> try'd this yet. If you consider it stable enough for
>> production-use i'll try it.
>>
>>Christoph
>
>Christoph; I've been building the 2.4.4b1 releases and using them
>here, usually within 12 hours of their release on Jean-Louis's
>site, with no known problems here, on a redhat8.0 box using a
>Seagate/Compaq 4 slot changer.  For me, thats 'production use'.
>
>IMO, amanda is a moving target, getting better all the time, and
> its currently at least as stable as any 2.4.2 release ever was. 
> But that, and a buck twenty five will get you a cuppa most
> places.
>
>Here if it breaks, it hasn't broken a paying client, just me, but
>the list will be notified asap too.  Would I put it on a clients
>machinery?  In a heartbeat...
>
>My $0.02, not adjusted for inflation. :)

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

NAK: amandad busy

[justin m. clayton]

I've been receiving this error on some, but not always all, of my hosts
during amcheck. What could be causing this issue? Which logs are most
likely to be housing the magic info I need to solve this?

Thanks,

Justin Clayton
VLSI Research System Administrator
University of Washington
Electrical Engineering Dept
[EMAIL PROTECTED]
206/543.2523  EE/CSE 307E

Re: The Old Selfcheck Issue

[Tim Souder]

Also, just to be sure, check to see if the new name of the host (which
may have changed if the host uses dhcp to grab its name) is setup properly
in the disklist file (of course, if the name of the backup server is
localhost in disklist this cannot be a problem).

I hope this helps,

Tim

On 10 Feb 2003, Brad wrote:

> Hello,
>
>
> We change the IP address on our amanda server because we moved to a new
> building. Now, when we run "su amanda -c "amcheck daily" we continually
> get the 'selfcheck request timed out' error, but the server can still
> check the other hosts it backs up. No other changes were made to the
> server. It was up and running for several months before the move w/o any
> problems. Here's what I've verified:
>
> amanda can write to /var/tmp/amanda
> there are no firewalls in place
> according to lsof, all amanda services are still running
> I can ping the server from itself and from other clients on the network
> Restarting xinetd or rebooting does not correct the problem
> The server has entries for itself in /var/lib/amanda/.amandahosts
>
> Any ideas? We're using version 2.4.2p2-7 on a RH 7.3 server (it was
> installed with RH's default rpms). Like I said earlier, it worked
> perfectly for several months before we moved to the new building and
> changed IPs, but that doesn't seem like it should cause this.
>
> Thanks
>
>

question - backup up level

[David . Lee]

After ran 'amdump' (gnutar is the utility), I saw hosts got different lavel
of
backup. I don't know why.
How to control backup level? ie, all hosts backup level 0.
The following is the summary of 'amdump':

DUMP SUMMARY:

HOSTNAME DISKL

pocs02/   0
pocs02/archiv   0
pocs02/dev/fd   0
pocs02/home   0
mws   /1
mws   /boot  1
mws   /dev/shm1
mws   /home1
mws   -igna/local  1
mws02  / 2
mws02 /boot1
mws02 /dev/shm  1
cat_rip1   /   1
cat_rip1   /boot 1
cat_rip1   /home   1
cat_rip2   /   1
cat_rip2  /boot  1
cat_rip2   /home   1

Thanks!

David

Nevermind: amcheck not returning anything

[Rebecca Pakish Crum]

I'm a moron...apparently I gave amanda /bin/false when I set her up as a user. She 
doesn't like that. Please disregard.

-Original Message-
From: Rebecca Pakish Crum 
Sent: Monday, February 10, 2003 5:20 PM
To: Amanda Users (E-mail)
Subject: amcheck not returning anything


Hi all...I have been using amanda for quite some time and never encountered this 
problem before...

Installed 2.4.2p2 on a RH8.0 box...
When I run su amanda -c "amcheck isymmdaily" 
I just get the prompt back at me. No errors in /var/log/messages, nothing in 
/tmp/amanda.
Very strange.

xinetd is configured and showing my 3 amanda services in chkconfig --list
.amandahosts is configured
/etc/hosts looks good

Permissions on /tmp/amanda look good, permissions on /usr/local/etc/amanda/isymmdaily 
look good.

I don't get it...I've got nothing to look at and tell me what is going on!! HELP.


Rebecca A. Crum  
Systems Administrator 
Unterberg & Associates, P.C. 
(219) 736-5579 ext. 184 

gotchas to consider when upgrading from 2.4.2 to 2.4.3?

[Mark Stosberg]

Hello,

At my Amanda installation, we have a server and several clients all
running 2.4.2p2. I would like to upgrade at least the server to take
advantage of some of the features in 2.4.3. I have some questions for
veterans of this upgrade:

 - will the existing amanda config files work directly?
 - Do we need to upgrade the clients, if they don't need to take
 advantage of any of the new configuration options in 2.4.3?

Thanks!

  Mark

--
http://mark.stosberg.com/

amcheck not returning anything

[Rebecca Pakish Crum]

Hi all...I have been using amanda for quite some time and never encountered this 
problem before...

Installed 2.4.2p2 on a RH8.0 box...
When I run su amanda -c "amcheck isymmdaily" 
I just get the prompt back at me. No errors in /var/log/messages, nothing in 
/tmp/amanda.
Very strange.

xinetd is configured and showing my 3 amanda services in chkconfig --list
.amandahosts is configured
/etc/hosts looks good

Permissions on /tmp/amanda look good, permissions on /usr/local/etc/amanda/isymmdaily 
look good.

I don't get it...I've got nothing to look at and tell me what is going on!! HELP.


Rebecca A. Crum  
Systems Administrator 
Unterberg & Associates, P.C. 
(219) 736-5579 ext. 184 

Re: Problems with full backups

[Bradley Marshall]

On Mon, Feb 10, 2003 at 07:28:39AM -0500, Joshua Baker-LePain wrote:
> >   FAILURE AND STRANGE DUMP SUMMARY:
> > driver: FATAL driver received unexpected token (2) from taper
> OS, version, and amanda version would be helpful.  Also, look in your 
> system logs for any error messages around the time of the failed backups.  
> Finally, look in the amdump.N file for exactly what taper told driver.

Linux 2.2.21, Debian 2.2, amanda 2.4.2p2.  There is nothing I can find
in the system logs about this problem.  The extract from the amdump.N
looks like:

changer: opening pipe to: /usr/lib/amanda/chg-zd-mtx -slot next
changer: got exit: 0 str: 2 /dev/nst0
taper: slot 2: date Xlabel FullPlugged2003011702 (first labelstr match)
taper: read label `FullPlugged2003011702' date `X'
taper: wrote label `FullPlugged2003011702' date `20030208'
driver: result time 20788.194 from taper: QUITTING 00-00052 [writing file: No space 
left on device]
driver: driver received unexpected token (2) from taper
taper: DONE [idle wait: 9003.563 secs]
taper: writing end marker. [FullPlugged2003011702 OK kb 0 fm 0]

There's plenty of space left on the dump disk, and there are more
partitions to dump after this one, but thats the end of the file.
There are also more tapes in the changer, but it doesn't seem to want
to use it.

Thanks,
Brad
-- 
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
|Brad Marshall|   Plugged In Software|
|Senior Systems Administrator | http://www.pisoftware.com|
|mailto:[EMAIL PROTECTED]   |  GPG Key Id: 47951BD0 / 1024b|
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
 Fingerprint:  BAE3 4794 E627 2EAF 7EC0  4763 7884 4BE8 4795 1BD0

RE: 2.4.4b1 cygwin client and specifying DLEs with spaces...

[Bort, Paul]

If your system is also generating old 8.3 names (for backwards
compatibility) you can mix them in: 

/cygdrive/c/docume~1/myfolder

The command "dir /x" (under XP Pro, yours may vary) shows the short names
for files that need them.


> -Original Message-
> From: Richard Morse [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 10, 2003 2:43 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: 2.4.4b1 cygwin client and specifying DLEs with spaces...
> 
> 
> Hi!  This is probably a really easily answered question, but 
> I'm not having
> any luck finding it (probably going blind)...
> 
> I've got the 2.4.4b1 client set up on a cygwin machine.  The 
> backup is going
> well, but in order to create a DLE, I had to do some 
> aliasing.  Is there a
> way to specify a DLE like:
> X.. /cygdrive/c/Documents and 
> Settings/myuserfolder comp-tar
> 
> That is, include paths with spaces?
> 
> Alternatively, in the .amanda-gtar-excludes file, can I 
> specify directories
> with spaces?  So I can exclude /Program Files?
> 
> Thanks,
> Ricky
> 

Re: 2.4.4b1 cygwin client and specifying DLEs with spaces...

[Doug Kingston]

I can show you my .amanda.exclude for a Cygwin installation (attached).  
There is no problem with spaces.

By DLE I assume you mean the disklist file?  Not sure how to get spaces 
in that.  Have you looked at the source?

-Doug-

Richard Morse wrote:

Hi!  This is probably a really easily answered question, but I'm not having
any luck finding it (probably going blind)...

I've got the 2.4.4b1 client set up on a cygwin machine.  The backup is going
well, but in order to create a DLE, I had to do some aliasing.  Is there a
way to specify a DLE like:
X.. /cygdrive/c/Documents and Settings/myuserfolder comp-tar

That is, include paths with spaces?

Alternatively, in the .amanda-gtar-excludes file, can I specify directories
with spaces?  So I can exclude /Program Files?

Thanks,
Ricky

 

./.emacs.d
./CD-Images
./DMI
./Documents and Settings/Owner/Local Settings/Temp
./Documents and Settings/Owner/Local Settings/Temporary Internet Files
./Documents and Settings/Owner/My Documents/Data/Mozilla/dpk/y59np5c1.slt/Cache
./Documents and Settings/Owner/Recent
./Documents and Settings/eb/My Documents/jmcscans
./Documents and Settings/eb/Local Settings/Temp
./Documents and Settings/eb/Local Settings/Temporary Internet Files
./Documents and Settings/amanda/Local Settings/Temp
./Documents and Settings/amanda/Local Settings/Temporary Internet Files
./HP
./I386
./INSTALLS.TMP
./ML
./My Download Files
./PARATOOL
./Program Files
./RECYCLER
./System Volume Information
./WIN51
./WIN51IC
./WINDOWS
./WUTemp
./cygwin/bin
./cygwin/lib
./cygwin/sbin
./cygwin/tmp
./cygwin/usr
./ffastun.ffa
./ffastun.ffl
./ffastun.ffo
./ffastun0.ffx
./hiberfil.sys
./pagefile.sys
./ntldr

Re: The Old Selfcheck Issue

[Matt Hyclak]

On Mon, Feb 10, 2003 at 02:17:15PM -0500, Brad enlightened us:
> Any ideas? We're using version 2.4.2p2-7 on a RH 7.3 server (it was
> installed with RH's default rpms). Like I said earlier, it worked
> perfectly for several months before we moved to the new building and
> changed IPs, but that doesn't seem like it should cause this.
> 

Is there anything leftover in /etc/hosts?

Matt

-- 
Matt Hyclak
Department of Mathematics
Ohio University
(740) 593-1263



msg17645/pgp0.pgp
Description: PGP signature

Re: The Old Selfcheck Issue

[Frank Smith]

Sounds like you may still have the server's old IP address somewhere
in your hosts file, or in DNS/NIS.  See if 'nslookup servername'
returns what you expect.

Frank

--On Monday, February 10, 2003 14:17:15 -0500 Brad <[EMAIL PROTECTED]> wrote:


Hello,


We change the IP address on our amanda server because we moved to a new
building. Now, when we run "su amanda -c "amcheck daily" we continually
get the 'selfcheck request timed out' error, but the server can still
check the other hosts it backs up. No other changes were made to the
server. It was up and running for several months before the move w/o any
problems. Here's what I've verified:

amanda can write to /var/tmp/amanda
there are no firewalls in place
according to lsof, all amanda services are still running
I can ping the server from itself and from other clients on the network
Restarting xinetd or rebooting does not correct the problem
The server has entries for itself in /var/lib/amanda/.amandahosts

Any ideas? We're using version 2.4.2p2-7 on a RH 7.3 server (it was
installed with RH's default rpms). Like I said earlier, it worked
perfectly for several months before we moved to the new building and
changed IPs, but that doesn't seem like it should cause this.

Thanks




--
Frank Smith [EMAIL PROTECTED]
Systems Administrator  Voice: 512-374-4673
Hoover's Online  Fax: 512-374-4501

Re: Question about amlabel

[lone_wolf_20]

--- Jon LaBadie <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 10, 2003 at 02:06:53PM +0100, Paul
> Bijnens wrote:
> > 
> > Pro-Fit wrote:
> > >Hey folks - thanks for all your help - another
> newbie
> > >question...
> > >
> > >Is it possible to put the amlabel process in the
> CRON
> > >as opposed to running it manually everyday?  How
> would
> > >one do this?
> > 
> > I wouldn't do it... :-)
> > 
> > The label on the tape serves some useful purposes.
>  First it verifies
> > that the tape in the device is indeed an Amanda
> tape, and not some
> > other tape containing the data for your nobel
> prize project.
> > With the tapelabel, Amanda can verify that she has
> the expected tape
> > and not one that should not yet be overwritten
> (i.e. not yesterdays 
> > backup that you forgot to take out, because you
> had a day off for example).
> > 
> > That's why you first label your tapes, when you
> awake, and not half 
> > sleeping, and after three times verifing that you
> put in the correct
> > tape in the drive.  And you also put a sticker on
> the tape with the
> > Amanda's label on it, e.g. DailySet1-001. 
> Stickers cannot be put on a 
> > tape by cron afaik.
> > 
> > Once labelled, you normally never ever have to
> relabel a tape.
> > 
> > Taking this in consideration, you don't need to
> amlabel a tape by a cron 
> > command at night, wiping out whatever tape was
> someone put by accident 
> > in the tape drive.  There is nobody around to
> verify that the tape that 
> > you put in around 5 PM is still the same...
> > 
> > If you do feel the need to relabel a tape each
> time it is used by 
> > Amanda, you are probably trying to force Amanda
> into something for which 
> > she is not designed, like labeling your tapes
> "monday", "tuesday", etc.
> > Look in the archives of this list to find the
> arguments against this scheme.
> > 
> > ps.  If you really are smarter than Amanda, try
> this command in your 
> > crontab: "amlabel -f  ", about 5
> minutes before the 
> > amdump entry.
> > 
> > pps.  if you really are smarter than Amanda, you
> would already know the 
> > above command too :-)
> >
> 
> And if all that smart they probably would also know
> to amrmtape the old label
> should a previously indexed tape be used.
> 
> -- 
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Just a quick summary of how Amanda treats tapes and
backups, which by the question, seems in order:

Think of Amanda as having a pool of tapes devoted to a
specific backup set, rather than having a Monday,
Tuesday, etc.  Let's say you have 15 tapes.  You can
label each tape 'DailySet1_001' through
'DailySet1_015' (or however you have your label string
set up in your amanda.conf file for the set).

Now these tapes are owned by the DailySet1 backup set.
   Amanda keeps track of which tapes have been dumped
to and when they were last used.  The configuration
file specifies the number of tapes you have, and how
often full backups are to be run (dumpcycle).  

When amdump is run, you'll notice in the report e-mail
not only the tape that the backups were dumped to, but
also what tape Amanda expects to use next.  In this
way, Amanda lets you know what tape it wants to use
for the next dump, or it'll manage the tapes by itself
in a changer.  BTW, the line 'a new tape' does not
mean an unlabeld tape, just one that hasn't been
dumped to yet.  Once you reach the end of your tapes
(in this case after 15 dumps), you'll notice Amanda
will prompt for the first tape to be used again for
the 16th dump.

Amanda is built to manage your tape use, and re-use,
for you, and it's usually a good idea to let it do
that as others have already said.

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

2.4.4b1 cygwin client and specifying DLEs with spaces...

[Richard Morse]

Hi!  This is probably a really easily answered question, but I'm not having
any luck finding it (probably going blind)...

I've got the 2.4.4b1 client set up on a cygwin machine.  The backup is going
well, but in order to create a DLE, I had to do some aliasing.  Is there a
way to specify a DLE like:
X.. /cygdrive/c/Documents and Settings/myuserfolder comp-tar

That is, include paths with spaces?

Alternatively, in the .amanda-gtar-excludes file, can I specify directories
with spaces?  So I can exclude /Program Files?

Thanks,
Ricky

The Old Selfcheck Issue

[Brad]

Hello,


We change the IP address on our amanda server because we moved to a new
building. Now, when we run "su amanda -c "amcheck daily" we continually
get the 'selfcheck request timed out' error, but the server can still
check the other hosts it backs up. No other changes were made to the
server. It was up and running for several months before the move w/o any
problems. Here's what I've verified: 

amanda can write to /var/tmp/amanda
there are no firewalls in place
according to lsof, all amanda services are still running
I can ping the server from itself and from other clients on the network
Restarting xinetd or rebooting does not correct the problem
The server has entries for itself in /var/lib/amanda/.amandahosts

Any ideas? We're using version 2.4.2p2-7 on a RH 7.3 server (it was
installed with RH's default rpms). Like I said earlier, it worked
perfectly for several months before we moved to the new building and
changed IPs, but that doesn't seem like it should cause this.

Thanks

Bayramýnýz Kutlu Olsun

[ISILDAK GROUP]

Title: Post Message


IÞILDAK GROUP SÝZE BAYRAM TEBRÝÐÝ GÖNDERMÝÞ 
BURAYA TIKLAYARAK TEBRÝK KARTINA ULAÞABÝLÝRSÝNÝZ.
 

Re: Amflush failing silently

[Christoph Scheeder]

GRMBL..
Sorry, i can't give you a traceback of amflush, today it worked flawlessly.
Nothing changed, only one amanda-dir less then last week and all is fine.
I'll have to wait until it reapears until i can give more details.
seemed to be caused by bad karma and 3 failed amanda-runs in the holdingdisk.
sorry.
Chritoph

Jean-Louis Martineau schrieb:

On Sat, Feb 08, 2003 at 01:27:34PM +0100, Christoph Scheeder wrote:


Hi,

Jean-Louis Martineau schrieb:


On Thu, Feb 06, 2003 at 01:32:01PM +0100, Christoph Scheeder wrote:



Hi,
Thanks, but that can't be the problem, because this patch had been applied
*before* the last failing amflush.
And it does not show the described symptoms, amflush is not hanging and
not eating up memory and cpu-cycles, it simply terminates fast without 
sending
an e-mail or doing anything it is expected to do.
Noe core-files laying around, it just marks the first matching tape as 
used in the database and then terminates.
Any thoughts?


Could you run amflush under a debugger? I would like to know where it 
crash?

If you can give me a brief instruction how i'll try it, i've never done
this before, so i don't know how.



$ gdb amflush
(gdb) run 

type 'where' on the gdb prompt when it crash.

Send me also the amflush log file.

Jean-Louis


Do you have the same problem with 2.4.4b1?


this is the main production-server of a customer of us, and i'm a bit scared
about installing "beta"-software on it, so i haven't try'd this yet.
If you consider it stable enough for production-use i'll try it.



I would have released the 2.4.4 stable this week-end if you haven't send
this bug report. It is better than 2.4.3.

Jean-Louis

Re: chg-zd-mtx error

[Joshua Baker-LePain]

On Mon, 10 Feb 2003 at 11:01am, Benjamin Herbert wrote

> I dont have a changer.conf file.  I only have a changer.conf-clean,
> changer.conf-access and a changer.conf-slot file.  They all contain 0 in
> them.

Erm, you need a conf file.  Look in chg-zd-mtx itself for how to set it 
up.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: chg-zd-mtx error

[Eric Sproul]

On Mon, 2003-02-10 at 12:01, Benjamin Herbert wrote:
> I dont have a changer.conf file.  I only have a changer.conf-clean,
> changer.conf-access and a changer.conf-slot file.  They all contain 0 in
> them.
> 

Benjamin,
Think of the 'changerfile' config element as a prefix for a number of
changer-related config and status files.  I also use chg-zd-mtx, and my
changerfile is set to /etc/amanda/Servers/CHANGER, which results in the
following files:

CHANGER-access
CHANGER-barcodes
CHANGER-clean
CHANGER-slot

These are all status files used by the glue script and do not need to be
edited.  I also have CHANGER.conf in which I placed my local variables,
like firstslot, lastslot, cleanslot, etc.  You have to create this file,
so chg-zd-mtx can find it by sticking '.conf' to the end of the path
specified in changerfile.

HTH,
Eric

> 
> On Mon, Feb 10, 2003 at 11:51:32AM -0500, Joshua Baker-LePain wrote:
> > On Mon, 10 Feb 2003 at 10:07am, Benjamin Herbert wrote
> > 
> > > I am trying to use the chg-zd-mtx script to contorl the tape changer on
> > > an exabyte LTO tape changer.  I am running redhat 7.3.  
> > > 
> > > Heres is some of the stuff in my amanda.conf:
> > > 
> > > tpchanger "chg-zd-mtx"  # the tape-changer glue script
> > > tapedev "/dev/nst0" # the no-rewind tape device to be used
> > > rawtapedev "/dev/nst0"  # the raw device to be used (ftape only)
> > > changerfile "/usr/local/amanda/etc/amanda/test/changer.conf"
> > > changerdev "/dev/sg0"
> > 
> > Are you sure about that changerdev?  For my Overland changer, the tape 
> > drive and robotics have separate SCSI IDs.  The tape drive is ID 4, and 
> > the robotics are ID 6.  Therefore the tape drive is sg0, and the robotics 
> > are sg1.
> > 
> > > Here is the command that I run:
> > > 
> > > /usr/local/amanda/libexec/chg-zd-mtx -info
> > > 
> > > 
> > > Here is the output of the command:
> > > 
> > > [root@X test]$ /usr/local/amanda/libexec/chg-zd-mtx -info
> > > /usr/local/amanda/libexec/chg-zd-mtx: [: : integer expression expected
> > > /usr/local/amanda/libexec/chg-zd-mtx: [: -lt: unary operator expected
> > >  6 1
> > 
> > First, can mtx talk to your changer?  What's the output of 'mtx -f 
> > /dev/sg0 status' (or sg1, as above).
> > 
> > If the device is correct, we'll need to see your CHANGER.conf file.
> > 
> > -- 
> > Joshua Baker-LePain
> > Department of Biomedical Engineering
> > Duke University

Re: chg-zd-mtx error

[Benjamin Herbert]

This has been resolved.  I needed to fix the 'sed' command in the
chg-zd-mtx script.  For some reason the one I had was setting $used to
nothing, which was creating the error.  It works fine now.  Thanks for
the replys.



On Mon, Feb 10, 2003 at 11:01:10AM -0600, Benjamin Herbert wrote:
> 
> Here is some output from a mtx command:
> 
> [root@darwin libexec]$ /usr/sbin/mtx -f /dev/sg0 status
> Storage Changer /dev/sg0:1 Drives, 10 Slots ( 0 Import/Export )
> Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag =
>Storage Element 1:Empty
>Storage Element 2:Full :VolumeTag=
>Storage Element 3:Full :VolumeTag=
>Storage Element 4:Full :VolumeTag=
>Storage Element 5:Full :VolumeTag=
>Storage Element 6:Full :VolumeTag=
>Storage Element 7:Full :VolumeTag=
>Storage Element 8:Empty
>Storage Element 9:Empty
>Storage Element 10:Empty
> 
> 
> So it seems that my changerdev is fine.
> 
> I dont have a changer.conf file.  I only have a changer.conf-clean,
> changer.conf-access and a changer.conf-slot file.  They all contain 0 in
> them.
> 
> 
> On Mon, Feb 10, 2003 at 11:51:32AM -0500, Joshua Baker-LePain wrote:
> > On Mon, 10 Feb 2003 at 10:07am, Benjamin Herbert wrote
> > 
> > > I am trying to use the chg-zd-mtx script to contorl the tape changer on
> > > an exabyte LTO tape changer.  I am running redhat 7.3.  
> > > 
> > > Heres is some of the stuff in my amanda.conf:
> > > 
> > > tpchanger "chg-zd-mtx"  # the tape-changer glue script
> > > tapedev "/dev/nst0" # the no-rewind tape device to be used
> > > rawtapedev "/dev/nst0"  # the raw device to be used (ftape only)
> > > changerfile "/usr/local/amanda/etc/amanda/test/changer.conf"
> > > changerdev "/dev/sg0"
> > 
> > Are you sure about that changerdev?  For my Overland changer, the tape 
> > drive and robotics have separate SCSI IDs.  The tape drive is ID 4, and 
> > the robotics are ID 6.  Therefore the tape drive is sg0, and the robotics 
> > are sg1.
> > 
> > > Here is the command that I run:
> > > 
> > > /usr/local/amanda/libexec/chg-zd-mtx -info
> > > 
> > > 
> > > Here is the output of the command:
> > > 
> > > [root@X test]$ /usr/local/amanda/libexec/chg-zd-mtx -info
> > > /usr/local/amanda/libexec/chg-zd-mtx: [: : integer expression expected
> > > /usr/local/amanda/libexec/chg-zd-mtx: [: -lt: unary operator expected
> > >  6 1
> > 
> > First, can mtx talk to your changer?  What's the output of 'mtx -f 
> > /dev/sg0 status' (or sg1, as above).
> > 
> > If the device is correct, we'll need to see your CHANGER.conf file.
> > 
> > -- 
> > Joshua Baker-LePain
> > Department of Biomedical Engineering
> > Duke University

Re: chg-zd-mtx error

[Benjamin Herbert]

Here is some output from a mtx command:

[root@darwin libexec]$ /usr/sbin/mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 10 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag =
   Storage Element 1:Empty
   Storage Element 2:Full :VolumeTag=
   Storage Element 3:Full :VolumeTag=
   Storage Element 4:Full :VolumeTag=
   Storage Element 5:Full :VolumeTag=
   Storage Element 6:Full :VolumeTag=
   Storage Element 7:Full :VolumeTag=
   Storage Element 8:Empty
   Storage Element 9:Empty
   Storage Element 10:Empty


So it seems that my changerdev is fine.

I dont have a changer.conf file.  I only have a changer.conf-clean,
changer.conf-access and a changer.conf-slot file.  They all contain 0 in
them.


On Mon, Feb 10, 2003 at 11:51:32AM -0500, Joshua Baker-LePain wrote:
> On Mon, 10 Feb 2003 at 10:07am, Benjamin Herbert wrote
> 
> > I am trying to use the chg-zd-mtx script to contorl the tape changer on
> > an exabyte LTO tape changer.  I am running redhat 7.3.  
> > 
> > Heres is some of the stuff in my amanda.conf:
> > 
> > tpchanger "chg-zd-mtx"  # the tape-changer glue script
> > tapedev "/dev/nst0" # the no-rewind tape device to be used
> > rawtapedev "/dev/nst0"  # the raw device to be used (ftape only)
> > changerfile "/usr/local/amanda/etc/amanda/test/changer.conf"
> > changerdev "/dev/sg0"
> 
> Are you sure about that changerdev?  For my Overland changer, the tape 
> drive and robotics have separate SCSI IDs.  The tape drive is ID 4, and 
> the robotics are ID 6.  Therefore the tape drive is sg0, and the robotics 
> are sg1.
> 
> > Here is the command that I run:
> > 
> > /usr/local/amanda/libexec/chg-zd-mtx -info
> > 
> > 
> > Here is the output of the command:
> > 
> > [root@X test]$ /usr/local/amanda/libexec/chg-zd-mtx -info
> > /usr/local/amanda/libexec/chg-zd-mtx: [: : integer expression expected
> > /usr/local/amanda/libexec/chg-zd-mtx: [: -lt: unary operator expected
> >  6 1
> 
> First, can mtx talk to your changer?  What's the output of 'mtx -f 
> /dev/sg0 status' (or sg1, as above).
> 
> If the device is correct, we'll need to see your CHANGER.conf file.
> 
> -- 
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University

Re: chg-zd-mtx error

[Joshua Baker-LePain]

On Mon, 10 Feb 2003 at 10:07am, Benjamin Herbert wrote

> I am trying to use the chg-zd-mtx script to contorl the tape changer on
> an exabyte LTO tape changer.  I am running redhat 7.3.  
> 
> Heres is some of the stuff in my amanda.conf:
> 
> tpchanger "chg-zd-mtx"  # the tape-changer glue script
> tapedev "/dev/nst0" # the no-rewind tape device to be used
> rawtapedev "/dev/nst0"  # the raw device to be used (ftape only)
> changerfile "/usr/local/amanda/etc/amanda/test/changer.conf"
> changerdev "/dev/sg0"

Are you sure about that changerdev?  For my Overland changer, the tape 
drive and robotics have separate SCSI IDs.  The tape drive is ID 4, and 
the robotics are ID 6.  Therefore the tape drive is sg0, and the robotics 
are sg1.

> Here is the command that I run:
> 
> /usr/local/amanda/libexec/chg-zd-mtx -info
> 
> 
> Here is the output of the command:
> 
> [root@X test]$ /usr/local/amanda/libexec/chg-zd-mtx -info
> /usr/local/amanda/libexec/chg-zd-mtx: [: : integer expression expected
> /usr/local/amanda/libexec/chg-zd-mtx: [: -lt: unary operator expected
>  6 1

First, can mtx talk to your changer?  What's the output of 'mtx -f 
/dev/sg0 status' (or sg1, as above).

If the device is correct, we'll need to see your CHANGER.conf file.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: sol 2.6 HP-C1557A (12000e) changer device

[Jay Lessert]

On Mon, Feb 10, 2003 at 04:09:07PM +0100, [EMAIL PROTECTED] wrote:
> Thanks all
> 
> It's working now. Had to compile 'sst' from the contrib dir, configure sst.conf
> and 'add_drv'. It's now at
> /devices/pci@1f,0/pci@1/scsi@2,1/sst@4,1:character.
> 
> I just wonder whether this is the best (stable) solution?

For Solaris 2.6, it might be the only solution (except possibly
for STCTL (http://www.cs.pdx.edu/~eric/stctl/).

For Solaris 8+, there's a Sun driver, sgen(7D), you would use that.

-- 
Jay Lessert   [EMAIL PROTECTED]
Accelerant Networks Inc.   (voice)1.503.439.3461
Beaverton OR, USA(fax)1.503.466.9472

chg-zd-mtx error

[Benjamin Herbert]

Hello,

I am trying to use the chg-zd-mtx script to contorl the tape changer on
an exabyte LTO tape changer.  I am running redhat 7.3.  

Heres is some of the stuff in my amanda.conf:

tpchanger "chg-zd-mtx"  # the tape-changer glue script
tapedev "/dev/nst0" # the no-rewind tape device to be used
rawtapedev "/dev/nst0"  # the raw device to be used (ftape only)
changerfile "/usr/local/amanda/etc/amanda/test/changer.conf"
changerdev "/dev/sg0"


Here is the command that I run:

/usr/local/amanda/libexec/chg-zd-mtx -info


Here is the output of the command:

[root@X test]$ /usr/local/amanda/libexec/chg-zd-mtx -info
/usr/local/amanda/libexec/chg-zd-mtx: [: : integer expression expected
/usr/local/amanda/libexec/chg-zd-mtx: [: -lt: unary operator expected
 6 1


Has anybody seen this or have any ideas.  Thanks for any information.

-Ben

tape not found in jukebox

[Brian Cuttler]

Amanda 2.4.2p2 with chg-zd-mtx from 2.4.3
Solaris 8, SUN Storedge 9 ie HP C7145

I've been running the same config for close to two
weeks, on Fridays amdump run, started from cron we
failed to find the required tape in the jukebox.

On monday I ran amcheck for the config and it found
the tape just fine, no intervention. amflush then
ran successfully.

BTW, this was also an issue for my other jukebox.
Same apparent result and same resolution.

FYI: I'm the site with two concurrent amanda runs for
 the same user on the same machine, one to each
 jukebox. One for local disk and one for remote clients.

Any ideas why both amanda's failed to find the next tape ?
And if so, how do I avoid problems in the future ?

thanks,

Brian

- Forwarded message from [EMAIL PROTECTED] -

>From [EMAIL PROTECTED] Fri Feb  7 21:59:24 2003
From: [EMAIL PROTECTED]
Date: Fri, 7 Feb 2003 21:59:04 -0500 (EST)
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: NewtonR AMANDA MAIL REPORT FOR February 7, 2003
X-MailScanner: Found to be clean

*** A TAPE ERROR OCCURRED: [label NEWTONR08 or new tape not found in rack].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: NEWTONR08.


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:05
Run Time (hrs:min) 0:29
Dump Time (hrs:min)0:32   0:00   0:32
Output Size (meg)9067.20.0 9067.2
Original Size (meg)  9067.20.0 9067.2
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped6  0  6   (1:4 2:2)
Avg Dump Rate (k/s)  4851.8--  4851.8

Tape Time (hrs:min)0:00   0:00   0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)   0.00.00.0
Filesystems Taped 0  0  0
Avg Tp Write Rate (k/s) -- -- -- 


NOTES:
  driver: WARNING: /amanda/workr: 36700160 KB requested, but only 34403066 KB 
available.
  planner: Incremental of csserv:/opt bumped to level 2.


DUMP SUMMARY:
  DUMPER STATSTAPER STATS 
HOSTNAME DISK   L   ORIG-KBOUT-KB COMP% MMM:SS   KB/s MMM:SS   KB/s
 --- -
csserv  /  1 96448 96448   --1:21 1185.9   N/AN/A 
csserv  /opt   2 68288 68288   --1:06 1029.5   N/AN/A 
csserv  /source2   576   576   --3:442.6   N/AN/A 
csserv  /var/spool 1   8602912   8602912   --   20:09 7117.1   N/AN/A 
panther /  1  1344  1344   --3:366.2   N/AN/A 
panther /data  1515200515200   --1:57 4417.7   N/AN/A 

(brought to you by Amanda version 2.4.2p2)

- End of forwarded message from [EMAIL PROTECTED] -

Re: Unsubscribe

[Joshua Baker-LePain]

On Mon, 10 Feb 2003 at 10:47am, Marcelo Pinto wrote

> I cannot unsubscribe me from this list. Please, anyone, help me!!!

Just follow the instructions at , which are the 
same as for every other majordomo list out there.

Hint: you *never* send subscribe or unsubscribe requests to the list 
itself.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Configure/Install

[Brian Cuttler]

Christopher,

You can get a listing of the options to the configure utility with
the "--help" switch. I got over 100 lines of options with explanitory
text (displayed in only the head of the output, its much much longer)
and I'd be surprised if the listing of switches wasn't exhaustive.

> ./configure --help
Usage: configure [options] [host]
Options: [defaults in brackets after descriptions]
Configuration:
  --cache-file=FILE   cache test results in FILE
  --help  print this message
  --no-create do not create output files
  --quiet, --silent   do not print `checking...' messages
  --version   print the version of autoconf that created configure

Its also my understanding and experience that you _never_ need to
modify the config utility and the config.log and .cache files are
modified by configure when you run the utility, so you wouldn't want
to hand edit though either.

As far as additional explaination of the switches, I can recommend
the documentation in the docs/ directory and the amanda.conf web
site which containts a pointer to the amanda_users mailing list and
archives.

I've found that I've needed to set few of the switches, --with-user,
--with-group and I believe that someone else on our site may have
build another version of amanda for our firewall system that set
the range of available ports. There used to be a problem with a
library on the IRIX systems but I believe that even that defaults
correctly these days.

If you have specific questions on some of the switches and can't
find the information in the archives than the amanda_users list
would be your best resource, remember to include OS, version,
amanda, version, perhaps tape drive, disk type (UFS, EFS, XFS...)
client and server information as relevant and your actual question.





> Since you were so helpful with my last issue I have another question to bounce off 
>of you.   What you suggested worked for my previous issue, and now I'm going through 
>the amanda.conf configuration.  My question is to you know where I can find some info 
>on the conf file with some detailed explanation on what the settings mean.  I realize 
>there is probably no easy way to edit this file besides going through it and editing 
>it correctly, I guess I am a spoiled Windows user who is use to everything being done 
>for you with little or no changes doing an install and configure
> 
> Any help would be greatly appreciated
> 
> 
> Christopher Broadwater
> PC/LAN Specialist
> Victoria IS Department
> 10 New Road
> East Providence, RI
> 02909
> (401)-435-9220 X2273
> 
> 
> -Original Message-
> From: Brian Cuttler [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 07, 2003 12:58 PM
> To: Chris Broadwater
> Subject: Re: Configure/Install
> 
> 
> 
> No need to edit the script, they are command line arguments.
> 
> ./configure --with-user=amanda --with-group=sys
> 
> in my case anyway.
> 
> ./configure has a help option, off hand I don't recall what
> it is but just saw it in a list message that you probably
> also received.
> 
> 
> > thanks
> > 
> > AM I to assume the user a group add is a switch put at the end of the configure 
>command?   Or do I create or edit an exisitng script?
> > 
> > Christopher Broadwater
> > PC/LAN Specialist
> > Victoria IS Department
> > 10 New Road
> > East Providence, RI
> > 02909
> > (401)-435-9220 X2273
> > 
> > 
> > -Original Message-
> > From: Brian Cuttler [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, February 07, 2003 11:52 AM
> > To: Chris Broadwater
> > Subject: Re: Configure/Install
> > 
> > 
> > 
> > Amanda is a wonderful scheduler, record keeper etc but relies
> > on the native dump utility or some form of tar, often gnutar
> > though you have to check the version, there are some that are
> > known to be broken and other versions that are highly recommended.
> > 
> > Personally I don't have any linux machines under amanda backup
> > though I know that many people on the list do.
> > 
> > 
> > > I am very new to amanda, looking for a vieable backup solution for a LINUX 
>Sever, we had migrated over from a DG?UX box and was using a backup routine using 
>DUMP however dump on its own seems to be flaky and unreliable on the LINUX box.  I'll 
>try what you suggested Thanks
> > > 
> > > Christopher Broadwater
> > > PC/LAN Specialist
> > > Victoria IS Department
> > > 10 New Road
> > > East Providence, RI
> > > 02909
> > > (401)-435-9220 X2273
> > > 
> > > 
> > > -Original Message-
> > > From: Brian Cuttler [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, February 07, 2003 11:20 AM
> > > To: Chris Broadwater
> > > Subject: Re: Configure/Install
> > > 
> > > 
> > > 
> > > You are new to amanda ??
> > > 
> > > run configure with the options
> > > 
> > >   --with-user=
> > >   --with-group=
> > > 
> > > to show which username will run the utility and while
> > > group they belong to.
> > > 
> > > In my case its "amanda" and "sys" where sys has access to
> > > the 

Re: Question about amlabel

[Jon LaBadie]

On Mon, Feb 10, 2003 at 02:06:53PM +0100, Paul Bijnens wrote:
> 
> Pro-Fit wrote:
> >Hey folks - thanks for all your help - another newbie
> >question...
> >
> >Is it possible to put the amlabel process in the CRON
> >as opposed to running it manually everyday?  How would
> >one do this?
> 
> I wouldn't do it... :-)
> 
> The label on the tape serves some useful purposes.  First it verifies
> that the tape in the device is indeed an Amanda tape, and not some
> other tape containing the data for your nobel prize project.
> With the tapelabel, Amanda can verify that she has the expected tape
> and not one that should not yet be overwritten (i.e. not yesterdays 
> backup that you forgot to take out, because you had a day off for example).
> 
> That's why you first label your tapes, when you awake, and not half 
> sleeping, and after three times verifing that you put in the correct
> tape in the drive.  And you also put a sticker on the tape with the
> Amanda's label on it, e.g. DailySet1-001.  Stickers cannot be put on a 
> tape by cron afaik.
> 
> Once labelled, you normally never ever have to relabel a tape.
> 
> Taking this in consideration, you don't need to amlabel a tape by a cron 
> command at night, wiping out whatever tape was someone put by accident 
> in the tape drive.  There is nobody around to verify that the tape that 
> you put in around 5 PM is still the same...
> 
> If you do feel the need to relabel a tape each time it is used by 
> Amanda, you are probably trying to force Amanda into something for which 
> she is not designed, like labeling your tapes "monday", "tuesday", etc.
> Look in the archives of this list to find the arguments against this scheme.
> 
> ps.  If you really are smarter than Amanda, try this command in your 
> crontab: "amlabel -f  ", about 5 minutes before the 
> amdump entry.
> 
> pps.  if you really are smarter than Amanda, you would already know the 
> above command too :-)
>

And if all that smart they probably would also know to amrmtape the old label
should a previously indexed tape be used.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: sol 2.6 HP-C1557A (12000e) changer device

[forster]

Thanks all

It's working now. Had to compile 'sst' from the contrib dir, configure sst.conf
and 'add_drv'. It's now at
/devices/pci@1f,0/pci@1/scsi@2,1/sst@4,1:character.

I just wonder whether this is the best (stable) solution?

Cheers
urs

>Sounds like you need to get the chg- working first.
>
>have a look at the docs in the tape-changer directory.
>
>
>
>-- 
>Martin Hepworth
>Senior Systems Administrator
>Solid State Logic Ltd
>+44 (0)1865 842300
>
>Gene Heskett wrote:
>> On Monday 10 February 2003 06:48, [EMAIL PROTECTED] wrote:
>> 
>>>Hello
>>>
>>>I did lots of reading manuals and mailing lists but still not
>>>succeeded in having amanda talk to the changer.
>>>
>>>Config:
>>>amanda 2.4.3
>>>solaris 2.6
>>>HP surestore C1557A (12000e)
>>>
>>>Previous installation of Soltice jukebox uses '/dev/lus'. But
>>>amanda cannot use it.
>>>
>>>***
>>>/dev/lus ->
>>>../devices/pci@1f,0/pci@1/pci@3/SUNW,isptwo@4/lus@0,0:0
>>>
>>>[pbrazor1]/export/home/amanda$ amtape Daily show
>>>amtape: could not get changer info: open: /dev/lus: Bad file
>>>number ***
>>>
>>>There is only 1 device in rmt '/dev/rmt/0...' .
>>>Installation test-routine of the changer software says:
>>>
>>>
>>>[pbrazor1]/etc/LGTOuscsi$ ./inquire
>>>[EMAIL PROTECTED]:FUJITSU MAB3091S SUN9.0G1806|Disk,
>>>/dev/rdsk/c0t3d0s2 [EMAIL PROTECTED]:HP C1557A U709|Tape,
>>>/dev/rmt/0mbn
>>>[EMAIL PROTECTED]:HP C1557A U709|Autochanger (Jukebox)
>>>
>>>/dev/rmt/0mbn -> ../../devices/pci@1f,0/pci@1/scsi@2,1/st@4,0:mbn
>>>
>>>
>>>But there is no 'st@4,1' either.
>>>
>>>So which software do I need to install or what configuration is
>>>needed?
>>>
>>>Thanks for any help
>>>urs
>> 
>> 
>> I don't believe this is an amanda problem, but a solaris kernel 
>> problem.  Unforch, I'll leave the definitive solaris answers to 
>> Jon.
>> 
>> If its anything like linux, then you should find the correct device 
>> in the /var/log/dmesg (or whatever solaris calls it) file. If its 
>> not there, the next question is, is solaris doing a 'scan all luns' 
>> on boot, I believe it must in order to find the changer robot since 
>> many of them are located at the same bus address as the drive 
>> itself, but at a higher Logical Unit Number, aka 'lun'.  For a 
>> linux kernel, this must be turned on in the kernel config and the 
>> kernel rebuilt as it doesn't default to on.
>> 
>
>
>
>
>**
>This email and any files transmitted with it are confidential and
>intended solely for the use of the individual or entity to whom they
>are addressed. If you have received this email in error please notify
>the system manager.
>
>This footnote also confirms that this email message has been swept by
>MIMEsweeper for the presence of computer viruses.
>
>www.mimesweeper.com
>**
>

Re: Unsubscribe

[Jon LaBadie]

On Mon, Feb 10, 2003 at 10:47:17AM -0300, Marcelo Pinto wrote:
> 
> I cannot unsubscribe me from this list. Please, anyone, help me!!!

mail [EMAIL PROTECTED], subject help

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: sol 2.6 HP-C1557A (12000e) changer device

[Jon LaBadie]

On Mon, Feb 10, 2003 at 12:48:46PM +0100, [EMAIL PROTECTED] wrote:
> Hello
> 
> I did lots of reading manuals and mailing lists but still not succeeded
> in having amanda talk to the changer.
> 
> Config:
> amanda 2.4.3
> solaris 2.6
> HP surestore C1557A (12000e)
> 
> 
> [pbrazor1]/etc/LGTOuscsi$ ./inquire
> [EMAIL PROTECTED]:FUJITSU MAB3091S SUN9.0G1806|Disk, /dev/rdsk/c0t3d0s2
> [EMAIL PROTECTED]:HP C1557A U709|Tape, /dev/rmt/0mbn
> [EMAIL PROTECTED]:HP C1557A U709|Autochanger (Jukebox)
> 
> /dev/rmt/0mbn -> ../../devices/pci@1f,0/pci@1/scsi@2,1/st@4,0:mbn
> 
> 
> But there is no 'st@4,1' either.
> 
> So which software do I need to install or what configuration is needed?

Find your "Getting Started" document, or download same as an acrobat file
for the HP support website.  It includes very specific switch settings
for Sun (and other OS's) systems.  Some of the switches are on the back
panel, and others are on the drive bottom and require case removal for
external drives or unmounting for internal drives.

To get the lun 1 (st@4,1 vs st@4,0) you will also have to tell Solaris
to scan those lun's on reboot.  To do this edit the file /kernel/drv/st.conf.
Near the end are lines like:

# name="st" class="scsi" target=2 lun=0;
# name="st" class="scsi" target=3 lun=0;
# name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
# name="st" class="scsi" target=6 lun=0;

My scsi id is 5, yours appears to be 4, thats fine.  Make sure the appropriate
line is uncommented for your target id.  As supplied I think all are uncommentd
from 0 to 6.  I commented out the unneeded ones for a minor speed up of reboots.
But if I ever change scsi id target on my tape drive, or add another drive, I
will have to remember to uncomment these lines.

Also as supplied, no LUN's except 0 are scanned.  You will have to add at least
the one "lun=1" line for your target id.  Doesn't hurt to add for all targets,
again with minor reboot slowdown.

Note also that anytime you upgrade your Solaris from 2.6 -> ??? or install a
patch that affects the st driver, this file will be overwritten and the changes
will have to be remade.  A couple of times I've done some admin tasks and
amanda stopped working -- OH yeah, got to reset st.conf.

While you are in this file, just check that it knows about your changer.  There
should be two other entries of interest.  In the top half of the file should
be aline that is used during boot to identify your tapedrive.  Mine looks like
this, YMMV:

"HP  C1557A", "HP DDS-3 4mm DAT loader",   "HPdds3",

The last field is a label pointing to an entry in the second half of the file
that provides initialization values for the scsi tape driver.  My HPdds3 line is:

HPdds3= 1, 0x34,0, 0x0D639, 4, 0x00, 0x13, 0x24, 0x03, 3;

After these, do a reconfigure boot.  I get both a /dev/rmt/0 and /dev/rmt/1.
The higher number is the changer device, the lower the tape drive.

BTW HP has their own program "mtx" to manipulate the changer and versions are
available for Solaris at ftp.hp.com.  The freeware mtx works also.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Amanda, multiple tape drives, and native restores

[Brian Cuttler]

I'd second Frank (Smith)'s idea.

With our 2nd jukebox and LTO drives I'd much prefer to use
a single amanda config rather than the current config, designed
to utilize both drives at the same time (no matter how well it 
is working) of 2 amanda configs, one for local and one for remote
disks, running _concurrently_ on the same processor.

>Has anyone considered setting up a pool of 2 or more drives, and
> having a master taper process that would assign DLEs to a particular
> drive whenever a drive was available?  It could be round-robin, with
> a little extra logic to do some size leveling.  If you had two drives,
> half of your DLEs (size-wise) would end up on drive 1 and half on
> drive 2.  To restore a given DLE you would only need one of those tapes.

Unsubscribe

[Marcelo Pinto]

I cannot unsubscribe me from this list. Please, anyone, help me!!!
MarceloBusca Yahoo! 
O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.

Re: sol 2.6 HP-C1557A (12000e) changer device

[Martin hepworth]

Sounds like you need to get the chg- working first.

have a look at the docs in the tape-changer directory.



--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
+44 (0)1865 842300

Gene Heskett wrote:

On Monday 10 February 2003 06:48, [EMAIL PROTECTED] wrote:


Hello

I did lots of reading manuals and mailing lists but still not
succeeded in having amanda talk to the changer.

Config:
amanda 2.4.3
solaris 2.6
HP surestore C1557A (12000e)

Previous installation of Soltice jukebox uses '/dev/lus'. But
amanda cannot use it.

***
/dev/lus ->
../devices/pci@1f,0/pci@1/pci@3/SUNW,isptwo@4/lus@0,0:0

[pbrazor1]/export/home/amanda$ amtape Daily show
amtape: could not get changer info: open: /dev/lus: Bad file
number ***

There is only 1 device in rmt '/dev/rmt/0...' .
Installation test-routine of the changer software says:


[pbrazor1]/etc/LGTOuscsi$ ./inquire
[EMAIL PROTECTED]:FUJITSU MAB3091S SUN9.0G1806|Disk,
/dev/rdsk/c0t3d0s2 [EMAIL PROTECTED]:HP C1557A U709|Tape,
/dev/rmt/0mbn
[EMAIL PROTECTED]:HP C1557A U709|Autochanger (Jukebox)

/dev/rmt/0mbn -> ../../devices/pci@1f,0/pci@1/scsi@2,1/st@4,0:mbn


But there is no 'st@4,1' either.

So which software do I need to install or what configuration is
needed?

Thanks for any help
urs



I don't believe this is an amanda problem, but a solaris kernel 
problem.  Unforch, I'll leave the definitive solaris answers to 
Jon.

If its anything like linux, then you should find the correct device 
in the /var/log/dmesg (or whatever solaris calls it) file. If its 
not there, the next question is, is solaris doing a 'scan all luns' 
on boot, I believe it must in order to find the changer robot since 
many of them are located at the same bus address as the drive 
itself, but at a higher Logical Unit Number, aka 'lun'.  For a 
linux kernel, this must be turned on in the kernel config and the 
kernel rebuilt as it doesn't default to on.





**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

RE: running amlable from CRON

[Keith Higgs]

Why would anybody want to do this? If a tape containing vital
information is in the drive at the time amlabel will still label the
tape for use with AMANDA. Then, if you follow through and actually allow
AMANDA to write to that tape you will have lost that vital information.

I have an Oracle 9i database that I am backing up frequently.  I have
enough tapes for a two week cycle plus one pre-labeled and ready to go.
It really does NOT take that long to prepare this many tapes in a single
sitting.  Once they're labelled you can pretty much forget about them
aside from cycling new tapes into the pool as they age.

D. Keith Higgs  x0559
 Case Western Reserve University, Webmaster - University Library
 Additional Information at http://www.cwru.edu/UL/ and
http://keith.cwru.edu/
"Follow the white rabbit."


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of Mitch Collinsworth
> Sent: Friday, February 07, 2003 09:50 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: speed problem
> 
> 
> 
> Hi David,
> 
> Sun hardware is really not my area of expertise, but I'm sure 
> there are
> others on amanda-users who can answer this.  If your Sun 
> boxes will only
> do 10 Mbps/half-duplex then just make sure your switch ports 
> are set to
> either auto/auto or 10/half and you'll be fine.
> 
> -Mitch
> 
> 
> On Fri, 7 Feb 2003 [EMAIL PROTECTED] wrote:
> 
> > Mitch.
> > Here is the version of my Sun OS:
> > "SunOS gitpocs02 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-5_10"
> > The /dev/hme is "FEPS Ethernet Driver  v1.115"
> > The host seems too old to support 100/full-duplex.
> > Do you agree?
> >
> > Thanks!
> >
> > David
> >
> > -Original Message-
> > From: Mitch Collinsworth [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, February 06, 2003 7:18 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: speed problem
> >
> >
> >
> > On Thu, 6 Feb 2003 [EMAIL PROTECTED] wrote:
> >
> > > My tape server is a Linux host (Redhat 7.3).
> > > My clients are either Linux hosts or Sun Solaris hosts.
> > > All client hosts are on the same domain.
> > > When I run 'amdump' to backup Linux hosts, the speed is 
> pretty good.
> > > When I run 'amdump' to backup Sun Solaris hosts, the 
> speed is extremely
> > > slow.
> > > It seems not a network or hardware issue.
> >
> > Seems?  You don't sound particularly sure on this point...  In my
> > experience one thing that is a frequent cause of deadly slow network
> > backups is a duplex mismatch between a backup client and 
> the ethernet
> > switch it connects to.  I've seen systems that the user had 
> been happily
> > using without complaint for weeks or months before asking 
> for backups.
> > When their backup went painfully slow I'd check their 
> network settings
> > and invariably find a duplex mismatch.
> >
> > Another cause of slowness can be doing client compression, 
> especially
> > "client best" on slow hardware.  How old/slow are your 
> Solaris boxen?
> >
> > -Mitch
> >
> 

Re: Question about amlabel

[Paul Bijnens]

Pro-Fit wrote:

Hey folks - thanks for all your help - another newbie
question...

Is it possible to put the amlabel process in the CRON
as opposed to running it manually everyday?  How would
one do this?


I wouldn't do it... :-)

The label on the tape serves some useful purposes.  First it verifies
that the tape in the device is indeed an Amanda tape, and not some
other tape containing the data for your nobel prize project.
With the tapelabel, Amanda can verify that she has the expected tape
and not one that should not yet be overwritten (i.e. not yesterdays 
backup that you forgot to take out, because you had a day off for example).

That's why you first label your tapes, when you awake, and not half 
sleeping, and after three times verifing that you put in the correct
tape in the drive.  And you also put a sticker on the tape with the
Amanda's label on it, e.g. DailySet1-001.  Stickers cannot be put on a 
tape by cron afaik.

Once labelled, you normally never ever have to relabel a tape.

Taking this in consideration, you don't need to amlabel a tape by a cron 
command at night, wiping out whatever tape was someone put by accident 
in the tape drive.  There is nobody around to verify that the tape that 
you put in around 5 PM is still the same...

If you do feel the need to relabel a tape each time it is used by 
Amanda, you are probably trying to force Amanda into something for which 
she is not designed, like labeling your tapes "monday", "tuesday", etc.
Look in the archives of this list to find the arguments against this scheme.

ps.  If you really are smarter than Amanda, try this command in your 
crontab: "amlabel -f  ", about 5 minutes before the 
amdump entry.

pps.  if you really are smarter than Amanda, you would already know the 
above command too :-)



--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: sol 2.6 HP-C1557A (12000e) changer device

[Gene Heskett]

On Monday 10 February 2003 06:48, [EMAIL PROTECTED] wrote:
>Hello
>
>I did lots of reading manuals and mailing lists but still not
> succeeded in having amanda talk to the changer.
>
>Config:
>amanda 2.4.3
>solaris 2.6
>HP surestore C1557A (12000e)
>
>Previous installation of Soltice jukebox uses '/dev/lus'. But
> amanda cannot use it.
>
>***
>/dev/lus ->
> ../devices/pci@1f,0/pci@1/pci@3/SUNW,isptwo@4/lus@0,0:0
>
>[pbrazor1]/export/home/amanda$ amtape Daily show
>amtape: could not get changer info: open: /dev/lus: Bad file
> number ***
>
>There is only 1 device in rmt '/dev/rmt/0...' .
>Installation test-routine of the changer software says:
>
>
>[pbrazor1]/etc/LGTOuscsi$ ./inquire
>[EMAIL PROTECTED]:FUJITSU MAB3091S SUN9.0G1806|Disk,
> /dev/rdsk/c0t3d0s2 [EMAIL PROTECTED]:HP C1557A U709|Tape,
> /dev/rmt/0mbn
>[EMAIL PROTECTED]:HP C1557A U709|Autochanger (Jukebox)
>
>/dev/rmt/0mbn -> ../../devices/pci@1f,0/pci@1/scsi@2,1/st@4,0:mbn
>
>
>But there is no 'st@4,1' either.
>
>So which software do I need to install or what configuration is
> needed?
>
>Thanks for any help
>urs

I don't believe this is an amanda problem, but a solaris kernel 
problem.  Unforch, I'll leave the definitive solaris answers to 
Jon.

If its anything like linux, then you should find the correct device 
in the /var/log/dmesg (or whatever solaris calls it) file. If its 
not there, the next question is, is solaris doing a 'scan all luns' 
on boot, I believe it must in order to find the changer robot since 
many of them are located at the same bus address as the drive 
itself, but at a higher Logical Unit Number, aka 'lun'.  For a 
linux kernel, this must be turned on in the kernel config and the 
kernel rebuilt as it doesn't default to on.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

Re: Question about amlabel

[Gene Heskett]

On Monday 10 February 2003 06:58, Pro-Fit wrote:
>Hey folks - thanks for all your help - another newbie
>question...
>
>Is it possible to put the amlabel process in the CRON
>as opposed to running it manually everyday?  How would
>one do this?
>
>Thanks!
>
That should be a one time per tape, for the lifetime of that tape, 
operation.

Why do you need to do it every night?

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

Re: Problems with full backups

[Joshua Baker-LePain]

On Mon, 10 Feb 2003 at 3:37pm, Bradley Marshall wrote

> I've got a config thats set to do full backups that I run seperately
> to my normal one.  However, whenever I run it, I get the following in
> the report:
> 
>   FAILURE AND STRANGE DUMP SUMMARY:
> driver: FATAL driver received unexpected token (2) from taper
> 
> It does about 26 filesystems ok, but fails on 3, with the above error
> message.  There are no other obvious error messages in the report.
> 
> I'm using tar for all my disks, and have no troubles with my normal
> backups.  Any ideas?  Please let me know if there's any information
> I've missed that can be useful.

OS, version, and amanda version would be helpful.  Also, look in your 
system logs for any error messages around the time of the failed backups.  
Finally, look in the amdump.N file for exactly what taper told driver.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Question about amlabel

[Pro-Fit]

Hey folks - thanks for all your help - another newbie
question...

Is it possible to put the amlabel process in the CRON
as opposed to running it manually everyday?  How would
one do this?

Thanks!

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

sol 2.6 HP-C1557A (12000e) changer device

[forster]

Hello

I did lots of reading manuals and mailing lists but still not succeeded
in having amanda talk to the changer.

Config:
amanda 2.4.3
solaris 2.6
HP surestore C1557A (12000e)

Previous installation of Soltice jukebox uses '/dev/lus'. But amanda cannot
use it.

***
/dev/lus -> ../devices/pci@1f,0/pci@1/pci@3/SUNW,isptwo@4/lus@0,0:0

[pbrazor1]/export/home/amanda$ amtape Daily show
amtape: could not get changer info: open: /dev/lus: Bad file number
***

There is only 1 device in rmt '/dev/rmt/0...' .
Installation test-routine of the changer software says:


[pbrazor1]/etc/LGTOuscsi$ ./inquire
[EMAIL PROTECTED]:FUJITSU MAB3091S SUN9.0G1806|Disk, /dev/rdsk/c0t3d0s2
[EMAIL PROTECTED]:HP C1557A U709|Tape, /dev/rmt/0mbn
[EMAIL PROTECTED]:HP C1557A U709|Autochanger (Jukebox)

/dev/rmt/0mbn -> ../../devices/pci@1f,0/pci@1/scsi@2,1/st@4,0:mbn


But there is no 'st@4,1' either.

So which software do I need to install or what configuration is needed?

Thanks for any help
urs