Re: FAILURE AND STRANGE DUMP SUMMARY
On 2007-06-18 20:53, Robert Echlin wrote: FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] Have you read/understood/checked: http://wiki.zmanda.com/index.php/Mesg_read:_Connection_reset_by_peer cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] cpu.ind.com /var/lib/mysql lev 0 was successfully retried Olivier notes that the network connection failed, at least before the estimate was finished. Also note the third line: Successfully retried. Check out what happens after that, as it may have gone on to successfully backup cpu.ind.com:/var/lib/mysql Rob -- Rob Echlin Software Development Environment Prime Espial IPTV rechlin -at- espial.com Phone: +1 613-230-4770 ext 1150 www.espial.com Espial Group Inc. Confidential Important Notice: This communication is intended to be received only by the individual or entity to whom or to which it is addressed and may contain information that is privileged, confidential and/or subject to copyright. Any unauthorized use, copying, review or disclosure of this communication is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender by reply email. Thank you for your cooperation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fedora Sent: Monday, June 18, 2007 12:23 AM To: amanda-users@amanda.org Subject: Re: FAILURE AND STRANGE DUMP SUMMARY fedora wrote: Hi guys. I am newbie here. I got problem with my Amanda. here is the result in mail report: FAILURE AND STRANGE DUMP SUMMARY: ind.ayo.com/var/lib/mysql lev 0 STRANGE STATISTICS: All OK. Showed the progress FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it | Total bytes written: 562432000 (537MiB, 7.7MiB/s) sendbackup: size 549250 sendbackup: end NOTES: planner: Full dump of ind.ayo.com:/var/lib/mysql promoted from 5 days ahead. taper: tape DailySet1-04 kb 2727712 fm 10 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - - ind.ayo -/lib/mysql 0 549250 301765.51:10 429.8 0:00 154753.5 Nothing errors in debug files. Can u guys tell me how come Amanda still complaining failed and strange whereas dump summary looks OK even I can recover the backup files. Any ideas guys?? I got new problem: These dumps were to tape DailySet1-13. The next tape Amanda expects to use is: DailySet1-14. FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] cpu.ind.com /var/lib/mysql lev 0 was successfully retried can anyone explain to me? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: FAILURE AND STRANGE DUMP SUMMARY
FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] Means that Amanda client on cpu.ind.com closed connection with Amanda server before the dump (or estimate was finished). Olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
Hi, fedora schrieb: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] Maybe the client was rebooted during the backup or xinetd restarted. cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] The server didn't send an estimate or backup, because of a maybe reboot. cpu.ind.com /var/lib/mysql lev 0 was successfully retried Everything was done fine. Amanda retried successfully. Regards Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: FAILURE AND STRANGE DUMP SUMMARY
Thanks Marc. Marc Muehlfeld wrote: Hi, fedora schrieb: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] Maybe the client was rebooted during the backup or xinetd restarted. cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] The server didn't send an estimate or backup, because of a maybe reboot. cpu.ind.com /var/lib/mysql lev 0 was successfully retried Everything was done fine. Amanda retried successfully. Regards Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11170958 Sent from the Amanda - Users mailing list archive at Nabble.com.
RE: FAILURE AND STRANGE DUMP SUMMARY
FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] cpu.ind.com /var/lib/mysql lev 0 was successfully retried Olivier notes that the network connection failed, at least before the estimate was finished. Also note the third line: Successfully retried. Check out what happens after that, as it may have gone on to successfully backup cpu.ind.com:/var/lib/mysql Rob -- Rob Echlin Software Development Environment Prime Espial IPTV rechlin -at- espial.com Phone: +1 613-230-4770 ext 1150 www.espial.com Espial Group Inc. Confidential Important Notice: This communication is intended to be received only by the individual or entity to whom or to which it is addressed and may contain information that is privileged, confidential and/or subject to copyright. Any unauthorized use, copying, review or disclosure of this communication is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender by reply email. Thank you for your cooperation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fedora Sent: Monday, June 18, 2007 12:23 AM To: amanda-users@amanda.org Subject: Re: FAILURE AND STRANGE DUMP SUMMARY fedora wrote: Hi guys. I am newbie here. I got problem with my Amanda. here is the result in mail report: FAILURE AND STRANGE DUMP SUMMARY: ind.ayo.com/var/lib/mysql lev 0 STRANGE STATISTICS: All OK. Showed the progress FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it | Total bytes written: 562432000 (537MiB, 7.7MiB/s) sendbackup: size 549250 sendbackup: end NOTES: planner: Full dump of ind.ayo.com:/var/lib/mysql promoted from 5 days ahead. taper: tape DailySet1-04 kb 2727712 fm 10 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - - ind.ayo -/lib/mysql 0 549250 301765.51:10 429.8 0:00 154753.5 Nothing errors in debug files. Can u guys tell me how come Amanda still complaining failed and strange whereas dump summary looks OK even I can recover the backup files. Any ideas guys?? I got new problem: These dumps were to tape DailySet1-13. The next tape Amanda expects to use is: DailySet1-14. FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] cpu.ind.com /var/lib/mysql lev 0 was successfully retried can anyone explain to me? -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a1 1169793 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: FAILURE AND STRANGE DUMP SUMMARY
fedora wrote: Hi guys. I am newbie here. I got problem with my Amanda. here is the result in mail report: FAILURE AND STRANGE DUMP SUMMARY: ind.ayo.com/var/lib/mysql lev 0 STRANGE STATISTICS: All OK. Showed the progress FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it | Total bytes written: 562432000 (537MiB, 7.7MiB/s) sendbackup: size 549250 sendbackup: end NOTES: planner: Full dump of ind.ayo.com:/var/lib/mysql promoted from 5 days ahead. taper: tape DailySet1-04 kb 2727712 fm 10 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - - ind.ayo -/lib/mysql 0 549250 301765.51:10 429.8 0:00 154753.5 Nothing errors in debug files. Can u guys tell me how come Amanda still complaining failed and strange whereas dump summary looks OK even I can recover the backup files. Any ideas guys?? I got new problem: These dumps were to tape DailySet1-13. The next tape Amanda expects to use is: DailySet1-14. FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] cpu.ind.com /var/lib/mysql lev 0 was successfully retried can anyone explain to me? -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11169793 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: FAILURE AND STRANGE DUMP SUMMARY
Almost files which is the extension ./databasename/*.MYI changed not only ./mysql/general_log.CSV Olivier Nicole wrote: Is there any proper mysql backup that can backup database without stopping it?? If so, I don't have to worry about it? Of course it wasn't failed but I just worried if I recover it and the database or tables might be corrupt just because Amanda detected strange. Please advice. I remember I have seen something about backuping MySQL database, look at Amanda web site. Now what is the file ./mysql/general_log.CSV ? In my run of MySQL (version 4) I do not have such a file. Is it important or not if you loose it? If it is only a log file, like the name suggests, maybe loosing it would not be so dramatic. Best regards, Olivier -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11056985 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: FAILURE AND STRANGE DUMP SUMMARY
fedora wrote: Almost files which is the extension ./databasename/*.MYI changed not only ./mysql/general_log.CSV Of course they changed. I usually try to avoid Read the documentation type responses, but I think this might be a good time to suggest it. The mysql docs tell you pretty clearly that backing up the database files directly is not going to work. You need to either dump the databases and back those up (a number of methods have been presented) or use a tool specifically designed to do them on the fly. Dustin posted a link to that a couple of days ago. LP
Re: FAILURE AND STRANGE DUMP SUMMARY
any solutions for me? fedora wrote: Hi guys. I am newbie here. I got problem with my Amanda. here is the result in mail report: FAILURE AND STRANGE DUMP SUMMARY: ind.ayo.com/var/lib/mysql lev 0 STRANGE STATISTICS: All OK. Showed the progress FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it | Total bytes written: 562432000 (537MiB, 7.7MiB/s) sendbackup: size 549250 sendbackup: end NOTES: planner: Full dump of ind.ayo.com:/var/lib/mysql promoted from 5 days ahead. taper: tape DailySet1-04 kb 2727712 fm 10 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - - ind.ayo -/lib/mysql 0 549250 301765.51:10 429.8 0:00 154753.5 Nothing errors in debug files. Can u guys tell me how come Amanda still complaining failed and strange whereas dump summary looks OK even I can recover the backup files. Any ideas guys?? -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11021151 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: FAILURE AND STRANGE DUMP SUMMARY
FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it Means that the file mysql/general_log.CSV was getting modified while tar was trying to save it. Most probably this file has not been included (or included wrongly) in your amanda backup. You have to understand that it takes some amount of time for tar to make a copy of a *big* file. If that big file is changing often, it is very likely it will be changing while tar is trying to copy it. There is very little you can make about it, except stopping mysql while you are doing th backup :) Actually, this is only a STRANGE, not a FAIL. A bit of auto promotion, this page https://wwws.cs.ait.ac.th/amanda/operator.shtml reccords a number of Amanda error message and the explanation for it, and possible recovery action. Olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
Is there any proper mysql backup that can backup database without stopping it?? If so, I don't have to worry about it? Of course it wasn't failed but I just worried if I recover it and the database or tables might be corrupt just because Amanda detected strange. Please advice. Olivier Nicole wrote: FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it Means that the file mysql/general_log.CSV was getting modified while tar was trying to save it. Most probably this file has not been included (or included wrongly) in your amanda backup. You have to understand that it takes some amount of time for tar to make a copy of a *big* file. If that big file is changing often, it is very likely it will be changing while tar is trying to copy it. There is very little you can make about it, except stopping mysql while you are doing th backup :) Actually, this is only a STRANGE, not a FAIL. A bit of auto promotion, this page https://wwws.cs.ait.ac.th/amanda/operator.shtml reccords a number of Amanda error message and the explanation for it, and possible recovery action. Olivier -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11022275 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: FAILURE AND STRANGE DUMP SUMMARY
Hi, fedora schrieb: Is there any proper mysql backup that can backup database without stopping it?? If so, I don't have to worry about it? Of course it wasn't failed but I just worried if I recover it and the database or tables might be corrupt just because Amanda detected strange. Please advice. I use a script for exporting the databases to an extra partition some time before amanda collect the data for backup. The script backup every database into a single file, using mysqldump. Also it write me a small logfile and send me an eMail if an error occured. All this is done while the MySQL server is running. Only for backup the BinaryLogs I have to lock the tables for a second. For me this is the best solution. Regards Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: FAILURE AND STRANGE DUMP SUMMARY
Is there any proper mysql backup that can backup database without stopping it?? If so, I don't have to worry about it? Of course it wasn't failed but I just worried if I recover it and the database or tables might be corrupt just because Amanda detected strange. Please advice. I remember I have seen something about backuping MySQL database, look at Amanda web site. Now what is the file ./mysql/general_log.CSV ? In my run of MySQL (version 4) I do not have such a file. Is it important or not if you loose it? If it is only a log file, like the name suggests, maybe loosing it would not be so dramatic. Best regards, Olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
On Jun 8, 2007, at 1:15 AM, fedora wrote: Is there any proper mysql backup that can backup database without stopping it?? If so, I don't have to worry about it? Of course it wasn't failed but I just worried if I recover it and the database or tables might be corrupt just because Amanda detected strange. Please advice. In my opinion your best bet is to regularly back up you MySQL databases and let those backups be stored by Amanda. There is a script http://sourceforge.net/projects/automysqlbackup/ that when run daily from cron will do daily, weekly and monthly backups of all or some of your MySQL databases. On my server, I exclude the raw MySQL databases and back up the MySQL backups. In the event of a restore, the backups can be easily applied to the new installation of MySQL and you're back up and running. Cheers, Bruce. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: FAILURE AND STRANGE DUMP SUMMARY
We use the following script (via a cron job) to get a distinct file for each database. We then only back up the /var/spool/mysqldumps directory. We run the script about an hour before the backups kick off. LP #!/bin/bash # Daily database dumps for inclusion in amanda backups. MYU=/mysql user with appropriate permissions/ MYP=/mysql users password/ MYDBS=`mysql -e show databases; -u $MYU -p$MYP|sed -e 's/|//g' |sed -e '1d'` for d in $MYDBS; do mysqldump --user=$MYU --password=$MYP $d /var/spool/mysqldumps/$d.sql done
Re: FAILURE AND STRANGE DUMP SUMMARY
Hi,
fedora schrieb:
Is there any proper mysql backup that can backup database without stopping
it??
If so, I don't have to worry about it? Of course it wasn't failed but I just
worried if I recover it and the database or tables might be corrupt just
because Amanda detected strange. Please advice.
I use a script for exporting the databases to an extra partition some time
before amanda collect the data for backup. The script backup every database
into a single file, using mysqldump. Also it write me a small logfile and send
me an eMail if an error occured. All this is done while the MySQL server is
running. Only for backup the BinaryLogs I have to lock the tables for a second.
For me this is the best solution.
See my script below.
Regards
Marc
--
Marc Muehlfeld (Leitung Systemadministration)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78
http://www.medizinische-genetik.de
#!/bin/bash
##
#
# Backup mysql tables, binary logs (if enabled) and configuration
#
# Created: 2002-11-21, Marc Muehlfeld
# Last edited: 2007-01-23, Marc Muehlfeld
#
##
##
# Configuration area
##
# MySQL password for root user
MYSQLPASSWD={password}
# Keep old backup $KEEP days
KEEP=2
# Path where you want to put the backup
DESTINATION=/BACKUP/mysql
# Logfile
LOG=/var/log/`basename $0`.log
# Set path for required tools
PATH=$PATH:/bin:/usr/bin
# Whitespace separated list of all configuration files you want to save
CONFIGS=/etc/my.cnf
##
# Here begins the program
##
# Logging function to stdout and logfile
function logging () {
echo -e `date +%d.%m.%Y %H:%M:%S` $1 | tee -a $LOG
}
logging Starting backup
# Create destination directory if it doesn't exist and secure it.
umask 0027
test ! -d $DESTINATION mkdir -p $DESTINATION
chown root:root $DESTINATION
# Create temporary directory
TMPDIR=$DESTINATION/MySQL_`date +%d-%m-%Y_%H-%M-%S`
mkdir $TMPDIR
# Create list with database names
logging Create list with database names
DATABASES=`mysql -u root --password=$MYSQLPASSWD EOF
show databases;
quit
EOF`
DATABASES=`echo $DATABASES | sed -e 's/^Database //'`
# Dump databases
mkdir -p $TMPDIR/db_exports
for DB in $DATABASES ; do
logging Dumping $DB
mysqldump -u root -p$MYSQLPASSWD $DB -e -a -c --add-drop-table
--add-locks -F -l $TMPDIR/db_exports/$DB.sql
done
# Copy configs
logging Backup configuration
mkdir -p $TMPDIR/configs
cp -p $CONFIGS $TMPDIR/configs
# Check if there are binary logs enabled
egrep ^log-bin /etc/my.cnf /dev/null 21
if [ $? -eq 0 ] ; then
logging Copy binary logs
# Preparing
mysql -u root -p$MYSQLPASSWD EOF
FLUSH TABLES WITH READ LOCK;
FLUSH LOGS;
EOF
# Copy binlog
mkdir -p $TMPDIR/bin_log
BINLOGDIR=`dirname $(egrep ^log-bin /etc/my.cnf | sed -e 's/^.*=//g')`
cp -p -r $BINLOGDIR $TMPDIR/bin_log
# Remove old binlogs
mysql -u root -p$MYSQLPASSWD EOF
RESET MASTER;
UNLOCK TABLES;
EOF
fi
# Build tar package
logging Building tar package
cd $DESTINATION
DIRONLY=`echo $TMPDIR | sed -e 's/^.*\///g'`
tar -zcf $DIRONLY.tar.gz $DIRONLY
# Remove all backups older than $KEEP days
logging Removing backups older than $KEEP days
find $DESTINATION/* -type f ! -mtime -$KEEP -exec rm -rf '{}' ';'
# Cleanup
logging Removing temporary directory
rm -rf $TMPDIR
# Finish
logging Backup finished\n
exit 0
Re: FAILURE AND STRANGE DUMP SUMMARY
On Fri, Jun 08, 2007 at 01:15:51AM -0700, fedora wrote: Is there any proper mysql backup that can backup database without stopping it?? You've already had a number of suggestions, so I'll just add one (and a shameless one, at that): ZRM for MySQL can back up MySQL databases without the need to dump them first or take them offline. See http://mysqlbackup.zmanda.com/ for documentation and downloads. For the other folks who posted scripts (wow! I haven't seen a response like that in a while!), please feel free to add the scripts and descriptions of them to http://wiki.zmanda.com, for those that are not already posted there. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: FAILURE AND STRANGE DUMP SUMMARY:
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator wrote: Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I assume that from the message at the bottom of the report that - file changed as we read it has caused a FAILURE AND STRANGE DUMP. Have I got anything to worry about here!. On the myserver machine, the file _.1.tmp: has changed while it was getting saved. and I have read that GNU tar is able to recover from this error. You may not be able to recover that one file. But it was a temporary, probably only partially complete, file anyway so why care about it. Should not impact the rest of the dump. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: FAILURE AND STRANGE DUMP SUMMARY:
Hi Cheers for the reassurance. I will make note of your comments to file. Thanks On Thu, 2005-09-29 at 07:15 -0400, Jon LaBadie wrote: On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator wrote: Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I assume that from the message at the bottom of the report that - file changed as we read it has caused a FAILURE AND STRANGE DUMP. Have I got anything to worry about here!. On the myserver machine, the file _.1.tmp: has changed while it was getting saved. and I have read that GNU tar is able to recover from this error. You may not be able to recover that one file. But it was a temporary, probably only partially complete, file anyway so why care about it. Should not impact the rest of the dump. -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: FAILURE AND STRANGE DUMP SUMMARY:
On Thursday 29 September 2005 07:15, Jon LaBadie wrote: On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator wrote: Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I assume that from the message at the bottom of the report that - file changed as we read it has caused a FAILURE AND STRANGE DUMP. Have I got anything to worry about here!. On the myserver machine, the file _.1.tmp: has changed while it was getting saved. and I have read that GNU tar is able to recover from this error. You may not be able to recover that one file. But it was a temporary, probably only partially complete, file anyway so why care about it. Should not impact the rest of the dump. That was the holding disk Jon. It should either be excluded, or specifically not named in a disklist entry. He's probably backing up '/', rather than naming the subdirs in his disklist. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
RE: failure and strange dump summary -- disk offline
Does anyone have any more suggestions I can look into for resolving my sda3 disk? amcheck does not report any problems. my amanda user is part of the disk group /dev/sda1 performs without missing a beat, /dev/sda3 continuously reports /dev/sda3 lev 0 FAILED [disk /dev/sda3 offline on mn-py-linuxsvr?] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - mn-py-linuxs /dev/sda3 0 FAILED --- -Original Message- From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] Sent: Thursday, October 28, 2004 6:46 PM To: Brian Tima Subject: Re: failure and strange dump summary Hi, Brian, on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users: BT I've been messing with AMANDA now for a couple months, I keep putting BT off trying to resolve my issues. But once again, here I am. BT Attempting BT to inquire if anyone has some direction for me on what I must do to BT correct my disk being offline? What does amcheck report? Is /dev/sda3 readable for the AMANDA-user? What does ll /dev/sda[13] tell you? -- best regards, Stefan G. Weichinger
Re: failure and strange dump summary -- disk offline
Hi, Brian Tima, on Freitag, 29. Oktober 2004 at 17:20 you wrote to amanda-users: BT Does anyone have any more suggestions I can look into for resolving my sda3 BT disk? BT amcheck does not report any problems. BT my amanda user is part of the disk group BT /dev/sda1 BT performs without missing a beat, /dev/sda3 BT continuously reports /dev/sda3 lev 0 FAILED [disk /dev/sda3 offline on BT mn-py-linuxsvr?] Look up the logfiles (/tmp/amanda, /var/adm/amanda) Did you configure and make AMANDA as AMANDA-user? Installed it as root? What does amadmin yourconf version say? -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: failure and strange dump summary -- disk offline
Brian Tima wrote: Does anyone have any more suggestions I can look into for resolving my sda3 disk? What filesystem is sda? ext2 reiserfs? ... What is in the debug file on the client: /tmp/amanda/*.debug concerning this DLE ? (I thought someone already asked, but I never saw the answer.) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.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: failure and strange dump summary -- disk offline
I don't understand what you are asking by All the ones relevant to /dev/sda3 ? I've tried with DUMP and GNUTAR, currently configured to run gnutar. are any switches needed in the grep /dev/sda3 command ? I have cleared /tmp/amanda and running it now -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens Sent: Friday, October 29, 2004 10:56 AM To: Brian Tima Cc: Amanda Mailing List Subject: Re: failure and strange dump summary -- disk offline Brian Tima wrote: File system is ext3 Which debug file do I check? Here are the files showing in the directory /tmp/amanda All the ones relevant to /dev/sda3 ? You never posted (afaik) which program you used to dump the filesystem (dump or gnutar). Do a grep of /dev/sda3 or the mountpoint for gnutar in the files. Another easy one: the middle numbers are datatime stamps. If that is still too much work, remove all those files in /tmp/amanda, then run it once, and look through all files that just got created. Remember ON THE CLIENT, not on the amanda server. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.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: failure and strange dump summary -- disk offline
--On Friday, October 29, 2004 12:06:07 -0500 Brian Tima [EMAIL PROTECTED] wrote: I don't understand what you are asking by All the ones relevant to /dev/sda3 ? I've tried with DUMP and GNUTAR, currently configured to run gnutar. Tar deals with filesystems, not devices, so you need to either use dump on /dev/sda3 or use tar on the path where it it is mounted. Even with tar on a device you should still get a tar image, it just won't be what your expecting, so you still have a problem. . are any switches needed in the grep /dev/sda3 command ? I have cleared /tmp/amanda and running it now Let us know what's in /tmp/amanda on the client when it's done. Frank -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens Sent: Friday, October 29, 2004 10:56 AM To: Brian Tima Cc: Amanda Mailing List Subject: Re: failure and strange dump summary -- disk offline Brian Tima wrote: File system is ext3 Which debug file do I check? Here are the files showing in the directory /tmp/amanda All the ones relevant to /dev/sda3 ? You never posted (afaik) which program you used to dump the filesystem (dump or gnutar). Do a grep of /dev/sda3 or the mountpoint for gnutar in the files. Another easy one: the middle numbers are datatime stamps. If that is still too much work, remove all those files in /tmp/amanda, then run it once, and look through all files that just got created. Remember ON THE CLIENT, not on the amanda server. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.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 * *** -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: failure and strange dump summary
Hi Stefan. Amcheck reports Amanda Tape Server Host Check - Holding disk /var/tmp: 26486092 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape LinM label ok Server check took 7.524 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.017 seconds, 0 problems found -Original Message- From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] Sent: Thursday, October 28, 2004 6:46 PM To: Brian Tima Subject: Re: failure and strange dump summary Hi, Brian, on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users: BT I've been messing with AMANDA now for a couple months, I keep putting BT off trying to resolve my issues. But once again, here I am. BT Attempting BT to inquire if anyone has some direction for me on what I must do to BT correct my disk being offline? What does amcheck report? Is /dev/sda3 readable for the AMANDA-user? What does ll /dev/sda[13] tell you? -- best regards, Stefan G. Weichinger
RE: failure and strange dump summary
Is /dev/sda3 readable for the AMANDA-user? How do I check if /dev/sda3 is readable by the amanda user? What does ll /dev/sda[13] tell you? It tells me brw-rwx--- 1 root disk8, 1 Mar 19 2002 /dev/sda1 brw-rwx--- 1 root disk8, 3 Mar 19 2002 /dev/sda3 -Original Message- From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] Sent: Thursday, October 28, 2004 6:46 PM To: Brian Tima Subject: Re: failure and strange dump summary Hi, Brian, on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users: BT I've been messing with AMANDA now for a couple months, I keep putting BT off trying to resolve my issues. But once again, here I am. BT Attempting BT to inquire if anyone has some direction for me on what I must do to BT correct my disk being offline? What does amcheck report? Is /dev/sda3 readable for the AMANDA-user? What does ll /dev/sda[13] tell you? -- best regards, Stefan G. Weichinger
RE: failure and strange dump summary
--On Thursday, October 28, 2004 19:11:41 -0500 Brian Tima [EMAIL PROTECTED] wrote: Is /dev/sda3 readable for the AMANDA-user? How do I check if /dev/sda3 is readable by the amanda user? What does ll /dev/sda[13] tell you? It tells me brw-rwx--- 1 root disk8, 1 Mar 19 2002 /dev/sda1 brw-rwx--- 1 root disk8, 3 Mar 19 2002 /dev/sda3 Check to make sure your amanda user a member of the group 'disk' on that server. Frank -Original Message- From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] Sent: Thursday, October 28, 2004 6:46 PM To: Brian Tima Subject: Re: failure and strange dump summary Hi, Brian, on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users: BT I've been messing with AMANDA now for a couple months, I keep putting BT off trying to resolve my issues. But once again, here I am. BT Attempting BT to inquire if anyone has some direction for me on what I must do to BT correct my disk being offline? What does amcheck report? Is /dev/sda3 readable for the AMANDA-user? What does ll /dev/sda[13] tell you? -- best regards, Stefan G. Weichinger -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Failure and Strange Dump Summary
On Fri, 3 May 2002 at 2:52pm, Michael Kopach wrote FAILURE AND STRANGE DUMP SUMMARY: localhost hda5a lev 0 FAILED [missing result for hda5a in localhost response] Two things: o You want to use a hostname. Even if you don't think you do, you do. localhost will more than likely come back to bite you. o Are you sure hda5a is correct? Are you sure it shouldn't just be hda5? o You may want to try using directory names (e.g. /home), rather than devices. It comes in handy if you add disks or move stuff around. OK, fine, so that was 3. (brought to you by Amanda 2.4.3b3 b is for beta. If you don't need the new features, you probably want to stick with 2.4.2p2 plus patches. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: FAILURE AND STRANGE DUMP SUMMARY:
On Tue, 29 Jan 2002 16:12:17 -0500 John R. Jackson [EMAIL PROTECTED] wrote: [..] I looked at the code and that error only comes from one place, when driver has tried doing a dump once and it failed but was requeued to TRYAGAIN, then the second attempt also failed. I'm not sure the message means what it says, that there really was a problem connecting to the host. That may have been what it originally meant, but now it might mean other things (in case it isn't obvious, this code gets a little confusing to navigate). I'm pretty sure it has nothing to do with starting a new tapecycle, except in an indirect way (if at all). My best guess is it has something to do with the amount of holding disk space you have, or possibly other activity going on in the holding disk at the same time Amanda is running (e.g. Amanda thought it had N MBytes but when it actually tried to use the space, less than that was really there). I would need to see the corresponding amdump.nn file that goes along with one of these errors, and possibly all the client logs for that same run. If you want to contact me offline of the list for this, that's OK. In the meantime, you might try dropping maxdumps back to 1. That may or may not help -- it's just a guess. Hi John, you are right about the TRYAGAIN, take a look ath an excerpt of /var/log/amanda/DailySet1/amdump.3 at the backup server ---cut-on--- driver: adding holding disk 0 dir /amanda_holding_disk size 512000 reserving 512000 out of 512000 for degraded-mode dumps driver: start time 27.648 inparallel 10 bandwidth 600 diskspace 512000 dir OBSOLETE datestamp 20020126 driver: drain-ends tapeq LFFO big-dumpers 7 driver: result time 27.648 from taper: TAPER-OK driver: send-cmd time 27.648 to dumper0: FILE-DUMP 00-1 /amanda_holding_disk/20020126/heiner.buero-till.de._usr_samba1_ing__buero.1 heiner.buero-till.de /usr/s amba1/ing_buero 1 2002:1:23:23:46:49 1073741824 GNUTAR 96 |;bsd-auth;compress-fast;index;exclude-list=/etc/amanda/exclude.gtar; driver: state time 27.649 free kps: 590 space: 511904 taper: idle idle-dumpers: 9 qlen tapeq: 0 runq: 13 roomq: 0 wakeup: 15 driver-idle: start-wait driver: interface-state time 27.649 if : free 590 driver: hdisk-state time 27.649 hdisk 0: free 511904 dumpers 1 driver: send-cmd time 42.641 to dumper1: FILE-DUMP 01-2 /amanda_holding_disk/20020126/heiner.buero-till.de._usr_samba_fax__eingang.1 heiner.buero-till.de /usr/ samba/fax_eingang 1 2002:1:23:23:45:48 1073741824 GNUTAR 96 |;bsd-auth;compress-fast;index;exclude-list=/etc/amanda/exclude.gtar; driver: state time 42.642 free kps: 580 space: 511808 taper: idle idle-dumpers: 8 qlen tapeq: 0 runq: 12 roomq: 0 wakeup: 15 driver-idle: start-wait driver: interface-state time 42.642 if : free 580 driver: hdisk-state time 42.642 hdisk 0: free 511808 dumpers 2 driver: result time 42.643 from dumper1: TRY-AGAIN 01-2 nak error:amandad busy dumper: stream_client: connected to 192.168.1.25.41043 ---cut-off--- Your guess about the holding disk might be right, because I have only about 500 MB space left which is configured for this amount at amanda.conf. The data to backup are a few :) GB, is there a calculation for the size of the holding disk corresponding to the amount of data to backup? Sorry, I haven't found any amdump.* file neither at the server nor at the client. Well, don't blame me as I am a new user, but what do you mean with dropping maxdumps back to 1 and how to do that? BTW, the server is a debian with a pentium II cpu at 400 MHz and amanda been installed from source, because debian doesn't have packages for the actual bugfixed release and it has no other jobs to do at night than amanda. ... I hope, that you can tell me to get a bigger holding disk and that this would fix my could not connect to client - problem. ... if not, I'll have to ask my boss, if he agrees about giving more information to your hands if you are willing to get them to help me :) :) adTHANXvance Sascha
Re: FAILURE AND STRANGE DUMP SUMMARY:
On Mon, 28 Jan 2002 13:01:40 -0500 John R. Jackson [EMAIL PROTECTED] wrote: ... suddenly 3 of 14 mountpoints on the same machine failed for reasons I don't get. ... machine /some/mountpoint_1 lev 1 FAILED [could not connect to machine] Some things to check: * See if there are left over amandad (or dumper) processes laying around still running from a previous failure. * Verify that the amandad service in inetd.conf/xinetd is set to wait (the default is nowait). * Make sure you don't have multiple cron jobs running at the same time. Thanks John, - client's inetd.conf says: amanda dgram udp wait backup /usr/local/lib/amanda/amandad amandad - server's inetd.conf says: amandaidx stream tcp nowait backup /usr/local/lib/amanda/amindexd amindexd amidxtape stream tcp nowait backup /usr/local/lib/amanda/amidxtaped amidxtaped ...that's what the doc/INSTALL told me to do, which was pretty good working the first cycle of 11 tapes. Now, just after reusing the very first tape, those errors occured so suddenly. Obviously it was good to ask, because the new backup has even more faliures of this kind! I checked the cronjobs, there are the two like advised (one to check tape, the other one to run amanda) for the backup-user, none for root or any other at the same time. Checking running processes is a nightshift job, I'd like to avoid :) Any more tips left? adTHANXvance Sascha
Re: FAILURE AND STRANGE DUMP SUMMARY:
Checking running processes is a nightshift job, I'd like to avoid :) Understood. I'm on a first name basis with all three Operations shifts (plus weekends) here, and I'm not sure that's necessarily a good thing. They're nice people, but at 3 AM ... :-) :-) Any more tips left? I looked at the code and that error only comes from one place, when driver has tried doing a dump once and it failed but was requeued to TRYAGAIN, then the second attempt also failed. I'm not sure the message means what it says, that there really was a problem connecting to the host. That may have been what it originally meant, but now it might mean other things (in case it isn't obvious, this code gets a little confusing to navigate). I'm pretty sure it has nothing to do with starting a new tapecycle, except in an indirect way (if at all). My best guess is it has something to do with the amount of holding disk space you have, or possibly other activity going on in the holding disk at the same time Amanda is running (e.g. Amanda thought it had N MBytes but when it actually tried to use the space, less than that was really there). I would need to see the corresponding amdump.nn file that goes along with one of these errors, and possibly all the client logs for that same run. If you want to contact me offline of the list for this, that's OK. In the meantime, you might try dropping maxdumps back to 1. That may or may not help -- it's just a guess. Sascha John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FAILURE AND STRANGE DUMP SUMMARY:
... suddenly 3 of 14 mountpoints on the same machine failed for reasons I don't get. ... machine /some/mountpoint_1 lev 1 FAILED [could not connect to machine] Some things to check: * See if there are left over amandad (or dumper) processes laying around still running from a previous failure. * Verify that the amandad service in inetd.conf/xinetd is set to wait (the default is nowait). * Make sure you don't have multiple cron jobs running at the same time. Sascha John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FAILURE AND STRANGE DUMP SUMMARY:
Hi, Thks for zour former helps.. I do a special configuration with only the host that I'm having a problem with (atalante). and amanda success to do this. So i'm kind of puzzled about it. To give you more information I would like to tell you that -atalante is the backup client host and the Tape Server Host in the same time furthermore I'd like to ask some other questions - I don't really understand how you guys are nominating the clients and the servers I thought that amanda was composed of -many serverS on each host where we would like to backup data from -one client orchestrating the download and where we can found the programs amdump - Is there a way to force the planner to not do a level 0 on a host - Amrmtape: considering I'm using a configuration for many times and that I would like to do some changes on it. I thought that I can launch an amdump and if the result failed , I have just to launch an amrmtape to discard the last amdump and to have all the databases at the same point that before the tests (if I do the amrmtapes on all tapes used during the tests) I get the fellowing error after launching amdump. ... sendbackup: info BACKUP=/usr/sbin/ufsdump ... | DUMP: SIGBUS() ABORTING! ? DUMP: bread: dev_seek error: Invalid argument Actually, Amanda gets it after it launches ufsdump. This is not an Amanda problem -- it's a ufsdump problem. If you ran that command yourself the same way Amanda does, it would also fail. The first thing I'd do is contact Sun (I assume that's what the client is running) and get the latest ufsdump/ufsrestore patches. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FAILURE AND STRANGE DUMP SUMMARY:
I do a special configuration with only the host that I'm having a problem with (atalante). and amanda success to do this. So i'm kind of puzzled about it. That could just mean whatever made ufsdump upset doesn't happen to be active at the moment. -atalante is the backup client host and the Tape Server Host in the same time OK. That's a normal situation. - I don't really understand how you guys are nominating the clients and the servers Yeah, that confuses people, and I agree the terminology could easily be considered backward. But it is the way it is and to start calling things by the other names would only make matters worse. I thought that amanda was composed of -many serverS on each host where we would like to backup data from Those are called Amanda clients. -one client orchestrating the download and where we can found the programs amdump And that's called the Amanda server. - Is there a way to force the planner to not do a level 0 on a host Use strategy nofull or strategy incronly in the dumptype. But read about them in the amanda(8) man page. - Amrmtape: considering I'm using a configuration for many times and that I would like to do some changes on it. I thought that I can launch an amdump and if the result failed , I have just to launch an amrmtape to discard the last amdump and to have all the databases at the same point that before the tests (if I do the amrmtapes on all tapes used during the tests) That should be correct. Why? Is it not working? You might also consider backing up (e.g. with GNU tar by hand) the curinfo database and tapelist files yourself before a test run, and then just restore them to start again. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FAILURE AND STRANGE DUMP SUMMARY:
I get the fellowing error after launching amdump. ... sendbackup: info BACKUP=/usr/sbin/ufsdump ... | DUMP: SIGBUS() ABORTING! ? DUMP: bread: dev_seek error: Invalid argument Actually, Amanda gets it after it launches ufsdump. This is not an Amanda problem -- it's a ufsdump problem. If you ran that command yourself the same way Amanda does, it would also fail. The first thing I'd do is contact Sun (I assume that's what the client is running) and get the latest ufsdump/ufsrestore patches. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Failure and strange dump summary
On Feb 20, 2001, "FFx" [EMAIL PROTECTED] wrote:
my exact version is : amanda 2.4.2-19991216-beta1
Then yours pre-dates the patch. Time to upgrade :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Failure and strange dump summary
Yop again!
i sucessfully upgraded to amanda 2.4.2
but my original path to the am* binaries changed from /usr/sbin to
/usr/local/sbin
so i copied my /etc/amanda/conf files to /usr/local/etc/amanda/conf
when i run the "new" amcheck utility "/usr/local/sbin/amcheck conf" i got
the error:
/usr/local/etc/amanda/conf/amanda.conf", line 85: configuration keyword
expected
"/usr/local/etc/amanda/conf/amanda.conf", line 85: end of line expected
"/usr/local/etc/amanda/conf/amanda.conf", line 88: configuration keyword
expected
"/usr/local/etc/amanda/conf/amanda.conf", line 88: end of line expected
my question is :
has the amanda.conf file syntax changed from previous versions of amanda ??
my previus version was 2.4.2-19991216-beta1
- Original Message -
From: "Alexandre Oliva" [EMAIL PROTECTED]
To: "FFx" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, February 20, 2001 12:51 PM
Subject: Re: Failure and strange dump summary
On Feb 20, 2001, "FFx" [EMAIL PROTECTED] wrote:
my exact version is : amanda 2.4.2-19991216-beta1
Then yours pre-dates the patch. Time to upgrade :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Failure and strange dump summary
when i run the "new" amcheck utility "/usr/local/sbin/amcheck conf" i got the error: /usr/local/etc/amanda/conf/amanda.conf", line 85: configuration keyword expected "/usr/local/etc/amanda/conf/amanda.conf", line 85: end of line expected "/usr/local/etc/amanda/conf/amanda.conf", line 88: configuration keyword expected "/usr/local/etc/amanda/conf/amanda.conf", line 88: end of line expected So what's on lines 85 and 88? has the amanda.conf file syntax changed from previous versions of amanda ?? I don't think so. You need to look at the lines it doesn't like and compare them to amanda(8) and/or post them here. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FAILURE AND STRANGE DUMP SUMMARY
On Tue, 23 Jan 2001, Gerald T. Freymann wrote: FAILURE AND STRANGE DUMP SUMMARY: amanda file://xxx/PAP2 lev 0 STRANGE And then what follows is a line by line blow of each and every file that got backed up. How do you make Amanda think these PC shares are no longer "Strange?" You didn't say what versions of amanda and samba you're using. I used to see this with old versions when I had samba configured with too high a logging level. It's been so long since I've looked at this I don't now remember what the correct level is, but this is where I'd suggest looking first. -Mitch P.S. You have a very catchy name. Well to me anyhow, since I have an uncle named Jerry Freyman. :-)
Re: FAILURE AND STRANGE DUMP SUMMARY
You didn't say what versions of amanda and samba you're using. I used to see this with old versions when I had samba configured with too high a logging level. I'm using Amanda 2.4.1p1 and Samba 2.0.7 P.S. You have a very catchy name. Well to me anyhow, since I have an uncle named Jerry Freyman. :-) Oh? We're from Lithuanian (sp?) originally... Grandma landed in Toronto, Ontario, Canada many moons ago. Grandfather was left behind as a POW. -Gerry
Re: FAILURE AND STRANGE DUMP SUMMARY
Gerald T. Freymann [EMAIL PROTECTED] wrote: I'm using Amanda 2.4.1p1 and Samba 2.0.7 You should apply the patch http://www.amanda.org/patches/2.4.1p1/samba2-2418.diff or upgrade to amanda-2.4.2 HTH, Lipo -- Roland E. Lipovits Vienna, Austria
