X

Retrospect issues: Internal Consistency Check error;

Retrospect issues: Internal Consistency Check error;

CNET staff
2 min read
Time checking; header error; more

Internal Consistency Check error Joseph Holmes writes: "I've been getting an error in Retrospect 5.0.205 (the latest version): 'Internal Consistency Check Failed: Assertion Check at 'elem.c-812.'" He contacted Dantz about this and they replied:

"Some users with the new Retrospect Driver Update have reported this problem. If you are running the Driver Update, and you do not own a VXA tape drive, try removing the driver. Dantz is aware of this problem and working toward a solution."

Thomas Isenbarger sent us a similar message confirming the problem and solution.

Time checking via AppleTalk on remote volumes John Manning writes: "There appears to be a bug in the way OS X translates file time information on remote volumes, at least when connecting via AppleTalk. I created a small text file on the remote machine and checked the modification time on that day and about a week later. The information returned via ssh is correct (and consistent). The information returned via AppleTalk is wrong. Worse, it isn't static, which causes Retrospect Express to repeatedly backup files that haven't actually changed. [The primary machine is a beige G3 with a G4/500 upgrade. The remote machine is a dual-USB iBook. Both are running 10.1.4.]

Bad Backup Set header errors with Sony DDS-4 DAT under Mac OS X Michael de Haan alerted us to a Dantz Knowledgebase article that states: "Some users have reported "bad backup set headers" while attempting to back up to the Sony SDT-10000 or SDT-11000 (DDS-4) drives under OS X. All incidents have had a SCSI adapter in common, the Adaptec 39160." The article provides a solution, which worked for Michael.

Server limits? Russell Owen comments on some limitations he found with Retrospect Server 5:

  • Retrospect Server running on Windows still cannot back up Mac OS X clients.
  • Retrospect Server 5 does not see Macs running older client software. Thus I'd have to buy new client licenses to see my old Mac OS 8 and 8 computers (which I suspect would then render them invisible to our main Windows backup server). Fortunately the older version of Retrospect still runs fine in Classic mode.

"Your Macintosh Clock may be wrong" dialog See the Retrospect item on today's OS 9 page for coverage of a patch for Retrospect 4.1 or earlier.