Re: DLT vs. AME autoloaders.

[C. Chan]

Also Sprach Olivier Nicole:

> >The next part of my question is about DLT vs. AME technologies
> >themselves.  It seems like everyone
> >uses DLT for its reliability but AME (including Mammoth and AIT) boast
> >faster transfer rates
> >and greater capacity.  I was wondering if anyone had any horror stories
> >or personal experiences to help
> >me to decide which technology to go with.
>

AME (Advance Metal Evaporative) is a tape media technology. Linear tapes
for the most part use another tape media technology called AMP (Advance
Metal Particle). AME currently is capable of higher data densities
which is a requirement for 8mm helical scan tape drives since
they use smaller cartridges. Both media technologies claim excellent
shelf life and reuse cycles.

Linear and helical scan technologies are both mature technologies
and proven reliable for many applications. The marketing literature
from each side would have you believe the other technology is
a steaming pile of crap destined for an early inglorious extinction,
but we all know what marketing is worth. As for word of mouth
comparison, there aren't that many admins who have experience
with both technologies, most chose one early on and stick
with it since it's a bloody pain to migrate.

Mammoth and AIT do not have higher single cartridge capacities
or higher transfer rates. SuperDLT and LTO Ultrium have single
cartridge capacities of ~100GB and transfer rates of > 12MB/s.
Mammoth 2 has a native capacity of 60GB and AIT-2 50GB. Both
have roadmaps with 100GB capacity within the next year however.

DLT has more of a track record than the other midrange tape
technologies, mostly because throughout the early '90s it was
the only decent midrange tape drive. DDS2 and Exabyte 8x00 were
really quite unreliable. As a result you will hear a lot of
(mostly justified) praise from system administrators for DLT;
however, this does not mean that other tape drives are not
reliable or worthy of consideration. As mentioned by Mr. Olivier,
Tandberg SLR is another worthy linear tape competitor which
is actually less expensive for a given capacity than DLT.

I would say that linear tape has an advantage in transfer rate
and cartridge capacity. Linear tapes are also less susceptible to
environmental factors like dust or smoke.

8mm helical scan has faster time to restore, especially Sony AIT with
static RAM on each cartridge. This is important in HSM applications
where IBM Magstor is really the only option among linear tapes.
8mm autoloaders and jukeboxes also have higher data densities since
the cartridges are smaller, making them the storage of choice in
space constrained operations.

In short there is no simple answer.

--
C. Chan < [EMAIL PROTECTED] > 
Finger [EMAIL PROTECTED] for PGP public key.

Re: DLT vs. AME autoloaders.

[Olivier Nicole]

>The next part of my question is about DLT vs. AME technologies
>themselves.  It seems like everyone
>uses DLT for its reliability but AME (including Mammoth and AIT) boast
>faster transfer rates
>and greater capacity.  I was wondering if anyone had any horror stories
>or personal experiences to help
>me to decide which technology to go with.

You said it all, reliability. When you NEED the backup, then you must
be able to trust your tapes, and be sure that files are there and
readable...

Any other consideration come second.

I am very happy with SLR myself (another linear technoligy). And I
could check that the transfer rate that is advertised can be really
achieved in running condition.

Olivier

Re: Solaris 8 s28_38shwp2 SPARC

[Olivier Nicole]

On synnu1, check /tmp/amanda/* 

And don't take a no for an answer :)

Olivier

Re: Cannot execute runtar after upgrade: Redhat 6.2 --> 7.1

[Michael Hannon]

At 03:16 PM 7/6/2001 -0500, John R. Jackson wrote:
> >...  We recently upgraded one of our Amanda servers to Redhat 7.1
> >(from Redhat 6.2), and we experienced some difficulties with the backup
> >after that.  ...
>
>In the process, did you switch to running amandad from xinetd (instead
>of inetd)?  Did you fix the xinetd config file (the RPM's have it wrong,
>last I heard).  There are examples in the Amanda FAQ.  In particular,
>you probably want "groups yes".

We're certainly running from xinetd now.  Our inetd.conf amanda entries got 
converted automatically during the upgrade.  (I don't know to which RPM's 
you're referring, but we don't run Amanda from RPM's.)  It looks as if adding:

 group  = adm
 groups = yes

to all of /etc/xinetd.d/am* is sufficient to fix the problem.

Thanks, John.

 - Mike

Re: Solaris 8 s28_38shwp2 SPARC

[John R. Jackson]

>... I inquired to the group of admins here if
>anything had changed on this box or if any outages occured but they
>have responded with 'no'.

And you believed them???  :-)

>ERROR: sunny1.neptune.com: [access as amanda not allowed from
>[EMAIL PROTECTED]]

The problem is with your ~amanda/.amandahosts file on sunny1.neptune.com.
It should contain:

  sunny1.neptune.com amanda

You should also make sure user "amanda" has access to the file (i.e. it
owns it) and that it has search permission down through the directories
to it.  For instance, try this on sunny1.neptune.com:

  su amanda -c "cat ~amanda/.amandahosts"

(you may need to substitute the home directory of "amanda" for ~amanda).

>Denise E.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

DLT vs. AME autoloaders.

[Frank J. Miles]

This is really a 2 part question.

I was wondering if anyone had experience with various drivers for
autoloaders with DLT or AME autoloaders in Linux.  Every dealer that I
talk to claims that I must buy 3rd party software
to get the drivers for their autoloaders/libraries.  From the posts to
the list, it seems that there are plenty
of people using autoloaders but also using Amanda.  If you had to go out
and buy backup software then
it would seem less likely that you would use Amanda.  I haven't used any
commercial software, so I don't
know how it stacks up with Amanda.  Will most autoloaders natively work
with Linux drivers?

The next part of my question is about DLT vs. AME technologies
themselves.  It seems like everyone
uses DLT for its reliability but AME (including Mammoth and AIT) boast
faster transfer rates
and greater capacity.  I was wondering if anyone had any horror stories
or personal experiences to help
me to decide which technology to go with.

Re: [Fwd: amdump taking over a day to complete]

[Erick Bodine]

John,

I tried running dump by itself and it turns out that dump on the tape server was the 
problem.  I upgraded to the latest version (dump-0.4b19-5.6x.i386.rpm) and everything 
is working fine now.  Once again, a problem not with amanda but with something else.

Many thanks for your suggestions.

Erick Bodine
Xpedite Systems Inc.


"John R. Jackson" wrote:

> > The slow client is a Toshiba Magna 3000 with a single 18-GB SCSI disk.  I am
> > backing up another partition on the same disk on the same host at the same ti
> >me with no problems.  I do not see any disk or network errors on either the cl
> >ient or the tape backup
> > server.
>
> The next thing I'd try is doing the backup command by hand on the
> client and watching closely what happens.  If you're using GNU tar,
> I just posted yet another dissertation on how to do this.  Look for the
> "Problem backing up" thread.
>
> If you're using dump, just run the command from sendbackup*debug but
> without the 'u' option.  Doing a catalogue is not as useful in this case
> because of the way dump images are formatted.  Better would be to write
> it to a file and see how fast it's growing, although I realize that might
> need more scratch disk space than you have.  Next better would be to pipe
> the output to an rsh over to your tape server and drop it in your holding
> disk (assuming it's big enough), although that introduces other variables.
>
> Or you could try piping the output to the attached C program (and then
> to /dev/null).  I just slapped it together, but it seems to give a rough
> idea of how much output has been generated in more or less real time.
>
> > Erick Bodine
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
>   
>
>   Name: xx.c
>xx.c   Type: C Source file (application/x-unknown-content-type-cfile)
>Description: xx.c

Re: inetd on crack

[xavier]

John R. Jackson wrote:

>>... inetd on the client machine starts 
>>to eat more and more cpu ressources up to 98% ...
>>
>
>If it's inetd chewing up the resources, then you need to talk to your
>OS vendor.  It's unlikely Amanda can cause that.
>
>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
I finally solved my problem, seems that amrecover corrupted (somehow) 
amandad. So i've copied the demon from my server to my client and ran it 
from command line with user 'operator' ...  the system was missing some 
libraries (more precisely libc and libreadline) .

So if anyone as the same problem, that is it

Re: Cannot execute runtar after upgrade: Redhat 6.2 --> 7.1

[John R. Jackson]

>...  We recently upgraded one of our Amanda servers to Redhat 7.1 
>(from Redhat 6.2), and we experienced some difficulties with the backup 
>after that.  ...

In the process, did you switch to running amandad from xinetd (instead
of inetd)?  Did you fix the xinetd config file (the RPM's have it wrong,
last I heard).  There are examples in the Amanda FAQ.  In particular,
you probably want "groups yes".

>But I still don't understand why this issue arose in the first place.  Our 
>nsswitch.conf file calls for local files to be searched before the NIS maps 
>are consulted for group information:
>...
>Recall that this is all happening on one system, the server system.  Why 
>isn't /etc/group consulted, thereby showing amanda's membership in the adm 
>group?  ...

You're asking the wrong people.  Amanda does not do anything with groups.
Xinetd initializes all that for the services it starts (e.g. amandad).
You need to ask the xinetd/Redhat folks.

> - Mike

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Solaris 8 s28_38shwp2 SPARC

[Denise Ives]

All,

Just this past week out of the blue amanda on sunny1 (tapeserver) is
returning access denied. I inquired to the group of admins here if
anything had changed on this box or if any outages occured but they
have responded with 'no'.

I've checked host IP entries in /etc/host

amanda entires in /etc/inetd.conf
the .amandahosts entry

and still can not figure out this access problem we are having.

Any help?




Amanda Backup Client Hosts Check

ERROR: sunny1.neptune.com: [access as amanda not allowed from
[EMAIL PROTECTED]]




-- 
Denise E.

Re: starttime weirdness

[John R. Jackson]

>Well, I only ever want to write to tape when running this config and
>so have not specified a holding disk at all.

Oh.  Well that explains a few things :-).

>Given this, how would you think Amanda would then behave?

As I said, I'm just guessing based on a quick read of the code, but I
think if you had enough holding disk for the largest image you'll get
from PC, it will do what you want.

In any case, if you've got the disk, it would certainly be worth testing
at least once.  If it doesn't help, you haven't lost anything since you
can grab the holding disk space back.

>Paul Yeatman

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Cannot execute runtar after upgrade: Redhat 6.2 --> 7.1

[Michael Hannon]

Greetings.  We recently upgraded one of our Amanda servers to Redhat 7.1 
(from Redhat 6.2), and we experienced some difficulties with the backup 
after that.  In particular, Amanda was suddenly unable to execute "runtar" 
on the server itself!.  (I.e., it isn't a question of root access to 
NFS-mounted file systems, etc.)

This is on a server system which uses NIS as one source of information.

I found a thread on this topic from early this year in the archives for 
this list.  I didn't find that discussion particularly useful, as it 
focused mostly on obvious permission problems, etc.  I think the issue is a 
little more subtle than that and may relate to a bug in Redhat 
software.  I'd like to bounce some ideas off of this group to see if 
anybody has any additional insight.

The crucial thing about the use of runtar is that it is an suid (root) 
program, which allows *group* execution.  The idea is to place the amanda 
user (which we call amanda) into the group associated with runtar.

[root@server libexec]# pwd
/usr/local/libexec
[root@server libexec]# ls -l runtar
-rwsr-x---1 root amanda  99369 Jul  5 18:18 runtar

(Note that the associated group here was originally "adm", rather than 
amanda.  See discussion below.)

We had placed amanda into two groups, adm and disk.  That worked fine under 
Redhat 6.2.  It doesn't appear to work under Redhat 7.1.  The reason for 
that is, evidently, that Redhat's NIS implementation does not put group 
ID's lower than MINGID=500 into the NIS maps.  (See /var/yp/Makefile)  For 
instance:

[root@server libexec]# groups amanda
amanda : amanda adm disk


[root@server libexec]# ypcat -k group | grep amanda
amanda amanda:x:656:amanda

Putting amanda into a "non-privileged" group (also called amanda) and 
associating that group with runtar appears to have solved our problem.

But I still don't understand why this issue arose in the first place.  Our 
nsswitch.conf file calls for local files to be searched before the NIS maps 
are consulted for group information:

[root@server /etc]# grep group nsswitch.conf
#group: db files nisplus nis
group:  files nis
netgroup:   files nis

Recall that this is all happening on one system, the server system.  Why 
isn't /etc/group consulted, thereby showing amanda's membership in the adm 
group?  Note that /etc is browseable by everybody and /etc/group is world 
readable.

Thanks.

 - Mike

==
Michael Hannonmailto:[EMAIL PROTECTED]
Dept. of Physics  530.752.4966
University of California  530.752.4717 FAX
Davis, CA 95616-8677

Re: starttime weirdness

[peanut butter]

Hi and thanks for the help.

--From John R. Jackson--
> I'm not sure that's what's going on.  Note the following:
> 
> >driver-idle: no-diskspace
> 
> As far as I can tell from the code, Amanda will run everything it can
> before those with a delay (but see below).  The problem is, the "best"
> client (your PC) appears to not fit in the holding disk, based on the
> "no-diskspace" status above.
> 
> Amanda always leaves direct to tape backups until after all the ones
> that could go into the holding disk.  So yes, it's going to not do the
> PC until after the other machines, but it's because the dump won't fit
> in the holding disk, not because of the delayed start.
> 
> I think :-).

Well, I only ever want to write to tape when running this config and
so have not specified a holding disk at all.

Given this, how would you think Amanda would then behave?

Do you think there is a good possibility I would get the result I want
if I designated some holding space?

-- 
Paul Yeatman   (858) 534-9896[EMAIL PROTECTED]
 ==
 ==Proudly brought to you by Mutt==
 ==

Re: changer problems

[John R. Jackson]

>Still  I have problems with amanda 2.4.2p2 and my changer. I got the 
>error "amcheck-server: could not get changer info: badly formed result 
>from changer: "/usr/local/libexec/chg-zd-mtx: [: -eq: unary operator 
>expected"

What version of mtx are you using?  What does "mtx -f /dev/sga status"
have to say (in particular, the "Data Transfer Element" lines)?

>Sandra

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: compiling on aix 4.3.3

[John R. Jackson]

>I've been trying all day to compile the latest stable release of amanda on aix
> 4.3.3.  ...

I do this pretty often with no problem.

What do you mean by "the latest stable release"?

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

compiling on aix 4.3.3

[John Jolet]

I've been trying all day to compile the latest stable release of amanda on aix 4.3.3.  
Everything seems fine, except when it hits the client-src directory, it fails thusly:
Making all in client-src
/usr/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config 
-I../common-src-g -O2   -c getfsent.c
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -g -O2 -c getfsent.c -o 
getfsent.o
getfsent.c: In function `open_fstab':
getfsent.c:154: `MNTTAB' undeclared (first use in this function)
getfsent.c:154: (Each undeclared identifier is reported only once
getfsent.c:154: for each function it appears in.)
make: 1254-004 The error code from the last command is 1.


Stop.
make: 1254-004 The error code from the last command is 1.

this is confusing me...  There's neither an fstab, nor an mnttab in aix.  Am I missing 
something here?  I'm using the gcc and gnu automake.  the only arguments I gave 
configure was the --with-user and --with-group directives.

Help!  I've searched the archives, and I see lots of people seem to be using aix, but 
I can't find this error.


-- 

Re: Symbolic Link and Next Tape Prediction ?

[John R. Jackson]

>I choose to do that using amcheck instead ...

I agree amcheck is the better tool, however ...

>I taught my guys to change the tape in the morning when the previous
>back-up is over (new tape name is at top of amdump report).

The problem is that Edward said "They will not receive amanda email to
check for next tape name".  I was just pointing out how the "what tape
is next" information (without the whole Amanda daily report) could be
sent to his operators so they would know what to mount.

And if they don't get the normal run mail, they also won't get the amcheck
"I didn't like that tape" mail so they can fix it before the real run.

>Olivier

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: FW: chg-scsi

[Todd Pfaff]

I've just been through this (ie. using the newer, supported chg-scsi from
the 2.5.0 cvs development source with an amanda-2.4.2p2 server) so the
procedure is fresh in my mind.  Here's what you do.

- build and install your 2.4.2p2 server
- get the 2.5.0 source via cvs
- first, login to cvs server
- just press enter when prompted for password
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/amanda login 
- next, get the source
- this will retrieve the entire 2.5.0 source from the cvs server into
  your current directory
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/amanda co amanda 
- build the amanda-2.5.0 server from this source (you may need the
autoconf tools to proceed with this, but don't ask me any questions about
this, you're on your own)
- when the build is finished, copy changer-src/chg-scsi to your
amanda-2.4.2p2 server libexec directory

That's it!  Works great with an Exabyte 215 changer and Mammoth2 drive.

--
Todd Pfaff \  Email: [EMAIL PROTECTED]
Computing and Information Services  \ Voice: (905) 525-9140 x22920
ABB 132  \  FAX: (905) 528-3773
McMaster University   \
Hamilton, Ontario, Canada  L8S 4M1 \

Re: help: problems building Amanda 2.4.2p2 on HP-UX v10.20

[Stephen Walton]

Here's the configure command I've used to build Amanda 2.4.2p2 on two
HP-UX 10.20 machines (an aging 735/99 and a newer K460) with no trouble:

./configure  --with-user=amanda --prefix=/opt/amanda-2.4.2p2 \
--localstatedir=/var/opt --with-configdir=/etc/opt/amanda \
--with-amandahosts --with-group=sys \
--with-includes=/opt/readline/include \
--with-libraries=/opt/readline/lib

Notice the leading period.  Also notice that I downloaded and installed
the precompiled readline HP-type software depot from hpux.cs.utah.edu.
Is it possible that Mr.  Rivera has another configure command on his
search path which is getting picked up before the one in the current
directory?

-- 
Stephen Walton, Professor of Physics and Astronomy,
California State University, Northridge
[EMAIL PROTECTED]

On Mon, 2 Jul 2001, Rivera, Edwin wrote:

> hello all,
>
> i'm trying to build amanda on an HP A180 box running HP-UX v10.20, however,
> I'm running into the following errors when running ./configure.

changer problems

[Sandra Panesso]

Hi :

Still  I have problems with amanda 2.4.2p2 and my changer. I got the 
error "amcheck-server: could not get changer info: badly formed result 
from changer: "/usr/local/libexec/chg-zd-mtx: [: -eq: unary operator 
expected"

Amanda Backup Client Hosts Check

Client check: 8 hosts checked in 0.445 seconds, 0 problems found

(brought to you by Amanda 2.4.2p2)

this my amanda.conf that  is /usr/local/etc/amanda/miro_daily

runtapes 6  # number of tapes to be used in a single run of 
amdump
 # we have two to enable writing to holding disk 
for morn
ing amflushes.
tpchanger "chg-zd-mtx"  # the tape-changer glue script
 # Even though tapedev is ignored since we use
 # tpchanger, we keep this in case we need to 
revert
 # to no changing.
tapedev "/dev/nst0" # the no-rewind tape device to be used
rawtapedev "/dev/null"  # the raw device to be used (ftape only)
#changerstatus "/usr/local/etc/amanda/miro_daily/changer-status"
changerfile "/usr/local/etc/amanda/miro_daily/changer"
changerdev "/dev/sga"

tapetype DDS3
--
my changer.conf file  is on /usr/local/etc/amanda/miro_daily

number_configs  1
eject   0   # Tapedrives need an eject command
number_configs  1
sleep   90  # Seconds to wait until the tape gets ready
cleanmax100 # How many times could a cleaning tape get used
changerdev  /dev/sga
#
# Next comes the data for drive 0
#
config  0
drivenum0
dev /dev/nst0
scsitapedev /dev/sga
startuse1   # The slots associated with the drive 0
enduse  6   #
statfile/usr/local/etc/amanda/miro_daily/tape0-slot  # The file 
where th
e actual slot is stored
#cleancart  6   # the slot where the cleaningcartridge for drive 
0 is lo
cated
#cleanfile  /usr/local/etc/amanda/miro_daily/cleanfile # The file 
where the
cleanings are recorded
usagecount  /usr/local/etc/amanda/miro_daily/totaltime
tapestatus  /usr/local/etc/amanda/miro_daily/changer-status # here 
will some
  status infos be stored
[root@miro miro_daily]# vi changer.conf

number_configs  1
eject   0   # Tapedrives need an eject command
sleep   90  # Seconds to wait until the tape gets ready
cleanmax100 # How many times could a cleaning tape get used
changerdev  /dev/sga
#
# Next comes the data for drive 0
#
config  0
drivenum0
dev /dev/nst0
scsitapedev /dev/sga
startuse1   # The slots associated with the drive 0
enduse  6   #
statfile/usr/local/etc/amanda/miro_daily/tape0-slot  # The file 
where th
e actual slot is stored
cleancart   6   # the slot where the cleaningcartridge for drive 
0 is lo
cated
cleanfile   /usr/local/etc/amanda/miro_daily/cleanfile # The file 
where the
cleanings are recorded
usagecount  /usr/local/etc/amanda/miro_daily/totaltime
tapestatus  /usr/local/etc/amanda/miro_daily/changer-status # here 
will some
  status infos be stored


this my chg-zd-mtx file in /usr/local/libexec

  firstslot=1  1st tape slot
  lastslot=5  Last tape slot
  cleanslot=6  Slot with cleaner tape
#
#   # Do you want to clean the drive after a certain number of accesses?
#   # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we
#   #have no reliable way to count this. A single amcheck could
#   #generate as many accesses as slots you have, plus 1.
#   # ALSO NOTE - many modern tape loaders handle this automatically.
#
  AUTOCLEAN=0  Set to '1' or greater to enable
#
  autocleancount=99    Number of access before a clean.
#
  havereader=1 If you have a barcode reader, set to 1.

#
  offlinestatus=0  Set to 0 if 'mt status' gives an
OFFLINE_BEFORE_UNLOAD=0  Does your tape driver require a
#  'mt offline' before mtx unload?


# You may need to customize these things
MT=/bin/mt
MTF=-f
MTX=/usr/local/bin/mtx



So anything is wrong with that?


I hope you guys can help me.


Thanks,

Sandra

unsubscribe

[Kevin Cade]

unsubscribe

FW: chg-scsi

[Rob Earl]

Gene,

Sorry for this chain of e-mails, but different thoughts keep popping into my
head.  One thing I should mention to you in case you didn't see it in other
e-mails is that I'm using a Compaq TL891 Tape Library, not a Seagate
product.  Do you think the chg-scsi interface is what I should be using with
the Compaq Tape Library?  If not, what would you recommend?

Thanks,
Rob


-Original Message-
From: Rob Earl [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 9:03 AM
To: Gene Heskett; John R. Jackson
Cc: Amanda-Users
Subject: FW: chg-scsi


Gene,

Here are the linking errors:

ld:
Unresolved:
ScanBus
SCSI_OpenDevice
SCSI_CloseDevice
Tape_Status
DumpSense
Sense2Action
SCSI_ExecuteCommand
Tape_Ioctl
make: *** [chg-scsi] Error 1

Thanks,
Rob

-Original Message-
From: Rob Earl [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 8:45 AM
To: Gene Heskett; John R. Jackson
Cc: [EMAIL PROTECTED]
Subject: RE: chg-scsi


Hi Gene,

Here's what I did.

I went to the sourceforge site to the following link:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/amanda/amanda-2/changer-src/

I then downloaded each file and replaced the changer-src directory on my
machine with what I downloaded.  I ran ./configure from the Amanda directory
and then ran make.  I got errors that there was no Makefile for changer-src.
I noticed that there is only a Makefile.am file in the new changer-src
directory, so I moved the Makefile from the old changer-src to the new.  I
ran make again, but chg-scsi did not get built.  So I went to the
changer-src directory and ran "make chg-scsi" and got the exact same
unresolved errors that I was getting before.  Any ideas to what I'm doing
wrong for the build of this product?

Thanks,
Rob


-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 12:26 AM
To: John R. Jackson
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: chg-scsi


Gene Heskett sends Greetings to John R.;

>>I now have an executable program in the changer-src directory called
>>chg-scsi.  ...

>You just think you do :-).

>>I'm thinking this might have something to do with the unresolves during
the
>>build of chg-scsi.  ...

>Yup.

>>Is there something special I should set when building the executable?

>As I said, chg-scsi is not maintained in the released branches (I don't
>know the details -- one of the other authors does all the chg-scsi work).
>You'll probably need to get the CVS main branch version.  There are
>entries in the FAQ about how to get the CVS code, and my previous letter
>described (although possibly too briefly) what to do with it.

>If you have trouble getting it going, don't hesitate to post.

>>Rob

>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

John and Rob, chg-scsi was just re-worked in the cvs, with the
development work actually being done on my office machine about 2 weeks
back by Thomas Hepper.  It now works fairly well with a Seagate 4586NP
changer.  The corrected sources s/b in amanda-2/changer-src.

Cheers, Gene
--
  Gene Heskett, CET, UHK   |Amiga A2k Zeus040, 70MB ram, 31 gigs
   | Linux @ 500mhz, 320MB ram, 50 gigs
 email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
   
This messages reply content, but not any previously quoted material,
is © 2001 by Gene Heskett, all rights reserved.
--

FW: chg-scsi

[Rob Earl]

Gene,

Here are the linking errors:

ld:
Unresolved:
ScanBus
SCSI_OpenDevice
SCSI_CloseDevice
Tape_Status
DumpSense
Sense2Action
SCSI_ExecuteCommand
Tape_Ioctl
make: *** [chg-scsi] Error 1

Thanks,
Rob

-Original Message-
From: Rob Earl [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 8:45 AM
To: Gene Heskett; John R. Jackson
Cc: [EMAIL PROTECTED]
Subject: RE: chg-scsi


Hi Gene,

Here's what I did.

I went to the sourceforge site to the following link:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/amanda/amanda-2/changer-src/

I then downloaded each file and replaced the changer-src directory on my
machine with what I downloaded.  I ran ./configure from the Amanda directory
and then ran make.  I got errors that there was no Makefile for changer-src.
I noticed that there is only a Makefile.am file in the new changer-src
directory, so I moved the Makefile from the old changer-src to the new.  I
ran make again, but chg-scsi did not get built.  So I went to the
changer-src directory and ran "make chg-scsi" and got the exact same
unresolved errors that I was getting before.  Any ideas to what I'm doing
wrong for the build of this product?

Thanks,
Rob


-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 12:26 AM
To: John R. Jackson
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: chg-scsi


Gene Heskett sends Greetings to John R.;

>>I now have an executable program in the changer-src directory called
>>chg-scsi.  ...

>You just think you do :-).

>>I'm thinking this might have something to do with the unresolves during
the
>>build of chg-scsi.  ...

>Yup.

>>Is there something special I should set when building the executable?

>As I said, chg-scsi is not maintained in the released branches (I don't
>know the details -- one of the other authors does all the chg-scsi work).
>You'll probably need to get the CVS main branch version.  There are
>entries in the FAQ about how to get the CVS code, and my previous letter
>described (although possibly too briefly) what to do with it.

>If you have trouble getting it going, don't hesitate to post.

>>Rob

>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

John and Rob, chg-scsi was just re-worked in the cvs, with the
development work actually being done on my office machine about 2 weeks
back by Thomas Hepper.  It now works fairly well with a Seagate 4586NP
changer.  The corrected sources s/b in amanda-2/changer-src.

Cheers, Gene
--
  Gene Heskett, CET, UHK   |Amiga A2k Zeus040, 70MB ram, 31 gigs
   | Linux @ 500mhz, 320MB ram, 50 gigs
 email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
   
This messages reply content, but not any previously quoted material,
is © 2001 by Gene Heskett, all rights reserved.
--

RE: chg-scsi

[Rob Earl]

Hi Gene,

Here's what I did.

I went to the sourceforge site to the following link:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/amanda/amanda-2/changer-src/

I then downloaded each file and replaced the changer-src directory on my
machine with what I downloaded.  I ran ./configure from the Amanda directory
and then ran make.  I got errors that there was no Makefile for changer-src.
I noticed that there is only a Makefile.am file in the new changer-src
directory, so I moved the Makefile from the old changer-src to the new.  I
ran make again, but chg-scsi did not get built.  So I went to the
changer-src directory and ran "make chg-scsi" and got the exact same
unresolved errors that I was getting before.  Any ideas to what I'm doing
wrong for the build of this product?

Thanks,
Rob


-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 12:26 AM
To: John R. Jackson
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: chg-scsi


Gene Heskett sends Greetings to John R.;

>>I now have an executable program in the changer-src directory called
>>chg-scsi.  ...

>You just think you do :-).

>>I'm thinking this might have something to do with the unresolves during
the
>>build of chg-scsi.  ...

>Yup.

>>Is there something special I should set when building the executable?

>As I said, chg-scsi is not maintained in the released branches (I don't
>know the details -- one of the other authors does all the chg-scsi work).
>You'll probably need to get the CVS main branch version.  There are
>entries in the FAQ about how to get the CVS code, and my previous letter
>described (although possibly too briefly) what to do with it.

>If you have trouble getting it going, don't hesitate to post.

>>Rob

>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

John and Rob, chg-scsi was just re-worked in the cvs, with the
development work actually being done on my office machine about 2 weeks
back by Thomas Hepper.  It now works fairly well with a Seagate 4586NP
changer.  The corrected sources s/b in amanda-2/changer-src.

Cheers, Gene
--
  Gene Heskett, CET, UHK   |Amiga A2k Zeus040, 70MB ram, 31 gigs
   | Linux @ 500mhz, 320MB ram, 50 gigs
 email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
   
This messages reply content, but not any previously quoted material,
is © 2001 by Gene Heskett, all rights reserved.
--

Re: Specifig backup plan - HELP!

[Olivier Nicole]

>After looking around for a good OpenSourse backup solution, I
>decided to make use of Amanda. Now I'am facing a problem configuring
>this software the way it fits my company backup policy. Thus I am asking
>you, those who are surely more familiar with this topic.
>   Here are requirements I need to meet:

Then amanda may not be the tool for you.

You cannot choose when full dumps are done

You cannot easily mix-up monthly and weekly full dumps

You need one tape per DAY for incremental back-ups

All this can be worked around, but that will need dirty tricks, and
you will loose some benefits of Amanda when you want to restore
(applying the same tricks again).

Even using tapes A1 to A7 one week and tapes B1 to B7 on the other
week, is not straight forward.

Good luck

Olivier

unsubscribe

[GWilliam]

unsubscribe

Re: Symbolic Link and Next Tape Prediction ?

[Olivier Nicole]

>One simple way would be to do this a few hours before the "real"
>amdump run:
>
>  amadmin  tape | Mail -s "Amanda tapes needed" whoever

I choose to do that using amcheck instead

I see several advantages: it emails automatically, check the tape
status, check the clients...

I taught my guys to change the tape in the morning when the previous
back-up is over (new tape name is at top of amdump report).

Then I run amcheck via cron a 15:00, 15:45 and 16:00

There is a side advantage, sometime with FreeBSD, the tape device
hangs at the 1st action on that tape. So I am sure it hangs on the
amcheck and not on the amdump.

I should also consider avoiding back-up when the tape has not been
loaded (holidays).

Olivier

Specifig backup plan - HELP!

[Mariusz Brylant]

 After looking around for a good OpenSourse backup solution, I 
decided to make use of Amanda. Now I'am facing a problem configuring 
this software the way it fits my company backup policy. Thus I am asking 
you, those who are surely more familiar with this topic.
   Here are requirements I need to meet:


Tapes:
FM1, FM2, FM3 -monthly tapes for full backups with 3 months cycle, 
so that we have last three full monthly backups. Backups performed on 
1st Monday of the month.

FW2, FW3, FW4, FW5 - weekly tapes for full backups starting from 2nd 
week of the month and recycling after 2 or 3 weeks (depending on how 
many weeks we have in a  particular month) . Performed every Monday 
starting from 2nd week of the month.

IW1, IW2 - daily tapes for inremental backups rotating every week. 
Performed every day.

   To make everything a bit more understandable, let me give you an 
example. Lets assume we have a period of 4 months, one of which has 5 
weeks. Here is a tapes usage schema for those months (M stands for 
month, W for week and D - sure you now,:-)):


  M1 M2  
  M3M4 
  
   
-
   W1 -  W2 -  W3  - W4  ||  W1 -  W2  - W3  - W4  - W5  ||  W1 -  W2 -  
W3 -  W4  |  W1 -  W2 -  W3 - W4

   FM1  FW2FW3   FW4FM2  FW2   FW3FW4  FW5FM3FW2  
FW3FW4FM1  FW2   FW3  FW4
   IW1   IW2 IW1IW2 IW1   IW2IW1  IW2 . and 
so on.



   I hope someone would help me to map this scenario into Amanda's 
configuration schema(s). Please try to respond ASAP.

   Thanx and best regards,
   Mariusz Brylant.

..oo00##~*°°*~oo.
..oo00## Mariusz Brylant ~oo.
..oo00## Sys'n'Net Administrator ~ooo.
..oo00##   eCard S.A ~oo.
..oo00##~*OFFICE   **~ooo
..oo00##  address:Domaniewska 41 ~ooo..
..oo00##  MARD D ~.
..oo00##  02-672 Warsaw  ~o
..oo00##  Poland ~..
..oo00##  mailto: [EMAIL PROTECTED]  ~ooo.
..oo00##  www:www.ecard.com.pl   ~oo.
..oo00##  phone:  +48(22)8744490 ~o.
..oo00##  fax:+48(22)8744491 ~oo...
..oo00##~*PRIVATE  **~oo
..oo00##  mailto: [EMAIL PROTECTED] ~ooo
..oo00##  mailto: [EMAIL PROTECTED]   ~
..ooOO##~*°°*~..

Re: Problem getting overland changer running

[Peter Druck]

John,
first of all, amanda seems to be running. I can make amdump and amrestore
but I need further testing. Nevertheless here are the answers:

> >... In my installation it is
> > Data Transfer Element:  Full (Unknown Storage Element Loaded)
>
> What version of mtx are you using?  I looked at the sources for 1.2.13
> (and 1.2.11) and don't see how it can generate this line.  It always
> includes the device number, e.g.:
>
It looks like to be 1.1-240 (included with the suse 7.1 distribution).
The chg-zd-mtx runs when you change in readstatus()
...
sed -n 's/Data Transfer Element 0:Empty/-1/p;s/Data Transfer Element
0:Full (Storage Element \(.\) Loaded)/\1/p'`

into

sed -n 's/Data Transfer Element:.*Empty/-1/p;s/Data Transfer Element:.*Full (Storage 
Element \(.\) Loaded)/\1/p'`

Perhaps it's a different response of this Overlan changer. Anyway,
with this changes the error
[: -lt: unary operator expected
disapeared.


>   Data Transfer Element 128:  Full (Unknown Storage Element Loaded)
>
> Also, what do you have tapedev set to in amanda.conf?

/dev/nst0

>
> >BTW the chg-zd-mtx does only run mtx status (without the -f option).
>
> That's because it sets the TAPE environment variable from the changerdev
> value in amanda.conf.  Mtx will use that if -f is not on the command line.
>
> >Peter
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>

BTW, the day befor I had a question regarding the error

  changer: opening pipe to: /usr/lib/amanda/chg-zd-mtx -slot next
  taper: slot /usr/bin/mt:: no tape online

I got rid of this error by inserting a seep 100 in loadslot()
...

# If there is an error, abort unless the slot is simply empty

if [ $status -ne 0 ]; then
empty=`echo $result | grep "is Empty"`
if [ -z "$empty" ]; then
echo "$loadslot $result"
exit 2
else
loadslot next
fi
else
# ==> inserted sleep 100 so the tape has time do calibrate
# and get ready
/bin/sleep 100
# Don't assume the drive is ready until we stop getting tape off
# line


Peter

 +---+
 |e-Mail: [EMAIL PROTECTED] |
 +---+