Multiple tape sets possible?

[Jakob Oestergaard]

Hello Amanda People,

I'm running amanda with a five-tape DLT changer, and everything seems to
work just beautifully so far (well, after I spent two hours trying to
label a cleaning tape at least  ;).  However, I do have some questions
regarding how to use the tapes, or how to arrange them in "tape sets".

What I want to achieve:
 If the room with the servers *and* the streamer burns down, I want to
know that I have a full backup (minus the up-to five tapes of incremental
backup that will be lost when the streamer is lost) off site.
 I want daily incremental backups, and weekly full backups. A full backup
can usually be done on one tape. And there are seven days in a week here :)

Currently I'm experimenting with a tape-cycle of 15 tapes. Usually only
one tape is used per day, meaning I will have two full dumps during the
tape cycle.

But I'm uncomfortable with having just one series of tapes knowing that
"somewhere" in this series I have two full dumps.  If I want to move a
full dump off-site, which tapes do I take?  Sure I could look in the
Amanda reports, but I think it's easier to have TapeSet-{1...8}-A and
TapeSet-{1...8}-B tapes,  eg. two separate series of tapes on which I am
absolutely certain that I have a full dump on each set.

But this can't easily be done as far as I can see: If I want to run
differently labeled tapes, it's two different configurations. And I can't
label two tapes with the same name without some hackery.

What is the "right" solution?

Thank you,

  / jakob

Re: Reading Indices

[John R. Jackson]

>> How many lines are in your tapelist file?
>
>   That's exactly what it turned out to be.  ...

Yeah, sorry about that.  I was cleaning up two weeks worth of E-mail
and didn't notice you had already worked out this part of the problem.

>   So, adding them to tapelist got me up to four weeks, but I have
>more tapes than that, and adding them to tapelist does no good; they don't
>show, although there are indices and logfiles.  ...

Are you sure about the logfiles?  That's the other piece of information
Amanda needs.  In particular, do the log files list the correct VSN?

If you don't see the logfiles in "logdir", check for a directory named
"oldlog" and see if they are still laying around in there.

And as I mentioned, I'd use "amadmin  find ..." as a test tool.

>-- Lorrie

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

Re: Reading Indices

[Lorrie Wood]

On Fri, Aug 31, 2001 at 11:21:52PM -0500, John R. Jackson wrote:
> 
> >amrecover> history
> 
> How many lines are in your tapelist file?

That's exactly what it turned out to be. 8-) Not enough lines
in tapelist, because I hadn't set tapespercycle large enough. I wanted
a hundred tape recycling pool, but had only set a small number of tapes
per dump cycle, so that was all Amanda was keeping around.

So, adding them to tapelist got me up to four weeks, but I have
more tapes than that, and adding them to tapelist does no good; they don't
show, although there are indices and logfiles.. Aside from adding them to 
tapelist, is there anything I can do to get amanda to read the indices for 
these older tapes? 

Thanks!

-- Lorrie

RE: Can't start amandad from xinetd on RedHat 7.1

[Mark Holm]

John,

Bastille is a program distributed by www.bastille-linux.org to tighten the
security of Linux. It is now also distributed on the RedHat 7.1 CD's and is
one of the three recommended methods of tightening up a system that sits
outside the firewall on the Internet. If I get a chance, I'll try it again
on another less critical path and let everyone know what the real problem
was. Right now, I need to get this working first as we have exceeded our
ability to use our old system.

markh

-Original Message-
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 01, 2001 7:18 AM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Can't start amandad from xinetd on RedHat 7.1 


>It did end up being something that Bastille did ...

FYI, I don't know what "Bastille" is (not sure I want to), but just get
the general idea from your comments.

>... we finally determined that it had closed down anything that used UDP
>and dgrams.  

Sheesh!  That's kind of excessive.  :-)

More than just Amanda use UDP.  For instance, NFS and DNS.  Are you sure
it was UDP and not some other attribute?

>... 1) I told it not to take strong measures against the BSD r-tools ...

They don't use UDP.

>... 2) Don't add the TMP-DIR scripts ...

Don't know what that means.

I'd be asking the Bastille folks what's up with this.  If you find out
anything else, please post it here.  I'm sure we haven't heard the last
of this.

>One of the
>two of these fixed the problem, but I am not sure which. Given that it
takes
>a couple of hours to rebuild (an that it is working now) I am not sure I
>want to find out right now. 

Understood :-).

>   markh

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

Re: amcheck ok, but amdump fails with missing result...

[John R. Jackson]

>...  The only problem is I can't get it to work...

The output you sent (which was just what was needed to start working on
this, btw -- thanks), all looks perfectly correct, with the one minor
issue that sendsize didn't do anything :-).

Put these two lines:

  OPTIONS maxdumps=4;hostname=raid1;
  GNUTAR /alpha1/top 0 1970:1:1:0:0:0 0

in a temp file, then run sendsize by hand **as the Amanda user** on that
client with the file as standard input.  Let me know what it outputs
both to stdout/stderr and the /tmp/amanda/*.debug file.

>dail

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

Re: Undesired tape usage

[Joshua Baker-LePain]

On Thu, 30 Aug 2001 at 7:52pm, David Galveias wrote

> 1st run (1st week) - full backup using 24 Gb tape
> 2nd run (2nd week) - incremental backup using 2 Gb tape
> 3rd run (3rd week) - incremental backup using 2 Gb tape
> 4th run (4th week) - incremental backup using 2 Gb tape
>
> 1st run (1st week) - full backup using 24 Gb tape
> 2nd run (2nd week) - incremental backup using 2 Gb tape
> 3rd run (3rd week) - incremental backup using 2 Gb tape
> 4th run (4th week) - incremental backup using 2 Gb tape
> ...etc
>
> The problem is that amanda requires to have 1 tape more than the
> runspercycle value, meaning that my tape sets must have 5 tapes (one 24
> Gb tape + four 2 Gb tapes).

No, the documentation for amanda suggests that you have
tapecycle > runspercycle.  This is for your protection.  Here's your
scenario:

week 1 - full backup onto 24GB tape1
week 2 - incremental onto 2 GB tape2
week 3 - incremental onto 2 GB tape3
week 4 - incremental onto 2 GB tape4
week 5 - full backup onto 24GB tape1

Now, consider what happens if, during the week 5 backup onto tape1,
something goes wrong -- the SCSI bus burps, the tape/drive throws an I/O
error, etc, or something else happens *after* the tape has started
writing.  Your full backups are now *gone*, and you have little/no chance
of doing a full restore.

What you should have at a minimum is a tapecycle of 5, with 2 of those
tapes (tape1 and tape5) being 24GB tapes.

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

Re: Solaris 8 Server hangs during backup

[Gerhard den Hollander]

* Eva Freer <[EMAIL PROTECTED]> (Mon, Aug 13, 2001 at 11:52:48AM -0400)
> Amanda Users:
> 
> We have a highly subnetted configuration of Solaris 8 and 2.6 boxes, mostly
> E220R's. The subnets are connected via firewalls. Each subnet has its own
> Amanda server with an Exabyte Mammoth tape drive. We use hardware
> compression only. The Amanda is 2.4.2p1 on most nodes.
[snip]

The usual concerns apply:
1) did you check the scsi chains on all machines to ensure proper
   termination, proper cables &c &c 
2)  What is in the syslog on the hanging machine
3) You say the machine gets slower and slower (which means it's
   progressive).
   Did you try running top (or similar) on the machine to see what was
   happening (e.g. was the machine running out of memory ? out of swap
   space ?)
   Was there anything special in the /tmp/amanda logfiles ?
   [you will have to make sure /tmp/amanda is not mounted on tmpfs
4) Are you using software compression ?

> but the problem persists. Messages in the logs (not from amanda) indicate
> that the system is very busy (e.g. sendmail won't run the queue because the
> load average is too high.) Amanda is the only thing really happening other
> than the usual OS stuff.

Could you run top/ps -ef or whatever to see what exactly is runnig, and
what is hogging the CPU ?
Are you using ufsdump or tar dump ?

Kind regards,
 --
Gerhard den Hollander   Phone +31-10.280.1515
Global Technical SupportFax   +31-10.280.1511 
Jason Geosystems BV (When calling please note: we are in GMT+1)

[EMAIL PROTECTED]  POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam  
JASON...#1 in Reservoir CharacterizationThe Netherlands

  This e-mail and any attachment is/are intended solely for the named
  addressee(s) and may contain information that is confidential and privileged.
   If you are not the intended recipient, we request that you do not
 disseminate, forward, distribute or copy this e-mail message.
  If you have received this e-mail message in error, please notify us
   immediately by telephone and destroy the original message.

Re: amrecover

[Gerhard den Hollander]

* Brandon Amundson <[EMAIL PROTECTED]> (Fri, Aug 17, 2001 at 02:58:11PM -0400)
> First I want to say thanks to all of you who respond to email like mine.
> 
> I am trying to test amrecover.  when I run amrecover daily, I get the
> following error.
> 
> AMRECOVER Version 2.4.2p2. Contacting server on mail.daml.org ...
> amrecover: Unexpected server end of file

I've had that happen once ..
what happened was the compressed index files get expanded to /var/tmp (or
somewhere like that) to get sorted
(I think amrecover does a zcat indexfile.gz | sort | something else)
and /var/tmp does not have enough space for this.
I hacked around that problem by making sort always sort to /tmp iso
/var/tmp (sort is a shell script that does
exec /bin/sort.exe  -T /tmp/ "$@"
)
Note, this most be done on the index host, not on the client

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

amcheck ok, but amdump fails with missing result...

[Dail Rowe]

Hi Everyone,

I have been using amanda to do backups to a tape drive for a while,
but we recently decided to start doing backups to a RAID system.
I downloaded amanda-242-tapeio from sourceforge, and the compile
and install went fine.  The only problem is I can't get it to work...
Sorry for the length of this message, but I am guessing that the best
way to get help is to provide as much (possibly) relevant info as possible.
Since I think the most likely source of error is my configuration, I am
including the config files at the top.  After that are various output from
amanda software.  Thanks in advance for any help...

dail


amanda.conf

org "test"
mailto "amanda"
dumpcycle 21 days
runspercycle 3
tapecycle 4 tapes
dumpuser "amanda"
netusage  1000 Kbps
labelstr "^test_[0-9]*$"
tapedev "file:/raid/backup"
tapetype RAID-FILE
infofile "/usr/local/etc/amanda/test/info"
logdir   "/usr/local/etc/amanda/test/log"
indexdir "/usr/local/etc/amanda/test/index"
maxdumps 4

holdingdisk hd1 {
  comment "main holding disk"
  directory "/home/amanda/backup"
  use 6 Gb
  chunksize 2 GB
}

define dumptype global {
  compress client fast
  dumpcycle 1 week
  maxdumps 4
  index on
}

define dumptype remote {
  global
  program "GNUTAR"
}

define tapetype RAID-FILE {
  comment "File on the raid disk"
  length 4 mbytes
  filemark 0 kbytes
}

define interface local {
comment "local disk"
use 1000 kbps
}

define interface eth0 {
comment "10 Mbps ethernet"
use 400 kbps
}

=

disklist:

raid1 /alpha1/top remote eth0

=

amcheck reports:

[amanda@raid1 test]$ /usr/local/sbin/amcheck test
Amanda Tape Server Host Check
-
Holding disk /home/amanda/backup: 17427732 KB disk space available, that's plenty
NOTE: skipping tape-writable test
Tape test_0 label ok
WARNING: info file /usr/local/etc/amanda/test/info/raid1/_alpha1_top/info: does not 
exist
Server check took 0.002 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.023 seconds, 0 problems found

(brought to you by Amanda 2.4.2p2-tapeio)
[amanda@raid1 test]$

=

I assume that the warning is not meaningful???  When I do

[amanda@raid1 test]$ /usr/local/sbin/amdump test

it returns in a couple of seconds, and the mail report is:

Date: Sat, 1 Sep 2001 11:22:05 -0400
From: Amanda Backup User <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: test AMANDA MAIL REPORT FOR September 1, 2001

These dumps were to tape test_0.
The next tape Amanda expects to use is: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
  raid1  /alpha1/top lev 0 FAILED [missing result for /alpha1/top in raid1 
response]


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00   0:00   0:00
Output Size (meg)   0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0  0  0
Avg Dump Rate (k/s) -- -- --

Tape Time (hrs:min)0:00   0:00   0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)   0.00.00.0
Filesystems Taped 0  0  0
Avg Tp Write Rate (k/s) -- -- --

?
NOTES:
  planner: Adding new disk raid1:/alpha1/top.
  driver: WARNING: got empty schedule from planner
  taper: tape test_0 kb 0 fm 0 [OK]

?
DUMP SUMMARY:
 DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-- - 
raid1/alpha1/top 0 FAILED ---

(brought to you by Amanda version 2.4.2p2-tapeio)

=

Although the various files in /tmp/amanda don't show any errors that are obvious to
me, I included them below in the hopes that more experienced eyes will detect the
problem:

amandad.20010901121415.debug:

amandad: debug 1 pid 2885 ruid 505 euid 505 start time Sat Sep  1 12:14:15 2001
amandad: version 2.4.2p2-tapeio
amandad: build: VERSION="Amanda-2.4.2p2-tapeio"
amandad:BUILT_DATE="Fri Aug 31 08:44:31 EDT 2001"
amandad:BUILT_MACH="Linux raid1 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 
unknown"
amandad:CC="gcc"
amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"

Re: amrecover trouble

[Chris Pascoe]

Hi John,

> amrecover -C /Inside/ -s backup.x.net -t backup.x.net -d /dev/nst0
... leads to...
> amrecover: Unexpected server end of file

This sounds like you have the "wait" flag set to "yes" for the amandaidx
service in /etc/xinetd.d/amandaidx.  Try changing it to "no".  (Or, if
your box uses normal inetd, make sure it's set to nowait in
/etc/inetd.conf).

Chris

Re: Can't start amandad from xinetd on RedHat 7.1

[John R. Jackson]

>It did end up being something that Bastille did ...

FYI, I don't know what "Bastille" is (not sure I want to), but just get
the general idea from your comments.

>... we finally determined that it had closed down anything that used UDP
>and dgrams.  

Sheesh!  That's kind of excessive.  :-)

More than just Amanda use UDP.  For instance, NFS and DNS.  Are you sure
it was UDP and not some other attribute?

>... 1) I told it not to take strong measures against the BSD r-tools ...

They don't use UDP.

>... 2) Don't add the TMP-DIR scripts ...

Don't know what that means.

I'd be asking the Bastille folks what's up with this.  If you find out
anything else, please post it here.  I'm sure we haven't heard the last
of this.

>One of the
>two of these fixed the problem, but I am not sure which. Given that it takes
>a couple of hours to rebuild (an that it is working now) I am not sure I
>want to find out right now. 

Understood :-).

>   markh

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

Undesired tape usage

[David Galveias]

Hi there.
Here's my situation:
I have sets of 4 tapes (one 24 Gb tape + three 2 Gb tapes) to backup my machines.
I'll have 4 runs per cycle corresponding to the 4 weeks of the month, meaning that i 
want to have:

1st run (1st week) - full backup using 24 Gb tape
2nd run (2nd week) - incremental backup using 2 Gb tape
3rd run (3rd week) - incremental backup using 2 Gb tape
4th run (4th week) - incremental backup using 2 Gb tape

1st run (1st week) - full backup using 24 Gb tape
2nd run (2nd week) - incremental backup using 2 Gb tape
3rd run (3rd week) - incremental backup using 2 Gb tape
4th run (4th week) - incremental backup using 2 Gb tape
...etc

The problem is that amanda requires to have 1 tape more than the runspercycle value, 
meaning that my tape sets must have 5 tapes (one 24 Gb tape + four 2 Gb tapes).
This way, when it reachs the end of the month, when Amanda is going to do a full 
backup, it will ask for the 5th tape, that i don't want to use for full backups due to 
space constraints.
And finally my question is : How can i tell Amanda to use the 1st tape of the set for 
full backups? (in an automatic way, since i know i can do this using amadmin)

Thanks for your attention

Host down selfcheck error -- new cause for the problem (with solution...)

[John W. Price]

Hi all:

I just added a new client to my amanda setup, and ran amcheck to make
sure it was working.  It didn't.  Instead, I got the following:

=
> amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk {dumpdisk}: {size} disk space available, using {othersize}
NOTE: skipping tape-writable test
Tape DailySet1-10 label ok
Server check took 7.676 seconds

Amanda Backup Client Hosts Check

WARNING: {newclient}: selfcheck request timed out.  Host down?
Client check: 3 hosts checked in 30.072 seconds, 1 problem found

(brought to you by Amanda 2.4.2p2)
>
=

I went through the FAQ list, and didn't find anything useful, until I
hit John Jackson's post at
.  The very last
thing he suggests is to run amandad on the client node as the amanda
user, and watch what happens.  Well, I got the following:

=
> /usr/local/libexec/amandad
ld.so.1: /usr/local/libexec/amandad: fatal: libreadline.so.4: open
failed: No such file or directory
Killed
>
=

Then I remembered: in my setup, the client host NFS mounts /usr/local
from the tape host.  That's how it gets the amanda binaries.  However,
/lib (where the readline library) is *not* NFS mounted, so that library
isn't available.

I copied it over, and now everything appears happy.  FYI.

John

troubleshooting

[brian]

i have been having some trouble with my tape drive.. and in turn, trouble
with amanda.  what are some simple things i can do to test out my tape
drive?  any time i try and write to a tape amanda says that there is no
tape or that its at the end of the tape.

ive got a sony ait-1 drive on a machine running linux.

thanks
brian

Dump failures

[Frank Bertrand]

If anyone can give me a clue as to what is going on, it would be greatly appreciated.

Help 1:


I have a Linux box running RedHat 7.1;

Linux sxgate 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686 unknown

FilesystemSize  Used Avail Use% Mounted on
/dev/sda5  13G  3.2G  9.5G  25% /
/dev/sda1 517M  7.8M  483M   2% /boot
/dev/md0   33G  3.5G   28G  11% /home (Software striped (Raid5) across 3 
drives)

When I start my dumps with all 3 filesystems, only one will start, the other two will 
fail.
(Not always the same one starts)

amanda.debug:
=

Amanda 2.4 REQ HANDLE 000-10010148 SEQ 999202365
SECURITY USER root
SERVICE sendbackup
OPTIONS hostname=sxgate;
DUMP /boot 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;


sending ack:

Amanda 2.4 ACK HANDLE 000-10010148 SEQ 999202365


bsd security: remote host sumire.hstc.necsyl.com user root local user amanda
amandahosts security check passed
amandad: running service "/usr/lib/amanda/sendbackup"
amandad: got packet:

Amanda 2.4 REQ HANDLE 000-10010398 SEQ 999202365
SECURITY USER root
SERVICE sendbackup
OPTIONS hostname=sxgate;
DUMP / 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;


amandad: received other packet, NAKing it
  addr: peer 198.170.2.24 dup 198.170.2.24, port: peer 567 dup 519
sending nack:

Amanda 2.4 NAK HANDLE 000-10010398 SEQ 999202365
ERROR amandad busy


amandad: got packet:

Amanda 2.4 REQ HANDLE 000-10010148 SEQ 999202365
SECURITY USER root
SERVICE sendbackup
OPTIONS hostname=sxgate;
DUMP /home 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;


amandad: received other packet, NAKing it
  addr: peer 198.170.2.24 dup 198.170.2.24, port: peer 567 dup 574
sending nack:

Amanda 2.4 NAK HANDLE 000-10010148 SEQ 999202365
ERROR amandad busy


amdump:
===
amdump: start at Thu Aug 30 15:12:45 CDT 2001
got result for host sxgate disk /home: 0 -> 3621366K, -1 -> -1K, -1 -> -1K
got result for host sxgate disk /boot: 0 -> 7954K, -1 -> -1K, -1 -> -1K
got result for host sxgate disk /: 0 -> 3251847K, -1 -> -1K, -1 -> -1K
getting estimates took 15.440 secs

GENERATING SCHEDULE:

sxgate /home 9 0 1970:1:1:0:0:0 3621366 2150
sxgate / 7 0 1970:1:1:0:0:0 3251847 108394
sxgate /boot 7 0 1970:1:1:0:0:0 7954 1

driver: send-cmd time 15.488 to dumper0: FILE-DUMP 00-1 
/amanda/118/20010830/sxgate._boot.0 sxgate /boot 0 1970:1:1:0:0:0 DUMP |;bsd-auth;
driver: send-cmd time 15.488 to dumper1: FILE-DUMP 01-2 
/amanda/118/20010830/sxgate._home.0 sxgate /home 0 1970:1:1:0:0:0 DUMP |;bsd-auth;
driver: send-cmd time 15.488 to dumper2: FILE-DUMP 02-3 
/amanda/118/20010830/sxgate._.0 sxgate / 0 1970:1:1:0:0:0 DUMP |;bsd-auth;
driver: result time 15.502 from dumper2: FAILED 02-3 amandad busy
driver: result time 15.504 from dumper1: FAILED 01-2 amandad busy


Help 2:

When I run only the dump for the filesystem that is striped, the dump does dump across 
the network to the
holding disk, but will stop after a while, wait for the timeout period, then fail.

Any ideas, is it because of the striping?

Again, any suggestion will be appreciated.

Thanks.

-
***
Frank Bertrand | Phone:  281/465-1503
NEC Systems, Inc.  | Fax:281/465-1599
4200 Research Forest Drive | E-mail: [EMAIL PROTECTED]
The Woodlands, TX 77381| URL: http://www.necservers.com
***

Re: regenerating an amanda report

[Gene Heskett]

Gene Heskett sends Greetings to Joshua Baker-LePain;

 JB> On Wed, 15 Aug 2001 at 3:51pm, Joshua Baker-LePain wrote

 JB> Yeah, I did write that on Aug 15.  And I *didn't* send it out
 JB> again...

Yeah, I have a regular rash of old messages this morning.  ???

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

Avoiding zero size dumps

[Robert Minsk]

Why is amanda dumping the following directory at level 1 when the estimate
returns 0K?

setting up estimates for millennium:/shows/vsky/mn/mn065
setup_estimate: millennium:/shows/vsky/mn/mn065: command 0, options:
last_level 0 next_level0 6 level_days 0
getting estimates 0 (20) 1 (0) -1 (-1)

got result for host millennium disk /shows/vsky/mn/mn065: 0 -> 20K, 1 -> 0K, -1
-> -1K

pondering millennium:/shows/vsky/mn/mn065... next_level0 6 last_level 0 (not due
for a full dump, picking an incr level)
   picklev: last night 0, so tonight level 1
  curr level 1 size 0 total size 180917330 total_lev0 67193330 balanced-lev0size
52566208

millennium /shows/vsky/mn/mn065 pri 1 lev 1 size 0

millennium /shows/vsky/mn/mn065 1 1 2001:8:28:9:33:46 0 0

Is there anyway to configure amanda to avoid zero size dumps?  On our tape
drive it takes about 45 seconds to dump a zero size disk.  We have about
316 of these empty filesystems giving about 4 hours of empty backups.

--
Robert MinskCentropolis Effects, LLC.
[EMAIL PROTECTED]10950 Washington Blvd., Studio B
Culver City, Ca. 90232-4025

Re: Getting a TOC from an existing tape?

[Joshua Baker-LePain]

On Thu, 30 Aug 2001 at 10:40am, Paul Lussier wrote

> I just checked the FAQ-O-Matic and docs/, but couldn't find this answer.
> (btw, looks like that fom needs some clean-up, there are a bunch of
>  empty "New Item" items in there).
>
> I have a tape, and want to find out what's on it directly from
> the tape.  I know I've seen this answered some where before, but
> can't seem to remember wherer.
>
amrestore /dev/nst0 no-such-host

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

amrecover trouble

[John Holstein, IS]

Unix Linux

Trying a "test" of amrecover.

using the command:
amrecover -C /Inside/ -s backup.x.net -t backup.x.net -d /dev/nst0

I am getting:

amrecover: Unexpected server end of file

Ok, that's fine, I think it's because I am not running a DNS server inside 
the firewall and the 10.0.0.x IP's are not returning a proper reverse 
lookup. I can handle that, or if you have a particular suggestion go ahead 
and shoot. BTW: the box is listed in /etc/hosts

Anyway, the *other* problem, when the error above is given, the very next 
time I try amrecover, I get this:

amrecover: Error connecting to server: Connection refused

I check the backup box for amandaid to be running, as it was before the 
trial amrecover and it's missing from a netstat -ap

Any known reason for amandaid to crash because of the bad DNS problem?


John Holstein
CN IS

Re: amverify, can't do tar dumps

[bhlewis]

[EMAIL PROTECTED] said:
> Was tar-1.13.17 a known troublemaker?  In other words, are the backups
> currently on hand, made by tar-1.13.17 all trashed?

Yes it's a known troublemaker, and your backups may well be trashed.

1.13.17 created bad Amanda index files, so amrestore won't work correctly. I
don't know if that's just the symptom that's easiest to see or if bad index
files are the extent of the problem.  I suspect there's more, and -.17
creates tar files with bogus pathnames.  

Anyway, schedule level 0 dumps on your office machine tonight!

-Ben

-- 
Benjamin LewisThank goodness modern convenience is a 
Database Analyst/Programmer  thing of the remote future.
Purdue University Computing Center  -- Pogo, by Walt Kelly
[EMAIL PROTECTED] 

Re: Getting a TOC from an existing tape?

[Mitch Collinsworth]

On Thu, 30 Aug 2001, Paul Lussier wrote:

> I just checked the FAQ-O-Matic and docs/, but couldn't find this answer.
> (btw, looks like that fom needs some clean-up, there are a bunch of
>  empty "New Item" items in there).
 
Yes, it's getting to be a bit of a mess.


> I have a tape, and want to find out what's on it directly from
> the tape.  I know I've seen this answered some where before, but
> can't seem to remember wherer.

If my somewhat fuzzy memory serves, the trick is to run amrestore and
specify a phoney host/disk name combination.  Then it will scan the
tape looking for the filesystem you asked for, printing out those it
does find along the way.  Since the phoney fs won't be found it will
scan all the way to the end of the tape, and voila, you have a tape
listing.

I suppose some enterprising soul could turn this into a real command,
or command option.  It probably hasn't been done because it works well
enough to satisfy most folks like this.  The big problem with this is
only that it continues to be a FAQ due to its general obscurity.

-Mitch

Getting a TOC from an existing tape?

[Paul Lussier]

Hi all,

I just checked the FAQ-O-Matic and docs/, but couldn't find this answer.
(btw, looks like that fom needs some clean-up, there are a bunch of
 empty "New Item" items in there).

I have a tape, and want to find out what's on it directly from
the tape.  I know I've seen this answered some where before, but
can't seem to remember wherer.

Thanks,


-- 

Seeya,
Paul

...we don't need to be perfect to be the best around,
and we never stop trying to be better. 
   Tom Clancy, The Bear and The Dragon

 If you're not having fun, you're not doing it right!

Re: Looking for info on freebsd and an HP DAT24x6i changer.

[Douglas K. Rand]

grubble> [...] I'm desperately trying to figure out why I can't get an
grubble> HP Surestore 24x6i changer to work with freebsd.  I've
grubble> exhausted all of my resources and mailing lists to no avail,
grubble> so I'm resorting to emailing you because of this message I
grubble> found in the amanda-users archive.

Perhaps the problem you are having is that that particular changer
reports having 0 pickers, which pisses off chg-chio. I have a really
ugly fix:

--- chg-chio.orig   Thu Aug 30 21:52:45 2001
+++ chg-chioWed Aug 15 20:23:55 2001
@@ -232,10 +232,10 @@
 
}
close(FH);
-   if ( $max_drive == 0 or $max_picker == 0 ) {
-   print "$progname: No drive or picker ? ($max_drive/$max_picker)\n";
-   exit(2);
-   }
+#  if ( $max_drive == 0 or $max_picker == 0 ) {
+#  print "$progname: No drive or picker ? ($max_drive/$max_picker)\n";
+#  exit(2);
+#  }
 
print LOG &do_time(), ": leave: getTapeParams: $max_slot, $max_drive, 
$max_picker\n";
return ($max_slot, $max_drive, $max_picker);

Which just comments out the error checking for no pickers.

But if you are having other problems, let me know.

Oh, I added amanda-users to the CC so others can chime in too.

Re: dump to tape failed

[wanadoo]

Mitch Collinsworth ha escrito:

> On Tue, 28 Aug 2001, wanadoo wrote:
>
> > driver: result time 3.503 from dumper0: FAILED 01-2 [taper port
> > open: Resource temporarily
> > unavailable]
> > driver: result time 123.497 from taper: TAPE-ERROR 00-1 [port
> > connect timeout]
>
> It sounds like another process already has the port that taper
> wants to use, hence it's failing when trying to open it.  By any
> chance is there an old taper process still running from a previous
> amanda run?
>
> -Mitch

I have restarted the server and I have run amdump again. But the result
is the same. Do you know how I can find a process if it has the port?
Thanks,

Mercedes.

Re: Backing up a system twice, simultaneously ?

[Paul Lussier]

In a message dated: Wed, 22 Aug 2001 17:39:54 CDT
"Marc W. Mengel" said:

>I have a script that will rsh over to some list of nodes and make a
>disklist, and one to check your disklist and tell you if new filesystems
>have appeared, and suggest a new disklist.   I can post them if
>anyone's interested.

Hmmm, that might be quite useful.  I'd like to take a look at it if 
you wouldn't mind posting it.

Thanks,
-- 

Seeya,
Paul

...we don't need to be perfect to be the best around,
and we never stop trying to be better. 
   Tom Clancy, The Bear and The Dragon

 If you're not having fun, you're not doing it right!