Jump to content

rhwalker

Members
  • Content count

    5,089
  • Joined

  • Last visited

Everything posted by rhwalker

  1. You should post in the Retrospect 8 forum. If you are using the Retrospect 8.2 beta, then post in that forum. If you are using the Retrospect 8.1 release, post in that forum. This is the Retrospect 6.x forum. Russ
  2. rhwalker

    Tape library stuck in endless loops

    If that's the case, then the UL4D/UL4S is not the right card. The right card would be the UL5D or the UL5D Low Profile (which most people use) because of the PCIe slots in the Intel xServe. Hopefully you figured that out before buying one. Russ
  3. rhwalker

    Tape library stuck in endless loops

    Does the drive pass diagnostics? You may have a bad drive / autoloader. Also, you haven't provided any configuration information (Intel? PPC? version of Mac OS X, etc.) Russ
  4. Here's what I would suggest: Your testing seems to have eliminated a RAID 1 data issue. You indicate that the pathname is simply "c:\data", but it isn't clear from that response whether you have a single directory with all of the files (hmmm.... perhaps there is some issue with the number of files in the directory, and that could correlate with why the problem just started recently) or whether there are subdirectories below that. My point about pathname length would only apply if there are lots of nested subdirectories below c:\data . You could duplicate that directory and then do a binary search (delete half the files, see if the remaining half can be backed up, etc.) to narrow down if it's a single file that has the problem. That would also test whether it's a "number of files in one directory" issue that Retrospect can't handle. For faster testing, you could define that duplicated directory as a Retrospect subvolume so that the entire volume doesn't have to be scanned. Test first that the error is seen when just having this directory as a subvolume. Another approach would be to use a trial license of Retrospect 7.7 to see if it's a bug fixed by that version. A caution, though: Once you use Retrospect 7.7 with a backup set, you can't go back to Retrospect 7.6. So, you will have to do your testing with a new backup set. Russ
  5. You may be under the misconception that these forums are the way to contact Retrospect support. They are not. From the Retrospect Forum Rules / Terms of Use: Now, admittedly, the "EMC" part needs updating after the recent sale, but we are just users like you are. If you want a response from Retrospect support, you need to contact them, and these forums aren't the way to do that. The updated contact information link is: http://www.retrospect.com/contactsupport Russ
  6. Ok, next thing to try would be to see if it's a pathname length issue. What happens if that directory is moved to a higher level. Can it be backed up then? If this works, you know it's a pathname length issue. Or perhaps it is an odd filename problem or some such. Have you tried to isolate a particular file or subdirectory that is causing the problem? I'm stumped. But using the approach above might help you find the problem so that you could submit a bug report and get it fixed. Russ
  7. Your question should not be about what version of the Retrospect client, but instead about what version of Retrospect. Retrospect 6.1.x is not supported for use with Snow Leopard (Mac OS 10.6.x). See the Retrospect Snow Leopard Compatibility Statement Yes. Well, there are MANY issues with the currently-released Retrospect 8.1 product. However, the Retrospect 8.2 Beta (currently, Beta 1) is quite good. The warning in the Retrospect 8.2 Beta Read Me about using Retrospect 8.2 on Mac OS 10.5.x (Leopard) is primarily if you are upgrading from Retrospect 8.1. Because you will be starting from scratch if you move to Retrospect 8.2 now, you shouldn't see those issues. However, you cannot import the scripts, settings, etc., from Retrospect 6.1, and the user interface is VERY different. It takes a brain transplant to get used to the new interface. If you have problems, post in the Retrospect 8.2 Beta forum, and we'll try to help. Be sure to read the Retrospect 8.2 Users Guide, the Getting Started Guide, and the Read Me for the Beta before starting. Right now, if you are using Retrospect 6.1.x, the biggest thing that you will miss is external scripting, which is not yet present in the Retrospect 8.1 release or 8.2 product. That presents problems when trying to back up an always-up server, but there are workarounds. Russ
  8. One item in the filesystem repair might be an issue: The interesting part about your problem report is that it "just recently started happening." So, Retrospect worked fine with this RAID 1 volume until recently. Did anything (hardware, software, drivers) change? It may be that the filesystem issue caused some mystery garbage block from space to drop on some critical structure, and Retrospect isn't able to do its filesystem traversal. Is it possible for you to boot from something else (perhaps a CD), copy this particular folder off somewhere (to another drive), delete the folder, and then copy it back? That should eliminate any filesystem issues. Russ
  9. RAID 1 (mirror) configurations are very hard to troubleshoot when there are problems. One of the drives could have bad sectors and the other might not. Most RAID drivers, on read requests, will return the first data to come from either drive, so it's possible a bad sector on one drive might not always cause an error, which will only be reported when both sectors error out. Many RAID drivers will try to recover a bad sector on one member by rewriting or even remapping the sector. Errors can be further masked by the automatic sector remapping that some drives do when soft errors start occurring. The only way to check for bad sectors on a RAID 1 volume is to split the mirror, check each drive individually, then pick which drive is to be the RAID primary, and re-establish the mirror and allow the mirror to rebuild. Russ
  10. rhwalker

    Moving Config Files

    Yep. A possible "gotcha" is that I don't know which of the two places Retrospect looks first for its config files. You might have to install and then move the config files to the other location. I've never run with the config files in the non-default location myself. Russ
  11. It's still a bit unclear to me just which Exabyte product you have. It's complicated a bit by Exabyte (Tandberg) marketing changing the names of everything every so often. I'm not aware of a VXA-2a. Here is the specs page for what I believe you have: VXA-2 StorageLoader specifications I think that you have the model 119.11500 (now called the Tandberg StorageLoader VXA-2 Firewire). We have the model 119.00510 (now called the Tandberg StorageLoader VXA-2 Plus), which is the same drive and autoloader, SCSI interface, and ethernet admin interface. Could you try the experiment without the FireWire extender? There may be some timing issue. I can assure you, at least with the SCSI version of this drive, if Apple System Profiler (and also the ATTO SCSI HBA Config program) does not see the drive in the System Profile, then Retrospect won't be able to see it. I thought that the same was true for the Firewire version. Russ
  12. rhwalker

    Moving Config Files

    Yes. See the section entitled "Moving Retrospect" in the index of the Users Guide. While that section is intended for moving Retrospect to a new computer, I believe that you can figure it out from that. See also page 273 of the Retrospect 7.5/7.6 User's Guide: Retrospect 7.5 / 7.6 User's Guide there are two places that Retrospect looks for the Config75.dat (and .bak) file: either the default location (where yours probably is) or in the same directory as the Retrospect application. See the User's Guide for details. Those are the choices. If your Retrospect application is installed on the drive that is having space issues, I'd suggest swapping in a bigger drive. Russ
  13. rhwalker

    ATTO SCSI not mounting Quantum drive

    Sounds like you've got a bad drive that has hardware problems. If the drive doesn't show up in Apple System Profiler and the ATTO Config Tool, there is no hope for Retrospect to be able to talk to it. I would RMA the drive. Russ
  14. If you can't see the Exabyte VXA autoloader in System Profiler, then there is no hope for Retrospect to see it. Sure you have a good Firewire port? They blow out rather easily. Anything else on that Firewire chain? Retrospect really likes to have tape drives on their own chain (at least that is the way it is for SCSI). Retrospect 6.x does something during its initial device scan that causes the bus to reset, which causes dropped transfer complete interrupts for disk drives, and can hang the system. But that's for SCSI, and you aren't getting that far. I still don't have a clue as to what Exabyte drive you have. Russ
  15. You might want to post some screen shots. For details about the magic dance you need to do first so that you can post screen shots, see: Forum Attachment Rules Change
  16. rhwalker

    Missing catalog error

    You guessed correctly. Correct. The media set (f/k/a/ backup set, and f/k/a/ data set) is simply Retrospect's database into which it dumps files and metadata, etc., and the catalog is Retrospect's index into its database so that it can find things quickly. Nope. But certainly at great expense of time. It may take a week or more, depending on the number of members in your media set (and how closely they are coupled - bandwidth wise - to the engine) to rebuild a catalog. That's one (but not the only) reason to limit the number of members in a media set. When you are in the crisis of trying to get back online quickly after a crash, it's no fun to spend days rebuilding the catalog before you can begin doing the restore. Moral: back up your catalogs. It all depends on your backup policy, and what your priorities are. I don't think I have ever heard of someone using that approach. Localized media sets at a central server would seem to make for better management. The usual use for multiple servers is either to: (a) spread the load when a single server can't back up all clients in the allotted backup window; or ( to compartmentalize sensitive data. Russ
  17. rhwalker

    Server Stopping/Crashing(?)

    Well, you've got several choices. (1) Perhaps the preferences files (config80.dat and config80.bak) are corrupted. If you've saved away copies of these from when it worked, you could stop the engine, replace those, try. (2) If you don't have saved copies but have backed them up using Retrospect, you could stop the engine, move the suspect bad files somewhere away where Retrospect engine won't find them, start the engine (will have to re-enter license info and minimal config stuff), then use the engine to restore copies from your backups from when it worked. (3) If you didn't back them up, then you will have to use step (2), above, and re-enter all of your configuration - scripts, etc. (4) Or, you could try the Retrospect 8.2 beta, which has many, many bugs fixed. See the beta forum. Study the Read Me carefully. Russ
  18. Depends on which Exabyte drive you have (VXA-2 or VXA-160 or VXA-320, etc.). Sounds like you didn't install a Retrospect Driver Update ("RDU"). The installed RDU version will be announced in the Retrospect log each time Retrospect launches. But Retrospect 6.1.15.101 or 6.1.16.100 should do it. Here is the Retrospect Driver Update Version History: RDU Version History Here's a link to Retrospect 6.1 RDU 6.1.16.100: RDU 6.1.16.100 and install instructions Russ
  19. rhwalker

    Server Stopping/Crashing(?)

    Could you explain a little more about your configuration? You don't install the Retrospect client on the same machine as the Retrospect engine. Surprised it would crash, but that's not the architecture, if I understand you correctly. There are three parts to the Retrospect 8 suite: (1) Retrospect engine, which does the real work (2) Retrospect console (or the mini-console iPhone app), which chats with the Retrospect engine and is simply a GUI to control the engine and display status, etc. The console may be installed on the same machine as the Retrospect engine, or may be on a different machine, even one on a different continent. (3) Retrospect client - installed on other computers on the LAN, chats with Retrospect engine to supply files from the client to the engine for backup, and to receive files from the engine for restore onto the client. Retrospect client is never installed on the same computer as Retrospect engine. Please explain a bit more about your configuration. Russ
  20. Note that this requires the filesystems on the two volumes to be of the same type (but not necessarily of the same size) so that the metadata can match. If the filesystems are different, then the time granularity may not be the same, the permissions models on the two filesystems may not be the same, etc. Russ
  21. rhwalker

    Retrospect sold to Roxio...

    Retrospect 6.1 on Tiger for production use. Retrospect 8.1 is not ready for production use, at least at our firm. I have an isolated testbed set up for 8.x testing. When Retrospect 8 becomes reliable, we will upgrade all of our computers, but not until then. Russ
  22. rhwalker

    a little advice? backup strategy

    Works fine for me using Firefox (3.6.3). Interestingly, the link seems to break in Safari (4.1). I supplied it as a "TinyURL" because the actual link is long and a bit odd. Here's a link that works in Safari, but that doesn't display right in these forums if the actual link is used: http://iwiring.net/#[[What%20Should%20a%20Good%20Backup%20Policy%20Address?]] Retrospect has always been able to do that, and still can. Just make a disk media set, add the disks as members. However, because you seem to want to preserve version history by doing incremenetals, you will have to let Retrospect use its proprietary format. Regardless of what the currently-favored name is for the data set / backup set / media set, it's simply Retrospect's database, and the catalog is the index into the database. Just as all software version control software uses a database (proprietary for each software package, RCS, SCCS, etc.), so does Retrospect. Russ
  23. rhwalker

    Retrospect sold to Roxio...

    You seem to have competing and inconsistent metrics. (1) you want it reliable, and (2) you want it now. Pick one. I vote for reliable. Russ
  24. rhwalker

    a little advice? backup strategy

    May I suggest, before you start fooling with details like these, that you first forumulate a backup policy? Here's a pretty good list of the issues to consider: What Should a Good Backup Policy Address? Just as a comment, if you think about it for just a minute, it is necessary for Retrospect to store its backup data in a "proprietary format" in order to correctly preserve metadata for the variety of supported client platforms, and also to preserve revision history. However, Retrospect can (and always has been able to) store data in a "non-proprietary format" if you are willing to give up revision history and metadata preservation. In older versions it was called "duplicate", in Retrospect 8 it is called "copy". Regardless of what you call it, that's not a "backup", which preserves revision history and metadata. What you seem to want is a "sync" methodology, and there are better tools than Retrospect for that. Retrospect's strength is in backup and preservation of revision history, with ease of restore to a point in time. Russ
  25. rhwalker

    Retrospect sold to Roxio...

    Seems to me like the release is still on track: Retrospect tweet of June 1 - one or two more weeks I'd rather the beta release be solid, well-tested, and with documentation so that the beta testers won't be wasting their time shaking out those last few issues before full release. I don't know about you, but it's a pretty big investment of my time to shake out a release before production deployment. While we are a very tiny outfit, our data has great value. I, for one, am very pleased and encouraged to see that this release seems to be done right with proper procedures. It's not trivial to make a release like this, in multiple languages, with documentation, for such a complex product, complicated by a sale of the company right before the release. I'm sure that it takes time to revise the T-shirts, too... Russ
×