Re: Compression Ratio misprinting on labels

2004-08-25 Thread Paul Bijnens
Phil Homewood wrote:
Upgraded one box to 2.4.4p3. amreport still shows the
bogus labels when run against a log generated under
2.4.4p2. Tonight I'll see what it does when it creates
the log itself. :-)
Do you mean you upgraded a client?  Just the amanda server is fine.
The 2.4.4p3 server is compatible with older clients.

(Does amreport pull its stats from anywhere but the logfile?)
It also needs the amanda.conf and the disklist file.
I should delve into the source code to find out what exact information
it gets from there (e.g. columnspec, mailadress come to mind).
If you like, you may send me such a log file, so I could have a look
at the strange things it calculates.
--
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: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header

2004-08-25 Thread Paul Bijnens
Ranveer Attalia wrote:
SOrry about this, but I'm having a nightmare I attempted the amrecover
again last night on a file and it worked. 
I took the tapes out of the drive and put in the daily incremental tapes
and hashed out the server that failed so it doesnt attempt to back it
up.

However, this morning I have tried to do a amrestore but when I run an
amadmin Weekly telhp6 /opt it is telling me its not a dump list (what
does this mean? nothing has changed on the tapes since last night!!)
No dump to list (real error message) has a different meaning than
not a dump list (what you seem to be reading).  It means that amadmin
is unable to find information about any dumps (== backups).
And that's because:
AMANDA SERVER:
$  amadmin Weekly find telhp6
Warning: no log files found for tape Fri4.1 written 2004-04-23
Warning: no log files found for tape Mar0.1 written 2004-03-28
Warning: no log files found for tape Weekly5 written 2004-02-28
Warning: no log files found for tape Weekly4 written 2004-02-14
Warning: no log files found for tape Weekly3 written 2004-02-07
Warning: no log files found for tape Weekly2 written 2004-01-30
Warning: no log files found for tape Weekly1 written 2004-01-23 Scanning
/amanda...
Scanning /amanda1...
No dump to list
$
Yes, that's because the log files are gone.  And the log files are
what amadmin find uses go find out which tape contains what :-)
Don't remove the log files!
The lucky thing is that amanda does not DEPEND on the log files
to be able to restore anything.  It just becomes a little less
easy.

$mtx load 1
$ amtape Weekly current
amtape: scanning current slot in tape-changer rack:
slot 2: date 20040820 label Fri3.2
$ mt -f /dev/rmt/1ubn rew
AMANDA CLIENT:
#remsh tsssun1 -l amanda -n /opt/amanda/sbin/amrestore -p /dev/rmt/1ubn
telhp6 /opt | restore rbf 2 -
amrestore:   0: skipping start of tape: date 20040820 label Fri3.2
amrestore:   1: skipping pedlinux1._scratch.20040820.0
amrestore:   2: skipping telsun4._projects.20040820.0
amrestore:   3: skipping telhp3._home.20040820.0
amrestore:   4: restoring telhp6._opt.20040820.0
Tape is not a dump tape
# 
Ok. Now it did find the correct tape, and did find the relevant
backup image (number 4 it seems).
Was this backup made by dump, then you need restore, but if
it was created by gnutar than then you gnutar to restore.

HELP PLEASE! I NEED TO GET THIS SORTED FAST! 
Welcome to the wonderful stress of restoring  :-)
Tip:  first be calm, think slowly, better take 5 minutes
more to investigate something than rushing and panicking.
Even take half an hour to read the documentation again!
Just ignore the users (temporarily).
--
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  *
***



amanda package

2004-08-25 Thread Kaushal Shriyan
Can i have the rpms of amanda-2.4.4p3 for upgrading my amanda package
-- 
Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318
Cell : +91-9820367783




Re: Compression Ratio misprinting on labels

2004-08-25 Thread Phil Homewood
Paul Bijnens wrote:
 Upgraded one box to 2.4.4p3. amreport still shows the
 bogus labels when run against a log generated under
 2.4.4p2. Tonight I'll see what it does when it creates
 the log itself. :-)
 
 Do you mean you upgraded a client?  Just the amanda server is fine.
 The 2.4.4p3 server is compatible with older clients.

Sorry, yes, I meant I upgraded the server. (one box here
being one of two amanda servers.)

 (Does amreport pull its stats from anywhere but the logfile?)
 
 It also needs the amanda.conf and the disklist file.

Yup, but there are no stats there.

 I should delve into the source code to find out what exact information
 it gets from there (e.g. columnspec, mailadress come to mind).

My columnspec is unspecified (ie, default). (That was one
of the things I initially suspected -- a missing column width
causing a snprintf() to get confused, for example. Doesn't
appear to be the case.)

 If you like, you may send me such a log file, so I could have a look
 at the strange things it calculates.

We'll see what happens in tonight's run with 2.4.4p3 :-)
I did manage to whittle down the logs (trimming all but
one DLE from them) to a state where I could trigger the
bogus behaviour by changing only limited info. But I
didn't completely exhaust all the options there before
deciding that the upgrade to 2.4.4p3 was perhaps a better
idea. :-) It *looked* like it was getting the orig-kb
value from thin air, as changing that had no effect on
the label (but changing the kb did.) That's why I
asked about amreport pulling stats from other places.

But I'll explore that idea further tomorrow, if 2.4.4p3
still misbehaves.

The configs I'm using have grown up from (I think) 2.4.1
or thereabouts. They've been around (and been hacked up
occasionally) for several years. So there's possibly
something missing that 2.4.4p[23] expects to see...


Re: FW: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header

2004-08-25 Thread Paul Bijnens
Ranveer Attalia wrote:
I realised that I had commented out the WEEKLY/disklist (being over
cautius last night) so thats why there was no dump to list. When I do it
now - it works ok:
Fine.

Was this backup made by dump, then you need restore, but if it was
created by gnutar than then you gnutar to restore.

Looks like it was done by dump. Below is a cut of the WEEKLY/disklist
file for telhp6 and the WEEKLY/amanda.conf file. 
DISKLIST
...
telhp6 /opt always-full
...
define dumptype always-full {
global
comment Full dump of this filesystem always
compress none
index
priority high
dumpcycle 0
Unless dumptype global does not contains program GNUTAR, then
it is indeed dump.
You can also verify this on the amanda tape header, which contains
this information too!
mt -f /dev/rmt/1ubn rewind
mt -f /dev/rmt/1ubn fsf 4
dd bs=32k count=1 if=+dev+rmt/1ubn
and voila; you should see something like:
AMANDA: FILE 20040623 host /the/dir lev 0 comp N program /usr/bin/gtar
To restore, position tape at start of file and run:
dd if=tape bs=32k skip=1 | /usr/bin/gtar -f... -
But I guess you'll see restore instead of gtar.
Or do you see a variant of restore, like vxrestore?  See below.

When trying the amrestore its still complaining about Tape is not a
dump tape 
First you need to be sure about which program is generating that error
message.
I guess it is the restore command.
Try doing a strings -a /usr/sbin/restore and verify if there is
message Tape is not a dump tape.

How do I use GNUTAR (please plase give me an example using hostname:
telhp6,  partition: opt, amanda server: tsssun1 
(although I dont think its using GNUTAR from the info above)

as root:
cd /the/destination/folder
remsh ...amrestore-cmd-as-used-is-ok... | tar -xpvf -
But I believe you are correct in using restore.
Are you using the restore on the correct architecture?
You need restore from the HP-machine for HP-dumps, and if
the filesystem was a special format like veritas, you need
the corresponding restore for that filesystem.
The amanda tapeheader for that backup does contain that information!
Instead of reading the slow tape over and over again, you can
dump the backup image on a disk (leave out the -p from amrestore).
And then try to find out what kind of image it is, with e.g.
using file telhp6._opt.20040824.0, and trying tar and/or
restore to generate a table of contents.
Just ignore the users (temporarily)
I do that anyway  ;-) 
Its my boss I'm more worried about ! 
Never mind about him, especially in these cases.  (And he should know
that too!)
--
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  *
***



Amplot on letter-size paper?

2004-08-25 Thread KEVIN ZEMBOWER
I just started using amplot, and am having some difficulty. All my plots seem to be 
for legal size paper, 14 inches long. Any way to change them into letter? I don't see 
any text at the top, as the man page indicates; it runs off the page just above the 
'100%' in the holding disk area.

Thanks. I also can't figure out how to cause my printer to use legal paper. I've tried 
using 'mpage -bLegal' but it didn't work, but that's another problem.

Thanks for any suggestions.

-Kevin Zembower

-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD  21202
410-659-6139




Re: Input/output error attempting to run amlabel

2004-08-25 Thread Paul Bijnens
(I hate top posting, so I reordered the mail a little bit...)
(And I also hate long lines...)
KEVIN ZEMBOWER wrote:
Frazier Scott [EMAIL PROTECTED] 08/24/04 11:14PM 
Can anyone give me an idea why this might be occurring (see below)? 
Mandrake Linux 9.2, su'ed to the amanda user, all config files seem to
be set up OK, using chg-zd-mtx, tapetype set to the pv120t-dds4 found on
the faq-o-matic site, Dell PowerVault 120T AutoLoader with DDS-4 tapes. 
I am attempting to populate the tapelist (already touched the file). 
After I get this error, running mt -f /dev/nst0 status also gives me
 Input/output error.
Errors from mt indicate that the problem is completly outside amanda.
Any hints in /var/log/messages?
Is the tape still blinking when you type the command?  I mean,
maybe you type the commands too fast?

   If I then unload the tape using mtx -f /dev/sg5
unload, I can reload the tape using mtx -f /dev/sg5 load 1 and mt -f
/dev/nst0 status works fine.  I attempt to run amlabel again, and the
whole thing starts over again.
-bash-2.05b$ /usr/amanda/sbin/amlabel sunday amanda001 slot 1
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label, reading label: Input/output error
rewinding, writing label amanda001
amlabel: writing endmark: Input/output error

I think that the first error, when reading, is caused by trying to
read the label from a pristine tape, with nothing written on it. I get
this error all the time when I label new tapes. I just ignore it.
Correct.

There has recently been some discussion of this on this list, and I
may actually have this wrong. This is just my guess.
However, the second input/output error, when 'writing endmark,' I've
never seen before (I started writing this response before I noticed
this). Maybe someone else can help with that.
The second error is indeed unexepected.  But amlabel seems
not the cullprit, as even mt status gives an error?
Try to isolate the problem using simple commands
like dd bs=32k count=1 if=... of=..., and mt 

--
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: 'strange amanda header' errors

2004-08-25 Thread Scott Frisbie
 
  
Eric, Paul,  
Thanks for all your help. Looks like we have a tape drive that's 
going  
south on us from the checks we've run over the weekend. We've  
already got a new drive, just need to get it installed.  
Scott  
  
  
--- In [EMAIL PROTECTED], 
 Eric Siegerman [EMAIL PROTECTED]  
wrote:  
 On Fri, Aug 20, 2004 at 07:08:47AM +0800, Scott Frisbie wrote:  
  Ran the revised shell and am attaching it to the mail along 
with the  
other files.  
   
 Thanks.  Unfortunately, all it does is convince me that some  
 *really weird* stuff is going on :-(  
   
 Running the headers through od -c was to prove to us 
that what  
 you'd shown in your email is what was really there, as opposed 
to  
 having been further corrupted by cut-and-paste, CTRL-M's causing  
 parts of lines to be overwritten on the screen, etc.  
   
 I am now convinced that what you showed was for real.  Too bad; 
I  
 was really hoping that there were control characters in either  
 amanda.conf or disklist that were causing this.  There aren't.  
   
 Here are those headers, turned back into plain text, but with  
 non-printable characters turned into escape sequences:  
   
 AMANDA: TAPESTART DATE 20040810 TAPE BootCamp207\n\f\n  
AMANDA: FILE 20040810 192.168.3.224 /home/shared/perllib lev 
1  
compN program /bin/gtar\nTo restore,position tape at 
start of file and  
run:\n\tdd if=tapebs=32k skip\xBD1| /bin/gtar 
-f... -\n\f\n  
 AMANDA: FILE 20040810 nis /var/lib/dhcp lev 0 comp N program  
/bin/gtar\nTo restore, position tape at start\xA0of file and 
run:\n\tdd  
if=tape bs=32k skip=1 | /bin/gtar -f... -\n\f\n  
 AMANDA: FILE 20040810 intrepid /usr/shares/marketing lev 1  
compN program /bin/gtar\nTo restore,position tape at 
start of file and  
run:\n\tdd if=tapebs=32k skip\xBD1| /bin/gtar 
-f... -\n\f\n  
 AMANDA: FILE 20040810 cvs /etc lev 0 compN program  
/bin/gtar\nTo restore,position tape at start of file and 
run:\n\tdd  
if=tapebs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
AMANDA: FILE 20040810 intrepid 
/home/mailhub/scottf/recover_test  
lev 0 compN program /bin/gtar\nTo restore, position tape at 
start of file  
and run:\n\tdd if=tapebs=32k skip\xBD1| /bin/gtar 
-f... -\n\f\n  
AMANDA: FILE 20040810 192.168.3.224 
/home/odin/reports/scripts  
lev 1 compN program /bin/gtar\nTo restore,position tape 
at start of file  
and run:\n\tdd if=tapebs=32k skip\xBD1| /bin/gtar 
-f... -\n\f\n  
 AMANDA: FILE 20040810 nis /var/yp lev0 comp N program  
/bin/gtar\nTo restore, position\xA0tape at start\xA0of file and 
run:\n\tdd  
if=tape bs=32k skip=1| /bin/gtar -f... -\n\f\n  
 AMANDA: FILE 20040810 192.168.3.224 /home/odin/stats lev 1  
compN program /bin/gtar\nTo restore,position tape at 
start of file and  
run:\n\tdd if=tapebs=32k skip\xBD1| /bin/gtar 
-f... -\n\f\n  
AMANDA: FILE 20040810 nis /var/named lev 0 compN 
program  
/bin/gtar\nTo restore,position tape at start of file and 
run:\n\tdd  
if=tapebs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
AMANDA: FILE 20040810 intrepid /usr/shares/support lev 1 
compN  
program /bin/gtar\nTo restore, position tape at start of file and 
run:\n\tdd  
if=tape bs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
AMANDA: FILE 20040810 192.168.3.224 /etc lev 0 compN 
program  
/bin/gtar\nTo restore, position tape at start of file and run:\n\tdd 
if=tape  
bs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
 AMANDA: FILE 20040810 nis /etc lev 0 compN program  
/bin/gtar\nTo restore, position tape at start of file and run:\n\tdd  
if=tapebs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
AMANDA: FILE 20040810 intrepid /usr/shares/IT_Dept lev 0 
compN  
program /bin/gtar\nTo restore, position tape at start of file and 
run:\n\tdd  
if=tape bs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
 AMANDA: FILE 20040810 intrepid /home/amanda lev 1 comp N  
program /bin/gtar\nTo restore, position\xA0tape at start\xA0of file 
and  
run:\n\tdd if=tape bs=32k skip=1| /bin/gtar -f... 
-\n\f\n  
AMANDA: FILE 20040810 intrepid /home/archive lev 0 
compN  
program /bin/gtar\nTo restore, position tape at start of file and 
run:\n\tdd  
if=tape bs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
 AMANDA: FILE 20040810 intrepid /home/snips lev 0 compN  
program /bin/gtar\nTo restore, position tape at start of file and 
run:\n\tdd  
if=tape bs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
AMANDA: FILE 20040810 intrepid /home/os-iso lev1 comp 
N  
program /bin/gtar\nTo restore, position\xA0tape at start\xA0of file 
and  
run:\n\tdd if=tape bs=32k skip=1| /bin/gtar -f... 
-\n\f\n  
AMANDA: FILE 20040810 intrepid /home/sus lev 0 compN 
program  
/bin/gtar\nTo restore,position tape at start of file and 
run:\n\tdd  
if=tapebs=32k skip\xBD1| /bin/gtar -f... -\n\f\n  
AMANDA: FILE 20040810 intrepid /etc lev0 comp N 
program  
/bin/gtar\nTo restore, position\xA0tape at start of file and 
run:\n\tdd  
if=tape bs=32k skip=1| /bin/gtar -f... 

Re: advice please!

2004-08-25 Thread Maccy

Hi Paul,

Many thanks for your advice! It will be very useful.

 Ahh, nice set up, that's what I have and really like it.  Mine has a
 barcode reader in it too, though I've not spent the time to configure
 that yet (it's on the todo list when I find some more 'round tuits' :)

I'm not sure whether mine has one, if it does I'll get it up and running
somewhere down the line, have to concentrate on the basics first of course
:-)

 Not overly complicated, just run 2 different configurations.
 (I'm assuming that the Fri-Sun backups are meant for offsite storage ?)

They could be, although are not currently, no.

 The big problem is going to be your full dumps.  Do you really want
 to run a full dump Fri, Sat, and Sun?  Or do you just want to run a
 single full dump of the data allowing it to run over those 3 days?

I want to do the latter.

Can you explain more about the bumpsize?

Maccy


ibm ultrium lto library/tape loader using chg-zd-mtx (freebsd)(amanda 2.4.4)

2004-08-25 Thread Armand Sulter

I'm trying to get this puppy to work with
3 tapes for now, i can control the robot
fine with the mtx program but amanda keeps
giving me :

bash-2.04$ /usr/local/sbin/amlabel bef Test01 slot 2
amlabel: could not load slot 2: could not determine current slot, are you sure your 
drive slot is 2

I put the tape from slot 1 in the drive, it knows theres one
in slot 2 and 3 but it keeps complaining about the 'current' slot.

From what i can tell the output of the mtx command is in a format
the regex's from the glue script should match.

changer.conf

firstslot=1 # First slot
lastslot=3  # Last slot
cleanslot=-1# Don't use a cleaning tape slot
driveslot=0 # This is the slot of the drive
havereader=0# Do not use the barcode reader
autoclean=0 # Do not autoclean
offline_before_unload=0 # Does not require offline before unload
havebarcode=0

amanda.conf (snippet)
-
runtapes 1
tapedev /dev/pass2
changerdev  /dev/pass3
tapetype IBM-LTO3580

mtx results
-
bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 status
  Storage Changer /dev/pass3:1 Drives, 20 Slots ( 1 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag =
  Storage Element 1:Empty:VolumeTag=
  Storage Element 2:Full :VolumeTag=
  Storage Element 3:Full :VolumeTag=
  Storage Element 4:Empty:VolumeTag=
  Storage Element 5:Empty:VolumeTag=
  Storage Element 6:Empty:VolumeTag=
  Storage Element 7:Empty:VolumeTag=
  Storage Element 8:Empty:VolumeTag=
  Storage Element 9:Empty:VolumeTag=
  Storage Element 10:Empty:VolumeTag=
  Storage Element 11:Empty:VolumeTag=
  Storage Element 12:Empty:VolumeTag=
  Storage Element 13:Empty:VolumeTag=
  Storage Element 14:Empty:VolumeTag=
  Storage Element 15:Empty:VolumeTag=
  Storage Element 16:Empty:VolumeTag=
  Storage Element 17:Empty:VolumeTag=
  Storage Element 18:Empty:VolumeTag=
  Storage Element 19:Empty:VolumeTag=
  Storage Element 20 IMPORT/EXPORT:Empty:VolumeTag=


bash-2.04$ /usr/local/sbin/mtx -f /dev/pass2 inquiry
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULTRIUM-TD1 '
Revision: '12U2'
Attached Changer: No

bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 inquiry
Product Type: Medium Changer
Vendor ID: 'HP  '
Product ID: 'C7200   '
Revision: '126I'
Attached Changer: No

does anyone have any experience with these ?

With best regards,

Armand Sulter - Systems Administration

  ENTER.NET - The Road to the Internet Starts Here! (tm)
  (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED]




Restore buffer?

2004-08-25 Thread Darren Landrum
I am in charge of seeting up a new backup server for the County of Montrose, 
CO. My boss has asked me to put together a system that will allow us to 
buffer a restore job (say, grabbing a file from tape) before sending the file 
back to its proper place on a server.

The reason he feels this is necessary is so we can look at a file restored 
from tape before we destroy anything that might be on the server proper. That 
way, it can be confirmed by the user that this is indeed the file(s) they 
need restored before we commit to the final action.

Is Amanda capable of this kind of operation?

Thank you very much for your time.

-- 
Regards,
Darren Landrum
Montrose County IT



Re: ibm ultrium lto library/tape loader using chg-zd-mtx (freebsd)(amanda2.4.4)

2004-08-25 Thread Frazier Scott
Question:

What does
/usr/local/sbin/mt -f /dev/pass2 status
give you?


 Armand Sulter [EMAIL PROTECTED] 8/25/2004 9:31:28 AM 

I'm trying to get this puppy to work with
3 tapes for now, i can control the robot
fine with the mtx program but amanda keeps
giving me :

bash-2.04$ /usr/local/sbin/amlabel bef Test01 slot 2
amlabel: could not load slot 2: could not determine current slot, are
you sure your drive slot is 2

I put the tape from slot 1 in the drive, it knows theres one
in slot 2 and 3 but it keeps complaining about the 'current' slot.

From what i can tell the output of the mtx command is in a format
the regex's from the glue script should match.

changer.conf

firstslot=1 # First slot
lastslot=3  # Last slot
cleanslot=-1# Don't use a cleaning tape slot
driveslot=0 # This is the slot of the drive
havereader=0# Do not use the barcode reader
autoclean=0 # Do not autoclean
offline_before_unload=0 # Does not require offline before
unload
havebarcode=0

amanda.conf (snippet)
-
runtapes 1
tapedev /dev/pass2
changerdev  /dev/pass3
tapetype IBM-LTO3580

mtx results
-
bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 status
  Storage Changer /dev/pass3:1 Drives, 20 Slots ( 1 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag =
  Storage Element 1:Empty:VolumeTag=
  Storage Element 2:Full :VolumeTag=
  Storage Element 3:Full :VolumeTag=
  Storage Element 4:Empty:VolumeTag=
  Storage Element 5:Empty:VolumeTag=
  Storage Element 6:Empty:VolumeTag=
  Storage Element 7:Empty:VolumeTag=
  Storage Element 8:Empty:VolumeTag=
  Storage Element 9:Empty:VolumeTag=
  Storage Element 10:Empty:VolumeTag=
  Storage Element 11:Empty:VolumeTag=
  Storage Element 12:Empty:VolumeTag=
  Storage Element 13:Empty:VolumeTag=
  Storage Element 14:Empty:VolumeTag=
  Storage Element 15:Empty:VolumeTag=
  Storage Element 16:Empty:VolumeTag=
  Storage Element 17:Empty:VolumeTag=
  Storage Element 18:Empty:VolumeTag=
  Storage Element 19:Empty:VolumeTag=
  Storage Element 20 IMPORT/EXPORT:Empty:VolumeTag=


bash-2.04$ /usr/local/sbin/mtx -f /dev/pass2 inquiry
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULTRIUM-TD1 '
Revision: '12U2'
Attached Changer: No

bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 inquiry
Product Type: Medium Changer
Vendor ID: 'HP  '
Product ID: 'C7200   '
Revision: '126I'
Attached Changer: No

does anyone have any experience with these ?

With best regards,

Armand Sulter - Systems Administration

  ENTER.NET - The Road to the Internet Starts Here! (tm)
  (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED] 




Re: Restore buffer?

2004-08-25 Thread Eric Siegerman
On Wed, Aug 25, 2004 at 11:32:07AM -0600, Darren Landrum wrote:
 [restoring to a temporary location]
 
 Is Amanda capable of this kind of operation?

Yes.

And your boss is right :-)  When restoring individual files (as
opposed to disaster-recovering an entire partition), doing it
this way is much safer than restoring in place, and is often
recommended on this list.  Besides allowing you to inspect the
files, it guards against user error in doing the restore (e.g.
restoring files you didn't mean to, thereby clobbering the
current versions).

From amrecover(8):
   In  order  to  restore files in place [i.e. to do what you
   want *not* to do] you must invoke amrecover from the root of
   the backed up filesystem, or use lcd to move into that
   directory, otherwise a directory tree that resembles the
   backed up filesystem will be created in the current
   directory.
   [...]
   If you do not want to overwrite existing files, create a
   subdirectory to run amrecover from and then move the restored
   files afterward.

--

|  | /\
|-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau


Re: Restore buffer?

2004-08-25 Thread KEVIN ZEMBOWER
I have never bothered setting up or using the restore component of Amanda (amrestore). 
I dd the backup from the tape, uncompress if necessary and pipe to restore or tar -x. 
I put the restored file in my (root or amanda) directory and could then compare it to 
the existing file if I wanted to. In this sense, amanda can do what you require. This 
is done by a (skilled?) administrator, however. If users needed to do this, it might 
be too complex and done too infrequently for them to do without error.

Hope this helps.

-Kevin

-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD  21202
410-659-6139

 Darren Landrum [EMAIL PROTECTED] 08/25/04 01:32PM 
I am in charge of seeting up a new backup server for the County of Montrose, 
CO. My boss has asked me to put together a system that will allow us to 
buffer a restore job (say, grabbing a file from tape) before sending the file 
back to its proper place on a server.

The reason he feels this is necessary is so we can look at a file restored 
from tape before we destroy anything that might be on the server proper. That 
way, it can be confirmed by the user that this is indeed the file(s) they 
need restored before we commit to the final action.

Is Amanda capable of this kind of operation?

Thank you very much for your time.

-- 
Regards,
Darren Landrum
Montrose County IT





Re: Restore buffer?

2004-08-25 Thread Frank Smith
--On Wednesday, August 25, 2004 11:32:07 -0600 Darren Landrum [EMAIL PROTECTED] 
wrote:

 I am in charge of seeting up a new backup server for the County of Montrose, 
 CO. My boss has asked me to put together a system that will allow us to 
 buffer a restore job (say, grabbing a file from tape) before sending the file 
 back to its proper place on a server.
 
 The reason he feels this is necessary is so we can look at a file restored 
 from tape before we destroy anything that might be on the server proper. That 
 way, it can be confirmed by the user that this is indeed the file(s) they 
 need restored before we commit to the final action.
 
 Is Amanda capable of this kind of operation?

I almost always use Amanda this way, restoring into a scratch directory
and then moving the files to where they need to go.

Frank

 
 Thank you very much for your time.
 
 -- 
 Regards,
 Darren Landrum
 Montrose County IT



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



Re: ibm ultrium lto library/tape loader using chg-zd-mtx (freebsd)(amanda2.4.4)

2004-08-25 Thread Armand Sulter

It comes back with :

bash-2.04# mt -f /dev/pass2 status
mt: /dev/pass2: Operation not permitted

Are you saying i should be able to access
/dev/pass2 as a regular tape drive ?

i read somewhere sometimes you have to use
the changer as tapedev, tried that tho, same
results.

With best regards,

Armand Sulter - Systems Administration

  ENTER.NET - The Road to the Internet Starts Here! (tm)
  (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED]



On Wed, 25 Aug 2004, Frazier Scott wrote:

 Question:

 What does
 /usr/local/sbin/mt -f /dev/pass2 status
 give you?


  Armand Sulter [EMAIL PROTECTED] 8/25/2004 9:31:28 AM 

 I'm trying to get this puppy to work with
 3 tapes for now, i can control the robot
 fine with the mtx program but amanda keeps
 giving me :

 bash-2.04$ /usr/local/sbin/amlabel bef Test01 slot 2
 amlabel: could not load slot 2: could not determine current slot, are
 you sure your drive slot is 2

 I put the tape from slot 1 in the drive, it knows theres one
 in slot 2 and 3 but it keeps complaining about the 'current' slot.

 From what i can tell the output of the mtx command is in a format
 the regex's from the glue script should match.

 changer.conf
 
 firstslot=1 # First slot
 lastslot=3  # Last slot
 cleanslot=-1# Don't use a cleaning tape slot
 driveslot=0 # This is the slot of the drive
 havereader=0# Do not use the barcode reader
 autoclean=0 # Do not autoclean
 offline_before_unload=0 # Does not require offline before
 unload
 havebarcode=0

 amanda.conf (snippet)
 -
 runtapes 1
 tapedev /dev/pass2
 changerdev  /dev/pass3
 tapetype IBM-LTO3580

 mtx results
 -
 bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 status
   Storage Changer /dev/pass3:1 Drives, 20 Slots ( 1 Import/Export )
 Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag =
   Storage Element 1:Empty:VolumeTag=
   Storage Element 2:Full :VolumeTag=
   Storage Element 3:Full :VolumeTag=
   Storage Element 4:Empty:VolumeTag=
   Storage Element 5:Empty:VolumeTag=
   Storage Element 6:Empty:VolumeTag=
   Storage Element 7:Empty:VolumeTag=
   Storage Element 8:Empty:VolumeTag=
   Storage Element 9:Empty:VolumeTag=
   Storage Element 10:Empty:VolumeTag=
   Storage Element 11:Empty:VolumeTag=
   Storage Element 12:Empty:VolumeTag=
   Storage Element 13:Empty:VolumeTag=
   Storage Element 14:Empty:VolumeTag=
   Storage Element 15:Empty:VolumeTag=
   Storage Element 16:Empty:VolumeTag=
   Storage Element 17:Empty:VolumeTag=
   Storage Element 18:Empty:VolumeTag=
   Storage Element 19:Empty:VolumeTag=
   Storage Element 20 IMPORT/EXPORT:Empty:VolumeTag=


 bash-2.04$ /usr/local/sbin/mtx -f /dev/pass2 inquiry
 Product Type: Tape Drive
 Vendor ID: 'IBM '
 Product ID: 'ULTRIUM-TD1 '
 Revision: '12U2'
 Attached Changer: No

 bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 inquiry
 Product Type: Medium Changer
 Vendor ID: 'HP  '
 Product ID: 'C7200   '
 Revision: '126I'
 Attached Changer: No

 does anyone have any experience with these ?

 With best regards,

 Armand Sulter - Systems Administration
 
   ENTER.NET - The Road to the Internet Starts Here! (tm)
   (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED]
 




Re: Restore buffer?

2004-08-25 Thread Darren Landrum
Thank you to all for you answers. I think at this point, it's all over but the 
actual implementation.

I'm using Suse 9.1 with a Quantum SDLT320, in case you're all curious.

Regards,
Darren Landrum
Montrose County IT


On Wednesday 25 August 2004 12:24 pm, Frank Smith wrote:
 --On Wednesday, August 25, 2004 11:32:07 -0600 Darren Landrum 
[EMAIL PROTECTED] wrote:
  I am in charge of seeting up a new backup server for the County of
  Montrose, CO. My boss has asked me to put together a system that will
  allow us to buffer a restore job (say, grabbing a file from tape) before
  sending the file back to its proper place on a server.
 
  The reason he feels this is necessary is so we can look at a file
  restored from tape before we destroy anything that might be on the server
  proper. That way, it can be confirmed by the user that this is indeed the
  file(s) they need restored before we commit to the final action.
 
  Is Amanda capable of this kind of operation?

 I almost always use Amanda this way, restoring into a scratch directory
 and then moving the files to where they need to go.

 Frank

  Thank you very much for your time.
 
  --
  Regards,
  Darren Landrum
  Montrose County IT



Re: Restore buffer?

2004-08-25 Thread Michael Loftis
amrecover and amrestore can be used to recover or restore arbitrary parts 
of the backup tape( s ) to arbitrary places...assuming the machine you're 
running them from has the appropriate tools available (IE gnutar and/or the 
particular 'dump' programs needed) -- so the generic answer is 'yes' -- 
restores can happen to any amanda client that is given access to the server.

--On Wednesday, August 25, 2004 11:32 -0600 Darren Landrum 
[EMAIL PROTECTED] wrote:

I am in charge of seeting up a new backup server for the County of
Montrose,  CO. My boss has asked me to put together a system that will
allow us to  buffer a restore job (say, grabbing a file from tape) before
sending the file  back to its proper place on a server.
The reason he feels this is necessary is so we can look at a file
restored  from tape before we destroy anything that might be on the
server proper. That  way, it can be confirmed by the user that this is
indeed the file(s) they  need restored before we commit to the final
action.
Is Amanda capable of this kind of operation?
Thank you very much for your time.
--
Regards,
Darren Landrum
Montrose County IT


--
GPG/PGP -- 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E 


Re: Input/output error attempting to run amlabel - Resolved

2004-08-25 Thread Frazier Scott
Turns out I'm an idiot.  Just needed to clean the drive.  Sorry for the
hassle!

 KEVIN ZEMBOWER [EMAIL PROTECTED] 8/25/2004 8:47:19 AM 
I think that the first error, when reading, is caused by trying to read
the label from a pristine tape, with nothing written on it. I get this
error all the time when I label new tapes. I just ignore it.

There has recently been some discussion of this on this list, and I may
actually have this wrong. This is just my guess.

However, the second input/output error, when 'writing endmark,' I've
never seen before (I started writing this response before I noticed
this). Maybe someone else can help with that.

-Kevin

 Frazier Scott [EMAIL PROTECTED] 08/24/04 11:14PM 
Can anyone give me an idea why this might be occurring (see below)? 
Mandrake Linux 9.2, su'ed to the amanda user, all config files seem to
be set up OK, using chg-zd-mtx, tapetype set to the pv120t-dds4 found
on
the faq-o-matic site, Dell PowerVault 120T AutoLoader with DDS-4 tapes.

I am attempting to populate the tapelist (already touched the file).

After I get this error, running mt -f /dev/nst0 status also gives me
Input/output error.  If I then unload the tape using mtx -f /dev/sg5
unload, I can reload the tape using mtx -f /dev/sg5 load 1 and mt -f
/dev/nst0 status works fine.  I attempt to run amlabel again, and the
whole thing starts over again.

-bash-2.05b$ /usr/amanda/sbin/amlabel sunday amanda001 slot 1
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label, reading label: Input/output error
rewinding, writing label amanda001
amlabel: writing endmark: Input/output error

Thanks,

Frazier.




How does amanda determine free space?

2004-08-25 Thread Dave Sherohman
I just installed the amanda client on a new server that's being added
to our backups and, thanks to minor libc versioning issues, the host
check is returning a series of

dir /tmp/amanda needs 64KB, only has -2147483648KB available.

errors.

I've only seen this bug with the large negative sizes in df before,
so I brought that up-to-date on the new server and it now reports disk
sizes and available space correctly, but amanda's still getting the
bad readings.

So, what method does amanda use to determine the available space?
I assume it's not internal, as the amanda and glibc versions are in sync,
but that makes it non-obvious which other app needs to be updated to
clear this up.

(This is on a Debian basically-stable system which needed an app running
at the version from testing and dragged in the testing glibc along
with it.)



Re: ibm ultrium lto library/tape loader using chg-zd-mtx(freebsd)(amanda2.4.4)

2004-08-25 Thread Frazier Scott
Yup.  I was trying to set up amanda using chg-zd-mtx.  mtx -f /dev/sg5
yielded info on the changer, and mtx -f /dev/sg4 yielded info on the
drive so I figured tapedev should be /dev/sg4.  When I couldn't get the
tests to work, I looked at the script and discovered that in the places
it accesses tapedev, it uses the mt command.  So, I changed my tapedev
to /dev/nst0 (the no-rewind device I usually use with mt), and it
worked like a charm.  Now I'm just trying to figure out how to enable
host control of compression on my Dell PowerVault 120T DDS4.

Frazier.

 Armand Sulter [EMAIL PROTECTED] 8/25/2004 11:25:26 AM 

It comes back with :

bash-2.04# mt -f /dev/pass2 status
mt: /dev/pass2: Operation not permitted

Are you saying i should be able to access
/dev/pass2 as a regular tape drive ?

i read somewhere sometimes you have to use
the changer as tapedev, tried that tho, same
results.

With best regards,

Armand Sulter - Systems Administration

  ENTER.NET - The Road to the Internet Starts Here! (tm)
  (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED] 



On Wed, 25 Aug 2004, Frazier Scott wrote:

 Question:

 What does
 /usr/local/sbin/mt -f /dev/pass2 status
 give you?


  Armand Sulter [EMAIL PROTECTED] 8/25/2004 9:31:28 AM 

 I'm trying to get this puppy to work with
 3 tapes for now, i can control the robot
 fine with the mtx program but amanda keeps
 giving me :

 bash-2.04$ /usr/local/sbin/amlabel bef Test01 slot 2
 amlabel: could not load slot 2: could not determine current slot,
are
 you sure your drive slot is 2

 I put the tape from slot 1 in the drive, it knows theres one
 in slot 2 and 3 but it keeps complaining about the 'current' slot.

 From what i can tell the output of the mtx command is in a format
 the regex's from the glue script should match.

 changer.conf
 
 firstslot=1 # First slot
 lastslot=3  # Last slot
 cleanslot=-1# Don't use a cleaning tape slot
 driveslot=0 # This is the slot of the drive
 havereader=0# Do not use the barcode reader
 autoclean=0 # Do not autoclean
 offline_before_unload=0 # Does not require offline before
 unload
 havebarcode=0

 amanda.conf (snippet)
 -
 runtapes 1
 tapedev /dev/pass2
 changerdev  /dev/pass3
 tapetype IBM-LTO3580

 mtx results
 -
 bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 status
   Storage Changer /dev/pass3:1 Drives, 20 Slots ( 1 Import/Export )
 Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag =
   Storage Element 1:Empty:VolumeTag=
   Storage Element 2:Full :VolumeTag=
   Storage Element 3:Full :VolumeTag=
   Storage Element 4:Empty:VolumeTag=
   Storage Element 5:Empty:VolumeTag=
   Storage Element 6:Empty:VolumeTag=
   Storage Element 7:Empty:VolumeTag=
   Storage Element 8:Empty:VolumeTag=
   Storage Element 9:Empty:VolumeTag=
   Storage Element 10:Empty:VolumeTag=
   Storage Element 11:Empty:VolumeTag=
   Storage Element 12:Empty:VolumeTag=
   Storage Element 13:Empty:VolumeTag=
   Storage Element 14:Empty:VolumeTag=
   Storage Element 15:Empty:VolumeTag=
   Storage Element 16:Empty:VolumeTag=
   Storage Element 17:Empty:VolumeTag=
   Storage Element 18:Empty:VolumeTag=
   Storage Element 19:Empty:VolumeTag=
   Storage Element 20 IMPORT/EXPORT:Empty:VolumeTag=


 bash-2.04$ /usr/local/sbin/mtx -f /dev/pass2 inquiry
 Product Type: Tape Drive
 Vendor ID: 'IBM '
 Product ID: 'ULTRIUM-TD1 '
 Revision: '12U2'
 Attached Changer: No

 bash-2.04$ /usr/local/sbin/mtx -f /dev/pass3 inquiry
 Product Type: Medium Changer
 Vendor ID: 'HP  '
 Product ID: 'C7200   '
 Revision: '126I'
 Attached Changer: No

 does anyone have any experience with these ?

 With best regards,

 Armand Sulter - Systems Administration
 
   ENTER.NET - The Road to the Internet Starts Here! (tm)
   (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED] 
 




Tapetype for a SpectraLogic DASTape 100?

2004-08-25 Thread David C. Kovar
Good morning,

I am attempting to set up a new installation of Amanda with a SpectraLogic
DASTape 100. I was unable to find an existing definition for this drive and
was wondering if anyone had one they could share?

Thank you very much.

-David



Re: sendbackup file renaming failure

2004-08-25 Thread Mitch Collinsworth

On Wed, 25 Aug 2004, Jim Summers wrote:

 On Wed, 2004-08-25 at 19:53, Mitch Collinsworth wrote:
 
  error [renaming /var/adm/amanda/gnutar-lists/usda01afs:usda01_b_.*.backup_0.new
  to /var/adm/amanda/gnutar-lists/usda01afs:usda01_b_.*.backup_0: No such file or
  directory]

 Just a guess, but possibly the fs involved has reached 100% capacity?

Nope.

-Mitch