Re: something of an emergency amrecover question

[Bernhard R. Erdmann]

> Now I just get to, ah...wait a while for these to all extract.

Amanda rulez!

Re: changer backup...

[John R. Jackson]

>What I want to do with this config. is to backup a couple of linux
>machines. I know that I need several configs ...

Why?  I back up dozens of machines to a single tape via a single config.
That's the usual way of setting up Amanda.  One server, multiple clients.

>... So, when I run amanda to do the backup, will amanda figure
>out itself which tape to use?  ...

I think so.  I think it will see the "wrong" tape and advance to the next
one until it finds the "right" tape for the configuration it is running.

You can test this with "amcheck".

>So, does this also mean that I have to
>amlabel those tapes manually before use?

Yes.  You have to amlabel all Amanda tapes.

>-Daniel.

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

Re: restoring from chunked holding disk files

[Todd Pfaff]

On Fri, 20 Apr 2001, John R. Jackson wrote:

> To deal with multiple holding disks and chunks being scattered around,
> the header on the files contains a link to the next file.  It's absolute
> and valid from the server point of view.  I suspect that's something we
> need to think about in the future (I can see it causing other problems),
> but is certainly nailing you right now.
> 
> Any chance you can create temporary symlinks on the client to emulate
> the server holding disk structure?  Like "ln -s /net/mmri1011/2 /2"?

yup, already thought of that workaround, even though i didn't
understand the cause of the problem.  i did this and it's working...
ln -s /net/mmri1011/2/amanda /2/amanda

--
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: amcheck failing with "selfcheck request timed out"

[John R. Jackson]

>When amcheck is run, the clients -do- start amandad.  I get prolific
>amandad.debug  and selfcheck.debug files on the clients.  ...

Actually, you're getting a bit **too** much :-).

>I'm green on Linux, so that may be part of the problem. xinetd is new to me,
>but I think I've got the files in xinetd.d configured correctly on the
>server, since each file is an analogy to the corresponding old inetd.conf
>entry.  Typos always possible.

Actually, there are some subtle differences.  Please post the xinetd
config file you're using.  I'm most suspicious of a problem with it.
There have been numerous "issues" here recently.

>The debug files say there is some weirdness with acknowledgments.  ...

Specifically what they are saying is that amcheck sent the SERVICE request
(and so on) to amandad, amandad sent back the response (the OK lines),
but what it got back was not an ACK to the response but a repeat of
the request.  The repeat is normal when amcheck has waited 30 seconds
and doesn't think the client has responded.  But I don't know why it
would think that.

Do you have a /tmp/amanda/amcheck*debug file on the server?  Is there
anything of interest in it?

>David Carter

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

Re: No such file or directory

[John R. Jackson]

>ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such
>file or directory]
>ERROR: myserver.mydomain.com: [can not access /disc1 (/disc1): No such
>file or directory]

This message says Amanda was not able to convert the /disc* names to
the corresponding /dev names (those names should show up inside the
parenthesis).

Does your Amanda user (the one inetd kicks amandad off as) have access
to /etc/vfstab and /etc/mtab?  What happens if you run "mount" as the
Amanda user?

Try this, too:

  cd client-src
  make getfsent
  ./getfsent /disc1

It should output some debugging information about how Amanda tried to
find the mount point.

> Tal Ovadia

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

Re: restoring from chunked holding disk files

[John R. Jackson]

>amrestore: can't open /2/amanda/20010420/mmri1001._2.0.1: No such file or
>directory
>
>huh?  why did amrestore trim /net/mmri1011 off the path?

That's why I asked if the files were really in the holding disk.
They only sort of are in your case.

To deal with multiple holding disks and chunks being scattered around,
the header on the files contains a link to the next file.  It's absolute
and valid from the server point of view.  I suspect that's something we
need to think about in the future (I can see it causing other problems),
but is certainly nailing you right now.

Any chance you can create temporary symlinks on the client to emulate
the server holding disk structure?  Like "ln -s /net/mmri1011/2 /2"?

Or, another approach is to run amrestore on the server and rsh/ssh the
image back to the client:

  mmri1001 # rsh mmri1011 amrestore -p /2/amanda/20010420/mmri1001._2.0 | tar ...

Or you can always use emacs and so some binary editing :-).

>Todd Pfaff

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

Re: restoring from chunked holding disk files

[Todd Pfaff]

On Fri, 20 Apr 2001, John R. Jackson wrote:

> If those files are truely in the holding disk (i.e. you didn't bring
> them back from tape), amrestore (certainly in 2.4.2 and I think before
> that) already knows how to read from the holding disk and will do all
> the chaining for you.  So it would be:
> 
>   amrestore -p /path/to/mmri1001._2.0 | tar tf ...

ran into a problem...

the holding disk is nfs-exported from the amanda server to the client i'm
restoring.  i access this nfs share via the path /net/server/path.  the
client is mmri1001, the server is mmri1011.  so, on mmri1001 i did:

amrestore -p /net/mmri1011/2/amanda/20010420/mmri1001._2.0 | tar xvf -

it got through the first chunk and then reported:

amrestore: can't open /2/amanda/20010420/mmri1001._2.0.1: No such file or
directory

huh?  why did amrestore trim /net/mmri1011 off the path?

--
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: Scheduling problem

[John R. Jackson]

>...  Amanda's way of attempting to balance the backup 
>load throughout the dumpcycle messing up my schedule.  ...

Seems to me you're the one messing up Amanda's schedule :-) :-).

In addition to the idea from Thommy, you could create one file like this
called "full":

  define dumptype full_or_incremental {
strategy noinc
  }

and another like this in a file named "incremental":

  define dumptype full_or_incremental {
strategy nofull
  }

then in your amanda.conf have this line early on:

  includefile "full_or_incremental"

and have every dumptype (or global) reference the above dumptype
(full_or_incremental):

  define dumptype global {
...
full_or_incremental
  }

The amdump cron job then sets a symlink of full_or_incremental to either
"full" or "incremental" depending on what day it is.

  today=`date '+%A'`
  rm -f full_or_incremental
  if [ $today = Friday ]
  then
ln -s full full_or_incremental
  else
ln -s incremental full_or_incremental
  fi
  amdump ...

>Bill Campbell

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

Re: restoring from chunked holding disk files

[Todd Pfaff]

On Fri, 20 Apr 2001, John R. Jackson wrote:

> >I want to restore a filesystem from some amanda holding disk chunk files:
> >
> >-rw---   1 backup   backup   2147385344 Apr 20 04:04 mmri1001._2.0
> >-rw---   1 backup   backup   2147385344 Apr 20 04:17 mmri1001._2.0.1
> >-rw---   1 backup   backup   1540063232 Apr 20 04:30 mmri1001._2.0.2
> >
> >So, I need to do something like this:
> >
> >cat mmri1001._2.0* | amrestore -p - mmri1001 /2 | tar tf - |p
> 
> Wow, are you ever working too hard :-).

Tell me about it.  I've been working on a disaster recovery all day and
I'm a bit frazzled.

> If those files are truely in the holding disk (i.e. you didn't bring
> them back from tape), amrestore (certainly in 2.4.2 and I think before
> that) already knows how to read from the holding disk and will do all
> the chaining for you.  So it would be:
> 
>   amrestore -p /path/to/mmri1001._2.0 | tar tf ...

Excellent, thanks.  I'm glad it's easier than I was making it out to be.

> If that doesn't work for some reason, go down a layer and use subshells
> with dd:
> 
>   ( dd if=mmri1001._2.0 bs=32k skip=1 ; \
> dd if=mmri1001._2.0.1 bs=32k skip=1 ; \
> dd if=mmri1001._2.0.2 bs=32k skip=1 ) | gunzip | tar ...
> 
> (remove the gunzip if you're not using software compression, of course).

Well, that's cool too.  This was pretty much what I was asking for, I just
wasn't sure how to accomplish it.  But I'm trying your simpler suggestion
above first.

Thanks again John.

--
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: restoring from chunked holding disk files

[John R. Jackson]

>I want to restore a filesystem from some amanda holding disk chunk files:
>
>-rw---   1 backup   backup   2147385344 Apr 20 04:04 mmri1001._2.0
>-rw---   1 backup   backup   2147385344 Apr 20 04:17 mmri1001._2.0.1
>-rw---   1 backup   backup   1540063232 Apr 20 04:30 mmri1001._2.0.2
>
>So, I need to do something like this:
>
>cat mmri1001._2.0* | amrestore -p - mmri1001 /2 | tar tf - |p

Wow, are you ever working too hard :-).

If those files are truely in the holding disk (i.e. you didn't bring
them back from tape), amrestore (certainly in 2.4.2 and I think before
that) already knows how to read from the holding disk and will do all
the chaining for you.  So it would be:

  amrestore -p /path/to/mmri1001._2.0 | tar tf ...

It doesn't look like the man page got updated until 2.4.2, but if you
look at the comments at the head of the source in 2.4.1p1 you should
see "tape-device|holdingfile".

If that doesn't work for some reason, go down a layer and use subshells
with dd:

  ( dd if=mmri1001._2.0 bs=32k skip=1 ; \
dd if=mmri1001._2.0.1 bs=32k skip=1 ; \
dd if=mmri1001._2.0.2 bs=32k skip=1 ) | gunzip | tar ...

(remove the gunzip if you're not using software compression, of course).

>Todd Pfaff

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

Re: Amanda backup

[John R. Jackson]

> I am backing up 3 systems using amanda. My /etc/dumpdates on 3 systems ( tota
>l 12 files)shows that al the files were backed up.  ...

Did the Amanda mail report show all 12 file systems being backed up?
Any problems reported?  Did all of the images make it to the tape or
did you have to amflush some?

>But the amverify shows less
> file systems than what /etc/dumpdates indicate( only 4 files). 

I'd have to see the amverify report to know exactly what you mean.

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

restoring from chunked holding disk files

[Todd Pfaff]

I want to restore a filesystem from some amanda holding disk chunk files:

-rw---   1 backup   backup   2147385344 Apr 20 04:04 mmri1001._2.0
-rw---   1 backup   backup   2147385344 Apr 20 04:17 mmri1001._2.0.1
-rw---   1 backup   backup   1540063232 Apr 20 04:30 mmri1001._2.0.2

So, I need to do something like this:

cat mmri1001._2.0* | amrestore -p - mmri1001 /2 | tar tf - |p

but as far as I know, amrestore does not support reading from standard
input as the tape device.  This may be a useful feature to add to
amrestore.

Anyone have any suggestions for a simple way to accomplish this?

--
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 \

amcheck failing with "selfcheck request timed out"

[David Carter]

I've got a new install on RedHat 7.1 (amanda server 2.4.2p2) and clients are
Solaris 2.6 (amanda 2.4.1p1)

I've gone through the entries in the AMANDA FAQ-o-matic without success.

I built amanda on the RedHat system, rather than installing the pre-compiled
rpm included with the distribution.

The builds were all configured with the following options:

--with-user=root --with-group=sys --with-amandahosts

When amcheck is run, the clients -do- start amandad.  I get prolific
amandad.debug  and selfcheck.debug files on the clients. The clients have
been working with another server (Solaris 2.6 amanda 2.4.1p1) for quite some
time.  The only thing I've changed on the clients is the .amandahosts file.
It seemed like that's all that should be necessary on the client side.

I'm green on Linux, so that may be part of the problem. xinetd is new to me,
but I think I've got the files in xinetd.d configured correctly on the
server, since each file is an analogy to the corresponding old inetd.conf
entry.  Typos always possible.

The debug files say there is some weirdness with acknowledgments.  All the
machines are inside our firewall.

client: draco
server: zig
Here's draco's amandad.debug file:

--
amandad: debug 1 pid 19035 ruid 0 euid 0 start time Fri Apr 20 17:59:23 2001
amandad: version 2.4.1p1
amandad: build: VERSION="Amanda-2.4.1p1"
amandad:BUILT_DATE="Mon Oct 16 17:51:46 CDT 2000"
amandad:BUILT_MACH="SunOS draco 5.6 Generic_105181-22 sun4u sparc
SUNW,Ultra-5_10"
amandad:CC="gcc"
amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man"
amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/"
amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump"
amandad:RESTORE="/usr/sbin/ufsrestore"
amandad:GNUTAR="/usr/local/bin/gtar"
amandad:COMPRESS_PATH="/usr/local/bin/gzip"
amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" MAILER="/bin/mailx"
amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
amandad: defs:  DEFAULT_SERVER="draco" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="draco"
amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
amandad:CLIENT_LOGIN="nobody" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
got packet:

Amanda 2.4 REQ HANDLE 001-D0A40708 SEQ 987804045
SECURITY USER root
SERVICE selfcheck
OPTIONS ;
DUMP /home 0 OPTIONS |;bsd-auth;


sending ack:

Amanda 2.4 ACK HANDLE 001-D0A40708 SEQ 987804045


bsd security: remote host zig user root local user root
amandahosts security check passed
amandad: running service "/usr/local/libexec/selfcheck"
amandad: sending REP packet:

Amanda 2.4 REP HANDLE 001-D0A40708 SEQ 987804045
OPTIONS ;
OK /home
OK /usr/sbin/ufsdump executable
OK /etc/dumpdates read/writable
OK /dev/null read/writable
OK /tmp has more than 64 KB available.
OK /tmp/amanda has more than 64 KB available.
OK /etc has more than 64 KB available.


amandad: got ack:

Amanda 2.4 REQ HANDLE 001-D0A40708 SEQ 987804045
SECURITY USER root
SERVICE selfcheck
OPTIONS ;
DUMP /home 0 OPTIONS |;bsd-auth;


amandad: weird, it's not a proper ack
  addr: peer C0A8C36F dup C0A8C36F, port: peer 319 dup 319
amandad: sending REP packet:

Amanda 2.4 REP HANDLE 001-D0A40708 SEQ 987804045
OPTIONS ;
OK /home
OK /usr/sbin/ufsdump executable
OK /etc/dumpdates read/writable
OK /dev/null read/writable
OK /tmp has more than 64 KB available.
OK /tmp/amanda has more than 64 KB available.
OK /etc has more than 64 KB available.


amandad: waiting for ack: timeout, retrying
amandad: got ack:

Amanda 2.4 REQ HANDLE 001-D0A40708 SEQ 987804045
SECURITY USER root
SERVICE selfcheck
OPTIONS ;
DUMP /home 0 OPTIONS |;bsd-auth;


amandad: weird, it's not a proper ack
  addr: peer C0A8C36F dup C0A8C36F, port: peer 319 dup 319
amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, giving up!
amandad: pid 19035 finish time Fri Apr 20 18:00:23 2001
--

Here's the selfcheck.debug file:
--
selfcheck: debug 1 pid 19036 ruid 0 euid 0 start time Fri Apr 20 17:59:23
2001
/usr/local/libexec/selfcheck: version 2.4.1p1
checking disk /home: device /dev/rdsk/c0t0d0s7: OK
selfcheck: pid 19036 finish time Fri Apr 20 17:59:23 2001
--



David Carter
McLeodUSA Information Systems
[EMAIL PROTECTED]
281-465-1835

Re: something of an emergency amrecover question

[Nathan J. Mehl]

In the immortal words of Bernhard R. Erdmann ([EMAIL PROTECTED]):
> Hey, reading restore's (Linux dump-0.4b21) manpage offers an option for
> you:
> 
> amrestore -p $TAPE host /partition | restore X /tmp/files-to-restore f -

not quite...but that was the hint I needed, and many thanks!

it's actually:

amrestore -p $TAPE host disk | \
restore -xc -X /tmp/files-to-restore -f -

Many, many thanks again!

Now I just get to, ah...wait a while for these to all extract.

-n

<[EMAIL PROTECTED]>
Ocean water in / my small, light aircraft engine / makes me very dead.
Environmental / aviator is that the / water there? Oh God!
Rocky mountain high / sunshine on my shoulder now / makes me decompose.
(--haikus for John Denver)

Re: something of an emergency amrecover question

[John R. Jackson]

>Is there any way in amrecover to recursively add every instance of a
>filename in a set of directories?  ...

No.  I just took a note to myself yesterday to add a "find" command to
at least find files with a given pattern.  That could be extended to
also add them to the extraction list.

Note that you're likely to have trouble with the vast number of files
you want to restore though.  Amanda has to live within OS command line
(number of arguments and total length) limits.  If you blow by those,
it's not going to work.

My guess is you'll have to make multiple passes at the image and use
something like xargs to grab batches at a time.  Something like this:

  zcat the-index-files | grep the-file-pattern > the-file-list
  xargs get-some-files < the-file-list

  #!/bin/sh
  # get-some-files
  mt -f /dev/whatever rewind
  mt -f /dev/whatever fsf NNN
  amrestore -p /dev/whatever | restore xbf 2 - "$@"

Note that this mis-handles files with blanks in their name, etc.
If that's a problem, replace with sufficient quantities of Perl.

>-n

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

Re: something of an emergency amrecover question

[Bernhard R. Erdmann]

> > Maybe you can (z)grep your indexfiles for the filenames?
> 
> Hm, I suppose I could, but then how to feed that all into
> amrecover/amrestore?

You could (z)grep the index, feed it into a file and take split(1) to
make chunks of no more than 50 to 200 lines.
It depends on how much command line arguments you can use with restore
or in general. I don't know the exact limit, maybe it's 4 KB for the
environment.

zgrep  "index\.html" > /tmp/files-to-restore
split -l 100 /tmp/files-to-restore
amrestore -p $TAPE host /partition | restore f - x 'cat xaa'
amrestore -p $TAPE host /partition | restore f - x 'cat xab'

Hey, reading restore's (Linux dump-0.4b21) manpage offers an option for
you:

amrestore -p $TAPE host /partition | restore X /tmp/files-to-restore f -

Re: Restore help!

[Bernhard R. Erdmann]

Hi Mark,

I'll put it back to the list, it might be interesting for others, too.

> > Can you amrestore the complete image to disk?
> >
> > amrestore $TAPE host /partition
>
> Yup. I have 2 level 0 amrestore images to disk, one in compressed and the
> other a whopping 10gb file (only 2.43 kernel and reiserfs would handle this).

you can do two other tricks:

- use split(1) to do nice chunks
- use a raw disk device, e.g. /dev/hdd oder /dev/hdd6

amrestore -p $TAPE host /partition | split -b 2000M
cat x* | restore rf -

amrestore -p $TAPE host /partition > /dev/hdd6
restore rf /dev/hdd6

> > Did you try the "v" flag on restore?
> >
> > amrestore -p $TAPE host /partition | restore rvf -
> 
> This is where I'm at now, I'm using restore to get the files out. I'm not
> really familiar dump/restore, but it seems a bit like tar. I can list the
> files with tvf option, but this doesn't seem to be an adaquate test, as
> restore seems to store a table of contents at the beginning of the image
> rather than read thru the whole image like tar tvf will. If this latest
> version of dump/restore doesn't fix the problem, I'm stuck.

Did you already use "C" with restore to compare the dump image on tape
with the disk's content?

amrestore -p $TAPE host /partition | restore Cf -

Well, dump takes a completely different approach to backup than tar. Tar
walks through your directories. Dump unterstands the ext2 filesystem. It
searches for allocated inodes and backs up the data blocks they are
referencing to.

Re: something of an emergency amrecover question

[Nathan J. Mehl]

In the immortal words of Bort, Paul ([EMAIL PROTECTED]):
> You could restore all of the files to a temporary location, then just move
> the files you need...

Oh, sorry, I should have added a bit of context here:

The disk in question is the primary RAID array of my primary
fileserver.  45 GB of data -- it would take hours and hours and hours
to restore, and I'm not even sure I have a partition large enough
anywhere to restore it to. :(

-n

<[EMAIL PROTECTED]>
"He has been known by many names; the Prince of Lies, the Director, Lucifer, 
Belial, and once, at a party, some obnoxious drunk kept calling him 'Dude'."

Re: something of an emergency amrecover question

[Nathan J. Mehl]

In the immortal words of Bernhard R. Erdmann ([EMAIL PROTECTED]):
> > Is there any way in amrecover to recursively add every instance of a
> > filename in a set of directories?  e.g. restore every instance of
> > "index.html" on a given disk of a given host.  "addx
> > /?([^/]+/)*index.html" was my first thought, but addx only appear to
> > apply the regexp to the current working directory, and won't traverse
> > subdirectories.
> 
> Maybe you can (z)grep your indexfiles for the filenames?

Hm, I suppose I could, but then how to feed that all into
amrecover/amrestore?

-n

--<[EMAIL PROTECTED]>
And when love is gone, there's always justice.  And when justice is gone
there's always force.  And when force is gone, threre's always mom.  Hi mom!
 (--Laurie Anderson)
--

Re: Restore help!

[Bernhard R. Erdmann]

> I have recently used amrestore to get an entire level 0 partition/disk
> off of an amanda tape and onto disk on a Redhat Linux box. I'm trying to
> use restore to get  files out of this large amrestore file. When using
> restore on this file, it will read the file, create all the directories
> from the backup, but when it goes to restore the files into the
> directories it just created, I receive a checksum error. My first

I assume you use dump/restore on Linux. What version of dump?

Can you amrestore the complete image to disk?

amrestore $TAPE host /partition

Do you get an error here? That would mean, your drive/tape/whatever
could be bad.

If not, can you restore from that file?

cd /somewhere
restore rf /where/you/dropped/that/file/from/amrestore

Did you try the "v" flag on restore?

amrestore -p $TAPE host /partition | restore rvf -

RE: something of an emergency amrecover question

[Bort, Paul]

You could restore all of the files to a temporary location, then just move
the files you need...

-Original Message-
From: Nathan J. Mehl [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 20, 2001 4:45 PM
To: [EMAIL PROTECTED]
Subject: something of an emergency amrecover question



Okay, if anybody happens to be checking their mail at this hour on a
friday and has a clue, I would be pretty grateful...

Is there any way in amrecover to recursively add every instance of a
filename in a set of directories?  e.g. restore every instance of
"index.html" on a given disk of a given host.  "addx
/?([^/]+/)*index.html" was my first thought, but addx only appear to
apply the regexp to the current working directory, and won't traverse
subdirectories.

If there is no way to do this...may I suggest adding it? :)

-n

<[EMAIL PROTECTED]
g>
 Dear Future Employer: Who's your daddy? Who's your daddy? I think
we know. Thanks! $100,000 a year, I'll be there on monday, please.
 
-chelleMarie
--
--

Re: something of an emergency amrecover question

[Bernhard R. Erdmann]

> Is there any way in amrecover to recursively add every instance of a
> filename in a set of directories?  e.g. restore every instance of
> "index.html" on a given disk of a given host.  "addx
> /?([^/]+/)*index.html" was my first thought, but addx only appear to
> apply the regexp to the current working directory, and won't traverse
> subdirectories.

Maybe you can (z)grep your indexfiles for the filenames?

something of an emergency amrecover question

[Nathan J. Mehl]

Okay, if anybody happens to be checking their mail at this hour on a
friday and has a clue, I would be pretty grateful...

Is there any way in amrecover to recursively add every instance of a
filename in a set of directories?  e.g. restore every instance of
"index.html" on a given disk of a given host.  "addx
/?([^/]+/)*index.html" was my first thought, but addx only appear to
apply the regexp to the current working directory, and won't traverse
subdirectories.

If there is no way to do this...may I suggest adding it? :)

-n

<[EMAIL PROTECTED]>
 Dear Future Employer: Who's your daddy? Who's your daddy? I think
we know. Thanks! $100,000 a year, I'll be there on monday, please.
  -chelleMarie

Re: problem with amanda

[John R. Jackson]

>> If i run amrecover it returns : Error connecting to server: refused
>> connection
>
>Looks like you didn't enable the amidxtaped service.  That's totally
>separate from amandad.

Actually, I think this is the bug that is fixed in 2.4.2p2.

>Alexandre Oliva

>>  Strange. What's the output of the debug files?
>
>I add the files to the message:dump.0 , log..20010419

What's in /tmp/amanda/sendsize*debug?

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

Re: "Cannot do /usr/sbin/vxdump dumps"

[John R. Jackson]

>I am backing up a client which has VX file systems. The tape server has VX ins
>talled. ...

Did it have VX installed when ./configure was run for Amanda?  Does
"amadmin xx version | grep VXDUMP" show anything?  Does it show the
path is /usr/sbin/vxdump?

>Mangala Gunadasa

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

Re: Restore help!

[John R. Jackson]

>I have recently used amrestore to get an entire level 0 partition/disk
>off of an amanda tape and onto disk on a Redhat Linux box. I'm trying to
>use restore to get  files out of this large amrestore file. ...

What version of dump/restore?  Only relatively recent ones are reportedly
worth the trouble of running.

>... when it goes to restore the files into the
>directories it just created, I receive a checksum error. My first
>thoughts is that I had a bad archive. I ran a test by doing a "restore
>tvf ". ...

That's not much of a test.  It does not read the entire image, only the
directory section which is at the beginning (and is not very large).
It shows you the directory structure (e.g. the files you want), but does
not actually get that far into the image to see the file data.

>... I tried a completely
>separate backup and had the exact same results, so unless I have 2 bad
>backups (possible but unlikely), there is something I need to change in
>order to get the files out of this backup file.

My guess is your dump/restore programs are broken.  Time to either
upgrade and hope that fixes it or upgrade and then beg the dump/restore
folks for help.

>Mark Butscher

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

RE: chg-manual "poor man's" changer problems

[Hartmann, O.]

On Thu, 19 Apr 2001, Bort, Paul wrote:

Hello, here I'm again.

Well, the solution for my problem is really simple, but I have had to
read the script first as Paul Bort implied.

FreeBSD's 'mt' command reports in a different way than other OS' mt
and for that, the variable $ONLINEREGEX in the script chg-manual contains
no identifying expression to detect that a tape is 'online'. I added there
a string which is only present if a tape has been sucessfully loaded into
the drive and now, voila, it works fine also for FreeBSD driven UNIX boxes ;-)

Thanks a lot ...

:>(Warning: Stream-Of-Trace)
:>
:>OK, I'm getting closer. The reason that it keeps asking for a tape in the
:>same slot is because it doesn't know what slot it's on. The message:
:>
:> -> loaded <>
:>
:>Should really have a slot number in the <>, but doesn't. The variable $used
:>in chg-manual is empty for unknown reasons.
:>
:>I wish I knew more shell script.
:>
:>OK, it looks like the line before the "loaded" message is the relevant one:
:>
:>used=`$MT $MTF $tape status 2>&1 | tee -a $dbglog | $EGREP "$ONLINEREGEX"`
:>
:>This is placing the status message in the log, but it looks like no status
:>message I've ever seen.
:>
:>My status messages look like this:
:>
:>[amanda@tape configdir]$ mt -f /dev/nst0 status
:>SCSI 2 tape drive:
:>File number=0, block number=1, partition=0.
:>Tape block size 0 bytes. Density code 0x0 (default).
:>Soft error count since last status=0
:>General status bits on (101):
:> ONLINE IM_REP_EN
:>
:>I think that the grep is looking for 'ONLINE' and not finding it in your
:>status message, so it doens't think the tape drive is ready, and asks you to
:>insert a tape.
:>
:>Next steps would be to find out what AMANDA is invoking with $MT, and find
:>out if you have an mt command like mine, and how to bring the two closer
:>together.
:>
:>Sorry this took so long. I'm still learning shell script.
:>
:>
:>-Original Message-
:>From: Hartmann, O. [mailto:[EMAIL PROTECTED]]
:>Sent: Thursday, April 19, 2001 8:55 AM
:>To: Bort, Paul
:>Cc: [EMAIL PROTECTED]
:>Subject: RE: chg-manual "poor man's" changer problems
:>
:>
:>On Wed, 18 Apr 2001, Bort, Paul wrote:
:>
:>
:>Of course, you're right, but this problem is reported by AMANDA. This error
:>seems nasty.
:>
:>All right, I'll try to explain again the configuration and you'll see that
:>many things are clear as a canonical declaration- there must be an small
:>error or a microscopic misconfiguration ... :-(
:>
:>Operating system: FreeBSD 4.3-RC
:>AMANDA:   Amanda 2.4.2p1
:>
:>Tapedrive:HP C1533A 9503 (4GB DDS-2 DAT drive)
:>  The DAT drive is online and accessible!
:>  AMANDA user 'operator' has full access to
:>  the device.
:>  Actually I can read and write normal cpio/pax/tar
:>  from and to this drive as 'operator'.
:>
:>Tape cardridges:  HP and TDK DDS-2 DAT tapes, NOT labeled!
:>
:>Configuration:/etc/inetd.conf is sdet up already, also
:>/etc/services.
:>  Within "operator's" home .amandahosts exists, but it
:>  is not used usually for local administrative
:>operations.
:>  As defined at compiling time /etc/amandates exists
:>and
:>  ist operator-writeable.
:>  A amanda.conf file exists and is clearly read out by
:>  AMANDA. The important configuration tags are:
:>
:>   tpchanger   "chg-manual"
:>   tapedev "/dev/nsa0"
:>   #rawtapedev "/dev/nrsa0"
:>   changerfile
:>"/usr/local/etc/amanda/klima/changer.conf"
:>
:>  The file 'changer.conf' exists, but it is empty. for
:>any tag I put
:>  in there, I get an error by running amcheck so it
:>seems to be
:>  right to leave this file clear, but it must exists
:>due the fact
:>  the driver script 'chg-manual' needs it as the base
:>former for the
:>  following also existent files:
:>
:>  changer.confempty
:>  changer.conf-access 22 (times of access)
:>  changer.conf-clean  1
:>  changer.conf-slot   1 (reflects the slot
:>to use),
:>  changed this
:>temporarily to 0,
:>  doesn't matter ...
:>What I did, do and what the logs are:
:>
:>With the above mentioned configuration I tried to label or check tapes. For
:>instance of
:>labeling, I type exactly
:>
:>  amlabel -f CONFIG_NAME  CONFIG_TAG
:>
:>and gets:
:>
:>  insert tape into slot 0 and press return
:>
:>I hit return, but nothing happened

Linux SCSI utilities

[Jonathan Dill]

Hi folks,

I just found out about these sg_utils which may be helpful for folks
running amanda on Linux systems, especially for debugging tapedrive and
changer problems...

http://gear.torque.net/sg/#Utilities: sg_utils and sg3_utils
-- 
"Jonathan F. Dill" ([EMAIL PROTECTED])
CARB Systems and Network Administrator
Home Page:  http://www.umbi.umd.edu/~dill
Title: The Linux SCSI Generic (sg) Driver







The Linux SCSI Generic (sg) Driver
Introduction
Background
Features
SG device driver downloads
Utilities: sg_utils and
sg3_utils
Sg related pages
External references
SG in Redhat 6.2, 7.0 and
Mandrake 7.1
 

Introduction
The Linux sg driver is a upper level SCSI subsystem device driver that
is used primarily to handle devices _not_ covered by the other upper level
drivers: sd (disks), st (tapes) and sr (CDROMs). The sg driver is used
by scanners, cd writers and applications that read cd audio digitally.
Sg can also be used for less usual tasks performed on disks, tapes and
cdroms. Sg is a character device which, in some contexts, gives it some
advantages over sd and sr which are block devices. The interface of sg
is at the level of SCSI command requests and their associated responses.

Background
The original driver was written by Lawrence Foard in 1992 and remained
unchanged for several years. In August 1998 Heiko Eissfeldt and Joerg Schilling
started working on enhancements to this driver. Soon after, the author
became involved and these efforts culminated in a new sg driver being placed
in Linux kernel 2.2.6 which was released on 16th April 1999. It contains
the first major upgrade to the SCSI generic packet device driver ("sg")
since 1992. This new driver has a super-set of the original interface and
the semantics of the implementation are very similar. Hence it offers a
high degree of backward compatibility with the original driver.
The major reason for introducing a new sg driver into the 2.2 series
of kernels was the problem that the original device driver was having trouble
finding memory. This driver improves the situation by using scatter gather,
memory above the 16 Mbytes level and memory from the scsi dma pool as appropriate.
Other drivers were affected by these memory problems (especially those
associated with ISA hardware). In kernel 2.2.10 H.J. Lu introduced a new
kernel memory allocator that alleviated many of these memory problems.
On 4th January 2001 the Linux 2.4.0 kernel was introduced and it contained
a "version 3" sg driver that is described below.

Features
The following enhancements have been added: scatter gather, command queuing,
per file descriptor sequencing (was per device) and asynchronous notification.
Scatter gather allows large buffers (previously limited to 128 KB on i386)
to be used. Scatter gather is also a lot more "kernel friendly". The original
driver used a single large buffer which made it impossible to run 2 or
more sg-based applications at the same time. With the new driver a buffer
is reserved for each file descriptor guaranteeing that at least that buffer
size will be available for each request on the file descriptor. A user
may request a larger buffer size on any particular request but runs the
(usually remote) risk of an out of memory (ENOMEM) error.
A "version 3" sg driver is now available. It adds a new interface that
allows more control over SCSI commands and returns more information about
their performance. This driver is present in Linux kernel 2.4.0 . A separate
version with reduced capabilities is available for the 2.2 series kernels.
Features include: larger sense buffer, residual DMA count, 16 byte commands,
direct IO support, command duration timing and a "proc_fs" interface. Naturally
it is backward compatible with applications based on the sg interface in
the lk 2.2 series and earlier.

SG device driver downloads
The following table summarizes the different versions of the sg device
driver that are available. If you wish to use one of these tarballs then
untar it in /usr/src/linux (or wherever the top of your kernel tree is).
As a precaution you may wish to copy the files include/scsi/sg.h and drivers/scsi/sg.c
to other names. This will facilitate reversing the patch if required. For
information about the differences between versions see the history section
at the top of the include/scsi/sg.h file.
 


Linux version

Sg driver 
version+tarball

Patch

Notes



 < 2.2.6

sg22orig.tgz

 

found in RH6.0, original
documentation



 

 

 

 



2.2.6 + 2.2.7

sg2131.tgz

pat_sg2134_225.gz

 



2.2.8 + 2.2.9

sg2132.tgz

 

 



2.2.10 - 2.2.13

sg2134.tgz

patch

 



2.2.14 + 2.2.15

sg2136.tgz

patch  on sg version 2.1.34

(for documentation see bullet list)



2.2.16

sg2138.tgz

patch  on sg in lk 2.2.14+15

fixes scatter gather bugs on aha1542



2.2.17 - 2.2.19

sg2139.tgz

patch  on sg in lk 2.2.16

sg2138 broke sym53c416, now fixed



 

 

 

 



optional 2.2 series

sg version  3.0.17

 

sg version 3 backported to lk 2.2



optional 2.4 s

RE: chg-manual "poor man's" changer problems

[Bort, Paul]

If you have time to submit a diff or patch to amanda-hackers that would be
very helpful. 

-Original Message-
From: Hartmann, O. [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 20, 2001 2:09 PM
To: Bort, Paul
Cc: [EMAIL PROTECTED]
Subject: RE: chg-manual "poor man's" changer problems


On Thu, 19 Apr 2001, Bort, Paul wrote:

Hello, here I'm again.

Well, the solution for my problem is really simple, but I have had to
read the script first as Paul Bort implied.

FreeBSD's 'mt' command reports in a different way than other OS' mt
and for that, the variable $ONLINEREGEX in the script chg-manual contains
no identifying expression to detect that a tape is 'online'. I added there
a string which is only present if a tape has been sucessfully loaded into
the drive and now, voila, it works fine also for FreeBSD driven UNIX boxes
;-)

Thanks a lot ...

:>(Warning: Stream-Of-Trace)
:>
:>OK, I'm getting closer. The reason that it keeps asking for a tape in the
:>same slot is because it doesn't know what slot it's on. The message:
:>
:> -> loaded <>
:>
:>Should really have a slot number in the <>, but doesn't. The variable
$used
:>in chg-manual is empty for unknown reasons.
:>
:>I wish I knew more shell script.
:>
:>OK, it looks like the line before the "loaded" message is the relevant
one:
:>
:>used=`$MT $MTF $tape status 2>&1 | tee -a $dbglog | $EGREP "$ONLINEREGEX"`
:>
:>This is placing the status message in the log, but it looks like no status
:>message I've ever seen.
:>
:>My status messages look like this:
:>
:>[amanda@tape configdir]$ mt -f /dev/nst0 status
:>SCSI 2 tape drive:
:>File number=0, block number=1, partition=0.
:>Tape block size 0 bytes. Density code 0x0 (default).
:>Soft error count since last status=0
:>General status bits on (101):
:> ONLINE IM_REP_EN
:>
:>I think that the grep is looking for 'ONLINE' and not finding it in your
:>status message, so it doens't think the tape drive is ready, and asks you
to
:>insert a tape.
:>
:>Next steps would be to find out what AMANDA is invoking with $MT, and find
:>out if you have an mt command like mine, and how to bring the two closer
:>together.
:>
:>Sorry this took so long. I'm still learning shell script.
:>
:>
:>-Original Message-
:>From: Hartmann, O. [mailto:[EMAIL PROTECTED]]
:>Sent: Thursday, April 19, 2001 8:55 AM
:>To: Bort, Paul
:>Cc: [EMAIL PROTECTED]
:>Subject: RE: chg-manual "poor man's" changer problems
:>
:>
:>On Wed, 18 Apr 2001, Bort, Paul wrote:
:>
:>
:>Of course, you're right, but this problem is reported by AMANDA. This
error
:>seems nasty.
:>
:>All right, I'll try to explain again the configuration and you'll see that
:>many things are clear as a canonical declaration- there must be an small
:>error or a microscopic misconfiguration ... :-(
:>
:>Operating system: FreeBSD 4.3-RC
:>AMANDA:   Amanda 2.4.2p1
:>
:>Tapedrive:HP C1533A 9503 (4GB DDS-2 DAT drive)
:>  The DAT drive is online and accessible!
:>  AMANDA user 'operator' has full access to
:>  the device.
:>  Actually I can read and write normal cpio/pax/tar
:>  from and to this drive as 'operator'.
:>
:>Tape cardridges:  HP and TDK DDS-2 DAT tapes, NOT labeled!
:>
:>Configuration:/etc/inetd.conf is sdet up already, also
:>/etc/services.
:>  Within "operator's" home .amandahosts exists, but it
:>  is not used usually for local administrative
:>operations.
:>  As defined at compiling time /etc/amandates exists
:>and
:>  ist operator-writeable.
:>  A amanda.conf file exists and is clearly read out by
:>  AMANDA. The important configuration tags are:
:>
:>   tpchanger   "chg-manual"
:>   tapedev "/dev/nsa0"
:>   #rawtapedev "/dev/nrsa0"
:>   changerfile
:>"/usr/local/etc/amanda/klima/changer.conf"
:>
:>  The file 'changer.conf' exists, but it is empty. for
:>any tag I put
:>  in there, I get an error by running amcheck so it
:>seems to be
:>  right to leave this file clear, but it must exists
:>due the fact
:>  the driver script 'chg-manual' needs it as the base
:>former for the
:>  following also existent files:
:>
:>  changer.confempty
:>  changer.conf-access 22 (times of access)
:>  changer.conf-clean  1
:>  changer.conf-slot   1 (reflects the slot
:>to use),
:>  changed this
:>temporarily to 0,
:>  doesn't matter ...
:>What I did, do and

Restore help!

[Mark Butscher]

I have recently used amrestore to get an entire level 0 partition/disk
off of an amanda tape and onto disk on a Redhat Linux box. I'm trying to
use restore to get  files out of this large amrestore file. When using
restore on this file, it will read the file, create all the directories
from the backup, but when it goes to restore the files into the
directories it just created, I receive a checksum error. My first
thoughts is that I had a bad archive. I ran a test by doing a "restore
tvf ". When I just use restore to list, it can read thru
the entire file and I see everything on the backups, including what I'm
after. As soon as I try to extract the files, I can extract the
directories, but no files...just a checksum error. I tried a completely
separate backup and had the exact same results, so unless I have 2 bad
backups (possible but unlikely), there is something I need to change in
order to get the files out of this backup file.

Any help would be **greatly** appreciated.

Thanks,

--
Mark Butscher
System Administrator
Clarent Corporation
[EMAIL PROTECTED]

Re: Permission denied

[Bernhard R. Erdmann]

> When i run 'amcheck diaria' the result it's:
> 
> [...]
> ERROR: prueba: [could not access /root/pruebas/ (/root/pruebas/):
> Permission denied]
> [...]
> 
> drwxr-xr-x5 root root  /root/pruebas

What are the permissions of /root? Probably 700...

Tandberg SLR100

[Tilmann Holst]

Hi.

I want to use a "Tandberg SLR100" + Amanda + Linux (Debian/potato).
Is anyone out there using a similar setup?

Thanks in advance.

-- 
Tilmann Holst - TUCCO - the universal communication company
http://www.tucco.de, fon: +49-40-65777-510, fax: +49-40-65777-250

changer backup...

[Suen Tak Tsung Daniel]

Hi All,

Just want to check if my understanding is correct:-

I have a HP SureStore 12000E changer tape holding HP-DAT DDS-120 tapes. I
run amanda with mtx and chg-zd-mtx. It seems that the mtx works correctly,
at least, amcheck does not give me errors on the server side.

What I want to do with this config. is to backup a couple of linux
machines. I know that I need several configs, and the simplest is to have
one config per machine. I want to set things up so that one tape will
serve one machine. From what I've read, it seems that amanda checks things
out depending on the labels.

For example, if I want to backup two machines, so I make two set of
configuration files, each with different label patterns in amanda.confs.
My changer has 6 slots, and I insert 6 tapes in them, and label them with
3 tapes matching one set of configuration pattern, and 3 others matching
the other one. So, when I run amanda to do the backup, will amanda figure
out itself which tape to use? So, does this also mean that I have to
amlabel those tapes manually before use?

-Daniel.

Re: "Cannot do /usr/sbin/vxdump dumps"

[Mangala Gunadasa]

I am backing up a client which has VX file systems. The tape server has VX installed. 
When I do amverify on the backed-up file systems, I get the following error message.

"(Reading...Skipped etest._dg1_qa2.20010419.0) Cannot do /usr/sbin/vxdump dumps"  

Can I get help in solving this problem?.

Thank You

Mangala Gunadasa

Re: Ultrium LTO tape drive

[Ron Snyder]

On Thu, Apr 19, 2001 at 05:28:22PM +0200, Ingmar Schrey wrote:
> Have you done (are you doing) backups with different programs
> (Arkeia, taper, tar etc) or other OSes than linux?

No.  Yes.  :)

> If yes, what is your experience about backup speed?

Well, actually I'm fudging a bit. We're currently backing up about
10 hosts (including a netapp filer) using BudTool and a DLT40 juke
box.  We're switching to amanda and the LTO hardware, so it'll be
difficult to get meaningful results out of comparing backup times.

(Sorry if I misunderstood your question.)


> BTW how long did it take for tapetype to check the tape?

Hours.  I started it running late in the afternoon, and it was done
when I came in the next morning.

-ron

Re: Holding disks getting full ..

[Alexandre Oliva]

On Apr 20, 2001, Gerhard den Hollander <[EMAIL PROTECTED]> wrote:

> So it looks like amdump checks if there is enough space on the holding disk
> before it starts dumping,

Yep.

> and then simply continues dumping whitout checking if the holding disk
> becomes full, until it runs in a diskfull error and aborts the dump.

It would fall over to another holding disk, if you had one.

> The right thing (imo) would be to check every time a new chunk is written,
> and if the chunk to be written would fail the holding disk free space
> criteria, it should abort the dump.

And end up aborting the dump anyway?  What's the advantage?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: how do you backup up 5 days to a single tape?

[Yura Pismerov]

Alexandre Oliva wrote:
> 
> On Apr 19, 2001, Patrick Presto <[EMAIL PROTECTED]> wrote:
> 
> > I was hoping I could use the tapes
> > and just append to the last backup taken (somehow??).
> 
> And risk having a bus reset rewind the tape and getting a week's worth
> of backups overwritten?  No way!

Nevertheless it would be nice to have that feature as an option.
Especially considering capacity and price of new media (AIT,LTO, etc.).
Unless this will requere total Amanda re-design.



> 
> > If I did backup five days to the holding disk and then flushed the data to a
> > tape, would I be able to use amrecover to restore data from any of the last
> > 5 days?  Would I have to do anything special to recover?
> 
> I'd hope so, but you may have to position the tape manually for
> amrestore (as called by amrecover) to find the right image in the
> tape.  But I've never tried anything like that (restoring from a
> multi-run flush tape with amrecover, not positioning the tape :-)
> myself.
> 
> --
> Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist*Please* write to mailing lists, not to me

-- 

Yuri Pismerov, TUCOWS.COM INC.  (416) 535-0123  ext. 1352
 S/MIME Cryptographic Signature

Re: Holding disks getting full ..

[Gerhard den Hollander]

* Gerhard den Hollander <[EMAIL PROTECTED]> (Fri, Apr 20, 2001 at 09:54:04AM +0200)
> I've set amanda.conf to use all of the holding disk, minus 1Gb
> 
> holdingdisk hd2 {
> comment "smaller holding disk"
> directory "/eighteen1/amanda/lto"
> use -1Gb
> chunksize 250Mb
> }
> 
> However, I am getting diskfull errors on that disk when amanda is backing
> up .. 
> 
> Now I know there is another job running on that disk, that uses up quite
> some diskspace, but that job stops when the freediskspace is less than 500M
> and continues after that.
> 
> (i checked ;) )
> 
> However, amanda happily continues dumping until the disk is full, thena
> borts the dump, and retries later on.
> 
> Any clue ?

To be slightly more exact.
the sequence of events is:

amdump starts dumping   [disk space 3G ]
[dump is estimated to be 2G]
amdump dumps some parts [disk space 2G ]
other program starts filling the disk, while amanda is dumping
[diskspace is now 500M, other program waits till enough free
diskspace]
amdump continues dumping
disk full ..


So it looks like amdump checks if there is enough space on the holding disk
before it starts dumping,
and then simply continues dumping whitout checking if the holding disk
becomes full, until it runs in a diskfull error and aborts the dump.

The right thing (imo) would be to check every time a new chunk is written,
and if the chunk to be written would fail the holding disk free space
criteria, it should abort the dump.

Thoughts ?

Currently listening to: Gone-JJJ live

Gerhard,  <@jasongeo.com>   == The Acoustic Motorbiker ==   
-- 
   __O  Got no religion, don't need no friends
 =`\<,  Got all I want and I got no need to pretend
(=)/(=) Don't try to reach me, 'cause I'd tear up your mind
I've seen the future and I leave it all behind

Permission denied

[Enrique Rodríguez Lázaro]

Hi.

I have installed amanda 2.4.2p2 on my linux box red hat 6.2 kernel
2.2.16.

When i run 'amcheck diaria' the result it's:

[...]
ERROR: prueba: [could not access /root/pruebas/ (/root/pruebas/):
Permission denied]
[...]

drwxr-xr-x5 root root  /root/pruebas

Have i to permit user 'amanda' specials permissions over /root/pruebas?.
Have i change all permissions over my directories to backup?. I think
no, then ...?

Thanks in advance.

Re: Problem with Amanda and a SLR 50 by Tandberg

[Nicki Messerschmidt]

Tilmann Holst schreibt:
> Ich habe gerade auf der Mailingliste nach Tandberg-Erfahrungen gesucht,
> kann man mit einem Tandberg SLR glücklich werden?

I am still not sure! I had the Tandbarg SLR 50 running for some time without 
any problems and at some time in the past it began to produce errors over 
and over. My last status is that 2 Amanda runs were completed succesfully 
and I hope the next will also. My problem was solved with a
correct tapetype definition produced by the tapetype programm which I 
compiled from the amanda 2.4.2p2 source. I have attached it if your 
interested. 

Cheers
Nicki Messerschmidt 

 --  begin tape type definition for Tandberg SLR 50 --
define tapetype slr50 {
   comment "just produced by tapetype program"
   length 23104 mbytes
   filemark 0 kbytes
   speed 1784 kps
} 

 -- end of tape type definition for Tandberg SLR 50 -- 

Re: how do you backup up 5 days to a single tape?

[Alexandre Oliva]

On Apr 19, 2001, Patrick Presto <[EMAIL PROTECTED]> wrote:

> I was hoping I could use the tapes
> and just append to the last backup taken (somehow??).

And risk having a bus reset rewind the tape and getting a week's worth
of backups overwritten?  No way!

> If I did backup five days to the holding disk and then flushed the data to a
> tape, would I be able to use amrecover to restore data from any of the last
> 5 days?  Would I have to do anything special to recover?

I'd hope so, but you may have to position the tape manually for
amrestore (as called by amrecover) to find the right image in the
tape.  But I've never tried anything like that (restoring from a
multi-run flush tape with amrecover, not positioning the tape :-)
myself.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: how do you backup up 5 days to a single tape?

[Dietmar Goldbeck]

On Thu, Apr 19, 2001 at 02:53:20PM -0600, Patrick Presto wrote:
> Thanks for the Fast reply you rock!
> Is this the only way to do it you think?  I was hoping I could use the tapes
> and just append to the last backup taken (somehow??). I would prefer not to
> use the holding disk if possible.  
> If I did backup five days to the holding disk and then flushed the data to a
> tape, would I be able to use amrecover to restore data from any of the last
> 5 days?  Would I have to do anything special to recover?
> 

Every backup on the tape contains date information. amrestore
has an extra parameter for this case. From man amrestore

   Amrestore   extracts   files  from  the  tape  mounted  on
   tapedevice that match  hostname,  diskname  and  datestamp
   patterns given on the command line.  The tape must be in a
   format written by the amdump or amflush program.
[...]
   Datestamp is useful if you have multiple amflush  runs  on
   the tape.   

So you will be able to recover any daily point in time.  

The main risk involved is a crash of your holding disk. I
_personally_ would get at least 10 tapes and do 2 amflush runs a week.

Ciao
  Dietmar

-- 
 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.

Holding disks getting full ..

[Gerhard den Hollander]

I've set amanda.conf to use all of the holding disk, minus 1Gb

holdingdisk hd2 {
comment "smaller holding disk"
directory "/eighteen1/amanda/lto"
use -1Gb
chunksize 250Mb
}

However, I am getting diskfull errors on that disk when amanda is backing
up .. 

Now I know there is another job running on that disk, that uses up quite
some diskspace, but that job stops when the freediskspace is less than 500M
and continues after that.

(i checked ;) )

However, amanda happily continues dumping until the disk is full, thena
borts the dump, and retries later on.

Any clue ?



Currently listening to: The Tea Party - Live - Egyptian Prayer - Halcyon Days (New 
Years Eve Buffalo)

Gerhard,  <@jasongeo.com>   == The Acoustic Motorbiker ==   
-- 
   __O  If your watch is wound, wound to run, it will
 =`\<,  If your time is due, due to come, it will
(=)/(=) Living this life, is like trying to learn latin
in a chines firedrill

Re: problem with amanda

[Vicente Vives]

Thomas Bahls escribió:

> > When i run amdump it seems it's ok but only runs during 5 seconds.
> -
>  Strange. What's the output of the debug files?
>

I add the files to the message:dump.0 , log..20010419



>
> > I think it's too short to backup 700 Mb.
> > If i run amrecover it returns : Error connecting to server: refused
> > connection
>
> Are you sure you have all the three necessary lines in /etc/inetd.conf &
> sent a SIGHUP to the inetd?
>
> amanda  dgram   udp waitamanda  /opt/amanda/libexec/amandad
> amidxtape stream tcpnowait  root /opt/amanda/libexec/amidxtaped
> amandaidx stream tcpnowait amanda /opt/amanda/libexec/amindexd
>

Amandaidx stream tcp nowait backup /usr/sbin/tcpd
/usr/local/libexec/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd
/usr/local/libexec/amidxtaped
amanda dgram udp wait backup /usr/sbin/tcpd /usr/local/libexec/amandad



>
> Do you have a firewall installed between the server and the clients?
>

No , i don't, but i'm doing a localhost backup.



Thanks for your help.





amdump: start at Thu Apr 19 15:53:08 CEST 2001
planner: pid 891 executable /usr/local/libexec/planner version 2.4.2
planner: build: VERSION="Amanda-2.4.2"
planner:BUILT_DATE="mié abr 11 15:32:50 CEST 2001"
planner:BUILT_MACH="Linux pandora 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i686 
unknown"
planner:CC="gcc"
planner: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
planner:libexecdir="/usr/local/libexec" mandir="/usr/local/man"
planner:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
planner:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/"
planner:RDEV_PREFIX="/dev/" SAMBA_CLIENT="/usr/bin/smbclient"
planner:GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip"
planner:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
planner:listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
planner: defs:  DEFAULT_SERVER="pandora" DEFAULT_CONFIG="DailySet1"
planner:DEFAULT_TAPE_SERVER="pandora"
planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
planner:USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID HAVE_GZIP
planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
READING CONF FILES...
startup took 0.008 secs

SETTING UP FOR ESTIMATES...
setting up estimates for pandora:sda3
pandora:sda3 overdue 11432 days for level 0
setup_estimate: pandora:sda3: command 0, options:
last_level -1 next_level0 -11432 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates took 0.000 secs

GETTING ESTIMATES...
driver: pid 892 executable /usr/local/libexec/driver version 2.4.2
driver: send-cmd time 0.008 to taper: START-TAPER 20010419
driver: started dumper0 pid 896
driver: started dumper1 pid 897
driver: started dumper2 pid 898
driver: started dumper3 pid 899
error result for host pandora disk sda3: missing estimate
getting estimates took 0.074 secs
FAILED QUEUE:
  0: pandorasda3
DONE QUEUE: empty

ANALYZING ESTIMATES...
planner: FAILED pandora sda3 0 [missing result for sda3 in pandora response]
INITIAL SCHEDULE (size 286):

DELAYING DUMPS IF NEEDED, total_size 286, tape length 3993600 mark 111
  delay: Total size now 286.

PROMOTING DUMPS IF NEEDED, total_lev0 0, balanced_size 0...
analysis took 0.000 secs

GENERATING SCHEDULE:


driver: adding holding disk 0 dir /var/backups/holding_disk size 1048576
reserving 1048576 out of 1048576 for degraded-mode dumps
driver: start time 0.050 inparallel 4 bandwidth 2000 diskspace 1048576 dir OBSOLETE 
datestamp 20010419 driver: drain-ends tapeq LFFO big-dumpers 1
taper: pid 895 executable taper version 2.4.2
dumper: pid 896 executable dumper version 2.4.2, using port 836
dumper: pid 897 executable dumper version 2.4.2, using port 837
dumper: pid 898 executable dumper version 2.4.2, using port 838
dumper: pid 899 executable dumper version 2.4.2, using port 839
taper: read label `Cinta1' date `20010419'
taper: wrote label `Cinta1' date `20010419'
driver: result time 0.435 from taper: TAPER-OK
driver: state time 0.436 free kps: 2000 space: 1048576 taper: idle idle-dumpers: 4 
qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle
driver: interface-state time 0.436 if : free 600 if LE0: free 400 if LOCAL: free 1000
driver: hdisk-state time 0.436 hdisk 0: free 1048576 dumpers 0
driver: QUITTING time 0.436 telling children to quit
driver: send-cmd time 0.436 to dumper0: QUIT
driver: send-cmd time 0.436 to dumper1: QUIT
driver: send-cmd time 0.436 to dumper2: QUIT
driver: send-cmd time 0.436 to dumper3: QUIT
driver: send-cmd time 0.436 to taper: QUIT
taper: DONE [idle wait: 0.001 secs]
taper: writing end marker. [Cinta1 OK kb 0 fm 0]
driver: FINISHED time 6.048
amdump: end at Thu Apr 19 15:53:14 CEST 2001


START planner date 20010419
INFO plan

Re: want only full dumps (strategy noinc)

[Alexandre Oliva]

On Apr 18, 2001, Julian R C Briggs <[EMAIL PROTECTED]> wrote:

> How do others archive a set of large filesystems onto a set of small
> tapes?

If filesystems are larger than tapes, telling Amanda to back them up
as individual sub-directories with GNU tar.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: error with amlabel

[Alexandre Oliva]

On Apr 18, 2001, Jason Jin <[EMAIL PROTECTED]> wrote:

> with Amanda 2.4.2.

> rewinding, writing label DailySet1-000
> amlabel: writing endmark: I/O error

IIRC, this is fixed with:

2000-04-09  Alexandre Oliva  <[EMAIL PROTECTED]>
* server-src/amlabel.c (main): Check label *after* writing end mark.

that made it to 2.4.2p2, but not to 2.4.2

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: problem with amanda

[Alexandre Oliva]

On Apr 19, 2001, Vicente Vives <[EMAIL PROTECTED]> wrote:

> I run amcheck and it returns :

No ERRORs nor WARNINGs, that's good.

> If i run amrecover it returns : Error connecting to server: refused
> connection

Looks like you didn't enable the amidxtaped service.  That's totally
separate from amandad.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: compiling --with-db=gdbm

[Alexandre Oliva]

On Apr 19, 2001, Thomas Bahls <[EMAIL PROTECTED]> wrote:

>  could anyone give me a hint what options I do have to use when compiling
> with a database format other than 'text'?

Probably the best option is to change your mind.  Other database
formats only are (or used to be) supported for backward
compatibility.  Don't use them any more.  There will soon be features
that will require the text database.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: Firewall woes

[Alexandre Oliva]

On Apr 19, 2001, Kaley Davis <[EMAIL PROTECTED]> wrote:

> I also recompiled amanda on the amanda server with:

> --with-portrange=850,854 --with-udpportrange=850,854

It's the client that is affected by --with-portrange, and it's always
the server that contacts the client to open the TCP connections.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me