Re: Incremental and Full backups

[Chris Dahn]

  While we're on the topic, I have a theoretical question. We too are going 
to be splitting our backups in a very non-amanda way. The reason for us is 
that our incrementals tend to be small, so it's a waste of money for a small 
research group to do incrementals to the 100GB SDLT tape. Instead, 
incrementals (any day now) will be going to a 4GB DDS2 drive. 

  My question is, when for some reason amanda decides that a full backup 
needs to be done instead of an incremental, or when the incremental simply 
overflows the 4GB tape, what happens? Is there a way to tell amanda to dump 
the files to the SDLT drive instead? I would think I could just change the 
config file and amflush it. Or, should I just keep popping in DDS2 tapes 
until the incremental/untimely full backup finishes?

-- 

Chris Dahn, SERG Code Ninja
  3141 Chestnut St.
  Attn: MCS Department
  Philadephia, PA  19104
  Office: 215.895.0203
  Fax: 215.895.1582

<->Software Engineering Research Group<->
Feel the SERG!
http://serg.mcs.drexel.edu/
CAT 186, The Microwave
http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahn&op=index

Re: SCSI tape error with FreeBSD

[John Merryweather Cooper]

On Mon, 2002-04-01 at 19:01, Kirk Strauser wrote:
> 
> At 2002-04-02T01:46:18Z, Doug Silver <[EMAIL PROTECTED]> writes:
> 
> > So for the non-rewinding tape device I put in /dev/nsa0, which seems to
> > make sense after reading the mt and sa man pages (I know, I shouldn't be
> > RTFM'ing before hand, but oh well ;).  I've tried both /dev/nsa0 and
> > /dev/nrsa0 -- both failed!
> 
> Actually, you'll want /dev/nrsa0.  Otherwise, your tape will rewind between
> dumps, which is a Bad Thing.

>From the man page for sa, nsa0 would be the no-rewind device.  Adding
the "r" causes access to sa0 to be "raw."

> 
> > # dump 0f /dev/nsa0 /etc
> >   DUMP: Date of this level 0 dump: Mon Apr  1 17:27:47 2002
> >   DUMP: Date of last level 0 dump: the epoch
> >   DUMP: Dumping /etc to /dev/nsa0
> >   DUMP: bad sblock magic number
> >   DUMP: The ENTIRE dump is aborted.
> > 
> > Any suggestions?
> 
> I've seen similar errors with subtly corrupted filesystems.  Try fsck'ing
> the /etc volume and trying again.  Note: I'm using FreeBSD 4.5-STABLE on my
> workstation, and I've had (within the week) filesystems with corruptions
> that caused dump to abort but that had no other apparent problems.
> -- 
> Kirk Strauser
-- 
 _
  | |V| / '   ||  MacroHard --   \
\_| | | \_,   || the perfection of form over |
--|| substance, marketing over   |
Web:  http://www.borgsdemons.com  || performance, and greed over |
AIM:  johnmcooper || design . . .|
=/
Public Key:  http://www.borgsdemons.com/Personal/pgpkey.asc  |
=\

Re: Problem sending mail

[John R. Jackson]

>I would think that I could find the simple thing I need to change in 
>order to get sendmail to replace none but I can't find it.  any help 
>would be greatly appricated.

You need a program that understands "-s ".  ./configure looks
for Mail, mailx and mail in your PATH.  It apparently didn't find any
of those.

Get whichever one is appropriate in your PATH, then "make distclean"
and start over with ./configure, or else set MAILER on the command line:

  ./configure MAILER=/path/to/your/mail/program ...

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

Re: V17 EOT

[John R. Jackson]

>DELAYING DUMPS IF NEEDED, total_size 46743613, tape length 3584 mark 1931
>  delay: Dump too big for tape: ...
>  delay: Total size now 35786141.

So planner did the right thing, reducing the total estimated dump size
down below your tape size.

>Does this give any idea why it hits EOT?

Nope.  Now you'll have to go through the rest of the amdump.1 file and
find out which file system lied and dumped a lot more than the estimate
said it would.

Look at the GENERATING SCHEDULE section.  The number after the first
datestamp (the one with colons, e.g. 1970:1:1:0:0:0) is the estimated
size.  Then look for the "from taper: DONE" lines and the "kb " value.

Here's an example:

  DUMP HHH AAA 20020401 1 0 1970:1:1:0:0:0 11772 11
  DUMP HHH BBB 20020401 1 0 1970:1:1:0:0:0 1092 5

This say disk AAA on host HHH is expected to need 11772 KBytes and disk
BBB is expected to need 1092 KBytes.  Later ...

  driver: result time 11.986 from taper: DONE ... kb 1120 ...
  driver: result time 32.317 from taper: DONE ... kb 11776 ...

Pretty close (1120 vs. 1092 and 11776 vs. 11772).  The taper lines
include some rounding to 32 KByte boundaries and I think the header is
in one of these but not the other.

>Dick

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

Re: SCSI tape error with FreeBSD

[John R. Jackson]

>(sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
>command to clear this state.

I seem to recall hearing this before.  Try searching the mailing list
archive.

># dump 0f /dev/nsa0 /etc
>...
>  DUMP: bad sblock magic number
>  DUMP: The ENTIRE dump is aborted.

U, is /etc a file system?  If not, you can't do this.  Dump (in
general, and apparently for sure with your version) only works for file
systems, not directories.

>Doug Silver

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

Re: SCSI tape error with FreeBSD

[Kirk Strauser]

At 2002-04-02T01:46:18Z, Doug Silver <[EMAIL PROTECTED]> writes:

> So for the non-rewinding tape device I put in /dev/nsa0, which seems to
> make sense after reading the mt and sa man pages (I know, I shouldn't be
> RTFM'ing before hand, but oh well ;).  I've tried both /dev/nsa0 and
> /dev/nrsa0 -- both failed!

Actually, you'll want /dev/nrsa0.  Otherwise, your tape will rewind between
dumps, which is a Bad Thing.

> # dump 0f /dev/nsa0 /etc
>   DUMP: Date of this level 0 dump: Mon Apr  1 17:27:47 2002
>   DUMP: Date of last level 0 dump: the epoch
>   DUMP: Dumping /etc to /dev/nsa0
>   DUMP: bad sblock magic number
>   DUMP: The ENTIRE dump is aborted.
> 
> Any suggestions?

I've seen similar errors with subtly corrupted filesystems.  Try fsck'ing
the /etc volume and trying again.  Note: I'm using FreeBSD 4.5-STABLE on my
workstation, and I've had (within the week) filesystems with corruptions
that caused dump to abort but that had no other apparent problems.
-- 
Kirk Strauser

Problem sending mail

[John Rosendahl]

I have amanda (2.4.3b2) running for the most part but it will not send 
me a report
When I run amreport I get the following message
 sh: NONE: command not found
amreport: mail command failed: NONE -s "MEC Denver AMANDA MAIL REPORT 
FOR March 28, 2002" [EMAIL PROTECTED]

I would think that I could find the simple thing I need to change in 
order to get sendmail to replace none but I can't find it.  any help 
would be greatly appricated.

WANTED: DDS-3 tape drive

[John Koenig]

Anyone have a DDS-3 (4mm, 12 GB native) unit that has been removed 
from service? I am looking for a unit that is considered obsolete by 
the current owner; which I hope would make it nearly worthless and 
therefore quite inexpensive to procure from "you"...  :)

Thank you...

Re: V17 EOT

[rwk]

> >I can't seem to find the file you are referring to...
> 
> It's in `amgetconf  logdir` (sorry, I forget that because that's
> the same as my amanda.conf directory).

It's in /var/lib/amanda/Daily/amdump.3:

DELAYING DUMPS IF NEEDED, total_size 46743613, tape length 3584 mark 1931
  delay: Dump too big for tape: full dump of binar.americom.com:/home delayed.  Now at 
level 1.
  delay: Dump too big for tape: full dump of binar.americom.com:/usr delayed.  Now at 
level 1.
  delay: Dump too big for tape: full dump of vulcan.internal.americom.com:/var 
delayed.  Now at level 2.
  delay: Dump too big for tape: full dump of solo.americom.com:/ideroot delayed.  Now 
at level 2.
  delay: Dump too big for tape: full dump of solo.americom.com:/ delayed.  Now at 
level 3.
  delay: Dump too big for tape: full dump of wookie.internal.americom.com:/usr 
delayed.  Now at level 1.
  delay: Dump too big for tape: full dump of solo.americom.com:/bigger delayed.  Now 
at level 2.
  delay: Total size now 35786141.

Does this give any idea why it hits EOT?

Dick

P.S.

In case you don't recall, I keep hitting EOT despite having tapetype length
set to 35000 mbytes.  The V17 tape holds 38G (before hitting EOT).

changer.conf and tpchanger for sun storedge 4mm dds-3 autoloader

[Ben Fallah]

I have a Sun StorEdge 4mm DDS-3 autoloader (magazine of 6 tapes loader)
http://www.sun.com/storage/dds/index.html
any one with correct changer.conf file and know what tpchanger be set to in
amanda.conf ?
Thank You
-
Ben Fallah
Senior System/Network Engineer

SCSI tape error with FreeBSD

[Doug Silver]

I just changed my longtime Amanda server from BSDI to FBSD 4.4-Stable and
I'm not sure if I'm using the correct tape device.

Here's what dmesg shows:
sa0 at ahc0 bus 0 target 6 lun 0
sa0:  Removable Sequential Access SCSI-3 device 
sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit)

So for the non-rewinding tape device I put in /dev/nsa0, which seems to
make sense after reading the mt and sa man pages (I know, I shouldn't be
RTFM'ing before hand, but oh well ;).  I've tried both /dev/nsa0 and
/dev/nrsa0 -- both failed!

So, when I try to access the drive by running amflush I get this kernel
message:

(sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
command to clear this state.

so I run 'mt -f /dev/nsa0 rewind' and things appear to be okay, but I
still get that error.  Also tried this:

# dump 0f /dev/nsa0 /etc
  DUMP: Date of this level 0 dump: Mon Apr  1 17:27:47 2002
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /etc to /dev/nsa0
  DUMP: bad sblock magic number
  DUMP: The ENTIRE dump is aborted.

Any suggestions?

Thanks!

-- 
~
Doug Silver
Network Manager
Quantified Systems, Inc
~

Re: V17 EOT

[John R. Jackson]

>I can't seem to find the file you are referring to...

It's in `amgetconf  logdir` (sorry, I forget that because that's
the same as my amanda.conf directory).

>Dick

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

Re: Using Remote Tape Drive on Windows NT

[Richard Bond]

How about this being tucked into amanda -

http://www.traakan.com/ndmjob/index.html

http://www.traakan.com/ndmjob/cthon-2000.htm

Maybe I misunderstand - but a standard module like this sounds
right to go with the mangement amanda provides/

rcb


"John R. Jackson" wrote:

> >Is there any way to run an amanda server on one of the
> >Linux boxes but use the tape drive(s) on the Windows
> >NT server?  I am not opposed to writting a days worth
> >of code to accomplish this task.
>
> One possibility would be to use 2.4.3bX and write a new tapeio module
> (hopefully not too difficult) to use the "rmt" (remote mag tape) protocol.
> It has a number of problems but it might get the job done.
>
> Then you'd need to be able to fire up the rmt client on the NT box in
> some way and get it to talk to the tape drive.
>
> Do you know what Cygwin is (sorry if that's too basic a question)?
> Can the drive be accessed from Cygwin?
>
> Where I'm headed is "rmt" (the client) comes with GNU tar, so that side of
> the code might already be done, or close to it.  And I think there is an
> inetd service that might be able to be coerced into running rmt on demand.
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: V17 EOT

[rwk]

> cc: [EMAIL PROTECTED]
> Reply-to: [EMAIL PROTECTED]
> Date: Mon, 01 Apr 2002 11:15:23 -0500
> From: "John R. Jackson" <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
> Precedence: bulk
> 
> >But tapetype length was set to 35000.  ...
> 
> What was runtapes set to?

>From /usr/local/etc/amanda/Daily/amanda.conf:

runtapes 1  # number of tapes to be used in a single run of amdump

> >Why did it try to write more than
> >35G on the tape (as you point out it apparently wrote 38G before hitting
> >EOT).
> 
> I don't have enough information.  Look at a corresponding amdump.
> file on the server (in the amanda.conf directory).  Find the line that
> looks like this:
> 
>   DELAYING DUMPS IF NEEDED, total_size 22483420, tape length 55296000 mark 2000
> delay: Total size now 22483420.
> 
> What do they say for your system?

I can't seem to find the file you are referring to...

# ls -l /usr/local/etc/amanda/Daily/

-rw-rw-r--   1 amanda   disk20654 Mar 29 14:06 amanda.conf
-rw-rw-r--   1 amanda   disk 1261 Feb 14 16:53 disklist
-rw---   1 amanda   disk  176 Mar 29 06:00 tapelist
-rw---   1 amanda   disk  154 Mar 18 15:22 tapelist.amlabel
-rw---   1 amanda   disk  176 Mar 25 16:59 tapelist.yesterday

I tried to use "locate" to find anything with "amanda." but nothing was
found which matched "amanda.".  Please advise...

Thanks,
Dick

Re: tape server crash recovery

[John R. Jackson]

>I started up amdump by hand (although it didn't background itself like
>one would think it would given all the other amanda programs do ...

Amflush is the only Amanda program that backgrounds itself, so I'm not
sure what you mean by "all the other amanda programs do".

>[dumps too big, but cannot incremental dump new disk]
>
>This seems to be contingent on some variable that is currently escaping
>me though.  ...

My guess is the crash nailed some of the curinfo (database) files along
with the tapelist.

>If I force full dumps of the afflicted partitions for tonight should I
>be safe?

Since they are "new disks" you shouldn't need to do anything -- Amanda
will insist on doing a full dump.  Although doing a "force" won't hurt
anything.

>Brandon D. Valentine <[EMAIL PROTECTED]>

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

tape server crash recovery

[Brandon D. Valentine]

So early Saturday morning our tape server suffered a kernel panic, and
it appears to have happened smack in the middle of the amdump run.  When
I brought the machine back up I looked and found that the run had not
completed, so I ran amcleanup, which appears to have taken care of the
logfiles left behind.  Then I looked and found a directory still in the
holding disk from that night, which contained 4 incomplete dumps left
behind by the 4 active dumpers at crash time.  I removed this directory.
Then I ran amcheck to see if anything else was odd.  Where it should
have told me which tape was needed for the next run, it only said that
it was expecting a new tape.  I went and looked at the tapelist file for
this config and it was empty!  Amdump must have been accessing it in
some way when the crash occured.  Luckily tapelist.yesterday had not
been overwritten so I looked at it and found that it was exactly what I
needed:

20020329 Daily03 reuse
20020328 Daily02 reuse
20020327 Daily01 reuse
20020326 Daily10 reuse
20020323 Daily09 reuse
20020322 Daily08 reuse
20020321 Daily07 reuse
20020320 Daily06 reuse
20020319 Daily05 reuse
20020316 Daily04 reuse

The 20020330 run (Saturday morning) was set to reuse Daily04, and that
was what was in the drive when the crash occured.  I copied
tapelist.yesterday to tapelist, and ran amcheck again, which told me
what I expected to see:

Tape Daily04 label ok

I started up amdump by hand (although it didn't background itself like
one would think it would given all the other amanda programs do, I had
to hit ^Z and run 'bg' from the shell to get my terminal back).  It's
running now and appears to be going well except that some of the disks
are listed in the amstatus output like this:

[dumps too big, but cannot incremental dump new disk]

This seems to be contingent on some variable that is currently escaping
me though.  The amstatus output lists plenty of disks that have already
dumped & taped level 1 and level 2 incrementals since I started up
amdump.  Amdump doesn't seem to be ignorant of the run history, so I
wonder why it is singling out these certain volumes as 'new disks'.
Perhaps these are the volumes in the process of being dumped or taped
when the crash occured?  Thoughts?  Suggestions?

If I force full dumps of the afflicted partitions for tonight should I
be safe?

-- 
Brandon D. Valentine <[EMAIL PROTECTED]>
Computer Geek, Center for Structural Biology

"This isn't rocket science -- but it _is_ computer science."
- Terry Lambert on [EMAIL PROTECTED]

Re: need help on how to config root partition in disklist

[Joshua Baker-LePain]

On Mon, 1 Apr 2002 at 2:06pm, [EMAIL PROTECTED] wrote

> I checked the sendsize.*.debug file. It looks like that amanda didn't 
> translate the filesystem names to the right dirname. 
> 
> A working case will be like:
> calculating for amname '/dev/sda1' dirname '/boot'
> 
> the failed case looks like
> calculating for amname '/dev/sda6' dirname '/dev/sda6'
> 
> How could I get around with this?

You need to apply the advfs.patch available at 
 to the 2.4.2p2 source and 
reinstall.

> Can I put "/" instead of "/dev/sda6" in my disklist file? I am 
> hesitating to do this because I am not sure if I will include 
> everything ( for example /home which is a separate partition) by 
> using just /. What I intended to do is only backuping the root 
> partition.

Yes, you can do this.  Amanda runs the backup program (either dump or tar) 
in the appropriate way such that it stays within a filesystem.

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

need help on how to config root partition in disklist

[ZLiu]

Hi, 

I am a relatively new amanda users. I got a problem where I could not 
find answers in the exsiting mail archive. 

The problem is: in my disklist file I listed

machinename /dev/sda6 root-tar

/dev/sda6 is my root partition and the mount point is /

and I always get the error message about disk offline. 

although the following lines work fine.

machinename /dev/sda1 root-tar 
machinename /dev/sdb1 high-tar

/dev/sda1 is the /boot partition and /dev/sdb1 is the /home partition.

I checked the sendsize.*.debug file. It looks like that amanda didn't 
translate the filesystem names to the right dirname. 

A working case will be like:
calculating for amname '/dev/sda1' dirname '/boot'

the failed case looks like
calculating for amname '/dev/sda6' dirname '/dev/sda6'

How could I get around with this?

Can I put "/" instead of "/dev/sda6" in my disklist file? I am 
hesitating to do this because I am not sure if I will include 
everything ( for example /home which is a separate partition) by 
using just /. What I intended to do is only backuping the root 
partition.

My OS is RedHat 7.2 and amanda verison 2.4.2p2. 

Thanks. zhiwei

KONTAKT LENS FIYAT LISTES Lutfen karsilastirin -kxwojbkd

[akdenizgoz_]

  Akdeniz Göz Merkezi her zaman oldugu gibi tum lens cesitlerini en uygun 
fiyatlarla sizlere sunmaktadir.
Ustelik bir telefon yada e-mail ile adresinize teslim.
AKDENIZ GOZ MERKEZI www.akdenizgoz.com
Fevzipasa cad. No:73   Fatih / Istanbul  0 212 635 74 74
  Bausch & Lomb
Soflens 66 (1 kutu=3 aylik)(aylik-numarali-seffaf)   35.000.000 TL
Soflens 66 (4 kutu=1 yillik)(aylik-numarali-seffaf) 125.000.000 TL
Soflens 38 (1 kutu=3 aylik)(aylik-numarali-seffaf)   40.000.000 TL
Soflens 66 Toric  (1 kutu=3 aylik)(astigmatik-seffaf)  75.000.000 TL
Optima Colors (1 cift)(renkli - uzun süreli)  90.000.000 TL
Ciba
Focus Visitint (1 kutu=3 aylik)  (aylik-numarali-seffaf)   35.000.000 TL
Focus Visitint (4 kutu=1yillik )  (aylik-numarali-seffaf) 125.000.000 TL
Night&Day (1 kutu=3 aylik)  (aylik-numarali-seffaf)   80.000.000 TL
Focus Toric  (1 kutu=3 aylik)(astigmatik-seffaf)  85.000.000 TL
Ciba Illusion   (1 cift)(renkli - uzun süreli) 180.000.000 TL
FreshLook  
FreshLook(1 cift)(renkli - kisa süreli) 33.000.000 TL
FreshLook(1 cift)(renkli - kisa süreli - numarali)  42.000.000 TL
 Zeiss
Contact Day 30 (1 kutu=3 aylik) (aylik-numarali-seffaf)   50.000.000 TL
 Biomediks
Biomediks   (1 kutu=3 aylik)(aylik-numarali-seffaf)   35.000.000 TL
 
Tum lenslerimiz orijinal olup saglik bakanligi bandrolleri uzerindedir.
Kredi kartina komisyon uygulanmaz.
 
Bu maili bir daha almak istemiyorsaniz [EMAIL PROTECTED]  mail adresine bos mail 
atiniz.
If you want unsubscript from our list, please send empty mail [EMAIL PROTECTED]

Fwd: dump timeout problem

[Zhen Liu]

Zhen Liu
Via Webmail
[EMAIL PROTECTED]
-- Forwarded message ---


From: Zhen Liu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Fri, 29 Mar 2002 09:09:14 -0500

Hi,

Thanks for your suggestions, I did change the etimeout from 300
(5minutes by default) to 3600 (1 hour).  Meanwhile, I changed the
"localhost" to the FQDN...and my holding disk in amanda.conf to
2Mb... But I still got some kind of timeout issue...I tried to
back up 5 file systems and got 3 of them failed... 

Can you please help? below are my log files:


This is my /var/spool/mail message:

>From amanda  Fri Mar 29 03:47:29 2002
Return-Path: <[EMAIL PROTECTED]>
Received: (from amanda@localhost)
by apple.iusb.edu (8.11.2/8.11.2) id g2T8lSM10987
for zliu; Fri, 29 Mar 2002 03:47:28 -0500
Date: Fri, 29 Mar 2002 03:47:28 -0500
From: Amanda user <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: DailyBackup AMANDA MAIL REPORT FOR March 29, 2002

These dumps were to tape DailySet11.
The next 2 tapes Amanda expects to used are: a new tape, a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
  apple.iusb /scsi4-data lev 0 FAILED [data timeout]
  apple.iusb /scsi0-data lev 1 FAILED [data timeout]
  apple.iusb /apps lev 0 FAILED [data timeout]


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:13
Run Time (hrs:min) 2:42
Dump Time (hrs:min)0:18   0:00   0:18
Output Size (meg)1936.20.0 1936.2
Original Size (meg)  1936.20.0 1936.2
Avg Compressed Size (%) -- -- --(level:#disks
.)
Filesystems Dumped2  0  2   (1:2)
Avg Dump Rate (k/s)  1840.6--  1840.6

Tape Time (hrs:min)0:13   0:00   0:13
Tape Size (meg)  1936.30.0 1936.3
Tape Used (%)   4.80.04.8   (level:#disks
.)
Filesystems Taped 2  0  2   (1:2)
Avg Tp Write Rate (k/s)  2524.5--  2524.5

^L
FAILED AND STRANGE DUMP DETAILS:

/-- apple.iusb /scsi4-data lev 0 FAILED [data timeout]
sendbackup: start [apple.iusb.edu:/scsi4-data level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
|   DUMP: Date of this level 0 dump: Fri Mar 29 01:17:51 2002
|   DUMP: Date of last level 0 dump: the epoch
|   DUMP: Dumping /dev/sda9 (/scsi4-data) to standard output
|   DUMP: Label: none
|   DUMP: mapping (Pass I) [regular files]
|   DUMP: mapping (Pass II) [directories]
|   DUMP: estimated 620986 tape blocks.
|   DUMP: Volume 1 started at: Fri Mar 29 01:18:27 2002
|   DUMP: dumping (Pass III) [directories]
|   DUMP: dumping (Pass IV) [regular files]
\

/-- apple.iusb /scsi0-data lev 1 FAILED [data timeout]
sendbackup: start [apple.iusb.edu:/scsi0-data level 1]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
|   DUMP: Date of this level 1 dump: Fri Mar 29 01:51:33 2002
|   DUMP: Date of last level 0 dump: Thu Mar 28 13:26:41 2002
|   DUMP: Dumping /dev/sda7 (/scsi0-data) to standard output
|   DUMP: Label: none
|   DUMP: mapping (Pass I) [regular files]
|   DUMP: mapping (Pass II) [directories]
|   DUMP: estimated 950437 tape blocks.
|   DUMP: Volume 1 started at: Fri Mar 29 01:52:17 2002
|   DUMP: dumping (Pass III) [directories]
|   DUMP: dumping (Pass IV) [regular files]
|   DUMP: 66.01% done at 2091 KB/s, finished in 0:02
\

/-- apple.iusb /apps lev 0 FAILED [data timeout]
sendbackup: start [apple.iusb.edu:/apps level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
|   DUMP: Date of this level 0 dump: Fri Mar 29 02:47:12 2002
|   DUMP: Date of last level 0 dump: the epoch
|   DUMP: Dumping /dev/sda6 (/apps) to standard output
|   DUMP: Label: none
|   DUMP: mapping (Pass I) [regular files]
|   DUMP: mapping (Pass II) [directories]
|   DUMP: estimated 13642189 tape blocks.
|   DUMP: Volume 1 started at: Fri Mar 29 02:53:35 2002
|   DUMP: dumping (Pass III) [directories]
|   DUMP: dumping (Pass IV) [regular files]
|   DUMP: 2.89% done at 1314 KB/s, finished in 2:47
|   DUMP: 6.73% done at 1530 KB/s, finished in 2:18
|   DUMP: 11.72% done at 1776 KB/s, finished in 1:52
|   DUMP: 19.07% done at 2168 KB/s, finished in 1:24
\

^L
NOTES:
  planner: Last full dump of apple.iusb.edu:/apps on tape  overwritten
in 1 run.
  planner: Adding new disk apple.iusb.edu:/scsi4-data.
  taper: tape DailySet11 kb 1982752 fm 2 [OK]

^L
DUMP SUMMARY:
 DUMPER STATSTAPER
STATS 
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS 
KB/s
-- -

apple.iusb.e /apps   0 FAILED
---

Re: V17 EOT

[John R. Jackson]

>But tapetype length was set to 35000.  ...

What was runtapes set to?

>Why did it try to write more than
>35G on the tape (as you point out it apparently wrote 38G before hitting
>EOT).

I don't have enough information.  Look at a corresponding amdump.
file on the server (in the amanda.conf directory).  Find the line that
looks like this:

  DELAYING DUMPS IF NEEDED, total_size 22483420, tape length 55296000 mark 2000
delay: Total size now 22483420.

What do they say for your system?

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

Re: Two tape drives

[Eric Trager]

On Mon, 1 Apr 2002, C. Chan wrote:

> Is there currently a way to back up to two or more tape drives simultaneously
> using the same Amanda config?

Apparently not. I have a 30-slot jukebox attached to two drives and use
two different configs to run the robot and perform backups (sometimes
simultaneously), but amanda can't run one backup across two tapes in two
drives in parallel.

We have another system with a four-drive jukebox and Legato Networker and
Networker seems to handle the parallel stuff pretty well... for a price.

- -  -   --
Eric Trager
CMAG, DCB, CIT, NIH
12A/2020, 301-402-8738
[EMAIL PROTECTED]

Re: Two tape drives

[C. Chan]

Also Sprach Joshua Baker-LePain:

> chg-multi is what you're looking for -- it lets you use two tape drives as
> a changer.  Keep in mind that a single disklist entry still can't be
> bigger than a single tape.
>

Is there currently a way to back up to two or more tape drives simultaneously
using the same Amanda config?

I saw the RAIT code in 2.4.3beta, but I'm not interested in the
RAID-like features (parity, mirroring, striping).

-- 
C. Chan < [EMAIL PROTECTED] >
PGP Public Key: finger [EMAIL PROTECTED]

Adjusting runtapes

[Don Potter]

I'm decom' a server that was a tape hog.  So consequently I'm able to 
adjust my runtapes.  Has anybody experienced any adverse situations that 
would be derived from reducing the runtapes?

Don

Re: Two tape drives

[Joshua Baker-LePain]

On Mon, 1 Apr 2002 at 11:47am, David Flood wrote

> I want to split my backups over two DLT drives. Is this possible and 
> if so how is it best done? Can amanda be configured to do this 
> somehow or do/can I run two instances of amanda at the same 
> time?

chg-multi is what you're looking for -- it lets you use two tape drives as 
a changer.  Keep in mind that a single disklist entry still can't be 
bigger than a single tape.

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

Two tape drives

[David Flood]

I want to split my backups over two DLT drives. Is this possible and 
if so how is it best done? Can amanda be configured to do this 
somehow or do/can I run two instances of amanda at the same 
time?

-
David Flood
Systems Administrator
[EMAIL PROTECTED]
Tel: +44 (0)1224 262721
The Robert Gordon University
School of Computing
St. Andrews Street
Aberdeen
-