Jump to content

rhwalker

Members
  • Content count

    5,089
  • Joined

  • Last visited

Everything posted by rhwalker

  1. The administrator of the Retrospect site seems to be asleep at the switch. The only [color:red]EULA[/color] currently available on the Retrospect web site is the Current Retrospect EULA on the Retrospect Documentation web page. That [color:red]EULA[/color] may be out of date because it is unchanged from before the sale of the Retrospect product by EMC to Roxio (Sonic Solutions). The value of a license from EMC, which may no longer have any ownership rights in and to the Retrospect product and its underlying software, is questionable. There is also a (very different) [color:red]EULA[/color] presented by the installer for Retrospect 8.2.0 (build 399) (see attached [color:red]EULA[/color] license file) that may supersede the one posted on the Retrospect Documentation web page. The original poster may want to consult an attorney knowledgeable in software copyright law and licensing for his/her jurisdiction, as appropriate for the conflicts of laws issues that are also in play, and may also want to seek advice regarding whether the "entire agreement" clause of either [color:red]EULA[/color] can be modified by oral statements made by a Customer Support representative. Russ
  2. T.J., You'd do better to get help for your question if you posted in the Retrospect 8 forum because you seem to be using some unknown version of Retrospect 8. This forum is for versions of Retrospect prior to Retrospect 8. From the forum description: Here is the link to the Retrospect 8 forum: Retrospect 8 for Macintosh When you repost, it would be useful to indicate the specific version of Retrospect 8 (8.x.x) that you are using as well as your environment (underlying Mac type, and Mac OS version). Just as a guess, are you indicating that the "restart" is the same media set as the interrupted task? What does the media set show as its contents? Are you sure that Retrospect is trying to start over? It does have to rescan the entire source first, and then do a matching phase against the media set. If you use the backup assistant, what does the Preview show is going to be backed up? Admittedly, the preview process is terrible in Retrospect 8. Needs much work. Just some thoughts for when you repost so that we can try to help. Russ
  3. rhwalker

    No access on rebuild data?

    Sorry, that's the Retrospect console that allows you to manage/control the Retrospect engine. That's why I wanted to see a screen shot. The program for which you provided a screen shot. It's the GUI for the Retrospect engine. The Retrospect engine is the program that does the real work; the console is just the GUI, and they chat over the network. I suggest you take a moment to read the documentation and understand the different components of the program and what each does. See, for example, page 5 of the Retrospect 8 What's New and Getting Started Guide While the program might better handle your situation where you have (different) local UIDs and GIDs for each machine, I think that you are stuck using your workaround until you establish a correct and consistent enterprise-wide permissions model (Open Directory, etc.). In your case, where you have a Windows machine in the mix, you would need to do the so-called "Magic Triangle" setup so that Windows machines (using Active Directory) and Macs (using Open Directory) see the same permissions model, UIDs, GIDs, etc. We don't see this and never have because all of our computers (server, LAN computers, etc.) run off of a common Open Directory server. Russ
  4. Because optical devices are not fully supported. From the Roxio Retrospect 8.2 Read Me: The code base is new and still quite immature. The new code base program has only been out for a couple of years. If the provided workaround is not acceptable, then wait until optical drives are fully supported. If you are having problems with your specific DVD drive, then you might want to get a supported DVD drive. Russ
  5. rhwalker

    Really Disappointed in 8.2 update

    While you don't explicitly say what type of media sets you have, it appears that you are not using tape media sets. That might account for the difference. Russ
  6. rhwalker

    No access on rebuild data?

    Ok. Sure you aren't talking about opening the Retrospect [color:red]console[/color] program rather than the Retrospect client program? Perhaps it would help if you attached a screen shot to confirm. You might have to do the magic dance here: Forum attachment rules change Note that the forum admin contact email given in that post is a couple of years old, and now is obsolete (after the sale of Retrospect to Roxio). To contact the forum admin, use the "Contact Forum Admin" entry in the "Help" button drop down in the navigation bar at the top of this forum's window. Ok, then I believe that explains your issue, and you are probably seeing the expected behavior. Explanation: Because you have not set up enterprise-wide UID/GID, they aren't going to be the same on each computer. Unix POSIX permissions are done on a UID/GID basis. Your restore is being done on the Retrospect "engine" computer. When Retrospect does the restore, it is supposed to restore the UID/GID metadata existing when it backed up the file(s) and folder(s). Retrospect engine is able to write anything it wants (with whatever permissions it wants) because it is running setuid root. I suspect that the restore to the Windows box is done in a manner (by permissions there) that give you access, but the restore to the Retrospect engine box doesn't give you the needed permissions (hence the "no right" (Keine Rechte) message). If the G5 is running Mac OS X Server 10.4.11, then there ARE ACLs in play. Again, it would be instructive to see the results of an "ls -aloe" listing of the problematic folder, as well as a "mdls" of the problematic folder. Russ
  7. Thanks for following up and letting us know. Retrospect has always had a problem that it expects the tape drive subsystem to work perfectly. Over time, the Retrospect classic (6.x and earlier) matured to the point that somewhat-useful diagnostic messages would be put in the log if a tape error occurred, so that those with detailed error manuals for the particular drive could figure out what the problem was. It's very hard to debug and test tape error routines - you have to be able to reproduce the error (some are transient) and then figure out how to handle it. Been there, done that in my youth, when I wrote some Unix tape driver routines as part of a 4.2BSD port. What fun. Good luck on getting the drive fixed. Russ
  8. rhwalker

    Express HD 2.5 is the current version

    Purchase a current version (or use a trial version) of Retrospect (non-Express). The backup format is the same. Alternatively, put the drive on an older computer whose OS is supported by your version of Retrospect Express. Russ
  9. I agree. The "favorites" (f/k/a/ "subvolume") feature probably was a result of Retrospect's extremely long scanning phase, and was easy to add using the unix "chroot" syscall. Adding an "exclude" folder designation would require writing real code in the scan path, which would, um, require work. And it could also produce unexpected results if, for example, a symlink or hard link introduced a path into the middle of that (excluded) filesystem branch. Perhaps the product managers and engineers to whom you have spoken, Dave, have never used Retrospect in a real production environment. Those of us who do use Retrospect in a real production environment have to deal with: (a) sections of a volume that cause Retrospect to barf due to bugs, and which need to be excluded as a workaround or during bug testing - this thread is a perfect example of such a need; and ( the slow volume scan that necessarily occurs with the current design, necessitating a full filesystem traversal with filters applied at the single-file level; such scanning time is wasted for filesystem branches that are read-only (documentation) or for which daily backup is not warranted due to the backup policy. This sure would be a very good feature to have. Russ
  10. rhwalker

    No access on rebuild data?

    Precisely which version and build? (8.x.x) Earlier builds / versions had many more bugs than the present version. Let's be sure that we aren't chasing problems that have been solved by updates. (1) exactly what do you mean by "When I rebuild data"? Exactly what steps are you performing to do this? (2) on which of the relevant computers (engine (server)? client?) is this "Get Info" box showing the access problems? Is it on a volume local to that computer, a network share, etc.? (3) Are your UIDs / GIDs handled system-wide by Open Directory, WGM, etc.? or are they instead done on a machine-by-machine basis with local UID / GID sets? (4) are ACLs possibly in play here, rather than POSIX permissions? could you provide a "ls -aloe" listing of the problematic folder, as well as a "mdls" of the problematic folder? Sorry, I can't read German, but I think I can figure out what the various fields are by comparison with the English Get Info box. Russ
  11. Well, we don't have LTO4 (probably will migrate to that when/if Retrospect 8 stabilizes/matures and becomes ready for production use in our environment). However, here's a possibly-related bug that you might want to use to inspire your investigations. An earlier release of Retrospect had a similar bug for VXA-3 tapes (physically identical to VXA-2, but recorded at twice the density). The first time that the tape is written, a small burst pattern header is written by the drive at BOT, depending on the drive's density setting, to signal that this tape is a VXA-3 tape. When a tape is inserted, the drive reads this header as it positions at BOT, and reports back the density of the tape. The tape density can't be changed once writing has commenced on the tape, but the tape can be erased and the tape density can be changed by that process. Out of the wrapper, for backwards compatibility, blank VXA tapes would appear to be VXA-2. Retrospect had a bug (perhaps now fixed) whereby, in a VXA-3 drive, it would always use those tapes as VXA-2 (so that half VXA-3 density would be seen). The workaround was to use the Exabyte/Tandberg command line diagnostics to erase the blank tape into VXA-3 density before it was used the first time. You may be seeing a similar thing with LTO-3 / LTO-4. Just a thought for you to investigate. Russ
  12. Yea, probably an engine barf is treated like a SIGTERM or SIGQUIT. See signal.h for details. Russ
  13. rhwalker

    Mounting an external drive

    Yea, but then there's that pesky problem that Retrospect 8 lacks scripting coordination, so you'd have to schedule the applescript to run a short time before you think the backup will start. And then there's the related (and more difficult) problem of unmounting when the backup is done, again made more difficult because there is no (easy) way to coordinate external scripting events with Retrospect, so no (easy) way to know when the backup is done. Of course, you can cobble up a hack to sleep for a while, then check the Mac OS process status (e.g., ps | grep) to see whether the Retrospect engine is still chugging along with a certain high CPU percentage, etc., repeat until action stops. It would be very nice if (when) some form of scripting capability returns, as in Retrospect 4 through 6. Still even more problematic is the volume name confusion that results if Retrospect doesn't mount the drive itself. Mounting a volume in the Finder (and running an Applescript has the same effect because it runs as some user, different from the detached Retrospect engine doing the mounting) can confuse Retrospect. This is a great cause of confusion to users in this forum, and probably needs to be given great thought by the developers so that a "real" solution can be designed (what a concept - software by design) that covers mountable local volumes consistently with mountable network shares. Russ
  14. Yep. Been there, done that, and it's probably the right design decision. As an aside, note that the physical EOT strip is not an "error", but is really a warning indicator that the driver better finish up transfers soon before the tape unwinds off the reel. When the physical EOT strip is detected, there is still a bunch of tape past that on the reel (amount is determined by the spec for the particular type of tape, and is related to how long a CPU is allowed to react to the physical EOT sensing, considering the tape speed, etc.), and the driver is supposed to finish the current set of blocks "real soon" and then put down two file marks (EOF), which signify the "logical" EOT, past which the tape driver should not attempt to read or write. Hitting physical EOT does NOT stop the transfer in progress - it simply sets a status bit that the driver checks when it gets the "transfer complete" interrupt for the current tape block being written. In the absence of other errors (read-after-write error, etc.), the last block written has been correctly and fully written, even though EOT has been passed. But the driver better not keep writing or grave disorder may result. Some tape applications, if they want to ensure that each tape contains a complete set of files and no partial files, may do a "Space Reverse File" to move back over the previous file mark that terminated the previous file, then "Space Forward File" to move past that same previous file mark, then write a second file mark to indicate logical EOT (two file marks in a row) after the previous complete file. That's a detail to be handled by the application. End of trivia. Many tape systems just give up on error and require operator action as to what should be done. The operator is supposed to monitor the console output that spews forth on the teletype. Perhaps you are too young to remember. Russ
  15. rhwalker

    Disappearing Exabyte drive

    Ok, makes sense now. Um, more accurately, if I understand your updated problem statement, the problem didn't exist in Retrospect 8.1.622 on a PPC G5 running Mac OS 10.5.x, but does exist in Retrospect 8.2.0 (399) on an Intel MacPro running Mac OS 10.6.4. I don't see any indication that testing has been done running Retrospect 8.1.622 on an Intel MacPro running Mac OS 10.6.4, or that testing has been done running Retrospect 8.2.0 (399) on a PPC G5 running Mac OS 10.5.x. That makes it a bit hard to identify which variable is the cause. As for leaping back to Retrospect 8.1, you'd really have to do an uninstall of 8.2 followed by an install of 8.1. I'd suggest saving away copies of your catalogs and the config80.dat file, too, so that you could go back to the current setup if things go horribly wrong, and you might have to rebuild your catalogs under 8.1 and you might have to recreate your scripts, etc., for 8.1, starting from a clean config80.dat file (unless you have a copy saved away from when you were running 8.1). Some people have reported odd behavior on an upgrade from 8.1 to 8.2 if the old config80.dat preferences file was carried forward (perhaps corrupted in 8.1?), so there's no reason to believe that similar issues wouldn't occur going backwards. From what I have seen, though, 8.2 is a big improvement over 8.1 (though still not without warts). Your disappearing tape drive is odd, and is the first time I have heard of this specific problem. A bit more testing might help narrow down which of the many variables in your case are responsible. We don't have the Firewire Exabyte drive (only the SCSI version, on an ATTO HBA), so I haven't seen your particular issue and can't test for it. You seem to be doing all things right, though. Again, more testing is needed to identify the culprit trigger for this bug. Russ
  16. Screen shots might help characterize the bug and provide useful info to the bug testers.
  17. Hmmmm. Then perhaps this is related to the bug whereby Retrospect barfs on single-character volume names? Volumes don't show up if single-character names I may have misread the original problem statement in haste - I didn't fully appreciate that these were Proactive scripts. Russ
  18. It wouldn't be possible. No, it just isn't possible with the current design. If you think about it, the media set / backup set / data set, whatever the current marketing speak name is - it keeps changing - is just a database, and the catalog is a database index into the database. It would be possible, but not with the current design, to just treat the members as a bit bucket, and use whatever is available, providing that the member capacity hasn't been reached. That would solve the many-years-running request for moving disks offsite. Left as an exercise for the programmers. Russ
  19. rhwalker

    "Unable to create folder" on Add Source

    Nope, but we don't have firewalls on our LAN - our border is quite well locked down, and access is tightly controlled. Now, there is an additional port involved, but not with adding clients. The Retrospect console (and the Retrospect iPhone app, which is a mini-console) chats with the Retrospect engine over port 22024: Retrospect console port There is, in fact, a little diagnostic written by one of the Retrospect programmers, that can check out the multicast / broadcast stuff independently of Retrospect: Multicast Ping You might want to check that out and capture some packets, etc. There's also another firewall lockdown level on Leopard and Snow Leopard, not only opening/blocking ports to the machine, but only allowing ports to be opened by certain applications. The Retrospect installer doesn't seem to handle this right in all cases, and this might be an issue in your case if you upgraded from 8.1 to 8.2, which also involved changing some file names and locations. It's possible that the firewall is only open to the old application. Some people work around this issue by blowing everything away and doing a clean install, which the installer seems to handle. I think that some effort needs to be made to make the installer more forgiving. Russ
  20. rhwalker

    Disappearing Exabyte drive

    Something's inconsistent between your signature block: and your statement of your Retrospect version: I'll ignore that for the moment and assume that you are on the "current" 8.2 build. Really? I take that to mean a VXA-1 drive, right? The firmware level doesn't match any of the VXA-2 or VXA-3 rev levels. That's a bit old. Did it have this problem with 8.1? It might be useful to try a regression test to Retrospect 8.1. Also, your G5 to MacPro involved two major changes (ignoring the PPC to Intel processor change): Did your G5 have FW 400? Or FW 800? And, you probably did a Mac OS jump, too, at the same time, right?
  21. rhwalker

    "Unable to create folder" on Add Source

    Nope. Additional [color:red]protocols[/color] (multicast, broadcast) are required to [color:red]see[/color] (i.e., discover) clients for adding them, but you can still add them manually by IP if you can't reach them by multicast / broadcast. Backup is done by ports 497 (udp and tcp) only. Search the Knowledge Base for details (search on multicast or broadcast, or client discovery). If you carefully re-read the thread, this was buried (well, hinted) in a post upthread. Russ
  22. rhwalker

    Scanning HD...wasted time

    This is by design, and is the expected behavior. Not to say that the current design is the "best" one, but it is what it is. An explanation why is beyond the scope of this reply. Steve Maser has provided the correct workaround. Russ
  23. rhwalker

    Disappearing Exabyte drive

    What interface? SCSI? Firewire? If SCSI, what HBA card? What firmware version for the HBA card? Any other devices on the same SCSI channel? If Firewire, any other devices on the Firewire chain? What firmware level for the Exabyte drive? Have you tried running the Exabyte diagnostics? Russ
  24. rhwalker

    XServe G4 Single Processor

    Retrospect 8.x System Requirements That's below the "minimum" requirements, which list Dual G4 as the minimum. However, you could download a trial version and give it a shot. I haven't tested this particular configuration myself, but I certainly wouldn't characterize the behavior of Retrospect 8.x on a PPC as "running" - more like crawling. You will not be happy. Russ
  25. rhwalker

    "Unable to create folder" on Add Source

    What Retrospect client version?
×