RE: amanda mail report size
> create /usr/local/src/amanda/2.4.2p1/Makefile (attached) > create /usr/local/src/amanda/2.4.2p1/config.site (attached) > create /usr/local/src/amanda/2.4.2p1/amanda-2.4.2p1.tar.gz (distribution) > cd /usr/local/src/amanda/2.4.2p1 > make >&! 0-make-log & Thank you very much Todd. > then you have a record of exactly how you configured and built amanda-X in > the Makefile and config.site. to rebuild at any time, just make again. > it's a very easy way to maintain local builds of software packages. Makes a lot of sense I will have to start doing this for other software packages regards, -Ben > Todd Pfaff \ Email: [EMAIL PROTECTED]
RE: amanda mail report size
On Fri, 16 Mar 2001, Ben Hyatt wrote:
> So, in source /usr/local/src/amanda-2.4.1p1/example/config.site
> add the CFLAGS entry, run configure and rebuild? (make clean, make && make
> install)
here's how i do it (for amanda, and similarly for other packages)...
mkdir /usr/local/src/amanda
mkdir /usr/local/src/amanda/2.4.2p1
create /usr/local/src/amanda/2.4.2p1/Makefile (attached)
create /usr/local/src/amanda/2.4.2p1/config.site (attached)
create /usr/local/src/amanda/2.4.2p1/amanda-2.4.2p1.tar.gz (distribution)
cd /usr/local/src/amanda/2.4.2p1
make >&! 0-make-log &
then you have a record of exactly how you configured and built amanda-X in
the Makefile and config.site. to rebuild at any time, just make again.
it's a very easy way to maintain local builds of software packages.
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
PACKAGE=amanda
VERSION=2.4.1p1
RELEASE=${PACKAGE}-${VERSION}
SHELL=/bin/sh
CONFIG_SITE=/usr/local/src/amanda/${VERSION}/config.site
#all: clean unpack patch build-client build-server install-client install-server
server: clean unpack patch build-server
client: clean unpack patch build-client
clean:
/bin/rm -rf ${RELEASE}
unpack:
umask 022;\
gnutar zxf ${RELEASE}.tar.gz;\
chown -R 0.0 ${RELEASE}
patch:
umask 022;\
patch -p0 -t < patches/samba2-2418.diff
build-client:
umask 022;\
cd ${RELEASE};\
CONFIG_SITE=$(CONFIG_SITE); export CONFIG_SITE;\
./configure \
--without-server \
;\
make
build-server:
umask 022;\
cd ${RELEASE};\
CONFIG_SITE=$(CONFIG_SITE); export CONFIG_SITE;\
./configure \
;\
make
install-client:
umask 022;\
cd ${RELEASE};\
make install;\
cd /usr/local/amanda/lib;\
ln -s libamanda-2.4.1p1.so.0.0.0 libamanda-2.4.1p1.so;\
ln -s libamclient-2.4.1p1.so.0.0.0 libamclient-2.4.1p1.so;\
ln -s libamserver-2.4.1p1.so.0.0.0 libamserver-2.4.1p1.so;\
ln -s libamtape-2.4.1p1.so.0.0.0 libamtape-2.4.1p1.so;\
mkdir -p /usr/local/amanda/etc/gnutar-lists;\
chown backup.backup /usr/local/amanda/etc/gnutar-lists
install-server: install-client
install: install-client
# see srcdir/examples/config.site for details
CC=cc
CFLAGS=-DIGNORE_SMBCLIENT_ERRORS
sbindir=$prefix/bin
CONFIG_DIR=$prefix/etc
DEFAULT_SERVER=amandahost
FORCE_USERID=yes
CLIENT_LOGIN=backup
SETUID_GROUP=backup
USE_RUNDUMP=yes
SAMBA_CLIENT=/usr/local/samba/bin/smbclient
GNUTAR=$prefix/libexec/gnutar
GNUTAR_LISTDIR=$CONFIG_DIR/gnutar-lists
BSD_SECURITY=yes
USE_AMANDAHOSTS=yes
RE: amanda mail report size
On Thu, 15 Mar 2001, Ben Hyatt wrote:
> I have 8 samba shares which get backed up - due to open files I get a lot
> of errors from samba.
>
> I added 2 samba shares to the disklist (previous instance had 6 samba shares
> defined) my previous reports were never this big.
you can patch amanda to be less verbose when samba (or other) errors are
encountered. you only need to do this on the samba client that is the
host for the smbclient backups. that is, if your disklist looks like:
host1 //pchost/driveC comp-user-tar
host1 //pchost/driveD comp-user-tar
host2 / comp-user
you only need to patch amanda for host1.
there are two patches you can apply that affect two different aspects of
the smbclient backup.
1) client-src/sendbackup-gnutar.c
look for this code segment:
#ifdef IGNORE_SMBCLIENT_ERRORS
/* This will cause amanda to ignore real errors, but that may be
* unavoidable when you're backing up system disks. It seems to be
* a safe thing to do if you know what you're doing. */
{ DMP_NORMAL, "^ERRDOS - ERRbadshare opening remote file", 1},
{ DMP_NORMAL, "^ERRDOS - ERRbadfile opening remote file", 1},
{ DMP_NORMAL, "^ERRDOS - ERRnoaccess opening remote file", 1},
{ DMP_NORMAL, "^ERRSRV - ERRaccess setting attributes on file", 1},
{ DMP_NORMAL, "^ERRDOS - ERRnoaccess setting attributes on file", 1},
#endif
if you define IGNORE_SMBCLIENT_ERRORS then these smbclient error messages
will be treated as DMP_NORMAL and they will not cause a full error report
to be generated (ie. amanda will output all messages from the dump if any
non-DMP_NORMAL lines are detected. this is the problem you are seeing.).
you can define IGNORE_SMBCLIENT_ERRORS in your configure stage by, for
example, putting the following in config.site:
CFLAGS=-DIGNORE_SMBCLIENT_ERRORS
2) if you don't care to see any DMP_NORMAL lines in the report, only
DMP_STRANGE lines, look at client-src/sendbackup.c for this code:
typ = parse_dumpline(str);
switch(typ) {
case DMP_NORMAL:
case DMP_SIZE:
startchr = '|';
break;
default:
case DMP_STRANGE:
startchr = '?';
break;
}
fprintf(stderr, "%c %s\n", startchr, str);
and add a "return" statement after the "case DMP_NORMAL" line:
case DMP_NORMAL:
return;
so that the fprintf is not called for DMP_NORMAL lines. the downside to
this is that you will not see any of the possibly useful DMP_NORMAL
information when there is a DMP_STRANGE error. this could make debugging
the problem more difficult. it would be useful if this was a run-time
configurable feature.
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
Re: amanda mail report size
Ben Hyatt wrote: > > > Doesn't this mean that there is something wrong with backup ? > > I have 8 samba shares which get backed up - due to open files I get a lot > of errors from samba. > > I added 2 samba shares to the disklist (previous instance had 6 samba shares > defined) my previous reports were never this big. I don't think you can control it on amanda level since the messages are generated by smbclient. Patch the smbclient ? > > -Ben > > > Yuri Pismerov, TUCOWS.COM INC.(416) 535-0123 ext. 1352 -- Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 1352 S/MIME Cryptographic Signature
RE: amanda mail report size
> Doesn't this mean that there is something wrong with backup ? I have 8 samba shares which get backed up - due to open files I get a lot of errors from samba. I added 2 samba shares to the disklist (previous instance had 6 samba shares defined) my previous reports were never this big. -Ben > Yuri Pismerov, TUCOWS.COM INC.(416) 535-0123 ext. 1352
Re: amanda mail report size
Ben Hyatt wrote: > > Ever since I rebuilt Amanda and moved it over to another box, I have noticed > that > the email report size wise is huge (9 MB). Doesn't this mean that there is something wrong with backup ? > > Didn't recall the report's to be that big on the old amanda instance I had > running. > Had an amanda alias pointing to my corp email address, but now that the > message size is so big, > it's getting rejected at the mail server (not under my control) > > I've since pointed the amanda alias to my local account(plenty of control > ;)) and get the reports fine... just takes forever to load the report up > (mutt) ;) > > Is there any options on amreport, like setting a verbose level? I'm really > only interested > in dump summary. > > Thanks, > > -Ben -- Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 1352 S/MIME Cryptographic Signature
