Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by shadowspawn

  1. Quote: What does the profiler show for your Adaptec card? Ironically mine has an older ROM. Here are the details for my (working) card: Card Type scsi Card Name ADPT,2930CU Card Modem ADPT,1686806-04 Vendor ID 9004 Device ID 5078 ROM# 4.0 Revision 3
  2. Quote: I just switched to Mac OS 10.2.4 from Mac OS 9.2.2, using the same install of Retrospect 5.0.238. I have not had a successful backup to my SCSI Ecrix VXA-1 tape drive since doing so. I always get error 102 (trouble communicating). I have never had problems with Mac OS 9. The VXA drive and a JAZ drive are the only things on my SCSI bus. My SCSI card is an Adaptec 2930CU. I am using the same tape drive, Mac OS, and SCSI card, so there is a good chance it will work! The Adaptec card was unreliable early on with Mac OS X (and it was hell), but Adaptec finally got the drivers right. A few things to confirm: a) Are you using the latest Adaptec driver? I am not sure whether you need to install this separately, or whether it is built into Mac OS X. Check in the System Profiler, under Extensions. I have one called "Adaptec290X-2930.kext" at version 1.1.0. Are you using the latest VXA firmware? In Retrospect, got into Devices, and click the Device Status button. I have version 2C8C. c) As Amy covered, try having just the VXA drive connected on SCSI, nothing else. Try a different cable too.
  3. Quote: A. change the average on-time of each machine from 5 days, 10 hours a day to 24/7 (a tremendous waste of power) If you want suggestions for right now, I vote for A, and it is what I am doing with my clients. Since I have mixed Mac/PC clients, and the shutdown-after-backup had never been an option with the PC clients, it wasn't a big deal. Set the Energy Saver so the monitor goes to sleep, the hard disk goes to sleep, but the computer does NOT go to sleep. This hopefully reduce the "tremendous" waste of power to merely irritating. :-) Tell Mac OS 9 clients: shutdown and walk away Tell Mac OS X clients: logout and walk away. (Some people will need reminding when you notice they are not getting backed up, the shutdown and walk away gets fairly ingrained!)
  4. I notice a big hit during the catalog matching, and based on the memory usage visible in "top" suspect that more memory will help. Could be a good excuse to get your desktop computer outfitted with 1GB of RAM. :-)
  5. I am fairly certain that there were issues with some older versions of Retrospect not recognising that the VXA drive supports hardware compression, but don't have an URL for you. Based on your useful empirical evidence, it seems likely you are affected by the issue, so turn off software compression. This does not prevent hardware compression. The hardware and software compression options overlap a little, but you allow/disallow hardware compression when you create the backup set, and allow/disallow software compression when you create the backup or backup script.
  6. Another couple of data points, autoLaunch is working ok for me, until recently on a DP 450 MHz G4 running Mac OS X 10.1.5, and now on a DP 867 MHz G4 running Mac OS X 10.2.2. To cover the background again, Retrospect is launched automatically by a process called RetroRun. Two potential problems: a) this process may die. This was a problem with some earlier versions of Retrospect on some configurations, but should be fixed by upgrading to the latest version of Retrospect. this process might not be launched when your computer reboots, usually after copying Retrospect to a new computer rather than installing, and this should be fixed by reinstalling. So there are already known solutions to the known problems. To help pin down a potentially new problem you can help identify whether and when RetroRun goes bad, read on... 1) The first step is make sure you are running latest version of Retrospect, 5.0.238. 2) Then to find out whether RetroRun is running right now, launch the Terminal utility and paste in the command ps -auxwww | grep RetroRun and hit return. If you type the command, note that it is all case sensitive. I get something that looks like this: % ps -auxwww | grep RetroRun root 2320 0.0 0.0 15488 64 ?? Ss Mon04PM 0:18.27 /Library/StartupItems/RetroRun/RetroRun john 2570 0.0 0.1 1372 232 std R+ 5:44PM 0:00.01 grep RetroRun That first line tells me that RetroRun is running, and that is it owned by root as it should be, so I am looking good. 3) If it is not running, try rebooting and check again. If it is not running straight after a reboot, try reinstalling Retrospect. Reboot again. If it is still not running straight after a boot, carry on through the steps anyway in case the issue is a very early crash in RetroRun, but you are more likely to have an install problem. 4) OK, it is running straight after a boot but something goes wrong later. Presumably it is crashing. An easy way to find out is: Open the Console utility. Open its preferences. Click on the Crash tab. Turn on "Enable crash reporting". Turn on "Automatically display crash logs". Close preferences. Leave Console running but Hide it. Now when something crashes, Console will come to the front with a crash log window with technical details about what went wrong. The window title says which application bit the dust, for example, Finder.crash.log. One small trap is that the window shows the oldest messages at the top, so scroll to the bottom for details on the latest crash. (If you do not have Console running it will open new crash logs the next time you launch Console, but it is much more immediate feedback to keep it running so logs show up straight away.) 5) Get RetroRun running again without rebooting by launching Retrospect and quitting it again. Check whether RetroRun is running using the ps command in Terminal. 6) Next time Retrospect fails to autoLaunch, before doing anything else check to see if RetroRun is running, and check to see whether Console has a RetroRun crash window open. 7) Report back with the gory details of what went wrong when, and see if anyone has any bright ideas!
  7. One unlikely thing to try is running Disk Utility on your firewire drive in case the files/folders reappear if a problem is repaired. However, I'm still wondering about file permissions. I have not used ASIP for a while, I think the permissions issue might be avoided when connected to the ASIP server as the administrator account. Were you connected as the ASIP administrator account? If so, I give up. :-) The reason I am still asking is because the symptoms fit your description, and I haven't though of anything more likely. To illustrate the problem with a small example, on my Mac OS 9 "server" using personal file sharing I create Share Me [shared folder, everyone: read & write] Public [everyone: read & write] public file Private [everyone: none] private file I then connect as guest from my Mac OS X computer. Running a duplicate using Retrospect shows no errors, but I do not get the "private file" duplicated because although Retrospect can see that the folder exists, it can not see the contents of the folder. - 15/12/2002 12:28:39 AM: Copying Share Me… 15/12/2002 12:28:40 AM: Comparing trstest on Nine… 15/12/2002 12:28:40 AM: Execution completed successfully. Completed: 3 files, 4 KB Performance: 0.4 MB/minute (0.2 copy, 0.0 compare) Duration: 00:00:01 Retrospect does not warn that folder contents are not reachable, although perhaps it should!
  8. > I had verification on for some of the scripts. a) Scripts? Do the scripts covering the volumes with missing files use a selection criteria? What source did you use for the duplicate, a Retrospect client installed on the RAID server, or via file sharing? If you did it via file sharing, how did you have the volume mounted? File sharing privileges come into play if you are doing the copy via file sharing, so it matters what username was used to mount the volume.
  9. I'm also struggling with mail in general, but Outlook in particular. What I am considering is continuing nightly incremental backups, but only backing up mail files every 7 days. It hurts when the majority of an overnight backup across all clients is Outlook files!
  10. DHodges, have another look at the non-root set of instructions AmyC listed, you are leaving out the steps to save the password. Note that there is a "Configure" tab when you first launch Retrospect, but once you are in the Volumes window there is a "Configure" command which you use to save the password. * From the Volumes menu choose Configure (Command-J) * Provide Retrospect with the password to connect to the AFP volume Sleep well...
  11. I have seen some kernel crashes when changing USB devices since Mac OS X 10.2, unrelated to Retrospect, so might not be Retrospect at fault. Does it happen 100% of the time, under the circumstances you described? How are your tape drives connected? If you thrash the same interface (SCSI/firewire) without using Retrospect, like say a big Finder copy to a hard drive, does the same problem occur when you switch using the KVM?
  12. You can update Windows clients, and Mac OS 8/9 clients, but can not currently update Mac OS X clients. Post again if your clients are not running Mac OS X, because it should work!
  13. In theory one thing you can do is install a Windows client inside Virtual PC, and treat it as just another client. Obviously Virtual PC needs to be active when tha backup is running, just like any other client. (In practice, I am doing this and manual backups work ok but I am having a problem where Backup Server always claims the user has deferred the backup.)
  14. > We are running OS 10.2.1 with a clean system install and all updates. > The only other third-party software is Timbuktu 6.0.2. ... > Two Sony AIT drives are connected via Ultra Wide SCSI to an Initio > Miles Ultra Wide SCSI card with the latest firmware. Do you also have the Miles driver installed? The SCSI adapter compatibility list says a firmware update and driver are required. I'm not familiar with the Miles card, so just quoting from the Dantz page: http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27381 > A CD-RW is connected to an Orange Micro SCSI card with the latest firmware. The Orange Micro card is not supported on Mac OS X 10.2.1 yet, at least as far as Retrospect is concerned. (My guess is that this would not affect your disappearing-client problem, but could conceivably affect the hang-on-quit you are seeing, but only my guess.) > The current problem is that the clients can be "seen" when scanning but > cannot be seen when running the backup server. This does not happen > immediately but only after Retrospect has been running a few hours. Do you have a "speed threshold" set? This is in the Client Execution section of the options for the backup server script. There is a known issue where Mac OS X clients switch off unless this is set to zero. http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27285
  15. I actually feel the same, Retrospect was awesomely stable for years, but since upgrading to Retrospect 5 it is rare to have a week go by without a problem. However, two suggestions for improving reliability on our end: 1) Retrospect 5 is much more sensitive to network problems than previous versions, in particular it is prone to hanging rather than timing out when a problem occurs. If a particular client is giving problems it is worth going through the troubleshooting guides, even if that client worked fine with previous Retrospect versions. 2) Retrospect (and Mac OS X) are much more sensitive to SCSI issues than previous versions. There are a limited number of cards qualified for Mac OS X 10.1 and a very small number qualified for Mac OS X 10.2. It is worth checking very carefully that you have a qualified card, with the latest driver, the latest firmware, and that the SCSI device also has the latest firmware. (I spent months in reliability hell before the Adaptec cards were officially demoted!)
  16. I might have missed this, but is your airport network using an airport base station, or are you using direct computer-to-computer (airport) networking? (i.e. does your desktop computer have an airport card.) Is ethernet an option for doing the backup? (I am not suggesting yet you give up on airport, just exploring the fallback positions!)
  17. > By the way, you mentioned "a documented issue with Mac OS X 10.2" in > your reply. What is the issue and where is it documented? The explanation below is from the "Retrospect 5.0 Updated for Jaguar" announcement in this forum, there is further information in the ReadMe and presumably also in the KnowledgeBase. The last line is the one you needed to spot in the large amount of information available. :-) -- 4. Error -40 on clients running Mac OS X 10.2.x. Retrospect generates an error: "Can't read file retropds.22, error -40 (file positioning error)" resulting in the "retro22.pds" file not being backed up. This file is necessary for the Retrospect client software to operate correctly. Dantz is working with Apple to solve this problem. In the meantime, the Retrospect client software should be reinstalled manually following a Mac OS X 10.2.x system restore.
  18. > Well I give up. John, what you told me was exactly right and > Retrospect did update. But retrospect is still doing the same > exact thing it was doing before (frequent authentication, > autostart not functioning). I have been away for a week, so sorry for the late post. I may have a solution, although you will find it difficult to believe. Empty the trash. There is a bizarre bug in Mac OS X 10.2 where if you replace an application with one with the same name and location, the operating system sometimes runs a cached copy of the old one from the trash. (I am not sure whether rebooting also fixes the cache issue, but emptying the trash certainly has worked on several occasions for us ending considerable confusion about what on earth was going on.)
  19. > And last (so far) but certainly not least, I can't run backups > from the restored disks. I get the Net Retry hang thang. Two suggestions: 1) Uninstall the Retrospect client, and reinstall the client. There is a documented issue with Mac OS X 10.2 with one particular file internal to the client which means the client is not completely restored and must be manually reinstalled. 2) If this does not immediately fix the problem, run something to verify your hard disk. I think your issue is the dud client, but I had the same symptoms on a disk which failed validation although otherwise appeared fine.
  20. Short version: in my opinion there is definitely a bug in Retrospect BUT the bug only shows when you have a communication issue, and this you can troubleshoot. Longer version: I had major problems with infinite Net Retries when Retrospect 5 was first released. I isolated the majority of the hangs to two particular clients, which I performed major software and hardware surgery on until the problem was fixed. In the last two months I have only had infinite Net Retries when Mac OS X clients leave disk images mounted. Again IMHO a bug in Retrospect, but again, something I can try and avoid/fix. I have not had a chance to check whether this particular issue has been fixed in the latest Retrospect. From memory there is an excellent and exhaustive troubleshooting guide in the knowledge base in the error 519 tech note.
  21. > Tried to run the Retrospect driver update and it started retrospect and sat there. The driver update is just a file, not an installer. The Retrospect installer probably includes the latest driver as well. It sounds like you may not have run the installer yet, it is called Install Retrospect To check the driver version after the install, launch Retrospect and open the Log window (which has a message saying the driver version each time you launch), or check the driver file directly -- it belongs in the same folder as the Retrospect application. The version should be 3.0.104. If you do need to apply the driver update, you manually copy the driver file to the same folder as the Retrospect application. i.e. copy Retrospect 5.0 Driver Update to /Applications/Retrospect 5.0 (You are not the first person to be misled by the "Update" in the name of the driver file, it seems Dantz should change the name next version!)
  22. The good news is there is a likely explanation. The bad news is that your SCSI card is not supported on X right now. Check the recent thread DANTZ UPDATE ON SCSI ADAPTERS IN MAC OS X, or the Dantz knowledge base, or the Dantz supported scsi cards page on their web site. Here is the URL to the posting in this forum: http://forums.dantz.com/ubbthreads/showflat.php?Cat=&Board=Desktopworkgrupx&Number=14240&page=0&view=collapsed&sb=5&o=0&fpart=1
  23. 1) A spread bet on first week of November, no side bets from me. 2) Actually I am more interested in whether the update will address any of the various pre-Jaguar issues still outstanding. (The worst affecting me is the infinite Net Retry.) I am lucky enough to be able to work around the Jaguar issues. 3) In reply to queball's recent "Of course you hope...". Ouch, no fair complaining about getting insufficient information and then asking for more incomplete information. Dantz are not going to release untested partial updates when they are close to finishing a proper update, and are extremely unlikely to release details about their internal progress (interesting though it would be!).
  24. Buy one client for Windows computer. The registry on the PC will not be backed up unless you also setup the Registry Backup utility on the Windows client. There is no way to get 420 Gig of data fast. :-)
  25. > Somehow Mac installers still have this volume mentality which is > totally inappropriate in a UNIX world. Heck, the problem is more that unix has this fixed path mentality which is totally inappropriate in a Mac world. :-) It sounds like the installer is looking for a partition with both /Application and /Library/StartupItems, but is not recognising the mount point for this purpose. As a work-around, you could try making a link on your second partition back to /Library on the main partition. The installer might then consider your Application partition a "complete" partition, hopefully finding both /Applications and /Library.