Jump to content

Error 519 Retrospect freezes ASIP clients


croo

Recommended Posts

Hi,

 

 

 

The Server that we are trying to back up is an ASIP Server running ASIP 6.3.3. We have had an extensive look at the Dantz knowledgebase and have tried the fixes suggested. During backup, the Server is completely frozen and needs to be restarted using the reset button. The Server is a PowerMac G4 running OS9.1.

 

 

 

We have additionally in the last two days attempted to start a new backup set, hoping that this would resolve issues of corrupt catalogs, but the Server continues to freeze.

 

 

 

Any assistance you can provide will be highly appreciated.

 

 

Link to comment
Share on other sites

  • 2 weeks later...

Some customers have reported problems when backing up AppleShare IP servers

 

with both Retrospect 4.3 and 5.0.

 

 

 

There is one problem reported with Retrospect 5.0 running on an ASIP server,

 

where Retrospect is definitely not the cause:

 

 

 

The ASIP server crashes when Retrospect 5.0 autolaunches or is

 

launched from an alias.

 

 

 

We have identified this to be a problem between Mac OS 9 and the ASIP

 

software that may occur when any Carbon-style application is launched from

 

an alias. We have duplicated this behavior using other Carbon applications,

 

and we have reported the issue to Apple.

 

 

 

Other reported problems currently under investigation include:

 

 

 

Retrospect 4.3 running on an ASIP server asserts failure or

 

hangs during the backup's copy phase.

 

 

 

The ASIP server locks up when the first user logs in following

 

a backup of the server with the Retrospect 4.3 client.

 

 

 

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

 

Retrospect 5.0 client.

 

 

 

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

 

up from an ASIP server with the Retrospect 5.0 client.

 

 

 

Due to the complexity of the AppleShare IP software and the difficulty in

 

reliably reproducing these behaviors in a controlled environment, Dantz has

 

been unable to establish that Retrospect is the cause of these problems. As

 

such, we have opened a developer support case with Apple to determine the

 

root cause of these issues.

 

 

 

We consider this to be a matter of the highest priority, and we will provide

 

additional information on these issues as soon as we have anything

 

significant to report.

 

 

 

Thank you

 

 

 

Dantz Technical Support

 

 

Link to comment
Share on other sites

  • 1 month later...

Hello,

 

 

 

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.

 

 

 

Sincerely,

 

 

 

Dantz Development

 

Technical Support

 

www.dantz.com

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...