How to Unsubscribe ---
If you ever want to remove yourself from this mailing list, you can send mail to: [EMAIL PROTECTED] with the following command in the body of your email message: unsubscribe amanda-users or from another account, besides the one you are unsubscribing: unsubscribe amanda-users email-address David Carter McLeodUSA Information Systems [EMAIL PROTECTED] 281-465-1835
GNUTAR backup of VxFS fails
Running amanda 2.4.1p2 on Solaris 2.6. The gtar version is 1.11.8. All the files systems are ufs except for one Veritas VxFS files system. The VxFS is set to run with the GNUTAR dumptype and was working for many months. Lately, however, amanda gives me the syndesis1 /a lev 0 FAILED [disk /a offline on syndesis1?] error. According to the /tmp/amanda/runtar.debug file on syndesis1, the gtar dump is initiating but is now going directly to /dev/null. Any idea why this is happening, or where --file becomes /dev/null? Maybe I'm reading it wrong but that looks like what's happening. Also, a file called /usr/local/var/amanda/gnutar-lists/syndesis1_a_1 exists, but is is mod-dated from the last amanda run where this dump didn't come up as FAILED--. /tmp/amanda/runtar.debug: runtar: debug 1 pid 1863 ruid 0 euid 0 start time Wed May 16 01:55:03 2001 /usr/local/bin/gtar: version 2.4.1p1 running: /usr/local/bin/gtar: /usr/local/bin/gtar --create --directory /a --listed -incremental /usr/local/var/amanda/gnutar-lists/syndesis1_a_1.new --sparse --one-f ile-system --ignore-failed-read --totals --file /dev/null . David Carter McLeodUSA Information Systems [EMAIL PROTECTED] 281-465-1835
Lev 0 backup to disk - single system
Does anyone know how to get amanda to run a full backup but leave the dumpfiles on the holding disk after writing to tape? Holding disk space is not a problem. I want to do this for running a full backup on a single system prior to hardware upgrades, but save the time spent pulling dumps back off from tape when restoring afterward. Just trying to streamline a process to make life easier... Thanks... David Carter McLeodUSA Information Systems [EMAIL PROTECTED] 281-465-1835
One-time Full backup
I often have systems about to go through scheduled hardware maintenance, and I want to run a one-time level 0 backup of it prior to the maintenance and outside of its normal schedule. Once the maintenance is successful, this particular backup isn't needed any longer. I've created a configuration for it, and I'm just wondering if amanda will work correctly with: dumpcycle 1 runspercycle 1 tapecycle 1 and allow me to re-use the tape for the same thing next time. Just trying to avoid having to do an amrmtape amlabel every time... David Carter McLeodUSA Information Systems [EMAIL PROTECTED] 281-465-1835
Fixed: amcheck failing with selfcheck request timed out
The amcheck debug file on the server looked like a normal amcheck (other than taking 30 seconds to complete): amcheck: debug 1 pid 7865 ruid 0 euid 0 start time Fri Apr 20 17:59:42 2001 amcheck: dgram_bind: socket bound to 0.0.0.0.767 amcheck: pid 7865 finish time Fri Apr 20 18:00:12 2001 The problem, it turns out, was that ipchains had been installed on the server during the Red Hat 7.1 install. Since the machine is already inside our company firewall I removed ipchains and now everything works. Thanks John, for your time and for responding. David Carter McLeodUSA Information Systems [EMAIL PROTECTED] 281-465-1835
amcheck failing with selfcheck request timed out
I've got a new install on RedHat 7.1 (amanda server 2.4.2p2) and clients are Solaris 2.6 (amanda 2.4.1p1) I've gone through the entries in the AMANDA FAQ-o-matic without success. I built amanda on the RedHat system, rather than installing the pre-compiled rpm included with the distribution. The builds were all configured with the following options: --with-user=root --with-group=sys --with-amandahosts When amcheck is run, the clients -do- start amandad. I get prolific amandad.debug and selfcheck.debug files on the clients. The clients have been working with another server (Solaris 2.6 amanda 2.4.1p1) for quite some time. The only thing I've changed on the clients is the .amandahosts file. It seemed like that's all that should be necessary on the client side. I'm green on Linux, so that may be part of the problem. xinetd is new to me, but I think I've got the files in xinetd.d configured correctly on the server, since each file is an analogy to the corresponding old inetd.conf entry. Typos always possible. The debug files say there is some weirdness with acknowledgments. All the machines are inside our firewall. client: draco server: zig Here's draco's amandad.debug file: -- amandad: debug 1 pid 19035 ruid 0 euid 0 start time Fri Apr 20 17:59:23 2001 amandad: version 2.4.1p1 amandad: build: VERSION="Amanda-2.4.1p1" amandad:BUILT_DATE="Mon Oct 16 17:51:46 CDT 2000" amandad:BUILT_MACH="SunOS draco 5.6 Generic_105181-22 sun4u sparc SUNW,Ultra-5_10" amandad:CC="gcc" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" amandad:RESTORE="/usr/sbin/ufsrestore" amandad:GNUTAR="/usr/local/bin/gtar" amandad:COMPRESS_PATH="/usr/local/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" MAILER="/bin/mailx" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="draco" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="draco" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY amandad:CLIENT_LOGIN="nobody" 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-D0A40708 SEQ 987804045 SECURITY USER root SERVICE selfcheck OPTIONS ; DUMP /home 0 OPTIONS |;bsd-auth; sending ack: Amanda 2.4 ACK HANDLE 001-D0A40708 SEQ 987804045 bsd security: remote host zig user root local user root amandahosts security check passed amandad: running service "/usr/local/libexec/selfcheck" amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-D0A40708 SEQ 987804045 OPTIONS ; OK /home OK /usr/sbin/ufsdump executable OK /etc/dumpdates read/writable OK /dev/null read/writable OK /tmp has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: got ack: Amanda 2.4 REQ HANDLE 001-D0A40708 SEQ 987804045 SECURITY USER root SERVICE selfcheck OPTIONS ; DUMP /home 0 OPTIONS |;bsd-auth; amandad: weird, it's not a proper ack addr: peer C0A8C36F dup C0A8C36F, port: peer 319 dup 319 amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-D0A40708 SEQ 987804045 OPTIONS ; OK /home OK /usr/sbin/ufsdump executable OK /etc/dumpdates read/writable OK /dev/null read/writable OK /tmp has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: waiting for ack: timeout, retrying amandad: got ack: Amanda 2.4 REQ HANDLE 001-D0A40708 SEQ 987804045 SECURITY USER root SERVICE selfcheck OPTIONS ; DUMP /home 0 OPTIONS |;bsd-auth; amandad: weird, it's not a proper ack addr: peer C0A8C36F dup C0A8C36F, port: peer 319 dup 319 amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 19035 finish time Fri Apr 20 18:00:23 2001 -- Here's the selfcheck.debug file: -- selfcheck: debug 1 pid 19036 ruid 0 euid 0 start time Fri Apr 20 17:59:23 2001 /usr/local/libexec/selfcheck: version 2.4.1p1 checking disk /home: device /dev/rdsk/c0t0d0s7: OK selfcheck: pid 19036 finish time Fri Apr 20 17:59:23 2001 -- David Carter McLeodUSA Information Systems [EMAIL PROTECTED] 281-465-1835
RE: Average Dump Rate Question
Check your hme interface settings. I found that on the systems that
appeared to be slow, the NIC was configured for something other than 100
full, even though the physical network was 100 full.
If you have access to SunSolve ( http://sunsolve.sun.com/ ), you can check
out FAQ ID #2605 and Infodoc ID #18262 for some very useful information, as
well as some good instructions on changing your settings. You'll probably
have to have a SunSolve account to get the info. If you've read and
understood the docs, then the following might be helpful (at least it can
show you if the settings are conflicting):
To see the list of variables for the /dev/hme interface, use:
# ndd /dev/hme \?
I use this little script to show me the current settings:
#
VARLIST=`ndd /dev/hme \? | sed '1d' | cut -d" " -f1`
for VAR in $VARLIST
do
echo "${VAR} = `ndd /dev/hme ${VAR}`"
done
#
The output looks like this: (some comments are added in with #)
# ./nddcheck.sh
transceiver_inuse = 0
link_status = 1 # 1=up 0=down (Read-Only)
link_speed = 1 # 1=100mps 0=10mps (R-O)
link_mode = 0 # 1=full duplex 0=half duplex (R-O)
ipg1 = 8
ipg2 = 4
use_int_xcvr = 0
pace_size = 0
adv_autoneg_cap = 1 # Advertise whether you want to
auto-negotiate
# If adv_autoneg_cap = 0,
set one of the following
# adv_values to 1 and all
the others to 0.
# If adv_autoneg_cap = 1,
then
adv_100T4_cap = 0 # Advertise available
speeds/modes
adv_100fdx_cap = 1 # 100 full
adv_100hdx_cap = 1 # 100 half
adv_10fdx_cap = 1 # 10 full
adv_10hdx_cap = 1 # 10 half
autoneg_cap = 1 # Current settings (read-only
values)
100T4_cap = 0
100fdx_cap = 1
100hdx_cap = 1
10fdx_cap = 1
10hdx_cap = 1
lp_autoneg_cap = 0 # Link partner settings (read-only
values)
lp_100T4_cap = 0
lp_100fdx_cap = 0
lp_100hdx_cap = 0
lp_10fdx_cap = 0
lp_10hdx_cap = 0
instance = 0# /dev/hme0
lance_mode = 1
ipg0 = 16
So according to the settings, this system is configured to auto-negotiate
and has settled on 100 Mbps, half duplex. Auto-negotiate slows things down,
and so does the half duplex...
Check with the people who configure your network/routers/switches to be sure
of the settings you need to use. Also, if the machine is on a hub, that too
should be taken into consideration.
Hope this helps...
David Carter
McLeodUSA Information Systems
[EMAIL PROTECTED]
281-465-1835
-Original Message-
From: Tanniel Simonian [mailto:[EMAIL PROTECTED]]
Sent: Saturday, March 03, 2001 4:11 PM
To: [EMAIL PROTECTED]
Subject: Average Dump Rate Question
Currently my average dump rate on a 100mbit full switched network
consisting of Cisco 2948G's and Dell Pentium III 800 mhz with
512 megs of
ram server is at:
Avg Dump Rate (k/s) 364.5 364.5--
How can I speed this up?
In amanda.conf I have set netusage to 5 kbits.
should I increase that number, decrease the number of dumps running
concurrently, shouldn't my network card be able to handle at least 4
megabytes per second, (3com 35905B 100mbit)? Does high
compression play a
factor in the file transfer, or does the compression be done
on the client
machine then sent over the network to the dump disk?
My hard disk also is set up as this:
define interface local {
comment "a local disk"
use 5 kbps
}
My local disk is an IBM Ultra 2 9 gig 1 RPM drive. I believe 5
kbps is sort of slow for a drive like this, but I don't get any
improvements by bumping this number up?
What can I do to increase my dump rate? Also does amanda ignore, when
defining a tape type the speed of what the tape drive is
capable? Does it
leave determining the speed to the actual drive and interface?
define tapetype M2-AME225 {
comment "Exabyte EZ17 Mammoth2"
length 57487 mbytes
filemark 0 kbytes
speed 11765 kbytes
}
Avg Tp Write Rate (k/s) 6689.9 6689.9--
Im assuming that compression may play a role in the speed of the tape
drive copying content?
Any suggestions are greatly appreciated,
Thank you,
Tanniel Simonian
University of California Riverside Science Library
Linux Admin/Networking Admin
