Jump to content
Sign in to follow this  
bberndt

Is Retrospect crashing my server??!!

Recommended Posts

We have had this problem from tine to time here, on a Appleshare server that we run, with an installed copy of Retrospect Desktop on the server.

 

 

 

This copy of Retrospect 4.3 backs up the main SCSI harddrive to a SCSI DDS-4 tape drive. Its a 36 GB drive and the tapes are 40 compressed, and usually works just fine...

 

 

 

One of the other drives has been running very full, a 20GB, with ~500 KB free. Its not a boot drive, so I wasn't worried about it.

 

 

 

Lately, the machine has been crashing in an odd manner. I usually first notice that registered users on the ASIP server are not allow to connect. (bad password, it claims) Upon checking the actual machine, the finder is really slow, and programs, such as Retrospect fail to execute, usually with just nothing happening. This is usually fixed by rebooting. Sometimes, it requires formatting and reinstalling the OS and ASIP, though this last time I just cragged and dropped Retrospect to another drive and then back again.

 

 

 

I at first thought it was the full HD causing the problem, but the problem persisted after removing that drive.

 

 

 

In conclusion, the reason I think its Retrospect, is that it seems to occur after the back up is finished, in the early hours of the morning, and is noticed as people start to come in, around 8, and try to log on.

 

 

 

Any help would be appreciated.

Share this post


Link to post
Share on other sites

Dantz has been investigating several problems that customers have reported when backing up an AppleShare IP server with Retrospect 5.0. Reported problems include:

 

 

 

1) The ASIP server crashes when Retrospect 5.0 autolaunches or

 

is launched from an alias.

 

 

 

2) The ASIP server crashes at the beginning of a backup with the

 

Retrospect 5.0 client.

 

 

 

3) Retrospect returns "error 1 (unknown)" for some files backed

 

up from an ASIP server with the Retrospect 5.0 client.

 

 

 

Our investigation has revealed that these problems result from using Carbon APIs with AppleShare IP software. Problem #1 occurs when any Carbon application is launched from an alias, confirming our contention that it is not a Retrospect issue. Retrospect 5.0 uses HFS+ file system calls, as specified by Apple, which stimulate bugs in the AppleShare IP software, resulting in Problems #2 and #3.

 

 

 

We have reported all of these problems to Apple, but Apple's development efforts are now focused on Mac OS X Server. Without a commitment by Apple to address these problems, we have no choice but to suggest that our customers consider replacing AppleShare IP with Mac OS X Server.

 

 

 

------

 

The underlying problems are applicable to Retrospect 4.3 also as Retrospect 4.3 uses the same HFS+ file system calls as Retrospect 5.0.

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×