without tapes

2002-04-03 Thread Juanjo

Hi,

Is it possible to run amanda without-tapes so it dumps only to holding
disk?
But what I mean is not to take off the tapes physically but disabling tape
writing. I want to accumulate incrementals worth a week and flush them on
friday to a tape...

How can I do such a thing?







DLT

2002-04-03 Thread David Flood

Sorry if this subject is off topic but can you use a 40/80 DLT tape 
in a 35/70 DLT tape drive. Although we'd only be using it as a 35/70 
tape.

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



Re: DLT

2002-04-03 Thread Uncle George

technically yes. A DLT-IV tape is the tape of choice on a quantum 7000,
and quantum 8000. I do not know, however, if the tape that was written
with a 7000 series, and later re-used on an 8000 if it would be reliable
. I suspect that it should work.

But for a definitive answer, give www.quantum.com a call.

David Flood wrote:
 
 Sorry if this subject is off topic but can you use a 40/80 DLT tape
 in a 35/70 DLT tape drive. Although we'd only be using it as a 35/70
 tape.
 
 -
 David Flood
 Systems Administrator
 [EMAIL PROTECTED]
 Tel: +44 (0)1224 262721
 The Robert Gordon University
 School of Computing
 St. Andrews Street
 Aberdeen
 -



Unloading tapes when task done ?

2002-04-03 Thread Uncle George

It seems like when the whole procedure ( whether its labeling tape(s),
amchecking tape, or amdumping ) is complete, the tape is left in the
tape drive in an on-line state. 
Is there some reason why the tape is not at least rewind-offlined, or
for tape changer folks rewoffl/unload'ed back to the carousel slot when
the job/task is finished?

Just my 2 cents



Re: Unloading tapes when task done ?

2002-04-03 Thread Gerhard den Hollander

* Uncle George [EMAIL PROTECTED] (Wed, Apr 03, 2002 at 06:19:19AM -0500)
 It seems like when the whole procedure ( whether its labeling tape(s),
 amchecking tape, or amdumping ) is complete, the tape is left in the
 tape drive in an on-line state. 
 Is there some reason why the tape is not at least rewind-offlined, or
 for tape changer folks rewoffl/unload'ed back to the carousel slot when
 the job/task is finished?

Dunno,
my crontab sez:
0 18 * * 1-5 /volume/amanda/sbin/amdump lto; mt -f /dev/rmt/3h rewoffl

works like a charm.

Currently listening to: Helloween - If I Could Fly

Gerhard,  @jasongeo.com   == The Acoustic Motorbiker ==   
-- 
   __O  Some say the end is near.
 =`\,  Some say we'll see armageddon soon
(=)/(=) I certainly hope we will
I could use a vacation




Re: Unloading tapes when task done ?

2002-04-03 Thread Uncle George

I dunno either, will it work on a 6 drive auto changer/tape library?
/gat

 Dunno,
 my crontab sez:
 0 18 * * 1-5 /volume/amanda/sbin/amdump lto; mt -f /dev/rmt/3h rewoffl
 
 works like a charm.
 




Re: Unloading tapes when task done ?

2002-04-03 Thread Gene Heskett

On Wednesday 03 April 2002 06:19 am, Uncle George wrote:
It seems like when the whole procedure ( whether its labeling
 tape(s), amchecking tape, or amdumping ) is complete, the tape
 is left in the tape drive in an on-line state.
Is there some reason why the tape is not at least
 rewind-offlined, or for tape changer folks rewoffl/unload'ed
 back to the carousel slot when the job/task is finished?

Just my 2 cents

I'd druther it didn't.  By leaving the tape online, the display 
on the front of the changer tells me what slot is loaded.  If its 
the last slot, and its after the runtime for amdump, then I know 
to change tapes.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
98.7+% setiathome rank, not too shabby for a hillbilly



Re: Unloading tapes when task done ?

2002-04-03 Thread John R. Jackson

Is there some reason why the tape is not at least rewind-offlined ...

Because other users specifically asked for it to be left alone (we had
to remove code that used to rewind after each operation).  I assume they
run something else after amdump (for instance) to tack on a little more
data to the tape.

And in the case of a changer, offlining the drive may cause other things
to happen, such as dropping the stack and loading the next tape, which
might not be what you want.  Better that we leave things alone and if
a particular setup needs something different, it's easy for them to do.

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



Onstream ADR(2)60IDE

2002-04-03 Thread Hamm, Gottfried

Hi all,

I'm new to this list, so sorry if it's a FAQ: Is there a tape definition
to use Onstream ADR(2)60IDE drives (30 / 60 GB) with Amanda?

TIA,

Gottfried

-- 
Gottfried Hamm
Phone +49 (6249) 905005 | Fax +49 (6249) 905004
mailto:[EMAIL PROTECTED] | http://www.ghks.de



Re: Unloading tapes when task done ?

2002-04-03 Thread Uncle George

Guess I'm from old school. Older 9trk drives when left on, continually
have the vacuum on, and under constant tension. Its not healthy for the
tape. Does that happen with a DLT tape, how about the DDS tapes.
 I would NOT like a live tape to be left in the drive for long periods
of time. Who knows when a power failure will hit, who knows when the
drive will go awol. An unloaded tape, immediately after backup, is safe
from other folks, as well as the server, writing onto it.

Gene Heskett wrote:

 I'd druther it didn't.  By leaving the tape online, the display



Re: data timeout

2002-04-03 Thread Joshua Baker-LePain

On 3 Apr 2002 at 1:22am, [EMAIL PROTECTED] wrote

 I have experienced this several times now on more than one machine.  For
 example:
 
   vulcan.int /usr lev 0 FAILED [data timeout]
 
 When I check vulcan, I see dumps are still running and I have to kill
 them (after amdump has finished).
 
 What causes hangs like this and what can I do to try to prevent them.
 It seems to happen every other dump.
i 
 Thanks,
 Dick
 

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




Re: without tapes

2002-04-03 Thread Joshua Baker-LePain

On Wed, 3 Apr 2002 at 11:12am, Juanjo wrote

 Is it possible to run amanda without-tapes so it dumps only to holding
 disk?
 But what I mean is not to take off the tapes physically but disabling tape
 writing. I want to accumulate incrementals worth a week and flush them on
 friday to a tape...

If this is what you want to do, just don't put a tape in on Mon-Fri.  Then 
do your amflush(es) on Friday.  Note that you'll need to set your reserve 
to a low number to have room for full backups and you'll need enough 
holding space.

Also keep in mind that if that disk crashes on Thursday night/Friday 
morning, you've lost a week's worth of backups...

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




Re: back up data on holding disk only

2002-04-03 Thread Joshua Baker-LePain

On Tue, 2 Apr 2002 at 6:16pm, Julien Boret wrote

 I want to back up my data on the holding disk only. Every time I put a tape
 in the tape drive, Amanda will first try to back up the data on the tape and
 will only back up the data on the holding disk if there is no tape in the
 drive or if there is a problem with the tape.
 I would like to know if there is an option I can specify in the amanda.conf
 file that would tell Amanda to always back up my data on the holding disk
 without looking first if there is a tape in the tape drive.

If you *never* want that config to go to tape, you have two options.  With 
2.4.2p2, just define your tapedev in amanda.conf to be /dev/no/such/device 
or some such thing.  Amanda won't find the device, will go into degraded 
mode, and will put everything on the holding disk.

With 2.4.3bN (note the b for beta), you can use files on disk as if they 
were tapes.  Details on this are in the mailing list archives and in 
amanda(8) distributed with those versions.

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




Re: data timeout

2002-04-03 Thread Joshua Baker-LePain

On 3 Apr 2002 at 1:22am, [EMAIL PROTECTED] wrote

 I have experienced this several times now on more than one machine.  For
 example:
 
   vulcan.int /usr lev 0 FAILED [data timeout]
 
 When I check vulcan, I see dumps are still running and I have to kill
 them (after amdump has finished).

What type of machine, running what OS, and using what backup program?

If I may hazard a guess, is this a Linux box running a recent distro (i.e. 
2.4 kernel) and using dump?  If that's the case, then this is a standard 
problem (and the cause of a couple of near flame wars (or, as near as this 
list ever comes)).  The only sure-fire method of solving it in this case 
is to use tar rather than dump for your backups.  Although updating dump 
to the most recent version may help as well.

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




Re: data timeout

2002-04-03 Thread Joshua Baker-LePain

On Wed, 3 Apr 2002 at 9:06am, Joshua Baker-LePain wrote

Not a damn thing.  Real one coming.  Sorry 'bout that.

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




Still having problems with ufsdump returning 3...

2002-04-03 Thread Morse, Richard E.

Hi!  I'm still having problems with ufsdump returning error code three, thus
causing the dumps to fail.  There seems to be no consistancy to this -- the
disks get backed up correctly eventually, but it takes a number of tries.  None
of the log files that I know about (/tmp/amanda/*) seem to contain any more
information that what is reported in my nightly logs.  I've included the error
report below...

Any ideas where I look to see if I can figure out what the problem is?

Thanks,
Ricky


/-- .mgh.h /dev/dsk/c0t2d0s4 lev 2 FAILED [/usr/sbin/ufsdump returned 3]
sendbackup: start [.mgh.harvard.edu:/dev/dsk/c0t2d0s4 level 2]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/sbin/ufsrestore -f... -
sendbackup: info end
|   DUMP: Writing 32 Kilobyte records
|   DUMP: Date of this level 2 dump: Tue Apr 02 19:14:48 2002
|   DUMP: Date of last level 1 dump: Tue Mar 26 19:09:43 2002
|   DUMP: Dumping /dev/rdsk/c0t2d0s4 (.mgh.harvard.edu:/crc) to standard
output.
|   DUMP: Mapping (Pass I) [regular files]
|   DUMP: Mapping (Pass II) [directories]
|   DUMP: Mapping (Pass II) [directories]
|   DUMP: Mapping (Pass II) [directories]
|   DUMP: Estimated 1199200 blocks (585.55MB) on 0.01 tapes.
|   DUMP: Dumping (Pass III) [directories]
|   DUMP: Dumping (Pass IV) [regular files]
|   DUMP: 22.16% done, finished in 0:35
|   DUMP: 47.81% done, finished in 0:22
|   DUMP: 81.22% done, finished in 0:06
? sendbackup: index tee cannot write [Broken pipe]
|   DUMP: Broken pipe
|   DUMP: The ENTIRE dump is aborted.
? index returned 1
sendbackup: error [/usr/sbin/ufsdump returned 3]
\

-
Richard MorseSystem Administrator 
MGH Biostatistics Center  50 Staniford St. Rm 560
[EMAIL PROTECTED] 617/724-9830



Re: Unloading tapes when task done ?

2002-04-03 Thread Uncle George

Maybe they can OPT-OUT of the feature, but on a busy site, allowing the
customers to access the tape drives, would appear to make good business
sense. Particularily when the drives are doing just nothing.
/gat

btw, what do u mean each operation. Each run? If funny things happen,
maybe they should be addressed. After all, you got all these logs, and
status files hanging around.


John R. Jackson wrote:
 
 Is there some reason why the tape is not at least rewind-offlined ...
 
 Because other users specifically asked for it to be left alone (we had
 to remove code that used to rewind after each operation).  I assume they
 run something else after amdump (for instance) to tack on a little more
 data to the tape.
 
 And in the case of a changer, offlining the drive may cause other things
 to happen, such as dropping the stack and loading the next tape, which
 might not be what you want.  Better that we leave things alone and if
 a particular setup needs something different, it's easy for them to do.
 
 John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]



I know this message... help restore entire system

2002-04-03 Thread Mr Igor Vertiletsky

Hi all;

I am running RH 7.1 with an IDE hard drive. the system
is configured as amanda client and has only one
partition / (root). I've been getting some disk
read/write errors on this computer. To parafrase
Galaxy Quest: I know this message... It is a bad
message!!!, . It looks like the IDE drive is about to
go. I am planning to run fsck, but it has an equal
chance of trashing the system.

Anyway, my question is: how do I restore the entire
system (in case I need to rplace or rebuild hard
drive)? I have recent full dumps of the server.

Thanks.

igor.

__
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/



amanda auth hosts problem

2002-04-03 Thread Tom Van de Wiele

Hello list

I have a backupserver with two partitions on it that need to be backup'd
+ 2 clients.

I have a .amandahosts in the amanda user's $HOME.  It has this in it:

[cut]
hostname.eduline.be amanda
[/cut]

To make backups, this works fine.  But when I want to amrecover files, I
get that amanda authhosts failed.  When I change the user to root
instead of amanda, then amrecover works.  Is there a more sudle way
then to always change that user in that file?

(BTW, I applied the stream_client patch, recompiled and amrecover works)

Kind regards

-- Tom



-- 
Tom Van de Wiele
System Administrator

Eduline 
Colonel Bourgstraat 105a
1140 Brussel
http://www.eduline.be



Re: I know this message... help restore entire system

2002-04-03 Thread Don Potter

Good reference:

http://www.backupcentral.com/amanda-23.html

Don't forget to do a amadmin conf find machine filesystem

to detemine what tape has your most current backups (Level 0 and  1 
preferably)

Good Luck

Mr Igor Vertiletsky wrote:

Hi all;

I am running RH 7.1 with an IDE hard drive. the system
is configured as amanda client and has only one
partition / (root). I've been getting some disk
read/write errors on this computer. To parafrase
Galaxy Quest: I know this message... It is a bad
message!!!, . It looks like the IDE drive is about to
go. I am planning to run fsck, but it has an equal
chance of trashing the system.

Anyway, my question is: how do I restore the entire
system (in case I need to rplace or rebuild hard
drive)? I have recent full dumps of the server.

Thanks.

igor.

__
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/






Problems getting client to work.

2002-04-03 Thread Thomas -Balu- Walter

Hi all,

I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client.
One problem is that I don't know how the backup-server is set up, so I
wonder if anyone here can see sthg in the logs below.

The client is running on a SuSE-Linux 7.3 - self compiled using
./configure --with-user=amanda --with-group=disk
Compiling and installing didn't give me an error.

/var/lib/amanda which is the amanda-user homedir is owned by amanda:disk
and amanda has the right to rwx there. Amanda itself got a bash as
shell. The homedir contains the following files:

-rw-r--r--   1 root root   21 Mar  1 16:39 .amandahosts
drwxr-xr-x   2 amanda   disk 4096 Mar 12 11:00 gnutar-lists
drwxr-xr-x   2 amanda   disk 4096 Apr 28  2000 index

Both dirs are empty, .amandahosts contains backupserver.dom.ain backup

Can you see a problem in the following logs? Or point me into a
direction where to have a look?

 Regards from Muenster/Germany
Balu
PS: please reply personally too, as I am not subscribed to this list.

amandad.20020403005137.debug 
amandad: debug 1 pid 30345 ruid 37 euid 37 start time Wed Apr  3
00:51:37 2002
amandad: version 2.4.3b3
amandad: build: VERSION=Amanda-2.4.3b3
amandad:BUILT_DATE=Tue Mar 12 16:08:21 MET 2002
amandad:BUILT_MACH=Linux RoadRunner 2.2.14 #1 Mon Mar 13 10:51:48 GMT 2000 
i686 unknown
amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' 
'--with-group=disk'
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
amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/
amandad:RDEV_PREFIX=/dev/ SAMBA_CLIENT=/usr/bin/smbclient
amandad:GNUTAR=/bin/tar COMPRESS_PATH=/usr/bin/gzip
amandad:UNCOMPRESS_PATH=/usr/bin/gzip MAILER=/usr/bin/Mail
amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=RoadRunner DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=RoadRunner
amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN=amanda 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 007-60610608 SEQ 1017787508
SECURITY USER backup
SERVICE sendsize
OPTIONS maxdumps=1;hostname=123.123.123.123;
GNUTAR /home/balu 0 1970:1:1:0:0:0 -1 exclude-list=.amanda.exclude


sending ack:

Amanda 2.4 ACK HANDLE 007-60610608 SEQ 1017787508


bsd security: remote host backupserver.dom.ain user backup local user amanda
amandahosts security check passed
amandad: running service /usr/local/libexec/sendsize
amandad: sending REP packet:

Amanda 2.4 REP HANDLE 007-60610608 SEQ 1017787508
OPTIONS maxdumps=1;


amandad: got packet:

Amanda 2.4 ACK HANDLE 007-60610608 SEQ 1017787508


amandad: pid 30345 finish time Wed Apr  3 00:51:37 2002
 amandad.20020403005137.debug 


sendsize.20020403005137.debug 
sendsize: debug 1 pid 30346 ruid 37 euid 37 start time Wed Apr  3 00:51:37 2002
/usr/local/libexec/sendsize: version 2.4.3b3
sendsize: calculating for amname '/home/balu', dirname '/home/balu'
sendsize: getting size via gnutar for /home/balu level 0
 sendsize.20020403005137.debug


sendsize._home_balu.20020403005137.exclude is empty


additionally there is a selfcheck-file
selfcheck.20020403160640.debug 
selfcheck: debug 1 pid 2338 ruid 37 euid 37 start time Wed Apr  3 16:06:40 2002
/usr/local/libexec/selfcheck: version 2.4.3b3
selfcheck: exclude list file /home/balu/.amanda.exclude does not exist, ignoring
selfcheck: checking disk /home/balu
selfcheck: device /home/balu
selfcheck: OK
selfcheck: pid 2338 finish time Wed Apr  3 16:06:40 2002
 selfcheck.20020403160640.debug

-- 
Wipe Info uses hexadecimal values to wipe files. This provides more
security than wiping with decimal values.
-- Norton SystemWorks 2002 Professional Edition User's Guide



Re: amanda auth hosts problem

2002-04-03 Thread Don Potter

You are actually supposed to run amrecover as root...which makes sense 
being that would be the account that would be doing a restore or a 
recover typically.

Don

Tom Van de Wiele wrote:

Hello list

I have a backupserver with two partitions on it that need to be backup'd
+ 2 clients.

I have a .amandahosts in the amanda user's $HOME.  It has this in it:

[cut]
hostname.eduline.beamanda
[/cut]

To make backups, this works fine.  But when I want to amrecover files, I
get that amanda authhosts failed.  When I change the user to root
instead of amanda, then amrecover works.  Is there a more sudle way
then to always change that user in that file?

(BTW, I applied the stream_client patch, recompiled and amrecover works)

Kind regards

-- Tom








Re: Problems getting client to work.

2002-04-03 Thread Joshua Baker-LePain

On Wed, 3 Apr 2002 at 6:28pm, Thomas -Balu- Walter wrote

 I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client.
 One problem is that I don't know how the backup-server is set up, so I
 wonder if anyone here can see sthg in the logs below.
*snip*

Err, it would help if you told us what the problem was, i.e. send us the 
amanda email report that notes the problem or the problematic amcheck 
output.

Those logs looked fine, except for the missing exclude list.

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




Re: amanda auth hosts problem

2002-04-03 Thread Joshua Baker-LePain

On Wed, 3 Apr 2002 at 6:25pm, Tom Van de Wiele wrote

 Hello list
 
 I have a backupserver with two partitions on it that need to be backup'd
 + 2 clients.
 
 I have a .amandahosts in the amanda user's $HOME.  It has this in it:
 
 [cut]
 hostname.eduline.be   amanda
 [/cut]
 
 To make backups, this works fine.  But when I want to amrecover files, I
 get that amanda authhosts failed.  When I change the user to root
 instead of amanda, then amrecover works.  Is there a more sudle way
 then to always change that user in that file?

amrecover needs to be run as root, so .amandahosts on the server must 
allow root access from the clients.  Thus, a sample .amandahosts file on 
the amanda server might look like:

tapeserver.somewhere.com amanda
tapeserver.somewhere.com root
client1.somewhere.comroot
.
.

etc.

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




effects of changing dumptype?

2002-04-03 Thread Frank Smith

Will changing the dumptype of a filesytem in the disklist cause any
problems later if I need to restore a backup using the previous
dumptype, or does Amanda automagically figure out what was used?
Should it only be done immediately before a level 0 or would it
not matter if the incrementals were different from the full?
   I want to quit using compression on a few filesystems that don't
compress well to save CPU, but have a few months worth of backups
that are compressed.  Also, would a switch between dump/tar handled
the same way?

Thanks,
Frank

--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501



Re: Problems getting client to work.

2002-04-03 Thread Thomas -Balu- Walter

+ Joshua Baker-LePain [EMAIL PROTECTED] [03.04.02 18:51]:
 On Wed, 3 Apr 2002 at 6:28pm, Thomas -Balu- Walter wrote
 
  I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client.
  One problem is that I don't know how the backup-server is set up, so I
  wonder if anyone here can see sthg in the logs below.
 *snip*
 
 Err, it would help if you told us what the problem was, i.e. send us the 
 amanda email report that notes the problem or the problematic amcheck 
 output.

The problem is, that I don't get an email report or the amcheck
output... As stated above, I only set up the client. The backup-server
itself is not under my control - the admin of that server told me that
it has to be something with my client-setup. And I wanted to see if you
can see any problem on my side in those logs.

 Those logs looked fine, except for the missing exclude list.

Ok, thanks. So I'll have to kick the other admin to get it working ;-)

Balu
-- 
Linux is like a fractal: No matter how deep you go, there's always
more!  [Casey Bralla, 24.01.2001 in [EMAIL PROTECTED]]



Re: Problems getting client to work.

2002-04-03 Thread Joshua Baker-LePain

On Wed, 3 Apr 2002 at 8:23pm, Thomas -Balu- Walter wrote

  Err, it would help if you told us what the problem was, i.e. send us the 
  amanda email report that notes the problem or the problematic amcheck 
  output.
 
 The problem is, that I don't get an email report or the amcheck
 output... As stated above, I only set up the client. The backup-server
 itself is not under my control - the admin of that server told me that
 it has to be something with my client-setup. And I wanted to see if you
 can see any problem on my side in those logs.

Have him or her send you (or us) the output of amcheck.  You really can't 
debug this without being able to run those tools.

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




A few interesting problems (tapeless, interactive restores, etc)

2002-04-03 Thread Greg Mohney

Hello,

I am implementing AMANDA at my current workplace (used it once before
and loved it) however I have a few strange circumstances and questions
regarding my options.  If anyone can help me with the below it would be
appreciated.

First off, for reasons beyond the scope of this email, my AMANDA server
has no tape device.  I am sending all backups to the holding disk.  We
also have a large IBM tape library running ADSM that I would like to
incorporate into my AMANDA backup strategy.  In my head, it will go
something like this:

1. AMANDA schedules and performs backups to holding disk.
2. Every night, after AMANDA has completed her backups, the dated
directory is moved over to our ADSM server.
3. The holding disk is wiped clean (space saving measure, ADSM will have
the files anyway). 
3. The ADSM server spools the directory to tape.
4. I write a wonderfully sexy amrestore-wrapper script that will take
three arguments:
* machine name
* files to be restored
* date of file you want to extract
5. Wrapper script figures out which dump directories it needs to get
out of ADSM, gets them, and then runs the appropriate amrestore commands
to seemlessly restore said files.

I have a couple of problems (i.e. things I'm not sure about or are too
stupid to understand) however and they are as follows:

A) I need a way of asking AMANDA, If I want foo file from 3/20/2000 on
machine bar, which dump 'directories' will I need?  I have read and
re-read the man pages for amdump, amadmin, etc., but the answer is not
immediately obvious to me.  I understand AMANDA usually works with
tapes, but since even amrecover will look into holding disk dated
directories, surely there's a way to get this info from AMANDA (without
actually performing the restore, all I want is the dated directory names
so I can pull them out of ADSM and slap them back into the AMANDA
server's holding disk, so that amrestore/amrecover can get to them).

B) After writing the above, I'm not sure I remember what my second
problem was, or if it was relevent if (A) is solved.  Sorry.  I think it
had something to do with piping 'amrestore' output to tar not being
interactive as it could be with dump/restore.  In other words, I want
our tape monkies to be able to interactively restore files, but if I'm
using GNU tar all I can do is request specific files. Eh, but that's ok
I think...sorry...

Anyways, I know this is long and rambling.  I appreciate any help on the
above, or even different strategies if the one presented is on crack.

Thanks.
-- 
Greg Mohney
Technical Specialist, UNIX Administration
APAC Customer Services
(319) 896-5027




Re: data timeout

2002-04-03 Thread rwk

  I have experienced this several times now on more than one machine.  For
  example:
  
vulcan.int /usr lev 0 FAILED [data timeout]
  
  When I check vulcan, I see dumps are still running and I have to kill
  them (after amdump has finished).
 
 What type of machine, running what OS, and using what backup program?

Server: Intel RH Linux 5.1 kernel 2.2.5
Client: Intel RH Linux 7.2 kernel 2.4.7

 If I may hazard a guess, is this a Linux box running a recent distro (i.e. 
 2.4 kernel) and using dump?

You are correct (Intel RH Linux 7.2 kernel 2.4.7) on the client (which
is hanging).

 If that's the case, then this is a standard problem (and the cause of
 a couple of near flame wars (or, as near as this list ever comes)).
 The only sure-fire method of solving it in this case is to use tar
 rather than dump for your backups.  Although updating dump to the most
 recent version may help as well.

I didn't know that!  The client is running: dump-0.4b22-6

Does anyone know if there is a more recent version (or if there is a
dump we site)?

Thanks!
Dick

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



RESULTS MISSING

2002-04-03 Thread rwk

What does RESULTS MISSING mean?

I am running Intel RH Linux with Amanda version 2.4.2p2...

*** THE DUMPS DID NOT FINISH PROPERLY!

These dumps were to tape Daily6.
The next tape Amanda expects to use is: Daily1.

FAILURE AND STRANGE DUMP SUMMARY:
  gorn.ameri /ideroot2 lev 1 FAILED [/sbin/dump returned 3]
  solo.ameri /idebigger RESULTS MISSING
  vulcan.int /usr RESULTS MISSING
  maul.ameri / RESULTS MISSING
  andorian.a / RESULTS MISSING

Thanks,
Dick



Re: Unloading tapes when task done ?

2002-04-03 Thread Uncle George

Jay Lessert wrote:
 
 On Wed, Apr 03, 2002 at 06:19:19AM -0500, Uncle George wrote:
  It seems like when the whole procedure ( whether its labeling tape(s),
  amchecking tape, or amdumping ) is complete, the tape is left in the
  tape drive in an on-line state.
  Is there some reason why the tape is not at least rewind-offlined, or
  for tape changer folks rewoffl/unload'ed back to the carousel slot when
  the job/task is finished?
 
 1)  You would piss off people that are already doing:
 
 amdump DAILY; amverify DAILY
 
 ...from cron on a non-changer drive.
Maybe a visit to the toilet facility would do wonders to your
disposition. Its exceptionally arrogant of you to speak for us all. 
Since you dont know how it will be implemented, i can only wonder how
you or god know that this will be true.
 
 2)  Since it's already so easy to do any of:
 
 amdump DAILY; amtape DAILY eject
 amdump DAILY; amtape DAILY slot next
 amdump DAILY; amtape DAILY slot advance
 
 ...or anything else that makes sense for your particular installation,
 why hardwire some particular behavior into amdump (which would then
 inevitably be exactly the wrong behavior for some other poor schmoe's
 particular installation)?

Amazingly arrogant.  I might think that on a power failure, as Quantum
points out, they will not be responsible for the tape left inside the
drive. AND i agree with  their, slightly over stated, belief. The
purpose of a backup is not just to do a backup, but be able to restore
that data - generally when Kaos strikes. A trashed tape, even to the
poor schlep who believes in you, is of no use to anyone. When you are
finished, take the tape out, and put it in a safe place.
 
BTW who said it was, or has to be hardwired. it need not be any more
'hardwired' than dumpcycle 0, or compress none, or simply a
EjectWhenDone yes .

BTW#2 you should be doing an 
amdump  BACKUP; amtape BACKUP physically_set_write_protect_tab; amverify
BACKUP



Re: data timeout

2002-04-03 Thread Joshua Baker-LePain

On 3 Apr 2002 at 9:43pm, [EMAIL PROTECTED] wrote

 I didn't know that!  The client is running: dump-0.4b22-6
 
 Does anyone know if there is a more recent version (or if there is a
 dump we site)?

http://dump.sourceforge.net/

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




Re: Unloading tapes when task done ?

2002-04-03 Thread Uncle George

I Beleive you are in error. 4mm dds simply have the head stop spinning,
the tape is still wrapped around in the mechanism. The DLT I have does
not unload at all, unless specifically directed to. 
Maybe you can show me where u got your information from ? Maybe i can
find the quantum docs that say 'dont do that'.

Jay Lessert wrote:
 
 On Wed, Apr 03, 2002 at 08:58:29AM -0500, Uncle George wrote:
  Guess I'm from old school. Older 9trk drives when left on, continually
  have the vacuum on, and under constant tension. Its not healthy for the
  tape. Does that happen with a DLT tape, how about the DDS tapes.
 
 8mm, AIT*, DDS*, DLT*, LTO* drives all unload the tape (unwrap the
 tape from around the head and power down the servos) after some
 hardwired time period.
 
   I would NOT like a live tape to be left in the drive for long periods
  of time.
 
 Then don't.  Is there something you need to do that amtape doesn't
 know how to do?
 
 --
 Jay Lessert   [EMAIL PROTECTED]
 Accelerant Networks Inc.   (voice)1.503.439.3461
 Beaverton OR, USA(fax)1.503.466-9472



Re: DLT

2002-04-03 Thread Bernhard R. Erdmann

 Sorry if this subject is off topic but can you use a 40/80 DLT tape
 in a 35/70 DLT tape drive. Although we'd only be using it as a 35/70
 tape.

no problem to write on DLT IV tapes with a DLT 7000 drive



Re: Unloading tapes when task done ?

2002-04-03 Thread John R. Jackson

Maybe they can OPT-OUT of the feature ...

It's just as easy for someone to opt-in and do their own tape operations
when Amanda is done.  Amanda will currently support both camps -- unload
it when done vs. leave it alone.  Why add more complexity?  We already
have too many options (and lots of other things on the TODO list).

btw, what do u mean each operation.  ...

I meant amdump and amflush.

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



Re: Still having problems with ufsdump returning 3...

2002-04-03 Thread John R. Jackson

Hi!  I'm still having problems with ufsdump returning error code three, thus
causing the dumps to fail.  ...

? sendbackup: index tee cannot write [Broken pipe]
|   DUMP: Broken pipe
|   DUMP: The ENTIRE dump is aborted.
? index returned 1
sendbackup: error [/usr/sbin/ufsdump returned 3]

You're looking at the wrong end of the pipe.  The messages imply the
server side shut things down, which broke the pipe and filtered back
to the clients as bad news (there was nowhere to shove their data).

One scenerio would be running out of tape (or getting a tape error)
while doing a direct to tape backup.  The server would shut down its
side in that case and let the client fend for itself.

So what else is in the Amanda mail report?

Ricky

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



Re: I know this message... help restore entire system

2002-04-03 Thread John R. Jackson

... the system is configured as amanda client and has only one
partition / (root).  ...
Anyway, my question is: how do I restore the entire
system (in case I need to rplace or rebuild hard
drive)? I have recent full dumps of the server.

Amanda does not provide from bare metal restore features.  If it
crashes hard you'll need to get the client up enough (e.g. from your
original OS distribution materials) to get on the network and then you
can pull back the dump images and blat over the top of things.

I think there are some emergency boot packages available for Linux
that would help, but you'll have to poke around in those OS areas for
more information.

igor.

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



sendbackup with dumplevel 0 takes a while to startup :-{

2002-04-03 Thread Uncle George

according to the tar docs, the --listed-incremental will check on the
files listed in the file if the incremental file is not empty. I suppose
the listed-incremental file got filled during the sendsize proceedure?! 

During the sendbackup step, tar is apparently going through and checking
the list, as no data is being transmitted while tar is doing this check.
with a dtimeout of 30 minutes, i would get this unexpected timeout. 

Is this how its suppose to work for a level 0 dump? ( 4 hours
(wall-time) sendsize, ~4hours (wall-time) incremental check, and finally
the transfer of the data ( i suppose longer that 4 hours )) Is this how
it will work with other level dumps ( with the exception of the transfer
of data step) ?

/gat


10690 ?S  0:00 /usr/local/libexec/sendbackup
10691 ?S  0:00 /usr/local/libexec/sendbackup
10692 ?D  1:37 gtar --create --file - --directory /mnt/hdg3
--one-file-system --listed-incremental /usr/local/var/amanda/gnutar
10693 ?S  0:00 sh -c /bin/gtar -tf - 2/dev/null | sed -e
's/^\.//'
10694 ?S  0:01 /bin/gtar -tf - PWD=/tmp/amanda HOSTNAME=LX
MACHTYPE=alpha-redhat-linux-gnu SHLVL=1 SHELL=/bin/bash HOSTTYPE=alp
10695 ?S  0:00 sed -e s/^\.// PWD=/tmp/amanda HOSTNAME=LX
MACHTYPE=alpha-redhat-linux-gnu SHLVL=1 SHELL=/bin/bash HOSTTYPE=alph



Re: I know this message... help restore entire system

2002-04-03 Thread Lewis Watson


- Original Message - 
From: John R. Jackson [EMAIL PROTECTED]
To: Mr Igor Vertiletsky [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, April 03, 2002 6:52 PM
Subject: Re: I know this message... help restore entire system 


 ... the system is configured as amanda client and has only one
 partition / (root).  ...
 Anyway, my question is: how do I restore the entire
 system (in case I need to rplace or rebuild hard
 drive)? I have recent full dumps of the server.
 
 Amanda does not provide from bare metal restore features.  If it
 crashes hard you'll need to get the client up enough (e.g. from your
 original OS distribution materials) to get on the network and then you
 can pull back the dump images and blat over the top of things.


The kickstart config file works wonders when rebuilding. That will get the
bare metal install then use Amanda to restore the data. Works for me but I
would like to hear from others on this.

hth,
Lewis Watson


 






Re: I know this message... help restore entire system

2002-04-03 Thread Nick Russo

On Wed, 3 Apr 2002, Lewis Watson wrote:

 The kickstart config file works wonders when rebuilding. That will get the
 bare metal install then use Amanda to restore the data. Works for me but I
 would like to hear from others on this.

Since the question was about a bad drive, I assume there's a new
drive somewhere. I would mount it on a working client machine and
drop the restored data on it. Am I missing some complexity here?

Nick


 Nick Russo   email: [EMAIL PROTECTED]   phone: 773.702.3438
Computer Science Department   The University of Chicago
 Associate Director of Computing Systems, Systems Lead








Re: Unloading tapes when task done ?

2002-04-03 Thread Gene Heskett

On Wednesday 03 April 2002 08:58 am, Uncle George wrote:
Guess I'm from old school. Older 9trk drives when left on,
 continually have the vacuum on, and under constant tension. Its
 not healthy for the tape. Does that happen with a DLT tape, how
 about the DDS tapes. 

I'd have to assume that the DLT, which I know nothing about, 
shares such a feature with which nearly all other drives, 
including professional vcr's, that has a timeout of a minute or 
so, and, like the DDS drives I have, does a backout of the 
loading mechanism thereby removing the tape from contact with the 
scanner drum, usually with one supply or takeup spindle braked, 
and shuts the head drum down at the same time.  The drive then 
gradually cools to match its resting temps and the tape is mostly 
protected and not subjected to the internal heat rise the drive 
does when its active.  I do not consider the roughly 80 degree 
temps my tapes have when I eject the magazine as being that hard 
on the tape if the tape is not in motion.

I'd love to see the tapes stored and used at or slightly below 50 
degrees F, and 50% relative humidity as the tape is many times 
less abrasive then.  Some TV stations have even gone so far as to 
store their tapes in a small room adjacent to the control room 
which is maintained in the 40 degree and 40% range.   Everyting 
lasts longer, a lot longer.

The tape makers themselves recommend it too, and have data to 
show that a tape used and stored at 90/90 for temp and RH, is not 
just marginally more abrasive, but dozens of times more abrasive.

That effect was brought home to me many years ago when a 
headwheel failed in a now old 2 broadcast vtr.  The wheel had 
over 7000 hours of runtime on it, and the failure was in a rotary 
transformer.  We sent it back for repair.  It was re-installed 
and ran till something over 9000 runtime hours was used and it 
was worn out.  That headwheel came with a 200 hour prorated 
warranty as it had soft tips.  No, I didn't forget a decimal 
there.  The machine was in a precipitron clean, dry, cold room.  
Under more usual conditions I've seen them fail in 125 hours.

But we don't have those conditions inside the typical computers 
case, not by a long shot.

I would NOT like a live tape to be left
 in the drive for long periods of time. Who knows when a power
 failure will hit, who knows when the drive will go awol. An
 unloaded tape, immediately after backup, is safe from other
 folks, as well as the server, writing onto it.

I'd consider that a problem only in those drives like older 
QIC's, that leave everything engaged for long periods of time, 
thereby denting the drive rollers etc.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
98.7+% setiathome rank, not too shabby for a hillbilly



Re: A few interesting problems (tapeless, interactive restores, etc)

2002-04-03 Thread John R. Jackson

First off, for reasons beyond the scope of this email, my AMANDA server
has no tape device.  I am sending all backups to the holding disk.  We
also have a large IBM tape library running ADSM that I would like to
incorporate into my AMANDA backup strategy.  ...

Sounds like a perfect setup for the tapeio code in 2.4.3 (now in beta
test, but the tapeio stuff has been stable for a long time).  You would
set up a disk area to emulate a tape, then use the chg-multi tape changer
to move the data back and forth with your ADSM system.

The current (2.4.3 beta) chg-multi has a posteject hook to a script you
provide that could move the date into ADSM.  It would be easy to add a
preload step to do the other direction (don't know why I didn't think
of doing that when I did posteject).

A) I need a way of asking AMANDA, If I want foo file from 3/20/2000 on
machine bar, which dump 'directories' will I need?  ...

The tapeio code would take care of this.  Amanda would tell you you
needed tapes A, B and C, which would map directly to your ADSM areas.

If you don't go with tapeio, then I think amadmin config find ...
is what you'll want.  You may also need to be a bit sneaky about the data
motion to ADSM and leave the names and holding disk directories behind,
but truncate the files to zero length, or, worst case, truncate them to
just their 32 KByte header.  I'm pretty sure that would fool amrecover
sufficiently into using them (obviously, you'd have to reload the rest
of the data before turning the restore completely loose).

Greg Mohney

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



Re: sendbackup with dumplevel 0 takes a while to startup :-{

2002-04-03 Thread John R. Jackson

according to the tar docs, the --listed-incremental will check on the
files listed in the file if the incremental file is not empty. I suppose
the listed-incremental file got filled during the sendsize proceedure?! 

No.  It got filled by the previous sendbackup run (e.g. yesterday).

And, FYI, for a level 0 (full) dump, the listed incremental file comes
from /dev/null, i.e. it is used, but empty.

During the sendbackup step, tar is apparently going through and checking
the list, as no data is being transmitted while tar is doing this check.

I'm not sure exactly how tar does this.  You'd have to look at their
code or ask them.  I'd be surprised if it completely lost it for 30
minutes, though.

Is this how its suppose to work for a level 0 dump? ( 4 hours
(wall-time) sendsize, ~4hours (wall-time) incremental check, and finally
the transfer of the data ( i suppose longer that 4 hours ))  ...

Probably true.

Is this how
it will work with other level dumps ( with the exception of the transfer
of data step) ?

Yes.  Except Amanda may also request a third estimate one level higher
than the previous one if it might be time to bump (you can control this
with the bump* parameters).

You might want to consider using an alternate size calculation tool called
calcsize.  It's not well supported, and does not handle exclusion lists,
but does all the estimates at the same time so you might gain quite a
bit of time that way.

If you want to go this route, let me know and I'll find the postings
from a while back about turning it back on.

/gat

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



Re: Onstream ADR(2)60IDE

2002-04-03 Thread John R. Jackson

I'm new to this list ...

Welcome!

so sorry if it's a FAQ ...

It is, but that's OK :-).

Is there a tape definition
to use Onstream ADR(2)60IDE drives (30 / 60 GB) with Amanda?

In the FAQ off of the main www.amanda.org page:

  http://amanda.sourceforge.net/fom-serve/cache/293.html

You might also want to search the mailing list archives for references
to Onstream.  There have been quite a few problems reported, but also
some possible solutions (as I recall, certain microcode versions,
certain kernel versions, etc).

Gottfried

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



Amrestore and tar

2002-04-03 Thread Warren Flemmer

Greetings

I am having a problem with amrestore with backups made using gnutar.
I hope this is not in some doc I have missed or in the list archives, I
have spent a lot of time looking.

Lets say the server has the following hhd config:

FilesystemSize  Used Avail Use% Mounted on
/dev/sda8 251M  110M  127M  47% /
/dev/sda1  53M  3.8M   46M   8% /boot
/dev/sda6 3.1G  568M  2.4G  19% /home
/dev/sda5 3.1G  1.7G  1.2G  57% /usr
/dev/sda7 251M  123M  115M  52% /var

So I have a entry in disklist for the following (for the host)
client/root-tar
client/boot user-tar
client/home   user-tar
client/usr   user-tar
client/var   user-tar
Note: thay all use gtar (although confusing, the archives seem
to indicate gnutar is a better option than dump with 2.4.x kernals)
Also since amanda uses the --one-file-system option with gnutar
I have one entry per partition.

Now if amanda backs up more that one partition on the tape in one run, I 
could have
/boot
/
/home
say, on one tape, and in this order.

Now to restore I do the following on the client
ssh amandaserver amrestore -p /dev/nst0 host  host.tar
The first entry in the achive is extracted (/boot) and amrestore stops.

Now, if I were to say use the following in an attempt to get the / archive:
ssh amandaserver amrestore -p /dev/nst0 host /  host.tar
Once again /boot is extracted and amrestore stops once done.

So then, without having to extract the entire archive without amrestore,
how can I get the / partition from the tape as /boot is found first, matches
the diskname (at least in terms of regular expressions), extracts and stops?

Config is:
amanda 2.4.2p2
tar 1.13.19 (client) and tar 1.13.25 (server)
(BTW, will change all to 1.13.25 as I am still missing files with 
1.13.19, ie on this
host 823megs off 1.7gigs in usr was backed up :-( , clients with 1.13.25
seem to be fine)

Regards
Warren