test
-- Porqué usar una base de datos relacional cualquiera, si podés usar PostgreSQL? - Martín Marqués |[EMAIL PROTECTED] Programador, Administrador, DBA | Centro de Telematica Universidad Nacional del Litoral -
no dump from local disks
I'm having problems with the dumps from the local disks of one of our amanda
servers. We have on that server about 12 partitions from remote servers to
backup, and the all go great, except the local disks, so now I'm trying to do
a backup of only those partitions (the local disks) and I got this:
root@cdserv /tmp/amanda $ less amidxtaped.debug
amidxtaped: debug 1 pid 1058 ruid 2 euid 2 start time Tue Mar 12 09:36:00 2002
amidxtaped: version 2.4.1p1
EOF reached
amidxtaped: pid 1058 finish time Tue Mar 12 09:36:05 2002
The mail amdump sent me said this:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape Diario06.
Tonight's dumps should go onto 1 tape: Diario07.
FAILURE AND STRANGE DUMP SUMMARY:
taper: FATAL syncpipe_get: w: unexpected EOF
cdserv /dev/dsk/c1t6d0s3 lev 0 FAILED [dump to tape failed]
cdserv /dev/dsk/c1t6d0s0 RESULTS MISSING
cdserv /currents/2001/ RESULTS MISSING
cdserv /currents/2002/ RESULTS MISSING
and my disklist looks like this:
# Nueva config. para el nuevo
cdserv /dev/dsk/c1t6d0s3 incroot -1 local
cdserv /dev/dsk/c1t6d0s0 incroot -1 local
cdserv /currents/2001/ incroot -1 local
cdserv /currents/2002/ incroot -1 local
where incroot is this:
define dumptype global {
comment Global definitions
index yes
compress client best
#maxdump 2
holdingdisk true
record yes
}
# Definicion para discos locales **
define dumptype incroot {
global
comment Root, incremental, no HD, comp fast
holdingdisk no
priority high
dumpcycle 4
}
Any idea on why this isn't working?
P.D.: As you see, I'm on Amanda-2.4.1pl1
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
-
exclude list
Does the exclude list file live on the server or client, or both? Jeff
Re: exclude list
On Tue, 12 Mar 2002 at 10:41am, Jeffrey S. Auerbach wrote Does the exclude list file live on the server or client, or both? The client, in the place specified in the amanda.conf file on the server. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: exclude list
On Tue, Mar 12, 2002 at 10:41:27AM -0500, Jeffrey S. Auerbach wrote: Does the exclude list file live on the server or client, or both? Always on the client. 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
unsubscribe
unsubscribe
Re: exclude list
On the client. Does the exclude list file live on the server or client, or both? Jeff
format of exclude list
Ok, say I want to back up some directories in /usr and I wanted to exclude the directories below. Is the format that I used below appropriate to exclude the directories and their subdirectories below? I am using gtar. ./X11R6/* ./bin/* ./compat/* ./games/* ./include/* ./lib/* ./libdata/* ./libexec/* ./local/bin/* ./local/include/* ./local/info/* ./local/lib/* ./local/libdata/* ./local/libexec/* ./local/man/* ./local/perl/* ./local/rrdtool-1.0.33/* ./local/sbin/* ./local/sc/* ./local/share/* ./local/src/* ./local/var/* ./obj/* ./ports/* ./sbin/* ./share/* ./src/* ./tmp/* ./home/vpopmail/domains ./home/vpopmail/bin ./home/vpopmail/doc/* ./home/vpopmail/include ./home/vpopmail/lib
amrecover is actig really flaky.....
I backup the /var parttion of our mail server (solaris box) using straight ufsdump with hardware compresion. I'm able to amrecover anything on that particular filesystem except for /var/mail (kind of important). They are on the same partition so I'm not crossing devices. I get the statement that the file isn't on the volume. But I can dd the file from the tape and restore it with no problem. And access it as expected. It is almost as if the index maybe corrupted, but it is the same for every single backup. I was originally doing a comp-user in my disklist, and I adjusted it to always-full. The problem persists. Could it be some underlying permission issue. I use two seperate configs (Daily and Monthly) and I know the discussions that may raise. But I was able to pull the backup off of the monthly with no problem. The only differance betweeen the two configs is that Monthly doesn't update /etc/dumpdates and that the stratoegy for all partitions is always-full. Any advice would be greatly appreciated. This doesn't make sense to me at all. Don
Huge amreport output
Hiya gang- Last night, amreport sent out a 48MB report to my admin mailing list. I've tracked down why, and the culprit looks to have been the only real change made yesterday, this being a columnspec line with all of the width fields set to -1 in length (according to the man page and config file comments, this should work). I've removed the line, and it worked fine. Upon closer inspection, having *any* fields set to -1 causes amanda to loop through the integer space, generating a blank line for every step (appears to be what's going on, at least). Anyone else seen this problem with columnspec? Didn't see anything in the FAQ. Some pieces for reference, in case anyone needs them: The removed columnspec (split for mail width): columnspec HostName=0:-1,Disk=2:-1,Level=2:-1,OrigKB=1:-1,OutKB=2:-1,\ Compress=2:-1,DumpRate=2:-1,DumpTime=2:-1,TapeTime=2:-1,TapeRate=2:-1 /var/log/messages: Mar 12 00:01:01 mir sendmail[4351]: g2C00OS04351: from=amanda, size=48742802, class=0, nrcpts=1, msgid=[EMAIL PROTECTED] m, relay=amanda@localhost build: VERSION=Amanda-2.4.2p2 BUILT_DATE=Thu Nov 15 20:05:51 UTC 2001 BUILT_MACH=Linux .databuilt.com 2.4.9 #1 Tue Sep 18 20:56:20 GMT -5 2001 i686 unknown CC=gcc paths: bindir=/usr/local/bin sbindir=/usr/local/sbin libexecdir=/usr/local/libexec mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/gtar COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail listed_incr_dir=/usr/local/var/amanda/gnutar-lists defs: DEFAULT_SERVER=.databuilt.com DEFAULT_CONFIG=YouProbablyShouldNotBeRunningThis DEFAULT_TAPE_SERVER=.databuilt.com DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amanda-2.4.3b3 and libtool on Tru64 5.0
My issue is with libtool related failures when building 2.4.3b3 I tried several things suggested to me: o Am I running configure on a clean source tree? YES, freshly unpacked. o Have I tried: + downgrading libtool? YES to 1.3.4. Then re-intalled the 1.4.2 version again. Results of build are consistently the same on both 2.4.2p2 and 2.4.3b3 source trees, with either version. + upgrading libtool to beta version? NO... All I could find was an alpha/development version. + specifying the --disable-libtool? No need with 2.4.2p2 since this problem does not occur. With 2.4.3b3, this allows compilation to not fail until later with a libtool error Here is the output of 2.4.3b3 build with the --disable-libtool specified at the configure stage: # config.status: creating config/Makefile config.status: creating Makefile config.status: creating config/config.h Making all in config make[1]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config' cd .. \ CONFIG_FILES= CONFIG_HEADERS=config/config.h \ /usr/bin/sh ./config.status config.status: creating config/config.h config.status: config/config.h is unchanged make all-am make[2]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config' make[2]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config' make[1]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config' Making all in common-src make[1]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/common-src' source='alloc.c' object='alloc.o' libtool=no \ depfile='.deps/alloc.Po' tmpdepfile='.deps/alloc.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f alloc.c || echo './'`alloc.c source='amflock.c' object='amflock.o' libtool=no \ depfile='.deps/amflock.Po' tmpdepfile='.deps/amflock.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f amflock.c || echo './'`amflock.c source='debug.c' object='debug.o' libtool=no \ depfile='.deps/debug.Po' tmpdepfile='.deps/debug.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f debug.c || echo './'`debug.c source='dgram.c' object='dgram.o' libtool=no \ depfile='.deps/dgram.Po' tmpdepfile='.deps/dgram.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f dgram.c || echo './'`dgram.c dgram.c: In function `dgram_recv': dgram.c:292: warning: passing arg 6 of `recvfrom' from incompatible pointer type source='error.c' object='error.o' libtool=no \ depfile='.deps/error.Po' tmpdepfile='.deps/error.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f error.c || echo './'`error.c source='file.c' object='file.o' libtool=no \ depfile='.deps/file.Po' tmpdepfile='.deps/file.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f file.c || echo './'`file.c source='fileheader.c' object='fileheader.o' libtool=no \ depfile='.deps/fileheader.Po' tmpdepfile='.deps/fileheader.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f fileheader.c || echo './'`fileheader.c sh ./../regex-src/mkh -o -i _REGEX_H_ ./../regex-src/regex2.h ./../regex-src/regcomp.c ./../regex-src/regexec.c ./../regex-src/regerror.c ./../regex-src/regfree.c regex.h source='match.c' object='match.o' libtool=no \ depfile='.deps/match.Po' tmpdepfile='.deps/match.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f match.c || echo './'`match.c source='protocol.c' object='protocol.o' libtool=no \ depfile='.deps/protocol.Po' tmpdepfile='.deps/protocol.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f protocol.c || echo './'`protocol.c sh ./../regex-src/mkh -o -p ./../regex-src/regcomp.c regcomp.ih source='regcomp.c' object='regcomp.o' libtool=no \ depfile='.deps/regcomp.Po' tmpdepfile='.deps/regcomp.TPo' \ depmode=gcc3 /usr/bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c `test -f regcomp.c || echo './'`regcomp.c sh ./../regex-src/mkh -o -p ./../regex-src/regerror.c regerror.ih source='regerror.c' object='regerror.o' libtool=no \
filemarkers
Hi, Now that I've added a DDS4 tape drive to my backup arsenal and will be using DDS4 tapes, I'm requestioning the filemark parameter in tapetypes. The DDS3 drive I've used all this time has had a tapetype with a filemark of 0. I believe this is what the 'tapetype' test produced and, when I checked with other tapetypes and possibly people on the list that such a value wasn't ludicrous, I went with it...and I've experienced no problems because of it. But, looking over the tapetypes in general again, this value is usual non-zero which is making me requestion my decision. Why do so many people use a non-zero filemark value (one tapetype I saw for a DLT used one over a meg)? What's the point? If 0 works fine (is this only true for me?), why ever use anything else? I'm missing the point of any advantage it serves. Just curious if anyone had any input or a good answer for this. A quick search for filemark in the archives was futile as I mostly conjured up nothing but tapetype listings instead of discussion on the matter. -- Paul Yeatman (858) 534-9896 [EMAIL PROTECTED]
