Jump to content

markwmsn

Members
  • Content count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

About markwmsn

  • Rank
    Occasional Forum Poster
  1. markwmsn

    Retrospect 9.0.2 client respawn loop

    Just for the record, the problem continues on 10.2.0.
  2. I have a MacBook Pro running Mountain Lion 10.8.2 that has developed a problem with its Retrospect 9.0.2 client software. Even after completely uninstalling and reinstalling it, the client repeatedly exits with code 2 and immediately respawns. Eventually, the system throttle back the respawn rate. Naturally, nothing useful can be done with this client when it's going up and down like a yoyo. Any ideas on debugging this "code 2" exit? There are no other germane console messages on the client machine, often no other messages at all among a string of exit/respawn message pairs.
  3. markwmsn

    Additional Client License - Buy On Line

    Try the Retrospect Online Store, select Add-On, pick a package of 1, 5 or 10 client licenses. http://go.iomega.com/en-us/products/backup-software/retrospect-mac/add-on/
  4. markwmsn

    "Never Backed Up" report

    In my case, the whole disk has been backed up. What is showing up erroneously in the report is the client itself. (One happens to be a laptop, so backing up that disk is pretty much backing up the laptop. Another is a single-disk virtual XP machine, same deal.) So, what criterion would select the disks and not the clients to which they are connected? Alternatively, what would it take to get a backup date or "backed up" status on the entry for a Client? By the way, why does right-click "Duplicate report..." seem to do nothing? It would have been nice to edit a copy instead of mucking with the supplied example.
  5. :confused2: How do you figure that? How do you say "Backup folders named 'B' enclosed by folders named 'A'" if you have only a 'folder' selector and no 'enclosing folder' selector?
  6. Unfortunately, v6 will not write to a v5 backup set.
  7. You can rebuild the catalog from the backup tape(s).
  8. I'm not with Dantz, but maybe I can help. The "1 execution errors" message is just telling you how many other messages it gave you. In this case, there is just the one message 'File “Date & Time Preferences”: different modification date/time (set: 7/29/2002 9:25:02 AM, vol: 7/29/2002 10:11:37 AM), path: “OS 9 HD:System Folder:Preferences:Date & Time Preferences”. ' That is, the time stamp on this mentioned file was changed between the time it was backed up and the time it was checked. In the other example (over in the OS X forum), there were three execution errors, two of these time stamp discrepancies and one data size change. None of these is particularly surprising in a busy system. Retrospect doesn't consider any of these errors serious enough to stop execution, but reports them to you so you can decide whether you think action is required. (For example. if the change to Date & Time Preferences was a change of time zone, you might want to back up that file again to preserve the change.)
  9. Funny, I'm seeing this thread in "Macintosh OS 9 and Earlier >> Desktop and Workgroup for Macintosh", but the main forum list shows it with the same description as the line above: Macintosh OS 9 and Earlier Express for Macintosh For general discussions on Retrospect Express for Macintosh. Desktop and Workgroup for Macintosh For general discussions on Retrospect Express for Macintosh. Note that both carry the same description. I believe this is what larth as trying to discuss.
  10. markwmsn

    AIT Tape no longer works.

    Bill, I have that same SCSI card and ran into the same question about 2930U versus 2930CU. Adaptec Tech Support assured me that the card we have is supported by Adaptec under Mac OS X (preferrably with the 1.1 drivers) and that it is normal for the Ultra PowerDomain 2930 to show up as 2930CU in Apple System Profiler. They never explained why the designation 2930CU seems to mean different things in different contexts. --Mark
  11. markwmsn

    execution error

    Have you tried telling Retrospect that member 7 is missing? (That was an option on 4.0, wasn't it?)
  12. Thank you for your assistance. This problem has been resolved. Seagate Technical Support finally provided a firmware upgrade (1.22, up from 1.17 for me) that corrected the problem. They did not explain what the new version changed, other than the firmware level number returned in the ID string.
  13. Irena said "Adaptec's website says that the 2930CU is specifically for the PC and the 2930U is for the Mac. When we were compiling our resources we spoke with them and confirmed that the 2930CU is NOT supported on a Mac and is NOT supported under OS X." Whatever the actual real-world designations of the model for the PC and the Mac may be, I have confirmed with Adaptec Tech Support that my SCSI card which shows up on Apple System Profiler as "ADPT,2930CU" *IS* for the Mac and *IS* supported under OS X. I can attest that it came in a PowerDomain 2930 for the Mac box, with a Mac CD and a Mac manual, bears a Mac sticker on the ROM chips, and works just fine on Mac OS 9.2 and X (except for using my tape drive on OS X). Maybe Adaptec switched ID strings around since you were compiling your resources. Maybe they inadvertantly misprogrammed some PowerDomain 2930s with the wrong ID string. Better check with your sources there again. I will do likewise with mine.
  14. Thanks for the response, Irena. You said "You'll need to contact the vendor of the drive for the best steps to take to get the drive to show up to the OS." Seagate said "Seagate Technology does not write drivers for the MAC OS. We depend on our software vendors to handle the drivers. The drivers load with the backup software. Hopefully, your contact with Dantz has resolved this issue." Of course, it hasn't. You said "I can offer you some basic suggestions, but the drive manufacturer is likely going to have more detail." I followed the link to the basic suggestions. The first half has to do with fixing "a SCSI communication error (Bad backup set header, -100 or ­200 errors)", but I can't get that far yet; besides, I think I've already tried pretty much everything but cleaning the heads.. The second half concerns devices not appearing, but I've already followed that all the way down to "contact the drive vendor", and they sent me back to you. You said "Adaptec may be able to help as well." They are trying, but they seem sure that their software is doing its part. You said "Remember, the issue is not (yet) that Retrospect can't see the drive, but that the computer can't see the drive." Actually, the computer CAN see the drive (since it can back up to it with different software); Mac OS X and associated drivers and software can't see the drive. Finally, you said "I'm afraid I don't have any information on the configuration that we've tested this drive with. We do write the software to OPERATE the drive, but not for the drive to show up." It's really a pity you can't find out how you were able to test the drive. That might explain the missing link for me and john_bykowski (the other user with the HyperQIC drive on a 2930, in his own thread). If you hadn't told me that Dantz actually did test the drive and get it to work, I would already have concluded that NOBODY has written software to make the drive show up. Certainly, none of the obvious suspects admits it. Are there any other users out there who have this old tape drive working with this new card? Anybody else care to chime in?
×