Jump to content

4.3 Crashes on ASIP6.3.3


Recommended Posts

Hi,

 

 

 

ASIP 6.3.3 runing on two G4s running 9.2.2 and retrospec 4.3

 

 

 

Both crash intermittantly when attempting to backup.

 

 

 

1 Duplicates to HD 30gb more than 100,000 files

 

1 Backs up to tape 60gb more than 100,000 files

 

 

 

At least once or twice a week both will fail (at night) and lock the server.

 

 

 

Both these Macs have been built clean from scratch. They have minimal extentions

 

and no other scsi devices than are required.

 

 

 

The both have 1.5gb of memory, vmem is off.

 

 

 

Please can someone suggest the best config for retrospect so I can be confident that these macs

 

will backup all the time.

 

 

 

 

Link to comment
Share on other sites

The following article is the ASIP compatibility statement from Dantz. While this statement specifically mentions Retrospect 5.0, issues similar to those you are experiencing exist in Retrospect 4.3 also. The workarounds posted would be most relevant.

 

---------

 

 

 

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.

 

 

 

Some users of Retrospect have found the following workarounds helpful.

 

 

 

1) Try allocating more memory to Retrospect via the get info Window (Mac OS 9 users) in the finder

 

 

 

2) Turn off Sherlock Auto Indexing on the server

 

 

 

3) Configure Energy Saver (or Retrospect if the backup happens locally) to Restart the server every day following the backup or before the first users arrive in the morning.

 

 

 

4) You can try to perform a backup of the server while AppleShare itself is disabled, but this WILL prevent you from copying any AppleShare privileges.

 

 

 

5) If you backup is local to the server, try backing up the server as a client.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...