nathan Posted July 15, 2003 Report Share Posted July 15, 2003 I running Retrospect on a five computer G4 network. The machines are 800 MHz dual G4 with two 80 GB drives each. Every month or so the catalog gets screwed up and Retrospect can't seem to repair it. I end up having to erase my backup and start over. Currently I'm seeing the following error: error -24204 (chunk file damaged during access) OS is 10.2.6 and I'm running 5.0.238 version of Retrospect. I've wasted an enormous amount of time trying to keep the backup software at least limping along. Please help. Link to comment Share on other sites More sharing options...
AmyJ Posted July 24, 2003 Report Share Posted July 24, 2003 Please see the following article for information on chunk checksum errors: http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27313 Are you backing up to or from these 80 gig drives? If from, what are you backing up to? While in Retrospect, go to Configure > Devices > Device Status and list Vendor, Product and Version for your backup device. How big are the backup sets when this happens? Are there any other errors in the log that leading up to the time these errors are happening? Device communication errors, etc. Link to comment Share on other sites More sharing options...
nathan Posted August 1, 2003 Author Report Share Posted August 1, 2003 Ok, it happened again. I started a new media backup a few weeks ago and I've gotten new catalog errors. My backup device is AIT-3 tape. The device status listed by Retrospect is ID=SCSI-A:1 VENDOR=SONY Product=SDX-500C Version=010c Driver=Sony AIT DC (5.01) The errors in the log file are -39 (unexpected end of file) then -24204 (chunk file damaged during access) There are no communication errors in the log file that indicate a media failure. The summary of the backup set at this point is Used: 302.3 G for 5,985,598 files Storage: 6 members, 27 sessions, 12 Snapshots Options: Hardware compression Given that the backup computer has run rock solid, with the exception of Retrospect being totally unstable, for the past year and a half (since I got it) I find it hard to believe there is anything wrong with the computer. Link to comment Share on other sites More sharing options...
natew Posted August 4, 2003 Report Share Posted August 4, 2003 Nathan I understand your frustration- I'm sure your machine runs fine the rest of the time. Just keep in mind that Retrospect is doing things no other software does - copy huge amounts of data, write to your tape drive, get root access across the network... Retrospect is more likely that most software to expose hidden problems on your system. That said, What SCSI card are you using? Any chance you could try moving the backup to another machine as a test? Any chance you can try saving the Catalog files to a locally attached USB/Firewire drive? Nate Link to comment Share on other sites More sharing options...
shadowspawn Posted September 18, 2003 Report Share Posted September 18, 2003 Did this ever get resolved? I have just started getting very similar behavior with errors occurring and the catalog being damaged in the process. NB: I am not seeing chunk checksum errors. However, the main advice in the chunk checksum link that Amy gave was to try a different disk and/or different computer, which is what I am going to try. Drive Setup > First Aid reported no problems on the disk. Retrospect Server 5.1.167 DP G4 867 MHz Mac OS X 10.2.6 768 MB RAM VXA-1 tape drive (2C8C) Adaptec 2930CU SCSI adaptor, ROM 4.0 revision 3, driver 1.1.0 Backing up mounted volumes, macintosh clients, windows clients, to VXA-1 tape unit. Catalogs stored on 12 GB local partition, 4.75 GB available. Problem has occurred multiple times in last two weeks, no other hardware errors in log, two different backup sets, three different tapes. Backups sometimes run ok, and have been running fine in past with same configuration. Backup set Theta is 408.7 G for 4,340,168 files, catalog compression on Backup set Eta is 421.0 G for 4,261,950 files, catalog compression off These are the biggest backup sets I have ever had, so I wonder if the size is significant? Entries from log: - 2/9/2003 8:01:20 PM: Copying Orange on Orange MacX… 2/9/2003 8:01:20 PM: Connected to Orange MacX Can't save Snapshot in Theta, error -39 (unexpected end of file). Can't save catalog, error -24204 (chunk file damaged during access). [Theta] - 4/9/2003 10:31:31 PM: Copying DocumentationG3 on Documentation MacX… 4/9/2003 10:31:31 PM: Connected to Documentation MacX Couldn't write Snapshot, error -198 (unknown). Can't create session, error -40 (file positioning error). - 5/9/2003 10:52:59 AM: Copying System on Dxxx MacX… 5/9/2003 10:52:59 AM: Connected to Dxxx MacX Can't save Snapshot in Theta, error -39 (unexpected end of file). Can't save catalog, error -24204 (chunk file damaged during access). [Eta] - 17/9/2003 10:16:32 PM: Copying DRIVE C (C:) on Mxxx PC… 17/9/2003 10:16:32 PM: Connected to Mxxx PC Couldn't write Snapshot, error -198 (unknown). Can't create session, error -40 (file positioning error). - 18/9/2003 9:34:03 PM: Copying DRIVE C (C:) on Sxxx PC… 18/9/2003 9:34:03 PM: Connected to Sxxx PC Can't save Snapshot in Eta, error -39 (unexpected end of file). Can't save catalog, error -24204 (chunk file damaged during access). Link to comment Share on other sites More sharing options...
shadowspawn Posted September 18, 2003 Report Share Posted September 18, 2003 Found the answer when I rechecked previous postings (I missed it first time around). There is an upper limit of 2 GB on the catalog file. Obviously it would help if the Retrospect failure mode was a little more informative! Retro 5 under OSX -- 2G catalog file error? HELP! The catalog files on disk are: Eta: 1.99 GB Theta: 1.98 GB I think both the catalogs are actually uncompressed. Attempting to compress the catalog gives error -39 (unexpected end of file). The catalog options then still have the radio button showing the intent to have the catalog compressed, although the reality is different. Link to comment Share on other sites More sharing options...
CallMeDave Posted September 19, 2003 Report Share Posted September 19, 2003 Quote: I think both the catalogs are actually uncompressed. Attempting to compress the catalog gives error -39 (unexpected end of file). The catalog options then still have the radio button showing the intent to have the catalog compressed, although the reality is different. Note that the default setting for new catalogs in 5.1 is now compressed. Shame it wasn't this way on the original 5.0 release. Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.