Slow client
Hi, I noticed yesterday that one of my clients suddenly became very slow: by wall clock, seeing the file grows on the holding disk, it takes 9 minutes for 5 MB of GNUTAR level 2. previous run (Apr. 28th) for the same machine, same DLE, same level was 107 KB/s for the dump according to Amanda report. The slowness can be seen for every DLE on that client. Other than that, the client is working fine, load average is close to 0, it is not swapping or anything, network seems to be working fine. Any idea? I will run some more diagnostics later, once the backup is finished. Best regards, Olivier
Re: Slow client
Olivier Nicole wrote: Hi, I noticed yesterday that one of my clients suddenly became very slow: by wall clock, seeing the file grows on the holding disk, it takes 9 minutes for 5 MB of GNUTAR level 2. previous run (Apr. 28th) for the same machine, same DLE, same level was 107 KB/s for the dump according to Amanda report. That works out to about 9kB/s, which is pretty slow. Do you have a duplex mismatch or other errors on the network interface or switch port? Are you seeing any system messages about read errors on your disks? Have you recently changed OS/kernel/tar versions? What does the Amanda report show for dumper time and taper time for the DLE? Frank The slowness can be seen for every DLE on that client. Other than that, the client is working fine, load average is close to 0, it is not swapping or anything, network seems to be working fine. Any idea? I will run some more diagnostics later, once the backup is finished. Best regards, Olivier -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Slow client
Frank, Do you have a duplex mismatch or other errors on the network interface or switch port? No error visible. A manual transfer was also very slow, a reboot of the machine solved that. Are you seeing any system messages about read errors on your disks? Have you recently changed OS/kernel/tar versions? Nothing changed for a good while, only I did reboot the network equipment some time last week. I beleive the duplex did not get negociated properly after reboot. What does the Amanda report show for dumper time and taper time for the DLE? HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- - mailback / 04508018784 41.7 41:517.5 0:10 1870.1 mailback /home 2 187190 106368 56.8 213:068.3 0:30 3489.2 mailback /usr0 FAILED - mailback /var043080 6752 15.7 49:432.3 0:07 956.0 That's yucky :) OK that was only a network problem it seems. Thanks, Olivier
2.5.2b-20070507 build
Greetings; I saw this go by during the build, does it mean anything? Name main::include_list used only once: possible typo at amgtar line 50. Name main::ksize used only once: possible typo at amgtar line 263. Name main::opt_record used only once: possible typo at amgtar line 236. Name main::message_line used only once: possible typo at amgtar line 46. Name main::max_level used only once: possible typo at amgtar line 43. Name main::collection used only once: possible typo at amgtar line 53. Name main::index_xml used only once: possible typo at amgtar line 45. Name main::group_default used only once: possible typo at amgtar line 86. Name main::exclude_file used only once: possible typo at amgtar line 51. Name main::record used only once: possible typo at amgtar line 48. Name main::message_xml used only once: possible typo at amgtar line 47. Name main::index_line used only once: possible typo at amgtar line 44. Name main::include_file used only once: possible typo at amgtar line 49. Name main::user_backup used only once: possible typo at amgtar line 67. Name main::user_default used only once: possible typo at amgtar line 85. Name main::exclude_list used only once: possible typo at amgtar line 52. -- 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) The universe is like a safe to which there is a combination -- but the combination is locked up in the safe. -- Peter DeVries
Re: 2.5.2 compilation failure on irix-6.5.x
Pieter Bowman wrote: This is the case on both IRIX and OSF/1. These compilers can't handle: #define vstrallocf(...) debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__) I fix it in the 2.5.2 tree, but the next release will require that syntax, which is in the C99 standard. Do you have a C99 compiler on IRIX and OSF/1 ? Jean-Louis
db-based infofiles
In working on cleaning up the amanda codebase, I discovered that at least some of the db-based infofile backends (--with-db=gdbm, ndbm, db, dbm) probably don't work. I talked with Jean-Louis Martineau, and he mentioned that they have been deprecated for a long time in favor of the text database. I'd like to remove this support completely in the next release. So: are you or anyone you know using non-text infofiles? Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Backup on DVD-RAM
Hello, i have a working Amanda configuration which backup on DVD-RAM. (its like writing on a hard disk) The disks are all smaller than 4.3 GB, so a backup is no problem. But what happens if on disk gets greater than 4.3 GB? Can Amanda handle it, and ask for a second DVD to write the dumps on, or must i set a special option in the config? Any suggestions? regards, Sebastian signature.asc Description: OpenPGP digital signature
Please help... no backups since a week ago (data write: Connection reset by peer)
Can someone please help me?
Steven Settlemyre wrote:
I haven't changed my configs for months and things were running great
until last week. Since last tues, none of my dailies have finished,
and last night a monthly failed.
Looking through the logs I see the problem always seems to start with
data write: Connection reset by peer and Don't know how to send
ABORT command to chunker. I'm having a hard time interpreting the
logs and can't seem to find too much in the archives about this. Was
wondering if someone could walk me through an explanation of the
problem and how to avoid it in the future.
My monthlies run tape spanning on 3 40G tapes.
Here is the email output generated:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape Monthly21.
The next 3 tapes Amanda expects to use are: Monthly01, Monthly02,
Monthly03.
The next 3 new tapes already labelled are: Monthly19, Monthly20,
Monthly22.
FAILURE AND STRANGE DUMP SUMMARY:
wagstaff /usr/locallev 1 FAILED [data
write: Connection reset by peer]
lollipop /files1 lev 0 FAILED [data
write: Connection reset by peer]
helios /files3 lev 1 FAILED [data write:
Connection reset by peer]
helios / RESULTS MISSING
helios /files2 RESULTS MISSING
helios /usr RESULTS MISSING
helios /usr/localRESULTS MISSING
helios /var RESULTS MISSING
lollipop / RESULTS MISSING
lollipop /usr RESULTS MISSING
lollipop /usr/localRESULTS MISSING
wagstaff /files3 RESULTS MISSING
wagstaff /files4 RESULTS MISSING
wagstaff /files5 RESULTS MISSING
wagstaff /files6/vol/Voiceware RESULTS MISSING
wizard/files2 RESULTS MISSING
snapserver /hd/vol_mnt0/shares/TermLab RESULTS MISSING
snapserver /hd/vol_mnt0/shares/bcl RESULTS MISSING
snapserver /hd/vol_mnt0/shares/biochem RESULTS MISSING
snapserver /hd/vol_mnt0/shares/confocal RESULTS MISSING
driver: FATAL Don't know how to send ABORT command to chunker
chunker: FATAL error [bad command after RQ-MORE-DISK: QUIT]
chunker: FATAL error [bad command after RQ-MORE-DISK: QUIT]
chunker: FATAL error [bad command after RQ-MORE-DISK: QUIT]
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:08
Run Time (hrs:min) 1:01
Dump Time (hrs:min)1:55 1:40 0:16
Output Size (meg)8519.7 7729.7 790.1
Original Size (meg) 13146.311595.5 1550.8
Avg Compressed Size (%)64.8 66.7 50.9 (level:#disks
...)
Filesystems Dumped 35 12 23 (1:23)
Avg Dump Rate (k/s) 1261.0 1323.3 863.1
Tape Time (hrs:min)0:53 0:44 0:09
Tape Size (meg) 8521.6 7730.3 791.3
Tape Used (%) 21.1 19.02.1 (level:#disks
...)
Filesystems Taped35 12 23 (1:23)
(level:#chunks ...)
Chunks Taped 35 12 23 (1:23)
Avg Tp Write Rate (k/s) 2724.3 3000.8 1433.6
USAGE BY TAPE:
Label Time Size %NbNc
Monthly21 0:53 8726112k 21.13535
FAILED AND STRANGE DUMP DETAILS:
/-- wagstaff /usr/local lev 1 FAILED [data write: Connection reset by
peer]
sendbackup: start [wagstaff level 1]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc
|/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 1 dump: Tue May 08 01:11:26 2007
| DUMP: Date of last level 0 dump: Mon Apr 30 23:54:14 2007
| DUMP: Dumping /dev/rdsk/c0t0d0s7 (wagstaff:/usr/local) to standard
output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 13585968 blocks (6633.77MB) on 0.10 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
| DUMP: 16.49% done, finished in 0:50
| DUMP: 28.34% done, finished in 0:57
| DUMP: 38.89% done, finished in 1:12
\
/-- lollipop /files1 lev 0 FAILED [data write: Connection reset by peer]
sendbackup: start [lollipop level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/sbin/ufsrestore
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Mon May 07 23:52:56 2007
|
Re: Please help... no backups since a week ago (data write: Connection reset by peer)
On Wednesday 09 May 2007, Steven Settlemyre wrote:
Can someone please help me?
Steven Settlemyre wrote:
I haven't changed my configs for months and things were running great
until last week. Since last tues, none of my dailies have finished,
and last night a monthly failed.
Looking through the logs I see the problem always seems to start with
data write: Connection reset by peer and Don't know how to send
ABORT command to chunker. I'm having a hard time interpreting the
logs and can't seem to find too much in the archives about this. Was
wondering if someone could walk me through an explanation of the
problem and how to avoid it in the future.
My monthlies run tape spanning on 3 40G tapes.
Here is the email output generated:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape Monthly21.
The next 3 tapes Amanda expects to use are: Monthly01, Monthly02,
Monthly03.
The next 3 new tapes already labelled are: Monthly19, Monthly20,
Monthly22.
FAILURE AND STRANGE DUMP SUMMARY:
wagstaff /usr/locallev 1 FAILED [data
write: Connection reset by peer]
lollipop /files1 lev 0 FAILED [data
write: Connection reset by peer]
helios /files3 lev 1 FAILED [data write:
Connection reset by peer]
helios / RESULTS MISSING
helios /files2 RESULTS MISSING
helios /usr RESULTS MISSING
helios /usr/localRESULTS MISSING
helios /var RESULTS MISSING
lollipop / RESULTS MISSING
lollipop /usr RESULTS MISSING
lollipop /usr/localRESULTS MISSING
wagstaff /files3 RESULTS MISSING
wagstaff /files4 RESULTS MISSING
wagstaff /files5 RESULTS MISSING
wagstaff /files6/vol/Voiceware RESULTS MISSING
wizard/files2 RESULTS MISSING
snapserver /hd/vol_mnt0/shares/TermLab RESULTS MISSING
snapserver /hd/vol_mnt0/shares/bcl RESULTS MISSING
snapserver /hd/vol_mnt0/shares/biochem RESULTS MISSING
snapserver /hd/vol_mnt0/shares/confocal RESULTS MISSING
driver: FATAL Don't know how to send ABORT command to chunker
chunker: FATAL error [bad command after RQ-MORE-DISK: QUIT]
chunker: FATAL error [bad command after RQ-MORE-DISK: QUIT]
chunker: FATAL error [bad command after RQ-MORE-DISK: QUIT]
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:08
Run Time (hrs:min) 1:01
Dump Time (hrs:min)1:55 1:40 0:16
Output Size (meg)8519.7 7729.7 790.1
Original Size (meg) 13146.311595.5 1550.8
Avg Compressed Size (%)64.8 66.7 50.9 (level:#disks
...)
Filesystems Dumped 35 12 23 (1:23)
Avg Dump Rate (k/s) 1261.0 1323.3 863.1
Tape Time (hrs:min)0:53 0:44 0:09
Tape Size (meg) 8521.6 7730.3 791.3
Tape Used (%) 21.1 19.02.1 (level:#disks
...)
Filesystems Taped35 12 23 (1:23)
(level:#chunks ...)
Chunks Taped 35 12 23 (1:23)
Avg Tp Write Rate (k/s) 2724.3 3000.8 1433.6
USAGE BY TAPE:
Label Time Size %NbNc
Monthly21 0:53 8726112k 21.13535
FAILED AND STRANGE DUMP DETAILS:
/-- wagstaff /usr/local lev 1 FAILED [data write: Connection reset by
peer]
sendbackup: start [wagstaff level 1]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc
|/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 1 dump: Tue May 08 01:11:26 2007
| DUMP: Date of last level 0 dump: Mon Apr 30 23:54:14 2007
| DUMP: Dumping /dev/rdsk/c0t0d0s7 (wagstaff:/usr/local) to standard
output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 13585968 blocks (6633.77MB) on 0.10 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
| DUMP: 16.49% done, finished in 0:50
| DUMP: 28.34% done, finished in 0:57
| DUMP: 38.89% done, finished in 1:12
\
/-- lollipop /files1 lev 0 FAILED [data write: Connection reset by peer]
sendbackup: start [lollipop level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/sbin/ufsrestore
-f... -
sendbackup: info
Re: amanda upgrade questions
Replying to myself: It's my second attempt at trying to get any input as to how difficult it may be to upgrade amanda. I have not received any reply on both occasions. Are my questions too dumb ? I would like to read some sort of upgrade guide, but I can't find anything useful in the doc or in the amanda wiki. 2.5 seems pretty scary. I see a lot of problems on the list. Is it stable, or is it experimental ? Thanks 2007/5/7, Guy Dallaire [EMAIL PROTECTED]: I understand that amanda 2.5 is compatible with amanda 2.4 clients. This means I could upgrade my server and do the clients later ? I would like to upgrade to 2.5.2 for security reason (ability to encrypt backups, ssh) I compiled my server and client with restriction on the tcp and udp ports used for ease of firewall configuration: --with-tcpportrange=5,50100' '--with-udpportrange=850,859 Do these options still apply to the new amanda version ? Will the new version be able to restore old tapes that were written by the amanda 2.4 tapeserver ? Will amrecover on a 2.4 client be able to use the 2.5 amanda server ? Are the new encryption and ssh features easy to use ? Thanks !
Hardware suggestion
Hi, I am considering replacement for my Amanda server, the guy has been in production for about 6 years now and I want to be ready for the time when the tape drive will die. We currently use SLR100, wich is fine, very little tape failure, but tapes are expensive, a 50 GB (native) 100 GB (compressed) tape is the price of a 250 GB hard disk. The tape drive itself cost twice the price of the server at that time. So we are considering vtapes, but I would like to have hard disk physical rotation, the same way we have tape rotation --and it is manual changing of the tape every day. The only answer I don't have concernes the hardware to use for disk hot plug mounting and unmounting (on the software side,I now thatthe disk can be disconnected from the operating system before they are physically removed from the machine). Normal hot swap bay for hard disk are not designed for daily use, they are designed for maintenance only, and would break soon if I swaped the disk every day. Could anyone advise on some disk tray solution that is stong and reliable and will handle a lot of manipulation. idealy I wouldbe looking at one tray bay and 5 or 6 trays for the disks. best regards, Olivier
Re: amanda upgrade questions
On Wed, May 09, 2007 at 09:38:20PM -0400, Guy Dallaire wrote: Replying to myself: It's my second attempt at trying to get any input as to how difficult it may be to upgrade amanda. I have not received any reply on both occasions. Are my questions too dumb ? I would like to read some sort of upgrade guide, but I can't find anything useful in the doc or in the amanda wiki. 2.5 seems pretty scary. I see a lot of problems on the list. Is it stable, or is it experimental ? Thanks 2007/5/7, Guy Dallaire [EMAIL PROTECTED]: I understand that amanda 2.5 is compatible with amanda 2.4 clients. This means I could upgrade my server and do the clients later ? I would like to upgrade to 2.5.2 for security reason (ability to encrypt backups, ssh) Being compatible does not mean that the clients gain the new features of the upgraded server. If the client could not do encryption or ssh before, upgrading the server will not change the client. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amanda upgrade questions
Hi, It is actually quite simply to upgrade amanda. All you need to do is to download the latest version of Amanda (for this case amanda 2.5.2), untar it and execute the following commands to clean and recompile the latest build. make distclean ./configure -with-tcpportrange=5,50100 --with-udpportrange=850,859 make make install But becareful with amanda version 2.5.2 as it contains some bug issue with the amlabel on the vtapes. Regards Anthony On Wed, 2007-05-09 at 21:38 -0400, Guy Dallaire wrote: Replying to myself: It's my second attempt at trying to get any input as to how difficult it may be to upgrade amanda. I have not received any reply on both occasions. Are my questions too dumb ? I would like to read some sort of upgrade guide, but I can't find anything useful in the doc or in the amanda wiki. 2.5 seems pretty scary. I see a lot of problems on the list. Is it stable, or is it experimental ? Thanks 2007/5/7, Guy Dallaire [EMAIL PROTECTED]: I understand that amanda 2.5 is compatible with amanda 2.4 clients. This means I could upgrade my server and do the clients later ? I would like to upgrade to 2.5.2 for security reason (ability to encrypt backups, ssh) I compiled my server and client with restriction on the tcp and udp ports used for ease of firewall configuration: --with-tcpportrange=5,50100' '--with-udpportrange=850,859 Do these options still apply to the new amanda version ? Will the new version be able to restore old tapes that were written by the amanda 2.4 tapeserver ? Will amrecover on a 2.4 client be able to use the 2.5 amanda server ? Are the new encryption and ssh features easy to use ? Thanks !
