Re: Lables and Force

2004-03-24 Thread Stefan G. Weichinger
Hi, Brendon,

on Mittwoch, 24. März 2004 at 08:46 you wrote to amanda-users:

BS Hi all,

BS I am having a small struggle with Amanda. The problem is that I have
BS labled the tapes Monday - Friday. In the case like Monday which was a
BS public holiday, Mondays backup didn't run. This morning it should have
BS run Tuesday's backup but it's still looking for Monday's tape. I have
BS rum an amflush and amcleanup. This however doesn't help. How do I
BS get Amanda to skip a day and backup for the current day? Also, how do
BS I force a backup, even though it expects a labled tape. I know this
BS sounds like the same question but it's not.

As this is still a very common question when it comes to AMANDA there
is a document called TOP-TEN-QUESTIONS. It could be found in the
archives of this list and is already part of the AMANDA-CVS.

I have put it up at
http://www.oops.co.at/oops_technical_amanda_contrib.htm until the next
stable release of AMANDA will be available.

Look for the friday-tape-question, it's the third section.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]







dump summary in megabytes?

2004-03-24 Thread Anne Strikwerda
Title: Bericht



Hi,

In the dump 
summary in Amanda's mail report I'd like to see megabytes instead of kilobytes? 
Can I change this easily?

thanks,
Anne


Re: Lables and Force

2004-03-24 Thread Brendon Standing
 As this is still a very common question when it comes to AMANDA there
 is a document called TOP-TEN-QUESTIONS. It could be found in the
 archives of this list and is already part of the AMANDA-CVS.
 
 I have put it up at
 http://www.oops.co.at/oops_technical_amanda_contrib.htm until the next
 stable release of AMANDA will be available.

 Look for the friday-tape-question, it's the third section.

Thanks, This helps and it doesn't. So you cannot force a dump? Their
answer was no and yes, and their yes answer was about an incremental
backup that was larger than normal. 

-- 
Regards,

Brendon Standing
Senior Networks Administrator
Club Technology
+27 31 7177648




Re: Lables and Force

2004-03-24 Thread Stefan G. Weichinger
Hi, Brendon ,

on Mittwoch, 24. März 2004 at 09:53 you wrote to amanda-users:

 Look for the friday-tape-question, it's the third section.

BS Thanks, This helps and it doesn't. So you cannot force a dump? Their
BS answer was no and yes, and their yes answer was about an incremental
BS backup that was larger than normal.

It helps for the first question, I assume.

The meaning of force with AMANDA is that you can force a full dump
of a filesystem via amadmin.

Use

amadmin conf force [hostname [disks]* ]+

for this.

You asked

 Also, how do
 I force a backup, even though it expects a labled tape.

What do you mean? AMANDA always expects a labelled tape. It does not
use tapes without label.

I don't understand that question well enough to help you.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]







Re: Lables and Force

2004-03-24 Thread Brendon Standing

 
  Also, how do
  I force a backup, even though it expects a labled tape.
 
 What do you mean? AMANDA always expects a labelled tape. It does not
 use tapes without label.
 
 I don't understand that question well enough to help you.

If you saying that AMANDA doesn't use tapes without a label, you have
answered my question. Although why does it say: This is not an amanda
tape. Insert tape labled Monday or a new tape , when it won't back up
onto a new tape.

Thanks for the feedback guys. I would like to see a nicer way around
doing a forced backup outside of ones cycle.

-- 
Regards,

Brendon Standing
Senior Networks Administrator
Club Technology
+27 31 7177648




Re: Lables and Force

2004-03-24 Thread Stefan G. Weichinger
Hi, Brendon,

on Mittwoch, 24. März 2004 at 10:31 you wrote to amanda-users:

 What do you mean? AMANDA always expects a labelled tape. It does not
 use tapes without label.
 
 I don't understand that question well enough to help you.

BS If you saying that AMANDA doesn't use tapes without a label, you have
BS answered my question. Although why does it say: This is not an amanda
BS tape. Insert tape labled Monday or a new tape , when it won't back up
BS onto a new tape.

It says Give me the tape MONDAY I already have in my list or
add/label a new one. Maybe misleading, ok ...

If you read your amanda.conf, there is the labelstr-parameter that
says :

 labelstr [EMAIL PROTECTED]@[0-9][0-9]*$  # label constraint regex: all tapes 
 must match

All tapes must match. Quite explicit to me.

BS Thanks for the feedback guys. I would like to see a nicer way around
BS doing a forced backup outside of ones cycle.

What is bad with amadmin force?
What is your goal?

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]







Re: Lables and Force

2004-03-24 Thread Paul Bijnens
Brendon Standing wrote:

Also, how do
I force a backup, even though it expects a labled tape.
What do you mean? AMANDA always expects a labelled tape. It does not
use tapes without label.
I don't understand that question well enough to help you.


If you saying that AMANDA doesn't use tapes without a label, you have
answered my question. Although why does it say: This is not an amanda
tape. Insert tape labled Monday or a new tape , when it won't back up
onto a new tape.
You first have to label a tape, and that label has to be unique too,
even for a new tape (new means, labeled, but not yet used to backup).
It's not a good scheme to label your tapes Monday-Friday, as you
have already noticed.
But if your really, really want to do want you intend to do (skip the
monday tape), then you can lower your tapeycle by one (but keep the
real amount of tapes).
The tapecycle is the number of tapes that are active.  If you have
a tapecycle of 4 tapes, and you have 5 tapes, than you can feed amanda
any tape of the last two tapes.  Amanda will ask for the oldest one, but 
accepts the last-but-one too, but not one of the 4 most recently
used tapes.



Thanks for the feedback guys. I would like to see a nicer way around
doing a forced backup outside of ones cycle.


--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***


Re: Lables and Force

2004-03-24 Thread Gene Heskett
On Wednesday 24 March 2004 02:46, Brendon Standing wrote:
Hi all,

I am having a small struggle with Amanda. The problem is that I have
labled the tapes Monday - Friday. In the case like Monday which was
 a public holiday, Mondays backup didn't run. This morning it should
 have run Tuesday's backup but it's still looking for Monday's tape.
 I have rum an amflush and amcleanup. This however doesn't help.
 How do I get Amanda to skip a day and backup for the current day?
 Also, how do I force a backup, even though it expects a labled
 tape. I know this sounds like the same question but it's not.

Thanks.

Amanda uses the tapes in rotation, and you nameing convention is 
purely arbitray to amanda, who other than useing monday as a day when 
she should have been run in her calculations of what to back up on 
this run, doesn't care.  Just go ahead and feed her mondays tape and 
she'll happily purr along and do the job for you.

This is why its rather pointless to name your tapes by the day of the 
week, they'll be out of whack the first time your schedule hiccups.

It takes a while before most folks get out of the habit of trying to 
tell amanda what to do.  Amanda will guard your data just fine, but 
the routines themselves have no idea of what day of the week it is.

-- 
Cheers, Gene
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.


Re: Lables and Force

2004-03-24 Thread Gene Heskett
On Wednesday 24 March 2004 03:53, Brendon Standing wrote:
 As this is still a very common question when it comes to AMANDA
 there is a document called TOP-TEN-QUESTIONS. It could be found in
 the archives of this list and is already part of the AMANDA-CVS.

 I have put it up at
 http://www.oops.co.at/oops_technical_amanda_contrib.htm until the
 next stable release of AMANDA will be available.

 Look for the friday-tape-question, it's the third section.

Thanks, This helps and it doesn't. So you cannot force a dump? Their
answer was no and yes, and their yes answer was about an incremental
backup that was larger than normal.

That would probably be correct.  You gave amanda a value for the 
dumpcycle, normally considered as number of days.  You also gave her 
a 'runspercycle' I assume.  If 'dumpcycle' is 7, and 'runspercycle' 
is 5, then amanda knows she has to schedule so that in 7 days, but 
only 5 runs, she must do a full on each and every entry in the 
disklist within that 7 elapsed days, with only 5 runs to do it in.
If you have a changer robot, so that amanda can use more than one 
tape, it might be helpfull when you have a makeup tuesday, to let her 
use a second tape by setting runtapes to 2 just for that tuesday run.

If you have holding disk space enough to hold the backup, read those 
portions of the docs carefully, then it could have run on monday 
normally, and you could have flushed it first thing tuesday (to the 
mondays tape it was looking for) and all would be well again.

OTOH, if you have the changer, why not just go ahead and leave the 
crontab entry alone  let her do a monday backup even if it was a 
holiday?

The acronym for amanda is Advanced Maryland Automatic Network Disk 
Archiver.  Note the Automatic.  If left to settle into a routine 
without any interference from us, amanda will, after a couple of 
dumpcycles to get things figured out, be as happy as can be.  She 
doesn't take holidays off, doesn't ask for a raise or longer coffee 
breaks, what more could one ask? :-)

-- 
Cheers, Gene
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.


Annoying

2004-03-24 Thread Brendon Standing
Hi all,

I am a cpio man, and am used to getting a backup to do what I want it to
(IE flexible, without to many complications).
This is why Amanda is irritating me at the moment. Earlier I had the
problem where I was being ask for Monday's tape (Which was a public
holiday and so didn't run). After seeking your advise, I realized that
Amanda needed to run with Labels. I got a hold of Monday's tape which is
held offsite in the attempt to keep Amanda happy with the idea of also
running Tuesday backup afterwards.

However when trying to backup (# amdump CLG), I am receiving the error:
*** A TAPE ERROR OCCURRED: [tape_rdlabel: tape open: /dev/nsa1: Device
not configured].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: MONDAY.

I then tried to flush to tape (# amflush CLG) and get the error:*** A
TAPE ERROR OCCURRED: [tape_rdlabel: tape open: /dev/nsa1: Device not
configured].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: MONDAY.

Aa!!!

-- 
Regards,

Brendon Standing
Senior Networks Administrator
Club Technology
+27 31 7177648




Re: Annoying

2004-03-24 Thread Stefan G. Weichinger
Hi, Brendon Standing,

on Mittwoch, 24. März 2004 at 13:25 you wrote to amanda-users:

BS However when trying to backup (# amdump CLG), I am receiving the error:
BS *** A TAPE ERROR OCCURRED: [tape_rdlabel: tape open: /dev/nsa1: Device
BS not configured].

This is not an AMANDA-problem but a problem in your system's
configuration.

Make sure that you can access your tapes via a
nonrewinding-device-file and put that one into amanda.conf.

Look out for permissions.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]







Re: Annoying

2004-03-24 Thread Brendon Standing

On Wed, 2004-03-24 at 14:37, Stefan G. Weichinger wrote:
 Hi, Brendon Standing,
 
 on Mittwoch, 24. März 2004 at 13:25 you wrote to amanda-users:
 
 BS However when trying to backup (# amdump CLG), I am receiving the error:
 BS *** A TAPE ERROR OCCURRED: [tape_rdlabel: tape open: /dev/nsa1: Device
 BS not configured].
 
 This is not an AMANDA-problem but a problem in your system's
 configuration.
 
 Make sure that you can access your tapes via a
 nonrewinding-device-file and put that one into amanda.conf.
 
 Look out for permissions.

Hi, thanks for your response.
It's the same device that's been working for a couple of weeks now. I
miss one day's backup and the things gone all skrewy on me. I check the
permissions which usually effect /var/log/Group Name, and it's fine. I
even change ownership after each dump to make sure.

o o
 -

-- 
Regards,

Brendon Standing
Senior Networks Administrator
Club Technology
+27 31 7177648





Re: Annoying

2004-03-24 Thread Paul Bijnens
Brendon Standing wrote:

I am a cpio man, and am used to getting a backup to do what I want it to
(IE flexible, without to many complications).
Well, I'm a cpio man too :-)  That's why I switched to amanda, i.e. 
flexible, without too many complications.

You do realize that a tape label is just a sequence of bytes (32K by 
default) that identifies this tape to amanda.  You'll be thankful the
next time you forget your tape in the drive that contained all the
data for your nobelprize project.

However when trying to backup (# amdump CLG), I am receiving the error:
*** A TAPE ERROR OCCURRED: [tape_rdlabel: tape open: /dev/nsa1: Device
not configured].
This seems to be a hardware problem/configuration.
Are sure the tapedevice is /dev/nsa1 ?

Aa!!!
What gives:   mt -t /dev/nsa1 status  ?
Did you try with a scratch tape (not a tape labelled for amanda?)
find /tmp -depth -print | cpio -ocv /dev/nsa1

(using the familiar cpio way to test things out.)

--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***


Re: several questions

2004-03-24 Thread Jon LaBadie
On Wed, Mar 24, 2004 at 02:46:08PM +0800, Mathias Koerber wrote:
 
 d) I was looking into pre-post dump actions (eg to stop a database or email 
 delivery)
   I found the tips to write a specialized tar (amgtar) script which does 
 this.
   My question however is whether the protocol between server and client 
 could
   handle this, or at least handle whether a pre-post function is to be 
 called and
   its results etc.
 
   I understand that security is an issue, which means that which scripts 
 are allowed to
   run on each client should be controlled on that client itself, which 
 speaks for a
   local amgtar.
 
   Does anyone already have such a script which is flexible to support 
 several pre/post
   dump (and pre/post estimate?) scripts as well as handles errors in such 
 scripts?


Quite a while ago JRJ posted the attached readme and wrapper script.
I've not used them, just still have them available.


-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)
Subject: Re: Synchronizing Amanda with Applications 

I looked at the archives.  I found some references to such wrappers,
but I've failed to find a good example of one, and what needs to be done
on which machine (client/server).

OK, you asked for it :-).

Some notes on the following over-engineered, under-tested, script:

  * It has **NOT** been run in a full Amanda setup, other than what
little I did to make sure syntax was right and the general flow
worked.

  * The script uses **EXAMPLE** execution point functions (see the code).
You **WILL** have to change it to do what you want (and remove what
you don't).

  * There are definitions of the Amanda debug directory (e.g. /tmp/amanda)
and path to GNU tar (on the client) in the first few lines that may
need to be tweaked for your environment.

  * It is written in ksh (although now that I think about it, I probably
could have used Perl).  Hopefully the examples and your own shell
coding experience will be sufficient to fit in what you need, but
if you want some help, ask me offline.

The idea is to install this on the client and build Amanda there
using --with-gnutar=path-to-script.  Then set up the disks you want
to use this wrapper with GNU tar as the dump program in disklist and
add execution point functions (see the code) to the script to do what
you need.

Note that the script doesn't have to actually use GNU tar -- that's just
the trick to get Amanda to call it with a set of arguments that are easy
to decipher.  You can use a run_* function to use whatever dump program
you want, as long as it generates an estimate to stdout that Amanda can
parse and sends the actual dump image to stdout.

Note also that compression is a separate step Amanda will tack on to the
stdout of this script (or not).  If you want to do your own compression,
add it to the script and tell Amanda compress none.

Then test it at least once :-).  If you set the DEBUG environment variable
to print (or echo -- same difference), the script will run but not
execute anything (although you'll have to set up your own functions to
follow the examples in the code).  Here is a sample test line I used
(using ksh as a login shell):

  DEBUG=print gtar-wrapper.ksh \
  --directory /home/HomeAC \
  --file - \
  .

Amanda will pass whatever you set in disklist as the --directory argument.
To test estimates, change - to /dev/null for the --file argument.

Amanda passes a mess of other parameters, but only --directory and
--file are of interest to the script.  If you do any significant argument
processing, make sure you don't loose anything (see function do_home in
the script).

I think.  :-)

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

** Additional notes -- 12-Sep-01 **

Fixed some truly silly bugs.  Rewrote enough of the code to be able to
run under bash as well as ksh.
#!/bin/ksh

###
# This script is called by an Amanda client to run GNU tar.  We look
# through the arguments for what is being processed and (optionally)
# run extra things before and/or after GNU tar, or alter the actual
# command run (e.g. different GNU tar flags and options or a completely
# different program).
#
# Remember that this script runs as root under the Amanda runtar program.
# Exercise appropriate caution.
#
# To test, run with the DEBUG environment variable set to echo.
# The command line need not look exactly like what Amanda issues, but
# must include the --directory dir-to-back-up and --file outfile
# flags as well as the trailing ..  To test an estimate, set the
# output file to /dev/null:
#
#   env DEBUG=echo ./gtar-wrapper.ksh --directory /whatever --file /dev/null .
#
# and to test the real dump, set it to -:
#
#   env DEBUG=echo ./gtar-wrapper.ksh --directory /whatever --file - .
#
# John R. Jackson ([EMAIL PROTECTED])
# Purdue University 

Re: Avg Dump Rate and Compression

2004-03-24 Thread Jonathan Dill
There are a few more things to try.  First, there may be an mt command 
to set the default compression for the drive--that will at least help 
make sure if you use some new tapes, they will get started with the 
correct compression.  The tricky part is that some drives, such as 8mm, 
use the density to set the compression and ignore the compression 
command.  You can usually get some ideas by looking at the output of mt 
status.  Under Linux, the commands you want would be something like mt 
defcompress off and mt defdensity then the drive will (hopefully) use 
those settings by default when you load a new tape, and for some drives, 
may actually override what's on the tape that you load.  I have 
sometimes put these commands into one of the system startup scripts, 
such as /etc/rc.d/rc.local on Linux.

Second, some drives have dip switches that you can set to hard-disable 
compression.  For example, I had a Sony DDS4 autoloader that had dip 
switches to do that.  At least, the dip switches make it non-ambiguous 
what is going on.

Third, some drives may have (usually Windows-based) firmware utilities 
that will let you set the settings of the drive, sort of like software 
dip switches.  You would just need some Windows computer with a SCSI 
card in it, it wouldn't even have to be a good SCSI card just to send 
the commands to the drive as long as you have the right type of cable.  
The bad part is you have to disconnect the drive, possibly move it, and 
hook it up to the WIndows box.  Worst case, maybe you could get some 
sort of SCSI adapter for a laptop with WIndows, such as PCMCIA, USB, 
Firewire, or even Paralllel to SCSI adapter.

Fourth, some tape drives like AIT or AME (Mammoth) supposedly try to set 
the compression dynamically based on the data and don't care whatever 
you do to try to stop it--you would have to go to the manufacturer and 
look up the specs for the drive to find out if it does that.

Lastly, when I have run into this problem, I usually have done this, but 
wonder if it could have caused problems:

# load the tape
mt compress off
amrmtape config label
amlabel config label
If you're going to be doing this to a bunch of tapes in an autoloader, 
it probably would be easier to script the dd command that Gene 
described, because you just dump the header to a temp file and the 
script doesn't have to try to parse what's in the temp file to figure 
out what the tape should be called.

Good luck!

Gene Heskett wrote:

The only way I know of to fix such a tape is:
rewind it
read out the label to a scratch file using dd
rewind it again
turn the compression off with mt -f device whatever turns it off
dd that scratch file back to the tape using the non-rewinding device
dd at least enough data from /dev/zero to force the drive to flush its 
buffers.  This will force the drive to turn the header compression 
flag off and that tape will not be compressed again unless you turn 
compression back on.
 

--jonathan


desaster recovery

2004-03-24 Thread pascal thomas
Hallo everyone,
I´d like to know if it is possible to prepare a floppy-disk to reinstall an OS with 
it. E.g. a harddisk crashs and a full dump has been made before of every partition. I 
want to use a new PC with a nonformated harddisk drive then insert a floppy-disk and 
run amanda. Is that possible and if yes, how?

Maybe that question is somehow crazy but that´s what they want me offer them at my 
practical training. I have no idea.

With regards 
Pascal (Köln, Collogne)




selfcheck reply timed out

2004-03-24 Thread Pablo Quinta Vidal
Hi list!!!

I have my amanda configureted as Diaria and when it check the clients hosts
its tell me:

WARNING: medulio: selfcheck reply timed out.

medulio is the server and the only client.
I have the NIS deactivated because doesn´t works well. Should it be the 
error??

Thanks

_
Reparaciones, servicios a domicilio, empresas, profesionales... Todo en la 
guía telefónica de QDQ. http://qdq.msn.es/msn.cfm



RE: disaster recovery

2004-03-24 Thread Gavin Henry
if you are running a redhat machine or fedora you have:

kickstart. 

This will automate everything





Re: selfcheck reply timed out

2004-03-24 Thread Joshua Baker-LePain
On Wed, 24 Mar 2004 at 4:40pm, Pablo Quinta Vidal wrote

 I have my amanda configureted as Diaria and when it check the clients hosts
 its tell me:
 
 
 WARNING: medulio: selfcheck reply timed out.
 
 
 medulio is the server and the only client.
 I have the NIS deactivated because doesn´t works well. Should it be the 
 error??

Doubtful.  Do any files appear in /tmp/amanda?  Specifically 
/tmp/amanda/amandad*debug would be helpful.  What OS are you using?  Have 
you setup (x)inetd appropriately?

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



Re: desaster recovery

2004-03-24 Thread Joshua Baker-LePain
On Wed, 24 Mar 2004 at 4:47pm, pascal thomas wrote

 I´d like to know if it is possible to prepare a floppy-disk to 
 reinstall an OS with it. E.g. a harddisk crashs and a full dump has been 
 made before of every partition. I want to use a new PC with a 
 nonformated harddisk drive then insert a floppy-disk and run amanda. Is 
 that possible and if yes, how?

I'm assuming your OS is Linux here.  Look at Linux-on-CD kits like 
Knoppix.  I don't know if Knoppix includes the amanda tools, but even if 
it doesn't you can get your images off the tapes with dd and mt.

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



Re: desaster recovery

2004-03-24 Thread Stefan G. Weichinger
Hi, pascal,

on Mittwoch, 24. März 2004 at 16:47 you wrote to amanda-users:

pt Hallo everyone,
pt I´d like to know if it is possible to prepare a floppy-disk
pt to reinstall an OS with it. E.g. a harddisk crashs and a full dump
pt has been made before of every partition. I want to use a new PC
pt with a nonformated harddisk drive then insert a floppy-disk and
pt run amanda. Is that possible and if yes, how?

pt Maybe that question is somehow crazy but that´s what they
pt want me offer them at my practical training. I have no idea.

If it doesn't have to be exactly a floppy, you could pack your own
version of Knoppix with amanda-binaries on it. If you regularly rsync
stuff like curinfo and index-files to another host, you could provide
them to the Knoppix-CD via USB-stick.

Would be an interesting solution, I think ...

There are linux-boot-floppies like tomsrtbt, which you could use to
restore from tapes via mt and dd ...

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]







Re: selfcheck reply timed out

2004-03-24 Thread Joshua Baker-LePain
On Wed, 24 Mar 2004 at 5:26pm, Pablo Quinta Vidal wrote

 Doubtful.  Do any files appear in /tmp/amanda?  Specifically
 /tmp/amanda/amandad*debug would be helpful.  What OS are you using?  Have
 you setup (x)inetd appropriately?
 
 I´m running AMANDA in Debian with kernel 2.4.20. The inetd is allright but 
 in a file in /tmp/amanda
 appears this:
 
 amandad: time 0.011: sending ack:
 
 amanda 2.4 ACK HANDLE 000-403B0508 SEQ 1078488172
 
 
 amandad: error [getpwuid(-1) fails]
 amandad: time 0.025: error [getpwuid(-1) fails]
 amandad: pid 2179 finish time Thu Mar 4 12:50:02 2004
 
 
 Remembet I have the NIS stopped.

Then you need to either fix NIS or define the amanda user locally on the 
server.

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



Re: selfcheck reply timed out

2004-03-24 Thread Pablo Quinta Vidal
Doubtful.  Do any files appear in /tmp/amanda?  Specifically
/tmp/amanda/amandad*debug would be helpful.  What OS are you using?  Have
you setup (x)inetd appropriately?
I´m running AMANDA in Debian with kernel 2.4.20. The inetd is allright but 
in a file in /tmp/amanda
appears this:

amandad: time 0.011: sending ack:

amanda 2.4 ACK HANDLE 000-403B0508 SEQ 1078488172

amandad: error [getpwuid(-1) fails]
amandad: time 0.025: error [getpwuid(-1) fails]
amandad: pid 2179 finish time Thu Mar 4 12:50:02 2004
Remembet I have the NIS stopped.

_
¿Todavía no conoces el nuevo MSN Messenger? Descárgatelo gratis aquí. 
http://messenger.microsoft.com/es



Re: selfcheck reply timed out

2004-03-24 Thread Jonathan Dill
On Wed, 2004-03-24 at 11:30, Joshua Baker-LePain wrote:
  Remembet I have the NIS stopped.
 
 Then you need to either fix NIS or define the amanda user locally on the 
 server.

My experience has been that on linux, NIS (via ypbind) is unreliable and
tends to crash, so I always put the amanda user in the local passwd file
to make sure that backups don't fail even if ypbind craps out.  I think
part of my problem has been that I'm using SGI IRIX as NIS servers, and
Linux as NIS clients, and something between them is not 100% compatible.

If you really want to rely on NIS, I would suggest setting up some kind
of a watchdog to restart ypbind if it fails.  In fact, I think I am
going to look into that option right now, it would fix some of the
problems/complaints that I have had, like occasional problems with
people not being able to login.

-- 
Jonathan Dill [EMAIL PROTECTED]



Re: selfcheck reply timed out

2004-03-24 Thread Pablo Quinta Vidal
 Doubtful.  Do any files appear in /tmp/amanda?  Specifically
 /tmp/amanda/amandad*debug would be helpful.  What OS are you using?  
Have
 you setup (x)inetd appropriately?

 I´m running AMANDA in Debian with kernel 2.4.20. The inetd is allright 
but
 in a file in /tmp/amanda
 appears this:

 amandad: time 0.011: sending ack:
 
 amanda 2.4 ACK HANDLE 000-403B0508 SEQ 1078488172
 

 amandad: error [getpwuid(-1) fails]
 amandad: time 0.025: error [getpwuid(-1) fails]
 amandad: pid 2179 finish time Thu Mar 4 12:50:02 2004


 Remembet I have the NIS stopped.

Then you need to either fix NIS or define the amanda user locally on the
server.
I´ve NIS running without errors and now the message is  selfcheck request 
timed out
I had this problem earlier and when I solve this then came selfcheck reply 
timed out and now again
the old problem.
I checked the help ind docs/FAQ but it doesn´t work.
Help please and sorry if I´m tedious!!
Thanks

_
Dale rienda suelta a tu tiempo libre. Encuentra mil ideas para exprimir tu 
ocio con MSN Entretenimiento. http://entretenimiento.msn.es/



Re: selfcheck reply timed out

2004-03-24 Thread Jonathan Dill
Maybe there are some zombie amanda processes hanging in the
background.  Try looking at ps to see if any processes need to be
killed.  Look at the files in /tmp/amanda on the server and the clients
to see if there are any clues.  Try rebooting and see if the problem
still persists.

On Wed, 2004-03-24 at 13:09, Pablo Quinta Vidal wrote:
 I´ve NIS running without errors and now the message is  selfcheck request 
 timed out
 I had this problem earlier and when I solve this then came selfcheck reply 
 timed out and now again
 the old problem.
 I checked the help ind docs/FAQ but it doesn´t work.
 Help please and sorry if I´m tedious!!
 Thanks

-- 
Jonathan Dill [EMAIL PROTECTED]




TL891 plus fibre channel question

2004-03-24 Thread Larson, Thomas - DFI
I am currently trying to configure amanda for our department.  The tape
library we have is a Compaq TL891 with two tape drives and 26 storage slots.
I have it connected via a Compaq fibre channel tape controller(FCTC) to a
fedora linux box.

I can view the status of the tape library with an mtx -f /dev/sg0 status.  
Contents of my /proc/scsi/scsi show that fedora sees both the tape changer
and both drives.  The drives appear to be accessible via /dev/st0, /dev/st1,
/dev/nst0, and /dev/nst1 

My question is this:

I've reviewed the TAPE.CHANGERS documentation that is included with the
amanda binaries.  However it is not clear which changer configuration is
best suited to this hardware.  All I know is mtx commands that actually try
to interact with the hardware confuse the FCTC to the point of needing to be
rebooted.  Mtx staus commands are ok, but I tried configuring the chg-zd-mtx
changer portion of amanda and that kills it pretty quickly.

If anyone has experience configuring amanda for this hardware, I'd
appreciate any direction you could provide.  Thank you.

Thomas Larson 
System Administrator 
WI Dept of Financial Institutions 
[EMAIL PROTECTED] 
(608) 261-9545