Jump to content

Retro 6.0.212 Crash on client Mac OS X backup


Recommended Posts

Greetings,

 

I'm seeing repeatable Retrospect crashes when backing up a Mac OS X Tiger client from a Mac running Tiger.

 

Details below:

 

Backup machine:

--------------------

 

New PowerMac G5 Dual 2.5 GHz with Tiger (10.4.2) with File backup on external FireWire 400 drive.

Clients: 1 Windows XP machine, 1 iMac G4 800 MHz with Tiger (10.4.2) with Retro client 6.0.110.

 

My Backup script starts with the Client Container, which starts with the XP machine, then goes to the iMac.

It appears that the iMac backup completes, or nearly completes, and the Retrospect crash (on the PowerMac) occurs before the Compare begins.

 

The last entry in the Retrospect log is:

- 9/26/2005 1:09:32 AM: Copying TinaXDisk on TinaXMac…

 

The crash occurs almost two hours later, as shown by the system.log entry:

 

Sep 26 02:59:55 aladdin crashdump[580]: Retrospect crashed

Sep 26 02:59:56 aladdin crashdump[580]: crash report written to: /Users/osh/Library/Logs/CrashReporter/Retrospect.crash.log

 

A Crash report is generated. The top of it is included below. The crash is repeatable.

 

Additional background:

 

I recently upgraded to this PowerMac G5 from a PowerMac G4 also running the latest Tiger. My last backup using this same configuration (but backing up from the PowerMac G4) was last weekend. The only difference on the client is the installation of the very recent Security Update 2005-008 from Apple.

 

Any suggestions?

 

Thanks,

 

John

 

 

The CrashReporter log begins thusly:

 

**********

 

Host Name: aladdin

Date/Time: 2005-08-28 00:08:33.479 -0500

OS Version: 10.4.2 (Build 8C46)

Report Version: 3

 

Command: Retrospect

Path: /Applications/Other Applications/Retrospect 6.0/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect

Parent: launchd [1]

 

Version: 6.0.212 (6.0)

Build Version: ???

Project Name: ???

Source Version: ???

 

PID: 10328

Thread: 0

 

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0x4fa9e6a0

 

Thread 0 Crashed:

Link to comment
Share on other sites

Hi,

 

A couple questions:

 

1. Are you able to backup your Windows machine without crashing?

2. Is this PowerMac G5 a brand new setup or did you carry over your settings from your PowerMac G4?

3. Have you tried running repair permissions thru the Disk Utility on your iMac client?

4. Have you tried re-installing the Retrospect client on your iMac?

 

Please give these things a try and let us know how it goes.

Link to comment
Share on other sites

Quote:

Hi,

 

A couple questions:

 

1. Are you able to backup your Windows machine without crashing?

 


 

Yes. No problem with the Windows client.

 

Quote:

2. Is this PowerMac G5 a brand new setup or did you carry over your settings from your PowerMac G4?

 


 

I did use the Setup Assistant to transfer over everything but network settings

 

Quote:

3. Have you tried running repair permissions thru the Disk Utility on your iMac client?

 


 

Yes, nothing unusual was found (secure .log, and one other file with "special" permissions).

 

Quote:

4. Have you tried re-installing the Retrospect client on your iMac?

 


 

No! I did re-install Retrospect 6.0.212 on the G5, but I haven't re-installed the client on the iMac. I'll try that.

 

Thanks!

 

Quote:

Please give these things a try and let us know how it goes.

 


Link to comment
Share on other sites

Here's the latest.

 

 

 

I re-installed the client software, and re-ran the backup. Slightly different scenario, since the first client (the Windows laptop) was missing. The copy completed successfully, and after a seemingly long wait, the compare started, and completed successfully! The script continued on to a successful backup of the backup G5 server as well.

 

 

 

When looking at the log, I see 32 entries similar to the following:

 

 

 

Backup set format inconsistency (7 at 8798597)

 

 

 

I searched the text in the knowledgebase, and didn't get any hits. Any ideas?

 

 

 

I'll add the Windows laptop and try the whole script again tonight.

 

 

 

Thanks,

 

 

 

John

Link to comment
Share on other sites

Quote:

> Backup set format inconsistency

 

 

 

This is a bad thing on a File Backup Set, and would lead me to suspect the integrety of the Destination. The external drive/bridge/case/cable might very well be the problem (as could the new G5's FireWire port).

 

 

 

Dave

 


 

 

 

Lovely.

 

 

 

These are new external backup mechanisms. Seagate drives inside OWC Mercury FireWire/USB cases. I've had good luck with these in the past. I'll reformat it and write zero's to see if any problems pop up.

 

 

 

We'll see what happens tonight.

 

 

 

Thanks for the insight.

 

 

 

John

Link to comment
Share on other sites

Quote:

 

We'll see what happens tonight.

 

 


 

Last night, the backup completed successfully - no more crashes, no more errors!

 

I did re-format the external drive, writing zero's to it. I also unplugged and re-plugged the FireWire cable to the external drive. Perhaps that cleaned up the device errors. I guess the re-installation of the client cleared up the crashes - that or the phase of the moon...

 

Thanks!

 

John

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...