Jump to content

palter

Members
  • Content count

    31
  • Joined

  • Last visited

Community Reputation

0 Neutral

About palter

  • Rank
    Occasional Forum Poster
  1. Strange. The 6.5 client works fine for me on RHEL 3. (For that matter, the 6.0 client seemed to work as well before I upgraded to 6.5.) What kind of problem are you experiencing?
  2. I have the same type drive. First, the drive doesn't support hardware compression. Use software compression. Second, the quoted maximum rate is for a SCSI controller. On IDE, it won't be as fast. (Further, I believe the 240 MB/min presumes software compression as well which means the real hardware maximum speed is 120 MB/min.)
  3. The Linux client only works on x86 (i.e., Intel, AMD) based systems. It will not work on Macs. - Gary
  4. [i can't reply to this post directly in its original forum and I figured that this was the most appopriate alternate forum.] Thanks for the fix. But, for completeness sake, I think you should fix the permissions on the "Retrospect Client" folder and its contents in /Applications as well. They appear to be world-writable by default which isn't good. (Forutnately, the permissions on pitond are secure enough to prevent an unprivileged user from replacing it with something malicious that could run as root.) - Gary Palter Quote: Run this AppleScript on computers installed with Retrospect's Mac OS X Client software to fix the following bug: Incorrect permissions are assigned to the RetroClient folder and, in some cases, to the StartupItems folder. Note: The following permissions will be set: drwxrwxr-x root admin /Library/StartupItems drwxrwxr-x root admin /Library/StartupItems/RetroClient -rwxrwxr-x root admin /Library/StartupItems/RetroClient/RetroClient -rwxrwxr-x root admin /Library/StartupItems/RetroClient/StartupParameters.plist Filename: client_security_patch.sit Supported versions: 5.x client System's supported: Mac OS X only
  5. STT3401A-ED is a Travan 40GB drive, right? (Based on the model numbers listed at Seagate's site, this appears to be the most likely candidate.) You need at least Retrospect 5.6 with Driver Update (RDU) 3.1.102, Retrospect 6.0 with RDU 3.3.105, or Retrospect 6.5 to use this drive. - Gary
  6. palter

    Assertion failure at "hfslvtree.cpp-278"

    I ran some tests over the weekend using the new Mac OS X client referenced above. The new client successfully backed up my Mac OS X client without the assertion failure. Further experimentation showed that the client now explicitly excludes the named UNIX pipes created by Norton Personal Firewall 2.0. Presumably, it excludes all named pipe files, right? I originally reported this assertion failure in August 2002 and found the cause and a workaround about a month later. At the time, Robin Mayoff told me that an report (#893000) had been filed with engineering. Yet, I was never informed that you had resolved the problem. Why not? Also, I note that the updates page still lists the previous version (5.0.540) of the Mac OS X client. Is this new version (5.1.106) not officially released yet? And, is there a list of bug fixes and improvements for the new version? (I noticed that the download didn't include a ReadMe file.) Finally, I noticed that I no longer get the error File "Herman:Applications:Retrospect Client:Retrospect Client.app:Contents:Resources:retropds.22": can't read, error -1105 (improper seek) while backing up my Mac OS X client and said file is, in fact, copied to the backup set. Thanks for that fix! - Gary
  7. palter

    Retrospect 6.5?

    I just received a copy of the latest PC Connection catalog. Much to my surprise, I found a listing for Retrospect Professional 6.5 which claims "Now supports Windows Server 2003". Any comment? - Gary
  8. Just for the record ... I spoke with a friend who had the same tape drive as myself and was using Retrospect for backup. He reported that he never got an error when switching tapes. So, it became obvious that there was something wrong with my system. Well, about three weeks ago, my tape drive died. It would refuse to recognize any tapes. (I.e., I'd insert a tape and the drive would just sit there. Normally, on insertion, a TR-5 drive spins the tape a bit to verify that it's OK.) Of course, this happened the day after the warranty expired. I have upgraded to a Seagate Hornet 40 (Travan TR-7) internal ATAPI drive. It's working flawlessly so far. Thanks for putting up with me through all this, - Gary
  9. palter

    RH 8 troubles

    I upgraded my Linux client to Red Hat 8.0 earlier this week. Retrospect had no trouble backing up said client after the upgrade.
  10. palter

    Assertion failure at "hfslvtree.cpp-278"

    Yes, it still works for me. You might want to use the volume browser to look at your Macintosh client's boot volume. You can then apply the selector in the browser window to see if it's properly selecting the files.
  11. palter

    Assertion failure at "hfslvtree.cpp-278"

    Thanks to some information in another thread, I was able to discover the cause of the assertion failure. It occurs whenever Retrospect tries to backup a UNIX named pipe. (You can tell that a file is a named pipe in that the 'ls' command will display a 'p' as part of its mode string (e.g., 'prw-rw-rw-').) In particular, I am running Norton Personal Firewall 2.0. It creates three UNIX named pipes with the pathnames /private/var/log/Npfkernel.log.fifo /private/var/tmp/NpfCmds.fifo /private/var/tmp/NpfResponse.fifo Any attempt to backup these files produce the assertion failure at "hfslvtree.cpp-278". I created a selector to exclude these files (and other named pipes) and was able to successfully backup my Mac OS X client. The selector I used is Mac OS regular file flag is not set and Mac OS symbolic link flag is not set and Mac OS hard link flag is not set (In theory, this selector would also exclude device files but they reside in /dev which is automatically excluded by the Mac OS X client anyway.) I hope this information is helpful. - Gary Palter
  12. Thanks for the information; it allowed me to discover the reason my backup attempts failed. I am running Norton Personal Firewall 2.0. It creates three UNIX named pipes with the pathnames /private/var/log/Npfkernel.log.fifo /private/var/tmp/NpfCmds.fifo /private/var/tmp/NpfResponse.fifo Any attempt to backup these files produce the assertion failure at "hfslvtree.cpp-278". I created a selector to exclude these files (and other named pipes) and was able to successfully backup my Mac OS X client. The selector I used is Mac OS regular file flag is not set and Mac OS symbolic link flag is not set and Mac OS hard link flag is not set (In theory, this selector would also exclude device files but they reside in /dev which is automatically excluded by the Mac OS X client anyway.) I hope this information is helpful to anyone else having this problem. - Gary Palter
  13. Any response to my previous post dated August 19th? For the record, I've also tried all the trouble shooting tips listed in Melissa's original reply. They make no difference; I still get the 104 error whenever I fill a tape. - Gary Palter
  14. [i'm just a long-time Retrospect user; I don't work for Dantz] I'm the one who first reported the problem with backing up a Mac OS X client with Retrospect 6.0. For the record, I received the following note from Retrospect back on the 14th of August: "We have logged a bug for this problem and our engineers will be investigating the cause of this error in more detail." I can easily believe that they're still working on the problem; I suspect it's not an easy one. For JamieG: You say that you've successfully backed up a OS X client. I'm curious. How many files are on the OS X volumes that were backed up? How many files were backed up? Have you used any disk utilities (e.g., Norton Disk Doctor, DiskWarrior) on the OS X volumes or used any optimization software (e.g., Norton Speed Disk). What kind of backup medium are you using? [i'm just looking for differences between your situation and ours that might explain your success.] - Gary Palter
  15. [i don't work for Dantz; I'm just a long time Retrospect user.] The hardware compatibility database says that the HP SureStore T20 isn't qualified for use with Retrospect on a Macintosh; it is qualified for Retrospect on Windows. - Gary Palter
×