Re: amdump failed, Request to test.ru timed out.
According to Ignacio Dosil Lago: > Strange. > Was inetd up when you ran amdump? Yes, certaily. > Did you grant access to the tape server at the client via .amandahosts? test.ru:/etc/amanda | 554 >less .amandahosts test.ru amanda Have I filled .amandahosts correctly? > Have you checked inetd config. file? Yes, certaily. test.ru:/etc/amanda | 555 >less /etc/inetd.conf | grep -i amanda amanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad amandaidx stream tcp nowait amanda /usr/contrib/lib/amanda/amindexd amindexd amidxtape stream tcp nowait amanda /usr/contrib/lib/amanda/amidxtap ed amidxtaped kamanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad -krb4 > Perhaps you left behind some of this issues. > > > Mary N Koroleva wrote: > > >Hi, > > > >I run amcheck - it's all right. After I try to run amdump. > > > >test.ru:/etc/amanda/test/log | 513 >less amdump.1 > >amdump: start at Mon Mar 4 17:59:34 MSK/MSD 2002 > >planner: pid 6649 executable /usr/contrib/lib/amanda/planner version 2.4.1p1 > >planner: build: VERSION="Amanda-2.4.1p1" > >planner:BUILT_DATE="Sun Oct 8 22:38:54 GMT 2000" > >planner:BUILT_MACH="BSD/OS hephaestus.BSDI.COM 4.2 BSDI BSD/OS 4.2 Kerne > >l #2: Mon Aug 21 14:49:26 MDT 2000 [EMAIL PROTECTED]:/home/polk/sys/com > >pile/HEPHAESTUS i386" > >planner:CC="shlicc" > >planner: paths: bindir="/usr/contrib/bin" sbindir="/usr/contrib/sbin" > >planner:libexecdir="/usr/contrib/lib/amanda" > >planner:mandir="/usr/contrib/man" CONFIG_DIR="/etc/amanda" > >planner:DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/r" > >planner:DUMP="/sbin/dump" RESTORE="/sbin/restore" > >planner:SAMBA_CLIENT="/usr/contrib/bin/smbclient" > >planner:COMPRESS_PATH="/usr/contrib/bin/gzip" > >planner:UNCOMPRESS_PATH="/usr/contrib/bin/gzip" > >planner:MAILER="/usr/bin/Mail" > >planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" > >planner:DEFAULT_TAPE_SERVER="localhost" > >planner:DEFAULT_TAPE_DEVICE="/dev/nrst0" HAVE_MMAP > >planner:LOCKING=POSIX_FCNTL DEBUG_CODE BSD_SECURITY KRB4_SECURITY > >planner:SERVER_HOST_PRINCIPLE="amanda" > >planner:SERVER_HOST_INSTANCE="" > >planner:SERVER_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >planner:CLIENT_HOST_PRINCIPLE="rcmd" > >planner:CLIENT_HOST_INSTANCE="" > >planner:CLIENT_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >planner:TICKET_LIFETIME="128" CLIENT_LOGIN="operator" FORCE_USERID > >planner:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" > >planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > >READING CONF FILES... > >startup took 0.011 secs > > > >SETTING UP FOR ESTIMATES... > >setting up estimates for test.ru:/dev/sd0a > >test.ru:/dev/sd0a overdue 11751 days for level 0 > >setup_estimate: test.ru:/dev/sd0a: command 0, options: > >last_level -1 next_level0 -11751 level_days 0 > >getting estimates 0 (0) -1 (-1) -1 (-1) > >setting up estimates took 0.000 secs > > > >GETTING ESTIMATES... > >driver: pid 6650 executable /usr/contrib/lib/amanda/driver version 2.4.1p1 > >driver: send-cmd time 0.009 to taper: START-TAPER 20020304 > >taper: pid 6651 executable taper version 2.4.1p1 > >driver: started dumper0 pid 6653 > >driver: started dumper1 pid 6654 > >driver: started dumper2 pid 6655 > >driver: started dumper3 pid 6656 > >dumper: pid 6653 executable dumper version 2.4.1p1, using port 1021 > >dumper: pid 6654 executable dumper version 2.4.1p1, using port 1022 > >dumper: pid 6655 executable dumper version 2.4.1p1, using port 1023 > >dumper: pid 6656 executable dumper version 2.4.1p1, using port 512 > >taper: read label `Daily01' date `X' > >taper: wrote label `Daily01' date `20020304' > >error result for host test.ru disk /dev/sd0a: Request to test.ru timed out. > >getting estimates took 29.995 secs > >FAILED QUEUE: > > 0: test.ru /dev/sd0a > >DONE QUEUE: empty > > > >ANALYZING ESTIMATES... > >planner: FAILED test.ru /dev/sd0a 0 [Request to test.ru timed out.] > >INITIAL SCHEDULE (size 5120): > > > > > > > >But test.ru is up. > > > >Would you be so kind to promt me how amanda check host is up or down? > > > >Tnak you in advance, > >Mary Koroleva > > > > > > > -- Mary N Koroleva Russian Institute E-mail: [EMAIL PROTECTED]for Phone: +7 095 737 0601Public Networks
Re: amdump failed, Request to test.ru timed out.
According to Ignacio Dosil Lago: > Strange. > Was inetd up when you ran amdump? Yes, certaily. > Did you grant access to the tape server at the client via .amandahosts? test.ru:/etc/amanda | 554 >less .amandahosts test.ru amanda Have I filled .amandahosts correctly? > Have you checked inetd config. file? Yes, certaily. test.ru:/etc/amanda | 555 >less /etc/inetd.conf | grep -i amanda amanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad amandaidx stream tcp nowait amanda /usr/contrib/lib/amanda/amindexd amindexd amidxtape stream tcp nowait amanda /usr/contrib/lib/amanda/amidxtap ed amidxtaped kamanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad -krb4 > Perhaps you left behind some of this issues. > > > Mary N Koroleva wrote: > > >Hi, > > > >I run amcheck - it's all right. After I try to run amdump. > > > >test.ru:/etc/amanda/test/log | 513 >less amdump.1 > >amdump: start at Mon Mar 4 17:59:34 MSK/MSD 2002 > >planner: pid 6649 executable /usr/contrib/lib/amanda/planner version 2.4.1p1 > >planner: build: VERSION="Amanda-2.4.1p1" > >planner:BUILT_DATE="Sun Oct 8 22:38:54 GMT 2000" > >planner:BUILT_MACH="BSD/OS hephaestus.BSDI.COM 4.2 BSDI BSD/OS 4.2 Kerne > >l #2: Mon Aug 21 14:49:26 MDT 2000 [EMAIL PROTECTED]:/home/polk/sys/com > >pile/HEPHAESTUS i386" > >planner:CC="shlicc" > >planner: paths: bindir="/usr/contrib/bin" sbindir="/usr/contrib/sbin" > >planner:libexecdir="/usr/contrib/lib/amanda" > >planner:mandir="/usr/contrib/man" CONFIG_DIR="/etc/amanda" > >planner:DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/r" > >planner:DUMP="/sbin/dump" RESTORE="/sbin/restore" > >planner:SAMBA_CLIENT="/usr/contrib/bin/smbclient" > >planner:COMPRESS_PATH="/usr/contrib/bin/gzip" > >planner:UNCOMPRESS_PATH="/usr/contrib/bin/gzip" > >planner:MAILER="/usr/bin/Mail" > >planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" > >planner:DEFAULT_TAPE_SERVER="localhost" > >planner:DEFAULT_TAPE_DEVICE="/dev/nrst0" HAVE_MMAP > >planner:LOCKING=POSIX_FCNTL DEBUG_CODE BSD_SECURITY KRB4_SECURITY > >planner:SERVER_HOST_PRINCIPLE="amanda" > >planner:SERVER_HOST_INSTANCE="" > >planner:SERVER_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >planner:CLIENT_HOST_PRINCIPLE="rcmd" > >planner:CLIENT_HOST_INSTANCE="" > >planner:CLIENT_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >planner:TICKET_LIFETIME="128" CLIENT_LOGIN="operator" FORCE_USERID > >planner:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" > >planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > >READING CONF FILES... > >startup took 0.011 secs > > > >SETTING UP FOR ESTIMATES... > >setting up estimates for test.ru:/dev/sd0a > >test.ru:/dev/sd0a overdue 11751 days for level 0 > >setup_estimate: test.ru:/dev/sd0a: command 0, options: > >last_level -1 next_level0 -11751 level_days 0 > >getting estimates 0 (0) -1 (-1) -1 (-1) > >setting up estimates took 0.000 secs > > > >GETTING ESTIMATES... > >driver: pid 6650 executable /usr/contrib/lib/amanda/driver version 2.4.1p1 > >driver: send-cmd time 0.009 to taper: START-TAPER 20020304 > >taper: pid 6651 executable taper version 2.4.1p1 > >driver: started dumper0 pid 6653 > >driver: started dumper1 pid 6654 > >driver: started dumper2 pid 6655 > >driver: started dumper3 pid 6656 > >dumper: pid 6653 executable dumper version 2.4.1p1, using port 1021 > >dumper: pid 6654 executable dumper version 2.4.1p1, using port 1022 > >dumper: pid 6655 executable dumper version 2.4.1p1, using port 1023 > >dumper: pid 6656 executable dumper version 2.4.1p1, using port 512 > >taper: read label `Daily01' date `X' > >taper: wrote label `Daily01' date `20020304' > >error result for host test.ru disk /dev/sd0a: Request to test.ru timed out. > >getting estimates took 29.995 secs > >FAILED QUEUE: > > 0: test.ru /dev/sd0a > >DONE QUEUE: empty > > > >ANALYZING ESTIMATES... > >planner: FAILED test.ru /dev/sd0a 0 [Request to test.ru timed out.] > >INITIAL SCHEDULE (size 5120): > > > > > > > >But test.ru is up. > > > >Would you be so kind to promt me how amanda check host is up or down? > > > >Tnak you in advance, > >Mary Koroleva > > > > > > > -- Mary N Koroleva Russian Institute E-mail: [EMAIL PROTECTED]for Phone: +7 095 737 0601Public Networks
FileTooLargeError-2.4.2p2
/usr partition fails to write to tape although it seems to dump to the
holding disk OK. Nothing is left in the holding disk
(/var/local/storage/hold_amanda).
amanda 2.4.2p2
Travan 10/20Gb uncompressed/compressed tape
The tape definition received from running tapetype
define tapetype TRAVAN {
comment "just produced by tapetype program"
comment "Tecmar Travan NS20 - 3M Travan 20 Tape"
length 9935 mbytes
filemark 30 kbytes
speed 938 kbytes
>From "df"
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda5 1981990 1456881422659 78% /
/dev/sda130719 11083 18050 39% /boot
/dev/hda221472 2259 18105 12% /boothda
/dev/hda1 1939104823136 1115968 43% /dosC
/dev/sda6 3465433 2180149 1106034 67% /usr
/dev/sda7 1685149108162 1489897 7% /var
/dev/hdg1 2767240420 26266700 1%
/var/local/storage/hold_amanda
Date: Mon, 4 Mar 2002 06:01:52 -0800
From: Red Hat Linux User <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: buddies.orthodontists.info AMANDA MAIL REPORT FOR March 4, 2002
Status: RO
These dumps were to tape buddies_full-01.
The next tape Amanda expects to use is: buddies_full-02.
FAILURE AND STRANGE DUMP SUMMARY:
buddies/usr lev 0 FAILED ["data write: File too large"]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:06
Run Time (hrs:min) 1:52
Dump Time (hrs:min)0:50 0:50 0:00
Output Size (meg)2205.2 2205.20.0
Original Size (meg) 2205.2 2205.20.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped5 5 0
Avg Dump Rate (k/s) 754.4 754.4--
Tape Time (hrs:min)1:00 1:00 0:00
Tape Size (meg) 2205.4 2205.40.0
Tape Used (%) 22.2 22.20.0
Filesystems Taped 5 5 0
Avg Tp Write Rate (k/s) 622.1 622.1--
^L
FAILED AND STRANGE DUMP DETAILS:
/-- buddies/usr lev 0 FAILED ["data write: File too large"]
sendbackup: start [buddies:/usr level 0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f... -
sendbackup: info end
\
^L
NOTES:
planner: Adding new disk buddies:/usr.
taper: tape buddies_full-01 kb 2258304 fm 5 [OK]
^L
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
buddies / 0 14583361458336 -- 22:051100.8 40:03 606.8
buddies /boot 0 11072 11072 --0:043043.4 0:18 633.3
buddies /boothda02272 2272 --0:03 776.6 0:05 438.1
buddies /dosC 0 679136 679136 -- 26:11 432.4 18:06 625.7
buddies /usr0 FAILED ---
buddies /var0 107328 107328 --1:311175.2 1:58 906.4
(brought to you by Amanda version 2.4.2p2)
AND FROM SENDBACKUP.XXDEBUG
sendbackup: debug 1 pid 1989 ruid 20 euid 20 start time Tue Mar 5
04:06:59 2002/usr/lib/amanda/sendbackup: version 2.4.2p2
sendbackup: got input request: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS
|;bsd-auth;index;
parsed request as: program `GNUTAR'
disk `/usr'
lev 0
since 1970:1:1:0:0:0
opt `|;bsd-auth;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.1086
sendbackup: stream_server: waiting for connection: 0.0.0.0.1087
sendbackup: stream_server: waiting for connection: 0.0.0.0.1088
waiting for connect on 1086, then 1087, then 1088
sendbackup: stream_accept: connection from 192.168.1.1.1089
sendbackup: stream_accept: connection from 192.168.1.1.1090
sendbackup: stream_accept: connection from 192.168.1.1.1091
got all connections
sendbackup-gnutar: doing level 0 dump as listed-incremental to
/usr/var/amanda/gnutar-lists/buddies_usr_0.new
sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT
sendbackup: spawning /usr/lib/amanda/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory /usr
--one-file-system --listed-incremental
/usr/var/amanda/gnutar-lists/buddies_usr_0.new --sparse
--ignore-failed-read --totals .
sendbackup-gnutar: /usr/lib/amanda/runtar: pid 1993
sendbackup: started index creator: "/bin/gtar -tf - 2>/dev/null | sed -e
's/^\.//'"
index tee cannot write [Broken pipe]
thanks for any direction
Re: FileTooLargeError-2.4.2p2
On Tue, 5 Mar 2002 at 5:44am, ThomasRatliffDDS wrote > > /-- buddies/usr lev 0 FAILED ["data write: File too large"] > sendbackup: start [buddies:/usr level 0] > sendbackup: info BACKUP=/bin/gtar > sendbackup: info RECOVER_CMD=/bin/gtar -f... - > sendbackup: info end > \ You're probably using an older distribution that doesn't support large (>2GB) files. Set "chunksize" in amanda.conf to something smaller than 2GB-32KB. There's no performance penalty, so just use 1GB. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Requested to client timed out?
Roger, I am relatively new to Amanda, but I think I might be able to point you in the right direction. If you look in /tmp/amanda on lexus you should find a series of ".debug" files. You will know them when you see them. These are log files that the client keeps and are really handy when something like this pops up. When I am having trouble, I generally move (do not delete) any existing *.debug files to a temporary directory and then run an 'amcheck '. This will generate new *.debug files to read and check for problems. If there are no clues there, then I would look at the older logs. It sounds to me, just based on the report you attached that the client on lexus is just misconfigured. In order for anyone from the list to effectively help you, we will need some additional information. The following questions are a start: Did you install the client software from a pre-compiled 'packaged' file or did you compile from sources? What is the OS of the client (and server, presumably)? What sort of dumps are you running (tar, dump, etc)? Please remember to attach a representative sample of the /tmp/amanda/*.debug logs as well. Best of luck! Jeff On Tue, 2002-03-05 at 02:19, Roger wrote: > Hi I am having problems with my amanda server to back up some of it's own > directories. lexus is my amanda server and also a client. I have not > problems with other clients except lexus itself. > Below is the log that is emailed to me. Anyone encounter such problem and > have a solution for it? > > > These dumps were to tape Daily-06. > The next tape Amanda expects to use is: Daily-07. > > FAILURE AND STRANGE DUMP SUMMARY: > lexus /data lev 0 FAILED [Request to lexus timed out.] > lexus /home/mysql lev 0 FAILED [Request to lexus timed out.] > lexus /home/bugs lev 0 FAILED [Request to lexus timed out.] > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)1:10 > Run Time (hrs:min) 1:16 > Dump Time (hrs:min)0:04 0:03 0:00 > Output Size (meg) 108.1 107.01.1 > Original Size (meg) 146.2 136.59.7 > Avg Compressed Size (%)73.9 78.4 11.6 (level:#disks ...) > Filesystems Dumped4 2 2 (1:1 2:1) > Avg Dump Rate (k/s) 501.0 573.5 38.5 > > Tape Time (hrs:min)0:03 0:03 0:00 > Tape Size (meg) 108.2 107.01.2 > Tape Used (%) 0.90.90.0 (level:#disks ...) > Filesystems Taped 4 2 2 (1:1 2:1) > Avg Tp Write Rate (k/s) 680.9 686.3 401.3 > > > NOTES: > planner: Last full dump of lexus:/home/bugs on tape overwritten in 1 run. > planner: Last full dump of lexus:/home/mysql on tape overwritten in 1 > run. > planner: Last full dump of lexus:/data on tape overwritten in 1 run. > planner: Incremental of astinus:/home/cvs bumped to level 2. > planner: Full dump of astinus:/home/intranet/backup promoted from 11 days > ahead. > planner: Full dump of astinus:/home/szcvs/data promoted from 11 days > ahead. > taper: tape Daily-06 kb 110816 fm 4 [OK] > > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > astinus /home/cvs 26760896 13.3 0:17 53.8 0:02 561.9 > astinus -net/backup 0 139730 109504 78.4 3:11 574.0 2:19 787.3 > astinus -me/project 13200256 8.0 0:13 19.2 0:01 208.7 > astinus -szcvs/data 0 10 32 320.0 0:00 136.7 0:21 3.1 > lexus/data 0 FAILED --- > lexus/home/bugs 0 FAILED --- > lexus/home/mysql 0 FAILED --- > > (brought to you by Amanda version 2.4.2p2) > > > Roger > > > >
Re: amdump failed, Request to test.ru timed out.
According to Ignacio Dosil Lago: > I see ... .amandahosts is correctly filled but ... > Where is the amanda user home directory? Is .amandahosts there? It should. > (Hope this questions not to be too silly but I am a newby :-)) Yes, certainly ;-) test.ru:/etc/amanda | 599 >amcheck test Amanda Tape Server Host Check - /srvs/hold: 9678351 KB disk space available, using 9678351 KB. ERROR: /dev/nrst0: no tape online. (expecting a new tape) NOTE: skipping tape-writable test. Server check took 0.005 seconds. Amanda Backup Client Hosts Check WARNING: test.ru: selfcheck request timed out. Host down? Client check: 1 host checked in 30.002 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) Would you be so kind to promt me how selfcheck check is host down or up? What algorithm do Amanda use for checking? > > > Mary N Koroleva wrote: > > >According to Ignacio Dosil Lago: > > > >>Strange. > >>Was inetd up when you ran amdump? > >> > > > >Yes, certaily. > > > >>Did you grant access to the tape server at the client via .amandahosts? > >> > > > >test.ru:/etc/amanda | 554 >less .amandahosts > > > >test.ru amanda > > > >Have I filled .amandahosts correctly? > > > > > >>Have you checked inetd config. file? > >> > > > >Yes, certaily. > > > >test.ru:/etc/amanda | 555 >less /etc/inetd.conf | grep -i amanda > >amanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad > >amandaidx stream tcp nowait amanda /usr/contrib/lib/amanda/amindexd > > amindexd > >amidxtape stream tcp nowait amanda /usr/contrib/lib/amanda/amidxtap > >ed amidxtaped > >kamanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad > >-krb4 > > > >>Perhaps you left behind some of this issues. > >> > >> > >>Mary N Koroleva wrote: > >> > >>>Hi, > >>> > >>>I run amcheck - it's all right. After I try to run amdump. > >>> > >>>test.ru:/etc/amanda/test/log | 513 >less amdump.1 > >>>amdump: start at Mon Mar 4 17:59:34 MSK/MSD 2002 > >>>planner: pid 6649 executable /usr/contrib/lib/amanda/planner version 2.4.1p1 > >>>planner: build: VERSION="Amanda-2.4.1p1" > >>>planner:BUILT_DATE="Sun Oct 8 22:38:54 GMT 2000" > >>>planner:BUILT_MACH="BSD/OS hephaestus.BSDI.COM 4.2 BSDI BSD/OS 4.2 Kerne > >>>l #2: Mon Aug 21 14:49:26 MDT 2000 [EMAIL PROTECTED]:/home/polk/sys/com > >>>pile/HEPHAESTUS i386" > >>>planner:CC="shlicc" > >>>planner: paths: bindir="/usr/contrib/bin" sbindir="/usr/contrib/sbin" > >>>planner:libexecdir="/usr/contrib/lib/amanda" > >>>planner:mandir="/usr/contrib/man" CONFIG_DIR="/etc/amanda" > >>>planner:DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/r" > >>>planner:DUMP="/sbin/dump" RESTORE="/sbin/restore" > >>>planner:SAMBA_CLIENT="/usr/contrib/bin/smbclient" > >>>planner:COMPRESS_PATH="/usr/contrib/bin/gzip" > >>>planner:UNCOMPRESS_PATH="/usr/contrib/bin/gzip" > >>>planner:MAILER="/usr/bin/Mail" > >>>planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" > >>>planner:DEFAULT_TAPE_SERVER="localhost" > >>>planner:DEFAULT_TAPE_DEVICE="/dev/nrst0" HAVE_MMAP > >>>planner:LOCKING=POSIX_FCNTL DEBUG_CODE BSD_SECURITY KRB4_SECURITY > >>>planner:SERVER_HOST_PRINCIPLE="amanda" > >>>planner:SERVER_HOST_INSTANCE="" > >>>planner:SERVER_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >>>planner:CLIENT_HOST_PRINCIPLE="rcmd" > >>>planner:CLIENT_HOST_INSTANCE="" > >>>planner:CLIENT_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >>>planner:TICKET_LIFETIME="128" CLIENT_LOGIN="operator" FORCE_USERID > >>>planner:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" > >>>planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > >>>READING CONF FILES... > >>>startup took 0.011 secs > >>> > >>>SETTING UP FOR ESTIMATES... > >>>setting up estimates for test.ru:/dev/sd0a > >>>test.ru:/dev/sd0a overdue 11751 days for level 0 > >>>setup_estimate: test.ru:/dev/sd0a: command 0, options: > >>> last_level -1 next_level0 -11751 level_days 0 > >>> getting estimates 0 (0) -1 (-1) -1 (-1) > >>>setting up estimates took 0.000 secs > >>> > >>>GETTING ESTIMATES... > >>>driver: pid 6650 executable /usr/contrib/lib/amanda/driver version 2.4.1p1 > >>>driver: send-cmd time 0.009 to taper: START-TAPER 20020304 > >>>taper: pid 6651 executable taper version 2.4.1p1 > >>>driver: started dumper0 pid 6653 > >>>driver: started dumper1 pid 6654 > >>>driver: started dumper2 pid 6655 > >>>driver: started dumper3 pid 6656 > >>>dumper: pid 6653 executable dumper version 2.4.1p1, using port 1021 > >>>dumper: pid 6654 executable dumper version 2.4.1p1, using port 1022 > >>>dumper: pid 6655 executable dumper version 2.4.1p1, using port 1023 > >>>dumper: pid 6656 executable dumper version 2.4.1p1, using port 512 > >>>taper: read label `Daily01' date `X' > >>>t
Re: amdump failed, Request to test.ru timed out.
According to Ignacio Dosil Lago: > I see ... .amandahosts is correctly filled but ... > Where is the amanda user home directory? Is .amandahosts there? It should. > (Hope this questions not to be too silly but I am a newby :-)) Yes, certainly ;-) test.ru:/etc/amanda | 599 >amcheck test Amanda Tape Server Host Check - /srvs/hold: 9678351 KB disk space available, using 9678351 KB. ERROR: /dev/nrst0: no tape online. (expecting a new tape) NOTE: skipping tape-writable test. Server check took 0.005 seconds. Amanda Backup Client Hosts Check WARNING: test.ru: selfcheck request timed out. Host down? Client check: 1 host checked in 30.002 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) Would you be so kind to promt me how selfcheck check is host down or up? What algorithm do Amanda use for checking? > > > Mary N Koroleva wrote: > > >According to Ignacio Dosil Lago: > > > >>Strange. > >>Was inetd up when you ran amdump? > >> > > > >Yes, certaily. > > > >>Did you grant access to the tape server at the client via .amandahosts? > >> > > > >test.ru:/etc/amanda | 554 >less .amandahosts > > > >test.ru amanda > > > >Have I filled .amandahosts correctly? > > > > > >>Have you checked inetd config. file? > >> > > > >Yes, certaily. > > > >test.ru:/etc/amanda | 555 >less /etc/inetd.conf | grep -i amanda > >amanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad > >amandaidx stream tcp nowait amanda /usr/contrib/lib/amanda/amindexd > > amindexd > >amidxtape stream tcp nowait amanda /usr/contrib/lib/amanda/amidxtap > >ed amidxtaped > >kamanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad > >-krb4 > > > >>Perhaps you left behind some of this issues. > >> > >> > >>Mary N Koroleva wrote: > >> > >>>Hi, > >>> > >>>I run amcheck - it's all right. After I try to run amdump. > >>> > >>>test.ru:/etc/amanda/test/log | 513 >less amdump.1 > >>>amdump: start at Mon Mar 4 17:59:34 MSK/MSD 2002 > >>>planner: pid 6649 executable /usr/contrib/lib/amanda/planner version 2.4.1p1 > >>>planner: build: VERSION="Amanda-2.4.1p1" > >>>planner:BUILT_DATE="Sun Oct 8 22:38:54 GMT 2000" > >>>planner:BUILT_MACH="BSD/OS hephaestus.BSDI.COM 4.2 BSDI BSD/OS 4.2 Kerne > >>>l #2: Mon Aug 21 14:49:26 MDT 2000 [EMAIL PROTECTED]:/home/polk/sys/com > >>>pile/HEPHAESTUS i386" > >>>planner:CC="shlicc" > >>>planner: paths: bindir="/usr/contrib/bin" sbindir="/usr/contrib/sbin" > >>>planner:libexecdir="/usr/contrib/lib/amanda" > >>>planner:mandir="/usr/contrib/man" CONFIG_DIR="/etc/amanda" > >>>planner:DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/r" > >>>planner:DUMP="/sbin/dump" RESTORE="/sbin/restore" > >>>planner:SAMBA_CLIENT="/usr/contrib/bin/smbclient" > >>>planner:COMPRESS_PATH="/usr/contrib/bin/gzip" > >>>planner:UNCOMPRESS_PATH="/usr/contrib/bin/gzip" > >>>planner:MAILER="/usr/bin/Mail" > >>>planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" > >>>planner:DEFAULT_TAPE_SERVER="localhost" > >>>planner:DEFAULT_TAPE_DEVICE="/dev/nrst0" HAVE_MMAP > >>>planner:LOCKING=POSIX_FCNTL DEBUG_CODE BSD_SECURITY KRB4_SECURITY > >>>planner:SERVER_HOST_PRINCIPLE="amanda" > >>>planner:SERVER_HOST_INSTANCE="" > >>>planner:SERVER_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >>>planner:CLIENT_HOST_PRINCIPLE="rcmd" > >>>planner:CLIENT_HOST_INSTANCE="" > >>>planner:CLIENT_HOST_KEY_FILE="/etc/kerberosIV/srvtab" > >>>planner:TICKET_LIFETIME="128" CLIENT_LOGIN="operator" FORCE_USERID > >>>planner:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" > >>>planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > >>>READING CONF FILES... > >>>startup took 0.011 secs > >>> > >>>SETTING UP FOR ESTIMATES... > >>>setting up estimates for test.ru:/dev/sd0a > >>>test.ru:/dev/sd0a overdue 11751 days for level 0 > >>>setup_estimate: test.ru:/dev/sd0a: command 0, options: > >>> last_level -1 next_level0 -11751 level_days 0 > >>> getting estimates 0 (0) -1 (-1) -1 (-1) > >>>setting up estimates took 0.000 secs > >>> > >>>GETTING ESTIMATES... > >>>driver: pid 6650 executable /usr/contrib/lib/amanda/driver version 2.4.1p1 > >>>driver: send-cmd time 0.009 to taper: START-TAPER 20020304 > >>>taper: pid 6651 executable taper version 2.4.1p1 > >>>driver: started dumper0 pid 6653 > >>>driver: started dumper1 pid 6654 > >>>driver: started dumper2 pid 6655 > >>>driver: started dumper3 pid 6656 > >>>dumper: pid 6653 executable dumper version 2.4.1p1, using port 1021 > >>>dumper: pid 6654 executable dumper version 2.4.1p1, using port 1022 > >>>dumper: pid 6655 executable dumper version 2.4.1p1, using port 1023 > >>>dumper: pid 6656 executable dumper version 2.4.1p1, using port 512 > >>>taper: read label `Daily01' date `X' > >>>t
Backups running fine, but getting empty reports
The body of the daily backup report is always empty. Is there a /tmp/amanda/ file I can poke into to see if there's some file permission problem? Graham
character translations with smbclient (was Share Access)
Hi,
Thanks for the tip.
I went to the Netherlands last week so didn't get a chance to try this
out until this week.
I upgraded to samba 2.2.3a and that helped. The bad news is that it only
solved some of the problems. The file link to the floppy backs up now as
the translation of the link is consistent somehow, but the character
translation on the $ (dollar sign) and £ (pound sign) is not working
yet. Admittedly it is translated to something different than when using
samba 2.2.2, but it still can't be backed up. :(
Am I sufficiently off topic yet to be completely flamed of the amanda
list? Any one else seen this whilst using amanda?
TIA,
Tom
> -Original Message-
> From: Paul Bijnens [mailto:[EMAIL PROTECTED]]
> Sent: 22 February 2002 13:30
> To: Thomas Robinson
> Cc: Amanda-Users (E-mail)
> Subject: Re: Share Access
>
>
>
>
> Thomas Robinson wrote:
> >
> > I'm trying to backup some Windows shares and keep getting
> these STRANGE
> > reports from amamnda:
> >
> > I've found character substitutions on the some filenames
> where some of
> > the characters in the filenames are special characters:
> >
> > $ becomes oe ('dollar sign' becomes 'oe' diphthong)
> > ½ becomes « ('1/2' becomes '<<' double left chevrons)
> >
> > '? ERRDOS - ERRbadfile opening remote file' on files where these
> > substitutions occur.
>
>
> Speaking for my experience: it happens only with Samba 2.2.2.
> When I noticed it, I downgraded to samba 2.2.0 again, and the problem
> went away. Recently Samba 2.2.3a is out, and it works fine there too.
>
> I mentioned this problem on the samba list about half a year ago,
> but never got any meaningful replies, so I'm not sure if it really is
> the problem. Anyway since I upgraded to 2.2.3a last week, the problem
> did not reappear again. YMMV.
>
>
> --
> Paul Bijnens, Lant Tel +32
> 16 40.51.40
> Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32
> 16 40.49.61
> http://www.lant.com/ email:
> [EMAIL PROTECTED]
> **
> *
> * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z,
> ^Q, F6, *
> * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close,
> bye, /bye, *
> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort,
> hangup, *
> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$,
> shutdown, *
> * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A,
> ...*
> * ... "Are you sure?" ... YES ... Phew ... I'm out
> *
> **
> *
>
Re: FileTooLargeError-2.4.2p2
Perhaps your system has a 2 GB file size limit. Try setting chunksize
to 1 Gb in the holding disk section of amanda.conf.
Frank
--On Tuesday, March 05, 2002 05:44:35 -0800 ThomasRatliffDDS <[EMAIL PROTECTED]>
wrote:
>
> /usr partition fails to write to tape although it seems to dump to the
> holding disk OK. Nothing is left in the holding disk
> (/var/local/storage/hold_amanda).
>
> amanda 2.4.2p2
> Travan 10/20Gb uncompressed/compressed tape
> The tape definition received from running tapetype
> define tapetype TRAVAN {
> comment "just produced by tapetype program"
> comment "Tecmar Travan NS20 - 3M Travan 20 Tape"
> length 9935 mbytes
> filemark 30 kbytes
> speed 938 kbytes
>
> From "df"
>
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/sda5 1981990 1456881422659 78% /
> /dev/sda130719 11083 18050 39% /boot
> /dev/hda221472 2259 18105 12% /boothda
> /dev/hda1 1939104823136 1115968 43% /dosC
> /dev/sda6 3465433 2180149 1106034 67% /usr
> /dev/sda7 1685149108162 1489897 7% /var
>
> /dev/hdg1 2767240420 26266700 1%
> /var/local/storage/hold_amanda
>
>
>
> Date: Mon, 4 Mar 2002 06:01:52 -0800
> From: Red Hat Linux User <[EMAIL PROTECTED]>
> Message-Id: <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: buddies.orthodontists.info AMANDA MAIL REPORT FOR March 4, 2002
> Status: RO
>
> These dumps were to tape buddies_full-01.
> The next tape Amanda expects to use is: buddies_full-02.
>
> FAILURE AND STRANGE DUMP SUMMARY:
> buddies/usr lev 0 FAILED ["data write: File too large"]
>
>
> STATISTICS:
> Total Full Daily
>
> Estimate Time (hrs:min)0:06
> Run Time (hrs:min) 1:52
> Dump Time (hrs:min)0:50 0:50 0:00
> Output Size (meg)2205.2 2205.20.0
> Original Size (meg) 2205.2 2205.20.0
> Avg Compressed Size (%) -- -- --
> Filesystems Dumped5 5 0
> Avg Dump Rate (k/s) 754.4 754.4--
>
> Tape Time (hrs:min)1:00 1:00 0:00
> Tape Size (meg) 2205.4 2205.40.0
> Tape Used (%) 22.2 22.20.0
> Filesystems Taped 5 5 0
> Avg Tp Write Rate (k/s) 622.1 622.1--
>
> ^L
> FAILED AND STRANGE DUMP DETAILS:
>
> /-- buddies/usr lev 0 FAILED ["data write: File too large"]
> sendbackup: start [buddies:/usr level 0]
> sendbackup: info BACKUP=/bin/gtar
> sendbackup: info RECOVER_CMD=/bin/gtar -f... -
> sendbackup: info end
> \
>
> ^L
> NOTES:
> planner: Adding new disk buddies:/usr.
> taper: tape buddies_full-01 kb 2258304 fm 5 [OK]
>
> ^L
> DUMP SUMMARY:
> DUMPER STATSTAPER STATS
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> -- -
> buddies / 0 14583361458336 -- 22:051100.8 40:03 606.8
> buddies /boot 0 11072 11072 --0:043043.4 0:18 633.3
> buddies /boothda02272 2272 --0:03 776.6 0:05 438.1
> buddies /dosC 0 679136 679136 -- 26:11 432.4 18:06 625.7
> buddies /usr0 FAILED ---
> buddies /var0 107328 107328 --1:311175.2 1:58 906.4
>
> (brought to you by Amanda version 2.4.2p2)
>
> AND FROM SENDBACKUP.XXDEBUG
>
> sendbackup: debug 1 pid 1989 ruid 20 euid 20 start time Tue Mar 5
> 04:06:59 2002/usr/lib/amanda/sendbackup: version 2.4.2p2
> sendbackup: got input request: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS
>| ;bsd-auth;index;
> parsed request as: program `GNUTAR'
> disk `/usr'
> lev 0
> since 1970:1:1:0:0:0
> opt `|;bsd-auth;index;'
> sendbackup: try_socksize: send buffer size is 65536
> sendbackup: stream_server: waiting for connection: 0.0.0.0.1086
> sendbackup: stream_server: waiting for connection: 0.0.0.0.1087
> sendbackup: stream_server: waiting for connection: 0.0.0.0.1088
> waiting for connect on 1086, then 1087, then 1088
> sendbackup: stream_accept: connection from 192.168.1.1.1089
> sendbackup: stream_accept: connection from 192.168.1.1.1090
> sendbackup: stream_accept: connection from 192.168.1.1.1091
> got all connections
> sendbackup-gnutar: doing level 0 dump as listed-incremental to
> /usr/var/amanda/gnutar-lists/buddies_usr_0.new
> sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT
> sendbackup: spawning /usr/lib/amanda/runtar in pipeline
> sendbackup: argument list: gtar --create --file - --directory /usr
> --one-file-system --listed-incremental
> /usr/var/
Can you build amanda on one computer and move it to another?
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
summary: my experience of Spectra Logic treefrog on E250 running Solaris 8
Amanda on Solaris 8 with Spectra Logic Treefrog(2000).
Hardware: Sun Enterprise 250, Spectra Logic Treefrog with AIT-1 tape(SCSI
interface).
Software: Solaris 8, amanda 2.4.3b2, tar 1.13.19, mtx 1.2.16rel
This document shows how I got Treefrog to work under solaris 8. Big thank
to Stephen Carville on Amanda-user mailing list. He wrote a terrific
changer glue script for Treefrog in perl. Without his help, it would
probably take another light year to get my own backup working.
Disclaimer: This document is solely based on my own experience. I do NOT
guarantee the methods will work in your environment.
Attachment description:
chg-spectra.pl- Stephen Carville's perl changer glue script
changer.conf-changer's configuration file for chg-2.pl
amanda.conf-sample configuration file given to me by Stephen
Carville
barlabler.pl -perl script I wrote to label tape according to its
barcode.
Here it goes:
1. Install your treefrog. Remeber to set the configuration dial in the
back of the Treefrog to "9" so it works properly under Solaris. Read your
Treefrog manual on how to change the dial. You might need to modify
/dev/kernel/sgen.conf to have changer(robotic arm) working properly. The
tape drive should work without any modification. Remeber to reboot after
sgen.conf modification. If install correctly, your changer device
descriptor file would be in /dev/scsi/changer, and device would be in
/dev/rmt (See attachment)
2. Install MTX. It's a program that controls SCSI media changer devices.
You can download it from sourceforge. Confirm that you can use 'mtx' to
control your changer and 'mt' to control your tape device. Read the man
page on how to use those two commands.
3. Configure and install amanda. Follow docs/INSTALL, and you should have
no problem setting it up. Remember to copy chg-spectra.pl to Amanda's
changer glue script directory, default is in /usr/local/libexec.
4. Set up your backup configuration files by copying the default
amanda.conf.chg-scsi file from /usr/local/etc/amanda to
/usr/local/etc/amanda//amanda.conf. Change chg-scsi script
reference in amanda.conf to attached changer glue script(chg-spectra, see
attached sample amanda.conf) and modify tapedev and changerdev to point to
correct device files. Make sure you point the log, index, and debug
directories to appropriate place. Especially debug files, they're very
useful to debug amanda.
5. Amanda needs to label your tapes before it can write to them. If you
would like the labels to match your barcode, use the attached perl script
that I wrote(barlabeler). Make sure 'amlabel' and 'mtx' are in your path,
they're in "/usr/local/sbin" by default. I like to label them with barcode
because it's easier for me to locate tapes when I need them to restore. I
wont need a separate label for tapes. If you do not want to match labels
with the barcodes, you can label the tapes by manually issue amlabel command
to each tape.
6. Run 'amcheck ' and correct every errors it reports back.
Amanda doesn't create some directories and files by itself, so you'll have
to do it yourself. Stuff like log directory, index directory, gnu-tar
directory, or /etc/amandates file. You also need to make sure permission on
those directories and files are set correctly. Debug files are very useful
on figuring out where went wrong, so please consult them first when you run
into problem.
7. When 'amcheck' does not return any more error, you can run some test
dump. Once you make sure you can run dump and restore correctly, you can
delete log directory's content, index directory's content(if you setup
index), and the file "tapelist", then amanda will run fresh from scratch
again.
#!/usr/local/bin/perl
# Mark Lin. 2/25/2002
# Works with MTX version 1.2.16rel under solaris.
# This little perl script label every tape same as their barcode.
# It works by using mtx staus to get the barcode and use amlabel
# to label each tape with barcode.
use strict;
my (@result, @test, $line, $line2, $stat);
if (!@ARGV) {
print "Usage: barlabler \n";
exit 1;
}
@result = `mtx status 2>&1`;
foreach $line (@result) {
if ($line =~ m/Data Transfer Element 0:Full \(Storage Element (\d+).*([EC]\d{5})/)
{
# preserve the slot number and barcode
#print "$1, $2\n";
@test = `amlabel @ARGV[0] $2`;
if ($_) {
print "Label #2 Failed. reason below:\n";
foreach $line2 (@test) {
print "$line2";
}
}
else { print "label $2 in drive $1 succeed\n";
}
next;
}
# Change your regular expression if your tapes has different barcode.
if ($line =~ m/\s+Storage Element (\d+).*=([EC]\d{5})/) {
#print "slot: $1 volume: $2\n";
@test = `amlabel @ARGV[0] $2 slot $1`;
if ($_) {
print "Label #2 Failed. reason below:\n";
foreach $line2 (@test) {
print "$line2";
}
}
else {
Exabyte 210
Hello, I am using Exabyte 210 with EXB 8900 as the tape drive in debian 3.0. I can configure the Exabyte 210 libary but failed to configure the EXB 8900. So does anybody know how to configure the tape drive in linux. I am running 2.4.18 kernel. I cannot see the tape device in /proc/scsi/scsi. but only can see the 210 libary. Thanks in advance Arunav Mandal.
Re: make fails building krb4 support
On Mon, 4 Mar 2002, Ruth Anne wrote: I know it's bad form to followup your own message, but... > > I am attempting to make Amanda 2.4.2pl2 with krb4 support > server/client on NetBSD1.5.1_ALPHA; KerberosV 1.2.3 > > While Making all in common-src: > > ... > gcc -g -O2 -I/usr/local/krb5/include > -I/usr/local/krb5/include/kerberosIV -L/usr/local/krb5/lib -o genversion >genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lm -ltermcap -lkrb4 >-lkrb5 -lcrypto -ldes425 -lcom_err > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `init_common': > init_ctx.o(.text+0x13c): undefined reference to `krb5_c_random_seed' > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function >`krb5_set_default_in_tkt_ktypes': > init_ctx.o(.text+0x3de): undefined reference to `valid_enctype' > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `get_profile_etype_list': > init_ctx.o(.text+0x647): undefined reference to `krb5_string_to_enctype' > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function >`krb5_set_default_tgs_enctypes': > init_ctx.o(.text+0x75e): undefined reference to `valid_enctype' > collect2: ld returned 1 exit status > *** Error code 1 > > Stop. > *** Error code 1 I got my answer from the kerberos mailing list. At least in KerberosV 1.2.3, there was a library name change; crypto changed to k5crypto. So in the following lines in the configure file: KRB4LIBS="-lkrb4 -lkrb5 -lcrypto -ldes425 -lcom_err" KRB4LIBS="-lkrb4 -lcrypto -ldes425" change lcrypto to lk5crypto. This is in addition to the change that needs to be made in the configure file of libcrypto to libk5crypto. --Ruth Anne
Question about amreport.....
I did a full backup for production and I'mn working on the estetics right now. Since my backups span two tapes..I would of expected to seperate tape labels to be printed. Instead there was one label with the tape label divided by a comma. Is this correct Second when I attempted to adjust the label type to a 8.5x11...I should of been able to do the following: amreport Monthly -l (logfile name) -p /var/adm/amanda/postscript/8.5x11.ps This should of taken the config from the amanda.conf for Monthly and printed out the adjusted label. No such liuck...it just sent tthe report to myself via e-mail. Am I missing something??? Don
OnStream ADR2.60ide
Hi,
Here is the result of tapetype for the OnStream ADR2.60 ide tape
drive.
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 28100 mbytes
filemark 57 kbytes
speed 638 kps
--
Patrice Hamelin, ing. M.Sc.A.
Systems Analyst
Cray Canada Corp.
Re: character translations with smbclient (was Share Access)
Thomas Robinson wrote:
>
> > > $ becomes oe ('dollar sign' becomes 'oe' diphthong)
> > > ½ becomes « ('1/2' becomes '<<' double left chevrons)
>
> I upgraded to samba 2.2.3a and that helped. The bad news is that it only
> solved some of the problems. The file link to the floppy backs up now as
> the translation of the link is consistent somehow, but the character
> translation on the $ (dollar sign) and £ (pound sign) is not working
> yet. Admittedly it is translated to something different than when using
> samba 2.2.2, but it still can't be backed up. :(
I just noticed last week that the upgrade to 2.2.3a worked for
all my clients except the Win95 clients (only 2 left :-).
When using 2.2.2 they did not complain, and now they complain
for filenames as "\télécom.doc", with errmsg:
ERRDOS - ERRbadfile opening remote file
Downgrading to 2.2.2 makes Win95 work ok, but fails on Win2K :-(
You can't win them all.
Something you may have to look at:
What codepage is the client using?
(type "chcp" in a dos prompt)
What characterset is de Unix server configured to?
(see the "character set" parameter in smb.conf)
I have mine set to codepage 850 for the clients,
and 'character set = ISO8859-1' in smb.conf.
See the explanation in "man smb.conf" on character sets.
It may be completely unrelated, as I don't know if smbclient
uses these settings at all.
> Am I sufficiently off topic yet to be completely flamed of the amanda
> list? Any one else seen this whilst using amanda?
I'm sure many Amanda users have the problem, but it surely is a
Samba problem. Just try smbclient -T... by hand on a small directory
to experiment:
Amanda uses this command:
smbclient '\\pc\share' -U username -E -W workgroup -d0 -Tqca - | ...
Depending on samba version (2.2.0 - 2.2.2 - 2.2.3a), you get
different errors on filenames with non-USascii characters.
ps. I'm not on the Samba list, please CC me too.
--
Paul Bijnens, Lant Tel +32 16 40.51.40
Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61
http://www.lant.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Re: Question about amreport.....
BTW..it is defined in my amanda.conf as a label type Don Potter wrote: > I did a full backup for production and I'mn working on the estetics > right now. > > Since my backups span two tapes..I would of expected to seperate tape > labels to be printed. Instead there was one label with the tape > label divided by a comma. Is this correct > > > Second when I attempted to adjust the label type to a 8.5x11...I > should of been able to do the following: > > amreport Monthly -l (logfile name) -p > /var/adm/amanda/postscript/8.5x11.ps > > This should of taken the config from the amanda.conf for Monthly and > printed out the adjusted label. No such liuck...it just sent tthe > report to myself via e-mail. > > > Am I missing something??? > > Don
help for tape changer problem
Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! & HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get "amcheck-server: could not get changer info: open: /dev/sg0: success" -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger "chg-scsi" tapedev "0" changerfile "etc/amanda/DailySet1/changer.conf" changerdev "dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
Tapelist
Hi Everyone Again a general question. I added some tapes to our cycle, but in such a way that my tapelist looks as follows: 20020305 Weekly1 reuse 20020302 Weekly6 reuse 20020228 Weekly5 reuse 20020226 Weekly4 reuse 20020223 Weekly8 reuse 20020221 Weekly7 reuse 20020218 Weekly3 reuse 20020216 Weekly2 reuse So you see I use tapes in the order 1,2,3,7,8,4,5,6 I'd like this to be 1,2,3,4,5,6,7,8, for the sake of the guy taking over from me not being confused, and also for my left-brain mentality to not crinch every time amanda asks for tape 7 after tape 3. :) Any ideas? Another thing, if I'd now like to add a tape, Weekly9, after Weekly8, is it okay to update amanda.conf today, and rigging the tapelist file as follows: 20020305 Weekly1 reuse 20020302 Weekly6 reuse 20020228 Weekly5 reuse 20020226 Weekly4 reuse 20020224 Weekly9 reuse <--- Added this entry with fictitious date 20020223 Weekly8 reuse 20020221 Weekly7 reuse 20020218 Weekly3 reuse 20020216 Weekly2 reuse Thanks! Jan Boshoff
Re: Can you build amanda on one computer and move it to another?
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 > Sure, assuming same OS/etc. If the second box is only a client you could just build that part (--client-only or something like that). I think in general you don't even need to recompile the source, once everything is built you could tar it up and copy it over, but your environment will dictate that I'm sure. -d ~ Doug Silver Network Manager Quantified Systems, Inc ~
Re: Question about amreport.....
On Tue, 5 Mar 2002 at 11:00am, Don Potter wrote > Since my backups span two tapes..I would of expected to seperate tape > labels to be printed. Instead there was one label with the tape label > divided by a comma. Is this correct It's certainly not desired behavior... > Second when I attempted to adjust the label type to a 8.5x11...I should > of been able to do the following: > > amreport Monthly -l (logfile name) -p /var/adm/amanda/postscript/8.5x11.ps > > This should of taken the config from the amanda.conf for Monthly and > printed out the adjusted label. No such liuck...it just sent tthe > report to myself via e-mail. > Nope. From the amreport man page: -p postscriptfile Send the postscript output to the file postscript file instead of to the lpr(1) command. This option has an effect only if the lbl-templ directive is specified in amanda.conf. IOW, it redirected the postscript output (that is, the tape label that would normally be printed) to the named file -- you just overwrote the 8.5x11 label template... You need to change lbl-templ in amanda.conf to change the type of label that gets printed. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Question about amreport.....
I figured out the second question...it was dumping the postscript file in the log directory...big time goof...and aopon further reflection...I'm blowin smoke So ignore the idiot that resides in the Big Green Pickle Don Joshua Baker-LePain wrote: >On Tue, 5 Mar 2002 at 11:00am, Don Potter wrote > >>Since my backups span two tapes..I would of expected to seperate tape >>labels to be printed. Instead there was one label with the tape label >>divided by a comma. Is this correct >> > >It's certainly not desired behavior... > >>Second when I attempted to adjust the label type to a 8.5x11...I should >>of been able to do the following: >> >>amreport Monthly -l (logfile name) -p /var/adm/amanda/postscript/8.5x11.ps >> >>This should of taken the config from the amanda.conf for Monthly and >>printed out the adjusted label. No such liuck...it just sent tthe >>report to myself via e-mail. >> >Nope. From the amreport man page: > > -p postscriptfile > Send the postscript output to the file postscript > file instead of to the lpr(1) command. This option > has an effect only if the lbl-templ directive is > specified in amanda.conf. > >IOW, it redirected the postscript output (that is, the tape label that >would normally be printed) to the named file -- you just overwrote the >8.5x11 label template... > >You need to change lbl-templ in amanda.conf to change the type of label >that gets printed. >
Re: amdump failed, Request to test.ru timed out.
Check in /tmp/amanda for debugging files. Also do a 'kill -HUP' on the inetd process to make sure it rereads its configuration, and then run 'amcheck -c test'. Did you compile Amanda to use fully qualified hostnames -- if so make sure that you have that in the amandahosts file, you can even put both in there for now. In my experience, it's usually forgetting to HUP inetd after adding in the amanda entries. If there's a problem with the .amandahosts, Amanda will complain about permissions, not the host being down. -doug On Tue, 5 Mar 2002, Mary N Koroleva wrote: > According to Ignacio Dosil Lago: > > I see ... .amandahosts is correctly filled but ... > > Where is the amanda user home directory? Is .amandahosts there? It should. > > (Hope this questions not to be too silly but I am a newby :-)) > > Yes, certainly ;-) > > test.ru:/etc/amanda | 599 >amcheck test > Amanda Tape Server Host Check > - > /srvs/hold: 9678351 KB disk space available, using 9678351 KB. > ERROR: /dev/nrst0: no tape online. >(expecting a new tape) > NOTE: skipping tape-writable test. > Server check took 0.005 seconds. > > Amanda Backup Client Hosts Check > > WARNING: test.ru: selfcheck request timed out. Host down? > Client check: 1 host checked in 30.002 seconds, 1 problem found. > > (brought to you by Amanda 2.4.1p1) > > Would you be so kind to promt me how selfcheck check > is host down or up? What algorithm do Amanda use for > checking? > > > > > > > Mary N Koroleva wrote: > > > > >According to Ignacio Dosil Lago: > > > > > >>Strange. > > >>Was inetd up when you ran amdump? > > >> > > > > > >Yes, certaily. > > > > > >>Did you grant access to the tape server at the client via .amandahosts? > > >> > > > > > >test.ru:/etc/amanda | 554 >less .amandahosts > > > > > >test.ruamanda > > > > > >Have I filled .amandahosts correctly? > > > > > > > > >>Have you checked inetd config. file? > > >> > > > > > >Yes, certaily. > > > > > >test.ru:/etc/amanda | 555 >less /etc/inetd.conf | grep -i amanda > > >amanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad > > >amandaidx stream tcp nowait amanda /usr/contrib/lib/amanda/amindexd > > > amindexd > > >amidxtape stream tcp nowait amanda /usr/contrib/lib/amanda/amidxtap > > >ed amidxtaped > > >kamanda dgram udp waitamanda /usr/contrib/lib/amanda/amandad amandad > > >-krb4 > > > > > -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
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]
difference in tape devices question
Can anyone tell me the difference between the following no-rewind tape devices on Linux? I can't seem to find any info anywhere. /dev/nst0 /dev/nst0a /dev/nst0l /dev/nst0m Thanks, Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
Re: Tapelist
Sorry, I just found my question in the FAQ. Please ignore and forgive me for asking before reading! Thanks Jan Jan Boshoff wrote: > Hi Everyone > > Again a general question. I added some tapes to our cycle, but in such > a way that my tapelist looks as follows: > > 20020305 Weekly1 reuse > 20020302 Weekly6 reuse > 20020228 Weekly5 reuse > 20020226 Weekly4 reuse > 20020223 Weekly8 reuse > 20020221 Weekly7 reuse > 20020218 Weekly3 reuse > 20020216 Weekly2 reuse > > So you see I use tapes in the order 1,2,3,7,8,4,5,6 > > I'd like this to be 1,2,3,4,5,6,7,8, for the sake of the guy taking over > from me not being confused, and also for my left-brain mentality to not > crinch every time amanda asks for tape 7 after tape 3. :) > > Any ideas? > > Another thing, if I'd now like to add a tape, Weekly9, after Weekly8, is > it okay to update amanda.conf today, and rigging the tapelist file as > follows: > > 20020305 Weekly1 reuse > 20020302 Weekly6 reuse > 20020228 Weekly5 reuse > 20020226 Weekly4 reuse > 20020224 Weekly9 reuse <--- Added this entry with fictitious date > 20020223 Weekly8 reuse > 20020221 Weekly7 reuse > 20020218 Weekly3 reuse > 20020216 Weekly2 reuse > > Thanks! > Jan Boshoff
Re: Can you build amanda on one computer and move it to another?
If you're talking about making a client, why not just use the binary you created for the first box? We have 53 boxes of different genre running amanda. Our backup server is a Sun box running Solaris 6. A bunch of our clients are Sun boxes running Solaris 8 and we automount the amanda directories to those systems and use the same binary to back up ALL of them. Am I missing something in your question? Wayne Richards > 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
Re: difference in tape devices question
On Tue, 5 Mar 2002, Davidson, Brian wrote: > Can anyone tell me the difference between the following no-rewind tape > devices on Linux? I can't seem to find any info anywhere. > > /dev/nst0 > /dev/nst0a > /dev/nst0l > /dev/nst0m I think the -l and -m notations instruct the system to send information in low and medium compressed formats, respectively. I don't know what the -a means. - Eric
Build dies trying to make amoverview
I am attempting to make amanda 2.4.2p2 on a NetBSD 1.5_ALPHA system The make dies with the following message: cat amcheckdb.sh > amcheckdb chmod a+x amcheckdb cat amcleanup.sh > amcleanup chmod a+x amcleanup cat amdump.sh > amdump chmod a+x amdump make: don't know how to make amoverview. Stop *** Error code 1 I googled, and discovered that this is fixed in the pkgsrc for amanda, but I can't use the pkgsrc because I need to build amanda with kerberos. Any idea what I need to make this work, or how I can not build amoverview, as I am unlikely to use it? Thanks for any help, --Ruth Anne
Problem after upgrading OS
Hello! Last week I upgraded the OS of my backup-server from FreeBSD 4.3 to 4.5. After that there has been one unpleasant change in the way that Amanda 2.4.2p1 behaves on that server. I'm using the chg-manual script with HP DDS-3 drive (HP C1537A) which the system sees as /dev/nsa0. The problem appears if I forget to change the tape before the nightly backup starts. Before the upgrade it worked the way it should: it sent me mail once in a hour to insert the correct tape, and once I got to work and inserted it, the backup proceeded automatically. Now, after the upgrade, Amanda doesn't accept the tape I insert even though it is the correct one. I have to kill all the amanda processes and run amcleanup. Then I manually start amdump and it runs fine with the same tape. If the right tape is in drive when the backup start time arrives, the backup runs without problems. This has happened twice now with two different tapes. When I watch the changer.debug I can see how the tape is rewound, the header read and then the 'mt offline' command is issued which ejects the tape... Looks like the changer just decides that this isn't the right tape... What might cause such a problem? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Would a fly without wings be called a walk?
Re: Backups running fine, but getting empty reports
Graham Dunn <[EMAIL PROTECTED]> writes: > The body of the daily backup report is always empty. Is there a > /tmp/amanda/ file I can poke into to see if there's some file > permission problem? > > Graham Graham, Did you change your "columnspec" parameter? Especially "-1" values seem to be buggy in 2.4.2. I'd do an amreport and check if it segfaults. Database entries and recovery are still ok. HTH, Johannes Nieß
