amrecover

[Kaushal Shriyan]

Hi All

I get this below error when i run amrecover on the client machine

-- [EMAIL PROTECTED] kaushal]# amrecover 
AMRECOVER Version 2.4.4p1. Contacting server on localhost ...
220 oaks AMANDA index server (2.4.4p1) ready.
500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] 
amandahostsauth failed
[EMAIL PROTECTED] kaushal]# 

i have added my client hostname on the server .amandahosts 
but no help

can any one tell me why its happening

Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318
Cell : +91-9820367783



signature.asc
Description: This is a digitally signed message part

Re: AMANDA Documentation at www.oops.co.at (SGI Irix additions)

[Luc Lalonde]

Hello Stefan,
No not the email.   There are a few corrections in the text I resent 
you.   You changed the format of the text and I corrected the wording to 
ajust to your changes...

Thanks.
Stefan G. Weichinger wrote:
Hi, Luc,
on Donnerstag, 05. August 2004 at 15:59 you wrote to amanda-users:
LL> Hello Stefan,
LL> Here's a few corrections (in blue):
LL> Cut Here**
LL> Luc Lalonde <[EMAIL PROTECTED]
LL> > 

You mean the email-adress?? The format is pretty strict in my XML-DTD.
Or do I miss the point again?
best regards,
Stefan.
 

--
Luc Lalonde, analyste
-
Département de génie informatique:
École polytechnique de Montréal
(514) 340-4711 x5049
[EMAIL PROTECTED]
-
War is good for business, invest your son!
- 

Problem with Breaking Up Partition Bigger than Tape Size

[Don Clary]

I am trying to break up a 60 GB partition into chunks that will fit on 32 GB
(native) AIT-1 tapes.  I am using a Sony AIT i90-a tape drive on a Linux 9
system.  The big partition is on a remote client named "hsadm2".  The
following lines show the output running amcheck on the "hsadm2"
configuration.  The lines from the disklist file are included after the
error messages.

I built the breakup of the /home partition from the example disklist file.
I know that I am running an "older" version and that the latest stable
version is 2.4.4p3.

Can someone please point out the errors in breaking up the /home partition
into several tar files that can be spread across several amanda tapes?

Please excuse the long post.

Thanks,

Don Clary
Global Weather Dynamics, Inc.

=

-bash-2.05b$ /usr/sbin/amcheck hsadm2
Amanda Tape Server Host Check
-
Holding disk /var/tmp: 28675696 KB disk space available, that's plenty
WARNING: skipping tape test because amdump or amflush seem to be running
WARNING: if they are not, you must run amcleanup
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/hsadm2/_home_samba-share:
does not exist
NOTE: index dir /var/lib/amanda/DailySet1/index/hsadm2: does not exist
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/hsadm2/_home_old-code: does
not exist
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/hsadm2/_home_source: does
not exist
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/hsadm2/_home_ums: does not
exist
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/hsadm2/_home_nobig: does
not exist
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/hsadm2/_home_test: does not
exist
Server check took 0.157 seconds

Amanda Backup Client Hosts Check

WARNING: hsadm2:/home/samba-share does not support include file
ERROR: hsadm2:/home/samba-share (/home): selfcheck does not support device.
ERROR: hsadm2:/home/samba-share (/home): sendsize does not support device.
ERROR: hsadm2:/home/samba-share (/home): sendbackup does not support device.
WARNING: hsadm2:/home/old-code does not support include file
ERROR: hsadm2:/home/old-code (/home): selfcheck does not support device.
ERROR: hsadm2:/home/old-code (/home): sendsize does not support device.
ERROR: hsadm2:/home/old-code (/home): sendbackup does not support device.
WARNING: hsadm2:/home/source does not support include file
ERROR: hsadm2:/home/source (/home): selfcheck does not support device.
ERROR: hsadm2:/home/source (/home): sendsize does not support device.
ERROR: hsadm2:/home/source (/home): sendbackup does not support device.
WARNING: hsadm2:/home/ums does not support include file
ERROR: hsadm2:/home/ums (/home): selfcheck does not support device.
ERROR: hsadm2:/home/ums (/home): sendsize does not support device.
ERROR: hsadm2:/home/ums (/home): sendbackup does not support device.
WARNING: hsadm2:/home/nobig does not support multiple exclude
ERROR: hsadm2:/home/nobig (/home): selfcheck does not support device.
ERROR: hsadm2:/home/nobig (/home): sendsize does not support device.
ERROR: hsadm2:/home/nobig (/home): sendbackup does not support device.
ERROR: hsadm2:/home/test (/home): selfcheck does not support device.
ERROR: hsadm2:/home/test (/home): sendsize does not support device.
ERROR: hsadm2:/home/test (/home): sendbackup does not support device.
ERROR: hsadm2: [BOGUS REQUEST PACKET]
Client check: 1 host checked in 0.589 seconds, 1 problem found

(brought to you by Amanda 2.4.3)
-bash-2.05b$

===
Section of /etc/amanda/hsadm2/disklist.  I tried to start "small" with the
/home/test config, but that simple config does not work.


hsadm2 /home/test /home {
comp-root-tar
} 1

hsadm2 /home/nobig /home {
# all directories expcept the following
comp-root-tar
exclude "./umsv4"
exclude "./cvs*"
exclude "./linux.mry"
exclude "./shared"
} 1

(note: the "multiple exclude" error is not corrected by putting all excluded
dirs on one line separated by spaces.)

hsadm2 /home/ums /home {
comp-root-tar
include "./umsv4"
} 1

hsadm2 /home/source /home {
comp-root-tar
include "./cvs*"
} 1

hsadm2 /home/old-code /home {
comp-root-tar
include "./linux-mry"
} 1

hsadm2 /home/samba-share /home {
comp-root-tar
include "./shared"
} 1

Configuration Question

[Nick Niehoff]

I am backing up several machines to one large RAID array on one 
machine.  I have set my tapetype length to 4608 mbytes (4.5G) so I can 
eventually burn these tapes to DVD's (I have a 200 disk DVD-RW).  On a 
couple machines I have smaller RAID arrays which contain 150+Gb of 
data.  I am trying to configure the disklist so these few directories 
are low priority with high compression.  I would like the 
restore/recover process to be as simple as possible in case something 
ever happens.  I have found that for every entry in the disklist file 
when I use amrecover I have to setdisk to that disk.  Well I can break 
up these huge file systems into 4.5G chunks and put each chunk in the 
disklist file (as I must because one dump can not span multiple tapes 
correct?) but then when I use recover I have to start at the root and 
then setdisk to every subdirectory inside of that.  Is there a simple 
way of doing this so I can use amrecover/amrestore to recover from the 
root directory all other directories that are in different chunks?  I 
hope this makes since.

Thanks in advance,
Nick Niehoff

Re: `RESULTS MISSING' error

[Geert Uytterhoeven]

On Thu, 29 Jul 2004, Geert Uytterhoeven wrote:
> But amdump itself still fails:
>
> | *** THE DUMPS DID NOT FINISH PROPERLY!
> |
> | The next tape Amanda expects to use is: a new tape.
> | The next new tape already labelled is: DAILY01.
> |
> | FAILURE AND STRANGE DUMP SUMMARY:
> |   driver: FATAL reading result from taper: Connection reset by peer
> |   anakin sda5 RESULTS MISSING

I found the cause of the problem: apparently Debian's cdrw-taper package
contains a syntax error in the supplied config file, causing Amanda to fail.
Bug submitted and my complete bug report is available at

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263760

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

Re: AMANDA Documentation at www.oops.co.at (SGI Irix additions)

[Luc Lalonde]

I think that it should go into the SGI-Irix section...
Stefan G. Weichinger wrote:
Hi, Luc Lalonde,
on Donnerstag, 05. August 2004 at 04:09 you wrote to amanda-users:
LL> Hello Stefan,
LL> Thanks for the enormous work that you've done putting together this
LL> document.
Thank you ...
LL> I've to some Irix (6.5.x) notes:
LL> 1)  If you use a jukebox, you must set the ownership of the 
LL> robot-changer device to the Amanda operator:group in "/etc/ioperms".
LL> Here's my configure:

LL> /etc/ioperms: /dev/scsi/sc8d6l0 0600 amanda backup
LL> Otherwise the ownership:group is changed to root:sys after each reboot.
LL> 2)  When you do upgrades, check the file /var/sysgen/master.d/scsi to
LL> see if it has changed.   Otherwise your jukebox could be rendered 
LL> unuseable.   In particular, check if it has been replaced by a new
LL> version and renamed to 'scsi.O'.

LL> If you use the Amanda package provided by freeware.sgi.com, you are not
LL> affected by the first question since at compile time the Amanda operator
LL> is root:sys.
You have already thought about where one would prefer to find that
infos?
I assume this should go into the current chapter 9 "AMANDA Tape
Changer Support" ...
 

--
Luc Lalonde, analyste
-
Département de génie informatique:
École polytechnique de Montréal
(514) 340-4711 x5049
[EMAIL PROTECTED]
-
War is good for business, invest your son!
- 

Re: Problems compiling 2.4.4p3 on Solaris 2.51

[Jean-Louis Martineau]

Hi stan,

Change the call to snprintf in amqde.c to ap_snprintf.

Jean-Louis

On Wed, Aug 04, 2004 at 06:16:58PM -0400, stan wrote:
> I'm trying to comiple 2.4.4p3 on an ancient Solaris 2.5.1 machine.
> 
> I gte errors in the linking phase with snprintf not being found. 
> What's puzzling is that config.log clearly shows that this function 
> was not found:
> 
> conftest.c:294: warning: conflicting types for built-in function 'snprintf'
> Undefined   first referenced
>  symbol in file
>  snprintf/var/tmp//ccjH8So6.o
>  ld: fatal: Symbol referencing errors. No output written to conftest
>  collect2: ld returned 1 exit status
> 
> And it seems that the Amanda source tree provides this function
> for just such a case:
> 
> ./common-src/snprintf.c
> 
> Yet, I'm getting the following error:
> 
>  -g -O2 -o .libs/amqde amqde.o  -L/usr/local/lib -L/usr/include 
> ./.libs/libamclient.so
>  ../common-src/.libs/libamanda.so -lgen -lm -ltermcap -lsocket -lnsl -lintl 
> -R/opt/amanda/lib
>  -R/usr/local/lib
>  -R/usr/include
>  Undefined   first referenced
>   symbol in file
>   snprintfamqde.o
>   ld: fatal: Symbol referencing errors. No output written to .libs/amqde
> 
> 
> Any sugestions as to what I might be doign wrong?
> 
> 
> 
> -- 
> "They that would give up essential liberty for temporary safety deserve
> neither liberty nor safety."
>   -- Benjamin Franklin

-- 
Jean-Louis Martineau email: [EMAIL PROTECTED] 
Département IRO, Université de Montréal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montréal, Canada, H3C 3J7Fax: (514) 343-5834

adding amanda linux client to solaris amanda server

[Ranveer Attalia]

Title: Message



Hi 

 
I'm installing the 
amanda v2.4.4p2 client onto a linux (hostname: tsslin1) machine and trying to 
connect to the Amanda server on the Solaris machine (hostname: tsssun1) Setup 
*looks* fine, but am getting the following error when I try to test it using 
amrecover:
 
[EMAIL PROTECTED] sbin]# 
./amrecover -C Daily -t tsssun1 -s tsssun1
AMRECOVER Version 
2.4.4p2. Contacting server on tsssun1...
220 tsssun1 AMANDA 
index server (2.4.4p1) ready.
500 Access not 
allowed: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth 
failed
 
I have also added 
the entry into the .rhosts file on the amanda server (tsssun1) but still makes 
no difference
 
.rhosts
tsslin1 
root
tsslin1.tertio.com 
root
 
Can anyone help 
please?
 
Thanks 

 
- Ranveer 




Tertio Telecoms (www.telco-tertio.com)

Head Office: One Angel Square  Torrens Street  London  EC1V 1PL
Tel: +44 (0)20 7843 4000 - Fax: +44 (0)20 7843 4001

Bath Office: Riverside Buildings  108 Walcot Street  Bath  BA1 5BG
Tel: +44 (0)1225 478000 - Fax: +44 (0)1225 478001 

Munich Office: Freisinger Strasse 10, 85737 Ismaning/Munich, Germany,
Tel: +49 (0)89 665506 41 - Fax: +49 (0)89 665506 99

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of Tertio Ltd.

This email has been scanned by the MessageLabs Email Security System.