Jump to content

Recommended Posts

This is getting old fast, folks. Since Retrospect 5 manages to disable my AppleShare IP server every time I try to back it up, I have to run the backup from home, late at night. Last night the backup had problems (yet another corrupted catalog), and it took me until 1:30 AM to get it fixed. I have NEVER before used a product that caused me so much grief! Not to mention the fact that I am getting REALLY crabby from lack of sleep...

 

 

 

The only way I have found to get a successful backup is to shut down ASIP, restart the server with all of the AppleShare-related extensions turned off, run the backup, then restart the server with the AppleShare stuff turned back on. This is a royal pain, as there does not seem to be any way to script this (and believe me, I've tried). At least I have Timbuktu and a cable modem, otherwise it would be impossible.

 

 

 

Today I tried mounting the AppleShare server as a shared volume (just like I would access it from my computer), instead of as a volume specified by Retrospect. Once again, the backup got partway through (141 files) and then hosed my server, bringing down both AppleShare and Meeting Maker. The only thing unique about this time was that it gave me about a hundred "different creation date/time" or "different modification date/time" messages--all of which said that the "set" time was exactly one hour earlier than the "vol" time. It then said "error -35, volume doesn't exist". That's funny, it was there a minute ago! I guess that's 'cause Retrospect blasted it again somehow.

 

 

 

I won't bother with all of the details of my configuration--it's no different than that of many people who have already posted (except maybe that I'm backing up to file sets on FireWire hard drives instead of to tapes or CDs). It's obvious that the current version of Retrospect crashes AppleShare servers (and machines with sharing turned on). This has been reported over and over again. The fact is this: it used to work in Retrospect 4, and it doesn't work in 5.

 

 

 

The people at Dantz need to know that this is NOT a trivial problem for the people who rely on their product. The data on my server is much more critical that on my users' workstations. It's much more important to me that Retrospect work with my server than with workstations.

 

 

 

The least they could do is give us some idea if a fix for this is in the works, and when I might be able to go back to getting a full night's sleep.

 

 

 

Thanks for letting me vent.

 

 

 

 

Link to comment
Share on other sites

We are voraciously investigating the cause of ASIP crashes with Retrospect 5.0, and we will let everyone here know as soon as we have any information to report. This investigation continues to be our highest priority.

 

 

 

Irena Solomon

 

Dantz Tech Support

Link to comment
Share on other sites

*UPDATE*

 

 

 

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...