Jump to content


Popular Content

Showing content with the highest reputation since 12/24/2020 in all areas

  1. 1 point
    Then, tbh, you need a better system for archiving that data. Like with backups (and I draw a distinction between archive and backup), you should be thinking "3-2-1" -- 3 copies on 2 different media with 1 offsite and, importantly, you should be rotating your archives on to new media more often you have been. High-resilience disk-based storage is relatively cheap and you should use that for your "primary" archive copy. Don't forget to check application versions etc -- you may be near the point where you'll need to re-write old data to new formats... I wouldn't know -- and I'm not sure I'd trust anything over Retrospect for recovering RS's proprietary format (tar tapes would be a different matter). Best to avoid any problems with "3-2-1", media rotation, regular checks that you can retrieve files, and so on.
  2. 1 point
    Don't know about best, but what I'd try is: Rebuild to "tapeset1", starting with the first tape, expecting it to fail at the end of the tape as you've described Rebuild to "tapeset2", starting with the first tape, expecting it to fail... Take tape 1 out of the drive! Repair "tapeset2" and, when it says insert tape 1, mark tape 1 as missing and continue with tapes 2 and 3 You've now got the most data back that you can, albeit in two sets. You could then try and combine them by copying "tapeset1" to a new "diskset1", then "tapeset2" to that "diskset1" -- "diskset1" can then be moved to your newer machine for the conversion. Your choice as to whether "diskset1" is a File Set or Removable Media Set. You could, perhaps should, copy the two tape sets to two disk sets, convert them to the new format, then combine them -- it'll take longer but might be "safer". I'd also start to wonder about the chances of me ever needing to go back to data from 10+ years ago and whether it's worth all this extra work! That'd be a struggle between my innate laziness and my OCD, but you may have compliance issues to satisfy.
  3. 1 point
    oslomike, Was the Tape Backup Set that contains the "bad" tape originally written with the Exabyte drive? I'm guessing that this may be so if the Backup Set was created by v4 or v5; the timeline of Retrospect Mac releases at the bottom of this Retrospect History article versus the Wikipedia timeline for the release of AIT-2 seems to show that a Backup Set written up through 1999 couldn't have been written on your AIT-2 drive. Therefore, if you still have it lying around, I suggest you try re-reading the tapes in that Backup Set using your old Exabyte drive. I'm not an expert, but differences in mechanical skew between drives can make tapes written on one drive hard to read on another—especially for special characters such as end-of-tape markers. Let me tell you a tape story: In 1969 I was working as a programmer at ITT Data Services in Paramus NJ, and my boss asked me to write a program to read "gapless" tapes on the IBM S/360 DOS computer at our satellite Lakehurst office and copy them to ordinary "gapped" tapes. The "gapless" tapes were being written by the U.S. Navy's Lakehurst Naval Air Station (that's where the Hindenburg dirigible caught fire in 1937), using a tape drive attached to a radio-telemetry receiver that had no ability to store received data while an inter-block gap was being written. LNAS could read these "gapless" tapes using a Control Data minicomputer connected to a special tape drive that could somehow "stop in less than 2 inches and navigate backwards to before the stop", but the minicomputer had such a pitifully-small main memory (4K 12-bit words) that the LNAS engineers (testing top-secret aircraft; don't ask 🙄 ) couldn't do any real analysis on it. The engineers wanted ITT to copy such tapes onto "gapped" ones that could be read by an ordinary tape drive on one of ITT's 512KB OS/360 IBM mainframe computers in Paramus. I wrote a tricky copy program in S/360 DOS Assembler, and it worked successfully on a test tape. However it turned out that the LNAS tape drive attached to the radio-telemetry receiver had a skewed read-write head, and the Control Data minicomputer's tape drive read-write head had been skewed to match. ITT wasn't willing to skew one of its satellite-office IBM tape drives to match, so my program never got used in production. See an audio expert for an explanation of tape skew.
  4. 1 point
    oslomike, My gut feeling, from having worked extensively with tapes many years ago on IBM mainframes which didn't yet have disk drives, is that you've got an unreadable end-of-data marker on the first tape Member of the input Backup Set. The computer operators—a separate profession in those days—used to have a utility program that could write an end-of-tape marker on a tape, but AFAIK we don't have such a program now. (Some folks may: In 1992 I had backed up my wife's Mac using a Maynard QIC tape drive before I erased her HDD, and the Maynstream backup program—the ancestor of BE—couldn't read the tape to restore it. I paid DriveSavers US$600 to recover the data from the tape, which they did; it'd now cost around US$2000.) If you've got the data from that input tape on the output Backup Set, IMHO what you should do is to run another Transfer to the same output Backup Set using only the remaining tape Members of the input Backup Set—starting with the 2nd one. A way to do that would be to mark the first tape Member of the input Backup Set as Missing, per the NOTE under "The Members Tab" starting at the bottom of the left-hand column on page 155 of the Retrospect Mac 6 User's Guide.
  5. 1 point
    Just installed this update and tried the same Duplicate 'Replacing all contents' from the client to the Retro server machine. This time it works as it should.
  6. 1 point
    Prophoto, You are new here, and I don't think you will do very well with this comment. I'm a "home IT guy" with a Retrospect Desktop setup in use for over 10 years now. David is a prolific AND extremely helpful and knowledgeable contributor. I think you owe him a public apology. I can't express these thoughts strongly enough. Again, I think you owe him a public apology.