SSH problems
I am trying to get ssh authenticaion working on the amanda server to
itself. Amcheck -lc gives me a clean bill of health but the backups
still fail. The older 2.4.5 clients using BSD security still work fine
but the SSH eludes me.
On the backup called 'daily1 all directories return: lev 0 FAILED
[hmm, disk was stranded on waitq]
Is it because there are too many directories? (132) Is there a limit to
how many amanda can handle?
On the backup name flood using BSD the errors are even more weird:
amazon /NFS/tigris_backup/FLOOD/channel6 lev 0 FAILED [dumps too
big, 5 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/control lev 0 FAILED [dumps too
big, 167010 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/channel4 lev 0 FAILED [dumps too
big, 1844050 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/channel5 lev 0 FAILED [dumps too
big, 4590435 KB, but cannot incremental dump new disk]
amazon /NFS/euphrates_backup/GIS/logarch lev 0 FAILED [dumps too
big, 7943595 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/logarch lev 0 FAILED [dumps too
big, 8175800 KB, but cannot incremental dump new disk]
??? 5 KB is too big?!?! I double checked and my disktype is still set as:
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
That error makes no sense to me at all.
$ amadmin daily version
build: VERSION=Amanda-2.5.1p2
BUILT_DATE=Wed Jan 31 16:44:06 PST 2007
BUILT_MACH=Linux amazon.totalflood.com 2.6.11-1.35_FC3smp #1
SMP Mon Jun 13 01:17:35 EDT 2005 i686 i686 i386 GNU/Linux
CC=gcc
CONFIGURE_COMMAND='./configure' '--with-user=amanda'
'--with-group=adm' '--with-ssh-security' '--with-gnutar=/usr/local/bin/tar'
paths: bindir=/usr/local/bin sbindir=/usr/local/sbin
libexecdir=/usr/local/libexec mandir=/usr/local/man
AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda
CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/
RDEV_PREFIX=/dev/ DUMP=/sbin/dump
RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
SAMBA_CLIENT=/usr/bin/smbclient
GNUTAR=/usr/local/bin/tar COMPRESS_PATH=/bin/gzip
UNCOMPRESS_PATH=/bin/gzip LPRCMD=/usr/bin/lpr
MAILER=/usr/bin/Mail
listed_incr_dir=/usr/local/var/amanda/gnutar-lists
defs: DEFAULT_SERVER=amazon.totalflood.com
DEFAULT_CONFIG=DailySet1
DEFAULT_TAPE_SERVER=amazon.totalflood.com HAVE_MMAP
HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS
CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP
COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
For the time bing, I've dropped back to 2.4.5p2 which cannot handle the
number of directories in daily1 but will still backup most of the
systems. I guess some backup is better than no backup :-)
--
Stephen Carville -- polluting the ranks of skeptics since 1995.
---
Mystical man values human life. Rational man values the ability to
value human life.
-- Me
Re: SSH problems
Hi,
could it be the estimate is taking longer than the etimeout value? Try to
increase
etimeout in amanda.conf.
Hope this helps!
It's already at 1800 seconds.
None of the tests I ran today took longer than about five minutes to come
back with some kind of error.
Stephen Carville wrote:
I am trying to get ssh authenticaion working on the amanda server to
itself. Amcheck -lc gives me a clean bill of health but the backups
still fail. The older 2.4.5 clients using BSD security still work fine
but the SSH eludes me.
On the backup called 'daily1 all directories return: lev 0 FAILED
[hmm, disk was stranded on waitq]
Is it because there are too many directories? (132) Is there a limit to
how many amanda can handle?
On the backup name flood using BSD the errors are even more weird:
amazon /NFS/tigris_backup/FLOOD/channel6 lev 0 FAILED [dumps too
big, 5 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/control lev 0 FAILED [dumps too
big, 167010 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/channel4 lev 0 FAILED [dumps too
big, 1844050 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/channel5 lev 0 FAILED [dumps too
big, 4590435 KB, but cannot incremental dump new disk]
amazon /NFS/euphrates_backup/GIS/logarch lev 0 FAILED [dumps too
big, 7943595 KB, but cannot incremental dump new disk]
amazon /NFS/tigris_backup/FLOOD/logarch lev 0 FAILED [dumps too
big, 8175800 KB, but cannot incremental dump new disk]
??? 5 KB is too big?!?! I double checked and my disktype is still set
as:
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
That error makes no sense to me at all.
$ amadmin daily version
build: VERSION=Amanda-2.5.1p2
BUILT_DATE=Wed Jan 31 16:44:06 PST 2007
BUILT_MACH=Linux amazon.totalflood.com 2.6.11-1.35_FC3smp #1 SMP
Mon Jun 13 01:17:35 EDT 2005 i686 i686 i386 GNU/Linux
CC=gcc
CONFIGURE_COMMAND='./configure' '--with-user=amanda'
'--with-group=adm' '--with-ssh-security'
'--with-gnutar=/usr/local/bin/tar'
paths: bindir=/usr/local/bin sbindir=/usr/local/sbin
libexecdir=/usr/local/libexec mandir=/usr/local/man
AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda
CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/
RDEV_PREFIX=/dev/ DUMP=/sbin/dump
RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
SAMBA_CLIENT=/usr/bin/smbclient
GNUTAR=/usr/local/bin/tar COMPRESS_PATH=/bin/gzip
UNCOMPRESS_PATH=/bin/gzip LPRCMD=/usr/bin/lpr
MAILER=/usr/bin/Mail
listed_incr_dir=/usr/local/var/amanda/gnutar-lists
defs: DEFAULT_SERVER=amazon.totalflood.com
DEFAULT_CONFIG=DailySet1
DEFAULT_TAPE_SERVER=amazon.totalflood.com HAVE_MMAP
HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS
CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP
COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
For the time bing, I've dropped back to 2.4.5p2 which cannot handle the
number of directories in daily1 but will still backup most of the
systems. I guess some backup is better than no backup :-)
--
Thank you!
Kevin Till
Amanda documentation: http://wiki.zmanda.com
Amanda forums:http://forums.zmanda.com
Re: SSH problems
On Thursday 01 February 2007 11:02, Stephen Carville wrote: I am trying to get ssh authenticaion working on the amanda server to itself. Amcheck -lc gives me a clean bill of health but the backups still fail. The older 2.4.5 clients using BSD security still work fine but the SSH eludes me. I believe the FAQ or wiki has instructions on how to change the security model over, Stephan. I'd offer to help, but its been quite some time back up the log that I did it, and without consulting the FAQ or wiki, I know I'd leave something out. I've been following the wiki instructions -- which is one reason I'm so damn frusrtated. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2007 by Maurice Eugene Heskett, all rights reserved.
Re: Directory too large for single tape.
Ian Turner wrote:
On Monday 11 September 2006 01:48, Stephen Carville wrote:
I've been using Amanda for about five years now. The only problems I've
ever had are because a single dumps has to fit on a single tape.
If you upgrade to Amanda 2.5.x, then you can instruct Amanda to split dumps
across tapes; so you can make your partitions as large as you like, and just
use as many tapes as are required.
AFAICT, this doesn't really split the tar but tries to create separate
tars of subdirectories. Unfortunately RMAN puts it all in one directory
(There may be a way to split it -- I'm checking into that too).
Is it possible to get amanda to follow symlinks? Every file name ends
in a digit is it is trivial to do something like:
rm /empty/GIS1/*
find /NFS/euphrates_backup/GIS -name '*[1,3,5,7,9]' -exec ln -sf {}
/empty/GIS1/ \;
rm /empty/GIS2/*
find /NFS/euphrates_backup/GIS -name '*[0,2,4,6,8]' -exec ln -sf {}
/empty/GIS2/ \;
Then backup GIS1 and GIS2 as separate volumes.
Would it be better to try this trick with hard links? RMAN needs to be
able to delete uneeded files after each run.
The tricky part of this path is that if you have a single large filesystem
(and a few smaller ones), the single large one will dominate your tape usage,
resulting in an unbalanced backup window.
Cheers,
--Ian
--
Stephen Carville -- polluting the ranks of skeptics since 1995.
---
As democracy is perfected, the office of president represents, more and
more closely, the inner soul of the people. On some great and glorious
day the plain folks of the land will reach their heart's desire at last
and the White House will be adorned by a downright moron.
-- H. L. Mencken
Re: Directory too large for single tape.
Jon LaBadie wrote:
On Sun, Sep 10, 2006 at 10:48:08PM -0700, Stephen Carville wrote:
I've been using Amanda for about five years now. The only problems I've
ever had are because a single dumps has to fit on a single tape. I
usually solved this by using tar, client side compression, and breaking
up the partitions into smaller chunks. However, I seem to have reached
a limit.
One of my Oracle RMAN backups now stands at 109G. Even with compression
this requires 44G to 45G of space and will not fit on an AIT-2 tape.
The backups are dumped into a single directory and I don't know of any
way to split a directory with no subdirectories into two dumps. If
there is, I'd appreciate knowing how. Any other sugesstions are welcome.
Stephen,
what are we talking about in terms of files in a single directory
that total nearly 110GB? Is it one or two huge files? A hundred,
maybe a thousand, or more? What are the naming schemes? Always
the same or always predictable? Are there name extensions for
file types? If the numbers are reasonable you could create a
set of DLEs using include statements and a catch-all using
exclude statements.
For example, (assumptions include reasonable number of files,
say 1000 but I'm not certain what is reasonable, most with names
beginning with lowercase letters but a few with digits or uppercase
and an ascii charset :)
host Ora-a2g /path/to/RMAN/backup/dir {
your_current_dumptype
include file ./[a-g]*
}
host Ora-h2s /path/to/RMAN/backup/dir {
your_current_dumptype
include file ./[h-s]*
}
host Ora-t2z /path/to/RMAN/backup/dir {
your_current_dumptype
include file ./[t-z]*
}
host Ora-rest /path/to/RMAN/backup/dir {
your_current_dumptype
exclude file ./[a-z]*
}
All of the filenames end with a digit so something like this might work:
host Ora1 /path/to/RMAN/backup/dir {
your_current_dumptype
include file ./*[0,2,4,6,8]
}
host Ora2 /path/to/RMAN/backup/dir {
your_current_dumptype
include file ./*[1,3,5,7,9]
}
Do the hostnames have to be different or was that just for illutration?
--
Stephen Carville -- polluting the ranks of skeptics since 1995.
---
As democracy is perfected, the office of president represents, more and
more closely, the inner soul of the people. On some great and glorious
day the plain folks of the land will reach their heart's desire at last
and the White House will be adorned by a downright moron.
-- H. L. Mencken
Directory too large for single tape.
I've been using Amanda for about five years now. The only problems I've ever had are because a single dumps has to fit on a single tape. I usually solved this by using tar, client side compression, and breaking up the partitions into smaller chunks. However, I seem to have reached a limit. One of my Oracle RMAN backups now stands at 109G. Even with compression this requires 44G to 45G of space and will not fit on an AIT-2 tape. The backups are dumped into a single directory and I don't know of any way to split a directory with no subdirectories into two dumps. If there is, I'd appreciate knowing how. Any other sugesstions are welcome. I'm using: build: VERSION=Amanda-2.4.5 BUILT_DATE=Fri Jul 22 07:36:58 PDT 2005 BUILT_MACH=Linux amazon.totalflood.com 2.6.11-1.35_FC3smp #1 SMP Mon Jun 13 01:17:35 EDT 2005 i686 i686 i386 GNU/Linux CC=gcc CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=adm' paths: bindir=/usr/local/bin sbindir=/usr/local/sbin libexecdir=/usr/local/libexec mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/gtar COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip LPRCMD=/usr/bin/lpr MAILER=/usr/bin/Mail listed_incr_dir=/usr/local/var/amanda/gnutar-lists defs: DEFAULT_SERVER=amazon.totalflood.com DEFAULT_CONFIG=DailySet1 DEFAULT_TAPE_SERVER=amazon.totalflood.com DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- As democracy is perfected, the office of president represents, more and more closely, the inner soul of the people. On some great and glorious day the plain folks of the land will reach their heart's desire at last and the White House will be adorned by a downright moron. -- H. L. Mencken
Re: Tape AI T
[EMAIL PROTECTED] wrote:
Hi
I´ve a Sony AIT-1 i100/S tape installed in a FreeBSD 6.0 machine and I want
to use amanda. What´s the tapetype that I must to use and/ou other trips?
Her is the tapetype use for an AIT-1
define tapetype AIT1{
comment AIT-1 with 170m tapes
length 21568 mbytes
filemark 0 kbytes
speed 2699 kps
}
Regards
Engº Marcio Toledo
Analista de Informática - área de redes
Faculdade de Cïências Farmacêuticas - UNESP
Tel: 0xx-16-3322-2711
--
Stephen Carville -- polluting the ranks of skeptics since 1995.
---
Government is actually the worst failure of civilized man. There has
never been a really good one, and even those that are most tolerable are
arbitrary, cruel, grasping and unintelligent.
-- H. L. Mencken
Problems with amrecover in 2.4.5p1
My attempt to restore files with amrecover keep failing since I upgraded to 2.4.5. The output in amidxtaped.debug looks like: amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 20:33:06 2006 amidxtaped: version 2.4.5 amidxtaped: time 0.000: SECURITY USER root amidxtaped: time 0.001: bsd security: remote host shannon.totalflood.com user root local user amanda amidxtaped: time 0.001: amandahosts security check passed amidxtaped: time 0.001: CONFIG=daily1 amidxtaped: time 0.001: LABEL=UX0027 amidxtaped: time 0.001: FSF=18 amidxtaped: time 0.001: HEADER amidxtaped: time 0.001: DEVICE=/dev/ait2 amidxtaped: time 0.001: HOST=^shannon$ amidxtaped: time 0.001: DISK=^/var$ amidxtaped: time 0.001: DATESTAMP=20060217 amidxtaped: time 0.001: END amidxtaped: time 0.002: amrestore_nargs=0 amidxtaped: time 0.002: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = /dev/ait2 argv[4] = ^shannon$ argv[5] = ^/var$ argv[6] = 20060217 amrestore: could not open /dev/ait2: Permission denied amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission denied amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006 This makes no sense to me since I was able to recover the files using amrestore on the server. The client in the above is 2.4.5p1 the server is 2.4.5 -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
Re: Problems with amrecover in 2.4.5p1
Paul Bijnens wrote: On 2006-02-21 09:25, Stephen Carville wrote: My attempt to restore files with amrecover keep failing since I upgraded to 2.4.5. The output in amidxtaped.debug looks like: amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 [...] amrestore: could not open /dev/ait2: Permission denied amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission denied amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006 My first question then is, what are the permissions of /dev/ait2, and what are the user/group you are using for starting amidxtaped in (x)inetd. Sound of palm slapping forhead...That was it. /dev/ait2 is a symlink to /dev/nst0. I checked the old server and the permissions there were: crw-rw-r--1 root disk 9, 128 Aug 30 2001 /dev/nst0 On the new server: crw-rw 1 root disk 9, 128 Feb 19 11:53 /dev/nst0 Once I added the global read, amrecover worked again. I don't know how many time I looked at those permissions wihtseeing the problem. Thanks -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
Re: Client just started timing out.
Stephen Carville wrote: Ram TK Krishnamurthy wrote: Does changing the timeout on the server have any effect?` I hadn't thought of that. I increased it to 1800 for tomorrow night's run. I guess is was the timeout. Last night's backup ran as expected. -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
Client just started timing out.
For about a week one of my amanda clients has been timing out during planning. If I go into /tmp/amanda on thames (the client) I see a file like: $ cat amandad.20060131210039.debug amandad: debug 1 pid 18530 ruid 250 euid 250: start at Tue Jan 31 21:00:39 2006 amandad: version 2.4.5p1 amandad: build: VERSION=Amanda-2.4.5p1 amandad:BUILT_DATE=Mon Jan 30 08:08:00 PST 2006 amandad:BUILT_MACH=Linux thames 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=adm' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/gtar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=thames DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=thames amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 005-505AE508 SEQ 1138770050 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe7f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 005-505AE508 SEQ 1138770050 amandad: time 0.002: bsd security: remote host amazon.totalflood.com user amanda local user amanda amandad: time 0.013: amandahosts security check passed amandad: time 0.013: running service noop amandad: time 0.013: sending REP packet: Amanda 2.4 REP HANDLE 005-505AE508 SEQ 1138770050 OPTIONS features=feff9ffe7f; amandad: time 0.013: got packet: Amanda 2.4 ACK HANDLE 005-505AE508 SEQ 1138770050 amandad: time 0.013: pid 18530 finish time Tue Jan 31 21:00:39 2006 -- By comparison to other machines that do work, nothing in the above looks amiss. Moving over to the server (amazon), I see in the log DISK planner thames / DISK planner thames /boot DISK planner thames /export/common DISK planner thames /export/edi DISK planner thames /export/netapps DISK planner thames /export/private DISK planner thames /export/public DISK planner thames /var And then a few lines later FAIL planner thames /var 20060131 0 [Request to thames timed out.] FAIL planner thames /export/public 20060131 0 [Request to thames timed out.] FAIL planner thames /export/private 20060131 0 [Request to thames timed out.] FAIL planner thames /export/netapps 20060131 0 [Request to thames timed out.] FAIL planner thames /export/edi 20060131 0 [Request to thames timed out.] FAIL planner thames /export/common 20060131 0 [Request to thames timed out.] FAIL planner thames /boot 20060131 0 [Request to thames timed out.] FAIL planner thames / 20060131 0 [Request to thames timed out.] However, there is no indication on thames that the planner packet(s) were ever received. Shouldn't I at least see a sendsize.nn.debug file? Amazon is running amanda 2.4.5. Thames was running 2.4.3b2 when this all started but is now running 2.4.5p1. Fortunately in this case, none of the above is big problem. Thames is scheduled to be replaced soon and all of the important data is being mirrored to its replacement. Nevertheless, it is a bit frustrating to a have my backups mysteriously quit working on me. Suggestions are welcome. -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
Re: Client just started timing out.
Ram TK Krishnamurthy wrote: Does changing the timeout on the server have any effect?` I hadn't thought of that. I increased it to 1800 for tomorrow night's run. Anything in the /tmp/amanda/ logs on server? Nope. Not a mention of thames except for logfile cleanup (amtrmidx) since Jan 21. Any indications in syslog of a network burp? Nope. The only network change made recently was on Jan 19th I increased the MTU on amazon to 9000. However this is not affecting any of the other machines. Sorry, more questions than answers. Thanks tk Stephen Carville wrote: For about a week one of my amanda clients has been timing out during planning. If I go into /tmp/amanda on thames (the client) I see a file like: $ cat amandad.20060131210039.debug amandad: debug 1 pid 18530 ruid 250 euid 250: start at Tue Jan 31 21:00:39 2006 amandad: version 2.4.5p1 amandad: build: VERSION=Amanda-2.4.5p1 amandad:BUILT_DATE=Mon Jan 30 08:08:00 PST 2006 amandad:BUILT_MACH=Linux thames 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=adm' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/gtar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=thames DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=thames amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 005-505AE508 SEQ 1138770050 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe7f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 005-505AE508 SEQ 1138770050 amandad: time 0.002: bsd security: remote host amazon.totalflood.com user amanda local user amanda amandad: time 0.013: amandahosts security check passed amandad: time 0.013: running service noop amandad: time 0.013: sending REP packet: Amanda 2.4 REP HANDLE 005-505AE508 SEQ 1138770050 OPTIONS features=feff9ffe7f; amandad: time 0.013: got packet: Amanda 2.4 ACK HANDLE 005-505AE508 SEQ 1138770050 amandad: time 0.013: pid 18530 finish time Tue Jan 31 21:00:39 2006 -- By comparison to other machines that do work, nothing in the above looks amiss. Moving over to the server (amazon), I see in the log DISK planner thames / DISK planner thames /boot DISK planner thames /export/common DISK planner thames /export/edi DISK planner thames /export/netapps DISK planner thames /export/private DISK planner thames /export/public DISK planner thames /var And then a few lines later FAIL planner thames /var 20060131 0 [Request to thames timed out.] FAIL planner thames /export/public 20060131 0 [Request to thames timed out.] FAIL planner thames /export/private 20060131 0 [Request to thames timed out.] FAIL planner thames /export/netapps 20060131 0 [Request to thames timed out.] FAIL planner thames /export/edi 20060131 0 [Request to thames timed out.] FAIL planner thames /export/common 20060131 0 [Request to thames timed out.] FAIL planner thames /boot 20060131 0 [Request to thames timed out.] FAIL planner thames / 20060131 0 [Request to thames timed out.] However, there is no indication on thames that the planner packet(s) were ever received. Shouldn't I at least see a sendsize.nn.debug file? Amazon is running amanda 2.4.5. Thames was running 2.4.3b2 when this all started but is now running 2.4.5p1. Fortunately in this case, none of the above is big problem. Thames is scheduled to be replaced soon and all of the important data is being mirrored to its replacement. Nevertheless, it is a bit frustrating to a have my backups mysteriously quit working on me. Suggestions are welcome. -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel
Re: AIT2 tape size?
Toralf Lund wrote:
I've been meaning to ask about this for a long time:
Does anyone here use AIT2 tapes, a.k.a. SDX-50C, for Amanda backup? What
tape length are you using?
I ran amtapetype on my AIT-2 and;
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
This has proven pretty accurate.
Please note that I'm not asking for the tapetype entry from the
amanda.org archives, as it does not seem quite correct. I mean, the tape
size is specified as 50Gb, and that's more or less what the length
parameter in entry says, but it seems to me that it isn't actually
possible to write that much data to these tapes. The maximum seems to be
closer to 40Gb, actually.
OK, I might run amtapetype, but I'm lazy... And I'm also curious about
other people's experience with this tapes. For instance, can anyone
actually write as much as 50Gb?
- Toralf
--
Stephen Carville -- polluting the ranks of skeptics since 1995.
---
Government is actually the worst failure of civilized man. There has
never been a really good one, and even those that are most tolerable are
arbitrary, cruel, grasping and unintelligent.
-- H. L. Mencken
Thank you amanda
This morning the core server for my home network would not boot. The filesystem on the var partition was corrupt and even fsck couldn't fix it -- something about some inodes belonging to the wrong FS group. This evening I used lvm to create a new volume for var, added enough directories to get booted and used amanda to restore the partition from last nights's backup. I use an external USB drive for backups here at home so the whole process took about half an hour. In my pre-amanda days, this would have meant reinstalling the OS then recreating the lost configurations. I now return to lurking and learning from those who know more than me. -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
Re: Skip two tapes
On Monday November 08 2004 11:41 pm, Nicolas Ecarnot wrote: Hi, I have a configuration with ten tapes that runs nicely. For some reason, I have to skip two tapes : the last backup was made on tape05 and the next one has to be made on tape08 How can I do that ? What file should I hack for that ? You can use 'admadim config no-reuse tape' to temporarily remove them. Later, when you're ready to reuse them, 'amadmin config reusetape' . It can be a little tricky getting them back into the rotation in order tho :-) -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Fascism: When Socialism gets down to business.
Re: debugging chg-scsi
On Thursday November 04 2004 8:55 am, Erik Anderson wrote: Hello all - is there a way to get more information out of chg-scsi? I'm trying to debug a wierd issue: Good luck. I tried to get chg-scsi and chg-zg-mtx to works with a Spectra 2000 Treefrog and finally gave up. I ended up writing my own changer control program. [EMAIL PROTECTED] LPD $ amcheck LPD Amanda Tape Server Host Check - Holding disk /dumps/amanda: 36514756 KB disk space available, that's plenty amcheck-server: could not get changer info: could not read result from /usr/libexec/chg-scsi Amanda Backup Client Hosts Check Client check: 0 hosts checked in 0.001 seconds, 0 problems found I'm able to move tapes around, read them, etc using mt and mtx. Yes, I know that I could use chg-zg-mtx, but I'd like to find out why this is happening for curiosity's sake, if anything. If I run chg-scsi directly, this is what I get: [EMAIL PROTECTED] LPD $ /usr/libexec/chg-scsi -info No device found for tape eject And here's my chg-scsi.conf: number_configs 1 eject 1 # Tapedrives need an eject command sleep 5 # Seconds to wait until the tape gets ready cleanmax10 # How many times could a cleaning tape get used changerdev /dev/sg1 config 0 drivenum0 dev /dev/nst0 # the device that is used for the tapedrive 0 startuse0 # The slots associated with the drive 0 enduse 5 # statfile/etc/amanda/tape-slot # The file where the actual slot is stored cleancart 5 # the slot where the cleaningcartridge for drive 0 is located cleanfile /etc/amanda/tape-clean # The file where the cleanings are recorded usagecount /etc/amanda/backup/totaltime Thanks! -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Fascism: When Socialism gets down to business.
Re: debugging chg-scsi
On Thursday November 04 2004 9:52 am, Erik Anderson wrote: On Thu, 4 Nov 2004 09:44:38 -0800, Stephen Carville [EMAIL PROTECTED] wrote: Good luck. I tried to get chg-scsi and chg-zg-mtx to works with a Spectra 2000 Treefrog and finally gave up. I ended up writing my own changer control program. That's encouraging. ;-( Well, I don't want to discourage anyone from fixing it. Mostly all I did was port the shell script to Perl and worked from there. Even my Perl chokes once in a while but I suspect that is because the scsi tape driver in Redhat 7.2 is not as good as it could be. Eventually I want to upgrade the tape server to 9 or fedora. -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Fascism: When Socialism gets down to business.
Offsite Storage Options
My employer has been using Iron Mountain for offsite tape storage but their performance lately has been -- to be kind -- abominable. Does anyone have any reccommendations for a reliable offsite storage operation in the Los Angeles or Orange County areas of Southern California? Sorry if this a duplicate. I inadvertently sent the original from my work account instead of my home account. -- Stephen Carville Unix and Network Adminstrator DPSI 6033 W.Century Blvd. Los Angeles, CA 90045 310-342-3602
Re: New to Amanda- discouraged by some absurd limitations..
On Monday May 03 2004 11:05 pm, Justin Gombos wrote: * Jonathan Dill [EMAIL PROTECTED] [2004-05-02 12:44]: As others have pointed out, 700 MB CD-R is probably not going to be adequate for backing up multiple clients across the network anyway. I'll have to figure that out. I'm having trouble realizing how Amanda behaves. So far it doesn't look like I can reasonably predict when each file gets backed up. If a file's time stamp changes it will get backed up on teh next run. I find that pretty simple to predict. It seems it can't do a full backup, and then small incrementals that include only changed files. That is exactly what it does: A full backup of the data within each dumpcycle and all changed data is backed up between full dumps. -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: New to Amanda- discouraged by some absurd limitations..
On Monday May 03 2004 09:45 am, Jonathan Dill wrote: Jon LaBadie wrote: One of the concerns I have about disk-only based backup schemes is the total loss of data. If you encounter a 2-disk failure you lose not only your most recent, but all your backups. If a tape drive fails the data can be read on another drive. If a single tape goes bad, that is the only set of backups lost. If you're using multiple removable hard drives as tapes, I think that would mitigate the risk somewhat vs. disks that are online all the time, although spin-up seems to be THE most crucial moment in the life of any disk drive. I think disks still aren't as reliable as tapes in terms of failure rates, but would expect a removable hard drive solution to fall somewhere between full-time disk drives and tapes. I've been considering a backup to drive with daily copies made to tapes. I already use BackuoExec to backuop my Windoze boxes to a Samba share and then use Amanda to back those files up to tape. That works well so I don't see how a hybrid setup would be less robust than tapes alone. It means a lt lot of disk space -- in my case about 300 - 400 GB for a weeks worth -- but drives are getting real cheap. -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: New to Amanda- discouraged by some absurd limitations..
On Saturday May 01 2004 08:51 pm, Justin Gombos wrote: I was looking forward to using Amanda to backup 4-5 machines on my LAN and one over the Internet, but something seems incredibly stupid about the way Amanda forces the user to operate. Please tell me I'm wrong; maybe I'm misunderstanding the documentation. If I want to perform daily backups to CDRs, and I expect to have around 10 megs of data change per day, do I really have to waste an entire CDR every day? AFAIK, you are not wrong. At least with regard to tapes: Amanda does not put multiple backups on the same tape. However it also distributes the fulls over the tapecycle so add at least full/tapecycle to your estimate of space required. What does a CD-R cost these days? About 35-40 cents apiece? -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: Spectra Logic 6100 AIT library, tape settings ?
On Monday March 29 2004 08:32 am, Mark W4CHL wrote:
Have recently acquired a Spectra Logic AIT 6100 library, but don't see
any definitions for setting up the tape gripper in the library. Before
we get another one of these things as a spare, anyone have some hints
or tips to getting this thing working ?
If it is essentially the same as the 2000 then mtx will control the changer
and mt will control the tape drive. Here are the tapetypes I use:
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
define tapetype AIT2-100 {
comment AIT-2 with 230m tapes -- compression on
length 10 mbytes
filemark 3120 kbytes
speed 8100 kps
}
If you are unable to get any of the changer scripts to work, try:
http://www.heronforge.net/programs/chg-spectra.pl
Seems this is an early version of the Spectra Logic 2K (TreeFrog). I
haven't found any tape settings for either model from the Amanda.org
references.
Take it easy here on an Amanda newbie !
Cheers de Mark @ 7tronics
--
Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
--
Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: Barcode readers: how important?
On Tuesday November 25 2003 08:51 am, Fran Fabrizio wrote: Next question: They want $250 for 300 barcode labels. That seems excessive. Can these be made/obtained more reasonably? Depends on the label :-) I get AIT labels at $17.00 - $18.00 per shee pluss shippingt; 45 labels per sheet from http://www.issioptical.com/barcode_labels.html Make sure you know what kind of encoding your changer needs. -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Right wing socialists hate privacy as much as left wing socialists hate guns.
Always-full and incrementals
I have the following dumptype defined:
define dumptype global {
comment Global definitions
index yes
}
define dumptype always-full {
global
comment Full dump of this filesystem always
program GNUTAR
compress none
priority high
dumpcycle 0
}
Then in the disklist I have entries like:
chena /db/nt-backups/bering {
always-full
exclude Changer.cfg
}
However, lately I keep seeing entries like this in the emails:
chena:/db/nt-backups/bering 1 [dumps way too big, must skip incremental
dumps]
Now, if I am requesting always full, I should never see an incremental. Right?
Secondly what does the message mean? The file sizes are no larger than
usual. The particuar one above is only about 5.3G. Also, the amuont of data
written to tape is consistent with the backup being done sucessfully.
I am using amanda version 2.4.3b2
--
Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
--
Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: Always-full and incrementals
On Wednesday November 05 2003 07:42 am, you wrote: Stephen Carville wrote: chena:/db/nt-backups/bering 1 [dumps way too big, must skip incremental dumps] Now, if I am requesting always full, I should never see an incremental. Right? The message actually means something like: even an incremental one is too large. Secondly what does the message mean? The file sizes are no larger than usual. The particuar one above is only about 5.3G. Also, the amuont of data written to tape is consistent with the backup being done sucessfully. What is your tapesize set to? The size of that particular DLE is maybe not enough, but the total sum of data is. In the amdump file you can follow what planner thinks about the estimated sizes. From the name of the DLE, I guess it is a backup of some NT already, so probably the contents do change almost completely. Therefore an incremental or full would be about the same size. Yeah. They're files from Backup Exec. Turns out what happened was I recently switched from using AIT1 tapes for the NT backups to AIT2 tapes. However, I left the tapetype set at AIT1. Once the backups got loo large for 2 AIT1 tapes (runtapes = 2) amandam truied to get clever. :-) I've changed the tapetype to AIT2 so everything should be OK from now on. Thanks to everyone who answered. Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: Is this a valid disklist entry?
It may be correct but it looks wrong to me. Here is a example of a
disklist entry I use for a Snap server:
chena //snap01/development {
user-tar
exclude Temporary??Not?Backed?Up??
}
This needs to be accompanied by an entry in /etc/amandapass something
like:
//snap01/developmentbackupuser%passworddomain
On Sunday 24 August 2003 09:03 am, Robin WONG wrote:
Hi
I am attempting to backup a huge windows partition found on a snap
server
via a linux box. At first, I smbmounted the share and backed it up
via
this mount method. But I noticed that whether it was doing a level
0 dump
or a level 1 dump, the dumpsize was no different. It was always
doing a
level 0 regardless.
So, I had a look in docs/SAMBA, and I am guessing smbmount doesn't
take
into account the 'archive' bit. But when I stat a file on the
share, it
appears to return valid information, so I don't see why smbmounting
doesn't work. Anyway...
Suffice it to say, I can't do a full dump of the snap server every
evening, so I've attempted to use smbclient. However, the disklist
entry
I used for smbmounted shares no longer works. Amcheck fails with
the
following:
Amanda Backup Client Hosts Check
ERROR: snazz: [Can't open disk '//snapserver/files']
ERROR: snazz: [No include for '/mnt/snap/uz']
ERROR: snazz: [Can't open disk '//snapserver/files']
ERROR: snazz: [No include for '/mnt/snap/qt']
ERROR: snazz: [Can't open disk '//snapserver/files']
ERROR: snazz: [No include for '/mnt/snap/mp']
ERROR: snazz: [Can't open disk '//snapserver/files']
ERROR: snazz: [No include for '/mnt/snap/il']
ERROR: snazz: [Can't open disk '//snapserver/files']
ERROR: snazz: [No include for '/mnt/snap/eh']
ERROR: snazz: [Can't open disk '//snapserver/files']
ERROR: snazz: [No include for '/mnt/snap/ad']
Client check: 7 hosts checked in 2.099 seconds, 12 problems found
(brought to you by Amanda 2.4.4)
Here is one of the modified disklist entries I've attempted to use
to
backup the snap server:
snazz /mnt/snap/uz //snapserver/files {
# all directories that start with [u-z]
root-tar
include ./[u-zU-Z]*
} 1
I am running Samba 2.2.3a on RH7.3 with gtar 1.13.25 and AMANDA
2.4.4
I can't tell what I am doing wrong...unless there is a disklist
entry
limitation for samba shares...or exclude limitation of using tar
over
samba.
thanks
r
--
god# sed -e 's/windows/unix/g' world.conf
--
Stephen Carville
--
Right wing socialists hate privacy as much as the left wing
socialists hate guns.
Re: barcode readers and am-labels
On Wednesday 20 August 2003 11:45 am, Deb Baddorf wrote: Hi all -- I have a barcode reader with my tape robot. I've tested the robot and got it playing nicely with amanda; nut I haven't yet told her that it can do barcodes. In what fashion does amanda make use of the bar codes, assuming I tell her that I have a reader (havereader = 1)? Does amanda use them while finding tapes, or just report them to me for my visual usage? AFAIK, the amtape will use the file changer-barcodes to find a tape. I am not 100% sure of that because I wrote my own changer. Does the barcode label need to match the amlabel string? No. (it is kind of long for barcoding) Or is the barcode just *associated* with the amlabel (in the mentioned barcode database)? i.e. is UX0001 associated with MyTapeStringDaily-034 by the barcode database or does it have to actually *say* MyTapeStringDaily-034 on the barcode? When amlabel writes a label it add it and the barcode to the file changer-barcodes. If there is no barcode available the then barcode is a recorded as -1. -- Stephen Carville -- Right wing socialists hate privacy as much as the left wing socialists hate guns.
Re: CONGRATULATIONS!!!
On Tuesday 05 August 2003 05:57 am, Russell Adams wrote: Wow! Get 50M for using Amanda and helping out on the mailing list! Woo! Hmmm... Reckon I missed that message. Gots to admit that bogofilter is doing a pretty good job of filtering the spam. -- Stephen Carville -- Right wing socialists hate privacy as much as the left wing socialists hate guns.
Re: Failure because of missing tapes.
On Sunday 10 August 2003 02:10 pm, Jon LaBadie wrote: On Sun, Aug 10, 2003 at 11:59:52AM -0700, Stephen Carville wrote: Whenever Amanda has to roll over to a new tape and the first tape in the expected list is missing, the backups fail. For example, last night, the expected tapes were: C83166 C83259 C83170 The tape C83166 was not in the changer so my wrapper script loaded C83259, fired off amdump, and the backup started up fine. However, when the tape ran out, Amanda tried to load C83166 but couldn't find it and failed. C83170 was available but Amanda apparently did not try to load it. When amanda reported the next 3 tapes amanda expects are: was C83170 within that group? Yep: The next Amanda run should go onto tape C83166 or a new tape. The next Amanda run should go onto tape C83170 or a new tape. The next Amanda run should go onto tape C83257 or a new tape. Also, was C83170 used more than 14 tapes ago? Yep, again. I think unless at least the 2nd condition is met, that amanda will not use a tape. Perhaps but, AFAIK, if the tape is more than one cycle old (in this case over seven days) it should be reusable. Is there a configuration option I can use to tell Amanda to try the next tape if the desired tape is not avaialble? ... from amanda.conf dumpcycle 7 days runspercycle 6 tapecycle 14 tapes runtapes 3 end - I actually have 19 tapes allocated for this backup. I'd say have several more available, but not labeled. When you are about to encounter that situation, label a new tape. Amanda will always take a new tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Stephen Carville -- Right wing socialists hate privacy as much as the left wing socialists hate guns.
Re: Backup Server will not back itself up.
On Monday July 28 2003 12:27 am, you wrote: Stephen Carville wrote: About a week ago, my backup server stopped backing itself up: ... GNUTAR //snap01/development 0 1970:1:1:0:0:0 -1 exclude-file=Temporary\ \(Not\ Backed\ Up\!\) Exclude/Include list with spaces in the names do not work (yet). I have a (very ugly!) patch if urgent. But the good fix is much more difficult. See: http://groups.yahoo.com/group/amanda-hackers/message/3761 That was/is the problem. I had the same problem with spaces in file names a while back and I thought escaping them with a backslash fixed it. Next I'm going to try: exclude = Temorary??Not?Backed?Up?? ... FORMAT ERROR IN REQUEST PACKET ... REQ packet is bogus: extra text at end -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Mom Pop were just a couple of kids when they got married. He was eighteen, she was sixteen and I was three. -- Billie Holiday
Backup Server will not back itself up.
About a week ago, my backup server stopped backing itself up: chena /var lev 0 FAILED [badly formatted response from chena] chena /boot lev 0 FAILED [badly formatted response from chena] chena / lev 0 FAILED [badly formatted response from chena] All the other machines backup fine and theis setup as been workng for over a year. The only change I've made recently is to recompile the kernel with a tape support as a module. I've tried rebuilding and reinstalling amanda and I tried going back to the kernel with the tape support compiled in. Neither made a difference. A sample amandad.debug: amandad: debug 1 pid 23803 ruid 250 euid 250 start time Sun Jul 27 06:00:40 2003 amandad: version 2.4.3b2 amandad: build: VERSION=Amanda-2.4.3b2 amandad:BUILT_DATE=Fri Jul 25 16:50:11 PDT 2003 amandad:BUILT_MACH=Linux chena 2.4.18 #6 SMP Wed Jul 23 10:08:38 PDT 2003 i686 unknown amandad:CC=gcc amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient amandad:GNUTAR=/bin/gtar COMPRESS_PATH=/bin/gzip amandad:UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=chena DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=chena amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc got packet: Amanda 2.4 REQ HANDLE 001-F8250808 SEQ 1059310840 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=chena; GNUTAR //snap01/development 0 1970:1:1:0:0:0 -1 exclude-file=Temporary\ \(Not\ Backed\ Up\!\) GNUTAR //snap01/development 1 2003:7:15:9:51:31 -1 exclude-file=Temporary\ \(Not\ Backed\ Up\!\) GNUTAR /var 0 1970:1:1:0:0:0 -1 exclude-list=.exclude GNUTAR /var 1 2003:7:21:20:17:10 -1 exclude-list=.exclude GNUTAR /boot 0 1970:1:1:0:0:0 -1 exclude-list=.exclude GNUTAR /boot 1 2003:7:21:21:27:37 -1 exclude-list=.exclude GNUTAR / 0 1970:1:1:0:0:0 -1 exclude-list=.exclude GNUTAR / 1 2003:7:21:20:38:14 -1 exclude-list=.exclude sending ack: Amanda 2.4 ACK HANDLE 001-F8250808 SEQ 1059310840 bsd security: remote host chena user amanda local user amanda amandahosts security check passed amandad: running service /usr/local/libexec/sendsize amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-F8250808 SEQ 1059310840 OPTIONS maxdumps=1; FORMAT ERROR IN REQUEST PACKET amandad: got packet: Amanda 2.4 ACK HANDLE 001-F8250808 SEQ 1059310840 and sendsize.debug: sendsize: debug 1 pid 23804 ruid 250 euid 250 start time Sun Jul 27 06:00:40 2003 /usr/local/libexec/sendsize: version 2.4.3b2 REQ packet is bogus: extra text at end sendsize: pid 23804 finish time Sun Jul 27 06:00:40 2003 -- Stephen Carville -- Right wing socialists hate privacy as much as the left wing socialists hate guns.
Re: blacklisted verizon mail server
Does your outgoing mail go thru out013pub.verizon.net [206.46.170.44]? That server is blacklisted becasue it is an open relay. I had to whitelist the verizon.net domain because some of my employer's customers use verizon addresses and the admins at verizon insist that that server is not an open relay. I tested it. It _is_ an open relay. Here is a copy of a test email from abuse.net -- begin Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.heronforge.net (Postfix) with ESMTP id 72C279001E for [EMAIL PROTECTED]; Fri, 4 Apr 2003 18:35:04 -0800 (PST) Received: from mail.cpl.net [216.117.199.213] by localhost with POP3 (fetchmail-6.2.0) for [EMAIL PROTECTED] (single-drop); Fri, 04 Apr 2003 18:35:04 -0800 (PST) Received: by luke.cpl.net (mbox carville) (with Cubic Circle's cucipop (v1.31 1998/05/13) Fri Apr 4 18:33:58 2003) X-From_: [EMAIL PROTECTED] Fri Apr 4 18:30:37 2003 Received: from out013.verizon.net (out013pub.verizon.net [206.46.170.44]) by luke.cpl.net (8.11.3/8.11.3) with ESMTP id h352Ual71791 for [EMAIL PROTECTED]; Fri, 4 Apr 2003 18:30:36 -0800 (PST) Received: from www.abuse.net ([208.31.42.77]) by out013.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Fri, 4 Apr 2003 20:31:37 -0600 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: Test for susceptibility of [206.46.170.44] to third-party mail relay Date: Sat, 05 Apr 2003 02:31:34 GMT Message-Id: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] X-Sender-IP: 209.189.103.195 X-Envelope: [EMAIL PROTECTED] - [EMAIL PROTECTED] X-jf: 20010528, 1:1,2:1,3:0,4:0,ad:0,bo:0,di:1,do:1,he:1,ip:1,us:1 Lines: 14 Content-Type: X-UID: 11462 This is a test of third-party mail relay, generated via the Network Abuse Clearinghouse at http://www.abuse.net. Target host = 206.46.170.44 verizon.net Test performed by [EMAIL PROTECTED] from 209.189.103.195 A well-configured mail server should NOT relay third-party email. Otherwise, the server is subject to abuse by vandals and spammers, and probable blacklisting by recipients of the unwanted third-party e-mail. For information on how to secure a mail server against third-party relay, visit URL: http://www.mail-abuse.org/tsi/. -- end I also tested by the good 'ol telnet to port 25 and type in the commands by hand method. On Friday April 04 2003 04:26 pm, Gene Heskett wrote: Jon; I've sent a nastygram to [EMAIL PROTECTED] in an attempt to get this fixed. We'll see if they use their own list and it bounces. Yup, it did, as did my attempted forward of the bounce message to [EMAIL PROTECTED] regarding it. But a seperate message to postmaster went thru. I've also sent a similar msg, but a bit less nasty to [EMAIL PROTECTED] That one hasn't bounced. Me, a spammer? Thats hillarious. Nosy maybe, a bit of a knowitall too (old farts usually get that way, in case no one has noticed :), but a spammer? Boggles the mind. Good Grief even! Its raining here, sporadicly, and I have to work the graveyard at the transmitter tonight. Its beginning to get the wobblies according to the operators. And I haven't managed to get all the mud off my old 4wd pickup truck from my last trip up there.
Re: Mailreport debugging
On Monday 31 March 2003 03:19 am, Mats Blomstrand wrote: Im almost there now! Thanks for all help everyone! How are amanda sending the mail-reports? Is there a way to configure how it does? My problem is that it i want it to send reports to [EMAIL PROTECTED]. The sendmail on tapeserver is configured to talk to an central mailserver. That mailserver refuses to accept mail if it cant resolve the sender, and there is no [EMAIL PROTECTED] on that machine. Any suggestions? In amanda.conf, set mailto to [EMAIL PROTECTED] ... -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt === You have the right to remain helpless. Should you give up this right, anything you do will be used against you in a court of law. You have the right to an assailant. If you cannot find one yourself, the court will release one for you.
Re: tape drive opinions
With or without a changer? Look at the Spectra Logic libraries with AIT-2 or AIT-3 drives. On Saturday 29 March 2003 07:58 pm, Jeremy L. Mordkoff wrote: I need a 80 GB+ tape drive for a Dell Poweredge 2500 running Redhat 8.0 and Amanda Any suggestions? Thanks in advance JLM Jeremy Mordkoff Tatara Systems 978-206-0808 (direct) 978-206-0888 (fax) injustice anywhere threatens justice everywhere -- Dr. Martin Luther King -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt === The difference between robbery and taxes is simple: The first is someone threatening to hurt you if you do not give them your money. The second is legal.
Re: Problem with amrecover
Are backup and localhost different machines? On Thursday 27 March 2003 10:17 pm, Bartho Saaiman wrote: Hi All :) I am trying to restore from a tape using amrecover. If I use amrecover DailyBackup it says: AMRECOVER Version 2.4.2p2. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused If I use the -s backup and/or -t backup I also get the same: AMRECOVER Version 2.4.2p2. Contacting server on backup ... amrecover: cannot connect to backup: Connection refused I previously had a similar problem and rectified this by editing the /var/lib/amanda/.amandahosts and added localhost root to the file. Tried this as I am running amrecover as root but still could not fix it. Any suggestions on what I am missing?? -- # Bartho Saaiman # Network Administrator # Stellenbosch Automotive Engineering # Tel :: 27 21 882 8820 x 215 # Email :: bartho @ cae.co.za -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt === The difference between robbery and taxes is simple: The first is someone threatening to hurt you if you do not give them your money. The second is legal.
Re: Problems restoring from amanda server
On Thursday March 27 2003 12:20 pm, Alex Thurlow wrote: Forgive me if this is a stupid question, but I just switched to amanda from a custom setup and am having a problem when I try to restore. If I do: amrecover DailyBackup it says: AMRECOVER Version 2.4.2p2. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused I didn't backup to the local server. How do I tell the amanda client where to restore from? # amrecover -C config -s index server -t tape server
amrecover permission problem
I am having a permission problem with amrecover that makes no sense to me. Please cc me on any replies. I am a memebr of the list but I haven't seen any mail in a while $ sudo amrecover -C daily1 -s chena AMRECOVER Version 2.4.3b2. Contacting server on chena ... 220 chena AMANDA index server (2.4.3b2) ready. 200 Access OK Setting restore date to today (2003-03-14) 200 Working date set to 2003-03-14. 200 Config set to daily1. 200 Dump host set to thames. Trying disk /export ... Trying disk md0 ... Can't determine disk and mount point from $CWD '/export/recover' amrecover setdisk /export/private Scanning /scratch/amanda... 200 Disk set to /export/private. amrecover cd haxume/Accounting /export/private/haxume/Accounting amrecover setdate 2003-03-05 200 Working date set to 2003-03-05. amrecover add Acct Rec 03.xls Added /haxume/Accounting/Acct Rec 03.xls amrecover extract Extracting files using tape drive /dev/ait2 on host thames. The following tapes are needed: C83256 Restoring files into directory /export/recover Continue? [Y/n]: y Load tape C83256 now Continue? [Y/n/t]: y amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 The amidxtaped file shows: $ cat amidxtaped.20030314110107.debug amidxtaped: debug 1 pid 25567 ruid 250 euid 250 start time Fri Mar 14 11:01:07 2003 amidxtaped: version 2.4.3b2 SECURITY USER root bsd security: remote host thames user root local user amanda check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amidxtaped: security check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed security check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amidxtaped: pid 25567 finish time Fri Mar 14 11:01:07 2003 On Chena I have in .amandahosts: thames root thames amanda On Thames: chena amanda chena root The tape is loaded in the drive and I have checked it with dd to be sure it is readable. Both thames and chena are in /etc/hosts. Netstat shows an established connection between thames and chena:amadaidx. I've restored using amrecover before so why doesn't amanda allow me to connect now? -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
amrecover permission problem -- followup
I don't know if this was the cause or not but: The machine thames has two IP addresses. One on eth0, the other on eth0:1. Once I added both addresses to the host file on _both_ machines, amrecover happily restored the file. I'll admit I have no idea why this should make a difference, tho. All traffic I could see went thru the the primary eth0 address.
Re: Labels and Barcodes
The barcode is printed on the physical label on the tape. It is read by a laser and stored in the changer memory. I have no idea if the changer can print barcode labels but there is software that can. I buy my tapes AIT-2 with barcodes labels already on them so that is another option. On 16 Aug 2002, Jason Greenberg wrote: - Then how do you set the barcode? Is it a physical label? If my libary - reads bar codes, will it also print them? - - On Thu, 2002-08-15 at 16:25, Stephen Carville wrote: - On 15 Aug 2002, Jason Greenberg wrote: - - - What's the difference between labels and barcodes? Why, when I label - - tapes, does the VolumeTag= not show up for that tape? - - To amanda, a label is the information in the fist part of a tape. It - identifies what backup set the tape belongs to, when it was last used, - etc. Labels have nothing to do with the 'Volume Tag which are from - the barcodes. - - -- - -- Stephen Carville - UNIX and Network Administrator - DPSI (formerly Ace USA Flood Services) - 310-342-3602 - [EMAIL PROTECTED] - - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Labels and Barcodes
On 15 Aug 2002, Jason Greenberg wrote: - What's the difference between labels and barcodes? Why, when I label - tapes, does the VolumeTag= not show up for that tape? To amanda, a label is the information in the fist part of a tape. It identifies what backup set the tape belongs to, when it was last used, etc. Labels have nothing to do with the 'Volume Tag which are from the barcodes. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Sending mail from LAN.
The best doc IMO is DNS and Bind from O'Reilly. If you are goiung to be administering DNS suggest you buy it. I assume you have a server that does DNS for the zone called systematic.lan. If you are using Bind, add to the zone file after the ORIGIN statment (or the @ symbol) a record like: IN MX 10 mail then, if necessary, add an A record for the mail server. mail IN Aip.address.of.machine It will end up something like: $TTL3600 @ IN SOA dns.systematic.lan. domainadmin.systematic.co.za. ( 17 ; serial 3H ; refresh 15M ; retry 1W ; expire 3600 ) ; default IN NS dns IN MX 10 mail mailIN A192.168.12.69 etc... IF you are using Windoes, select New Mail Exchanger and fill in the values. Make sure there is an A record for the mail server. Do NOT point an MX name to a CNAME record (Alias on Windoes). You have been warned! On Wed, 31 Jul 2002, Trevor Fraser wrote: - Hello Stephen, - - I've done some work on our DNS server, but I am unfimiliar with a valid MX - record. How do I go about this, or if you prefer, do you know of a nice - doc on the subject. - - Thanks, Trevor. - - - Original Message - - From: Stephen Carville [EMAIL PROTECTED] - To: Trevor Fraser [EMAIL PROTECTED] - Cc: [EMAIL PROTECTED] - Sent: Tuesday, July 30, 2002 7:27 PM - Subject: Re: Sending mail from LAN. - - - Set up your DNS server to return a valid MX record for systematic.lan. - - On Tue, 30 Jul 2002, Trevor Fraser wrote: - - - Hello all. - - - - I've managed to sort out sending mail message to [EMAIL PROTECTED] - , - - many thanks to all who replied. This mailling list is worth more than - - gold...every tried getting support from the present leading software - - developersfat chance you little drop in the ocean!!! Just give a - - though for what we've got going here guys and girls. - - - - Sorry for the side track, I just rerealised how blessed Linux users are. - - - - The problem now is that our LAN domain doesn't exist on the internet, - and - - our mail-server only accepts mail from existing domains. How do I send - mail - - from an existing domain, or at least appear to be? - - - - -- - -- Stephen Carville - UNIX and Network Administrator - DPSI (formerly Ace USA Flood Services) - 310-342-3602 - [EMAIL PROTECTED] - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Sending mail from LAN.
Set up your DNS server to return a valid MX record for systematic.lan. On Tue, 30 Jul 2002, Trevor Fraser wrote: - Hello all. - - I've managed to sort out sending mail message to [EMAIL PROTECTED] , - many thanks to all who replied. This mailling list is worth more than - gold...every tried getting support from the present leading software - developersfat chance you little drop in the ocean!!! Just give a - though for what we've got going here guys and girls. - - Sorry for the side track, I just rerealised how blessed Linux users are. - - The problem now is that our LAN domain doesn't exist on the internet, and - our mail-server only accepts mail from existing domains. How do I send mail - from an existing domain, or at least appear to be? - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Memory leak?
On Mon, 1 Jul 2002, Trevor Morrison wrote: -HI, - - I am experiencing a severe memory leak in my RH 7.1 system 2.4.17 - modular kernel.. I will chew up about 720 M in about 6 hours. I was - wondering how many instances of dumper and taper need to be running when - amanda is started from a cron job. I currently show 2 tapers and 4 - dumpers as output from the ps -aux command. Does any one have a quick - and dirty way of seeing what is hogging all the memory? Any help is - appreciated. You can control the maximum numer of dumpers using 'inparallel' in amanda.conf. I doubt amanda is eating up your memory. I have never used it on RH 7.1 but I have run it on 7.0 and 7.2 with no problems not related to getting the tape drive and changer to work. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Sparse option again
OK, I guess it is not possible to turn of the --sparse option on any particular backup. So what would be the consequences of turning it off for all backups? I figure I can hack the sourse code to do it. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: S.O.S.
runtapes 2 You have to have a working changer configuration. On Fri, 11 Jan 2002, [iso-8859-15] Túlio Machado de Faria wrote: - Help me, please. - - - I need to use amanda with two units of tape in one backup. - - How? - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Permission _still_ denied
On Fri, 5 Apr 2002, Doug Silver wrote: - Hi Stephen - - - At first glance this appears like you might have built the amanda client - stuff with the tcp/udp portrange but not the amanda server. I'm not sure - since I'm using 2.4.2p2, so perhaps with this newer version the debug - messages are different. Does the amanda user have permission to - open up privileged ports (1024 -- I think)? That almost seems the - problem since if that user can't open up a connection on port 960 to - listen, but it can on 59116. I checked the config.status for both machines and I configured amanda --with-user=amanda --with-group=adm. AFAIK, the default is no portrange. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: multiple amdump per day overwrites level0
On 10 Apr 2002, Frederic Saincy wrote: - Hi all, - - in my amanda.conf - ### - dumpcycle 1 weeks - runspercycle 5 - tapecycle 6 tapes - ### - - i ran 7 amdumps today (testing). The first amdump does a level0, and - the last overwrite this unique level0 with a level1. - - This is a bug, a feature or did i miss something ? :) - - I can give more information if needed. - - Thank you and Bye. As I undertand the amanda scheduling algorithm, it does a full for everything to get started and then tries to spread the fulls out over the tapecycle. So, when you hit the seventh amdump, you should have a full of every filesystem on one of tapes 2 thru 6 so tape 1 can hold partials. To list what backups are on what tapes, try: $ amadmin config find $ amadmin config info $ amoverview config -- -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt == Government is like burning witches: After years of burning young women failed to solve any of society's problems, the solution was to burn more young women. ==
Re: Finding tapes
Try amadmin config find This prints out date, host, disk, level, tape, and status for everything in config. On Fri, 11 Jan 2002, Paul Lussier wrote: - - Hi all, - - I've been asked to locate a set up tapes based on dates. Any idea - how I do this? Basically I just need to search the date stamps for - each tape and tell my boss which tapes contain backups for the - specified period of time. - - I looked at the amadmin command, but the sub-commands all seem to - want a hostname. I need the information for *all* systems. - - Basically, if the tape was written to during the specified range, I - need to know. - - Any ideas? - - Thanks, - - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Spectra Logic Treefrog configuration
On Thu, 7 Mar 2002, F.M. Taylor wrote: - - How do I move a tape to the door. Thats the only thing I can't seem to - figure out. On my Spectra Logic (2000) there is no special provision for removing a tape. I just eject the tape (amtape config eject), open the door and remove the tape by hand. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
bind_portrtange: Permission denied
Two days ago, backups for one of the directories on my samba server started failing. Nothing was changed in the amanda configuration and this problem only affects the one directory. Total size of the directory is about 7.5 G. Unfortunately this is a shared drive exported to windows users via samba and suffers 'unintentional' deletions about twice a month. I've included the relevant parts of the e-mail and sendsize, sendbackup and runtar debug files. The only problem I can see : sendbackup: bind_portrange: port 909: Permission denied but this only happens on this one drive. Anyone know why? From email: /-- thames /export/common lev 0 FAILED [data timeout] sendbackup: start [thames:/export/common level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end \ From sendsize.debug: sendsize: calculating for amname '/export/common', dirname '/export/common' sendsize: getting size via gnutar for /export/common level 0 sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . Total bytes written: 7442524160 (6.9GB, 253MB/s) . sendsize: getting size via gnutar for /export/common level 1 sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_1.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . Total bytes written: 130897920 (125MB, 18MB/s) From sendbackup.debug sendbackup: debug 1 pid 7739 ruid 250 euid 250 start time Thu Apr 4 06:04:02 2002 /usr/local/libexec/sendbackup: version 2.4.3b2 sendbackup: got input request: GNUTAR /export/common 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;exclude-list=.exclude; parsed request as: program `GNUTAR' disk `/export/common' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;index;exclude-list=.exclude;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: bind_portrange: port 909: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.57536 sendbackup: bind_portrange: port 909: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.57537 sendbackup: bind_portrange: port 909: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.57538 waiting for connect on 57536, then 57537, then 57538 sendbackup: stream_accept: connection from 192.168.124.25.39935 sendbackup: stream_accept: connection from 192.168.124.25.39936 sendbackup: stream_accept: connection from 192.168.124.25.39937 got all connections sendbackup-gnutar: doing level 0 dump as listed-incremental to /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: spawning /usr/local/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . sendbackup: started index creator: /bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup-gnutar: /usr/local/libexec/runtar: pid 7742 From runtar.debug: runtar: debug 1 pid 7742 ruid 250 euid 0 start time Thu Apr 4 06:04:02 2002 gtar: version 2.4.3b2 running: /bin/gtar: gtar --create --file - --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Amanda and xinetd
On Tue, 11 Jun 2002, Cory Visi wrote:
- Well all my problems are basically due to the fact that Amanda refuses to
- work with xinetd. This was suggested by someone on the list and I finally
- decided to try it. Why doesn't Amanda work with xinetd? There is no good
- debugging log that would help in figuring out this problem. Amandad clearly
- does not recognize the IPv4 unicast bindings that it needs to with xinetd.
-
- Here is my inetd.conf:
-
- amanda dgram udp wait backup /usr/local/libexec/amandad amandad
-
- Here is my relevant xinetd.conf:
-
- service amanda
- {
- id = amanda-udp
- log_on_success += USERID
- log_on_failure += USERID
- socket_type = dgram
- protocol = udp
- wait = yes
- user = backup
- server = /usr/local/libexec/amandad
- }
-
- This really looks like a bug in the program as xinetd and inetd are
- designed to operate as identical as possible.
I use amanda 2.4.2p2 with xinetd.
/etc/xinetd.d/amanda:
# default: off
# description: AMANDA backup services
#
service amanda
{
socket_type = dgram
wait= yes
user= amanda
group = adm
server = /usr/local/libexec/amandad
disable = no
}
service amandaidx
{
socket_type = stream
wait= no
user= amanda
group = adm
server = /usr/local/libexec/amindexd
disable = no
}
service amidxtape
{
socket_type = stream
wait= no
user= amanda
group = adm
server = /usr/local/libexec/amidxtaped
disable = no
}
/etc/services:
amanda 10080/tcp
amanda 10080/udp
amandaidx 10082/tcp
amidxtape 10083/tcp
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
Re: amrecover problems
Use setdisk to tell amrecover what backup you want to restore from. On Tue, 11 Jun 2002, M. Cao wrote: - - - Can you explain the error on last line (Can't determine disk and mount - point from $CWD ) - - The index shows 20 files had been backup on the tape. But I can not list - any file from amrecover - - - bash-2.05# ./amrecover daily - AMRECOVER Version 2.4.2p2. Contacting server on bouncer ... - 220 bouncer AMANDA index server (2.4.2p2) ready. - 200 Access OK - Setting restore date to today (2002-06-11) - 200 Working date set to 2002-06-11. - 200 Config set to daily. - 200 Dump host set to bouncer. - Can't determine disk and mount point from $CWD - - - - - - Thanks - Minh - - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: amrestore problems
I guess it really was a permission problem. I added read permission to all on the tape device and I can extract files now. Anyone know why this is necessary? Permissions on the devices were: crw-rw1 root disk 9, 128 Aug 30 2001 /dev/nst0 and amanda ia member of the 'disk' group $ id amanda uid=250(amanda) gid=4(adm) groups=4(adm),6(disk) This seems to be OK for writing but not for reading. Is this an amanda feature? On Thu, 6 Jun 2002, Stephen Carville wrote: - I recently moved from solaris to linux so I am testing amrestore - again. I keep getting the following error: - - EOF, check amidxtaped.debug file on chena. - amrecover: short block 0 bytes - UNKNOWN file - amrecover: Can't read file header - extract_list - child returned non-zero status: 1 snip -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: amanda This account is currently not available.
On Fri, 7 Jun 2002, tom wrote: - first off I'm real real green at this Unix stuff. Person that used to take - care of this where I work left and now someone forgot to change the tape and - I need to perform an amflush. - - When I go to do this I get this error message amflush: must run amflush as - user amanda - - I try and login as amanda and I get this error message This account is - currently not available. - - How do I make the amanda account available so I can do the flush? What platform? As root, try 'su - amanda'. I never allow logins as amanda and setup the system so backup operators can su to the amanda user via sudo. If the above does not work then you may need to create the user. Check the amadna directory to get the correct uid and gid. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Can AMANDA only backup 24GB partitions???
Not as far as I know. This Monday one of my oracle directories generated a little over 50G of backup and another did today. I've also done special backups of 80G to 90G. On Wed, 5 Jun 2002, Kenny MacPherson wrote: - Can AMANDA on the whole only backup 24GB partitions or is this a tape - limitation in this case? - - I have a /home5 partition on a DELL 4400 running RH7.2 and it's failing - daily! Other partitions do backup okay. The only issue is that I have a - Mammoth-2/EZ17 and even when I snip my disklist down to this directory - alone, it fails to complete a backup. - - It's 55GB and AFAICT the M2 should eat that kind of space up no problem. - It's set for nocomp-high as Exabyte tell me the EZ17 always has hardware - compression on! - - Regards - - Kenny - - -- - Kenny MacPherson - IT Manager - DDI: +44 131 441 9967 - - -Original Message- - From: [EMAIL PROTECTED] - [mailto:[EMAIL PROTECTED]] On Behalf Of Lalo Castro - Sent: 04 June 2002 19:46 - To: [EMAIL PROTECTED] - Subject: Intermittent time-outs - snip - The 24 Gb limit with Amanda has not been hit yet. All clients' - Hard - drives added up is near 21 Gb, with about 40% average of that disk space - - full. Amanda does not do a full dump each time. - snip - - - - Wolfson Microelectronics Ltd. - http://www.wolfsonmicro.com - t: +44 131 272-7000 - f: +44 131 272-7001 - - Registered in Scotland 89839 - - This message may contain confidential or proprietary - information. If you receive this message in error, please - immediately delete it, destroy all copies of it and notify the sender. - You must not use or disclose any part of this message if you are not the - intended recipient. We may monitor all Email communication through our - networks. - - Any views expressed in this message are those of the individual sender, - except where the message states otherwise. - - We take reasonable precautions to ensure our Emails are virus free. - However, we cannot accept responsibility for any virus transmitted by us - and recommend that you subject any incoming Email to your own virus - checking procedures. - - Wolfson Microelectronics Limited is a company - incorporated in Scotland having its Registered Office at - 20 Bernard Terrace, Edinburgh EH8 9NX - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
RE: Amrecover connection refused - again!
Can you telnet to each of thes ports?
$ telent target amandaix (use 'quit' to exit)
$ telnet target amidxtape ('quit' or CR to exit)
If not, reload xinetd and check the messages file for any errors.
Also make sure that ipchains or iptables is not filtering the port.
On Mon, 3 Jun 2002, Rebecca Pakish wrote:
- That's not the file you're looking for. I believe it's
- /etc/xinetd.d/amandaidx that allows amrecover to work remotely.
-
- I don't have that file...I have a file /etc/xinetd.d/amanda that looks like
- this...
- service amanda
- {
- protocol= udp
- socket_type = dgram
- wait= yes
- user= amanda
- group = disk
- groups = yes
- server = /usr/local/libexec/amandad
- }
-
- service amandaidx
- {
- protocol= tcp
- socket_type = stream
- wait= yes
- user= amanda
- group = disk
- groups = yes
- server = /usr/local/libexec/amindexd
- }
-
- service amidxtape
- {
- protocol= tcp
- socket_type = stream
- wait= no
- user= amanda
- group = disk
- groups = yes
- server = /usr/local/libexec/amidxtaped
-
- I get the same error when I try to run amrecover on the amanda server, as
- well, so it's not a remote issue.
-
- You'll also need to make sure that the service is allowed in
- /etc/hosts.allow
- (it's amindexd) on slaw from ants.
-
- I currently don't have anything in /etc/hosts.allow, but I never have, and
- I've run amrecover before. (?) What do I need to add, just a line that says
- amindexd?
-
- rap
-
-
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
RE: Amrecover connection refused - again!
On Mon, 3 Jun 2002, Joshua Baker-LePain wrote:
- On Mon, 3 Jun 2002 at 9:38am, Rebecca Pakish wrote
-
- xinetd based services:
- chargen-udp:off
- chargen:off
- daytime-udp:off
- daytime:off
- echo-udp: off
- echo: off
- time-udp: off
- time: off
- amanda: on
- sgi_fam:on
- finger: off
- rexec: off
- rlogin: off
- rsh:off
- ntalk: off
- talk: off
- telnet: off
- wu-ftpd:off
- rsync: off
-
- There's your problem -- the service isn't running. Maybe an xinetd
- upgrade changed the functionality such that the three services in one
- file method doesn't work any longer. In any case, break your
- /etc/xinetd.d/amanda file into three files -- amanda, amandaidx, and
- amidxtape -- and restart xinetd. All three services should then show up
- in the above output.
I'm not so sure. I have a similar setup -- all three in one file --
and chkconfig reports the same thing to me. However, amrecover works
fine for me.
- Nothing in /etc/hosts.deny...would ipchains really benefit me? I'm blocking
- everything at the firewall, so I don't fell I need to worry about 'who' is
- using my services...
-
- Well, I'm paranoid, so I always set up both ipchains and
- hosts.{allow,deny} fairly tightly. Of course, I'm also in academentia,
- where every host (just about) is connected to the Big Bad Internet.
-
-
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
RE: Amrecover connection refused - again!
On Mon, 3 Jun 2002, Rebecca Pakish wrote:
- Can you telnet to each of thes ports?
-
- $ telent target amandaix (use 'quit' to exit)
-
- [root@slaw etc]# telnet slaw.unterlaw.com amandaidx
- Trying 10.1.7.23...
- telnet: connect to address 10.1.7.23: Connection refused
This is definitly a problem. That connection should not be refused.
This may require the 'shotgun' approach.
Do you have nmap ? Try:
# nmap -sT -p 10082 chena
Just to make sure it is not filtered. Probably not the problem tho...
Do an ldd on /usr/local/libexec/amindexd. JIC. I get somerhing like
this on my Linux server:
$ ldd /usr/local/libexec/amindexd
libm.so.6 = /lib/i686/libm.so.6 (0x4001e000)
libreadline.so.4 = /usr/lib/libreadline.so.4 (0x40041000)
libtermcap.so.2 = /lib/libtermcap.so.2 (0x40067000)
libnsl.so.1 = /lib/libnsl.so.1 (0x4006b000)
libc.so.6 = /lib/i686/libc.so.6 (0x40081000)
/lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000)
Make sure that /usr/local/libexec/amindexd is executable and will
start up. as the amanda user try:
$ /usr/local/libexec/amindexd
You should see somethng like:
amindexd: getpeername: Socket operation on non-socket
This just tests that amindexd will start up.
Try telneting to the port again. Then go to /tmp/amanda and locate
the amindexd.bunchanumbers.debug file. Look in there for a hint.
There are probably lots of these files so be sure to get the right
one. (OR just delete all of them before telnetting :-)
If you are using Linux, look in /var/log/secure to see if xinetd is
erally starting amandidx is.
Can't think of anything else off hand.
- $ telnet target amidxtape ('quit' or CR to exit)
- [root@slaw etc]# telnet slaw.unterlaw.com amidxtape
- Trying 10.1.7.23...
- Connected to slaw.unterlaw.com.
- Escape character is '^]'.
-
- If not, reload xinetd and check the messages file for any errors.
- Also make sure that ipchains or iptables is not filtering the port.
-
- I don't see where they are...
-
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
Re: mtx util
On Wed, 15 May 2002, Anthony A. D. Talltree wrote: - Just curious - anyone using mtx from sourceforge.net? - - I couldn't get it to work on my Solaris 8 / SPARC system 8^( I use v1.2.13 on a Solaris 8 box with no problems. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Question in case of disaster
On Tue, 14 May 2002, Radu Filip wrote: - On Mon, 13 May 2002, Anthony A. D. Talltree wrote: - - There's a lot to be said for printing tape labels or case inserts that - document the contents of each tape -- or for printing each day's results - and keeping them in a binder. - - In my case this cannot be done: I have a mission critical server, with - thousand of small files and there is an ocean between my location and - server location. In case of a disaster I have to be able to restore a huge - directory tree with more than 10,000 files within minutes or hours at - most. With a paper list and tapes that I have to get a visa and fly a day - in order to touch them this is not an option. - - As a workaround, I'm backing up all /var/lib/amanda/my_tapes on a diffrent - machine, but this is just an workaround. This is why I asked if baking up - index itself on the beginning of a tape so Amanda can use it as an - alternative it is planned as a future feature for Amanda, because in cases - when you need to restore everything in shortest time, this is really - usefull. What I am implementing here is a second Amanda tape server. After the backups are done on the primary, I run rsync to syncronoze all of the relavalent directories to the backup machine. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Backing up advice
On Mon, 29 Apr 2002, Chris Mason wrote: - Can anyone point me at some information on setting up a backup schedule, how - to organize tape rotation, etc. I'm planning a tape backup system for a - small business and need to write a HOWTO for them. I use the book _UNIX Backup and Recovery_ by Curtis Preston. It has followed me thru two admin jobs and hasn't failed me yet. www.backupcentral.com is pretty use3ful too. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: AIT libraries
I am using a Spectra-2000 15 tape changer with an AIT-2 drive. I can recommend it with a couple of caveats: 1. So far it has been reliable on Solaris 8 with a SE SCSI card. 2. Spectra and I have so far been unable to get the tape drive working on a Dell 1550 with LVD. On Mon, 22 Apr 2002, Brandon D. Valentine wrote: - This is exciting. My department is seriously looking at investing in a - tape library. I've always wanted one to call my own ;-). So it is with - this happy news that I turn to you, the most helpful group of tape - library owners I am aware of. - - I am seeking recommendations, testimonials if you will, from people - succesfully using AIT libraries with amanda. To aid in this, here's a - bit of background about our current setup and our projected budget - storage goals. - - We currently use a standalone SDX-300C AIT1 tape drive w/ 35GB tapes. - We run a 2week long 10tape Daily backup cycle and a Monthly 10tape - cycle. The Monthly cycle uses skip-incr, record no and chg-manual. - However, we are rapidly accumulating data beyond what I can - realistically do a chg-manual, skip-incr dump on. - - I am interested in AIT libraries in the 15-16 tape size range. Solid - compatibility with amanda is a must. We are looking to spend obviously - as little as possible to get a quality product, but $10k is a very firm - ceiling and the closer to $5k we can hold the price, the more likely it - is to get funded. Rackmount is a must, though I'm not so concerned with - how many RUs it takes up. So far the only products I am really familiar - with are the Sony LIB-152 LIB-162 series. I understand that Overland - Data and several other companies are also making AIT libraries. I'd be - interested to hear about those. Pros/Cons of them versus the Sony ones, - etc. - - My other question is: - Does anyone know how backwards compatible AIT2/AIT3 drives are with AIT1 - tapes? The reason I ask is that if the backwards compatibility is good - I would consider the extra cost of an AIT2 or 3 drive in the library up - front so that if (and when) the capacity of our existing tapes started - to become strained I could spring for the relatively cheap upgrade of a - new round of larger tapes. Those 100GB native capacity AIT3 tapes are - quite sexy. - - Thanks, - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: multiple amdump per day overwrites level0
On 10 Apr 2002, Frederic Saincy wrote: - Hi all, - - in my amanda.conf - ### - dumpcycle 1 weeks - runspercycle 5 - tapecycle 6 tapes - ### - - i ran 7 amdumps today (testing). The first amdump does a level0, and - the last overwrite this unique level0 with a level1. - - This is a bug, a feature or did i miss something ? :) - - I can give more information if needed. - - Thank you and Bye. As I undertand the amanda scheduling algorithm, it does a full for everything to get started and then tries to spread the fulls out over the tapecycle. So, when you hit the seventh amdump, you should have a full of every filesystem on one of tapes 2 thru 6 so tape 1 can hold partials. To list what backups are on what tapes, try: $ amadmin config find $ amadmin config info $ amoverview config -- -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt == Government is like burning witches: After years of burning young women failed to solve any of society's problems, the solution was to burn more young women. ==
RE: amrecover - I have obviously overlooked something
For xinetd use USR2. It causes a hard reload which re-reads the
configuration, and stops any servers which are no longer required.
On Redhat the easist way is
# service xinetd reload
On Fri, 5 Apr 2002, Morse, Richard E. wrote:
- Actually, and perhaps this should be noted somewhere else?, you can do the
- following:
-
- kill -USR1 your-xinetd-pid-here
-
- which should cause it to intelligently reload (ie, don't cut off any already
- existing connections)
-
- HTH,
- Ricky
-
- -Original Message-
- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]]
- Sent: Friday 05 April 2002 12:01 PM
- To: Doug Johnson
- Cc: Amanda-Users (E-mail)
- Subject: RE: amrecover - I have obviously overlooked something
-
-
- On Fri, 5 Apr 2002 at 11:48am, Doug Johnson wrote
-
- I am assuming that I need one of these files for amandaidx
- and amidxtape. Is
- this correct?
-
- Yep. Mine look like:
-
- [jlb@chaos jlb]$ cat /etc/xinetd.d/amandaidx
- # default: off
- #
- # description: Part of the Amanda server package
- service amandaidx
- {
- disable = no
- socket_type = stream
- protocol= tcp
- wait= no
- user= amanda
- server = /usr/local/libexec/amindexd
- }
- [jlb@chaos jlb]$ cat /etc/xinetd.d/amidxtape
- # default: off
- #
- # description: Part of the amanda server package
- #
- service amidxtape
- {
- disable = no
- socket_type = stream
- protocol= tcp
- wait= no
- user= amanda
- server = /usr/local/libexec/amidxtaped
- }
-
- Also note that xinetd needs more than just a HUP to restart
- itself. Just
- do '/etc/init.d/xinetd restart' after adding those files, and
- you'll be
- ready to go.
-
-
- --
- Joshua Baker-LePain
- Department of Biomedical Engineering
- Duke University
-
-
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
Permission _still_ denied
This is getting ridiculous! I cannot even get amanda to do a force full backup on this directory! Every other directory on the partition works fine. Is there some configuration option that can cause the damned sendbackup to try an bind to a low number port? Is that the real problem? Am using amanda version 2.4.3b2. sendbackup: debug 1 pid 30011 ruid 250 euid 250 start time Fri Apr 5 10:27:17 2002 /usr/local/libexec/sendbackup: version 2.4.3b2 sendbackup: got input request: GNUTAR /export/common 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;exclude-list=.exclude; parsed request as: program `GNUTAR' disk `/export/common' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;index;exclude-list=.exclude;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: bind_portrange: port 960: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.59116 sendbackup: bind_portrange: port 960: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.59117 sendbackup: bind_portrange: port 960: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.59118 waiting for connect on 59116, then 59117, then 59118 sendbackup: stream_accept: connection from 192.168.124.25.41442 sendbackup: stream_accept: connection from 192.168.124.25.41443 sendbackup: stream_accept: connection from 192.168.124.25.41444 got all connections sendbackup-gnutar: doing level 0 dump as listed-incremental to /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: spawning /usr/local/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . sendbackup-gnutar: /usr/local/libexec/runtar: pid 30014 sendbackup: started index creator: /bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Permission _still_ denied
On Fri, 5 Apr 2002, Doug Silver wrote: - Hi Stephen - - - At first glance this appears like you might have built the amanda client - stuff with the tcp/udp portrange but not the amanda server. I'm not sure - since I'm using 2.4.2p2, so perhaps with this newer version the debug - messages are different. Does the amanda user have permission to - open up privileged ports (1024 -- I think)? That almost seems the - problem since if that user can't open up a connection on port 960 to - listen, but it can on 59116. I checked the config.status for both machines and I configured amanda --with-user=amanda --with-group=adm. AFAIK, the default is no portrange. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Permission _still_ denied
Okay, I killed all the left over amanda processes and restarted the backup. It works! Thank you! It helps when I know where to look :-) On Fri, 5 Apr 2002, John R. Jackson wrote: - This is getting ridiculous! I cannot even get amanda to do a force - full backup on this directory! ... - - What happens? Do you still get the data timeout? - - That message means the server side of Amanda waited around for half - an hour (unless you changed dtimeout) and didn't hear anything from - the client. That can't be a good thing. - - I also note from your previous debug files that the tar process does not - appear to have completed, which also can't be good. Is it still running - (pid 7742, or 7739, or some child of one of them)? Is it hung in some - bad state? For instance, if it's in 'D' state, that means the kernel - has locked up on that process and it's reboot time (not to mention time - to talk to your OS folks). - - ... Is there some configuration option that can cause the - damned sendbackup to try an bind to a low number port? Is that the - real problem? - - The bind_portrange: port 960: Permission denied is normal -- ignore - it. That same routine (bind_portrange) is used for both privileged and - non-privileged calls. It tries for a privileged port first, complains - that it could not get one (duh) then tries for non-privileged. - - I knew that message would cause trouble when I put it in. Sigh. I've - removed it from 2.4.3. - - -- Stephen Carville - - John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
bind_portrtange: Permission denied
Two days ago, backups for one of the directories on my samba server started failing. Nothing was changed in the amanda configuration and this problem only affects the one directory. Total size of the directory is about 7.5 G. Unfortunately this is a shared drive exported to windows users via samba and suffers 'unintentional' deletions about twice a month. I've included the relevant parts of the e-mail and sendsize, sendbackup and runtar debug files. The only problem I can see : sendbackup: bind_portrange: port 909: Permission denied but this only happens on this one drive. Anyone know why? From email: /-- thames /export/common lev 0 FAILED [data timeout] sendbackup: start [thames:/export/common level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end \ From sendsize.debug: sendsize: calculating for amname '/export/common', dirname '/export/common' sendsize: getting size via gnutar for /export/common level 0 sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . Total bytes written: 7442524160 (6.9GB, 253MB/s) . sendsize: getting size via gnutar for /export/common level 1 sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_1.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . Total bytes written: 130897920 (125MB, 18MB/s) From sendbackup.debug sendbackup: debug 1 pid 7739 ruid 250 euid 250 start time Thu Apr 4 06:04:02 2002 /usr/local/libexec/sendbackup: version 2.4.3b2 sendbackup: got input request: GNUTAR /export/common 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;exclude-list=.exclude; parsed request as: program `GNUTAR' disk `/export/common' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;index;exclude-list=.exclude;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: bind_portrange: port 909: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.57536 sendbackup: bind_portrange: port 909: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.57537 sendbackup: bind_portrange: port 909: Permission denied sendbackup: stream_server: waiting for connection: 0.0.0.0.57538 waiting for connect on 57536, then 57537, then 57538 sendbackup: stream_accept: connection from 192.168.124.25.39935 sendbackup: stream_accept: connection from 192.168.124.25.39936 sendbackup: stream_accept: connection from 192.168.124.25.39937 got all connections sendbackup-gnutar: doing level 0 dump as listed-incremental to /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: spawning /usr/local/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . sendbackup: started index creator: /bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup-gnutar: /usr/local/libexec/runtar: pid 7742 From runtar.debug: runtar: debug 1 pid 7742 ruid 250 euid 0 start time Thu Apr 4 06:04:02 2002 gtar: version 2.4.3b2 running: /bin/gtar: gtar --create --file - --directory /export/common --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/thames_export_common_0.new --sparse --ignore-failed-read --totals --exclude-from /export/common/.exclude . -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Barcode reader
On Mon, 11 Mar 2002, Thomas Hepper wrote: - Hi, - On Fri, Mar 08, 2002 at 11:38:32AM -0800, Stephen Carville wrote: - [..] - In changer.conf set havereader=1 - - Hmm i think it must be - havebarcode 1 - - Which version of chg-scsi do you have. This option works not with 2.4.2 I wrote my own changer script based on chg-zd-mtx. That script uses 'havereader=1' and I just carried it over to my new script. I didn't know there was any other variant. I am using amanda 2.4.2p2. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Barcode reader
On Fri, 8 Mar 2002, Eric Trager wrote: - - Hi all, - - I'm happily using chg-scsi with our StorEdge and backups are going well. - Thanks to you all for helping me sort out a couple of things. - - I've tried to find an answer to this in the archives but to no avail. The - StorEdge we use has a barcode reader, and the tapes are physically - labelled. If I use mtx to check status, I get a nice list of tapes and - barcode entries. - - I have an entry for labelfile in my changer config file, but when I run - the chg-scsi -info command, I get - - 10 20 1 0 - - The fourth entry indicates I have no reader, but I do. How can I tell - amanda and chg-scsi that there's a reader to use? In changer.conf set havereader=1 -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Spectra Logic Treefrog configuration
On Thu, 7 Mar 2002, F.M. Taylor wrote: - - How do I move a tape to the door. Thats the only thing I can't seem to - figure out. On my Spectra Logic (2000) there is no special provision for removing a tape. I just eject the tape (amtape config eject), open the door and remove the tape by hand. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Can you build amanda on one computer and move it to another?
I did something similar for all my Sun boxes. I built amanda in an NFS shared home directory and installed it from there using make install on all of the Solaris boxes. So far it has worked fine. On Tue, 5 Mar 2002, Davidson, Brian wrote: - I have a sun box with all the necessary tools to build amanda (been there, - done that and it works great!). The second sun box does not have the tools - needed. If I edit config.status to change the host name can I build amanda - for the second box? - - Brian Davidson - 11710 Plaza America Drive - Reston, Virginia 20190 - 703.261.4694 - 703.261.5086 Fax -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
AIT2 drive on Linux
This is a little off topic but does anyone know a good source for information on getting an AIT2 SCSI tape drive and changer to work on Linux? I am trying to switch a Spectra 2000 changer to a Redhat 7.2 box and nothing I try seems to work. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Schedule question.....
I have to create both weekly and monthly archives that go offsite. I just use amadmin to force a full backup on the appropiate day. I set whatever tapes were used as no-reuse and, if necessary, add replacements into the rotation. Because the monthly tapes never rotate back in, every so often I go in and remove them from the tapelist by hand. The weekly fulls rotate on a four week cycle so I mark them as reuse when I put them back into the changer magazine. On Tue, 26 Feb 2002, Don Potter wrote: - Okay..I know the virtues of amanda allowing it to do all of the backup - scheduling itself (full and incremental), and I think that it is really - kewl. - - BUT.when your client base is used to 1st of the month full-backups I - have to adjust acordingly (so sayeth the boss man). - - That being said (and trying to apease the group that I support) could I - do the following and obtain that same effect: - - dumpcycle 31 days - runspercycle 31 days (daily backups.weekends included) - tapecycle 31 tapes - - I have a 6 slot tapechanger so I will be changing the tapes at the end - cycle and putting in new tapes. I can do a amadmin Daily force of all - my hosts and filesystems initally and take those tapes out of rotation, - and at the end of the tapecycle (I'm assuming I wouldn't need to do a - amadmin Daily no-reuse since they won't be in the changer at all) and - once the first of the month rolls around do the force again and once - again pull those tapes out of rotation. The level 0 would be out of the - rotation for basically forever. - - Does this sound viable? - - BTW...this is an inital implementation... - - Don - - - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: chg-zd-mtx
On Tue, 19 Feb 2002, Mark Lin wrote: - I'm using mtx in solaris to work with amanda. mtx command to the changer - all works fine. But when I tried it with chg-zd-mtx -info or use it in - changer glue script in amanda.conf then use amcheck, I get the same error - messag: - /usr/local/libexec/chg-zd-mtx: test: argument expected - - can someone help? - I've tried truss in solaris, but I just wasn't worthy to understand its - output. :( FWIW, I had the same problem with chg-zd-mtx. I finally gave up trying to fix it and wrote my own perl script to do the job. I can send you a copy off list if you'd like. It has only been tested on the Spectra 2000 with barcode reader so it may not work with whatever changer you have. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Index problems
tar version 1.13 puts those extra numbers at the start of each entry. These mess up the indexing. Uprade to a later version. I use 1.13.17 and 1.13.19 with no problems. On Wed, 2 Jan 2002 [EMAIL PROTECTED] wrote: - I have the index = yes setup in the conf file - - when i connect i get: - - 220 index/tape_server AMANDA index server (2.4.2p2) ready. - 200 Access OK - Setting restore date to today (2002-01-02) - 200 Working date set to 2002-01-02. - 200 Config set to normal. - 200 Dump host set to dagaz.site.edu. - Can't determine disk and mount point from $CWD - amrecover setdisk /usr/local - Scanning /var/backups/amanda... - 200 Disk set to /usr/local. - No index records for disk for specified date - If date correct, notify system administrator - - - in /var/amanda/index/host/disk/: - - -rw---1 amanda bin 2968629 Jan 2 12:38 20011221_0 - -rw---1 amanda bin258910 Dec 21 16:41 20011221_0.gz - -rw---1 amanda bin 13409 Dec 21 14:39 20011221_1.gz - -rw---1 amanda bin160235 Jan 2 16:33 20020102_1 - -rw---1 amanda bin 15990 Jan 2 15:10 20020102_1.gz - - in 20020102_1 - - (head) - 07414661435/./var/amanda/gnutar-lists/dagaz.lib.unomaha.edu_usr_local_1 - 07414664217/./amanda-2.4.2p2/amplot/amcat.awk - 07414664217/./amanda-2.4.2p2/amplot/amcat.awk.in - 07414664217/./amanda-2.4.2p2/amplot/amplot.awk - 07414664217/./amanda-2.4.2p2/amplot/amplot.g - 07414664217/./amanda-2.4.2p2/amplot/amplot.sh - 07414664217/./amanda-2.4.2p2/amplot/amplot.sh.in - 07414664217/./amanda-2.4.2p2/amplot/Makefile - 07414664217/./amanda-2.4.2p2/amplot/Makefile.am - 07414664217/./amanda-2.4.2p2/amplot/Makefile.in - - - so it looks like all the info is there but the server is not reading them - ?? - - btw - server tar (GNU tar) 1.13.19 - client tar (GNU tar) 1.13 - - thanks - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: amcheck works with inetd, fails with xinetd
On Thu, 14 Feb 2002, Jeff Stewart wrote:
- Apologies if this has been asked before. I've searched google and the list
- archives and have not found an answer that works for me.
- On a SuSE 7.3 box, amcheck is working fine when I run inetd, but is failing
- when I run xinetd. I'm getting everybody's favorite error: selfcheck request
- timed out.
- Since it is working with inetd but not with xinetd, it should be a problem
- with xinetd.conf, right? I am not getting any errors in /var/log/messages,
- and debug files are being created in /tmp/amanda.
- I definitely need this working with xinetd instead of inted.
- Thanks,
- Jeff Stewart
Dunno if this matters but I set the user on all three services to
'amanda'. Also you do not have amidxtape in /etc/services and no port
specified in xinetd.conf.
Maybe add an explicit 'disable = no' ? AFAIK this is the default but
maybe SUSE changed that.
- inetd.conf is:
- amandaidx stream tcp nowait root /usr/lib/amanda/amindexd amindexd
- amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped amidxtaped
- amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad
-
- xinetd.conf is:
- defaults
- {
- log_type= FILE /var/log/xinetd.log
- log_on_success = HOST EXIT DURATION
- log_on_failure = HOST ATTEMPT RECORD
- instances = 2
- }
- service amandaidx
- {
- socket_type = stream
- protocol= tcp
- wait= no
- user= root
- server = /usr/lib/amanda/amindexd
- }
- service amidxtape
- {
- socket_type = stream
- protocol= tcp
- wait= no
- user= root
- server = /usr/lib/amanda/amidxtaped
- }
- service amanda
- {
- socket_type = dgram
- protocol= udp
- wait= yes
- user= amanda
- server = /usr/lib/amanda/amandad
- }
-
- /etc/services is:
- amanda 10080/tcp
- amanda 10080/udp
- amandaidx 10082/tcp
-
-
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
Missing Tape has Backups Screwed
One of my tapes did not come back from offsite in time for today's backup (Some winidiot sent if off for four weeks instead of one) so today's backup failed. How can I get amanda to just skip that tape and go on to the next one in the sequence? When I try amcheck, amanda thinks all of the tapes in the changer are active tapes and will not write to them. Even if I load the next tape in the sequence mnaually, amcheck rejects it. How can I tell which tapes it will write too? dumpcycle 7 days runspercycle 5 tapecycle 15 tapes runtapes 2 So far, backups have only needed one tape per run so it seems to me that tapes from two weeks ago should no longer be active but amanda thinks they are. -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
RE: Missing Tape has Backups Screwed
On Fri, 8 Feb 2002, Bort, Paul wrote: - amadmin YOURCONFIG no-reuse MISSINGTAPE - - Then use the next tape in sequence. - - Just remember to mark it 'reuse' before it is next scheduled. Didn't work. $ amadmin daily1 tape The next Amanda run should go onto tape C83173 or a new tape. The next Amanda run should go onto tape C83174 or a new tape. $ amadmin daily1 no-reuse C83173 amadmin: marking tape C83173 as not reusable. $ amtape daily1 label C83174 amtape: scanning for tape with label C83174 amtape: slot 9: date 20020121 label C83174 (exact label match) amtape: label C83174 is now loaded. amdump reports *** A TAPE ERROR OCCURRED: [new tape not found in rack]. When I try 'amcheck daily1' it reports that _all_ the tapes are active. Even tapes that 'amtape daily1 info' says are not part of the current backup. -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
RE: Missing Tape has Backups Screwed
On Fri, 8 Feb 2002, Bort, Paul wrote: - Oops. Do you have runtapes 2 ? I think you would have to mark all of the - tapes that are in this run as no-reuse to get it to cycle around. - - Do you have runtapes * runspercycle = tapecycle? (ie, runtapes=2, - runspercycle=5, tapecycle=10 or something like that?) I should have been - more explicit about there needing to be spare tapes in the rotation for - no-reuse to do what you would expect. - - From what I've seen on the list, it's a good idea to have tapecycle - runtapes*runspercycle, for just this reason. You can temporarily pull a tape - from the rotation without confusing AMANDA. (For example, I have runtapes=1, - runspercycle=5, tapecycle=30, so I have six complete backup sets, one for - each of the last six weeks. I picked those numbers based on the number of - tape magazines I had for my changer.) - - Good Luck. Decreasing tapecycle from 15 to 10 did the trick. Thanks -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Monthly-type backup
On 27 Jan 2002, Dan Smith wrote:
- I want to (once a month) do a backup of all disks. My tapes are not
- large enough to fit the whole thing, so I need to spread it across 3
- tapes or so. I was thinking of setting up a 1-day dumpcycle with 3
- runspercycle and just do all three dumps on a saturday. I don't think
- this is the best way to do it, since anything that has changed between
- dumps will be backed up incremental to the 2nd or third run.
-
- Is there any way to do this elegantly? I was thinking I could also
- setup 3 jobs and spread the disks out among them, but that would be
- more work, and I'd like for amanda to organize the dumps so they best
- fill out each tape.
-
- Does anyone have any advice?
In amanda.conf define:
define dumptype always-full {
global
compress none
priority high
dumpcycle 0
}
Then in disklist put something like:
server /volume {
always-full
}
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
Re: Who uses Amanda?
On Fri, 25 Jan 2002, KEVIN ZEMBOWER wrote: - (This might seem like a stupid question to this group, but) I'm being - challenged by the folks who can't get my firewall setup to work with - Amanda that I should adopt a more industry-standard backup product. - Hogwash. But, I would like to at least offer an answer. - - Anyone have any guesses how many institutions and individuals are using - amanda? - - Anyone know, or want to self-disclose, some noteworthy institutions - using amanda? If you think this would clog up the list too badly, email - me privately at [EMAIL PROTECTED], and after a week or so, I'll - compile a list and post it to the email list. I have no idea if Ace USA is noteworthy be we use Amanda to backup Oracle servers, Web servers, Samba servers and several development machines. Total data written to tape in a cycle is about 200 Gig. I originally picked it because the difference between the price of Amanda (free) and BackupExec licenses ($$$) paid for the 15 tape changers with a barcode reader. Now that I've been using it for a few months, I've discovered it is faster and more effecient of tape usage than BackupExec. The windows admin is actually jealous :-) What firewall problems are you having? -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Amrecover still kicking my @$$
A while back I think someone have a similar problem that ended up being in his rhosts file. Perhaps you could look there. On Tue, 15 Jan 2002, Eric Hillman wrote: - On Tuesday 15 January 2002 12:13 pm, you wrote: - Looks to me like xinetd is working correctly. If xinetd was refusing - the connection you wolkd never see the 220 prompt. - - Some sugesstions: - - 1. Does amandahome/.amandahosts on the tape server have a line like: - - localhostroot - my.serverroot - - Yes, and then some. I've added root and operator lines for every - conceivable valid address for the system. (operator is the dumpuser, and - also the user that the amanda services run as under xinetd.) - - 2. It may be necessary to add the server name to /etc/hosts. - - We use DNS instead of hosts, but, regardless, it's in hosts as well, with the - same name that DNS reports. - - 3. Try - - # amrecover -s localhost -t localhost -C config - - Tried that too, same error message. - - When setting this up originally, I went through hell moving, renaming, - chowning and chmodding files, as a number of things weren't readable by the - operator user or were in the wrong place. (In fact, - /var/lib/amanda/config and /etc/amanda/config are now the same directory, - symlinked.) Is there any chance my thrashing about has screwed up some vital - file there that could trigger this error? 'lsof' tells me nothing - particularly useful, although I did learn that amindexd is writing debug logs: - - amindexd: debug 1 pid 2586 ruid 11 euid 11 start time Tue Jan 15 13:44:32 2002 - amindexd: version 2.4.1p1 - 220 [server] AMANDA index server (2.4.1p1) ready. - ÿôÿý - 500 Access not allowed - 200 Good bye. - amindexd: pid 2586 finish time Tue Jan 15 13:44:45 2002 - - Not very helpful to me. Is there any way to ratchet up the debug level? - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Amrecover has defeated me.
Looks to me like xinetd is working correctly. If xinetd was refusing the connection you wolkd never see the 220 prompt. Some sugesstions: 1. Does amandahome/.amandahosts on the tape server have a line like: localhostroot my.serverroot 2. It may be necessary to add the server name to /etc/hosts. 3. Try # amrecover -s localhost -t localhost -C config On Tue, 15 Jan 2002, Eric Hillman wrote: - - And yes, I have read the FAQ. - - On my RedHat 7 server, Amrecover invariably dies with an Unexpected server - end of file error. All other amanda functions (amdump, acheck, alabel) work - great. I have the sneaking suspicion that xinetd is somehow to blame, mainly - because of this error message which shows up in /var/log/messages whenever I - run amrecover: - - Jan 15 11:05:25 www xinetd[27241]: refused connect from 206.101.101.101 - - (I changed the IP address, but it is the eth0 address, despite the fact that - I'm using 'amrecover -s localhost') - - but... /etc/hosts.allow is set up to allow access from my own host and every - conceivable alias or variation thereof. Ditto for .amandahosts. And - telnetting directly to the ports seems to work. I can even get an amandaidx - session going, after a fashion (the line in ALL CAPS is my input): - - [root@penguin tmp]# telnet localhost 10082 - Trying 127.0.0.1... - Connected to localhost.localdomain (127.0.0.1). - Escape character is '^]'. - 220 penguin AMANDA index server (2.4.1p1) ready. - I CANT SPEAK YOUR CRAZY MOON LANGUAGE - 500 Access not allowed - 200 Good bye. - Connection closed by foreign host. - - Any suggestions on what I'm missing, or how I can track down why this is - happening? - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: S.O.S.
runtapes 2 You have to have a working changer configuration. On Fri, 11 Jan 2002, [iso-8859-15] Túlio Machado de Faria wrote: - Help me, please. - - - I need to use amanda with two units of tape in one backup. - - How? - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Finding tapes
Try amadmin config find This prints out date, host, disk, level, tape, and status for everything in config. On Fri, 11 Jan 2002, Paul Lussier wrote: - - Hi all, - - I've been asked to locate a set up tapes based on dates. Any idea - how I do this? Basically I just need to search the date stamps for - each tape and tell my boss which tapes contain backups for the - specified period of time. - - I looked at the amadmin command, but the sub-commands all seem to - want a hostname. I need the information for *all* systems. - - Basically, if the tape was written to during the specified range, I - need to know. - - Any ideas? - - Thanks, - - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: runspercycle vs. dumpcycle
On Thu, 10 Jan 2002, Benjamin Gross wrote: - One last question, is there anyway to actually know that out of a - tape cycle of 20 tapes, tape x - tape y contains a complete backup - for all your hosts ? I suppose keeping track of when the - dumpcycle starts, and when it ends, and what tapes were used would - be the only way to know. Try: amoverview config. It tells you what level backup was done on what date. amadmin config info server. It give you quite a bit of information about what backup levels were done to what tape on what date. -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: tapechanger advice
I use a Spectra 2000 with a single AIT2 drive and barcode reader attached to a Tatung Ultra 2, Solaris 8 box. None of the tape changer scripts worked with it so I wrote a perl script that works with the changer and mtx just fine. I have been using it for a few months and, so far, it has been solid as a rock. On Tue, 8 Jan 2002, Matthew Boeckman wrote: - Hello all, I am running amanda currently on a DLT1 single-tape drive and - loving it. I'm looking at aquiring a tape changer/carousel for a - different site that will house about 15 tapes in rotation. Ideally, this - will hang off of an ultra5 running Solaris8. I've looked at Overland, - and Quantum, and did a bit of reading in the archives for them as well. - My question to the list is: any recommendations on a rock-solid tape - changer that holds somewhere between 12-18 tapes, that plays well with - Sun/Solaris8 and amanda? - - It certainly seems from both my experience and reading this list that - most anything I get will work, but I'd like to avoid 36 hours of - interoperability issues if possible. Any and all advice appreciated. Thanks! - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
cruft directory
Whenever I use amoverview I get the following: $ amoverview daily1 bad date oracle-b: in oracle-b: skipping cruft directory, perhaps you should delete it. bad date oracle-a: in oracle-a: skipping cruft directory, perhaps you should delete it. bad date oracle-w: in oracle-w: skipping cruft directory, perhaps you should delete it. etc... Not a big deal but I'd like to know what these cruft directories are. -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: cruft directory
On Fri, 4 Jan 2002, Jean-Louis Martineau wrote: - On Fri, Jan 04, 2002 at 10:58:47AM -0800, Stephen Carville wrote: - Whenever I use amoverview I get the following: - - $ amoverview daily1 - bad date oracle-b: in oracle-b: skipping cruft directory, perhaps you - should delete it. - bad date oracle-a: in oracle-a: skipping cruft directory, perhaps you - should delete it. - bad date oracle-w: in oracle-w: skipping cruft directory, perhaps you - should delete it. - - etc... - - Not a big deal but I'd like to know what these cruft directories - are. - - That's an output of 'amadmin config find' it doesn't understand. - Could you try this patch. - - Anyway, you should not have those directory (oracle-a, ...) in - your holding disk directory. ? If I delete any one of those directories then amdump for that configurarion fails with an error: ERROR: log dir /flood/amanda/oracle-a: not writable Are you saying I should _not_ create these directories? -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: cruft directory
OK, I think I got it now :-) My logdir and my holdingdisk were the same. On Fri, 4 Jan 2002, Jean-Louis Martineau wrote: - On Fri, Jan 04, 2002 at 10:58:47AM -0800, Stephen Carville wrote: - Whenever I use amoverview I get the following: - - $ amoverview daily1 - bad date oracle-b: in oracle-b: skipping cruft directory, perhaps you - should delete it. - bad date oracle-a: in oracle-a: skipping cruft directory, perhaps you - should delete it. - bad date oracle-w: in oracle-w: skipping cruft directory, perhaps you - should delete it. - - etc... - - Not a big deal but I'd like to know what these cruft directories - are. - - That's an output of 'amadmin config find' it doesn't understand. - Could you try this patch. - - Anyway, you should not have those directory (oracle-a, ...) in - your holding disk directory. - - Jean-Louis - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Index problems
tar version 1.13 puts those extra numbers at the start of each entry. These mess up the indexing. Uprade to a later version. I use 1.13.17 and 1.13.19 with no problems. On Wed, 2 Jan 2002 [EMAIL PROTECTED] wrote: - I have the index = yes setup in the conf file - - when i connect i get: - - 220 index/tape_server AMANDA index server (2.4.2p2) ready. - 200 Access OK - Setting restore date to today (2002-01-02) - 200 Working date set to 2002-01-02. - 200 Config set to normal. - 200 Dump host set to dagaz.site.edu. - Can't determine disk and mount point from $CWD - amrecover setdisk /usr/local - Scanning /var/backups/amanda... - 200 Disk set to /usr/local. - No index records for disk for specified date - If date correct, notify system administrator - - - in /var/amanda/index/host/disk/: - - -rw---1 amanda bin 2968629 Jan 2 12:38 20011221_0 - -rw---1 amanda bin258910 Dec 21 16:41 20011221_0.gz - -rw---1 amanda bin 13409 Dec 21 14:39 20011221_1.gz - -rw---1 amanda bin160235 Jan 2 16:33 20020102_1 - -rw---1 amanda bin 15990 Jan 2 15:10 20020102_1.gz - - in 20020102_1 - - (head) - 07414661435/./var/amanda/gnutar-lists/dagaz.lib.unomaha.edu_usr_local_1 - 07414664217/./amanda-2.4.2p2/amplot/amcat.awk - 07414664217/./amanda-2.4.2p2/amplot/amcat.awk.in - 07414664217/./amanda-2.4.2p2/amplot/amplot.awk - 07414664217/./amanda-2.4.2p2/amplot/amplot.g - 07414664217/./amanda-2.4.2p2/amplot/amplot.sh - 07414664217/./amanda-2.4.2p2/amplot/amplot.sh.in - 07414664217/./amanda-2.4.2p2/amplot/Makefile - 07414664217/./amanda-2.4.2p2/amplot/Makefile.am - 07414664217/./amanda-2.4.2p2/amplot/Makefile.in - - - so it looks like all the info is there but the server is not reading them - ?? - - btw - server tar (GNU tar) 1.13.19 - client tar (GNU tar) 1.13 - - thanks - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Newbie: Can't get amanda user to work
Try changing .amandahosts on the client (which appears to be the same as the server in this case) to: admin amanda On Mon, 10 Dec 2001, KEVIN ZEMBOWER wrote: - I'm trying to get my first setup of amanda working. Running amcheck - gives me: - admin:/home/amanda # su amanda -c /usr/local/sbin/amcheck DailySet1 - Amanda Tape Server Host Check - - - Holding disk /var/amanda: 5807968 KB disk space available, that's - plenty - NOTE: skipping tape-writable test - Tape DailySet101 label ok - NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sdb1: does not - exist - NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda1: does not - exist - NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda3: does not - exist - Server check took 16.516 seconds - - Amanda Backup Client Hosts Check - - ERROR: admin: [access as amanda not allowed from - [EMAIL PROTECTED]] amandahostsauth failed - Client check: 1 host checked in 0.029 seconds, 1 problem found - - (brought to you by Amanda 2.4.3b1) - admin:/home/amanda # - - Yet, I have a .amandahosts file with what I think are the proper - contents and permissions: - admin:/home/amanda # ll /home/amanda/.amandahosts - -rw-r--r--1 amanda disk 30 Dec 10 16:36 - /home/amanda/.amandahosts - admin:/home/amanda # cat /home/amanda/.amandahosts - admin [EMAIL PROTECTED] - admin:/home/amanda # - - I'm stumped. I've tried or checked all the suggestions in the - FAQ-a-matic for this topic. It's probably something simple, that I don't - see because I'm new to amanda. Any suggestions? - - Thanks for your help. - - -Kevin Zembower - - - - E. Kevin Zembower - Unix Administrator - Johns Hopkins University/Center for Communications Programs - 111 Market Place, Suite 310 - Baltimore, MD 21202 - 410-659-6139 - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Redundancy in Amanda
My boss just asked me about redundancy in amanda. I explainmed to him how the software distributes the full backups over the runspercycle in an attempt to equalize the tape usage on each day's backup. He asked me if a tape were lost or damaged how much of the data could be restored? I don't really have answer to that one. Right now I have setup: dumpcycle 7 days tapecycle 15 runspercycle5 runtapes2 Backups usually take one tape. Is there any way I can estimate just how much data would be lost if any one tape were unavailable or unreadable? -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: AMRECOVER help!!
On Mon, 3 Dec 2001, Joseph Myers wrote:
- I have successfully completed a backup but am now trying to figure out the
- recover portion of the AMANDA program. Afterall, what good is a backup if
- you can't recover it. Here is my dilemna. I have two computers on a
- network.. Alpha1 and Intelraid1. Intelraid1 is the server and Alpha1 is
- the client so I'm trying to run amrecover on Alpha1 obviously. Here is the
- command I'm running followed by the output
-
- root@alpha1 /]# amrecover -C alpha1 -s intelraid1 -t intelraid1 -d
- /RAID/alpha1
- AMRECOVER Version 2.4.2p2. Contacting server on intelraid1 ...
- 220 intelraid1 AMANDA index server (2.4.2p2) ready.
- 200 Access OK
- Setting restore date to today (2001-12-03)
- 200 Working date set to 2001-12-03.
- 200 Config set to alpha1.
- 200 Dump host set to alpha1.xxx.xxx
- Can't determine disk and mount point from $CWD
- amrecover setdisk /dev/sda3
- Scanning /RAID/alpha1...
- 20011121: found Amanda directory.
- 200 Disk set to /dev/sda3.
- No index records for disk for specified date
- If date correct, notify system administrator
- amrecover setdisk /dev/sda3
- Scanning /RAID/alpha1...
- 20011121: found Amanda directory.
- 200 Disk set to /dev/sda3.
- No index records for disk for specified date
- If date correct, notify system administrator
-
- Ok.. here is the directory listing of /RAID/alpha1 on intelraid1:
-
- drwx--2 amanda amanda 4096 Dec 3 10:58 20011121
-
- And inside 20011121/ :
- -rw---1 amanda amanda 3925999616 Nov 21 11:12
- 192.168.1.3._dev_sda3.0
-
- obviously, I just did a dump onto the holding disk here because we have 100
- GB of RAID space to utilize so a tape drive just seems pointless. I'm
- pretty sure indexing is off, I don't know how to turn it on at least. My
- indexdir in my amanda.conf file is set to /usr/local/etc/amanda/alpha1.
- Can someone just tell me either (1) how to get this to work like it should
- or (2) how to use amrestore properly to get this to work? It's not
- imperative that I use this backup archive. The computer still works great
- and everything. I just need to make sure I can recover the files properly
- so if I have to turn on indexing or create another dump.. it's not a
- problem at all. Thanks for any help.
What I so is add indexing to my global dumptype and reference that in
sucessive dumptypes:
define dumptype global {
comment Global definitions
index yes
}
define dumptype user-tar {
global
program GNUTAR
compress none
priority medium
}
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
Re: Excludes not working
Putting a dot (.) in front of the directory names did the trick. Thanks to everyone who answered. On Tue, 4 Dec 2001, Stephen Carville wrote: -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Excludes not working
Redhat 7.0 w/tar 1.13.17 Solaris 8 w/tar 1.13.19 amanda 2.4.2p2 I have an exclude list that looks like: /proc /devices /tmp /temp /var/lock /var/spool/postfix/private /spool/postfix/private /var/tmp /lost+found *..LCK But amrecover tells me that amanda is still backing up these directories. For example: amrecover cd tmp /tmp amrecover ls 2001-12-03 . 2001-12-03 .font-unix/ 2001-12-03 amanda/ 2001-12-03 ssh-hHR25341/ From / the command: tar -cvl -X .exclude -f /dev/null . Indicates that /tmp being excluded up but amanda _is_ backing it up. So how the frell do I get these directories excluded for real? -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: amrecover: No index records for host?
This one burned me too :-) Update tar to at least 1.13.17. I've found that 1.13.17 and 1.13.19 both work On Mon, 3 Dec 2001, Rafe Thayer wrote: - Hi Folks, - Another question for ya. After I did an amdump to test out dumping our - disks to tape, I tried to do an amrecover to see if restoring the data - would work. It seems to work for our linux machines, but the solaris box - has some trouble. When I start up amrecover, it reports: - ... - 200 Config set to imash. - 501 No index records for host: hostname. Invalid? - Trying hostname.domainname... - 200 Dump host set to hostname.domainname - ... - - - Then I do a setdisk /etc and it reports: - - 200 Disk set to /etc. - No index records for disk for specified date - If date correct, notify system administrator - - So I figured that the index must not have been created for some reason, - but I checked that out on the server and it looks fine. Has the right - permissions and ownership. The wierd thing is, if I look into the index - files for the host that's giving me trouble, they look a little different - than the others. It looks like this: - - 06573011000/./security/dev/audio - 06573011000/./security/dev/fd0 - 06573011000/./security/dev/sr0 - 06573011000/./security/dev/st0 - 06573011000/./security/dev/st1 - ... - - Whereas for the linux hosts, the index looks like this: - - / - /CORBA/ - /CORBA/servers/ - /X11/ - ... - - (these are just the contents of /etc on each host). The version of tar on - the solaris machine is 1.13. I've heard tar can cause some problems. Do - you think that might be it? - - Thanks for your help! - - Rafe - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: Which Files get Backed Up?
On Wed, 21 Nov 2001, Dietmar Goldbeck wrote:
- On Tue, Nov 20, 2001 at 01:31:39PM -0800, Stephen Carville wrote:
- If I have an entry in disklist like:
-
- congo / {
- user-tar
- exclude list .exclude
- }
-
- Does this backup the entire root file system including any mounted
- partitions or just the root partition?
-
-
- Just the root file system. Amanda never goes into mounted filesystems.
-
- You have to maintain the disklist so that every filesystem is listed.
Good. That is the way I want it to be. Thanks for the information.
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
Which Files get Backed Up?
If I have an entry in disklist like:
congo / {
user-tar
exclude list .exclude
}
Does this backup the entire root file system including any mounted
partitions or just the root partition?
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
