version 2.4.2 and NT
Since now we have installed Amanda 2.4.1p1 which doesn't support exclude lists in Samba backups. Because I thought the current version 2.4.2 does we've downloaded it. But after reading the docs I coudn't find any hint in there. Just to be sure once again the question: does version 2.4.2 support file exclusion on NT clients? Thanx Alex
Re: GNU-Tar vs dump/restore ...
Hrmmm ... could you set this on a directory and have it ignore all
files/directories under that directory too? And, the
--with-dump-onor-nodump option .. is that enabled on client or server, or
both?
Thanks ...
On 2 Jan 2001, Greg Troxel wrote:
With BSD dump on 4.4BSD-derived systems, one can set the nodump flag
(see chflags(1)). Then, one can compile amanda with
--with-dump-honor-nodump, and the nodump flag will be honored even for
level 0 - normally it is honored only for 1 and up (see dump(8)).
(FreeBSD man pages can be read at http://www.freebsd.org/)
For example:
$ ls -lo sendbackup.debug sendsize.debug
-rw--- 1 amanda operator - 717 Jan 2 01:46 sendbackup.debug
-rw--- 1 amanda operator - 6544 Jan 2 01:13 sendsize.debug
$ chflags nodump sendsize.debug
$ ls -lo sendbackup.debug sendsize.debug
-rw--- 1 amanda operator - 717 Jan 2 01:46 sendbackup.debug
-rw--- 1 amanda operator nodump 6544 Jan 2 01:13 sendsize.debug
I use this feature regularly on FreeBSD and NetBSD to avoid backing up
build trees, stuff I've checked out from anoncvs, etc.
Greg Troxel [EMAIL PROTECTED]
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
Re: GNU-Tar vs dump/restore ...
A quick perusal of the documentation (src/sbin/dump/traverse.c)
indicates that dump walks the inode list and performs the nodump flag
check on each file individually.
grep HAVE_HONOR */*.c
client-src/sendbackup-dump.c:#ifdef HAVE_HONOR_NODUMP
client-src/sendbackup-dump.c:#ifdef HAVE_HONOR_NODUMP
client-src/sendsize.c:# ifdef HAVE_HONOR_NODUMP /* {
*/
client-src/sendsize.c:# ifdef HAVE_HONOR_NODUMP /* {
*/
client-src/sendsize.c:#ifdef HAVE_HONOR_NODUMP
It appears to be the client that uses this flag.
Note that 'chflags -R nodump foo' works well. While kludgy, running a
cron job before amanda would probably work.
AMFLUSH
I have a problem. Because of the newyear I was not in to flip tapes on monday
night. Like a good girl Amanda dumped to the holding disk just fine. When I
got in this morning I grabbed my tapes and ran amflush.
Needless to say, it was a good newyear so I'm not all there right now. I
put in tape 10 in our rotation, while amadmin was expecting tape 9. It
said "Expecting tape 9 or new tape". It then said "do you want to flush
these images to tape?" I answered yes. It then happily overwrote tape
10. I know amanda checks for this, it doesn't overwrite tapes. Did it get
confused because tape 10 was the tape that it would dump to this evening
normally? Any ideas?
On Tue, Jan 02, 2001 at 09:09:53AM -0500, [EMAIL PROTECTED] wrote:
The dumps were flushed to tape DSL-010.
Tonight's dumps should go onto 1 tape: DSL-009.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:50
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:49 0:30 0:19
Tape Size (meg) 11289.7 6850.3 4439.4
Tape Used (%) 19.1 11.57.6 (level:#disks ...)
Filesystems Taped86 22 64 (1:64)
Avg Tp Write Rate (k/s) 3933.4 3924.0 3948.0
NOTES:
taper: tape DSL-010 kb 11560640 fm 86 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
bkup01.hvn01 / 0 107180 107232 --N/A N/A0:264126.0
bkup01.hvn01 /boot 0 11702 11744 --N/A N/A0:043070.3
bkup01.hvn01 /usr0 495378 495424 --N/A N/A1:365173.2
bkup01.hvn01 /usr/local 0 386180 386240 --N/A N/A2:172824.3
bkup01.hvn01 /var0 10735 10784 --N/A N/A0:033847.8
. . .
winterbrew.d /boot 1 19 64 --N/A N/A0:01 81.2
winterbrew.d /usr1 306352 --N/A N/A0:01 435.4
winterbrew.d /usr/local 1 51 96 --N/A N/A0:01 129.0
winterbrew.d /var0 10033 10080 --N/A N/A0:033684.3
(brought to you by Amanda version 2.4.2-19991216-beta1)
--
Joshua Warchol
UNIX Systems Administrator
DSL.net
updated mtx script?
Someone was going to release an updated mtx script on the list...did I miss it? Thanks, Mike
nasty % bug during backup
Hello...
I setup amanda this past week. I had several questions, all of which
were answered by looking at the list archives. Thanks to all. Amanda
RULES!
I did run into a bug though. While I was doing test backups this is what
happened:
All scsi drives
DLT-8000 tape drive
using dump ( not tar)
Redhat linux (6.2)
mt-st-0.6
dump-0.4b20
amanda-2.4.2
mtx-1.2.11-pre1
holdingdisk hd1 {
comment "main holding disk"
directory "/var/spool/amanda"
use -512 Mb # how much space can we use on it
# a negative value mean:
#use all space except that value
chunksize 512Mb # size of chunk if you want big dump to be
This disk is a 18 gig scsi drive. At the time of this test ~8 gigs was
used elsewhere. So I had ~10 gigs free for amanda usage (10.5 gigs -
0.5 from holdingdisk). My disklist looked something like:
server1 /boot my-type
server1 / my-type
server1 /large my-type
...
server9 / my-type
server9 /var/spool my-type
All the small partitions went first and taped fine. The rest of the
larger partitions taped fine. Then the last two. Two ~20 gig
partitions with ~10 gigs used. The amstatus showed an estimate size of
9.9 gigs for boths these partitions. (The linux dump has a bug in the
size extimate). All the previous sessions ended up showing usage of
102% - 120%. The last two backups would fail and start over,
ping-ponging back and forth. It went something like this:
amanda-
I am backing up server3 /large with size estimate of 9.9gigs
I have 10gigs free on the holding disk - save to disk
0%..10%...(backing up to disk)...100%...110%...
out of usable disk space -- fail
Go to next disklist entry
I am backing up server4 /large with size estimate of 9.9gigs
I have 10gigs free on the holding disk - save to disk
0%..10%...(backing up to disk)...100%...110%...
out of usable disk space -- fail
Go to next disklist entry
( back to server6 and loop forever)
I saw this happen so I freed up more space on the holding disk. And it
kept happening even though 15 gigs were now free. The last two sessions
ping-ponged back and forth failing each time.
Maybe something like this could be added:
psuedo code
if (Out of usable disk space) {
happend before issue warning backup straight to tape
re-check disk to see if there is more space available
yes continue
} else {
mark this session as needing ESTIMATE * 1.2 free disk space
or ESTIMATE = CURRENTLY_USED * 1.2
issue warning
try again
}
I think the whole problem comes from using the estimated size as a hard
number. And the current linux dump ( from sourceforge ), at least on my
servers, under reports disk usage. I am backing up 28 partitions and
every one of them shows 102% - 120% backed up.
Thanks to the developers. Amanda Rules!
--
Christopher McCrory
"The guy that keeps the servers running"
[EMAIL PROTECTED]
http://www.pricegrabber.com
"Linux: Because rebooting is for adding new hardware"
Re: AMFLUSH
Joshua E Warchol [EMAIL PROTECTED] writes: Needless to say, it was a good newyear so I'm not all there right now. I put in tape 10 in our rotation, while amadmin was expecting tape 9. It said "Expecting tape 9 or new tape". It then said "do you want to flush these images to tape?" I answered yes. It then happily overwrote tape 10. I know amanda checks for this, it doesn't overwrite tapes. Did it get confused because tape 10 was the tape that it would dump to this evening normally? Any ideas? Amanda just asks for the next tape in the tapelist. Other tapes will work just as well as long as they don't contain "essential" data required for a restore. If tape 10 contained backups necessary for a restore Amanda wouldn't have overwritten it. At least this is how I understand the mechanism. /Jens -- Jens Bech Madsen The Stibo Group, Denmark
Re: nasty % bug during backup
Hi Christopher,
On Tue, Jan 02, 2001 at 07:19:32AM -0800, Christopher McCrory wrote:
All the small partitions went first and taped fine. The rest of the
larger partitions taped fine. Then the last two. Two ~20 gig
partitions with ~10 gigs used. The amstatus showed an estimate size of
9.9 gigs for boths these partitions. (The linux dump has a bug in the
size extimate). All the previous sessions ended up showing usage of
102% - 120%. The last two backups would fail and start over,
ping-ponging back and forth. It went something like this:
Could you try this patch on the server.
Send me (privately) your amdump.1 log file if
the patch doesn't fix the bug.
Jean-Louis
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
--- server-src/driver.c.origTue Dec 19 10:25:37 2000
+++ server-src/driver.c Sat Dec 23 15:37:01 2000
@@ -821,11 +821,17 @@
if( busy_dumpers == 1 ) { /* case c */
assignedhd_t **holdp;
int i;
+ long est_size;
/* set estimate to more than what is already use */
- sched(dp)-est_size = 20 * TAPE_BLOCK_SIZE;
+ est_size = 20 * TAPE_BLOCK_SIZE;
holdp = sched(dp)-holdp;
for(i=0; holdp[i]; i++ ) { /* for each disk */
- sched(dp)-est_size += holdp[i]-used;
+ est_size += holdp[i]-used;
+ }
+ fprintf(stderr,"est_size: %ld %ld\n",est_size,sched(dp)-est_size);
+ if(est_size sched(dp)-est_size) {
+ fprintf(stderr,"Should not be executed\n");
+ sched(dp)-est_size = est_size;
}
}
/* case b */
Re: Files after AMFLUSH
On Tue, Jan 02, 2001 at 08:29:43AM -0800, Wang Chen wrote: Hi, Amanda did not finish for a unknow reason on Dec.29,and I did amflush in the same day afternoon. After it done, I found a .tmp file left on holding dir. On Dec. 30, the backup did not get done either. There was also a same .tmp file left on the ~/20001230 dir of holding disk. I guess I may need to change " runtapes 1" to "runtapes 2" since our file image may too big to be taped by on tape. But can I delete the .tmp file on holding disk. Thanks in advance. The .tmp file can be removed, they are not completed dump. Did you kill some process? That's the only reason why they could be left there. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Wrong tape / amdump question
Hi, how do I get Amanda to dump the filesystems to holding disk if it finds the wrong tape in the drive (which I can manually flush them to tape at a later time)? I am running Amanda 2.4.2 on RH6.1 (2.2.18). The dumps work fine when the 'proper' tape is in the drive. It is almost like the dumps start but freeze up when it finds the wrong tape (even putting the correct tape in the drive doesn't trigger it to continue). Shane T. Ferguson
creating and index after the fact
Hello... I started to test the issue with my previous email. I thought to myself, "self, I need more stuff on the holding disk, why not use this as an opertunity to test a restore". I left "index no" in my config from my testing. :( Is there a way to create an index from the tapes? TIA -- Christopher McCrory "The guy that keeps the servers running" [EMAIL PROTECTED] http://www.pricegrabber.com "Linux: Because rebooting is for adding new hardware"
RE: Wrong tape / amdump question
When the wrong tape is in the drive, the dump suspends - it gets all the estimates from the other servers but when I check amstatus, I get "wait for dumping" for each filesystem (even after manually putting the correct tape in the drive). I ended up killing each process and running amcleanup. Once I re-ran amdump (with the right tape), everything worked fine. Shane -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jens Bech Madsen Sent: Tuesday, January 02, 2001 1:43 PM To: Amanda-Users Subject: Re: Wrong tape / amdump question "Shane T. Ferguson" [EMAIL PROTECTED] writes: Hi, how do I get Amanda to dump the filesystems to holding disk if it finds the wrong tape in the drive (which I can manually flush them to tape at a later time)? I am running Amanda 2.4.2 on RH6.1 (2.2.18). The dumps work fine when the 'proper' tape is in the drive. It is almost like the dumps start but freeze up when it finds the wrong tape (even putting the correct tape in the drive doesn't trigger it to continue). Shane T. Ferguson This should be the default behaviour if you have a holding disk configured. One thing to note, though, is that Amanda doesn't do level 0 dumps to disk. Only incrementals will be dumped to holding disk if the wrong tape is detected. Døs the backup freeze completely and need to be terminated abnormally or does it terminate without doing any backups? What does amandad.debug say? /Jens -- Jens Bech Madsen The Stibo Group, Denmark
amcheck errors
Help- Here are the problems that I am currently having. All help is greatly appreciated. Mike [amanda@host238 sbin]$ ./amcheck Daily Amanda Tape Server Host Check - Holding disk /dumps/amanda: 6564604 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape Daily01 label ok NOTE: info dir /opt/adm/amanda/DailySet1/curinfo/63.170.255.50: does not exist NOTE: info dir /opt/adm/amanda/DailySet1/curinfo/mars.o1.com/_dev_hda1: does not exist NOTE: info dir /opt/adm/amanda/DailySet1/curinfo/slowsrv/_usr: does not exist NOTE: index dir /opt/adm/amanda/DailySet1/index/slowsrv/_usr: does not exist NOTE: info dir /opt/adm/amanda/DailySet1/curinfo/slowsrv/_: does not exist NOTE: index dir /opt/adm/amanda/DailySet1/index/slowsrv/_: does not exist Server check took 5.607 seconds Amanda Backup Client Hosts Check ERROR: slowsrv: could not resolve hostname Client check: 3 hosts checked in 9.383 seconds, 1 problem found (brought to you by Amanda 2.4.2) begin:vcard n:Windbigler;Michael tel;work:916-554-2120 x-mozilla-html:TRUE org:;Network Operations version:2.1 email;internet:[EMAIL PROTECTED] title:UNIX Systems Administrator adr;quoted-printable:;;770 L Street =0D=0ASuite 960;Sacramento;CA;95814; end:vcard
Re: Backup of soft-raid device?
Rainer Hofmann wrote: Is it possible to backup a device /dev/md0/, which is a software raid level 0, at all? Yes, I use tar (1.13.18) for that without any problems. In the disklist, I use directory names, instead of devices. -- Regards Chris Karakas Dont waste your cpu time - crack rc5: http://www.distributed.net
Why selfcheck does not go to raw disk
Hi all, I add a new client, did what I did as last time. From backup server , run amcheck Daily. I got Permission denied for new adding. Checked the /tmp/amanda/selfcheck.debug, the line as following: checking disk c0t0d0s1: device /dev/dsk/c0t0d0s1: Permission denied . Why the selfcheck goes to check /dev/dsk/c0t0d0s1 in stead of raw disk /dev/rdsk/c0t0d0s1? Thank you for help __ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/
Re: AMFLUSH
Hmm, that seems to go counter to what I believe Amanda wants to do. During a normal amdump session it will not write to tape 10 if it expects tape 9, so why do this during a flush? Hmm. On Tue, Jan 02, 2001 at 04:34:09PM +0100, Jens Bech Madsen wrote: Joshua E Warchol [EMAIL PROTECTED] writes: Needless to say, it was a good newyear so I'm not all there right now. I put in tape 10 in our rotation, while amadmin was expecting tape 9. It said "Expecting tape 9 or new tape". It then said "do you want to flush these images to tape?" I answered yes. It then happily overwrote tape 10. I know amanda checks for this, it doesn't overwrite tapes. Did it get confused because tape 10 was the tape that it would dump to this evening normally? Any ideas? Amanda just asks for the next tape in the tapelist. Other tapes will work just as well as long as they don't contain "essential" data required for a restore. If tape 10 contained backups necessary for a restore Amanda wouldn't have overwritten it. At least this is how I understand the mechanism. /Jens -- Jens Bech Madsen The Stibo Group, Denmark -- Joshua Warchol UNIX Systems Administrator DSL.net
Re: updated mtx script?
Someone was going to release an updated mtx script on the list...did I
miss it?
Probably. Here's the latest.
--
Joe Rhett Chief Technology Officer
[EMAIL PROTECTED] ISite Services, Inc.
PGP keys and contact information: http://www.noc.isite.net/Staff/
#!/bin/sh
#
# Exit Status:
# 0 Alles Ok
# 1 Illegal Request
# 2 Fatal Error
#
# Contributed by Eric DOUTRELEAU [EMAIL PROTECTED]
# This is supposed to work with Zubkoff/Dandelion version of mtx
#
# Modified by Joe Rhett [EMAIL PROTECTED]
# to work with MTX 1.2.9 by Eric Lee Green http://mtx.sourceforge.net
#
# You may need to customize these things
MT=/usr/bin/mt
MTF=-f
MTX=/opt/amanda/bin/mtx
DD=/usr/bin/dd
firstslot=1
lastslot=7
cleanslot=8
accessbeforeclean=119
# No user-level customized required beyond this point.
# try to hit all the possibilities here
prefix=/opt/amanda
exec_prefix=${prefix}
sbindir=${exec_prefix}/sbin
libexecdir=${exec_prefix}/libexec
PATH=$sbindir:$libexecdir:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ucb:/usr/local/bin
export PATH
if [ -d "/tmp/amanda" ]; then
DBGFILE=/tmp/amanda/changer.debug
else
DBGFILE=/dev/null
fi
USE_VERSION_SUFFIXES="no"
if test "$USE_VERSION_SUFFIXES" = "yes"; then
SUF="-2.4.2b2"
else
SUF=
fi
myname=$0
tape=`amgetconf$SUF tapedev`
TAPE=`amgetconf$SUF changerdev`; export TAPE # for mtx command
if [ "$tape" = "/dev/null" -o "$TAPE" = "/dev/null" ]; then
echo "Both tapedev and changerdev must be specified in config file";
exit 2;
fi
changerfile=`amgetconf$SUF changerfile`
cleanfile=$changerfile-clean
accessfile=$changerfile-access
slotfile=$changerfile-slot
[ ! -f $cleanfile ] echo 0 $cleanfile
[ ! -f $accessfile ] echo 0 $accessfile
[ ! -f $slotfile ] echo 0 $slotfile
cleancount=`cat $cleanfile`
accesscount=`cat $accessfile`
# Routines start here
readstatus() {
usedslot=`$MTX status |
sed -n 's/Data Transfer Element 0:Empty/-1/p;s/Data Transfer Element
0:Full (Storage Element \(.\) Loaded)/\1/p'`
if [ "$usedslot" -eq "-1" ]; then
echo '-1' $slotfile
fi
echo "STATUS - currently loaded slot = $usedslot" $DBGFILE
}
eject() {
readstatus
echo "EJECT - ejecting tape from slot $usedslot" $DBGFILE
if [ $usedslot -gt 0 ]; then
$MTX unload $usedslot 2/dev/null
echo "0 $tape"
exit 0
else
echo "0 Drive was not loaded"
exit 1
fi
}
reset() {
readstatus
if [ $usedslot -gt 0 ]; then
echo "RESET - ejecting tape from slot $usedslot" $DBGFILE
$MTX unload $usedslot 2/dev/null
fi
echo "RESET - loading tape from slot 1" $DBGFILE
result=`$MTX load 1 21`
if [ $? -eq 0 ]; then
echo "1 $tape"
exit 0
else
echo "1 $result"
exit 1
fi
}
loadslot() {
readstatus
whichslot=$1
echo "LOADSLOT - load tape from slot $whichslot" $DBGFILE
case $whichslot in
current)
if [ $usedslot -lt 0 ]; then
loadslot=$firstslot
else
echo "$usedslot $tape"
exit 0
fi
;;
next|advance)
if [ $usedslot -lt 0 ]; then
loadslot=$firstslot
else
loadslot=`expr $usedslot + 1`
if [ $loadslot -gt $lastslot ]; then
loadslot=$firstslot
fi
fi
;;
prev)
loadslot=`expr $usedslot - 1`
if [ $loadslot -lt $firstslot ]; then
loadslot=$lastslot
fi
;;
first)
loadslot=$firstslot
;;
last)
loadslot=$lastslot
;;
[${firstslot}-${lastslot}])
loadslot=$1
;;
clean)
loadslot=$cleanslot
;;
*)
echo "0 illegal request"
exit 1
;;
esac
# Is this already the current slot?
if [ $loadslot = $usedslot ]; then
echo "$usedslot $tape"
exit 0
fi
# Is this a cleaning request?
if [ $loadslot = $cleanslot ]; then
expr
Re: updated mtx script?
That is a horrid, unportable and often failing hack. Sometimes the loaders will simply take longer than other times, especially if your unit is smart enough to auto-clean when necessary. Use the updated chg-zd-mtx script, which checks the drive status until ready. On Tue, Jan 02, 2001 at 07:43:51AM -0800, Christopher McCrory wrote: Hello... I ran into this last week using the chg-zd-mtx script. I had to add some 'sleep 90' commands to allow the tape drive to initialize after a change. Mike Cathey wrote: Someone was going to release an updated mtx script on the list...did I miss it? Thanks, Mike -- Christopher McCrory "The guy that keeps the servers running" [EMAIL PROTECTED] http://www.pricegrabber.com "Linux: Because rebooting is for adding new hardware" -- Joe Rhett Chief Technology Officer [EMAIL PROTECTED] ISite Services, Inc. PGP keys and contact information: http://www.noc.isite.net/Staff/
Re: Why selfcheck does not go to raw disk
Date: Tue, 2 Jan 2001 11:33:33 -0800 (PST) From: Wang Chen [EMAIL PROTECTED] I add a new client, did what I did as last time. From backup server , run amcheck Daily. I got Permission denied for new adding. Checked the /tmp/amanda/selfcheck.debug, the line as following: checking disk c0t0d0s1: device /dev/dsk/c0t0d0s1: Permission denied . Why the selfcheck goes to check /dev/dsk/c0t0d0s1 in stead of raw disk /dev/rdsk/c0t0d0s1? Thank you for help Presumably because the former (/dev/dsk/c0t0d0s1) is what you put in the appropriate disklist file. (It is my understanding expectation that the "permission denied" message you saw was generated not by a component of amanda (per se), but by the underlying "dump" (or "ufsdump") or (GNU) tar program.) Happy New Year, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823
Re: updated mtx script?
On Tue, Jan 02, 2001 at 12:04:39PM -0800, Joe Rhett wrote: Someone was going to release an updated mtx script on the list...did I miss it? Probably. Here's the latest. Hi Joe, Could you send a patch (diff -u) for chg-zd-mtx.sh.in ? Did the new script is compatible with the previous? Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Colorado Tape
Gregory Propf [EMAIL PROTECTED] 01/01/01 04:54am I have an old Travan floppy tape (400mb uncompressed). This makes me wonder if anyone is using Colorado QIC floppy tapes...? I've had no luck with the ft() stuff (FreeBSD 2.2 STABLE) and can't seem to find any more suitable interface/driver. Has anyone got (or heard of) one running with amanda? Perhaps there is better support in Linux or Solaris x86? I really only need to back up /etc on the local machine and a few others so the size of the tape would be perfect if I can make it work. Thanks Richard Grace
Re: creating and index after the fact
... I left "index no" in my config from my testing. :( Is there a way to create an index from the tapes? Not easily. In general, you have to read the image and send it back to the client, regenerate the index there and then send that back to the server. This should be easier with what's called the DUMPER-API, but nothing is available yet. Christopher McCrory John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Why selfcheck does not go to raw disk
... Why the selfcheck goes to check /dev/dsk/c0t0d0s1 in stead of raw disk /dev/rdsk/c0t0d0s1? ... Amanda does that conversion via your /etc/fstab (vfstab) file. Do you have c0t0d0s1 listed in there properly? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Why selfcheck does not go to raw disk
John, Yes, the c0t0d0s1 is listed in /etc/vfstab. The file systems were mounted form this file. Thanks. Wang --- "John R. Jackson" [EMAIL PROTECTED] wrote: ... Why the selfcheck goes to check /dev/dsk/c0t0d0s1 in stead of raw disk /dev/rdsk/c0t0d0s1? ... Amanda does that conversion via your /etc/fstab (vfstab) file. Do you have c0t0d0s1 listed in there properly? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/
Re: Why selfcheck does not go to raw disk
Yes, the c0t0d0s1 is listed in /etc/vfstab. ... Please post the corresponding lines from your disklist and vfstab files. Wang John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Why selfcheck does not go to raw disk
The disklist fw2 c0t0d0s0 comp-root # / fw2 c0t0d0s6 comp-user # /usr fw2 c0t0d0s1 comp-user # /var The /etc/vfstab /dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no - /dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no - /dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1 /var ufs 1 no Thanks. --- "John R. Jackson" [EMAIL PROTECTED] wrote: Yes, the c0t0d0s1 is listed in /etc/vfstab. ... Please post the corresponding lines from your disklist and vfstab files. Wang John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/
Re: Why selfcheck does not go to raw disk
The /etc/vfstab ... /dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1 /var ufs 1 no It's very hard to read this because of line wrapping or cut/paste, but it looks like you are missing a trailing '-' on that line. Some quick experiments on a system here seem to indicate that could cause the problem. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: RPM Weirdness with amreport
... If I uncomment the "lbl-templ" line amreport can't find the print command; I can't find a place to tell it what command to use. ... That's built in to the binaries, so you'll have to find out where the person who built it had the print package installed. I'd try: strings /path/to/amreport | grep lp This is yet another reason the Amanda developers strongly recommend building from source. Josh Kuperman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck errors
Here are the problems that I am currently having. ...
All the NOTE lines about things not existing may be ignored -- they are
for a new disk/client/whatever and will be created for you during the
normal run.
ERROR: slowsrv: could not resolve hostname
This says Amanda could not look up host name "slowsrv", i.e. a call to
gethostbyname("slowsrv") reported an error, which must be some kind of
configuration problem with your machine.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Bandwidth usage
I think I've gotten myself terribly confused on this. ... Looks just like the way I would have set it up (whether that's right or not is a completely different question :-). ... I see messages in the amdump files that I get bandwidth limited at times. I don't know if I've upped the netusage variable since that. You're always going to be limited by something. It might be that if you increased the bandwidth **way** up it would just tell you that it was limited by the number of dumps it could run on a client (for instance). So I wouldn't worry about it a lot unless you think you're spending too much time (amstatus give you time and % of total) sitting in this state and you really could run something else. As to netusage, since you've defined your own interfaces, netusage is not really used. It becomes the fallback value when you don't define an interface. [EMAIL PROTECTED] John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amandad looping on FreeBSD 2.2.7
$ cat /etc/xinetd.d/amanda ... wait= no I think this is wrong. It should be "yes" for "wait". I don't know what this "looping" is about, but it appears that the "amandad" service is deactivated ... When inetd/xinetd detects a service mis-behaving (which it calls "looping"), it will deactivite it for some period of time, like 10 minutes, then turn it back on. Or you may send inetd/xinetd a HUP to get it to turn everything back on earlier than the cycle time. Tom Griffing, Vistyx Corp John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
is a adic 1200 tape library supported
Hi Is the adic 1200 tape library supported. It is a dds2 tape library that hold s12 dds2 tape units. Hope to hear from anyone if it can or can not be , or if someone is using it with amnada. I wish to use it on solaris 8. Joseph
Re: must be run as user amanda
Try: su - amanda instead of su amanda On Tue, 2 Jan 2001, Francois Bradet wrote: Ever since I've upgraded from 2.4.1 to 2.4.2, I can't run amdump if I just "su" to user amanda. ex: ## rei:/usr/local/amanda/sbin# su amanda ## rei:/usr/local/amanda/sbin$ ./amdump AM ## amdump: must be run as user amanda However, if I telnet in as user amanda, it works just fine. Any idea what's causing this ? It used to work perfectly by su'ing as user amanda. I also do the following, when I start amdump manually: 1. telnet in as user 'hernick' (not a special user) 2. su as user 'root' 3. start a 'screen' 4. su as user 'amanda' 5. run 'amdump' -- Isaac Saldana
