Retrospect 6.0.212 crashes and never completes a backup

[sylvaherald]

Hi All,

 

Using Retrospect Workgroup on a clean install of OS X Server 10.4.2. I'm backing up to a LaCie Triple Interface 500GB drive, on Firewire 800. When I create a backup set, I don't do removable disk, I chose 'File' and place that file on the formatted LaCie.

 

Every single time I try to backup the files that the server hosts, which btw, are NOT in use, Retrospect crashes near the end of the process. I've tried so many different configs. Everytime I try to backup, Retrospect crashes, leaving no messages as to why in its log, and I get backups that I can't use. Sometimes, it just restarts the computer instantly, and I get a message about Retrospect failing when it boots back up and then other times, when it crashes, my screen turns to a tint of grey telling me I need to shut down.

 

I've called Retrospect, and their suggestions yielded no help.

 

This drive that we're trying to backup hosts 20+ users' data. It desperately needs nightly backups. If I chose the duplicate drive function in Retrospect, it works flawlessly. But I only want to backup changed files nightly, not to a completely new backup every night.

 

Please help!

[CallMeDave]

- What version of the Retrospect RDU is loading with the program? (you can find it listed in the Operations Log each time the program launches).

 

 

 

- What were the suggestions that "Retrospect" (the company is named "EMC/Dantz") gave you when you called?

 

 

 

- What model of Macintosh are you using?

 

 

 

- What is the memory configuration of the Macintosh? Is there non-Apple RAM installed?

 

 

 

- Is there a Retrospect file in /Library/Logs/CrashReporter/ ?

 

 

 

The "tint of grey" is an OS X kernal panic, something usually related to hardware interactions.

 

 

 

- Do you have other devices on the FireWire bus?

 

 

 

- Have you tried connecting the LaCie to a FireWire 400 port instead?

[sylvaherald]

- What version of the Retrospect RDU is loading with the program? (you can find it listed in the Operations Log each time the program launches).

 

? Retrospect version 6.0.212

launched at 8/8/2005 8:04 AM

+ Retrospect Driver Update, version 6.5.102

 

- What were the suggestions that "Retrospect" (the company is named "EMC/Dantz") gave you when you called?

 

Dantz suggested that I try to split the catalog file from the backup somehow, b/c they thought that might be causing an issue.

 

- What model of Macintosh are you using?

 

PowerMac G5 2.0DP

 

- What is the memory configuration of the Macintosh? Is there non-Apple RAM installed?

 

1.5GB RAM/Apple Installed

 

- Is there a Retrospect file in /Library/Logs/CrashReporter/ ?

 

Yes, with a ton of stuff in there

 

The "tint of grey" is an OS X kernal panic, something usually related to hardware interactions.

 

- Do you have other devices on the FireWire bus?

 

No, just this drive, which runs of FW800

 

- Have you tried connecting the LaCie to a FireWire 400 port instead?

 

No

[ringg]

If you say that you can perform Duplicate drive function flawlessly you might have another option - not that this will solve your problem of crashes. You can perform an "incremental" duplicate. Begin by creating a new script. Select "Duplicate" for the type of script. Select the Source Volume. Then when you select the Destination Volume, select "Replace Corresponding Files" from the pull down window at the top of the window. Only files that have been changed will be copied. Try that until you get the crashing problem fixed.

[CallMeDave]

Both "Replace entire disk" and "Replace Corresponding Files" do incemental Duplicates. The difference is that with the former, the files will be deleted from the Destination if they've been deleted from the Source (resulting in a mirror copy each time), while the latter will not delete anything from the Destination. In that case, the Destination drive will likely contain more files then the Source after the first operation.

 

Dave