tdknox Posted February 27, 2004 Report Share Posted February 27, 2004 I have an MDD 2x1.25GHz G4 w/2GB RAM running OS X 10.3.2 and Retrospect Workgroup 6.0, backing up to files on an external FireWire 250GB hard drive. The server itself can back up fine, and all but one of my clients have no issues. However, I have a Win2K client running 6.5.132, connected via LAN to my server. Any attempt to back up this particular client results in an error box popping up with the cryptic message: Quote: Internal consistency check failed: Assertion check at "elem.c-821" Then Retrospect spontaneously crashes. I've rebooted the client, re-installed the client software, updated the client software and updated the server from 5.1.127 to 6.0.128. Rebooted the server. Deleted and re-created the policy for the client. Deleted and re-created the backup set file. Nothing helps, and I cannot back up this client. This has been going on for about 2 months now. Anyone have a suggestion? Thanks! Tom Link to comment Share on other sites More sharing options...
natew Posted February 27, 2004 Report Share Posted February 27, 2004 Hi Can you tell if the problem happens during the file scan or after files are being copied? Does it happen if you try to backup just a subfolder on the client machine? Have you tried updating/reinstalling Network drivers on the client? Thanks Nate Link to comment Share on other sites More sharing options...
tdknox Posted February 28, 2004 Author Report Share Posted February 28, 2004 It hapens instantly, within seconds of the backup initiating. No, I have not replaced the network drives on the remote Win2K client. The system works for the customer, and all networking not related to Dantz works reliably. Tom Link to comment Share on other sites More sharing options...
natew Posted March 1, 2004 Report Share Posted March 1, 2004 Hi That isn't terribly unusual. There are many cases where corrupt TCP/IP or flaky drivers can work fine for filesharing and internet but fail terribly with Retrospect client. in many cases an uninstall/reinstall of the network driver will sort things out. Nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.