Re: amdump problem: "missing result" reported

2001-10-10 Thread Urte Fuerst


Great, I got through to the mailing list! :-)
I had big problems reaching the list, so I talked to John directly about
the problem.

> > What has changed now with the patch is the /tmp/amanda/sendsize.debug
> > output. I'm sure I found the / and home  stuff in sendsize.debug before
> > (even when they were not backed up), but now they are no longer present.
> That's really strange: why should Amanda estimate / and /home if they
> aren't backed up?
Dont know if you know about the problem. I once again include my
original email here to get you up to date:

-- original email --
Hello list,

I have a problem with amanda 2.4.2p2.

I'm doing backups on three SUN machines with amanda for quite some time
wihout any major problems.

About 2 weeks ago  we removed the bunch of single external disks from
that host and added one big raid disk (which is of course too big to be
backed up entirely on our 20gb native capacity tape). I then changed the
disklist for this host from about 7 filesystems (= physical disk
partitions) to 38 directory starting points.

The first few days of course we had missing filesystems on tape until
amanda has been able to do a level 0 dump on each of the new entries.
Nevertheless 6 of the entries remain non-backuped (including the root
filesystem and the user filesystem :-( ). I assume it might be a problem
with the number of entries in the disklist (I saw some discussions about
this in this newsgroup, but that turned out to be an error in the
exclude statement). I noticed that these 6 entries are the ones which
stand on top of the list.

The error in the mail report says:

FAILURE AND STRANGE DUMP SUMMARY:
  adler  /usr/export/amis/raid2/disk_head_97_05 lev 0 FAILED
[missing result for /usr/export/amis/raid2/disk_head_97_05 in adler
response]
  adler  /usr/export/amis/raid2/disk_head_96_05 lev 0 FAILED
[missing result for /usr/export/amis/raid2/disk_head_96_05 in adler
response]
  adler  /usr/export/amis/raid2/disk_head_95_08 lev 0 FAILED
[missing result for /usr/export/amis/raid2/disk_head_95_08 in adler
response]
  adler  /usr/export/amis/disk2 lev 0 FAILED [missing result for
/usr/export/amis/disk2 in adler response]
  adler  /usr/export/home/adler lev 0 FAILED [missing result for
/usr/export/home/adler in adler response]
  adler  / lev 0 FAILED [missing result for / in adler response]

I dont see something unusual in the /tmp/amanda/-files. Just ask if you
would like to see some extracts from there.

-- end of original email --

John then sent me some patch, but he was not sure wheather this would
help. And it did not. Thats the current state of the art. 

Kind regards,
Urte

-- 
   \|/
   @ @
---oOO-(_)-OOo-

Urte Fuerst
_/_/  _/ _/_/_/ German Aerospace Center DLR
   _/  _/_/ _/_/   
  _/   _/   _/ _/_/ Institute of Aeroelasticity
 _/_/  _/ _/ _/_/  Bunsenstrasse 10
_/_/  _/ _/_/D - 37073 Goettingen
   _/_/  _/ _/  _/Phone:  +49 (0)551 709 2432
  _/   _/   _/ _/_/   Fax:+49 (0)551 709 2862
 _/_/_/_/_/_/_/_/ _/  _/  e-mail: [EMAIL PROTECTED]



Re: amdump problem: "missing result" reported

2001-10-10 Thread Bernhard R. Erdmann

> What has changed now with the patch is the /tmp/amanda/sendsize.debug
> output. I'm sure I found the / and home  stuff in sendsize.debug before
> (even when they were not backed up), but now they are no longer present.

That's really strange: why should Amanda estimate / and /home if they
aren't backed up?



Re: How do i extract from a specific tape?

2001-10-10 Thread Bernhard R. Erdmann

> 1) i ran amrecover (as root) from the host where i lost my data
> 2) amanda ran through 1 of 3 tapes without error (the tape that had the
> level 0 from 10/08)

what a bad hit rate...

> 3) when amanda switched to the first of 2 tapes with level 1's on it, i got
> an error:
> EOF, check amidxtaped.debug file on amanda
> amrecover: short block 0 bytes
> UNKNOWN file
> amrecover: Can't read file header
> extract_list - child returned non-zero status: 1
> Continue? [Y/n] :

"short block" is mostly an indicator for the wrong blocksize but not in
your case. You got level 0 back.

> when i hit "y" , i was returned to my amrecover> prompt.  Does this mean the
> level 1 data on that tape is corrupt?  if so, can i move on to the 3rd tape
> and at least recover that data?

Did you run "amverify" on these two tapes?

Do you perform a full restore (i.e. mkfs, restore, restore, restore)? Or
just some files spread out over your tapes?
In the first case you don't need the first level 1 but only the last
level 1.



Re: How can I verify that Indexing is working?

2001-10-10 Thread Bernhard R. Erdmann

> - Did you set "index yes" in amanda.conf?
> 
> Yes.  I set it in the global section:

Please browse through the index directories (~amanda//index).
There should be directories for each host backed up and thereunder
directories for each filesystem (/ replaced by _) and therein gzipped
files containing the filenames in the backup. What's inside these files?



Re: Amrecover - Amandaidx Looping?

2001-10-10 Thread Bernhard R. Erdmann

> [root@garfield amanda]# cat amrecover.20011010121258.debug
> amrecover: debug 1 pid 2022 ruid 0 euid 0 start time Wed Oct 10
> 12:12:58 2001
> amrecover: stream_client: connect(10082) failed: Connection
> refused
> cannot connect to garfield: Connection refused
> amrecover: pid 2022 finish time Wed Oct 10 12:12:58 2001
> 
> And this is what I see in "/var/log/messages":
> Oct 10 12:01:20 garfield xinetd[1927]: warning: can't get client
> address: Transport endpoint is not connected
[...]
> Oct 10 12:01:21 garfield xinetd[1936]: warning: can't get client
> address: Transport endpoint is not connected
> Oct 10 12:01:21 garfield xinetd[1923]: amandaidx service was
> deactivated because of looping
[...]
> [root@garfield amanda]# cat /etc/xinetd.d/amandaidx
> # default: off
> #
> # description: Part of the Amanda server package
> service amandaidx
> {
>socket_type = stream
>protocol= tcp
>wait= yes
>user= amanda
>group   = disk
>server  = /usr/lib/amanda/amindexd
> }
[...]

Please check again with "wait = no" (don't forget to SIGUSR1 xinetd or
to restart it - SIGHUP won't help).

$ grep ^am /etc/inetd.conf
amanda  dgram   udp waitamanda  /usr/libexec/amanda/amandad 
amandad
amandaidx   stream  tcp nowait  amanda 
/usr/libexec/amanda/amindexd   amindexd
amidxtape   stream  tcp nowait  amanda 
/usr/libexec/amanda/amidxtaped amidxtaped



Re: amdump problem: "missing result" reported

2001-10-10 Thread Urte Fuerst


Hi John,

> I'm not sure if this will fix your problem, but it is the patch that
> allows requests larger than a single packet.
Unfortunately this patch did not fix it. I added the patch to the source
code, recompiled and reinstalled amanda. Then I added 2 of the 6
filesystems in the disklist again which I had commented out two weeks
ago.

Now I get the same error again in the amanda report:

FAILURE AND STRANGE DUMP SUMMARY:
  adler  /usr/export/home/adler lev 0 FAILED [missing result for
/usr/export/home/adler in adler response]
  adler  / lev 0 FAILED [missing result for / in adler response]

These two are again the first two filesystems in the disklist for host
adler which are missing on tape.

For me it really looks like a max-32-fileystems-per-host limit.

What has changed now with the patch is the /tmp/amanda/sendsize.debug
output. I'm sure I found the / and home  stuff in sendsize.debug before
(even when they were not backed up), but now they are no longer present. 

??
Kind regards, Urte

P.S. I'll try to CC: the amanda list. Maybe I can get through somehow?

-- 
   \|/
   @ @
---oOO-(_)-OOo-

Urte Fuerst
_/_/  _/ _/_/_/ German Aerospace Center DLR
   _/  _/_/ _/_/   
  _/   _/   _/ _/_/ Institute of Aeroelasticity
 _/_/  _/ _/ _/_/  Bunsenstrasse 10
_/_/  _/ _/_/D - 37073 Goettingen
   _/_/  _/ _/  _/Phone:  +49 (0)551 709 2432
  _/   _/   _/ _/_/   Fax:+49 (0)551 709 2862
 _/_/_/_/_/_/_/_/ _/  _/  e-mail: [EMAIL PROTECTED]



Re: How do I specify no chuncksize?

2001-10-10 Thread Mitch Collinsworth



On Tue, 9 Oct 2001, Stan Brown wrote:

> I tried hat I put in "chunksize -2GB" and got a message about negative
> chunksize not being suported any more.


Sheesh.  Sorry!  My mistake.  I was looking at an old version.
A more current example/amanda.conf has this comment:

holdingdisk hd1 {
comment "main holding disk"
directory "/dumps/amanda"   # where the holding disk is
use 290 Mb  # how much space can we use on it
# a non-positive value means:
#use all space but that value
chunksize 1Gb   # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
#  N Kb/Mb/Gb split images in chunks of size N
# The maximum value should be
# (MAX_FILE_SIZE - 1Mb)
#  0  same as INT_MAX bytes
}



So just use chunksize 0 for no chunking.

-Mitch




RE: Amrecover - Amandaidx Looping?

2001-10-10 Thread Mark Holm

In my case they are bound until you attempt to run amrecover. As soon as it
attempts to access the index server then you get the following in the
messages log:

Oct 10 15:23:11 blight xinetd[1255]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1256]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1257]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1258]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1259]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1260]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1261]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1248]: amandaidx service was deactivated
because of looping

>From that point on, it doesn't show up in netstat anymore because xinetd
deactivated it.

markh

-Original Message-
From: Bernhard R. Erdmann [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 4:03 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Amrecover - Amandaidx Looping?


> I have read extensively and have failed to find a solution to my
> problem.  I am hoping someone will know what I have done wrong.  I
> can't
> seem to get "amrecover" to work for me.

Check using netstat if the following port are bound:

$ netstat -an|grep :1008. 
tcp0  0 0.0.0.0:10082   0.0.0.0:*  
LISTEN
tcp0  0 0.0.0.0:10083   0.0.0.0:*  
LISTEN
udp0  0 0.0.0.0:10080   0.0.0.0:*

$ grep ^am /etc/services 
amanda  10080/udp   # amanda backup services
amandaidx   10082/tcp   # amanda backup services
amidxtape   10083/tcp   # amanda backup services



Re: selfcheck timeout - host down

2001-10-10 Thread Dietmar Goldbeck

On Wed, Oct 10, 2001 at 09:13:17AM -0500, Lee Fedor wrote:
> 
> service amanda
> {
> disable = no
> socket_type = dgram
> protocol= udp
> wait= yes
> user= dump
> group   = dump
> server  = /usr/lib/amanda/amandad
> port= 10080
> }
^

It's better to add amanda to /etc/services instead of using the port
number. Then kill xinetd and start it with debugging on 

xinetd -d 

and run amcheck, watching xinetd debug messages. This
should either work or give at least a detailed message.

-- 
 Alles Gute / best wishes  
 Dietmar GoldbeckE-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?  Gandhi: I think it would be a good idea.



How do i extract from a specific tape?

2001-10-10 Thread Rivera, Edwin

hello,

a superblock on the hard drive of my nfs exported /home filesystem went bad
this evening, and i couldn't recover from it, so i lost my /home filesystem
today.

i turned to amanda to get me out of this jam...

1) i ran amrecover (as root) from the host where i lost my data 
2) amanda ran through 1 of 3 tapes without error (the tape that had the
level 0 from 10/08)
3) when amanda switched to the first of 2 tapes with level 1's on it, i got
an error:
EOF, check amidxtaped.debug file on amanda
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue? [Y/n] : 

when i hit "y" , i was returned to my amrecover> prompt.  Does this mean the
level 1 data on that tape is corrupt?  if so, can i move on to the 3rd tape
and at least recover that data?


thanks in advance.


Highest Regards,

Edwin R. Rivera
UNIX Administrator
Tel:  +1 305 894 4609
Fax:  +1 305 894 4799
Page: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>



Re: your mail

2001-10-10 Thread Stephen Carville

On Wed, 10 Oct 2001, Joshua Baker-LePain wrote:

- On Wed, 10 Oct 2001 at 11:38am, Stephen Carville wrote
-
- > dumpcycle   7 days
- > runspercycle10
- > tapecycle   12 tapes
-
- > Backups are run Monday thru Friday. I figure this setup will give me a
- > full backup every Monday. Is that right?
-
- If backups are only run Mon-Fri (5 days), and your dumpcycle is 7 days (1
- week), then your runspercycle should be 5, not 10.  Runspercycle is how
- many runs per dumpcycle, not tapecycle.

OK, I think I've got it :-)

What is important is that if any tape -- say Wednesday's tape -- is
destroyed (earthquake, fire, airplane) I can still restore the
databases files up thru Tuesday from whatever tapes are in the
archive.  The DBA tells me he can restore the entire database from the
files on the volume I am backing up as long as I can restore these
files.  Because of how the tapes are rotated, that means all I can be
sure to have is Monday's and Tuesday's tapes plus all the tapes from
last week.  If the amanda scheduler makes this possible, then I am
happy.

- > Now how do I configure amanda to do differential backups (level 1) on
- > Tuesday thru Friday?  One email I found in the archives suggested
- > setting bumpdays to 4 but wouldn't that mean level 0 for four days?
-
- You're trying to force amanda into your schedule (full Monday,
- incremental otherwise).  The way amanda expects to be run is to be given
- the parameters above, and then be left alone to set her own schedule of
- full and incrementals within those parameters.  IOW, she'll try to balance
- out the backups so that each night's are about the same size as the
- previoius nights while making sure she does (in your case) level 0 of each
- FS at least once a week.

Like I said above, it doesn't matter as long as I can be certain that
I can restore the database and systems files.

-- 
-- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
==
Government is like burning witches:  After years of burning young
women failed to solve any of society's problems, the solution was to
burn more young women.
==





Re: How can I verify that Indexing is working?

2001-10-10 Thread Stephen Carville

On Thu, 11 Oct 2001, Bernhard R. Erdmann wrote:

- > I am trying to get the indexing working with amanda and I cannot
- > figure out to verify if I have it right yet.
-
- Did you set "index yes" in amanda.conf?

Yes.  I set it in the global section:

define dumptype global {
 index yes
# record no
}

define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
exclude list "/usr/local/lib/amanda/exclude.gtar"
priority low
}

define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority medium
}

I use "user-tar" for the dump in disklist.

-- 
-- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
==
Government is like burning witches:  After years of burning young
women failed to solve any of society's problems, the solution was to
burn more young women.
==





Re: How can I verify that Indexing is working?

2001-10-10 Thread Bernhard R. Erdmann

> I am trying to get the indexing working with amanda and I cannot
> figure out to verify if I have it right yet.

Did you set "index yes" in amanda.conf?

> Any idea what I am doing wrong?  Like Preston says in his book, nobody
> cares about backups, only restores!

Yeah, restoring rules!



Re: Amrecover - Amandaidx Looping?

2001-10-10 Thread Bernhard R. Erdmann

> I have read extensively and have failed to find a solution to my
> problem.  I am hoping someone will know what I have done wrong.  I
> can't
> seem to get "amrecover" to work for me.

Check using netstat if the following port are bound:

$ netstat -an|grep :1008. 
tcp0  0 0.0.0.0:10082   0.0.0.0:*  
LISTEN
tcp0  0 0.0.0.0:10083   0.0.0.0:*  
LISTEN
udp0  0 0.0.0.0:10080   0.0.0.0:*

$ grep ^am /etc/services 
amanda  10080/udp   # amanda backup services
amandaidx   10082/tcp   # amanda backup services
amidxtape   10083/tcp   # amanda backup services



Re:Amrecover and Amndaidx looping

2001-10-10 Thread Mark Holm

I am having exactly the same problem and cannot find an answer. The really
annoying part is that this was working just fine last week when I recovered
some files for the same server that is now complaining. My fails all look
similar to Mr. Smith. There have been two changes since last week. We rolled
all the Name Servers forward from 2 running  6.0 Redhat for Sparc and 1
running RedHat 7.0 to all running Redhat 7.1 on PCs and I rebooted the
backup server and added a couple of extra drives (which haven't even been
configured into the system yet). Is there some dependency on format of reply
from a name server for amandaidx? I have even attempted to do the recover
directly on the tape server box and get the same error using both localhost
and the fully qualified name of the tape server specifically given for all
the amrecover options. Help!?! Pulling files out without amrecover is a
pain...

markh

===
Mark A. Holm - Director of Network Engineering & Operations
Inherent.com, Inc.
2140 SW Jefferson St. Phone: (503) 224-6751
   Suite 200  extension 236
Portland, OR 97201  Fax: (503) 224-8872
   




Re: File too large?

2001-10-10 Thread Bernhard R. Erdmann

> I've got my chunksize set to 2Gb as it is, right now.  I'm using linux with
> a 2.2.14-5 kernel.  Would it cause problems if the chunksize was right at 2Gb?
> Perhaps I should lower it.

Oh yes, put it something below 2GB-32KB: a good value is 2000 MB



Re: selfcheck timeout - host down

2001-10-10 Thread Bernhard R. Erdmann

> IIRC, a SIGHUP isn't enough to restart xinetd.  You actually have to do
> '/etc/init.d/xinetd restart'.  Yes, it's annoying.

xinetd wants SIGUSR1 to reread the configuration files



Re: exclude directories

2001-10-10 Thread John W. Price

Alan Pham wrote:
> 
> Hi,
> 
> How can I exclude a directory (or directories) in a diskdev?
> For example, in disk list I have the following entry:
> 
> foohost c0t0d0s7
> 
> which is mounted on /export.
> 
> I have the following directories under /export:
> /export/home
> /export/scratch
> /export/slicer
> 
> How can I exclude /export/scratch?  This is a temp space to dump
> large output files from programs.

Somehow, I just got this message from the listserver.

I don't claim that this is the best way to do this, but it works for me.

In my amanda.conf, my dumptype "root-tar" looks like this:

=
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
exclude list "amanda/.amanda.excludes"
priority low
}
=

Most of the other tar-based dumptypes include root-tar, so this works
for all of them.  The "exclude list" line tells amanda to look in the
file "amanda/.amanda.excludes" for a list of files to exclude.  If I'm
backing up the /usr directory, for instance, the exclude file will be
/usr/amanda/.amanda.excludes.

In your case, given the dumptype definition above, you would create a
file called /export/amanda/.amanda.excludes with the following contents:

=
./home/*
./scratch/*
./slicer/*
=

Again, it works for me.  If it doesn't work for you, let me know and
I'll dig a little more.

John

-- 
   John Price *** **  ** *** [EMAIL PROTECTED]
   Where there is no solution, there is no problem.
   -- John G. Price (my father), ca. 1975.



Re: Netware

2001-10-10 Thread Jeff Pratt

You may also want to check out mars_nwe.  It does for netware what 
samba does for windows.  so you might be able to hack up the samba 
support to add netware.

Jeff

Toomas Aas wrote:

> Hi Felipe!
> 
> On 10 Oct 01 at 8:32 you wrote:
> 
> 
>>My name is Felipe and y tried to back up my information from 
>>netware 5 with amanda. Can I do it? how?
>>
> 
> I think you can't, currently. Some months ago the people from 
> MurkWorks (www.murkworks.com) were thinking of writing Amanda 
> dumper NLM for Netware, but I don't know if they found enough user 
> interest to tackle this project. You *might* find some information 
> from their website.
> 
> Another thing, if you have Netware NFS, maybe you can mount NW 
> volumes on some Un*x box and back them up this way. I've never used 
> or even seen NetWare NFS, though, so take this with the proverbial 
> grain of salt.
> 
> --
> Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
> * If it wasn't for C, we'd be using BASI, PASAL and OBOL!
> 
> 
> 





RE: Amanda 2.4.2p2 on Solaris 8 - "amanda" user account

2001-10-10 Thread Eva Freer

We had similar problems with BSM enabled. John Jackson gave me the
info on making amanda run as root in inetd.conf. The problem is
really with Solaris. John's info is attached.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Brian Cuttler
Sent: Wednesday, October 10, 2001 2:07 PM
To: [EMAIL PROTECTED]; Chris Knight
Subject: Amanda 2.4.2p2 on Solaris 8 - "amanda" user account


Hello all,

Have built a new tar-ball for a new "secure" system and wanted
to introduce a non-root non-bin account for amanda to run under.

Build (gcc on Solaris 2.8) seems to have gone well and the make
install ran cleanly.

Amended /etc/services and /etc/inetd.conf, placed both .rhosts
and .amandahosts under the login directory for the new account
but I'm unable to get amcheck to run.

Will provide full details below, just wanted to lay the problem
out first.

Any suggestions would be apreciated, I'm sure its minor - but
apparently not insignificant.

thanks,

Brian

---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773

# tail /etc/services

# Amanda
amanda  10080/udp   # amanda
amandaidx   10082/tcp   # amanda
amidxtape   10083/tcp   # amanda

# tail /etc/inetd.conf

# Amanda
amandaidx   stream  tcp nowait  amanda
/usr/local/lib/libexec/amindexd
amanda  dgram   udp waitamanda /usr/local/libexec/amandad
amandad

# cat /export/people/amanda/.amandahosts
bioinfo  bin
bioinfo  amanda
bioinfo.wadsworth.org bin
bioinfo.wadsworth.org amanda

Note - .rhosts is identical to .amandahosts and that the
amanda server is running amanda as "bin", hopefully I'll
get that fixed when I update the server next.

Yes - I am only configuring this new box as a "client", the
server is on a Solaris 2.7 system.

Running amcheck on the server I find the following messages
on the client. No /tmp/amanda directory is created nor any
amanda log files.

# tail /var/adm/messages
Oct  5 11:06:44 c110 inetd[24784]: [ID 858011 daemon.warning]
/usr/local/libexec/amandad: Hangup
Oct  5 11:07:04 c110 last message repeated 2 times

I know I'm missing something fairly minor - I just have no idea
what it is.

thanks,

Brian

- End of forwarded message from Brian Cuttler -

--- Begin Message ---

>We are running amanda 2.4.2p1 on Solaris 8 and Solaris 2.6 with it
>configured to run as amanda. Everything works fine until we enable Sun's
>Basic Security Module (BSM).  ...

This came up toward the end of May.  You can search the archives for
Subject "Problems with Solaris 8 BSM auditing and amanda 2.4.2p2".
I never saw a real solution to the problem go by, but there was a
workaround posted (appended).

>Eva Freer ([EMAIL PROTECTED])

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

  To: "Kevin M. Myer" <[EMAIL PROTECTED]>
  cc: [EMAIL PROTECTED]
  Subject: Re: Problems with Solaris 8 BSM auditing and amanda 2.4.2p2 
  Date: Wed, 30 May 2001 08:17:15 -0400
  From: Daniel Lorenzini <[EMAIL PROTECTED]>

  ...

  Kevin,

  I have seen this problem.  I suspect it is a Solaris problem but I
  can't be sure since I have not investigated it fully.  However, I have
  gotten it to work using a hack.

  Make a small script called "run-amandad" and put it in the directory with
  the other amada executables :

#!/bin/sh
su amanda -c /amandad

  Then change your inetd.conf line to:

amanda dgram  udp wait   root /run-amandad amanda

  I've been using this for a while and I haven't had any problems with it.

  Regards,

  Dan Lorenzini Greenwich Capital Markets
  [EMAIL PROTECTED]   600 Steamboat Road
  203-625-6088  Greenwich, CT 06830

--- End Message ---

BEGIN:VCARD
VERSION:2.1
N:Freer;Eva;Broadaway
FN:Eva Broadaway Freer
NICKNAME:Eva
ORG:Oak Ridge National Laboratory;Instrumentation & Controls Division
TITLE:Development Engineer
TEL;WORK;VOICE:865-574-6894
TEL;PAGER;VOICE:865-873-4293
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;PO Box 2008=0D=0AMS 6007=0D=0A;Oak Ridge;Tennessee;37831-6007;United State=
s
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:PO Box 2008=0D=0AMS 6007=0D=0A=0D=0AOak Ridge, Tennessee 37831-6007=0D=0AUni=
ted States
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20010315T015830Z
END:VCARD



How can I verify that Indexing is working?

2001-10-10 Thread Stephen Carville

I am trying to get the indexing working with amanda and I cannot
figure out to verify if I have it right yet.

If I log onto the client (euphrates) and try:

# sudo amrecover oracle-a

I get:

220 nile AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2001-10-10)
200 Working date set to 2001-10-10.
200 Config set to oracle-a.
200 Dump host set to euphrates.
Can't determine disk and mount point from $CWD

If I use setdisk to set the disk to one of the directories in
disklist:

amrecover> setdisk /t/tigris/ctrl_bkp
Scanning /flood/amanda...
  oracle-b: skipping cruft directory, perhaps you should delete it.
  oracle-a: skipping cruft directory, perhaps you should delete it.
  oracle-w: skipping cruft directory, perhaps you should delete it.
  data-a: skipping cruft directory, perhaps you should delete it.
200 Disk set to /t/tigris/ctrl_bkp.
No index records for disk for specified date
If date correct, notify system administrator

history shows:

amrecover> history
200- Dump history for config "oracle-a" host "euphrates" disk
"/t/tigris/ctrl_bkp"
201- 2001-10-10 2 oracle-a01 4
201- 2001-10-09 2 oracle-a00 3
201- 2001-10-08 1 oracle-a05 3
201- 2001-10-05 0 oracle-a04 6
201- 2001-10-04 1 oracle-a03 4
201- 2001-10-03 1 oracle-a02 5
200 Dump history for config "oracle-a" host "euphrates" disk
"/t/tigris/ctrl_bkp"

So there is a backup but no index!

.amandahost on the server (nile):

euphrates   root
euphrates   amanda

.amandahosts on the client (euphrates)

nileamanda

Both client and server have in /etc/services:

# amanda services
amanda  10080/udp
amandaidx   10082/tcp
amidxtape   10083/tcp

and in inetd.conf:

# amanda entries
amandadgram  udp wait   amanda /usr/local/libexec/amandad
amandad
amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd
amindexd
amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped
amidxtaped

Both sytems are running Solaris 8 and Linux (RH 7.X) will be added
soon.

Any idea what I am doing wrong?  Like Preston says in his book, nobody
cares about backups, only restores!

-- 
-- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
==
Government is like burning witches:  After years of burning young
women failed to solve any of society's problems, the solution was to
burn more young women.
==




Re: selfcheck timeout - host down

2001-10-10 Thread Lee Fedor

I was sighupping xinetd instead of stop/starting it.
Once I did that, it worked great. 

Thanks everyone,

Lee

> On Wed, Oct 10, 2001 at 09:13:17AM -0500, Lee Fedor wrote:
> > 
> > service amanda
> > {
> > disable = no
> > socket_type = dgram
> > protocol= udp
> > wait= yes
> > user= dump
> > group   = dump
> > server  = /usr/lib/amanda/amandad
> > port= 10080
> > }
> ^
> 
> It's better to add amanda to /etc/services instead of using the port
> number. Then kill xinetd and start it with debugging on 
> 
> xinetd -d 
> 
> and run amcheck, watching xinetd debug messages. This
> should either work or give at least a detailed message.
> 
> -- 
>  Alles Gute / best wishes  
>  Dietmar GoldbeckE-Mail: [EMAIL PROTECTED]
> Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
> Civilization?  Gandhi: I think it would be a good idea.



Re: Change dc=xxxxx

2001-10-10 Thread John Dalbec



Pierangelo Masarati wrote:
> 
> > Carlos Eduardo Gomes Marins wrote:
> >
> > Hi,
> >
> > I want to know if thereis any way to change the name of a dc entry.
> > The structure of my Ldap Server is similar to this:
> >
> >
> > dn: dc=arbi, dc=rsfn, dc=net, dc=br
> > objectClass: inetOrgPerson

This looks like a computer.  Why do you have objectClass: inetOrgPerson?
> > sn: arbi
> > cn: arbi.rsfn.net.br
> > .
> > .
> > .
> >
> > I'd like to change the entry dc=arbi, ... to a different name. How can
> > I do this after I've added this to my Ldap database?
> > Thanks in advance,
> 
> man ldapmordrn

man ldapmodrdn
> 
> Pierangelo.
> 
> --
> Dr. Pierangelo Masarati   | voice: +39 02 2399 8309
> Dip. Ing. Aerospaziale| fax:   +39 02 2399 8334
> Politecnico di Milano | mailto:[EMAIL PROTECTED]
> via La Masa 34, 20156 Milano, Italy   |
> http://www.aero.polimi.it/~masarati



Memory And Amrecover

2001-10-10 Thread Byron Schlemmer

Hi folks,

I get the following error when running amrecover :

amrecover> add filetorecover
Added /filetorecover
amrecover> extract

Extracting files using tape drive /dev/nsa0 on host
backup.server
The following tapes are needed: BKP-001

Restoring files into directory /tmp
Continue? [Y/n]: Y

Load tape BKP-001 now
Continue? [Y/n]: Y
tar: Skipping to next file header...
tar: Skipping to next file header...
tar: Skipping to next file header...
tar: Skipping to next file header...
tar: Skipping to next file header...
Couldn't allocate memory
extract_list - child returned non-zero status: 12
Continue? [Y/n]: n
amrecover> quit
200 Good bye.

I'm trying to extract filetorecover which is quite a large (500MB) text
log file. I've checked available memory and it's about 768MB, CPU load
is normal to. Any ideas what the problem is here?

TIA

-byron




Re: your mail

2001-10-10 Thread Joshua Baker-LePain

On Wed, 10 Oct 2001 at 11:38am, Stephen Carville wrote

> dumpcycle 7 days
> runspercycle  10
> tapecycle 12 tapes

> Backups are run Monday thru Friday. I figure this setup will give me a
> full backup every Monday. Is that right?

If backups are only run Mon-Fri (5 days), and your dumpcycle is 7 days (1
week), then your runspercycle should be 5, not 10.  Runspercycle is how
many runs per dumpcycle, not tapecycle.

> Now how do I configure amanda to do differential backups (level 1) on
> Tuesday thru Friday?  One email I found in the archives suggested
> setting bumpdays to 4 but wouldn't that mean level 0 for four days?

You're trying to force amanda into your schedule (full Monday,
incremental otherwise).  The way amanda expects to be run is to be given
the parameters above, and then be left alone to set her own schedule of
full and incrementals within those parameters.  IOW, she'll try to balance
out the backups so that each night's are about the same size as the
previoius nights while making sure she does (in your case) level 0 of each
FS at least once a week.

I haven't played around with bump settings, so I can't help there.  I can
just say that, unless there's a *really* compelling reason, it's best to
let amanda set her own schedule.

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




Re: File too large?

2001-10-10 Thread Joshua Baker-LePain

On Wed, 10 Oct 2001 at 3:20pm, Dave Brooks wrote

> I've got my chunksize set to 2Gb as it is, right now.  I'm using linux with
> a 2.2.14-5 kernel.  Would it cause problems if the chunksize was right at 2Gb?
> Perhaps I should lower it.
>
Yep, that's an issue.  Amanda adds on a 32KB for the header.  There's
no performance penalty for smaller chunksizes, which is why 1GB is the
default.

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




Re: File too large?

2001-10-10 Thread Dave Brooks

I've got my chunksize set to 2Gb as it is, right now.  I'm using linux with
a 2.2.14-5 kernel.  Would it cause problems if the chunksize was right at 2Gb?
Perhaps I should lower it.

-Dave

Maarten Vink writes:
>Maybe you are using an OS (linux for example) that has a filesize-limit of 2
>Gb? There's an option to limit filesizes in amanda.conf.
>
>Maarten Vink
>
>- Original Message -
>From: "Dave Brooks" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Wednesday, October 10, 2001 6:47 PM
>Subject: File too large?
>
>
>> What does "file to large" mean?  Example (from the email report:)
>>
>> FAILURE AND STRANGE DUMP SUMMARY:
>>   localhost  /hermes lev 0 FAILED ["data write: File too large"]
>>
>> I cant figure out whats up with that... my spooling disk is 40GB (and its
>> empty), and my tapes are 40GB compressed.  Any ideas as to what that
>means?
>>
>> -Dave
>>
>> --
>> david a. brooks
>> * systems administrator
>> * stayonline.net
>> * voice: .. 770/933-0600 x217
>> * email: .. [EMAIL PROTECTED]
>> * :wq!
>>
>
>

-- 
david a. brooks
* systems administrator
* stayonline.net
* voice: .. 770/933-0600 x217
* email: .. [EMAIL PROTECTED]
* :wq!



[no subject]

2001-10-10 Thread stefano

unsubscribe [EMAIL PROTECTED]



Re: Netware

2001-10-10 Thread Toomas Aas

Hi Felipe!

On 10 Oct 01 at 8:32 you wrote:

> My name is Felipe and y tried to back up my information from 
> netware 5 with amanda. Can I do it? how?

I think you can't, currently. Some months ago the people from 
MurkWorks (www.murkworks.com) were thinking of writing Amanda 
dumper NLM for Netware, but I don't know if they found enough user 
interest to tackle this project. You *might* find some information 
from their website.

Another thing, if you have Netware NFS, maybe you can mount NW 
volumes on some Un*x box and back them up this way. I've never used 
or even seen NetWare NFS, though, so take this with the proverbial 
grain of salt.

--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* If it wasn't for C, we'd be using BASI, PASAL and OBOL!



RE: Qualstar TLS 4212

2001-10-10 Thread Mark Holm

I have a 4220 which is the 22 tape version, but I had to build a custom
changer script based on the chg-mtx one to make it work reliably. I have
attached it and it's configuration script to this message.

markh


-Original Message-
From: Malcolm Locke [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 29, 2001 9:02 AM
To: [EMAIL PROTECTED]
Subject: Qualstar TLS 4212


I was just wondering before I start fiddling whether anyone has had
success (or otherwise) with the above changer, or a similar qualstar
model.  It is a 13 tape robot using Sony AIT tapes.  

I am not too worried about the tapetype configuration as I have found
information on this but am more interested if anyone can offer
configuration information on the changer.

Many thanks
-- 
Malcolm Locke  [ 365 Corportion - http://www.365corp.com/ ]
Tel: 020 7505 7817  Mob: 07759 476607
  PGP: 1024D/12DD2EC6 2001-02-20 Malcolm Locke <[EMAIL PROTECTED]>


begin 600 changer.conf
M(R!.=6UB97(@;V8@=&AE('1A<&4@9')I=F4@:6X@8VAA;F=E6-L92`Q,#`P#0H-"B,@1&\@=V4@;F5E9"!T;R!E:F5C
J="!T:&4@=&%P93H@,2`M(%EE&ET(%-T871U'!O7!I8V%L;'D-"B,)("!T:&ES(&ES("]D978O'!O9FERW!R:6YT("0R?2=@#0IE;F1S;&]T/6!GW!R:6YT("0R?2=@#0IC;&5A
M;G-L;W0]8&=R97`@7F-L96%N8VQE86YC>6-L92`D0TA!
M3D=%4D-/3D8@?"!A=VL@)WMP8VAG=&%P961E=B`D0TA!3D=%4D-/3D8@?"!A=VL@)WMP&ET(#([#0IF:0T*#0II9B!T97-T("(D96YD&ET(#([#0IF:0T*#0II9B!T97-T("(D8VQE86YC>6-L92(@/2`B+V1E=B]N
M=6QL(B`M;R`B)&-L96%N8WEC;&4B(#T@(B([('1H96X-"B`@8VQE86YC>6-L
M93TQ,`T*9FD-"@T*:68@=&5S="`A("(D;F5E9&5J96-T(B`]("(Q(CL@=&AE
M;@T*("!N965D96IE8W0],`T*9FD-"@T*96-H;R`B9FER6-L92(@/CX@)$1"1T9)3$4-"F5C:&\@(F-H9W1A<&5D
M978@("`@+3X@)&-H9W1A<&5D978B(#X^("1$0D=&24Q%#0IE8VAO(")N965D
M96IE8W0@("`@+3X@)&YE961E:F5C="(@/CX@)$1"1T9)3$4-"@T*8VAA;F=E
M6YA;64])#`-"DU4/2(O8FEN+VUT(@T*351&/2(M9B(-"DU4
M6#TB;71X("UF("1405!%(@T*1$0]+V)I;B]D9`T*;6%X=V%I='1I;64],C`P
M#0H-"B,-"B,@1G5N8W1I;VX@9&5F:6YI=&EO;G,-"B,-"F5J96-T7W1A<&4H
M*2![#0H@("`@(PT*("`@(",@0VAE8VL@=&\@&ET
M(#(-"B`@("`@(&9I#0H@("`@9FD-"GT-"@T*=V%I=%]F;W)?=&%P92@I('L-
M"B`@('1I;65?&ET(#$-"B`@(&9I#0I]#0H-"@T*(PT*
M#0IT87!E7V]N;&EN92@I('L-"B`@(&EF(%L@8"1-5"`D351&("1T87!E('-T
M871U2(@/CX@)$1"1T9)3$4-"B`@("`@
M('1A<&5?2\@>W!R:6YT("TQ?3LG8`T*#0H@(&EF(%L@+7H@(B1UPT*("!R96%D&ET(#`-"B`@96QS90T*("`@(&5C:&\@(C`@
M1')I=F4@=V%S(&YO="!L;V%D960B#0H@("`@97AI="`Q#0H@(&9I#0I]#0H-
M"G)EPT*("!R96%D2!T87!E(&1O97,@;F]T+@T*("`@(",@5V4@=&AE&ET(#`-"B`@("!F:0T*("`@(&5C:&\@(B`@
M("`@+3X@;&]A9"`@("1L;V%D(B`^/B`D1$)'1DE,10T*"2`@("`@("`-"B`@
M("!R97,]8"1-5%@@;&]A9"`D;&]A9"`D8VAG=&%P961E=B`R/B8Q8`T*("`@
M('-T871UW!R:6YT("0V("0W?2=@#0H@("`@("!I9B!;("(D>W-H
M;W)T7W)EPT*("!R96%D&ET(#(-"B`@("`@("`[.PT*
.("!E


[no subject]

2001-10-10 Thread Stephen Carville

I have amanda working with hand changing of tapes.  I will soon
get a tape changer woth an AIT2 drive.  Here is my proposed cycle:

dumpcycle   7 days
runspercycle10
tapecycle   12 tapes

Backups are run Monday thru Friday. I figure this setup will give me a
full backup every Monday. Is that right?

Now how do I configure amanda to do differential backups (level 1) on
Tuesday thru Friday?  One email I found in the archives suggested
setting bumpdays to 4 but wouldn't that mean level 0 for four days?

-- 
-- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
==
Government is like burning witches:  After years of burning young
women failed to solve any of society's problems, the solution was to
burn more young women.
==




Amanda 2.4.2p2 on Solaris 8 - "amanda" user account

2001-10-10 Thread Brian Cuttler

Hello all,

Have built a new tar-ball for a new "secure" system and wanted
to introduce a non-root non-bin account for amanda to run under.

Build (gcc on Solaris 2.8) seems to have gone well and the make
install ran cleanly.

Amended /etc/services and /etc/inetd.conf, placed both .rhosts
and .amandahosts under the login directory for the new account
but I'm unable to get amcheck to run.

Will provide full details below, just wanted to lay the problem
out first.

Any suggestions would be apreciated, I'm sure its minor - but
apparently not insignificant.

thanks,

Brian

---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773

# tail /etc/services 

# Amanda
amanda  10080/udp   # amanda
amandaidx   10082/tcp   # amanda
amidxtape   10083/tcp   # amanda

# tail /etc/inetd.conf

# Amanda
amandaidx   stream  tcp nowait  amanda /usr/local/lib/libexec/amindexd
amanda  dgram   udp waitamanda /usr/local/libexec/amandad amandad

# cat /export/people/amanda/.amandahosts
bioinfo  bin
bioinfo  amanda
bioinfo.wadsworth.org bin
bioinfo.wadsworth.org amanda

Note - .rhosts is identical to .amandahosts and that the
amanda server is running amanda as "bin", hopefully I'll
get that fixed when I update the server next.

Yes - I am only configuring this new box as a "client", the
server is on a Solaris 2.7 system.

Running amcheck on the server I find the following messages
on the client. No /tmp/amanda directory is created nor any
amanda log files.

# tail /var/adm/messages
Oct  5 11:06:44 c110 inetd[24784]: [ID 858011 daemon.warning] 
/usr/local/libexec/amandad: Hangup
Oct  5 11:07:04 c110 last message repeated 2 times

I know I'm missing something fairly minor - I just have no idea
what it is.

thanks,

Brian

- End of forwarded message from Brian Cuttler -



Re: Netware

2001-10-10 Thread Johannes Niess

Felipe de Jes·s Molina Bravo <[EMAIL PROTECTED]> writes:

> My name is Felipe and y tried to back up my information from 
> netware 5 with amanda. Can I do it? how?

Felipe,

AFIK there is no native netware client for Amanda. I'd use ncpfs on a
linux client to have the data seen as belonging to the linux box and
backup that.

HTH,

Johannes Niess




Re: File too large?

2001-10-10 Thread Maarten Vink

Maybe you are using an OS (linux for example) that has a filesize-limit of 2
Gb? There's an option to limit filesizes in amanda.conf.

Maarten Vink

- Original Message -
From: "Dave Brooks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 10, 2001 6:47 PM
Subject: File too large?


> What does "file to large" mean?  Example (from the email report:)
>
> FAILURE AND STRANGE DUMP SUMMARY:
>   localhost  /hermes lev 0 FAILED ["data write: File too large"]
>
> I cant figure out whats up with that... my spooling disk is 40GB (and its
> empty), and my tapes are 40GB compressed.  Any ideas as to what that
means?
>
> -Dave
>
> --
> david a. brooks
> * systems administrator
> * stayonline.net
> * voice: .. 770/933-0600 x217
> * email: .. [EMAIL PROTECTED]
> * :wq!
>




Amrecover - Amandaidx Looping?

2001-10-10 Thread smith

Hi all,

I have read extensively and have failed to find a solution to my
problem.  I am hoping someone will know what I have done wrong.  I
can't
seem to get "amrecover" to work for me.

Background:
Server name = garfield
OS = Red Hat Linux 7.1
Amanda = 2.4.2p2
Configuration = sky(rather than DailySet1)
Tape Device = /dev/nst0

When I try to run 'amrecover' as root, I get the following result :
[root@garfield /root]# amrecover -C sky
AMRECOVER Version 2.4.2p2. Contacting server on garfield ...
amrecover: cannot connect to garfield: Connection refused

This is what shows up in my "/tmp/amanda/amanda*debug":
[root@garfield amanda]# cat amrecover.20011010121258.debug
amrecover: debug 1 pid 2022 ruid 0 euid 0 start time Wed Oct 10
12:12:58 2001
amrecover: stream_client: connect(10082) failed: Connection
refused
cannot connect to garfield: Connection refused
amrecover: pid 2022 finish time Wed Oct 10 12:12:58 2001

And this is what I see in "/var/log/messages":
Oct 10 12:01:20 garfield xinetd[1927]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:20 garfield xinetd[1928]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:20 garfield xinetd[1929]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:20 garfield xinetd[1930]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:20 garfield xinetd[1931]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1932]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1933]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1934]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1935]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1936]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1923]: amandaidx service was
deactivated because of looping

Here's my 'xinetd.d' information from "/etc/xinetd.d/amanda":
[root@garfield amanda]# cat /etc/xinetd.d/amanda
# default: off
# description:  The client for the Amanda backup system.\
#   This must be on for systems being backed up\
#   by Amanda.
 service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group   = disk
server  = /usr/lib/amanda/amandad
}

Here's my 'xinetd.d' information from "/etc/xinetd.d/amandaidx":
[root@garfield amanda]# cat /etc/xinetd.d/amandaidx
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
   socket_type = stream
   protocol= tcp
   wait= yes
   user= amanda
   group   = disk
   server  = /usr/lib/amanda/amindexd
}

Here's my 'xinetd.d' information from "/etc/xinetd.d/amidxtape":
[root@garfield xinetd.d]# cat /etc/xinetd.d/amidxtape
# default: off
#
# description: Part of the amanda server package
#
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group   = disk
server  = /usr/lib/amanda/amidxtaped
}


I would be extremely grateful for any help anyone can offer.  I don't
know where else to look.  Thanks!

Jeffery Smith
[EMAIL PROTECTED]






Re: Amanda stops due file system full when it is not!

2001-10-10 Thread Wayne Richards

Check the number of inodes allocated in the filesystem.

Usually:

df -ki

> Hi,
> 
> I have a problem with my Amanda backups.  The Amanda backup stops while
> doing the second last share with an error:
> 
>   NOTICE:   alloc:   /holding:   file system full
> 
> But when I check the holding area I find that while it does have share data
> in it, it is only sitting at 24% of capacity and so should have lots of free
> space.
> 
> Can anyone help with this one?
> 
> Regards,
> 
> Craig Walker



---
Wayne Richards  Phone:  330 796-4462
Goodyear Tech CenterFax:330 796-3947
Department 431A e-mail: [EMAIL PROTECTED]
PO Box 3531
Akron, OH  44309-3531






File too large?

2001-10-10 Thread Dave Brooks

What does "file to large" mean?  Example (from the email report:)

FAILURE AND STRANGE DUMP SUMMARY:
  localhost  /hermes lev 0 FAILED ["data write: File too large"]

I cant figure out whats up with that... my spooling disk is 40GB (and its
empty), and my tapes are 40GB compressed.  Any ideas as to what that means?

-Dave

-- 
david a. brooks
* systems administrator
* stayonline.net
* voice: .. 770/933-0600 x217
* email: .. [EMAIL PROTECTED]
* :wq!



Netware

2001-10-10 Thread Felipe de Jes·s Molina Bravo

Hi

My name is Felipe and y tried to back up my information from 
netware 5 with amanda. Can I do it? how?

Thanks



Re: selfcheck timeout - host down

2001-10-10 Thread Joshua Baker-LePain

On Wed, 10 Oct 2001 at 9:13am, Lee Fedor wrote

> I have setup everything on my redhat 7.1 client
> for backups, but it isn't listening on 10080.
> (amanda-2.4.2p2)
>
> I have sigHUP'd xinetd several times while tweaking
> on this file, but still can't get the port to show
> up on netstat  Have I put something in here
> wrong?  Is there an obvious typo?

IIRC, a SIGHUP isn't enough to restart xinetd.  You actually have to do
'/etc/init.d/xinetd restart'.  Yes, it's annoying.

> service amanda
> {
> disable = no
> socket_type = dgram
> protocol= udp
> wait= yes
> user= dump
> group   = dump
> server  = /usr/lib/amanda/amandad
> port= 10080
> }

Just in case, this is what my /etc/xinetd.d/amanda file looks like:

service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group   = disk
server  = /usr/local/libexec/amandad
server_args = amandad
}


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




selfcheck timeout - host down

2001-10-10 Thread Lee Fedor


well, I know where the problem has to lie.
I just don't know what I am doing wrong, or
how to fix it.

I have setup everything on my redhat 7.1 client
for backups, but it isn't listening on 10080.
(amanda-2.4.2p2)

I have sigHUP'd xinetd several times while tweaking
on this file, but still can't get the port to show
up on netstat  Have I put something in here 
wrong?  Is there an obvious typo?

This is a new server that was pressed into use
in an emergency, and cannot be rebooted without
causing a bunch of grief... :(

Thanks in advance for any help anyone can give me.



This is my xinetd.conf file:

defaults
{
instances   = 60
log_type= SYSLOG authpriv
log_on_success  = HOST PID
log_on_failure  = HOST
}

service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= dump
group   = dump
server  = /usr/lib/amanda/amandad
port= 10080
}

service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= dump
group   = dump
server  = /usr/lib/amanda/amandaidx
port= 10082
}

service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= dump
group   = dump
server  = /usr/lib/amanda/amidxtape
port= 10083
}


#includedir /etc/xinetd.d




faq o matic

2001-10-10 Thread Lee Fedor

The faq o matic has been offline now for a couple
of days... some one know about this don't they?



unsubscribe

2001-10-10 Thread Hsu George-CGH039


unsubscribe




Amanda stops due file system full when it is not!

2001-10-10 Thread Walker, Craig

Hi,

I have a problem with my Amanda backups.  The Amanda backup stops while
doing the second last share with an error:

NOTICE:   alloc:   /holding:   file system full

But when I check the holding area I find that while it does have share data
in it, it is only sitting at 24% of capacity and so should have lots of free
space.

Can anyone help with this one?

Regards,

Craig Walker




Amandaidx-amrecover

2001-10-10 Thread X X

Amandaidx-amrecover

I'm having some trouble with amrecover:

When amandaidx is listening on the right port and I run amrecover with the 
right parameters I get the following error message on the client:

amrecover: Error reading line from server: Connection reset by peer.

And if I try it again I get this:

amrecover: cannot connect to BackupServer: connection refused.

The following is happening on the serversida:

In /var/log/messages:

BackupServer xinetd[970]: warning: can't get client address: Transport 
endpoint not connected.

This prints out 8 times and then:

amandaidx service was deactivated because of looping.

The amanda debug files says nothing of value.

I don't know what to do about this, why should not the server be able to 
connect to the client? I guess some sort of lookup is done and fails but I 
don't know what to do.
Any information are appreciated.

Os: Linux Red Hat 7.1 (sever and client)
Amanda: 2.4.2p2-1

_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp




unsubscribe

2001-10-10 Thread Monserrat Seisdedos Nuñez

unsubscribe





Finding tape changers

2001-10-10 Thread Terri Eads

Hello,

I'm new to this list, but didn't find much in the archives
about this subject.

I've recently inherited an Overland MiniLibrary Xpress from
a company that went out of business. I've been using amanda
in a very simple configuration. My question now is this: how
do I go about finding the right tape changer for this library?

Thanks for any info or pointers to docs.
-- 
Terri Eads  Systems Administrator
[EMAIL PROTECTED]   Research Applications Program
(303) 497-8425  National Center for Atmospheric Research