Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About rhwalker

  • Rank
    Lifetime Achievement Award
  1. Well, being just a user I have no more insight into the future than you do, but this thread might provide some glimpse of the timeline that you seek: Glimpse of timeline for Exchange 2010 support Russ
  2. Script Schedule

    Nope. Here's this forum's description: The Retrospect 8 forum link is here: Retrospect 8 for Macintosh I suggest, when you repost in the Retrospect 8 forum, that you include a screen shot so that we can take a look at how the scheduling is being done. Russ
  3. Engine Crashing...again

    Very insightful, Steve. The software needs to be robust enough (defensive programming) to handle bad media sets / bad catalogs. If I were on the Retrospect team, I would be trying to capture some of these bad catalogs / bad media sets so that the software weaknesses could be repaired. As long as we spend hours each month trashing media sets, rebuilding catalogs, re-creating preferences, without having these issues addressed, the problem will never get fixed. Russ
  4. Engine Crashing...again

    Sadly, no. Many of us are just as perplexed as to the cause of the config file corruption. If it was an easy problem to solve, I believe that the programmer(s) would have solved it already. Remember, the 8.x code branch is new code, quite immature. We (and our data) are the guinea pigs. Sigh. Russ
  5. Engine Crashing...again

    Ok, then you've narrowed it down to some bug that causes your config files to become corrupt, which causes the engine to crash. You've got so many variables in play here that I suggest you start narrowing things down with, say, a single client backup, to see if you can get a reproducible test case. I also suggest that you make periodic copies (whether finder copies, or Retrospect copy) of the config files so that you can restore them from when they were good and get back up and running quickly until the problem can be isolated. The program is known to be buggy and known to corrupt its config files. When that happens, the engine crashes. That's life in the Retrospect world right now. Russ
  6. Engine Crashing...again

    Well, for a start, you could provide version numbers. Mac OS version (10.x.x) on each computer in play. Exact Retrospect version on each computer in play (8.2.x engine, 8.2.x console, x.x.x client). It's unclear whether you are backing up the "6 servers" by mounting their volumes on the Retrospect engine machine, or whether you are running Retrospect client on those "6 servers". It's unclear what the OS are on those "6 servers" (windows? version? linux flavor? version?). Is there any information in the logs? Any crash reports? Is the Retrospect console on the same machine as Retrospect engine? The program is very buggy. Let's at least get some basic information from you. Russ
  7. Media versus thorough verification

    Again, an incorrect assumption. You assume that the code in /sbin/md5 is the same as used by Retrospect. The algorithm may (should) be the same, but the implementation may not be as fast in Retrospect. Russ
  8. You first need to understand the Retrospect paradigm. The backup set (Retrospect 6.x term) (Retrospect 8 terminology is "media set") is a database, and holds all of the backup information. The catalog is a database index into the backup set (media set). There are no files in the catalog - again, it's a database index. To get files out of the backup set (media set), you restore. To do this in Retrospect 6, from the initial "Retrospect Directory" screen, click the "Immediate" tab, then click the Restore button, choose a snapshot (or add a snapshot - i.e., have the catalog updated to include a database index for earlier sessions), choose files to restore, choose a destination, and let it fly. Russ
  9. First, you haven't indicated what version (x.x.x) of Retrospect you are running now. If you are running some version of Retrospect 8, you will need at least 8.2.x in order to retrieve from older tapes. Second, you haven't provided any information regarding how many years ago the tapes were made, or what version of Retrospect made them. If you are trying to retrieve from tapes made by Retrospect prior to Retrospect 6, you are out of luck. You will need to run Retrospect 6, convert the backup sets to Retrospect 6, then run Retrospect 8, convert the backup sets to Retrospect 8 media sets. I suggest that you read the Roxio Retrospect 8.2 Read Me, paying attention to the section entitled "Restoring from Retrospect 6.x Backups". Russ
  10. Client now showing volumes

    Does it even respect hostname other then for the initial lookup? Everything seems to show IP addresses (Engines and Clients) after they're added. I'll bet if you change the address of a machine and also change it's A Records, Retrospect won't find it. What an interesting insight. That might explain why those of us with "static map" DHCP configurations aren't seeing these issues, but those with true dynamic DHCP IP assignment are. Clients added by name should always be looked up by name, not merely on the initial client add step. Yes, perhaps that's for another thread. Russ
  11. Agreed. I'm in the same boat. Agreed. It's a bug. One of many. Perhaps someday some of the outstanding bugs will be fixed. I suggest that you file an incident report to make sure that this gets on the list and prioritized. These forums are user-to-user support. The official bug reporting page is here: File a support request Russ
  12. You don't say what version of Retrospect 8.1 you have (8.1.xxx). Many (but not all) bugs have been fixed. The Release Notes bugfix list is here: Retrospect 8.x Release Notes / bugfix list You are also aware that the Retrospect 8.2.399 update was released about 3.5 months ago, aren't you? Link is here: Retrospect updates Perhaps this is one of the bugs that have been fixed. No point in chasing fixed bugs. You might want to update and then report results. Russ
  13. Retrospect 8 and threads

    Realize that multiple threads will block if competing for the same resources. Hint: Do you have all backing up into the same media set? You might want to split things up. Russ
  14. Consider the case of a terabyte of historical files brought forward from MacOS 7, 8, 9 and ASIP 4.x into MacOS 10.x, with historical backups from Retrospect 2.0, 4.x, 6.x, etc. I've got that existence proof with such oddly-named files. No, a script can't do a search and replace for legal reasons - the files have to retain their names. Agreed, it's a dilemma. Russ
  15. You are aware that these forums are user-to-user support, aren't you? That's explained in the Forum Rules. I don't use the "Express" version of Retrospect, so I'm not able to offer any suggestions on your problem. Russ