Re: help with moving client between servers

[Brian Cuttler]

Amanda users,

I recalled the magic.

I had multiple DLE defined in the disklist, one with the 'correct'
dumptype and the rest not. I thought I could invoke # amcheck on
the single DLE to verify the config, this is NOT the case, the other
DLE for the same host with different/competing dumptypes causing
the problem.

When I commented out the other DLE and corrected amanda.conf auto
to be "bsd" (not "bsdtcp) # amcheck ran correctly.

I will not update the DLE in the disklist, remove comment field and
update dumptype.

thank you,

Brian


On Fri, Jun 29, 2012 at 09:53:47AM -0400, Brian Cuttler wrote:
> 
> Amanda Users,
> 
> I've been successfully backing up amanda client on Suse with
> amanda server on Suse, but want to migrate the client to another
> amanda server that is a newer version.
> 
> I have (attempted) to follow the article
> 
> http://forums.zmands.com/archive/index.php/t-423.html
> which is an article that gives the error I am receiving.
> 
> I am clearly missing something obvious, and I'm asking you 
> to look over what I did and tell me what dumb thing I'm doing.
> 
> Thanks in advance,  Brian
> 
> 
> Client is: amanda 2.5.2.1-46 on openSUSE 10.3 (X86-64)
> 
> New Server is: Amanda 3.3.0 on openSUSE 12.1 (x86_64)
> 
> I've configured a DLE this way, please don't put too much emphisis
> on the dumptype's name, that is easilly fixed.
> 
> From disklist
> radha  /usr12/andaman/usr1 user-tar-bsdtcp
> 
> 
> From amanda.conf
> define dumptype user-tar-bsdtcp {
> root-tar
> index
> comment "user partitions dumped with tar"
> auth "bsdtcp"
> compress client fast
> priority medium
> }
> 
> And updated /etc/xinetd.d/amanda on the Client to read
> 
> # default: off
> # description: Amanda backup client
> #
> service amanda 
> {
> socket_type = stream
> protocol= tcp
> wait= no
> user= amanda
> group   = disk
> server  = /usr/lib/amanda/amandad -auth=bsdtcp
> #   disable = yes
> disable = no
> }
> 
> I "think" I've hit every possible combination of "bsd" and "bsdtcp"
> on both the client and server end, remembering to restart xinetd on
> the client each time, but it continues to fail.
> 
> Amanda Backup Client Hosts Check
> 
> WARNING: radha: selfcheck request failed: tcpm_recv_token: invalid size: 
> "chown(/tmp/amanda/amandad/amandad.20120629095135.debug, 110, 110) failed. 
> "
> Client check: 1 host checked in 0.095 seconds.  1 problem found.
> 
> (brought to you by Amanda 3.3.0)
> 
> 
> ---
>Brian R Cuttler brian.cutt...@wadsworth.org
>Computer Systems Support(v) 518 486-1697
>Wadsworth Center(f) 518 473-6384
>NYS Department of HealthHelp Desk 518 473-0773
> 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: HELP ! Setting up a RAID-0 holding disk on centos 4.4

[Guy Dallaire]

2007/4/16, Paul Bijnens <[EMAIL PROTECTED]>:


Indeed, in the meantime, you can play around with command line options
to alter the amanda.conf parameters:

http://wiki.zmanda.com/index.php/Amanda#CONFIGURATION_OVERWRITE

First run amdump to holdingdisk, setting the tapedev to e.g. /dev/notape
(do not use /dev/null -- amanda assumes tapedev /dev/null is for testing
purposes and makes a backup, and trows it away).
Then run amflush using the paramaters in amanda.conf



I'm not using  amanda 2.5 yet.  Running 2.4.5

Re: HELP ! Setting up a RAID-0 holding disk on centos 4.4

[Paul Bijnens]

On 2007-04-14 01:28, Frank Smith wrote:
> Chris Marble wrote:
>> Guy Dallaire wrote:
>>> I really wish there was an easy way to instruct amanda to wait for all the
>>> client files,  before starting dumping the holding disk to tape, but there
>>> isn't.
>> Just run the backup without a tape in the drive and then amflush the backup
>> sometime later.
> 
> Unfortunately, that method doesn't work well if you're using a library.
> While it is possible to use a wrapper script to change the devices
> to something non-existent before each run and then changing it back
> and running amflush, it would be much more convenient to simply
> have a config option that delays taper until after the dumps are
> finished.

Indeed, in the meantime, you can play around with command line options
to alter the amanda.conf parameters:

http://wiki.zmanda.com/index.php/Amanda#CONFIGURATION_OVERWRITE

First run amdump to holdingdisk, setting the tapedev to e.g. /dev/notape
(do not use /dev/null -- amanda assumes tapedev /dev/null is for testing
purposes and makes a backup, and trows it away).
Then run amflush using the paramaters in amanda.conf



-- 
Paul Bijnens, xplanation Technology ServicesTel  +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, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

taperwait/taperstart/taperflush [was Re: HELP ! Setting up ...]

[Jon LaBadie]

On Fri, Apr 13, 2007 at 03:23:12PM -0400, Guy Dallaire wrote:
> 
> I really wish there was an easy way to instruct amanda to wait for all the
> client files,  before starting dumping the holding disk to tape, but there
> isn't.
> 
> New feature ?
> 

Several possibilites were suggested, none added to the core version of amanda.

In September 2005 Orion Poplawski submitted patches for version 2.4.5b for
an option he implemented called taperwait.

Jean-Louis suggested that Orion's patch did not solve some of the taper
scheduling problems and suggested a alternate model of two new options
called taperflush and taperstart.  JLM said he would undertake implementing
his idea when he got the time.

Orion reawakened the issue in August 2006 after the release of the 2.5 version.
He was not too keen on trying to port his 2.4.5 version of taperwait to 2.5
and was hoping JLM's suggestion was being implemented.

In that same discussion Paddy Sreenivasan suggested it be added to the list
of requested new features.


Add your desire for such a feature.

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

Re: HELP ! Setting up a RAID-0 holding disk on centos 4.4

[Frank Smith]

Chris Marble wrote:
> Guy Dallaire wrote:
>> I really wish there was an easy way to instruct amanda to wait for all the
>> client files,  before starting dumping the holding disk to tape, but there
>> isn't.
> 
> Just run the backup without a tape in the drive and then amflush the backup
> sometime later.

Unfortunately, that method doesn't work well if you're using a library.
While it is possible to use a wrapper script to change the devices
to something non-existent before each run and then changing it back
and running amflush, it would be much more convenient to simply
have a config option that delays taper until after the dumps are
finished.

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

Re: HELP ! Setting up a RAID-0 holding disk on centos 4.4

[Chris Marble]

Guy Dallaire wrote:
> 
> I finally found the right FM in order to RTFM and proceeded to create the
> RAID-0 holding disk with 2 250Gb SATA drives in order to try to fix the
> trhroughput problem with the tape drive. The raidtools have been replaced by
> the mdadm command.
> 
> I'm back to square one. Even if I use a RAID-0 stripped (64k stripes) array,
> I still can't feed the tape drive adequately when amanda is writing to the
> holding disk while it's being dumped to tape.
> 
> I really wish there was an easy way to instruct amanda to wait for all the
> client files,  before starting dumping the holding disk to tape, but there
> isn't.

Just run the backup without a tape in the drive and then amflush the backup
sometime later.
-- 
  [EMAIL PROTECTED] - HMC UNIX Systems Manager
  My opinions are my own and probably don't represent anything anyway.

Re: HELP ! Setting up a RAID-0 holding disk on centos 4.4

[Guy Dallaire]

2007/4/5, Guy Dallaire <[EMAIL PROTECTED]>:


Hello.

Due to performance problem on my holding disk, it was suggested by this
great group of people to create a striped raid for my holding disk. I have
acquired 2 new sata drives and I'm in the process of finding the
documentation abour how to create a RAID device

All the software raid how-to I find are for kernel 2.4.

Centos 4.4 is kernel 2.6

Also, they talk about the mkraid command, but this command is nowhere to
be found on centos.

Does anyone has a good and EASY source of focumentation about how to
create a RAID-0, create a file system and mount it on CENTOS 4 (Or RHEL4)
AFTER installation ?

There are many contraditing sources of info, I'm in a bit of a hurry, and
I must admit that I am more familiar with solaris software raid than linux.

Thanks a LOT !



I finally found the right FM in order to RTFM and proceeded to create the
RAID-0 holding disk with 2 250Gb SATA drives in order to try to fix the
trhroughput problem with the tape drive. The raidtools have been replaced by
the mdadm command.

I'm back to square one. Even if I use a RAID-0 stripped (64k stripes) array,
I still can't feed the tape drive adequately when amanda is writing to the
holding disk while it's being dumped to tape.

I benchmarked a 'dd' command of a 10gb file to tape (read only, nopt writing
to the array at the same time) and with various block sizes, and the
performance impact is minimal.  So it's of no use to recompile amanda.

I really wish there was an easy way to instruct amanda to wait for all the
client files,  before starting dumping the holding disk to tape, but there
isn't.

New feature ?

Thanks anyway

Re: Help restoring

[David Golden]

On 2005-08-30 13:25:09 -0400, Jon LaBadie wrote:
> > As to the other suggestions, my /dev/tape ls symlinked to /dev/nst0, so is
> > not rewinding.
> 
> Typically 'tape' references st0 and 'ntape' references nst0.
>
OTOH, my install of CentOS 4, something (udev, manages /dev
on most new linux kernel based OS Distros) has automagically 
made the  symlink from tape to nst0, not st0. Not saying it's right, 
or conventional in the wider ixoid world, just that that's what 
happened and that's what a fresh install of CentOS 4 (and 
therefore presumably what RHEL4) will do.

[EMAIL PROTECTED] ~]# grep -R tape /etc/udev/rules.d/
/etc/udev/rules.d/50-udev.rules:KERNEL="qft0",  SYMLINK="ftape"
/etc/udev/rules.d/50-udev.rules:KERNEL="nst[0-9]*", SYMLINK="tape%e"

Re: Help restoring

[Jon LaBadie]

On Tue, Aug 30, 2005 at 07:46:00PM +0200, Alexander Jolk wrote:
> >
> >Typically 'tape' references st0 and 'ntape' references nst0.
> >
> 
> ...and anyway, if you really used the non-rewinding device, the sequence 
> of commands that you posted should have worked.  If you want to get to 
> the bottom of things, try to verify whether indeed /dev/tape rewinds, or 
> not.
> 
> I'd suggest something like
> dd if=/dev/tape bs=32k count=1 | head -2
> (which should give you an amanda tape file header)
> dd if=/dev/tape bs=32k count=1 | file -z -
> (which should tell you that you have a gzip compressed tar archive)
> If this is not the case, you might really use the rewinding device; in 
> that case, try to find out why that's the case.  You really don't want 
> amanda to use the rewinding one.
> 

Gee, file -z, another interesting gnu-specific option of which I did not know.

> Alex
> 
> -- 
> Alexander Jolk / BUF Compagnie
> tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29
> 
> 
>>> End of included message <<<

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

Re: Help restoring

[Alexander Jolk]

Jon LaBadie wrote:

On Tue, Aug 30, 2005 at 05:59:26PM +0100, Tony van der Hoff wrote:

...


BTW, I think the device you are using "/dev/tape" is the rewind
on close device.  Thus after the first dd ... count=1 command
the tape probably rewinds to the beginning of the tape.
/dev/ntape is likely the "leave the tape where it is" device.



...


As to the other suggestions, my /dev/tape ls symlinked to /dev/nst0, so is
not rewinding.



Typically 'tape' references st0 and 'ntape' references nst0.



...and anyway, if you really used the non-rewinding device, the sequence 
of commands that you posted should have worked.  If you want to get to 
the bottom of things, try to verify whether indeed /dev/tape rewinds, or 
not.


I'd suggest something like
dd if=/dev/tape bs=32k count=1 | head -2
(which should give you an amanda tape file header)
dd if=/dev/tape bs=32k count=1 | file -z -
(which should tell you that you have a gzip compressed tar archive)
If this is not the case, you might really use the rewinding device; in 
that case, try to find out why that's the case.  You really don't want 
amanda to use the rewinding one.


Alex

--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: Help restoring

[Jon LaBadie]

On Tue, Aug 30, 2005 at 05:59:26PM +0100, Tony van der Hoff wrote:
> > 
...
> > BTW, I think the device you are using "/dev/tape" is the rewind
> > on close device.  Thus after the first dd ... count=1 command
> > the tape probably rewinds to the beginning of the tape.
> > /dev/ntape is likely the "leave the tape where it is" device.
...
> 
> As to the other suggestions, my /dev/tape ls symlinked to /dev/nst0, so is
> not rewinding.

Typically 'tape' references st0 and 'ntape' references nst0.

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

Re: Help restoring

[Tony van der Hoff]

Jon LaBadie <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>

> On Thu, Aug 25, 2005 at 07:43:53PM +0100, Tony van der Hoff wrote:
> > I'm trying to recover my /etc directory from tape, so in accordance with
> > docs/RESTORE, I'm doing this:
> > 
> > [EMAIL PROTECTED] etc]# mt fsf 1 && dd if=/dev/tape bs=32k count=1
> > AMANDA: FILE 20050821 tony-lx /etc lev 0 comp .gz program /bin/gtar
> > To restore, position tape at start of file and run:
> >dd if= bs=32k skip=1 | /bin/gzip -dc | bin/gtar -f... -
> > 
> > 
> > 1+0 records in
> > 1+0 records out
> > [EMAIL PROTECTED] etc]# dd if=/dev/tape bs=32k skip=1 | /bin/gzip -dc |
> > /bin/gtar -xpvf -
> > 
> > gzip: stdin: not in gzip format
> > 2+0 records in
> > 1+0 records out
> > 
> > And, of course nothing in my restore/etc dir. I hope it's just my
> > incompetence :( 
> > 
> 
> 
> Those two command sequences can not be run one after the other.
> Each assumes the tape is as the same starting position.  After
> positioning the tape to the beginning of a tape file, the first
> command looks at the first block of the tape file.  The second
> command, if started from the same beginning of a tape file,
> skips over the first block (the one read by the first command).
> But if the tape is not at the beginning of the file you either
> don't need to skip anything, or you have to rewind and reposition
> to the beginning of the tape file.
> 
> BTW, I think the device you are using "/dev/tape" is the rewind
> on close device.  Thus after the first dd ... count=1 command
> the tape probably rewinds to the beginning of the tape.
> /dev/ntape is likely the "leave the tape where it is" device.
> 

My sincere thanks to everyone who took the time to reply. As suggested, it
was the 'skip=1' instruction that caused the trouble. Omitting this in the
dd solved it. Stangely, I had already tried a "mt bsf 1" with the aim of
positioning the tape correctly, but that failed to improve matters.
Possibly, I was by then so confused that I messed it up.

As to the other suggestions, my /dev/tape ls symlinked to /dev/nst0, so is
not rewinding. I'm running Mandrake Linux 10.2 here. I created a seperate
/restore/etc directory, in which to restore /etc.

I think my initial confusion arose out of the suggestion from Amanda:
> > To restore, position tape at start of file and run:
> >dd if= bs=32k skip=1 | /bin/gzip -dc | bin/gtar -f... -
In fact,
To restore, run: 
dd if= bs=32k | /bin/gzip -dc | bin/gtar -f... -
would maybe have been more helpful and less verbose at this point. 

I guess I should have figured out which 'start of file' to position to, but
failed :-(

Anyway, thanks again.

-- 
Tony van der Hoff| mailto:[EMAIL PROTECTED]
Buckinghamshire, England 

Re: Help restoring

[Jon LaBadie]

On Thu, Aug 25, 2005 at 07:43:53PM +0100, Tony van der Hoff wrote:
> I'm trying to recover my /etc directory from tape, so in accordance with
> docs/RESTORE, I'm doing this:
> 
> [EMAIL PROTECTED] etc]# mt fsf 1 && dd if=/dev/tape bs=32k count=1
> AMANDA: FILE 20050821 tony-lx /etc lev 0 comp .gz program /bin/gtar
> To restore, position tape at start of file and run:
>dd if= bs=32k skip=1 | /bin/gzip -dc | bin/gtar -f... -
> 
> 
> 1+0 records in
> 1+0 records out
> [EMAIL PROTECTED] etc]# dd if=/dev/tape bs=32k skip=1 | /bin/gzip -dc |
> /bin/gtar -xpvf -
> 
> gzip: stdin: not in gzip format
> 2+0 records in
> 1+0 records out
> 
> And, of course nothing in my restore/etc dir. I hope it's just my
> incompetence :( 
> 


Those two command sequences can not be run one after the other.
Each assumes the tape is as the same starting position.  After
positioning the tape to the beginning of a tape file, the first
command looks at the first block of the tape file.  The second
command, if started from the same beginning of a tape file,
skips over the first block (the one read by the first command).
But if the tape is not at the beginning of the file you either
don't need to skip anything, or you have to rewind and reposition
to the beginning of the tape file.

BTW, I think the device you are using "/dev/tape" is the rewind
on close device.  Thus after the first dd ... count=1 command
the tape probably rewinds to the beginning of the tape.
/dev/ntape is likely the "leave the tape where it is" device.

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

Re: Help restoring

[Alexander Jolk]

Tony van der Hoff wrote:

I'm trying to recover my /etc directory from tape, so in accordance with
docs/RESTORE, I'm doing this:

[EMAIL PROTECTED] etc]# mt fsf 1 && dd if=/dev/tape bs=32k count=1
AMANDA: FILE 20050821 tony-lx /etc lev 0 comp .gz program /bin/gtar
To restore, position tape at start of file and run:
   dd if= bs=32k skip=1 | /bin/gzip -dc | bin/gtar -f... -


1+0 records in
1+0 records out
[EMAIL PROTECTED] etc]# dd if=/dev/tape bs=32k skip=1 | /bin/gzip -dc |
/bin/gtar -xpvf -

gzip: stdin: not in gzip format
2+0 records in
1+0 records out


Is /dev/tape rewinding or non-rewinding?  You already read the first 32k 
block in your first command, so if your tape is non-rewinding, the block 
you are skipping (skip=1) is actually the first real data block.  Try 
without the skip=1, and tell us whether that works.


You might as well specify which OS you are on while you're at it, so 
that we don't stress our crystal balls too much. :-)


Alex

PS.  Are you sure you want to restore directly into /etc, if that's what 
you're doing?



--
Alexander Jolk  * BUF Compagnie * [EMAIL PROTECTED]
Tel +33-1 42 68 18 28  *  Fax +33-1 42 68 18 29

Re: Help restoring

[Matt Hyclak]

On Thu, Aug 25, 2005 at 07:43:53PM +0100, Tony van der Hoff enlightened us:
> I'm trying to recover my /etc directory from tape, so in accordance with
> docs/RESTORE, I'm doing this:
> 
> [EMAIL PROTECTED] etc]# mt fsf 1 && dd if=/dev/tape bs=32k count=1
> AMANDA: FILE 20050821 tony-lx /etc lev 0 comp .gz program /bin/gtar
> To restore, position tape at start of file and run:
>dd if= bs=32k skip=1 | /bin/gzip -dc | bin/gtar -f... -
> 
> 
> 1+0 records in
> 1+0 records out
> [EMAIL PROTECTED] etc]# dd if=/dev/tape bs=32k skip=1 | /bin/gzip -dc |
> /bin/gtar -xpvf -
> 
> gzip: stdin: not in gzip format
> 2+0 records in
> 1+0 records out
> 
> And, of course nothing in my restore/etc dir. I hope it's just my
> incompetence :( 
> 
> Any suggestions, please?

Is /dev/tape a link to the non-rewinding device, or the rewinding device?
(/dev/nst0 for non-rewinding on linux and /dev/st0 for rewinding).

It looks to me like this is what happens in your above command:

Skip forward one to the file on tape that contains /etc
dd the first 32k block that contains the amanda label
dd the gzipped file *skipping the first block*, resulting in a gzip file
   missing the first 32k

You missed the part that says position tape at start of the file :-)

Try again without the second skip=1

Matt

-- 
Matt Hyclak
Department of Mathematics 
Department of Social Work
Ohio University
(740) 593-1263


pgpOSS1CF6fCY.pgp
Description: PGP signature

Re: Help with computing dump cycle

[Jon LaBadie]

On Wed, Jul 14, 2004 at 06:20:36AM +0800, Jay Ted wrote:
> Hello, 
>  
> I need help on figuring out how to set up the dump cycle.  The way I
have previously done backups is a full dump on Friday night with
incremental dumps Saturday through Thursday.  I keep
> the full dumps for the past 5 Fridays, and full dumps done on the
last Friday of the previous 3 months.  I short, I want to have the
ability to restore a system to its previous state for the last 7
> days, 5 weeks, and 3 months.   I have an Powervault 120T/DLT7000 that
holds 7 tapes.   With compression off each tape holds about 35G.  A
full dump of all of my systems uncompressed
> will fill nearly 6 tapes.  I have plenty of tapes to swap out all
tapes daily.  Is there an easy way to set amanda.conf up to backup like
this in only one configuration?  Or do I need multiple
> configs?  I have already read the Amanda chapter of the O'Reilly
Backup book.  I would just like to see someone's example config who may
be doing something similar to what I am trying to do. 
>  

If you always do what you've always done,
you will always have what you've always had.

Consider trying the scheduling that amanda was designed to do.
Namely it decides which days each disklist entry (DLE, nominally
a file system) receives a level 0 and what incremental it gets
other days.  The aim is to have the administrator give broad
specs, as in maximum time between level 0's for each DLE, and
let amanda worry about the specifics.  When balanced, amanda
will be able to backup about the same amount of data (as in
tape usage) each dump run.  No one hour backups Sat-Thur and
twelve hours on Fri, but two hours nightly.

I started out with a 1 week dumpcycle for everything and later
fine tuned some DLE's to only doing the level 0's, never any
incrementals as they never seem to change, others extended
to 2 weeks with incrementals too, and some shortened them to
3 days as they vary more rapidly and I wanted the level 0's
closer together.

jl
-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Help with computing dump cycle

[Joshua Baker-LePain]

On Wed, 14 Jul 2004 at 6:20am, Jay Ted wrote

> I need help on figuring out how to set up the dump cycle.  The way I have previously 
> done backups is a full dump on Friday night with incremental dumps Saturday through 
> Thursday.  I keep 
> the full dumps for the past 5 Fridays, and full dumps done on the last Friday of the 
> previous 3 months.  I short, I want to have the ability to restore a system to its 
> previous state for the last 7 
> days, 5 weeks, and 3 months.   I have an Powervault 120T/DLT7000 that holds 7 tapes. 
>   With compression off each tape holds about 35G.  A full dump of all of my systems 
> uncompressed 
> will fill nearly 6 tapes.  I have plenty of tapes to swap out all tapes daily.  Is 
> there an easy way to set amanda.conf up to backup like this in only one 
> configuration?  Or do I need multiple 
> configs?  I have already read the Amanda chapter of the O'Reilly Backup book.  I 
> would just like to see someone's example config who may be doing something similar 
> to what I am trying to 
> do. 

First, please fix your line lengths.  It makes it rather hard to read.

Reading the list archives, you'll see that forcing amanda into such a 
fixed schedule is rather difficult, and somewhat frowned upon.  Amanda 
likes to do its own scheduling, with the goal of eqaulizing the night's 
backups.

How many tapes do you have?  If you have 7 days*12 weeks=84 tapes, you can 
have 3 months worth of history to the daily level, with several level 0s 
of each filesystem spread throughout your tapes.  This is the easiest 
option, requiring only one config.  You could do, e.g., dumpcycle=12 days, 
runspercycle=12, tapecycle=84.

If you have 7 days*5 weeks=35 tapes + 6 tapes*3 months=18 for a total of 
53 tapes, you could do 5 weeks worth of history to the daily level plus a 
separate config doing level 0s of everything once a month.

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

Re: help getting started

[Gene Heskett]

On Wednesday 30 June 2004 08:01, Max Waterman wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Stefan G. Weichinger wrote:
>| Hi, Max,
>|
>| on Mittwoch, 30. Juni 2004 at 13:06 you wrote to amanda-users:
>|
>| MW> Hi,
>|
>| MW> I'm getting some errors in my amstatus output - can anyone
>
>enlighten me?
>
>|>># su amanda -c "/usr/sbin/amstatus DailySet1"
>|>>Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16
>|>> CST 2004
>|>>
>|>>localhost:/etc   2  24k finished
>|>> (16:46:53) Use of uninitialized value in printf at
>|>> /usr/sbin/amstatus line 760. Use of uninitialized value in
>|>> numeric ne (!=) at /usr/sbin/amstatus
>
>line 761.
>
>|>>localhost:/home  017720729k dumping
>|>> 0k
>
>(16:49:27)
>
>|>>Use of uninitialized value in addition (+) at /usr/sbin/amstatus
>|>> line
>
>770.
>
>|>>localhost:/usr/local 0   22701k finished
>|>> (16:47:32) localhost:/var   0  232660k
>|>> wait for dumping
>
>driver: (aborted)
>
>| MW> It seems to be taking ages to complete this backup...is
>| something
>
>wrong?
>
>| yes, it is. Those uninitialized values should not be there. A
>| quick look into amstatus seems to lead us to the estimates  
>|
>| But the estimates seem to succeed.
>|
>| What release of AMANDA is this, btw?
>
>2.4.3-4, it seems.

Humm, would it be possible for one of us to email you a more recent 
tar.gz of say 2.4.5b1?  The last one I have on site is dated 
20040622.

I'd go on an education campaign to get access to www.amanda.org 
enabled, along with access to the site Jean-Louis has for new 
snapshots at .

Only by severe miss-information on the part of the chinese filtering 
folks would they set a block on those two sites.

>| At first edit your disklist.
>|
>| Don't use "localhost", use the full hostname instead.
>
>OK, that's easy :)
>
>| Read docs/TOP-TEN-QUESTIONS for the explanation, if you want.
>
>Unfortunately, www.amanda.org is still not accessible from China :(
>
>I guess I can try one of the anonymous proxys, but they also,
>unsuprisingly, tend not to work very well from here either.
>
>Is there a mirror somewhere, is the relevant info installed with
> amanda? I see there's a fair bit of info. I'll dig some...esp. FAQ
> that's there.
>
>Thanks.
>
>Max.
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1.2.4 (Darwin)
>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
>iD8DBQFA4qur4frZ3W7OHZMRAvaCAJ91f8tCvD5nPYi7IQR9QTbi9VbbhACeOTvU
>B3ncR50BIUykoH30KQS/faQ=
>=btYK
>-END PGP SIGNATURE-

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: help getting started

[Gene Heskett]

On Wednesday 30 June 2004 07:06, Max Waterman wrote:
>Hi,
>
>I'm getting some errors in my amstatus output - can anyone enlighten
> me?
>
>> # su amanda -c "/usr/sbin/amstatus DailySet1"
>> Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16
>> CST 2004
>>
>> localhost:/etc   2  24k finished

Please re-read the fAQ and the TOP-TEN-QUESTIONS in the docs dir, and 
then give your machine a unique name.  localhost is not unique.

>> (16:46:53) Use of uninitialized value in printf at
>> /usr/sbin/amstatus line 760. Use of uninitialized value in numeric
>> ne (!=) at /usr/sbin/amstatus line 761. localhost:/home   
>>   017720729k dumping0k (16:49:27) Use of
>> uninitialized value in addition (+) at /usr/sbin/amstatus line
>> 770. localhost:/usr/local 0   22701k finished
>> (16:47:32) localhost:/var   0  232660k
>> wait for dumping driver: (aborted)
>>
>> SUMMARY  part real estimated
>>   size  size
>> partition   :   4
>> estimated   :   4   17976128k
>> flush   :   00k
>> failed  :   0  0k   (  0.00%)
>> wait for dumping:   1 232660k   (  1.29%)
>> dumping to tape :   0  0k   (  0.00%)
>> dumping :   10k 17720729k (  0.00%) (  0.00%)
>> dumped  :   222725k22739k ( 99.94%) (  0.13%)
>> wait for writing:   00k0k (  0.00%) (  0.00%)
>> wait to flush   :   00k0k (100.00%) (  0.00%)
>> writing to tape :   00k0k (  0.00%) (  0.00%)
>> failed to tape  :   00k0k (  0.00%) (  0.00%)
>> taped   :   222725k22739k ( 99.94%) (  0.13%)
>> 3 dumpers idle  : not-idle
>> taper writing, tapeq: 0
>> network free kps:   67
>> holding space   :   296960k (100.00%)
>>  dumper0 busy   :  0:02:17  ( 88.75%)
>>taper busy   :  0:00:10  (  6.90%)
>>  0 dumpers busy :  0:00:17  ( 10.98%)  start-wait: 
>> 0:00:17  (100.00%) 1 dumper busy  :  0:02:17  ( 89.02%)   
>> no-bandwidth:  0:01:49  ( 79.46%) start-wait:  0:00:28  ( 20.54%)
>
>It seems to be taking ages to complete this backup...is something
> wrong?

When it is done, what speed is reported in the email the dump sends 
you?  By that, I mean does it match within say 10% of the drives 
rated speed of data transfer?  Also, note the holding disk area of 
only 296,960k, (297 megs) which is not nearly enough for amdump to 
stuff a 17,720,729k (18Gb? break that into subdirs and use tar, not 
dump if thats what you are now using) dump, and this is forceing 
amdump to write directly to the tape, possibly with lots of 
under-runs that will result in the drive stopping, backing up and 
restarting (shoe shining) which takes time out of the write time, so 
I'd expect the write speeds reported to be a bit slow.

So in addition to giving the machine a unique name that can at least 
be resolved in the /etc/hosts file, find it some more holding disk 
area.  The localhost issue probably won't effect the backups, but it 
sure will mung any chances of a clean recovery should you need it.
>
>Max.
>
>Max Waterman wrote:
>> Thanks everyone for helping.
>>
>> I got email working (albeit only locally since my isp is blocking
>> my [chinese] IP address), so now I can get the reports.
>>
>> I bought some more tapes, and have used the amrmtape command to
>> start from scratch. Seems to be working like a charm. Next step is
>> 'day 4' :)
>>
>> http://www.harkness.co.uk/services/backup.html
>>
>> Thanks again...until next time.
>>
>> Max.
>>
>> Paul Bijnens wrote:
>>> Max Waterman wrote:
 I am not really sure. Maybe this :

 driver: result time 6.776 from taper: TAPE-ERROR [cannot
 overwrite active tape DailySet101]
>>>
>>> It seems that the very first time you ran the backup for '/etc'
>>> it worked fine. See:
>>>   http://reality.sgiweb.org/maxw/tmp/amanda/log.20040623.0.mail )
>>>
>>> This is how a normal run looks like.
>>>
>>> For the next test, you seem to be using the same tape.
>>> But you instructed to amanda ("tapecycle XXX") that she will not
>>> overwrite an active tape.  So she cannot write to that tape.
>>>
>>> She falls back to so called "degraded mode" backups dumping to
>>> the holdingdisk.  You also have specified "reserve 100" (that's
>>> the default if you didn't change it), meaning that in degraded
>>> mode, 100% of the holdingdisk is reserved for incremental
>>> backups.
>>>
>>> But the only disklistentry was a new one, and amanda cannot
>>> make an incremental backup when there is no full backup to base
>>> it on.  Then she gives up.
>>>
>>> Solution:  while testing, you can "amrmtape" the testing tape,
>>> or you need to give more tapes (until you have "tapecycle" number
>>> of tapes).

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Ple

Re: help getting started

[Stefan G. Weichinger]

Hi, Max,

on Mittwoch, 30. Juni 2004 at 14:01 you wrote to amanda-users:

MW> | Read docs/TOP-TEN-QUESTIONS for the explanation, if you want.

MW> Unfortunately, www.amanda.org is still not accessible from China :(

MW> I guess I can try one of the anonymous proxys, but they also,
MW> unsuprisingly, tend not to work very well from here either.

MW> Is there a mirror somewhere, is the relevant info installed with amanda?
MW> I see there's a fair bit of info. I'll dig some...esp. FAQ that's there.

This is ALPHA-stage when it comes to formatting, but the content is
the same as in the AMANDA-tarball:

http://www.oops.co.at/AMANDA-docs/index.html

There you can also find the top-ten ...
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: help getting started

[Max Waterman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan G. Weichinger wrote:
| Hi, Max,
|
| on Mittwoch, 30. Juni 2004 at 13:06 you wrote to amanda-users:
|
| MW> Hi,
|
| MW> I'm getting some errors in my amstatus output - can anyone
enlighten me?
|
|
|>># su amanda -c "/usr/sbin/amstatus DailySet1"
|>>Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004
|>>
|>>localhost:/etc   2  24k finished (16:46:53)
|>>Use of uninitialized value in printf at /usr/sbin/amstatus line 760.
|>>Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus
line 761.
|>>localhost:/home  017720729k dumping 0k
(16:49:27)
|>>Use of uninitialized value in addition (+) at /usr/sbin/amstatus line
770.
|>>localhost:/usr/local 0   22701k finished (16:47:32)
|>>localhost:/var   0  232660k wait for dumping
driver: (aborted)
|
|
| MW> It seems to be taking ages to complete this backup...is something
wrong?
|
| yes, it is. Those uninitialized values should not be there. A quick
| look into amstatus seems to lead us to the estimates  
|
| But the estimates seem to succeed.
|
| What release of AMANDA is this, btw?
2.4.3-4, it seems.
|
| At first edit your disklist.
|
| Don't use "localhost", use the full hostname instead.
OK, that's easy :)
| Read docs/TOP-TEN-QUESTIONS for the explanation, if you want.
Unfortunately, www.amanda.org is still not accessible from China :(
I guess I can try one of the anonymous proxys, but they also,
unsuprisingly, tend not to work very well from here either.
Is there a mirror somewhere, is the relevant info installed with amanda?
I see there's a fair bit of info. I'll dig some...esp. FAQ that's there.
Thanks.
Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA4qur4frZ3W7OHZMRAvaCAJ91f8tCvD5nPYi7IQR9QTbi9VbbhACeOTvU
B3ncR50BIUykoH30KQS/faQ=
=btYK
-END PGP SIGNATURE-

Re: help getting started

[Paul Bijnens]

Max Waterman wrote:
I'm getting some errors in my amstatus output - can anyone enlighten me?
# su amanda -c "/usr/sbin/amstatus DailySet1"
Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004
localhost:/etc   2  24k finished (16:46:53)
Use of uninitialized value in printf at /usr/sbin/amstatus line 760.
This seems to be produced by amanda 2.4.3.  Not sure of the cause,
but just that part in the amstatus code (among others) got updated
in 2.4.4.  The most recent stable version is 2.4.4p3.
I guess upgrading will at least gid rid of that error message.
...
localhost:/home   0 17720729k dumping 0k (16:49:27)
(reformatted the above line, and added a space)
So this seems to be a 17 Gbyte partition.  And it seems to be
dumping directly to tape, bypassing the holdingdisk.
Am I correct?

It seems to be taking ages to complete this backup...is something wrong?
I don't know. How long is it running?  How long would it take
to write 17 Gbyte to tape at full speed?
Maybe your tapedrive is not streaming anymore, because the bypassing
of the holdingdisk?  If the datastream cannot follow the speed
of the tapedrive, the drive has to stop/backup a little/restart
and this has tremendous influence on the throughput (not to mention
the wear and tear on the drive and the cartridge!!!).
If this is indeed the case, possible solutions are:
- use a larger holdingdisk
- divide /home in smaller chunks, each fitting into the holdingdisk
  (best is fitting at least two of them: one taping and rest dumping)
  See docs/disklist in the sources for an example how to do this.
- disable software compression if cpu is the bottleneck
(amstatus in amanda 2.4.4p3 also has better indications of dumps
that bypass holdingdisk.  Another reason to upgrade.)
--
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: help getting started

[Stefan G. Weichinger]

Hi, Max,

on Mittwoch, 30. Juni 2004 at 13:06 you wrote to amanda-users:

MW> Hi,

MW> I'm getting some errors in my amstatus output - can anyone enlighten me?

>> # su amanda -c "/usr/sbin/amstatus DailySet1"
>> Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004
>> 
>> localhost:/etc   2  24k finished (16:46:53)
>> Use of uninitialized value in printf at /usr/sbin/amstatus line 760.
>> Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 761.
>> localhost:/home  017720729k dumping 0k (16:49:27)
>> Use of uninitialized value in addition (+) at /usr/sbin/amstatus line 770.
>> localhost:/usr/local 0   22701k finished (16:47:32)
>> localhost:/var   0  232660k wait for dumping driver: 
>> (aborted)

MW> It seems to be taking ages to complete this backup...is something wrong?

yes, it is. Those uninitialized values should not be there. A quick
look into amstatus seems to lead us to the estimates  

But the estimates seem to succeed.

What release of AMANDA is this, btw?

At first edit your disklist.

Don't use "localhost", use the full hostname instead.
Read docs/TOP-TEN-QUESTIONS for the explanation, if you want.

Stefan

Re: help getting started

[Max Waterman]

Hi,
I'm getting some errors in my amstatus output - can anyone enlighten me?
# su amanda -c "/usr/sbin/amstatus DailySet1"
Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004
localhost:/etc   2  24k finished (16:46:53)
Use of uninitialized value in printf at /usr/sbin/amstatus line 760.
Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 761.
localhost:/home  017720729k dumping0k (16:49:27)
Use of uninitialized value in addition (+) at /usr/sbin/amstatus line 770.
localhost:/usr/local 0   22701k finished (16:47:32)
localhost:/var   0  232660k wait for dumping driver: (aborted)
SUMMARY  part real estimated
  size  size
partition   :   4
estimated   :   4   17976128k
flush   :   00k
failed  :   0  0k   (  0.00%)
wait for dumping:   1 232660k   (  1.29%)
dumping to tape :   0  0k   (  0.00%)
dumping :   10k 17720729k (  0.00%) (  0.00%)
dumped  :   222725k22739k ( 99.94%) (  0.13%)
wait for writing:   00k0k (  0.00%) (  0.00%)
wait to flush   :   00k0k (100.00%) (  0.00%)
writing to tape :   00k0k (  0.00%) (  0.00%)
failed to tape  :   00k0k (  0.00%) (  0.00%)
taped   :   222725k22739k ( 99.94%) (  0.13%)
3 dumpers idle  : not-idle
taper writing, tapeq: 0
network free kps:   67
holding space   :   296960k (100.00%)
 dumper0 busy   :  0:02:17  ( 88.75%)
   taper busy   :  0:00:10  (  6.90%)
 0 dumpers busy :  0:00:17  ( 10.98%)  start-wait:  0:00:17  (100.00%)
 1 dumper busy  :  0:02:17  ( 89.02%)no-bandwidth:  0:01:49  ( 79.46%)
   start-wait:  0:00:28  ( 20.54%)
It seems to be taking ages to complete this backup...is something wrong?
Max.
Max Waterman wrote:
Thanks everyone for helping.
I got email working (albeit only locally since my isp is blocking my 
[chinese] IP address), so now I can get the reports.

I bought some more tapes, and have used the amrmtape command to start 
from scratch. Seems to be working like a charm. Next step is 'day 4' :)

http://www.harkness.co.uk/services/backup.html
Thanks again...until next time.
Max.
Paul Bijnens wrote:
Max Waterman wrote:
I am not really sure. Maybe this :
driver: result time 6.776 from taper: TAPE-ERROR [cannot overwrite 
active tape DailySet101]

It seems that the very first time you ran the backup for '/etc' it
worked fine. See:
  http://reality.sgiweb.org/maxw/tmp/amanda/log.20040623.0.mail )
This is how a normal run looks like.
For the next test, you seem to be using the same tape.
But you instructed to amanda ("tapecycle XXX") that she will not
overwrite an active tape.  So she cannot write to that tape.
She falls back to so called "degraded mode" backups dumping to
the holdingdisk.  You also have specified "reserve 100" (that's the
default if you didn't change it), meaning that in degraded mode,
100% of the holdingdisk is reserved for incremental backups.
But the only disklistentry was a new one, and amanda cannot
make an incremental backup when there is no full backup to base
it on.  Then she gives up.
Solution:  while testing, you can "amrmtape" the testing tape,
or you need to give more tapes (until you have "tapecycle" number
of tapes).

Re: help getting started

[Max Waterman]

Thanks everyone for helping.
I got email working (albeit only locally since my isp is blocking my 
[chinese] IP address), so now I can get the reports.

I bought some more tapes, and have used the amrmtape command to start 
from scratch. Seems to be working like a charm. Next step is 'day 4' :)

http://www.harkness.co.uk/services/backup.html
Thanks again...until next time.
Max.
Paul Bijnens wrote:
Max Waterman wrote:
I am not really sure. Maybe this :
driver: result time 6.776 from taper: TAPE-ERROR [cannot overwrite 
active tape DailySet101]

It seems that the very first time you ran the backup for '/etc' it
worked fine. See:
  http://reality.sgiweb.org/maxw/tmp/amanda/log.20040623.0.mail )
This is how a normal run looks like.
For the next test, you seem to be using the same tape.
But you instructed to amanda ("tapecycle XXX") that she will not
overwrite an active tape.  So she cannot write to that tape.
She falls back to so called "degraded mode" backups dumping to
the holdingdisk.  You also have specified "reserve 100" (that's the
default if you didn't change it), meaning that in degraded mode,
100% of the holdingdisk is reserved for incremental backups.
But the only disklistentry was a new one, and amanda cannot
make an incremental backup when there is no full backup to base
it on.  Then she gives up.
Solution:  while testing, you can "amrmtape" the testing tape,
or you need to give more tapes (until you have "tapecycle" number
of tapes).

Re: help getting started

[Paul Bijnens]

Max Waterman wrote:
I am not really sure. Maybe this :
driver: result time 6.776 from taper: TAPE-ERROR [cannot overwrite 
active tape DailySet101]
It seems that the very first time you ran the backup for '/etc' it
worked fine. See:
  http://reality.sgiweb.org/maxw/tmp/amanda/log.20040623.0.mail )
This is how a normal run looks like.
For the next test, you seem to be using the same tape.
But you instructed to amanda ("tapecycle XXX") that she will not
overwrite an active tape.  So she cannot write to that tape.
She falls back to so called "degraded mode" backups dumping to
the holdingdisk.  You also have specified "reserve 100" (that's the
default if you didn't change it), meaning that in degraded mode,
100% of the holdingdisk is reserved for incremental backups.
But the only disklistentry was a new one, and amanda cannot
make an incremental backup when there is no full backup to base
it on.  Then she gives up.
Solution:  while testing, you can "amrmtape" the testing tape,
or you need to give more tapes (until you have "tapecycle" number
of tapes).
--
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: help getting started

[Max Waterman]

Paul Bijnens wrote:
You can generate the email by hand and safe it in a file instead:
  cd ~amanda/DailySet1
  amreport DailySet1 -l log.X.X -f save-mail-file

Ah, more interesting, but still difficult to figure out if anything has 
gone wrong.

At least if you have file named log.datestamp.lvl.
There should also be a file named amdump.1 with a detailed
log of the serverside amdump program.
Any useful error message in that file?
I am not really sure. Maybe this :
driver: result time 6.776 from taper: TAPE-ERROR [cannot overwrite 
active tape DailySet101]

I have put the other files here, if you care to have a look (I've made 
'.mail' files using the above 'amreport' command) :

http://reality.sgiweb.org/maxw/tmp/amanda/
I'm guessing I should concentrate on making email work...
Max.

# su amanda -c "/usr/sbin/amadmin DailySet1 info"
Current info for localhost /home:
~  Stats: dump rates (kps), Full:   -1.0,  -1.0,  -1.0
~Incremental:   -1.0,  -1.0,  -1.0
~  compressed size, Full: -100.0%,-100.0%,-100.0%
~Incremental: -100.0%,-100.0%,-100.0%
~  Dumps: lev datestmp  tape file   origK   compK secs
Make any sense?

Seems to me like amdump did nothing at all.

Re: help getting started

[Paul Bijnens]

Max Waterman wrote:
Phil Homewood wrote:
| amdump doesn't generally (ever?) give output on stdout -- it
| emails it.
You can generate the email by hand and safe it in a file instead:
  cd ~amanda/DailySet1
  amreport DailySet1 -l log.X.X -f save-mail-file
At least if you have file named log.datestamp.lvl.
There should also be a file named amdump.1 with a detailed
log of the serverside amdump program.
Any useful error message in that file?

# su amanda -c "/usr/sbin/amadmin DailySet1 info"
Current info for localhost /home:
~  Stats: dump rates (kps), Full:   -1.0,  -1.0,  -1.0
~Incremental:   -1.0,  -1.0,  -1.0
~  compressed size, Full: -100.0%,-100.0%,-100.0%
~Incremental: -100.0%,-100.0%,-100.0%
~  Dumps: lev datestmp  tape file   origK   compK secs
Make any sense?
Seems to me like amdump did nothing at all.
--
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: help getting started

[Max Waterman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phil Homewood wrote:
| amdump doesn't generally (ever?) give output on stdout -- it
| emails it.
|
|
|>BTW, email isn't configured on the host machine - perhaps it is telling
|>me it is working, but I can't read what it says.
|
|
| That could well be the case. :-) Though it should spend
| a noticeable amount of time telling you nothing before
| it emails you.
Hrm - it does return pretty quickly :(
In any case, I should put more effort into getting mail working then;
thanks :)
|
| Does "amadmin config info" tell you anything useful?
# su amanda -c "/usr/sbin/amadmin DailySet1 info"
Current info for localhost /home:
~  Stats: dump rates (kps), Full:   -1.0,  -1.0,  -1.0
~Incremental:   -1.0,  -1.0,  -1.0
~  compressed size, Full: -100.0%,-100.0%,-100.0%
~Incremental: -100.0%,-100.0%,-100.0%
~  Dumps: lev datestmp  tape file   origK   compK secs
Make any sense?
Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA2Xxr4frZ3W7OHZMRApAmAJ46iwAH35SR4PSPlKNatE1ePBdlOACbB0H8
jTI1rIV7bSA2LkttkOInc1s=
=MQZo
-END PGP SIGNATURE-

Re: help getting started

[Phil Homewood]

Max Waterman wrote:
> Could it be that it's actually working, but doesn't give an output that
> I am expecting - ie a list of files, or something that says 'I backed up
> so many files' or even "I'm done".

amdump doesn't generally (ever?) give output on stdout -- it
emails it.

> BTW, email isn't configured on the host machine - perhaps it is telling
> me it is working, but I can't read what it says.

That could well be the case. :-) Though it should spend
a noticeable amount of time telling you nothing before
it emails you.

Does "amadmin config info" tell you anything useful?
-- 
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - A CyberGuard Company

Re: help getting started

[Max Waterman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Bijnens wrote:
| Max Waterman wrote:
|
|> When I get to this part :
|>
|> su amanda -c "/usr/sbin/amdump DailySet1"
|>
|> it seems to return quite quickly without any messages at all.
|
|
|
| The normal way is to run "amcheck" first, fix everything
| it complains about, before proceeding with a real amdump.
Yeah, that was the previous step on the step-by-step page I was using :
su amanda -c "/usr/sbin/amcheck DailySet1"
First time it ran, it complained about the
/usr/local/lib/amanda/exclude.gtar - there was no /usr/local/lib/amanda
directory, so I created it and the file.
After that, it ran fine; well, I think so - here's what it does now (but
I've done some later steps now) :
| # su amanda -c "/usr/sbin/amcheck DailySet1"
| Amanda Tape Server Host Check
| -
| Holding disk /var/tmp: 1122360 KB disk space available, that's plenty
| ERROR: cannot overwrite active tape DailySet101
|(expecting a new tape)
| NOTE: skipping tape-writable test
| NOTE: info dir /var/lib/amanda/DailySet1/curinfo/localhost/_home: does
not exist
| NOTE: index dir /var/lib/amanda/DailySet1/index/localhost/_home: does
not exist
| Server check took 4.220 seconds
|
| Amanda Backup Client Hosts Check
| 
| Client check: 1 host checked in 0.120 seconds, 0 problems found
|
| (brought to you by Amanda 2.4.3)
Spot anything?
|
| If you got that far, and still have trouble, you can have a look
| in /tmp/amanda, where each client has his logfiles.
Ooh. Many files. I guess I'll look in reverse chronological order.
| And there is this mailing list, where you can post the exact
| error messages you find.  Of course.
Hrm. Looking at those files, I don't see anything which looks like an
error. I have a few 'runtar' files which, I assume are an indication
that it is trying to make the backup, and there's nothing in them that
indicates an error.
Could it be that it's actually working, but doesn't give an output that
I am expecting - ie a list of files, or something that says 'I backed up
so many files' or even "I'm done".
Perhaps I am not specifying a valid place to backup. I am trying to
backup '/home' which is a mount point - though I did specify the
/dev/ida/c0d0p5 at one point, and /etc, but with the same effect.
How can I check that a backup completed successfully?
BTW, email isn't configured on the host machine - perhaps it is telling
me it is working, but I can't read what it says.
Max.
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA2Tgx4frZ3W7OHZMRAjNAAJ9M6CjsRiFhZL0HVmZaPUiDun2SqgCfWhPm
5wGsSHbdUZ0P8dkevAsytEc=
=PQ/b
-END PGP SIGNATURE-

Re: help getting started

[Paul Bijnens]

Max Waterman wrote:
When I get to this part :
su amanda -c "/usr/sbin/amdump DailySet1"
it seems to return quite quickly without any messages at all.

The normal way is to run "amcheck" first, fix everything
it complains about, before proceeding with a real amdump.
The error messages of amcheck are usually much less cryptic than
the other utilities.
If you got that far, and still have trouble, you can have a look
in /tmp/amanda, where each client has his logfiles.
And there is this mailing list, where you can post the exact
error messages you find.  Of course.
--
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: Help with teaching Amanda tape rotation

[Paul Bijnens]

Chris Cameron wrote:

I'm hoping someone here will be kind enough to help me teach Amanda
about our tape rotation. I've read through man pages and mailing lists,
but it seems the way Amanda deals with tapes doesn't lend itself well to
our rotation schedule.
I guess I don't understand the complicated taperotation completely.

I have a similar archiving schedule. It runs in the weekend.
The tapes are labelled "archive-001" to "archive-xxx", sequentially
numbered.
Every monday the tapes are sent offsite, and older tapes are
returned.  The last weekend of each month, I mark the tapes "no-reuse" 
and I give them a color with a fluo-marker.  These tapes stay offsite
permanently.

Amanda asks normally for the oldest tape that is marked "reuse".
By marking a tape "no-reuse", it is effectively take out of the
normal rotation.
My tapecycle covers a period of 3 months, but I have more tapes.
That means that amanda warns me if I feed a tape that is not three
months old.
Because some tapes are retracted from the rotation (by marking them
"no-reuse"), I regularly have to add new tapes.

some months will have 5 thursdays, while others only 4. What this meant
in the past was some tapes made on the final (non-permanent offsite)
week would stay offsite until another month came around with 5 Thursdays
in it, which at times can be at least a year.
I don't understand the part above...  Isn't is simply the oldest tape
that comes back?  or have the labels somehow linked to the week number
in the month?


--
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: Help with teaching Amanda tape rotation

[Jon LaBadie]

On Fri, May 07, 2004 at 10:03:10AM -0600, Chris Cameron wrote:
> I'm hoping someone here will be kind enough to help me teach Amanda
> about our tape rotation. I've read through man pages and mailing lists,
> but it seems the way Amanda deals with tapes doesn't lend itself well to
> our rotation schedule.
> 
> I'll spare you a complete explanation of our backup system, and just
> tell you where I've run into trouble. 
> 
> Tapes used on Thursday are sent offsite, and we receive an old offsite
> tape back to use for next Thursday. The tape we write to each Thursday
> is from 4 months earlier for that same week (so 3rd week of May, we get
> the tape used the 3rd week of January).
> 
> On the last Thursday of every month, rather than write to an old tape we
> take a new tape and send it offsite, never to return (we hope).
> 
> 
> So, the tact on this I've taken is trying to use different
> configurations, which works well. However the problem I have is that
> some months will have 5 thursdays, while others only 4. What this meant
> in the past was some tapes made on the final (non-permanent offsite)
> week would stay offsite until another month came around with 5 Thursdays
> in it, which at times can be at least a year.
> 
> 
> Is there any chance of getting Amanda to ask for the right tapes with
> this kind of setup? Do I have any alternatives? Up until now I'd just
> kill the tapelist file and start over.
> 

Amanda will always accept a newly labeled tape.  Even if asking for
a different tape.  Given that, could you set your tapecycle to
exactly the number of tapes in onsite/offsite rotation, sounds like
it is about 17 or 18 (4 months).  Don't label them "week 1 of month",
but just 1 to 17.  Amanda will ask for them in the order she first
sees them.

On the archive week, 4th or 5th week of the month whatever, label a
new tape and use it even if amanda asks for number 14.  Then mark
that tape (amadmin) as a "no-reuse" so it does not ask for the tape
the next time around but the index for the tape will remain available.

With a little creative regular expression you could make your config
recognize tapes with different labels for the rotation and for the
archive.  For example you might have your config use a label like
Backup-[A]*[0-9][0-9]*.  Then you could have Backup-1 to Backup-17
in regular roation and monthly create a Backup-A1, Backup-A2 ...
for the archive.

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

Re: Help: could not connect to HOST

[Hans van Zijst]

Hi Armando,

First an apology: you can't telnet to port 10080 because amandad uses UDP 
and telnet uses TCP. Sorry, my fault, I leapt before I looked...

Did you check your (x)inetd configuration? I don't know which one Slackware 
uses, but I suspect it's inetd. Make sure it starts amandad. Anyway, if 
your other hosts run fine, it should be enough to have the same 
configuration lines in /etc/inetd.conf. After you made inetd reread its 
configuration, check your logs for possible error messages. And while 
you're at it, check if the path to amandad is correct and that it is 
executable :)

If that's not it, check for hints in the debug files that Amanda leaves in 
/tmp/amanda.

And my personal favourite is to fire up a sniffer and simply check what goes 
on. Makes you understand a bit better what Amanda does anyway.

Kind regards,

Hans


On Tuesday 04 May 2004 20:01, Armando Taffarel Neto wrote:
> Hi Hans, thanks for help.
>
> I try telnet to port 10080, but is not possible. I think /etc/services
> and /etc/inetd.conf are ok, cause other hosts are working with the same
> configuration. I compile amanda with the same parameters on all hosts.
> I stop the firewall of the hosts and of the server, but no success.
> All my machines are powered by Slackware.
>
> Can you help me?
>
> Thanks,
>
> Armando
>
> Em Ter, 2004-05-04 às 08:05, Hans van Zijst escreveu:
> > Hi Armando,
> >
> > Could be several things. First, are you sure your clients have amandad
> > running? Check your inetd or xinetd configuration and test by
> > telnetting to port 10080. If you can connect, amandad is running.
> >
> > If amandad is running and you still can't connect, there's probably a
> > firewall between your backup server and clients. If so, make sure you
> > punch holes in it.
> >
> > Can't say a lot more without more details :)
> >
> > Regards,
> >
> > Hans
> >
> > On Monday 03 May 2004 23:08, Armando Taffarel Neto wrote:
> > > Hello!
> > >
> > > I have a problem. My amanda mail report returns:
> > >
> > > FAILURE AND STRANGE DUMP SUMMARY:
> > > mailman/usr/local/etc lev 0 FAILED 20040503[could not connect to
> > > mailman]
> > > webserver2 /home/diegob lev 0 FAILED 20040503[could not connect to
> > > webserver2]
> > > mercurio   /usr/local/apache lev 0 FAILED 20040503[could not connect
> > > to mercurio]
> > > ...
> > >
> > > DUMP SUMMARY:
> > > mailman  -cal/uvscan 0 FAILED
> > > ---
> > > mercurio /boot   0 FAILED
> > > ---
> > > ...
> > >
> > > Any ideia?
> > >
> > > Thanks all!!!
> > >
> > > Taffarel


__

 This message has been checked for all known viruses
__
 De informatie verzonden met dit e-mailbericht is
 uitsluitend bestemd voor de geadresseerde.
 Openbaarmaking, vermenigvuldiging, verspreiding en/of
 verstrekking van deze informatie aan derden is 
 niet toegestaan. Wij aanvaarden geen aansprakelijkheid
 voor de juiste en volledige overbrenging van de inhoud
 van een verzonden e-mail bericht, noch voor tijdige
 ontvangst ervan.
__

  HTTP://WWW.Syncera.NL
__

Re: Help: could not connect to HOST

[Hans van Zijst]

Hi Armando,

Could be several things. First, are you sure your clients have amandad 
running? Check your inetd or xinetd configuration and test by telnetting to 
port 10080. If you can connect, amandad is running.

If amandad is running and you still can't connect, there's probably a 
firewall between your backup server and clients. If so, make sure you punch 
holes in it.

Can't say a lot more without more details :)

Regards,

Hans


On Monday 03 May 2004 23:08, Armando Taffarel Neto wrote:
> Hello!
>
> I have a problem. My amanda mail report returns:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> mailman/usr/local/etc lev 0 FAILED 20040503[could not connect to
> mailman]
> webserver2 /home/diegob lev 0 FAILED 20040503[could not connect to
> webserver2]
> mercurio   /usr/local/apache lev 0 FAILED 20040503[could not connect to
> mercurio]
> ...
>
> DUMP SUMMARY:
> mailman  -cal/uvscan 0 FAILED
> ---
> mercurio /boot   0 FAILED
> ---
> ...
>
> Any ideia?
>
> Thanks all!!!
>
> Taffarel


__

 This message has been checked for all known viruses
__
 De informatie verzonden met dit e-mailbericht is
 uitsluitend bestemd voor de geadresseerde.
 Openbaarmaking, vermenigvuldiging, verspreiding en/of
 verstrekking van deze informatie aan derden is 
 niet toegestaan. Wij aanvaarden geen aansprakelijkheid
 voor de juiste en volledige overbrenging van de inhoud
 van een verzonden e-mail bericht, noch voor tijdige
 ontvangst ervan.
__

  HTTP://WWW.Syncera.NL
__

Re: Help configuring a Breece Hill Q7

[jlm17]

Thanks for all of the information. I'm running Gentoo Linux on a Sun 
Ultra 2. the TAPE.CHANGER document is just what I was looking for. mtx 
and mt all work fine so my only problem was in determining how to 
configure amanda.

David Wolfskill wrote:
On Mon, Feb 23, 2004 at 11:20:45AM -0500, jlm17 wrote:

How do I configure amanda to handle a Breece Hill Q7 tape changer? It 
has two disks and 28 tape slots. I am guessing that I need to set 
tpchanger to "chg-scsi" but how do I tell it what the tape changer 
device is, and about both of the drives and the number of tapes etc.?


As Joshua pointed out, it would help to mention something about the OS
with which you're working.
I have not used that model, but I do have a different (re-badged) Breece
Hill device working under FreeBSD-STABLE, using the chg-chio changer.
I needed to make changes in order for it to work:

* To the chg-chio Perl script itself -- I sent the patches that I found
  appropriate in to amanda-hackers a couple of months ago.
* To /usr/src/sys/cam/scsi/scsi_ch.c; it seems that (per one of the
  FreeBSD SCSI developers who has way more clue than I do) that the
  device was lying about how big a buffer would be required to hold
  the result from a SCSI "inquiry" request.  The patch was really gross:
  I just multiplied the amount of buffer (as calculated) by 4 before
  the malloc() was done.  (If someone really wants this patch, please
  mail me privately -- this isn't an amanda issue.)
Peace,
david
--
Jason M'Sadoques
(978)392-6417 Phone
(888)422-3597 Pager
[EMAIL PROTECTED]
A146B

Re: Help configuring a Breece Hill Q7

[David Wolfskill]

On Mon, Feb 23, 2004 at 11:20:45AM -0500, jlm17 wrote:
>How do I configure amanda to handle a Breece Hill Q7 tape changer? It 
>has two disks and 28 tape slots. I am guessing that I need to set 
>tpchanger to "chg-scsi" but how do I tell it what the tape changer 
>device is, and about both of the drives and the number of tapes etc.?

As Joshua pointed out, it would help to mention something about the OS
with which you're working.

I have not used that model, but I do have a different (re-badged) Breece
Hill device working under FreeBSD-STABLE, using the chg-chio changer.

I needed to make changes in order for it to work:

* To the chg-chio Perl script itself -- I sent the patches that I found
  appropriate in to amanda-hackers a couple of months ago.

* To /usr/src/sys/cam/scsi/scsi_ch.c; it seems that (per one of the
  FreeBSD SCSI developers who has way more clue than I do) that the
  device was lying about how big a buffer would be required to hold
  the result from a SCSI "inquiry" request.  The patch was really gross:
  I just multiplied the amount of buffer (as calculated) by 4 before
  the malloc() was done.  (If someone really wants this patch, please
  mail me privately -- this isn't an amanda issue.)

Peace,
david
-- 
David H. Wolfskill [EMAIL PROTECTED]

Re: Help configuring a Breece Hill Q7

[Joshua Baker-LePain]

On Mon, 23 Feb 2004 at 11:20am, jlm17 wrote

> How do I configure amanda to handle a Breece Hill Q7 tape changer? It 
> has two disks and 28 tape slots. I am guessing that I need to set 

Two disks?  Or drives?  :)

> tpchanger to "chg-scsi" but how do I tell it what the tape changer 
> device is, and about both of the drives and the number of tapes etc.?
> 
> Either help or some pointers to documentation that I may have missed 
> would be appreciated.

What you want is to get your OS (which you never mention) talking with the 
changer.  Once you get your OS to see and possibly maniuplate the device, 
docs/TAPE.CHANGERS will help you get started with amanda.  chg-scsi is one 
optin for tpchanger, chg-zd-mtx is another.  Both are well documented in 
docs/TAPE.CHANGERS and, in the case of chg-zd-mtx, in the chg-zd-mtx 
script itself.

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

Re: Help deciphering errors from Samba backup

[Fran Fabrizio]

Well, it doesn't appear to be -strictly- a Samba problem, as from the
command line if I do (on the Amanda server as the user 'amanda'):

-bash-2.05b$ smbclient -U Administrator //snapper/dfs
Password:
smb: \> cd \home\faculty\bryant\bryantback-brblt\Images\
smb: \home\faculty\bryant\bryantback-brblt\Images\> ls
  .   D0  Sat Nov 22 11:02:31
2003
  ..  D0  Sat Nov 22 11:02:31
2003
[snip]
  Portrait11.jpg  107056  Fri Apr 20 08:45:42
2001
[snip]
smb: \home\faculty\bryant\bryantback-brblt\Images\> get Portrait11.jpg
smb: \home\faculty\bryant\bryantback-brblt\Images\> quit

...it works fine.  So it's either the way I configured Amanda to use
Samba, or the way that Amanda invokes Samba, or the way that Amanda,
Samba, and Win2k3 Active Directory play together, I think.

-Fran 






On Tue, 2004-01-13 at 13:06, Kurt Yoder wrote:
> This is a Samba problem. smbclient is complaining that it can't
> access those directories. Here's my initial google query:
> 
> http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%22Server+packet+had+invalid+SMB+signature%21%22&btnG=Google+Search
> 
> This didn't seem to return many results for me. You may want to do
> some further digging in Samba mailing list archives, post to Samba
> lists, etc.
> 
> Fran Fabrizio said:
> >
> > I'm attempting to do my first backup via Samba.  The first night it
> > failed, which was due to me not having the latest version of Amanda
> > to
> > work with Samba 3.  I installed Amanda 2.4.4p2.  It ran again last
> 
> 
-- 

Fran Fabrizio
Senior Systems Analyst
Department of Computer and Information Sciences
University of Alabama - Birmingham
[EMAIL PROTECTED]
(205) 934-0653

Re: Help deciphering errors from Samba backup

[Kurt Yoder]

This is a Samba problem. smbclient is complaining that it can't
access those directories. Here's my initial google query:

http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%22Server+packet+had+invalid+SMB+signature%21%22&btnG=Google+Search

This didn't seem to return many results for me. You may want to do
some further digging in Samba mailing list archives, post to Samba
lists, etc.

Fran Fabrizio said:
>
> I'm attempting to do my first backup via Samba.  The first night it
> failed, which was due to me not having the latest version of Amanda
> to
> work with Samba 3.  I installed Amanda 2.4.4p2.  It ran again last




-- 
Kurt Yoder
Sport & Health network administrator

Re: Help - recovering without amanda

[Jon LaBadie]

On Thu, Dec 04, 2003 at 08:40:39AM -0600, Rebecca Pakish Crum wrote:
> 
> Another point I would mention having successfully tackled this wonderful
> part of Amanda: make sure the good version of tar is first in your path
> when recovering. Part of the reason I had problems is that when I went
> to 'tar t' my image, it was using old, crappy tar in /usr/sbin/, not
> good, healthy tar in /usr/local/bin/ this led me to believe I was doing
> it wrong, when in fact I just needed to clarify my path situation.

Having several "tar's" on my system too, including a gtar that
is not suitable, is one reason why I configure amanda to use
/usr/local/libexec/amgtar which I make sure is good.  Then whenever
working with amanda I use "amgtar".

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

RE: Help - recovering without amanda

[Rebecca Pakish Crum]

> Ditto everything that Joshua says AND,
> don't recover into anything but an empty directory on a
> largly empty file system unless you know, and have practiced, 
> what you are doing.
> 
> I have a pretty good idea what I'm doing, and I have
> practiced this technique.  Yet I still recover to an
> empty directory.  Then transfer things if I'm happy
> with what was recovered.

This is sound advice and once I did this, all was basically well.
Another point I would mention having successfully tackled this wonderful
part of Amanda: make sure the good version of tar is first in your path
when recovering. Part of the reason I had problems is that when I went
to 'tar t' my image, it was using old, crappy tar in /usr/sbin/, not
good, healthy tar in /usr/local/bin/ this led me to believe I was doing
it wrong, when in fact I just needed to clarify my path situation.

Thanks to Jon and Joshua, who as usual, have the answer and explain it
well.

RE: Help - recovering without amanda

[Rebecca Pakish Crum]

> I always restore to a temp space, just in case.

I should have done this...I never do direct restores...ugh
> 
> > # mt rewind
> > # mt fsf 1
> > # dd if=/dev/rmt/0hn bs=1 skip=1 | /usr/local/bin/tar -xf -
>   ^
> Bad.  It should be bs=32k, as above (and as in the header you 
> got running 
> the first command).  Also, an even safer way is to not do the pipe:
> 
> dd if=/dev/rmt/0hn bs=32k skip=1 of=output.file
> 
> Then you can do 'tar t' on the output file to get a table of 
> contents and *really* make sure it's what you want.

The bs=1 was a typo...I can't cut and paste because this box is on a
test LAN that's not even getting out the door...my bad. But skipping the
pipe is a good suggestion.
> 
> Here's a brief summary.  Amanda stores several files on a 
> tape.  The first 
> is the tape header.  That's what you skip over with 'mt fsf 
> 1'.  The next 
> file is the first dump image.  The next is the second image, 
> etc.  Each 
> dump image has a 32k amanda header, and then the image.
> 
> The dd command with with 'bs=32k skip=1' reads the whole 
> file, skipping 
> over the first 32k -- the amanda header.  It stops when it 
> hits EOF of 
> that dump image.  If you run the exact same dd command again, 
> you'll grab 
> the next backup image.
> 

Thanks...I'll keep plugging away...

Re: Help - recovering without amanda

[Jon LaBadie]

On Mon, Dec 01, 2003 at 04:23:41PM -0600, Rebecca Pakish Crum wrote:
> > > docs/RESTORE is pretty clear, IMHO.  Have a look at that, and
> > > then let us 
> > > know *exactly* what you don't understand.  As a short intro, 
> > > you use 'mt' 
> > > to position the tape, 'dd' to grab the raw image off the tape, and 
> > > restore/'tar x' to extract the contents of the image.
> >  
> > docs/RESTORE says the same thing as the chapter, basically.
> > 
> > when I run:
> > # mt rewind
> > # mt fsf 1
> > # dd if=/dev/rmt/0hn bs=32k count=1
> > I get:
> > AMANDA: FILE 20031127 spork.unterlaw.com 
> > /u05/oracle/admin/testua lev 0 comp N program 
> > /usr/local/bin/tar To restore position tape at start of file and run:
> > dd if= bs=32k skip=1 | /usr/local/bin/tar -f... -
> > 1+0 records in
> > 1+0 records out
> > 
> > GREAT...this is one of the two things I would like to 
> > restore. Fantastic. So it appears as if this is the first 
> > thing on the tape...so I cd /u05/oracle/admin and run # mt 
> > rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=1 skip=1 | 
> > /usr/local/bin/tar -xf -
> > 107+0 records in
> > 107+0 records out

Ditto everything that Joshua says AND,
don't recover into anything but an empty directory on a
largly empty file system unless you know, and have practiced,
what you are doing.

I have a pretty good idea what I'm doing, and I have
practiced this technique.  Yet I still recover to an
empty directory.  Then transfer things if I'm happy
with what was recovered.

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

RE: Help - recovering without amanda

[Joshua Baker-LePain]

On Mon, 1 Dec 2003 at 4:18pm, Rebecca Pakish Crum wrote

> when I run:
> # mt rewind
> # mt fsf 1
> # dd if=/dev/rmt/0hn bs=32k count=1
> I get:

The amanda header, which is the first 32k of that tape "file".  The rest 
of that tape file contains the backup image.

> So it appears as if this is the first thing on the tape...so I cd
> /u05/oracle/admin and run

I always restore to a temp space, just in case.

> # mt rewind
> # mt fsf 1
> # dd if=/dev/rmt/0hn bs=1 skip=1 | /usr/local/bin/tar -xf -
  ^
Bad.  It should be bs=32k, as above (and as in the header you got running 
the first command).  Also, an even safer way is to not do the pipe:

dd if=/dev/rmt/0hn bs=32k skip=1 of=output.file

Then you can do 'tar t' on the output file to get a table of contents
and *really* make sure it's what you want.

Here's a brief summary.  Amanda stores several files on a tape.  The first 
is the tape header.  That's what you skip over with 'mt fsf 1'.  The next 
file is the first dump image.  The next is the second image, etc.  Each 
dump image has a 32k amanda header, and then the image.

The dd command with with 'bs=32k skip=1' reads the whole file, skipping 
over the first 32k -- the amanda header.  It stops when it hits EOF of 
that dump image.  If you run the exact same dd command again, you'll grab 
the next backup image.

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

RE: Help - recovering without amanda

[Rebecca Pakish Crum]

> > docs/RESTORE is pretty clear, IMHO.  Have a look at that, and
> > then let us 
> > know *exactly* what you don't understand.  As a short intro, 
> > you use 'mt' 
> > to position the tape, 'dd' to grab the raw image off the tape, and 
> > restore/'tar x' to extract the contents of the image.
>  
> docs/RESTORE says the same thing as the chapter, basically.
> 
> when I run:
> # mt rewind
> # mt fsf 1
> # dd if=/dev/rmt/0hn bs=32k count=1
> I get:
> AMANDA: FILE 20031127 spork.unterlaw.com 
> /u05/oracle/admin/testua lev 0 comp N program 
> /usr/local/bin/tar To restore position tape at start of file and run:
> dd if= bs=32k skip=1 | /usr/local/bin/tar -f... -
> 1+0 records in
> 1+0 records out
> 
> GREAT...this is one of the two things I would like to 
> restore. Fantastic. So it appears as if this is the first 
> thing on the tape...so I cd /u05/oracle/admin and run # mt 
> rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=1 skip=1 | 
> /usr/local/bin/tar -xf -
> 107+0 records in
> 107+0 records out
> 
> 
> Great...now what? And now if I try to run that dd command 
> again, it says:
> read: not enough space
> read: not enough space
> 0+0 records in
> 0+0 records out
> 
> What 107 records is is talking about the first time?? The 
> tape never appeared to be active after I ran my dd command 
> the first time, so what did it do with the mysterious 107 records.
> 
> The doc is clear on what commands to run, but I ran them, and 
> nothing seems to have happened.

ACTUALLY - I take that back, something seems to have happened, because I
now have 464 files in /u05/oracle/admin that were not there before, and
are NOT /u05/oracle/admin/testua...it IS however the /etc slice from a
different server. How did that happen if I looked at the header for
after mt fsf 1 and it was /u05/oracle/admin/testua.  OMG...this is
horrible. 
> 

RE: Help - recovering without amanda

[Rebecca Pakish Crum]

> docs/RESTORE is pretty clear, IMHO.  Have a look at that, and 
> then let us 
> know *exactly* what you don't understand.  As a short intro, 
> you use 'mt' 
> to position the tape, 'dd' to grab the raw image off the tape, and 
> restore/'tar x' to extract the contents of the image.
 
docs/RESTORE says the same thing as the chapter, basically.

when I run:
# mt rewind
# mt fsf 1
# dd if=/dev/rmt/0hn bs=32k count=1
I get:
AMANDA: FILE 20031127 spork.unterlaw.com /u05/oracle/admin/testua lev 0
comp N program /usr/local/bin/tar
To restore position tape at start of file and run:
dd if= bs=32k skip=1 | /usr/local/bin/tar -f... -
1+0 records in
1+0 records out

GREAT...this is one of the two things I would like to restore.
Fantastic.
So it appears as if this is the first thing on the tape...so I cd
/u05/oracle/admin and run
# mt rewind
# mt fsf 1
# dd if=/dev/rmt/0hn bs=1 skip=1 | /usr/local/bin/tar -xf -
107+0 records in
107+0 records out


Great...now what? And now if I try to run that dd command again, it
says:
read: not enough space
read: not enough space
0+0 records in
0+0 records out

What 107 records is is talking about the first time?? The tape never
appeared to be active after I ran my dd command the first time, so what
did it do with the mysterious 107 records.

The doc is clear on what commands to run, but I ran them, and nothing
seems to have happened.

Re: Help - recovering without amanda

[Jack Twilley]

The files are stored on tape in the normal manner.  Use mt or
equivalent to position the tape to the proper file.

If you examine any of the amanda files that are on the tape, you'll
see something like this:

AMANDA: FILE 20031128 duchess.twilley.org ad0s1f lev 3 comp .gz program /sbin/dump
To restore, position tape at start of file and run:
dd if= bs=32k skip=1 | /usr/bin/gzip -dc |/sbin/restore -f... -

The first line tells you a bit about the file.

The second two lines are the instructions necessary to completely
restore the entire dump without having installed amanda.

This is one of my favorite parts of amanda.

Jack.
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash


pgp0.pgp
Description: PGP signature

Re: Help - recovering without amanda

[Joshua Baker-LePain]

On Mon, 1 Dec 2003 at 3:21pm, Rebecca Pakish Crum wrote

> Has anyone ever done this? I'm finding the documentation confusing.
> We're working on disaster recovery and I'd really like to know how to do
> this...
> 
> Specifically - in 'the chapter' they outline the commands one is
> supposed to use, but I don't understand them...

docs/RESTORE is pretty clear, IMHO.  Have a look at that, and then let us 
know *exactly* what you don't understand.  As a short intro, you use 'mt' 
to position the tape, 'dd' to grab the raw image off the tape, and 
restore/'tar x' to extract the contents of the image.

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

Re: help!! can't find my "1 problem"

[Frank Smith]

I'm cc-ing this to the list, it will generally give you a quicker
response to direct follow-ups to the list instead of just the
individual that responded to the first question.  Also, it gets
added to the archives to help future users and gives the list
a chance to correct incomplete (or incorrect) answers, or point
out better ways of doing things in unusual situations.

--On Friday, November 28, 2003 11:21:24 -0500 jessica blackburn <[EMAIL PROTECTED]> 
wrote:

> Thank you for the help!  I can't believe that I forgot to include the
> error message I received. It's telling me that it cannot find the
> localhost.  Maybe this is a stupid question, but I'm really new at
> this.  Thanks for any help!
> 
> jess
> 
>  -bash-2.05b$ /usr/sbin/amcheck DailySet1
> Amanda Tape Server Host Check
> -
> Holding disk /var/tmp: 29337136 KB disk space available, that's plenty
> amcheck-server: slot 1: date Xlabel DailySet100 (first labelstr
> match)
> NOTE: skipping tape-writable test
> Tape DailySet100 label ok
> Server check took 0.187 seconds
>  
> Amanda Backup Client Hosts Check
> 
> WARNING: localhost: selfcheck request timed out.  Host down?
> Client check: 1 host checked in 29.998 seconds, 1 problem found

First, I would recommend you not use 'localhost' in your disklist;
it will bite you someday in the future.  Use the machines fully-
qualified domain name (host.example.com) instead.
   As to the error message, there is a quite a bit about it on the
amanda.org web site, in the faq-o-matic:

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

Most likely your (x)inetd is not set up correctly for amanda, second
guess would be tcpwrapper/firewall problems.  Anything in syslog
or /tmp/amanda when amcheck runs?

Frank

>  
> (brought to you by Amanda 2.4.3)
> 
>  
> 
> On Wed, 2003-11-26 at 17:44, Frank Smith wrote:
>> --On Wednesday, November 26, 2003 17:13:48 -0500 jessica blackburn <[EMAIL 
>> PROTECTED]> wrote:
>> 
>> > Hello again  I got past my original error of the slot empty and have
>> > since moved on to this new one!  Does anyone have any ideas where to
>> > even start looking for this problem before this girly intern goes
>> > insane!  
>> > 
>> 
>> If you said what the problem is we could be a lot more help. From a
>> quick glance at your config I's say you misunderstood a couple of
>> parameters, see below.
>> 
>> 
>> > Here is my amanda.conf file as i have it right now.
>> > 
>> > Thanks!!!
>> > 
>> > 
>> > 
>> ># 
>> ># amanda.conf - sample Amanda configuration file.  This started off life
>> > as
>> >#   the actual config file in use at CS.UMD.EDU.
>> ># 
>> ># If your configuration is called, say, "csd", then this file normally
>> > goes
>> ># in /etc/amanda/csd/amanda.conf.
>> ># 
>> > 
>> > org "DailySet1"# your organization name for reports
>> > mailto "amanda"# space separated list of operators at your site
>> > dumpuser "amanda"  # the user to run dumps under
>> > 
>> > inparallel 4   # maximum dumpers that will run in parallel
>> > netusage  600 Kbps # maximum net bandwidth for Amanda, in KB per sec
>> > 
>> > dumpcycle 4 weeks  # the number of days in the normal dump cycle
>> 
>> Seems rather long, it means that Amanda only schedules one full backup
>> of each filesystem every 4 weeks (they will probably happen more often
>> than that if there is plenty of room on the tapes, but you are only
>> gauranteed one).  To restore a filesystem will probably require a stack
>> of tapes to get all the incrementals.
>> 
>> > runspercycle 4 weeks# the number of amdump runs in dumpcycle days
>> 
>> runspercycle is how many time you run amdump during your dumpcycle.  If you
>> run Amanda every day then it should be 28 (just the number, no units are
>> needed).  If you only run it Monday through Friday it should be 20.
>> 
>> > tapecycle 25 tapes # the number of tapes in rotation
>> ># 4 weeks (dumpcycle) times 5 tapes per week (just
>> ># the weekdays) plus a few to handle errors that
>> ># need amflush and so we do not overwrite the full
>> ># backups performed at the beginning of the previous
>> ># cycle
>> 
>> You have to have at least as many tapes as you have runspercycle (i.e. 28
>> [or 24 if you ongo run M-F] in your config).  Having 1 or 2 extras is
>> almost a neceesity to avoid overwriting your last full backup of something
>> if it should fail for some reason.  Many people on the list prefer 2x or
>> more.
>> 
>> >### ### ### 
>> ># WARNING: don't use `inf' for tapecycle, it's broken!
>> >### ### ### 
>> > 
>> > bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
>> > bumpdays 1 # minimum days at each level
>> > bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
>> > 
>> > etimeout 300   # number of seconds per filesy

Re: help!! can't find my "1 problem"

[Frank Smith]

--On Wednesday, November 26, 2003 17:13:48 -0500 jessica blackburn <[EMAIL PROTECTED]> 
wrote:

> Hello again  I got past my original error of the slot empty and have
> since moved on to this new one!  Does anyone have any ideas where to
> even start looking for this problem before this girly intern goes
> insane!  
> 

If you said what the problem is we could be a lot more help. From a
quick glance at your config I's say you misunderstood a couple of
parameters, see below.


> Here is my amanda.conf file as i have it right now.
> 
> Thanks!!!
> 
> 
> 
># 
># amanda.conf - sample Amanda configuration file.  This started off life
> as
>#   the actual config file in use at CS.UMD.EDU.
># 
># If your configuration is called, say, "csd", then this file normally
> goes
># in /etc/amanda/csd/amanda.conf.
># 
> 
> org "DailySet1"   # your organization name for reports
> mailto "amanda"   # space separated list of operators at your site
> dumpuser "amanda" # the user to run dumps under
> 
> inparallel 4  # maximum dumpers that will run in parallel
> netusage  600 Kbps# maximum net bandwidth for Amanda, in KB per sec
> 
> dumpcycle 4 weeks # the number of days in the normal dump cycle

Seems rather long, it means that Amanda only schedules one full backup
of each filesystem every 4 weeks (they will probably happen more often
than that if there is plenty of room on the tapes, but you are only
gauranteed one).  To restore a filesystem will probably require a stack
of tapes to get all the incrementals.

> runspercycle 4 weeks# the number of amdump runs in dumpcycle days

runspercycle is how many time you run amdump during your dumpcycle.  If you
run Amanda every day then it should be 28 (just the number, no units are
needed).  If you only run it Monday through Friday it should be 20.

> tapecycle 25 tapes# the number of tapes in rotation
>   # 4 weeks (dumpcycle) times 5 tapes per week (just
>   # the weekdays) plus a few to handle errors that
>   # need amflush and so we do not overwrite the full
>   # backups performed at the beginning of the previous
>   # cycle

You have to have at least as many tapes as you have runspercycle (i.e. 28
[or 24 if you ongo run M-F] in your config).  Having 1 or 2 extras is
almost a neceesity to avoid overwriting your last full backup of something
if it should fail for some reason.  Many people on the list prefer 2x or
more.

>### ### ### 
># WARNING: don't use `inf' for tapecycle, it's broken!
>### ### ### 
> 
> bumpsize 20 Mb# minimum savings (threshold) to bump level 1 -> 2
> bumpdays 1# minimum days at each level
> bumpmult 4# threshold = bumpsize * bumpmult^(level-1)
> 
> etimeout 300  # number of seconds per filesystem for estimates.

If you have large filesystems with lots of small files you may need to
increase this.

># etimeout -600# total number of seconds for estimates.
># a positive number will be multiplied by the number of filesystems on
># each host; a negative number will be taken as an absolute total
> time-out.
># The default is 5 minutes per filesystem.
>   
> 
># Specify tape device and/or tape changer.  If you don't have a tape
># changer, and you don't want to use more than one tape per run of
># amdump, just comment out the definition of tpchanger.
> 
># Some tape changers require tapedev to be defined; others will use
># their own tape device selection mechanism.  Some use a separate tape
># changer device (changerdev), others will simply ignore this
># parameter.  Some rely on a configuration file (changerfile) to
># obtain more information about tape devices, number of slots, etc;
># others just need to store some data in files, whose names will start
># with changerfile.  For more information about individual tape
># changers, read docs/TAPE.CHANGERS.
> 
># At most one changerfile entry must be defined; select the most
># appropriate one for your configuration.  If you select man-changer,
># keep the first one; if you decide not to use a tape changer, you may
># comment them all out.
> 
> runtapes 1# number of tapes to be used in a single run of amdump
> tpchanger "chg-multi" # the tape-changer glue script
> tapedev "file:/backup/"   # the no-rewind tape device to be used
># rawtapedev "/dev/null"   # the raw device to be used (ftape only)
># changerfile "/var/lib/amanda/DailySet1/changer"
># changerfile "/var/lib/amanda/DailySet1/changer-status"
> changerfile "/etc/amanda/DailySet1/chg-multi.conf"
> changerdev "/dev/null"
> 
> tapetype HARD-DISK# what kind of tape it is (see tapetypes below)
> define tapetype HARD-DISK{
>   comment "20GB Hard disk"
>   length 2 mbytes
> }
> 
> 
> labelstr "^DailySet1[0-9][0-9]*$" # label constraint regex: all tapes
> must match

Re: help

[Stefan G. Weichinger]

Hi, [EMAIL PROTECTED],

on Mittwoch, 29. Oktober 2003 at 08:30 you wrote to amanda-users:

WFec> help

which help?

geht auch auf deutsch, wenn gewünscht ;-)

-- 
best regards,
Stefan

mailto:[EMAIL PROTECTED]

Stefan Gregor Weichinger
oops! linux consulting and implementation

Re: help

[Francisco Garcia]

What kind of help do you need?

[EMAIL PROTECTED] wrote:

help
--
Wolfgang Fuertbauer (E-Mail: [EMAIL PROTECTED])
EBEWE Pharma  Tel: ++43 7665 8123 315
Mondseestrasse 11 Fax: ++43 7665 8123 11
4866  Unterach, Austria
http://www.ebewe.com




 

Re: Help, Strange Error !!

[C.Scheeder]

Hi,
have you tried it with a brand new tape?
or only with tapes the old drive failed on?
I had a sdt-9000 die similar, producing write-errors
with medium-errors.
the Tapes wreer unusable even in a new drive until i took a big magnet
and wiped every bit on these tapes. after that they started working
again.
The defective drive must have written such a mess at the header peace of
the tape(s), so no other drive's would write to them until they where
bulk erased.
Christoph
Roberto Samarone Araújo (RSA) schrieb:
Hi,

  I have an Amanda Backup that was working fine now, when I try to use:
su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me:
   st0: Error with sense data: Current st09:00: sense key Medium
Error
   Additional sense indicates Write error
   
   If I try: mt erase /dev/st0, it return me:

st0: Error with sense data: Current st09:00: sense key Medium
Error
Additional sense indicates Write error
mt: /dev/tape: Input/Output error
I change my SDT-9000 tape to a new one and the problem persist.

I saw on the logs the messages:

st0: Block limits 1 - 16777215 bytes
st0: Error with sense data: Current st09:00 sense key Medium
Error
Additional sense indicates Write error
Does anyone could help me please ? When a try to recover a backup it
worked fine.
Roberto Samarone Araujo

Re: Help, Strange Error !!

[kend]

I had something very similar to this happen with my AIT-2 changer when it had
to be reset to company defaults.  Unbeknownst to me, the default tape for the
changer (drive? I don't remember) was DLT -- and, when it didn't find AIT-2
tapes, it complained bitterly, but not with any error that was obvious.  If
you've done anything "interesting" to your changer/drive lately, you just
might want to make sure it's still configured correctly.

$.02,

Ken D'Ambrosio
Sr. SysAdmin,
Xanoptix, Inc.

> Roberto Samarone Araújo (RSA) wrote:
>
>>Hi,
>>
>>  I have an Amanda Backup that was working fine now, when I try to
>> use:
>>su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me:
>>
>>   st0: Error with sense data: Current st09:00: sense key Medium
>>Error
>>   Additional sense indicates Write error
>>   
>>
>>   If I try: mt erase /dev/st0, it return me:
>>
>>st0: Error with sense data: Current st09:00: sense key Medium
>>Error
>>Additional sense indicates Write error
>>mt: /dev/tape: Input/Output error
>>
>>I change my SDT-9000 tape to a new one and the problem persist.
>>
>>I saw on the logs the messages:
>>
>>st0: Block limits 1 - 16777215 bytes
>>st0: Error with sense data: Current st09:00 sense key Medium
>>Error
>>Additional sense indicates Write error
>>
>>Does anyone could help me please ? When a try to recover a backup
>> it
>>worked fine.
>>
>>Roberto Samarone Araujo
>>
>>
>>
>>
>>
> I'd check my perms on /dev/st0 as well...make sure the restore didn't
> change any setting back that you may have edited.  Otherwise you could
> have a hardware problem...but I'd lean more to perms.
>
> =G=

Re: Help, Strange Error !!

[Galen Johnson]

Roberto Samarone Araújo (RSA) wrote:

Hi,

 I have an Amanda Backup that was working fine now, when I try to use:
su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me:
  st0: Error with sense data: Current st09:00: sense key Medium
Error
  Additional sense indicates Write error
  
  If I try: mt erase /dev/st0, it return me:

   st0: Error with sense data: Current st09:00: sense key Medium
Error
   Additional sense indicates Write error
   mt: /dev/tape: Input/Output error
   I change my SDT-9000 tape to a new one and the problem persist.

   I saw on the logs the messages:

   st0: Block limits 1 - 16777215 bytes
   st0: Error with sense data: Current st09:00 sense key Medium
Error
   Additional sense indicates Write error
   Does anyone could help me please ? When a try to recover a backup it
worked fine.
   Roberto Samarone Araujo



 

I'd check my perms on /dev/st0 as well...make sure the restore didn't 
change any setting back that you may have edited.  Otherwise you could 
have a hardware problem...but I'd lean more to perms.

=G=

Re: Help, Strange Error !!

[Joshua Baker-LePain]

On Wed, 22 Oct 2003 at 12:41pm, Roberto Samarone Araújo (RSA) wrote

>st0: Error with sense data: Current st09:00: sense key Medium
> Error
>Additional sense indicates Write error

Try cleaning the drive.

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

Re: Help, Strange Error !!

[Frank Smith]

--On Wednesday, October 22, 2003 12:41:02 -0700 "Roberto Samarone Araújo (RSA)" 
<[EMAIL PROTECTED]> wrote:

> Hi,
> 
>   I have an Amanda Backup that was working fine now, when I try to use:
> su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me:
> 
>st0: Error with sense data: Current st09:00: sense key Medium
> Error
>Additional sense indicates Write error
>
> 
>If I try: mt erase /dev/st0, it return me:
> 
> st0: Error with sense data: Current st09:00: sense key Medium
> Error
> Additional sense indicates Write error
> mt: /dev/tape: Input/Output error
> 
> I change my SDT-9000 tape to a new one and the problem persist.
> 
> I saw on the logs the messages:
> 
> st0: Block limits 1 - 16777215 bytes
> st0: Error with sense data: Current st09:00 sense key Medium
> Error
> Additional sense indicates Write error
> 
> Does anyone could help me please ? When a try to recover a backup it
> worked fine.
> 
> Roberto Samarone Araujo
> 

Is the tape write-protected?

Frank


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

Re: Help with Dell 132T

[Alexander Jolk]

Alexander Jolk wrote:
> I have just got a PV-132T with an LTO-2 drive.  I'm in the
> process of setting it up and will report on my success
> or failure in the next few days.

Just to keep you posted, the PV-132T works fine for me on Debian woody,
amanda version 2.4.4p1-20030716, with chg-zd-mtx and mtx-1.2.16rel. 
Still scratching at setting up my disklist and dumpcycle, but actual
backup and restore are working.

The barcode reader works, see `Barcode readers' in the amanda
FAQ-O-matic (http://amanda.sourceforge.net/fom-serve/cache/273.html).

Attention to potential buyers: the changer doesn't properly support the
SCSI `EAAP' command, which means you can't use its import/export slot
from mtx.  (See
http://sourceforge.net/mailarchive/forum.php?thread_id=3005134&forum_id=5040
for more details.)  This doesn't hurt amanda operations, of course.

Let me know if any of you want more information.  (Also, Jon, do you
want an update for your usage survey?)

Alex

-- 
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: Help

[Paul Bijnens]

Rohit wrote:

On machine1 (RH7.3)
amanda-2.4.2p2-7
amanda-client-2.4.2p2-7
in amanda 2.4.2 the only way to support multiple excludes
is to give it a filename with "exclude list" containing the list of the
excluded files.  Read "man amanda" on the RH7.3 machine.

Amanda Backup Client Hosts Check

WARNING: machine1:/h2 does not support multiple exclude
WARNING: machine1: selfcheck request timed out.  Host down?
Client check: 3 hosts checked in 30.071 seconds, 1 problem found
The timeout problem is maybe related; or could be something completely
different.  Try solving one problem at a time...
--
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: Help

[Rohit]

Thanks for your response. Here are amanda versions which I am running on
tape server:

Tape Server (RH9)
amanda-client-2.4.3-4
amanda-server-2.4.3-4
amanda-2.4.3-4

On machine1 (RH7.3)
amanda-2.4.2p2-7
amanda-client-2.4.2p2-7

And yes. /h2 exists on machine1. I now named my DLE like this:

machine1 /h2 {
comp-user-tar
exclude "./Appleshare" "./apple"
}

But even when I run amcheck.. it gives this error:

-bash-2.05b$ /usr/sbin/amcheck -c DailySet1

Amanda Backup Client Hosts Check

WARNING: machine1:/h2 does not support multiple exclude
WARNING: machine1: selfcheck request timed out.  Host down?
Client check: 3 hosts checked in 30.071 seconds, 1 problem found

Thanks again!

- Original Message - 
From: "Paul Bijnens" <[EMAIL PROTECTED]>
To: "Rohit" <[EMAIL PROTECTED]>; "AMANDA Users"
<[EMAIL PROTECTED]>
Sent: Monday, October 06, 2003 3:22 PM
Subject: Re: Help


> Rohit wrote:
> >
> > my disklist entry looks like this:
> >
> > machine1 /ha2 /h2 {
> >   comp-user-tar
> >   exclude "./Appleshare" "./apple"
> > }
>
> Does "/h2" on machine1 exist? Or is it named "/ha2"?
> Why do you have a different name here?
> The possibility to give a label to the share is
> to do something like:

> machine1 /home /snapshot/home comp-user-tar
>
> Here you make a backup of the the filesystem "/home"
> but you you do this by backing up the snapshot filesystem
> mounted under /snapshot/home.
>
> Or something like this:
>
> machine1 /homeAN /home {
> comp-user-tar
> include "./[a-nA-N]*"
> }
> machine1 /homeREST /home {
> comp-user-tar
> exclude "./[a-nA-N]*"
> }
>
> Here you make a backup of the same share twice, but with
> a complementing include/exclude option.  Handy to split
> a large filesystem into multiple DLE's.
>
> But labeling a DLE different than it's physical name, is
> just plain confusing.  Which one is real?
>
>
> > machine1 /Label-Group1 //meosis/users {
> >  comp-user-tar
> >  exclude "./user1" "./user2" "./user3" "./user4"
> > }
>
> Here you have a samba-share on host meosis, to be backed
> up by smbclient on machine1.  (samba implementation for amanda
> cannot do multiple excludes (yet)
>
> Is that what you want?  Is smbclient compiled in on the amanda
> software on "machine1"?
>
> It also helps specifying which version of amanda (on server and client)
> you are using.
>
>
> >
> > Where could I have gone wrong?
>
> In reading the docs?   :-)
>
> -- 
> 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: Help

[Paul Bijnens]

Rohit wrote:
my disklist entry looks like this:

machine1 /ha2 /h2 {
  comp-user-tar
  exclude "./Appleshare" "./apple"
}
Does "/h2" on machine1 exist? Or is it named "/ha2"?
Why do you have a different name here?
The possibility to give a label to the share is
to do something like:
machine1 /home /snapshot/home comp-user-tar

Here you make a backup of the the filesystem "/home"
but you you do this by backing up the snapshot filesystem
mounted under /snapshot/home.
Or something like this:

machine1 /homeAN /home {
comp-user-tar
include "./[a-nA-N]*"
}
machine1 /homeREST /home {
comp-user-tar
exclude "./[a-nA-N]*"
}
Here you make a backup of the same share twice, but with
a complementing include/exclude option.  Handy to split
a large filesystem into multiple DLE's.
But labeling a DLE different than it's physical name, is
just plain confusing.  Which one is real?

machine1 /Label-Group1 //meosis/users {
 comp-user-tar
 exclude "./user1" "./user2" "./user3" "./user4"
}
Here you have a samba-share on host meosis, to be backed
up by smbclient on machine1.  (samba implementation for amanda
cannot do multiple excludes (yet)
Is that what you want?  Is smbclient compiled in on the amanda
software on "machine1"?
It also helps specifying which version of amanda (on server and client)
you are using.

Where could I have gone wrong?
In reading the docs?   :-)

--
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: Help

[Rohit]

I also get these errors when I try to run amcheck:

-bash-2.05b$ /usr/sbin/amcheck -c DailySet1

Amanda Backup Client Hosts Check

WARNING: machine1:/Label-Group1 does not support multiple exclude
ERROR: machine1:/Label-Group1 (//meosis/users): selfcheck does not support
device.
ERROR: machine1:/Label-Group1 (//meosis/users): sendsize does not support
device.
ERROR: machine1:/Label-Group1 (//meosis/users): sendbackup does not support
device.
WARNING: machine1:/ha2 does not support multiple exclude
ERROR: machine1:/ha2 (/h2): selfcheck does not support device.
ERROR: machine1:/ha2 (/h2): sendsize does not support device.
ERROR: machine1:/ha2 (/h2): sendbackup does not support device.

my disklist entry looks like this:

machine1 /ha2 /h2 {
  comp-user-tar
  exclude "./Appleshare" "./apple"
}

machine1 /Label-Group1 //meosis/users {
 comp-user-tar
 exclude "./user1" "./user2" "./user3" "./user4"
}

Where could I have gone wrong?

...Rohit


- Original Message - 
From: "Rohit" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 06, 2003 2:05 PM
Subject: Re: Help


> Thanks Jon. I tried to create DLE in disklist file but failed.
> What exactly is the syntax of creating DLE?
>
>{
> dumptype
> exclude or include list etc.
>
> } 1
>
> Thanks a lot again!
>
> - Original Message - 
> From: "Jon LaBadie" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, October 05, 2003 10:32 PM
> Subject: Re: Help
>
>
> > On Sun, Oct 05, 2003 at 04:04:46PM +0530, Rohit wrote:
> > > Thanks for your response and sorry for not giving you enough
> > > information before hand. I managed to get past this error, I
> > > have another question though :)
> > >
> > > I have various shares on the servers which are close to
> > > 10 GB to 25 GB of data on each share. What I have is
> > > 12/24 GB HP-DAT drive. How does amanda handle full backups
> > > in this case? Does it split the image across two different
> > > tapes?
> >
> > Amanda deals with "disk list entries" (DLEs) these could be
> > an entire file system/shares backed up by a file system dump
> > program (system specific) or by gnutar.  A DLE could also
> > be a partial file system/share starting at some directory
> > under the top level.  These can only be backed up by gnutar.
> >
> > The limitation is that the backup image (after compression
> > if used) must fit on a single tape.  If the backup image of
> > a DLE is larger than a tape, then the administrator must
> > split the single DLE into multiple DLE's.  See the sample
> > disklist in the examples directory of your amanda source.
> >
> >
> > -- 
> > Jon H. LaBadie  [EMAIL PROTECTED]
> >  JG Computing
> >  4455 Province Line Road(609) 252-0159
> >  Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Help

[Rohit]

Thanks Jon. I tried to create DLE in disklist file but failed. 
What exactly is the syntax of creating DLE?

   {
dumptype
exclude or include list etc. 

} 1

Thanks a lot again!

- Original Message - 
From: "Jon LaBadie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 05, 2003 10:32 PM
Subject: Re: Help


> On Sun, Oct 05, 2003 at 04:04:46PM +0530, Rohit wrote:
> > Thanks for your response and sorry for not giving you enough
> > information before hand. I managed to get past this error, I
> > have another question though :)
> > 
> > I have various shares on the servers which are close to
> > 10 GB to 25 GB of data on each share. What I have is
> > 12/24 GB HP-DAT drive. How does amanda handle full backups
> > in this case? Does it split the image across two different
> > tapes?
> 
> Amanda deals with "disk list entries" (DLEs) these could be
> an entire file system/shares backed up by a file system dump
> program (system specific) or by gnutar.  A DLE could also
> be a partial file system/share starting at some directory
> under the top level.  These can only be backed up by gnutar.
> 
> The limitation is that the backup image (after compression
> if used) must fit on a single tape.  If the backup image of
> a DLE is larger than a tape, then the administrator must
> split the single DLE into multiple DLE's.  See the sample
> disklist in the examples directory of your amanda source.
> 
> 
> -- 
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Help

[Jon LaBadie]

On Sun, Oct 05, 2003 at 04:04:46PM +0530, Rohit wrote:
> Thanks for your response and sorry for not giving you enough
> information before hand. I managed to get past this error, I
> have another question though :)
> 
> I have various shares on the servers which are close to
> 10 GB to 25 GB of data on each share. What I have is
> 12/24 GB HP-DAT drive. How does amanda handle full backups
> in this case? Does it split the image across two different
> tapes?

Amanda deals with "disk list entries" (DLEs) these could be
an entire file system/shares backed up by a file system dump
program (system specific) or by gnutar.  A DLE could also
be a partial file system/share starting at some directory
under the top level.  These can only be backed up by gnutar.

The limitation is that the backup image (after compression
if used) must fit on a single tape.  If the backup image of
a DLE is larger than a tape, then the administrator must
split the single DLE into multiple DLE's.  See the sample
disklist in the examples directory of your amanda source.


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

Re: Help

[Rohit]

Thanks for your response and sorry for not giving you enough
information before hand. I managed to get past this error, I
have another question though :)

I have various shares on the servers which are close to
10 GB to 25 GB of data on each share. What I have is
12/24 GB HP-DAT drive. How does amanda handle full backups
in this case? Does it split the image across two different
tapes?

Also on one particular partition where the data is just
6GB or so.. Amanda complains that there is that dump (level 0
for /home) partition is larger than the tape. How do I handle
backups for such partitions?

This is the error which I got from Amanda Mail report after
running amdump command:

*** A TAPE ERROR OCCURRED: [cannot overwrite active tape TLS-set-1-01].
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: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
  localhost  /home lev 0 FAILED [dump larger than tape, but cannot
incremental dump new disk]


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:01
Run Time (hrs:min) 0:06
Dump Time (hrs:min)0:04   0:00   0:04
Output Size (meg) 266.80.0  266.8
Original Size (meg)   912.40.0  912.4
Avg Compressed Size (%)29.2--29.2   (level:#disks ...)
Filesystems Dumped3  0  3   (1:3)
Avg Dump Rate (k/s)  1025.9--  1025.9

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


NOTES:
  planner: Adding new disk localhost:/home.
  planner: Full dump of localhost:/var/www specially promoted from 7 days
ahead.


DUMP SUMMARY:
 DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-- - 
localhost/home   0 FAILED ---
localhost-al/test 1  348030  78504  22.6   1:26 908.9   N/A   N/A
localhost/var/log1   88580   5178   5.8   0:08 616.5   N/A   N/A
localhost/var/www1  497650 189475  38.1   2:511104.9   N/A   N/A

(brought to you by Amanda version 2.4.3)

- Original Message - 
From: "Jon LaBadie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 04, 2003 8:46 PM
Subject: Re: Help


> On Sat, Oct 04, 2003 at 01:18:30PM +0530, Rohit wrote:
> > Any idea about this error?
> >
> > Thanks!
> >
> > Rohit
> >
> > *** THE DUMPS DID NOT FINISH PROPERLY!
> >
> > The next tape Amanda expects to use is: a new tape.
> >
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   localhost  /usr/local/test RESULTS MISSING
> >   localhost  /var/www RESULTS MISSING
> >   localhost  /home RESULTS MISSING
> >   localhost  /var/log RESULTS MISSING
> >   amreport: ERROR error copying PostScript template file
> > /etc/amanda/DailySet1/HP-DAT.ps: Broken pipe
> >
> >
> > STATISTICS:
> >   Total   Full  Daily
> >       
> > Estimate Time (hrs:min)0:00
> > Run Time (hrs:min) 0:00
> > Dump Time (hrs:min)0:00   0:00   0:00
> > Output Size (meg)   0.00.00.0
> > Original Size (meg) 0.00.00.0
> > Avg Compressed Size (%) -- -- -- 
> > Filesystems Dumped0  0  0
> > Avg Dump Rate (k/s) -- -- -- 
> >
> > Tape Time (hrs:min)0:00   0:00   0:00
> > Tape Size (meg) 0.00.00.0
> > Tape Used (%)   0.00.00.0
> > Filesystems Taped 0  0  0
> > Avg Tp Write Rate (k/s) -- -- -- 
> >
> >
> > DUMP SUMMARY:
> >  DUMPER STATSTAPER STATS
> > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS
KB/s
>
> -- - 
> > localhost-al/test   MISSING --
> > localhost/var/log
 MISSING --
> > localhost/var/www
 MISSING --
> >
> > (brought to you by Amanda version 2.4.3)
> >
> >
>
> With so little info, my psychic powers are limited.  :)
>
> You need to look at:
> the amcheck output,
> the log files, and
> the debug files.
>
> -- 
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Help

[Jon LaBadie]

On Sat, Oct 04, 2003 at 01:18:30PM +0530, Rohit wrote:
> Any idea about this error?
> 
> Thanks!
> 
> Rohit
> 
> *** THE DUMPS DID NOT FINISH PROPERLY!
> 
> The next tape Amanda expects to use is: a new tape.
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   localhost  /usr/local/test RESULTS MISSING
>   localhost  /var/www RESULTS MISSING
>   localhost  /home RESULTS MISSING
>   localhost  /var/log RESULTS MISSING
>   amreport: ERROR error copying PostScript template file
> /etc/amanda/DailySet1/HP-DAT.ps: Broken pipe
> 
> 
> STATISTICS:
>   Total   Full  Daily
>       
> Estimate Time (hrs:min)0:00
> Run Time (hrs:min) 0:00
> Dump Time (hrs:min)0:00   0:00   0:00
> Output Size (meg)   0.00.00.0
> Original Size (meg) 0.00.00.0
> Avg Compressed Size (%) -- -- -- 
> Filesystems Dumped0  0  0
> Avg Dump Rate (k/s) -- -- -- 
> 
> Tape Time (hrs:min)0:00   0:00   0:00
> Tape Size (meg) 0.00.00.0
> Tape Used (%)   0.00.00.0
> Filesystems Taped 0  0  0
> Avg Tp Write Rate (k/s) -- -- -- 
> 
> 
> DUMP SUMMARY:
>  DUMPER STATSTAPER STATS
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
> -- - 
> localhost-al/test   MISSING --
> localhost/var/log  MISSING --
> localhost/var/www  MISSING --
> 
> (brought to you by Amanda version 2.4.3)
> 
> 

With so little info, my psychic powers are limited.  :)

You need to look at:
the amcheck output,
the log files, and
the debug files.

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

Re: Help with writing to tape

[Jon LaBadie]

On Thu, Sep 25, 2003 at 09:46:38AM -0500, chris weisiger wrote:
> I am able to use the following commands for amanda properly:
> amlabel
> amtape
> amcheck
> 
> but...i am unable to write to a tape(never used tape backup before, so i 
> dont know exactly how to read the log files properly)..i am wanting 
> to backup the server that amanda is running on
> so do i need amanda-client rpm installed also...if so i have it installed...
> 
> this is the only thing i have in my disklist file
> 
> bs1.domain.name /etc comp-root-tar
> 
> i added the following to .amandahosts file:
> 
> bs1.domain.name amanda
> 
> i can telnet to ports 10082 and 10083  but NOT 10080

telnet uses tcp, port 10080 is set up for udp only


> 
> and when i run amcheck DailySet1 this is the output:
> 
> Amanda Tape Server Host Check
> -
> Holding disk /data: 66999148 KB disk space available, using 66998124 KB
> amcheck-server: slot 3: date 20030924 label DailySet14 (first labelstr 
> match)
> NOTE: skipping tape-writable test
> Tape DailySet14 label ok
> NOTE: info dir /usr/adm/amanda/normal/database: does not exist
> NOTE: it will be created on the next run
> NOTE: index dir /usr/adm/amanda/normal/index: does not exist
> Server check took 28.989 seconds
> 
> Amanda Backup Client Hosts Check
> 
> Client check: 1 host checked in 0.039 seconds, 0 problems found
> 
> (brought to you by Amanda 2.4.3)
> 
> when i run the following:
> 
> su amanda -c "amadmin DailySet1 find bs1"
> bash: /root/.bashrc: Permission denied

You really should fix whatever is wrong in the .bashrc file.
Unlikely to affect anything here however.

> the following is returned: by the way "/data" is the main holding disk
> 
> Scanning /data...
>  lost+found: skipping cruft directory, perhaps you should delete it.
> 
> No dump to list
> 
> So is there anything i overlooked or havent completed yet to write to a 
> tape?


What I'd like to know is if you have run an amanda backup yet,
i.e. amdump?  If not, there can't be any backups to find.


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

Re: Help with writing to tape

[C.Scheeder]

Hmm.

what about running

amdump DailySet1

to actually let amnda do her work, get the dump for your /etc dir
and put it to tape before you try to find a dump which has never
been done until now?
Christoph
chris weisiger wrote:
I am able to use the following commands for amanda properly:
amlabel
amtape
amcheck
but...i am unable to write to a tape(never used tape backup before, so i 
dont know exactly how to read the log files properly)..i am wanting 
to backup the server that amanda is running on
so do i need amanda-client rpm installed also...if so i have it 
installed...

this is the only thing i have in my disklist file

bs1.domain.name /etc comp-root-tar

i added the following to .amandahosts file:

bs1.domain.name amanda

i can telnet to ports 10082 and 10083  but NOT 10080

and when i run amcheck DailySet1 this is the output:

Amanda Tape Server Host Check
-
Holding disk /data: 66999148 KB disk space available, using 66998124 KB
amcheck-server: slot 3: date 20030924 label DailySet14 (first labelstr 
match)
NOTE: skipping tape-writable test
Tape DailySet14 label ok
NOTE: info dir /usr/adm/amanda/normal/database: does not exist
NOTE: it will be created on the next run
NOTE: index dir /usr/adm/amanda/normal/index: does not exist
Server check took 28.989 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.039 seconds, 0 problems found
(brought to you by Amanda 2.4.3)

when i run the following:

su amanda -c "amadmin DailySet1 find bs1"
bash: /root/.bashrc: Permission denied
the following is returned: by the way "/data" is the main holding disk

Scanning /data...
 lost+found: skipping cruft directory, perhaps you should delete it.
No dump to list

So is there anything i overlooked or havent completed yet to write to a 
tape?

btw also
these services i  have running for amanda
amanda
amandaidx
amidxtape
and i stopped iptables also

Thanks

Re: help with backing up

[Jon LaBadie]

On Wed, Sep 24, 2003 at 11:21:14AM -0500, chris weisiger wrote:
> Here is the only thing i have in my disklist file:
> 
> bs1 /home root-tar
> 
> of course i backed up the original
> 
> here is two example lines from the original disklist file
> #joespc  wd0e comp-user
> #joespc /msdos comp-user-tar
> 
> now i know /msdos is  a directory, what would wd0e be? a directory or a 
> disk that will be used to back up the host joespc?
> 
> here is where i am in trying to get my backup to work...
> 
> switching of tapes , moving prev/next, setting labels all working
> 
> i run the following command to do my backup
> 
> amdump DailySet1
> 
> i then tail the amdump log file..the only problem is i really dont know 
> exactly if the dump is
> working or not...i have used the amstatus commandbut again not 
> exactly know how to
> read it stillcan someone paste an log file that shows and working 
> dump log file...
> and i have even used the adadmin command to find directories on tapes 
> and nothing shows up
> 
> [EMAIL PROTECTED] DailySet1]# su amanda -c "amadmin DailySet1 find localhost 
> DailySet15 /etc"

As a first comment, are you, or who ever is specified in amanda.conf,
getting an emailed report after each amdump?  You should.  What about
amcheck with and without the mail option.

Next, rather than running

amadmin DailySet1 find localhost DailySet15 /etc

which is kinda specific (only finds dumps of a disklist entry for
the /etc directory, which you probably don't have but have /; and
only for localhost in the disklist which you probably don't have
but have "joespc" or "bs1"; and only on tape DailySet15 which is
not a valid request), --- like that run on parenthetical clause? ---
instead ask to find anything from a host.  Like:

amadmin DailySet1 find bs1

jl
-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Tapetype for LTO-2 (was Re: Help with Dell 132T)

[Paul Bijnens]

chris weisiger wrote:

I have another question, i think i need to turn compression of...
so my question is,
which device to i turn compression off on?
That's OS dependant.
For solaris, you need to specify the correct device /dev/rmt/0l,
assuming you have configured /kernel/drv/st.conf correctly for
the drive in question.
For linux, there is a file /etc/stinit.def with parameters
used while booting or loading the tape kernel module;
or the command "mt -t /dev/st0 compression 0".
(Google around a bit -- this has been discussed many times
before on this list.)
You can of course always find the dip switch
on the drive that disables the compression too.
But the good news for your drive is that a modern LTO drive
does not suffer from the expanding-already-compressed-files
syndrome that most tape drives have.  So, in fact, it does
not matter that much anymore to turn compression off for
an LTO drive.


Alexander Jolk wrote:

I wrote:
I have just got a PV-132T with an LTO-2 drive.
Running amtapetype on it gives me the following:

define tapetype lto2 {
   comment "just produced by tapetype prog (hardware compression off)"
   length 199690 mbytes
   filemark 10922 kbytes
   speed 30058 kps
}


--
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: Tapetype for LTO-2 (was Re: Help with Dell 132T)

[Alexander Jolk]

(I believe we are still talking Linux?  Other systems have other
traditions, it seems.)

> how do i check to see if compression is off or on..
To check:   mt -f /dev/nst0 datcompression
To disable: mt -f /dev/nst0 datcompression 0

> and will i need to put this in rc.local when server is needed to be
> rebooted?

Probably yes, unless you can find a jumper that disables compression
once and for all.  This discussion has been held several times before;
you'll find answers with excruciating details in the archives.  Gene H.
for instance, has posted on several occasions, a complete write-up on
the caveats of hardware compression, which you should read even if it
does not necessarily apply to our LTO-2 drive, just to know what can
happen.

Alex

-- 
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: Tapetype for LTO-2 (was Re: Help with Dell 132T)

[chris weisiger]

how do i check to see if compression is off or on..
and will i need to put this in rc.local when server is needed to be
rebooted?

Alexander Jolk wrote:

  
which device to i turn compression off on?

  
  
You turn the compression off on your tape drive, probably /dev/nst0. 
The changer lives on a different SCSI address, and shows up as /dev/sg0,
but has nothing to do with your drive's compression.

Alex

  

Tapetype for LTO-2 (was Re: Help with Dell 132T)

[Alexander Jolk]

I wrote:
> I have just got a PV-132T with an LTO-2 drive.

Running amtapetype on it gives me the following:

define tapetype lto2 {
comment "just produced by tapetype prog (hardware compression off)"
length 199690 mbytes
filemark 10922 kbytes
speed 30058 kps
}

I'll add it to the FAQ-O-Matic as soon as I get my password confirmed.

Alex

-- 
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: Help with Dell 132T

[Alexander Jolk]

> Has any successfully have amanda working with the Dell PV-132T?
> if not what files do i have to editi just have to edit the
> amanda.conf file?

I have just got a PV-132T with an LTO-2 drive.  I'm in the process of
setting it up and will report on my success or failure in the next few
days.  So far, Debian woody's `mtx' recognises the changer just fine,
just not the import/export slot; `amtapetype' is currently running.

Alex

-- 
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: Help with amrecover, cannot connect- connection refused

[Nicolas Ecarnot]

On Tue, Aug 26, 2003 à 04:55:33PM -0400, John Grover wrote:
> Amanda list:
> 
> I'm doing my first test of amrecover (amdump ran fine) and I get an
> error "amrecover: cannot connect to  : connection
> refused". I tried amrecover as root with all the command line options
> set except tape device.

I just had the same problem yesterday.
I solved it by :
- running amrecover as root
- adding this line
backupServer.mydomain.com root
to /home/operator/.amandahosts

HTH

-- 
Nicolas Ecarnot

Re: Help I can't do amlabel

[Marcelo Block Teixeira]

thanks Roger, you are right!!
It is working now.
Thank you!!
- Original Message -
From: "Roger Koot" <[EMAIL PROTECTED]>
To: "Marcelo Block Teixeira" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 11:14 AM
Subject: Re: Help I can't do amlabel


as you can see in your mail, amanda requires the non-rewinding
tapedevice. /dev/st0 is a REWINDING tape device
use /dev/nst0 instead, that's the non-rewinding tape device.
so, to check, use 'mt -f /dev/nst0 status'
also, be *sure* you have /dev/nst0 as tape device in your amanda config.
btw. if your tapedrive is an ATA device (IDE) then you should use
/dev/nht0 as non-rewinding tape device. (yes /dev/ht0 is the rewinding
ide tape device)

I hope this'll help you out.

roger

On Thu, 2003-07-31 at 16:00, Marcelo Block Teixeira wrote:
> I read about it here and I think my problem is the blocksize between
> reading and writing, however I don't know how I can fix it.
> Somebody can help me?
>
> my setup:
>
> $ amlabel DailySet1 DailySet100
>
> labeling tape in slot 1 (/dev/st0):
> rewinding, reading label, not an amanda tape
> rewinding, writing label DailySet100, checking label
> amlabel: no label found, are you sure /dev/st0 is non-rewinding?
>
> $ mt -f /dev/st0 status
>
> SCSI 2 tape drive:
> File number=0, block number=0, partition=0.
> Tape block size 0 bytes. Density code 0x13 (DDS (61000 bpi)).
> Soft error count since last status=0
> General status bits on (4101):
> BOT ONLINE IM_REP_EN
>
> $ /etc/amanda/DailySet1/amanda.conf
>
> org "DailySet1"
> mailto "cpd"
> dumpuser "amanda"
> inparallel 4
> netusage  600 Kbps
> dumpcycle 4 weeks
> runspercycle 4 weeks
> tapecycle 25 tapes
>
> bumpsize 20 Mb
> bumpdays 1
> bumpmult 4
> etimeout 300
>
> runtapes 1
> tpchanger "chg-multi"
> changerfile "/etc/amanda/DailySet1/changer.conf"
>
> tapetype SONY-DAT
> labelstr "^DailySet1[0-9][0-9]*$"
>
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/var/tmp"
> use 290 Mb
> chunksize 2 Gb
> }
>
> infofile "/var/lib/amanda/DailySet1/curinfo" # database filename
> logdir   "/var/lib/amanda/DailySet1"  # log directory
> indexdir "/var/lib/amanda/DailySet1/index" # index directory
>
> tapelist "/etc/amanda/DailySet1/tapelist"
>
> define tapetype SONY-DAT {
> comment "SONY-DAT 5000"
> length 3157 mbytes
> filemark 2165 kbytes
> speed 204 kps
> }
>
> define dumptype global {
> comment "Global definitions"
> }
>
> define dumptype comp-user-tar {
> user-tar
> compress client fast
> }
>
> $ /etc/amanda/DailySet1/changer.conf
>
> multieject 0
> gravity 0
> needeject 0
> ejectdelay 0
> statefile /etc/amanda/DailySet1/changer-status
> firstslot 1
> lastslot 1
> slot 1 /dev/st0
>
>
>
>
>
>
>
>
>
>
>
>
> Sem mais,
> Atenciosamente
> Marcelo Block - CPD
> CADService Produtos Eletrônicos
> Do more, Grow more, Be more
> ICQ: 319176888
> Fone:55-19-3246-1333
--
Roger Koot <[EMAIL PROTECTED]>
Open Source Adviesbureau Koot

Re: Help I can't do amlabel

[Roger Koot]

as you can see in your mail, amanda requires the non-rewinding
tapedevice. /dev/st0 is a REWINDING tape device
use /dev/nst0 instead, that's the non-rewinding tape device.
so, to check, use 'mt -f /dev/nst0 status'
also, be *sure* you have /dev/nst0 as tape device in your amanda config.
btw. if your tapedrive is an ATA device (IDE) then you should use
/dev/nht0 as non-rewinding tape device. (yes /dev/ht0 is the rewinding
ide tape device)

I hope this'll help you out.

roger

On Thu, 2003-07-31 at 16:00, Marcelo Block Teixeira wrote:
> I read about it here and I think my problem is the blocksize between
> reading and writing, however I don't know how I can fix it.
> Somebody can help me?
>  
> my setup:
>  
> $ amlabel DailySet1 DailySet100
>  
> labeling tape in slot 1 (/dev/st0): 
> rewinding, reading label, not an amanda tape
> rewinding, writing label DailySet100, checking label
> amlabel: no label found, are you sure /dev/st0 is non-rewinding?
>  
> $ mt -f /dev/st0 status
>  
> SCSI 2 tape drive:
> File number=0, block number=0, partition=0.
> Tape block size 0 bytes. Density code 0x13 (DDS (61000 bpi)).
> Soft error count since last status=0
> General status bits on (4101): 
> BOT ONLINE IM_REP_EN
>  
> $ /etc/amanda/DailySet1/amanda.conf
>  
> org "DailySet1"  
> mailto "cpd"
> dumpuser "amanda"
> inparallel 4 
> netusage  600 Kbps 
> dumpcycle 4 weeks 
> runspercycle 4 weeks
> tapecycle 25 tapes
>  
> bumpsize 20 Mb  
> bumpdays 1  
> bumpmult 4  
> etimeout 300  
>  
> runtapes 1  
> tpchanger "chg-multi" 
> changerfile "/etc/amanda/DailySet1/changer.conf"
>  
> tapetype SONY-DAT
> labelstr "^DailySet1[0-9][0-9]*$" 
>  
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/var/tmp" 
> use 290 Mb  
> chunksize 2 Gb 
> }
>  
> infofile "/var/lib/amanda/DailySet1/curinfo" # database filename
> logdir   "/var/lib/amanda/DailySet1"  # log directory
> indexdir "/var/lib/amanda/DailySet1/index" # index directory
>  
> tapelist "/etc/amanda/DailySet1/tapelist"
>  
> define tapetype SONY-DAT {
> comment "SONY-DAT 5000"
> length 3157 mbytes
> filemark 2165 kbytes
> speed 204 kps
> }
>  
> define dumptype global {
> comment "Global definitions"
> }
>  
> define dumptype comp-user-tar {
> user-tar
> compress client fast
> }
>  
> $ /etc/amanda/DailySet1/changer.conf
>  
> multieject 0
> gravity 0
> needeject 0
> ejectdelay 0
> statefile /etc/amanda/DailySet1/changer-status
> firstslot 1
> lastslot 1
> slot 1 /dev/st0
> 
> 
> 
>  
>  
>  
>  
>  
> 
>   
>   
>  
> Sem mais,
> Atenciosamente
> Marcelo Block - CPD
> CADService Produtos Eletrônicos
> Do more, Grow more, Be more
> ICQ: 319176888
> Fone:55-19-3246-1333
-- 
Roger Koot <[EMAIL PROTECTED]>
Open Source Adviesbureau Koot

RE: help with disklist/tapelist and amlabel

[Josh Welch]

Joseph Andorful said:
> 
> --- Josh Welch <[EMAIL PROTECTED]> wrote:
> > Joseph Andorful said:
> > > 
> > > I'm configuring AMANDA to backup to a hard disk
> > rather
> > > than a tape drive.  I followed the instructions
> > from
> > > "Amanda Faq-O-Matic: How to configure for tapeless
> > > operation."  However, there seems to be a problem
> > with
> > > the way I configured the disklist file.  When I
> > try to
> > > run amlabel, it says:  amlabel: could not load
> > > tapelist "/etc/amanda/DailySet1/tapelist"
> > > 
> > > Please Help.
> > > 
> > > Joseph Andorful
> > > 
> > If I recall correctly, I was able to get past this
> > with
> > 
> > #touch /etc/amanda/DailySet1/tapelist
> > 
> > Josh
> 
> 
> I performed that command as you said, but it still
> didn't work.  What is the configuration for the
> disklist/tapelist file supposed to look like?
> 
> Joseph
> 
> 
Well, I am doing something similar to you, only with five 
"tapes" and my tapelist currently looks like this:
20030716 Tape01 reuse
20030715 Tape05 reuse
20030714 Tape04 reuse
20030714 Tape03 reuse
20030714 Tape02 reuse

You shouldn't have to touch this beyond the initial creation
of the file. I thought I remembered reading someone saying
that they had problems if this was not a 0 byte count file,
for instance if you did a vi on the file and wrote it out
rather than just doing a touch. That could be wrong however.

The tapelist file should be written by amlabel, which
you should be running as the amanda user, and then updated
by amanda as it runs, if I am not mistaken. Make sure that
your amanda user has the rights to this directory and file.

Josh

Re: help with disklist/tapelist and amlabel

[Paul Bijnens]

Joseph Andorful wrote:

run amlabel, it says:  amlabel: could not load
tapelist "/etc/amanda/DailySet1/tapelist"


>>Josh Welch wrote:
#touch /etc/amanda/DailySet1/tapelist

Josh


I performed that command as you said, but it still
didn't work.  What is the configuration for the
disklist/tapelist file supposed to look like?
For the beginning it should be an empty file (and if not using
2.4.4p1 but 2.4.4 or earlier, then it may not even have
a blank line in it).
Is it owned by amanda?  ls -l should show size 0.

--
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: help with disklist/tapelist and amlabel

[Joseph Andorful]

--- Josh Welch <[EMAIL PROTECTED]> wrote:
> Joseph Andorful said:
> > 
> > I'm configuring AMANDA to backup to a hard disk
> rather
> > than a tape drive.  I followed the instructions
> from
> > "Amanda Faq-O-Matic: How to configure for tapeless
> > operation."  However, there seems to be a problem
> with
> > the way I configured the disklist file.  When I
> try to
> > run amlabel, it says:  amlabel: could not load
> > tapelist "/etc/amanda/DailySet1/tapelist"
> > 
> > Please Help.
> > 
> > Joseph Andorful
> > 
> If I recall correctly, I was able to get past this
> with
> 
> #touch /etc/amanda/DailySet1/tapelist
> 
> Josh


I performed that command as you said, but it still
didn't work.  What is the configuration for the
disklist/tapelist file supposed to look like?

Joseph

__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: help with disklist/tapelist and amlabel

[Josh Welch]

Joseph Andorful said:
> 
> I'm configuring AMANDA to backup to a hard disk rather
> than a tape drive.  I followed the instructions from
> "Amanda Faq-O-Matic: How to configure for tapeless
> operation."  However, there seems to be a problem with
> the way I configured the disklist file.  When I try to
> run amlabel, it says:  amlabel: could not load
> tapelist "/etc/amanda/DailySet1/tapelist"
> 
> Please Help.
> 
> Joseph Andorful
> 
If I recall correctly, I was able to get past this with

#touch /etc/amanda/DailySet1/tapelist

Josh

Re: help with disklist/tapelist and amlabel

[Gene Heskett]

On Wednesday 16 July 2003 10:13, Joseph Andorful wrote:
>I'm configuring AMANDA to backup to a hard disk rather
>than a tape drive.  I followed the instructions from
>"Amanda Faq-O-Matic: How to configure for tapeless
>operation."  However, there seems to be a problem with
>the way I configured the disklist file.  When I try to
>run amlabel, it says:  amlabel: could not load
>tapelist "/etc/amanda/DailySet1/tapelist"

ISTR you'll have to 'touch' that file to create it.

>Please Help.
>
>Joseph Andorful
>
>__
>Do you Yahoo!?
>SBC Yahoo! DSL - Now only $29.95 per month!
>http://sbc.yahoo.com

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: help with backup problems please

[Lucio.yahoo]

Thanks to everybody for your patience, now it works. The problem was
 precisely the .amandahosts file.

Special thanks to Paul Bijnens for being the first to point out the real
problem.

Re: help with backup problems please

[Gene Heskett]

On Thursday 26 June 2003 06:51, Onime Clement wrote:
>Next Step
>Add the following line in the file ~amanda/.amandahosts
>(/var/lib/amanda/.amandahosts)
>
>fmserver amanda
>
>The file should already have entries for
>localhost amanda
>localhost.localdomain amanda
>
>If not please add them.
>
>> >Pay special attention to typos in inetd.conf;
>>
>> I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now
>
>Let's hope it remains on! I suspect that using chkconfig keeps a
> system status on each server..

AFAIK chkconfig doesn't keep a database, but reads the status of each 
'server' from its file in order to generate an up2date display for 
the query function.

For amanda stuffs I've always just edited the starter file and 
restarted xinetd.

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: help with backup problems please

[Gene Heskett]

On Thursday 26 June 2003 06:39, Paul Bijnens wrote:
>Gene Heskett wrote:
>> That file should exist in /home/"amanda-user"/.amandahosts, and
>> look something like this:
>> ---
>> FQDN amanda
>> FQDN root
>> ---
>> Where my amanda-user is amanda.  And I'm not sure if the second
>> line is needed at all.  FQDN is the servers full name of course. 
>> This file must also exist on the clients, in the same location,
>> which gives the server access rights there too.
>
>On the client the first line is needed so that the user "amanda"
>can start a backup on this client; FQDN = name of server in this
> case.
>
>On the server the second line is needed so that "root" on the client
>can start a restore; FQDN = name of the client in this case.
>
>The meaning is: when some "username" from "host" connects, let him
> in.
>
>So, usually you have a oneliner on each client, and a large list on
> the server. (Also remember the server is also a client in most
> cases.) You can leave most of entries on the server commented
> out(*), so that someone from workstation A with root access cannot
> restore files from or SecretServer B, if security is a concern.
>
>(*) commented out = there is no real comment sign but if you add a
>#-sign in front of the name, the hostname effectively never matches,
>(unless you really have a host named "#" or '#host' :-) ).

Thanks for clarifying that Paul.

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: help with backup problems please

[Onime Clement]

Next Step
Add the following line in the file ~amanda/.amandahosts 
(/var/lib/amanda/.amandahosts)

fmserver amanda

The file should already have entries for 
localhost amanda
localhost.localdomain amanda

If not please add them.


> >Pay special attention to typos in inetd.conf; 
> 
> I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now 

Let's hope it remains on! I suspect that using chkconfig keeps a system 
status on each server..

> the problem is:
> 
> 
> planner: ERROR localhost:  [access as amanda not allowed from [EMAIL PROTECTED] 
> amandahostsauth failed
> 
> 
> Note that amanda had been running as root for a while yesterday, so I suspect 
> it chowned some file somewhere, and now the amanda user is not able to cope 
> with them anymore, but I'm not sure at all of this.
> 
> 
> What could be the next step?
> 

Re: help with backup problems please

[Paul Bijnens]

Gene Heskett wrote:

That file should exist in /home/"amanda-user"/.amandahosts, and look 
something like this:
---
FQDN	amanda
FQDN	root
---
Where my amanda-user is amanda.  And I'm not sure if the second line 
is needed at all.  FQDN is the servers full name of course.  This 
file must also exist on the clients, in the same location, which 
gives the server access rights there too.
On the client the first line is needed so that the user "amanda"
can start a backup on this client; FQDN = name of server in this case.
On the server the second line is needed so that "root" on the client
can start a restore; FQDN = name of the client in this case.
The meaning is: when some "username" from "host" connects, let him in.

So, usually you have a oneliner on each client, and a large list on the 
server. (Also remember the server is also a client in most cases.)
You can leave most of entries on the server commented out(*),
so that someone from workstation A with root access cannot restore
files from or SecretServer B, if security is a concern.

(*) commented out = there is no real comment sign but if you add a 
#-sign in front of the name, the hostname effectively never matches,
(unless you really have a host named "#" or '#host' :-) ).

--
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: help with backup problems please

[Gene Heskett]

On Thursday 26 June 2003 06:27, Lucio.yahoo, (by way of Lucio.yahoo 
wrote:
>> For RedHat 9
>> Try the following command as root
>>
>> chkconfig amanda on
>
>I've edited /etc/xinetd.d/amanda by hand instead, then I restarted
> xinetd. Now the problem is:
>
>planner: ERROR localhost:  [access as amanda not allowed from
> [EMAIL PROTECTED] amandahostsauth failed

That file should exist in /home/"amanda-user"/.amandahosts, and look 
something like this:
---
FQDNamanda
FQDNroot
---
Where my amanda-user is amanda.  And I'm not sure if the second line 
is needed at all.  FQDN is the servers full name of course.  This 
file must also exist on the clients, in the same location, which 
gives the server access rights there too.

>Note that amanda had been running as root for a while yesterday, so
> I suspect it chowned some file somewhere, and now the amanda user
> is not able to cope with them anymore, but I'm not sure at all of
> this.
>
>What could be the next step?

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: help with backup problems please

[Christoph Scheeder]

Hi,
two things:
1.) never use localhost in a disklist entry, it will come back and bite 
you later
always use the full name of the host.
2.) in the homedirectory of the amanda-user create a file ".amandahosts" 
owned by the amanda user and
with permisions 0600, containing at least the line:

fmserveramanda

then test  your setup with  "

amcheck 

christoph

Lucio.yahoo schrieb:

  Pay special attention to typos in inetd.conf; 
   

I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now 
the problem is:

planner: ERROR localhost:  [access as amanda not allowed from [EMAIL PROTECTED] 
amandahostsauth failed

Note that amanda had been running as root for a while yesterday, so I suspect 
it chowned some file somewhere, and now the amanda user is not able to cope 
with them anymore, but I'm not sure at all of this.

What could be the next step?

 

Re: help with backup problems please

[Gene Heskett]

On Thursday 26 June 2003 04:20, Lucio.yahoo wrote:
>> You should get an e-mail with error messages and statistics.
>
>Here is the mail I receive (mailto "root"), but, to be honest, it
> doesn't help me very much...
>
>From [EMAIL PROTECTED]  Thu Jun 26 08:11:16 2003
>Date: Thu, 26 Jun 2003 08:11:15 +0200
From: root <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: MyOrg AMANDA MAIL REPORT FOR June 26, 2003
>
>These dumps were to tape DailySet1n4.
>The next tape Amanda expects to use is: a new tape.
>
>FAILURE AND STRANGE DUMP SUMMARY:
>  planner: ERROR Request to localhost timed out.
>  localhost  /dev/md0 RESULTS MISSING

Aha!  Since the error came from planner, it looks as if the etimeout 
value set in your amanda.conf might be too small.  As /dev/md0 is a 
software raid, its probably pretty big, and the estimate phase is 
going to take extra time.  I know of one such 360 gig setup, and its 
not particularly fast, only makeing about 30Mb a second in an hdparm 
test.  I'd expect it would take at least 45 minutes to get an 
estimate back from that one.

Heres a grep for mine, where the raid is not involved:

etimeout 600# number of seconds per filesystem for estimates.
dtimeout 1800   # number of idle seconds before a dump is aborted.
ctimeout 5  # maximum number of seconds that amcheck waits

which translates to 10 minutes, 30 minutes, and 5 seconds.  One of my 
clients is a dog by todays standards.

[...]

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: help with backup problems please

[Lucio.yahoo]

>Pay special attention to typos in inetd.conf; 

I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now 
the problem is:


planner: ERROR localhost:  [access as amanda not allowed from [EMAIL PROTECTED] 
amandahostsauth failed


Note that amanda had been running as root for a while yesterday, so I suspect 
it chowned some file somewhere, and now the amanda user is not able to cope 
with them anymore, but I'm not sure at all of this.


What could be the next step?

Re: help with backup problems please

[Lucio.yahoo]

> For RedHat 9
> Try the following command as root
>
> chkconfig amanda on

I've edited /etc/xinetd.d/amanda by hand instead, then I restarted xinetd.
 Now the problem is:

planner: ERROR localhost:  [access as amanda not allowed from
 [EMAIL PROTECTED] amandahostsauth failed

Note that amanda had been running as root for a while yesterday, so I suspect
it chowned some file somewhere, and now the amanda user is not able to cope
with them anymore, but I'm not sure at all of this.

What could be the next step?

Re: help with backup problems please

[Dietmar Goldbeck]

On Thu, Jun 26, 2003 at 08:20:29AM +, Lucio.yahoo wrote:
> > You should get an e-mail with error messages and statistics.
> 
> Here is the mail I receive (mailto "root"), but, to be honest, it doesn't help 
> me very much...
> 

Yes, the mail is not very helpful for a newbie.
OTOH i cannot offer any help without error messages.


> FAILURE AND STRANGE DUMP SUMMARY:
>   planner: ERROR Request to localhost timed out.

The server couldn't reach the client. (Doesn't matter if client and
server are the same machine. Amanda is always communicating over an
UDP and TCP)

Please start with amcheck debugging and follow these tips from the FAQ.
My personal favourite is 
clear debug files   rm -r /tmp/amanda
stop inetd  fuser -k /usr/sbin/inetd 
and starting it with -d option. inetd -d
Then run amcheck and watch if inetd gives output.
If you cannot find the problem, please post the file under /tmp/amanda.

See also http://amanda.sourceforge.net/fom-serve/cache/13.html
FAQ: 

Q: Why does `amcheck' report `selfcheck request timed out'?

A: This can occur under several different situations.  First, make
sure this problem is repeatable; if Amanda programs are
NFS-auto-mounted, some clients may fail to mount the Amanda binaries
in time.

   If the error is repeatable, log into the client, and check whether
the directory /tmp/amanda exists, and a file named amandad.debug
exists in there: amandad will create this file whenever it starts.  If
this file does not exist, amandad is not starting properly, or it
lacks permission to create /tmp/amanda/amandad.debug.

   In the latter case, wipe out /tmp/amanda, and amandad should create
it next time it runs.  In the former case, check your inetd
configuration.  Make sure you have added the Amanda services to
/etc/services (or the NIS services map), that /etc/inetd.conf was
properly configured, and that you have signalled inetd to reread this
file (some systems may need rebooting).  Check section 2.2 from the
INSTALL file for details.  Check the inetd man-page for possible
differences between the standard inetd.conf format and the one in your
system.

   Pay special attention to typos in inetd.conf; error messages will
probably appear in /var/adm/messages or /var/log/messages if you have
typed the amandad program name incorrectly.  Make sure the same user
that you have specified at configure-time (--with-user=) is
listed in inetd.conf.  Check whether this user has permission to run
amandad, as well as any shared libraries amandad depends upon, by
running the specified amandad command by hand, as the Amanda user.  It
should just time-out after 30 seconds waiting for a UDP packet.  If
you type anything, it will abort immediately, because it can't read a
UDP packet from the keyboard.

   As soon as you have properly configured inetd.conf so as to run
amandad, you should no longer get the `selfcheck request timed out'
message.  A nice tool to help make sure inetd is really listening on
the amandad port is lsof, available at
ftp://vic.cc.purdue.edu/pub/tools/unix/lsof.

-- 
 Alles Gute / best wishes  
 Dietmar Goldbeck E-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?  Gandhi: I think it would be a good idea.

Re: help with backup problems please

[Onime Clement]

For RedHat 9
Try the following command as root

chkconfig amanda on

The client aspect of amanda (run via xinetd) is disabled by default! 
The above command turns it on. If that fails then check to see if it 
works after you issue the command 
service iptables stop
In which case it is a firewall issue.

Thanks
Clement Onime

On Thu, 26 Jun 2003, Lucio.yahoo wrote:

> > What does 'amcheck DailySet1' say?
> 
> Amanda Tape Server Host Check
> -
> Holding disk /var/tmp: 30819288 KB disk space available, using 25576408 KB
> NOTE: skipping tape-writable test
> Tape DailySet1n4 label ok
> NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist
> NOTE: it will be created on the next run
> NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist
> Server check took 8.201 seconds
> 
> Amanda Backup Client Hosts Check
> 
> WARNING: localhost: selfcheck request timed out.  Host down?
> Client check: 1 host checked in 29.995 seconds, 1 problem found
> 
> (brought to you by Amanda 2.4.3)
> 
> Wow! It has found a problem on the client host (wich is phisically the server, 
> btw). But, why this problem? What am I missing?
> 
> >
> > How about 'amstatus DailySet1 --file logdir/amdump.1'?  (where ever
> > your "logdir" is...)
> >
> 
> # amstatus DailySet1 --file /var/lib/amanda/DailySet1
> Using /var/lib/amanda/DailySet1
> 
> 
> SUMMARY  part real estimated
>   size  size
> partition   :   0
> estimated   :   0  0k
> flush   :   00k
> failed  :   0  0k   (  0.00%)
> wait for dumping:   0  0k   (  0.00%)
> dumping to tape :   0  0k   (  0.00%)
> dumping :   00k0k (  0.00%) (  0.00%)
> dumped  :   00k0k (  0.00%) (  0.00%)
> wait for writing:   00k0k (  0.00%) (  0.00%)
> wait to flush   :   00k0k (100.00%) (  0.00%)
> writing to tape :   00k0k (  0.00%) (  0.00%)
> failed to tape  :   00k0k (  0.00%) (  0.00%)
> taped   :   00k0k (  0.00%) (  0.00%)
> all dumpers active
> taper idle
> 
> Can you see anything strange here?
> 
> > How about 'amreport DailySet1 -l logdir/log.20030625.0 -f /tmp/foo'
> > (again, logdir and whatever the appropriate logfile name is).
> 
> Please refer to my reply to Dietmar Goldbeck for this.
> 
> >
> > How about /tmp/amanda/* on the client and server?
> 
> *** amtrmidx.debug ***
> could not open index directory 
> "/var/lib/amanda/DailySet1/index/localhost/_dev_md0/"amtrmidx: pid 4997
> 
> # The first missing subdir is localhost
> 
> There are lots of other debug files down there, I've checked only a few but 
> the one above seems the only interesting one (along with the others from the 
> same process).
> 
> 

Re: help with backup problems please

[Lucio.yahoo]

> What does 'amcheck DailySet1' say?

Amanda Tape Server Host Check
-
Holding disk /var/tmp: 30819288 KB disk space available, using 25576408 KB
NOTE: skipping tape-writable test
Tape DailySet1n4 label ok
NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist
NOTE: it will be created on the next run
NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist
Server check took 8.201 seconds

Amanda Backup Client Hosts Check

WARNING: localhost: selfcheck request timed out.  Host down?
Client check: 1 host checked in 29.995 seconds, 1 problem found

(brought to you by Amanda 2.4.3)

Wow! It has found a problem on the client host (wich is phisically the server, 
btw). But, why this problem? What am I missing?

>
> How about 'amstatus DailySet1 --file logdir/amdump.1'?  (where ever
> your "logdir" is...)
>

# amstatus DailySet1 --file /var/lib/amanda/DailySet1
Using /var/lib/amanda/DailySet1


SUMMARY  part real estimated
  size  size
partition   :   0
estimated   :   0  0k
flush   :   00k
failed  :   0  0k   (  0.00%)
wait for dumping:   0  0k   (  0.00%)
dumping to tape :   0  0k   (  0.00%)
dumping :   00k0k (  0.00%) (  0.00%)
dumped  :   00k0k (  0.00%) (  0.00%)
wait for writing:   00k0k (  0.00%) (  0.00%)
wait to flush   :   00k0k (100.00%) (  0.00%)
writing to tape :   00k0k (  0.00%) (  0.00%)
failed to tape  :   00k0k (  0.00%) (  0.00%)
taped   :   00k0k (  0.00%) (  0.00%)
all dumpers active
taper idle

Can you see anything strange here?

> How about 'amreport DailySet1 -l logdir/log.20030625.0 -f /tmp/foo'
> (again, logdir and whatever the appropriate logfile name is).

Please refer to my reply to Dietmar Goldbeck for this.

>
> How about /tmp/amanda/* on the client and server?

*** amtrmidx.debug ***
could not open index directory 
"/var/lib/amanda/DailySet1/index/localhost/_dev_md0/"amtrmidx: pid 4997

# The first missing subdir is localhost

There are lots of other debug files down there, I've checked only a few but 
the one above seems the only interesting one (along with the others from the 
same process).

Re: help with backup problems please

[Lucio.yahoo]

> You should get an e-mail with error messages and statistics.

Here is the mail I receive (mailto "root"), but, to be honest, it doesn't help 
me very much...

>From [EMAIL PROTECTED]  Thu Jun 26 08:11:16 2003
Date: Thu, 26 Jun 2003 08:11:15 +0200
From: root <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: MyOrg AMANDA MAIL REPORT FOR June 26, 2003

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

FAILURE AND STRANGE DUMP SUMMARY:
  planner: ERROR Request to localhost timed out.
  localhost  /dev/md0 RESULTS MISSING


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

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

^L
NOTES:
  planner: Adding new disk localhost:/dev/md0.
  driver: WARNING: got empty schedule from planner
  taper: tape DailySet1n4 kb 0 fm 0 [OK]

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

(brought to you by Amanda version 2.4.3)

Re: help with backup problems please

[Dietmar Goldbeck]

On Wed, Jun 25, 2003 at 06:46:56PM +, Lucio.yahoo wrote:

> The problems:
> # amdump DailySet1
> moves the tape for a few seconds, does not give any output on the screen and 
> it runs way too little time to believe it has written anything on the tape, 


What is your mailto entry in amanda.conf?
You should get an e-mail with error messages and statistics.

If you don't get this e-mail ( but mailto seems to be configured)
try sending a mail from the backup user to you. 

amadmin test version | grep MAILER

gives you the program amanda tries to execute. /usr/bin/Mail on my
server. YMMV

To check mail, amcheck -m is fine.

-- 
 Alles Gute / best wishes  
 Dietmar Goldbeck E-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?  Gandhi: I think it would be a good idea.

Re: Help compiling on OS X/Darwin

[Martin Hepworth]

Ken Simpson wrote:
Ken Simpson wrote:

Hi, I am a newbie to UN*X, and have downloaded the 2.4.4 sources and 
read the notes on compiling on OS X and have searched the lists.

However I can't get it to compile on OS X Jag. There are warnings in 
the configure and when I compile I get recursive errors in Amanda.h. 
Can anyone point me to a FAQ or a help page please? Or offer any 
other advice?

Thanks
Ken

I compiled it under 10.1 with little problem (there was a problem but 
I can;t remember what it was..).

What errors where you getting on the configure?

Thank for helping Martin,

these are the errors, and I have added the entire configure output as an 
attachment

configure: WARNING: you should use --build, --host, --target
configure: WARNING: *** You do not have gnuplot.  Amplot will not be 
installed.
configure: WARNING: netinet/ip.h: present but cannot be compiled
configure: WARNING: netinet/ip.h: check for missing prerequisite headers?
configure: WARNING: netinet/ip.h: proceeding with the preprocessor's result
configure: WARNING: *** No readline library, no history and command line 
editing in amrecover!



ok looking at the log file, you've told it that its a NetBSD based 
system. You'll have to mess with the default system types so that it 
matches powerpc-apple-rhapsody5.5 and use that for the type. Also I find 
I don;t need to put in the --with-config=backupset on clients..

there should be soemthing in on the the messages on the list archive on 
this as I kinda remember messing with some file to get this right.

--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
+44 (0)1865 842300


**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**