Hard Disk Backup

2002-09-30 Thread james 

How do I configure Amanda to backup to a partition on the same hard drive?
 Or where can i find out how to do that?

Thanks
-james

Re: EXB-8700, 160m XL tapes, and tapetype

2002-09-30 Thread Galen Johnson 

Bob Tanner wrote:

>Quoting Galen Johnson ([EMAIL PROTECTED]):
>  
>
>>The filemark is just a way for tape systems to waste tape...be glad that 
>>it's zero...the real question is what is the advertised capacity of 
>>these tapes?  
>>
>>
>
>7G uncompressed. The tape drive I have is listed below:
>
>http://www.cpuinc.com/8700.html
>
>  
>
>>Did you turn off hardware compression?  What is the error 
>>given in the logs?
>>
>>
>
>$ mt -f /dev/nst0 status
>SCSI 2 tape drive:
>File number=0, block number=0, partition=0.
>Tape block size 1024 bytes. Density code 0x0 (default).
>Soft error count since last status=0
>General status bits on (4101):
> BOT ONLINE IM_REP_EN
>
>$ mt -f /dev/nst0 densities
>Some SCSI tape density codes:
>code   explanation   
>0x00   default  
>
>
>I could not find what the "default" setting of the tape drive is. Nor could I
>find a way or option in the densities to force uncompressed (if the default is
>compressed).
>  
>
Typically, running either "mt -f /dev/nst0 compression 0' or "mt -f 
/dev/nst0 datcompression 0".  I'm assuming you're running a flavor of 
linux.   Some drives also have a way to turn the hardware compression 
off on the device itself.  Once you are fairly certain you have 
compression off, rerun tapetype with something along the lines of 
'tapetype -f /dev/nst0 -e 7g'.  You obviously didn't get anywhere near 
the capacity expected.  You may also want to check out the manuals for 
the drive and see if you have to set the blocksize to control 
compression and read the mt man page (under slackware 'man mt-st' to get 
the real man page).

>Several errors:
>
>Sep 30 20:38:27 linux kernel: st0: Error with sense data: Info fld=0x3c0, Defer
>red st09:00: sense key Medium Error
>
>Sep 28 15:27:22 linux xinetd[12977]: START: amanda pid=13189 from=127.0.0.1
>
>Sep 28 15:27:22 linux xinetd[13189]: {general_handler} (13189) Unexpected
>signal: 11 (Segmentation fault)
>
>
>  
>
The logs I was referring to were the amanda debug logs...They are a bit 
more thorough where amanda is concerned.

=G=

Re: EXB-8700, 160m XL tapes, and tapetype

2002-09-30 Thread Bob Tanner 

Quoting Galen Johnson ([EMAIL PROTECTED]):
> The filemark is just a way for tape systems to waste tape...be glad that 
> it's zero...the real question is what is the advertised capacity of 
> these tapes?  

7G uncompressed. The tape drive I have is listed below:

http://www.cpuinc.com/8700.html

> Did you turn off hardware compression?  What is the error 
> given in the logs?

$ mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 1024 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (4101):
 BOT ONLINE IM_REP_EN

$ mt -f /dev/nst0 densities
Some SCSI tape density codes:
code   explanation   
0x00   default  


I could not find what the "default" setting of the tape drive is. Nor could I
find a way or option in the densities to force uncompressed (if the default is
compressed).

Several errors:

Sep 30 20:38:27 linux kernel: st0: Error with sense data: Info fld=0x3c0, Defer
red st09:00: sense key Medium Error

Sep 28 15:27:22 linux xinetd[12977]: START: amanda pid=13189 from=127.0.0.1

Sep 28 15:27:22 linux xinetd[13189]: {general_handler} (13189) Unexpected
signal: 11 (Segmentation fault)


-- 
Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700
http://www.mn-linux.org, Minnesota, Linux | Fax   : (952)943-8500
http://www.tcwug.org, Minnesota, Wireless | Coding isn't a crime. 
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288

Re: EXB-8700, 160m XL tapes, and tapetype

2002-09-30 Thread Galen Johnson 

Bob Tanner wrote:

>amanda-2.4.3b4
>EXB-8700 Tape Drive
>Exabyte 160M XL tapes
>
>Got amanda configured. But amdump keeps erroring out. I used the EXB-8500 as my
>template for the EXB-8700. But since amdump wasn't working, I ran tapetype.
>
>Here is how I ran it:
>
># /usr/sbin/tapetype  -f /dev/nst0
>
>This is what I get back:
>
>wrote 21909 32Kb blocks in 67 files in 1713 seconds (short write)
>wrote 22168 32Kb blocks in 136 files in 1990 seconds (short write)
>define tapetype unknown-tapetype {
>comment "just produced by tapetype program"
>length 705232 kbytes
>filemark 0 kbytes
>speed 382 kps
>}
>
>Can the filemark really be 0? I'm not 100% sure what that does or if it's
>related to my problem of amanda not working.
>
>
>
>  
>
The filemark is just a way for tape systems to waste tape...be glad that 
it's zero...the real question is what is the advertised capacity of 
these tapes?  Did you turn off hardware compression?  What is the error 
given in the logs?

=G=

EXB-8700, 160m XL tapes, and tapetype

2002-09-30 Thread Bob Tanner 

amanda-2.4.3b4
EXB-8700 Tape Drive
Exabyte 160M XL tapes

Got amanda configured. But amdump keeps erroring out. I used the EXB-8500 as my
template for the EXB-8700. But since amdump wasn't working, I ran tapetype.

Here is how I ran it:

# /usr/sbin/tapetype  -f /dev/nst0

This is what I get back:

wrote 21909 32Kb blocks in 67 files in 1713 seconds (short write)
wrote 22168 32Kb blocks in 136 files in 1990 seconds (short write)
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 705232 kbytes
filemark 0 kbytes
speed 382 kps
}

Can the filemark really be 0? I'm not 100% sure what that does or if it's
related to my problem of amanda not working.



-- 
Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700
http://www.mn-linux.org, Minnesota, Linux | Fax   : (952)943-8500
http://www.tcwug.org, Minnesota, Wireless | Coding isn't a crime. 
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288

Problem running ./configure on 2.4.3b4 on AIX

2002-09-30 Thread Anthony Valentine 

Hello all.

I am getting the following warnings/errors when doing a ./configure on
amanda 2.4.3b4 under AIX 4.3.3:


configure: WARNING: *** No terminal library, no history and command line
editing in amrecover!


configure: WARNING: *** Neither shmget() nor mmap() found!
configure: WARNING: *** This system will not support the Amanda server.


configure: WARNING: *** No working file locking capability found!
configure: WARNING: *** Be VERY VERY careful.


I don't get any of these when running configure on 2.4.2p2

Anyone have any ideas?

Anthony Valentine


-- 
UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things.

SUMMARY: Error compiling AMANDA sources on AIX 4.3 (`MNTTAB' undeclared)

2002-09-30 Thread Dombrowski, Todd 

I forgot to search Google groups! Here's the answer that I found there, and
which worked for me as well:

"From: Bernhard R. Erdmann ([EMAIL PROTECTED])
Subject: Re: Error compiling on AIX 4.3.3.0.09 
Newsgroups: list.amanda.users
View this article only 
Date: 2001-10-02 16:30:14 PST 
 

> I am trying to compile Amanda (2.4.2.p2) on an AIX 4.3.3 box to be used as
a
> client only (I used the --without-server configure option).  It dies
during
> the compile with this message: [...]
> 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.
[...]

A temporary solution is to kick away or to rename mntent.h to
mntent.h.ibmsucks. Don't forget to "make distclean" or "rm config.cache"
before another shot of "./configure --with-user=... ---with-group=...
--with-blabla=..."
Nobody has come up with a general solution for AIX 4.3.3, yet. Though is
has bitten many Amanda users/admins on AIX 4.3.3. :-("



-Original Message-
From: Dombrowski, Todd [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 12:17 PM
To: '[EMAIL PROTECTED]'
Subject: Error compiling AMANDA sources on AIX 4.3 (`MNTTAB' undeclared)

I recently ran across an issue on a new AIX 4.3 server we installed a few
weeks back. I just tried to compile amanda and I received the following
error (running `make`):

make[1]: Entering directory `/tmp/amanda-install/amanda-2.4.2p2/client-src'
/usr/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I../config -I../common-src-g -O2   -c amandates.c
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -g -O2 -c
amandates.c -o amandates.o
echo timestamp > amandates.lo
/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[1]: *** [getfsent.lo] Error 1
make[1]: Leaving directory `/tmp/amanda-install/amanda-2.4.2p2/client-src'
make: *** [all-recursive] Error 1

Re: Error compiling AMANDA sources on AIX 4.3 (`MNTTAB' undeclared)

2002-09-30 Thread Doug Meredith 

Todd,

> From: "Dombrowski, Todd" <[EMAIL PROTECTED]>
[...]
> I recently ran across an issue on a new AIX 4.3 server we installed a few
[...]
> getfsent.c: In function `open_fstab':
> getfsent.c:154: `MNTTAB' undeclared (first use in this function)

I don't have a solution for you, but I do have a little bit of info.

I have encountered the same problem trying to build the Amanda client under
CygWin.  It occurs with 2.4.2p2 and 2.4.3b4.  MNTTAB is a symbolic constant
that on RedHat 7.3 equates to "/etc/fstab".  On RedHat this is defined in
/usr/include/mntent.h.  I hacked getfsent.c and inserted the macro directly
and was then able to compile without errors.  I haven't tried running it
yet.  Good luck.

Doug

--
Doug Meredith
Skyridge Systems Inc.
(506) 854-7997
www.skyridge.com

Error compiling AMANDA sources on AIX 4.3 (`MNTTAB' undeclared)

2002-09-30 Thread Dombrowski, Todd 

Greetings to fellow amanda users. I'd like to start off by saying amanda is
an incredible product which has saved our company much money and frustration
over the past 2 years. I've been in charge of the initial installation,
configuration and current maintenance of amanda, and I must say, the product
has exceeded all expectations.

I recently ran across an issue on a new AIX 4.3 server we installed a few
weeks back. I just tried to compile amanda and I received the following
error (running `make`):

make[1]: Entering directory `/tmp/amanda-install/amanda-2.4.2p2/client-src'
/usr/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I../config -I../common-src-g -O2   -c amandates.c
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -g -O2 -c
amandates.c -o amandates.o
echo timestamp > amandates.lo
/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[1]: *** [getfsent.lo] Error 1
make[1]: Leaving directory `/tmp/amanda-install/amanda-2.4.2p2/client-src'
make: *** [all-recursive] Error 1


I've tried the FAQ-O-Matic and Google, but have not found anything regarding
this error. Unfortunately, my company has blocked egroup.com so I cannot
search through the mailing list archives.

Prior to compilation I installed the following 'pre-compiled for AIX'
packages:
gnu.flex-2.5.4.0.exe
gnu.gdb-5.0.0.0.exe
termpkg-3.0.0.0.exe
gnu.gcc-2.95.3.0.exe
gnu.make-3.79.1.0.exe
gnu.gcc.g++-2.95.3.0.exe
gnu.readline-4.1.0.1.exe

Put /usr/local/bin at the head of my path.

And for the brave: Here's the configure command and output.

./configure --with-user=amanda --with-group=backup --without-server \
--with-tape-server=amandaserver --with-index-server=amandaserver

creating cache ./config.cache
checking host system type... rs6000-ibm-aix4.3.3.0
checking target system type... rs6000-ibm-aix4.3.3.0
checking build system type... rs6000-ibm-aix4.3.3.0
checking cached system tuple... ok
checking for a BSD compatible install... config/install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for non-rewinding tape device... /dev/null
checking for raw ftape device... /dev/null
checking for Kerberos and Amanda kerberos4 bits... no
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for object suffix... o
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for executable suffix... no
checking for ar... /usr/bin/ar
checking for mawk... no
checking for gawk... no
checking for nawk... nawk
checking for nawk command line variable assignment... yes with -v
checking for bison... bison -y
checking for cat... /usr/bin/cat
checking for compress... /usr/bin/compress
checking for dd... /usr/bin/dd
checking for egrep... /usr/bin/egrep
checking for getconf... /bin/getconf
checking for gnuplot... no
configure: warning: *** You do not have gnuplot.  Amplot will not be
installed.
checking for grep... /usr/bin/grep
checking for gtar... no
checking for gnutar... no
checking for tar... /usr/bin/tar
configure: warning: *** /usr/bin/tar is not GNU tar, so it will not be used.
checking for smbclient... no
checking for gzip... /usr/local/bin/gzip
checking for Mail... /usr/bin/Mail
checking for mt... /usr/bin/mt
checking for chio... no
checking for chs... no
checking for mtx... no
checking for lpr... /usr/bin/lpr
checking which flag to use to select a printer... -P
checking for pcat... /usr/bin/pcat
checking for perl5... no
checking for perl... /usr/local/bin/perl
checking for sh... /usr/bin/sh
checking for backup... /usr/sbin/backup
checking for ufsrestore... no
checking for restore... /usr/sbin/restore
checking whether /usr/sbin/backup supports -E or -S for estimates... no
checking for xfsdump... no
checking for xfsrestore... no
checking for vxdump... no
checking for vxrestore... no
checking for vdump... no
checking for vrestore... no
checking for large file compilation CFLAGS...
checking for large file compilation LDFLAGS...
checking for large file compilation LIBS...
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
updating cache ./conf

Re: Amanda on ia64

2002-09-30 Thread Bram Metsch 

On Mon, 30 Sep 2002 10:56:26 -0400
Jean-Louis Martineau <[EMAIL PROTECTED]> wrote:

> Hi Bram,
> 
> Which release of amanda are you trying to compile?
> Could you try the latest 2.4.3b4 snapshot from
> http://www.iro.umontreal.ca/~martinea/amanda ?
> 
> Jean-Louis
> 

Hi Jean-Louis,

Thank you very much. 2.4.3b4 seems to work.
(I was trying 2.4.2p2 first)

Bram.

Faq-o-matic Update

2002-09-30 Thread Jason Greenberg 

To whomever maintains the amanda faq-o-matic:

RE: Issue:
http://amanda.sourceforge.net/fom-serve/cache/310.html, 

Behavior:
This issue can also persist even after an upgrade to gnutar > 1.13.19. 
Even after re-configuring , compiling and installing amanda with the new
gnutar specified --with-gnutar=/usr/local/bin/tar (1.13.25), amanda
continued to use /bin/tar.  

The issue was resolved by physically replacing /bin/tar with gnutar >
1.13.19.  



-- 
Jason Greenberg, CCNP
Network Administrator
Execulink, Inc.
[EMAIL PROTECTED]

Re: Amanda on ia64

2002-09-30 Thread Jean-Louis Martineau 

Hi Bram,

Which release of amanda are you trying to compile?
Could you try the latest 2.4.3b4 snapshot from
http://www.iro.umontreal.ca/~martinea/amanda ?

Jean-Louis

On Mon, Sep 30, 2002 at 04:28:43PM +0200, Bram Metsch wrote:
> Hello,
> 
> has anybody got an idea how to buid amanda on an ia64 (Intel Itanium)?
> 
> ./configure tells me:
>  
> creating cache ./config.cache
> checking host system type... Invalid configuration `ia64-unknown-linux-gnu': machine 
>`ia64-unknown' not recognized
> 
> checking target system type... Invalid configuration `ia64-unknown-linux-gnu': 
>machine `ia64-unknown' not recognized
> 
> checking build system type... Invalid configuration `ia64-unknown-linux-gnu': 
>machine `ia64-unknown' not recognized
> 
> checking cached system tuple... ok
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... found
> checking for working autoconf... found
> checking for working automake... found
> checking for working autoheader... found
> checking for working makeinfo... missing
> checking for non-rewinding tape device... /dev/null
> checking for raw ftape device... /dev/null
> checking for Kerberos and Amanda kerberos4 bits... no
> checking for gcc... gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for object suffix... o
> checking for Cygwin environment... no
> checking for mingw32 environment... no
> checking for executable suffix... no
> 
> *
> This machine, target type , is not known
> to be fully supported by this configure script.  If the
> installation of Amanda on this system succeeds or needed
> any patches, please email [EMAIL PROTECTED] with
> the patches or an indication of the sucess or failure of
> the Amanda installation on your system.
> *
> 
> checking for ar... /usr/bin/ar
> checking for mawk... no
> checking for gawk... gawk
> checking for gawk command line variable assignment... yes with -v
> checking for bison... bison -y
> checking for cat... /bin/cat
> checking for compress... /usr/bin/compress
> checking for dd... /bin/dd
> checking for egrep... /bin/egrep
> checking for getconf... /usr/bin/getconf
> checking for gnuplot... /usr/bin/gnuplot
> checking for grep... /bin/grep
> checking for gtar... /bin/gtar
> checking for smbclient... no
> checking for gzip... /bin/gzip
> checking for Mail... /usr/bin/Mail
> checking for mt... no
> checking for chio... no
> checking for chs... no
> checking for mtx... no
> checking for lpr... /usr/bin/lpr
> checking which flag to use to select a printer... -P
> checking for pcat... no
> checking for perl5... no
> checking for perl... /usr/bin/perl
> checking for sh... /bin/sh
> checking for ufsdump... no
> checking for dump... /sbin/dump
> checking for ufsrestore... no
> checking for restore... /sbin/restore
> checking whether /sbin/dump supports -E or -S for estimates... S
> checking for xfsdump... no
> checking for xfsrestore... no
> checking for vxdump... no
> checking for vxrestore... no
> checking for vdump... no
> checking for vrestore... no
> checking for large file compilation CFLAGS... 
> checking for large file compilation LDFLAGS... 
> checking for large file compilation LIBS... 
> checking for ranlib... ranlib
> checking for ld used by GCC... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> updating cache ./config.cache
> loading cache ./config.cache within ltconfig
> ltconfig: you must specify a host type if you use `--no-verify'
> Try `ltconfig --help' for more information.
> configure: error: libtool configure failed
> 
> and when I try '--disable-libtool', it does not work either.
> 
> TIA,
> Bram.

-- 
Jean-Louis Martineau email: [EMAIL PROTECTED] 
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834

Amanda on ia64

2002-09-30 Thread Bram Metsch 

Hello,

has anybody got an idea how to buid amanda on an ia64 (Intel Itanium)?

./configure tells me:
 
creating cache ./config.cache
checking host system type... Invalid configuration `ia64-unknown-linux-gnu': machine 
`ia64-unknown' not recognized

checking target system type... Invalid configuration `ia64-unknown-linux-gnu': machine 
`ia64-unknown' not recognized

checking build system type... Invalid configuration `ia64-unknown-linux-gnu': machine 
`ia64-unknown' not recognized

checking cached system tuple... ok
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking for non-rewinding tape device... /dev/null
checking for raw ftape device... /dev/null
checking for Kerberos and Amanda kerberos4 bits... no
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for object suffix... o
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for executable suffix... no

*
This machine, target type , is not known
to be fully supported by this configure script.  If the
installation of Amanda on this system succeeds or needed
any patches, please email [EMAIL PROTECTED] with
the patches or an indication of the sucess or failure of
the Amanda installation on your system.
*

checking for ar... /usr/bin/ar
checking for mawk... no
checking for gawk... gawk
checking for gawk command line variable assignment... yes with -v
checking for bison... bison -y
checking for cat... /bin/cat
checking for compress... /usr/bin/compress
checking for dd... /bin/dd
checking for egrep... /bin/egrep
checking for getconf... /usr/bin/getconf
checking for gnuplot... /usr/bin/gnuplot
checking for grep... /bin/grep
checking for gtar... /bin/gtar
checking for smbclient... no
checking for gzip... /bin/gzip
checking for Mail... /usr/bin/Mail
checking for mt... no
checking for chio... no
checking for chs... no
checking for mtx... no
checking for lpr... /usr/bin/lpr
checking which flag to use to select a printer... -P
checking for pcat... no
checking for perl5... no
checking for perl... /usr/bin/perl
checking for sh... /bin/sh
checking for ufsdump... no
checking for dump... /sbin/dump
checking for ufsrestore... no
checking for restore... /sbin/restore
checking whether /sbin/dump supports -E or -S for estimates... S
checking for xfsdump... no
checking for xfsrestore... no
checking for vxdump... no
checking for vxrestore... no
checking for vdump... no
checking for vrestore... no
checking for large file compilation CFLAGS... 
checking for large file compilation LDFLAGS... 
checking for large file compilation LIBS... 
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
loading cache ./config.cache within ltconfig
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed

and when I try '--disable-libtool', it does not work either.

TIA,
Bram.

Re: Newbie with amrecover...

2002-09-30 Thread BRINER Cedric 

> Hello
> I use Amanda and a tape drive on my database server, and yesterday i deal
> with disk problems on it.
> So i wanted to verify my tapes on another server and i encoutered some
> difficulties.

I think that you have to specify to amrecover where is the amandaIndex
with the flag -i and also where is the tapeserver with the flag -t.

so you should write something like 
amrecover  -t  -i 

Amanda Index is defined in the configuration file !!!

good luck

briner
 
> My questions are :
> Can i read my tapes from another server using the drive of my database
> server (Amrecover tried to connect to my db server) ?
> Do I need my conf file (Daily) to restore anything (ie Do i need to save it
> on another hard disk) ?
> 
> I read documentation on http://www.backupcentral.com/amanda-23.html but it
> isn't very clear for me
> Many thanks for advices
> 
> Olivier
>