Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. DavidHertzberg

    Wish to Change Destination Media

    Ultrachanel, In the traditional IT phrase, "RTFM". Since you've an allergy to stating what version of Retrospect Windows you are using, I'll refer to the Retrospect Windows 16 User's Guide. Read as much of pages 372–387, which is easily findable as "Managing Backup Sets" in the Table of Contents, as you need. After creating your new Backup Set(s), change your scripts—for which starting on page 390 would be good mental exercise. Here's where to find User's Guides from previous releases.
  3. Ultrachanel

    Wish to Change Destination Media

    I have been backing up to removable hard drives for several years, the type that fit in a cradle on a tower style computer box. I now wish to use 2TB WD External USB HDD's which will be easier to transport home each day. Can someone please let me know how best to proceed with this. I would appreciate any help. Michael
  4. Yesterday
  5. oslomike and Nigel Smith, Let's get our terminology in sync with Retrospect's terminology, which is mostly 30 years old and wasn't adopted by the rest of the IT industry. I'll refer to the Retrospect Mac 13 User's Guide, which is—fortunately for this thread—the last Mac version before the august Documentation Committee started refusing to copy the contents of "What's New" chapters into other chapters of the UG and (later) restricting the "What's New" chapter to marketing drivel: Page 144 says about "archive" That concurs with your use of "archive", except that Retrospect has a particular type of script named Archive—described from the rest of page 144 to the top of page 146. An Archive script does what the quoted paragraph says, but as a version of a Backup script with some enhancements and some limitations. One of the enhancements is an option to delete from the Source ("move" in the quote) the data that has been backed up to the Destination. Page 15 shows the latest version of the "Grooming" dialog for Retrospect Mac. Pages 221-223 describe Grooming of a Disk Media Set, but it has not been updated to include the Months to keep specification shown in the dialog on page 15 —an enhancement that was added in Retrospect Mac 12. Pages 163–164 tell how to create a Groom script. What Nigel Smith calls a "filter" is called a "custom Rule" in Retrospect Mac; it used to be called a "custom Selector" before Retrospect Mac 8, and is still called one in Retrospect Windows—despite its having the capability of excluding files (which is why Retrospect Mac 8 renamed it a Rule). Creating one is described under "Adding or Editing Rules" on pages 195–199; using them—as well as "built-in Rules"—is described on pages 193–195.
  6. Last week
  7. Nigel, SAN is for live data for the most part. We tend to keep projects that are up to 18 months old because clients in the music industry have a tendency to need the material to make something new from it; long story. So, I this is what I'm thinking would be good for me. 1. Archive the entire SAN to LTO; happens nightly and is rotated with three media sets throughout the week. (Archive is taken care of) 2. With a NAS or internal drives in the MacPro, 12 T of disk storage to keep 18 months of backup, with the use of a filter in RS, and writing the data to Disk sets. (backup taken care of) 3. Groom disk sets so that any project or file that's older than 18 months gets groomed off the disk media sets. Am I understanding this correctly? The great thing for me about RS, is that it does it's thing and I ONLY have to make sure the correct LTO tape is in the drive. It's pretty much set it and forget it. I'm hopefully what I described above can also be set and forget for the most part.
  8. Hi Nigel! Once again, thanks! I'll try and have a look at the 13.5 version over the weekend. I did try to rebuild a v6.1 File set using RS 17 but it came out the same as 10.5. I'm hoping that 13.5 will be magic. OR, can you think of some simple setting somewhere that might affect the rebuilds that I'm doing? Maybe even the way my File Sets were created in v6.1?
  9. RS can do that, just by using filters on what is backed up. Grooming is the step after that where you then remove things from your backup set so it doesn't keep growing and growing. Personally I've never used grooming and, instead, start new backup sets every year -- I do that from scratch with a new full backup of every client, but you could do it by transferring the last backups from "Old Set" to "New Set" and continuing with incrementals to "New Set". The previous year's backups are "archived" by putting the tapes into secure storage. No, I mean automated scheduled checks of your NAS/SAN's integrity -- eg parity checking. Your SAN can probably do that, but if you just had a bunch of external drives you'd have to do it yourself (or rely on SMART warnings, by which time it might be too late). If it was me, I'd keep the SAN only for "live" data -- a good, performant, SAN is an expensive way of storing old data that you only need occasional (if any) access to. I'd get a slower, cheaper, NAS and move that old data to there from the SAN -- that NAS would now be my archive. How/when that happened would be a "business rules" decision -- for example, if you worked by project you might archive the whole project when the final invoice was issued (on the theory that work stops at that point so the data is "fixed"), or if work was less structured you might archive anything that hasn't been accessed in the last 12 months. Or you may not bother at all -- it may be better to pay for extra SAN storage than to waste your (chargeable!) time on such things 😉 There are many ways to skin this particular cat, so start with what you want to achieve, figure out the resources available to you, and go from there.
  10. You'll find all older versions here. Licensing may be an issue -- if you have a license for a newer version, and that key doesn't work with the old, you could try asking Support for a downgrade license. But if you've got a newer version, why not use that for the rebuild instead and see if that transfers the snapshots?
  11. Hi Nigel, Thanks for doing that test. I tried your suggestion where I attempt a Restore and then select More Backups, but the results are always empty. The RS console shows me the rebuilt Media set has over 300 backups in it, but the program will now show me any of them. Strange. Maybe it's actually better in later versions of the program? I couldn't find a MacOS v13 of the app that you mentioned. Are you using a PC? Could that be the difference? I would rarely need to get to the older snapshots, but once in a while, it can be a real lifesaver.
  12. Hi Nigel, I see that I didn't really understand the difference between backup and archive. It seems a lot clearer now. In my case, an archive has been the priority. I have three media sets that are rotated three times a week. What I'm discovering is that we could probably benefit from having a RS Disk Media set that backups everything on the SAN RAID that's less than 18/24 months old. I guess this is something RS can do, yes? Is that what you mean by scrubbing? Is that also what Retrospect calls grooming? I'll look into it. As far as if I REALLY need to keep old archives and every snapshot. I would need it only very seldom, but when I do need it it's a life saver. I will probably end up making v6.1 File Sets of all my old v4-v6 Media sets just so I can get the data off the old tapes that are getting increasingly problematic, and then back up all of those File Sets to the RS v17 on the LTO tapes. I don't really enjoy the IT hat I have to wear, but I'm getting better at it, especially thanks to people like yourself and others who have been very generous with what they know. I'm very grateful. Thanks
  13. Exactly the same (I deliberately created them with separate catalog files, to match your situation). The v6 catalog file will be ignored -- this is a "rebuild", which starts from scratch and reconstructs the backup using only the data file, rather than a "repair". Try the alternate route -- attempt a "Restore" operation on the v10 set and use the "More Backups..." button to see if they are shown. Or, simply give up 😉 Do you really need to do a "point in time" restore of a whole volume from x years ago? If not, you can likely do what you'll need by simply using filters on the whole set -- eg "all files and sub-folders in the Important Project folder last modified in 2010" then manually selecting what to restore from the results.
  14. Sorry, I didn't make my point very well (or, indeed, at all!). We often use "backup" and "archive" interchangeably, but you may find it helpful to consider them as two different things -- "backup" for recovery (disk failure, wrongly deleted files, reverting to a previous version), "archive" for long-term storage of data you want to keep. In many ways this is a false dichotomy -- you may need to keep your backups long-term (eg compliance) and you can restore files from your archive -- but it can help from a management POV to keep the two separate. Of course, being a belt-and-braces type guy, I'd then archive my backups and make sure my archive was backed up 🙂 More copies are good! It's really a data management/business rules thing. It helps us because we tend to work on projects (or by person) so when the project is finished (or the person leaves) all associated data can be archived, keeping it in a single place while also freeing up resources on the "live" systems. YMMV. It doesn't really matter whether you use DAS, NAS, a bunch of drives in a cupboard that you plug in when needed -- whatever works for you! NAS is more expensive per TB than comparable DAS because you are paying for the computer that "runs" it as well as the storage, but because it is a complete "system" you can take advantage of in-built scheduled disk-scrubbing etc rather than having to roll your own health checks on DAS. But if your RAID is a SAN it probably has those already -- in many ways, a NAS is just a poor man's SAN 😉 But the best system is the one that works for you. Managing data is a necessity but, after a certain point, can cost more than it's worth to your business. Only you know where that point is and how best to get there.
  15. No magic -- just LaunchDaemon doing its thing. From the Engine's plist: <key>KeepAlive</key> <true/> So if you want to force-quit the RS Engine you'll have to unload the LaunchDaemon plist first. Untried, but sudo launchctl unload /Library/LaunchDaemons/com.retrospect.retroengine.plist ...in Terminal will probably (I'm looking at v13) do the trick.
  16. Our RAID is a SAN setup via iSCSI, I've never used a NAS.
  17. Nigel, You're correct about my old backups, I wasn't very smart in the early days; I'm only a little smarter now. 🙂 I do have triplicate Media sets on all my LTO-5 Sets and the live shared storage we use daily is a spread across several RAID 5 volumes. I should probably have a better system for maintaining and grooming some sort of mirror backup that can automatically groom the hard disks after 18 months time. Would a NAS be good for this?
  18. Hi Nigel, You got me thinking. Are you native 6.1 Files Sets showing up in the Retrospect app as a Folder, or a single file. My File Sets that I transferred from tapes show up as a Folder in Retrospect and that's probably because the File set consists of two files, a catalog file and then all the data in another file. On my 10.5 system, when I rebuild a 6.1 File Set, I'm only able to rebuild by selecting the Data file; the catalog file seems to be ignored. I just wondered if you experience the same?
  19. Hi Twickland! I tried everything, including Force Quit from the Activity Monitor app. It magically restarts itself in seconds. It's alive! 🙂
  20. Sometimes the engine gets stuck in some mode where it needs a force quit. It's probably easiest to do this in Activity Monitor.
  21. After rebuilding the v6.1 media set using RS 10.5, the catalog shows that there's 335 backups in the media set. Is there a trick to accessing them? They don't show up on Backups Tab nor can I "retrieve" any. Looks as if there's 335 backups somewhere.
  22. David, Thanks for the history lesson! I find it interesting. I suspect there's some bugs several places. In fact, after just now creating a new LTO media set using RS 6.1 (transferred a file set to a tape media set: LTO-5), and then rebuilding that same media set (reading the LTO-5 tape) using RS 10.5, alas there's no snapshots in the new 10.5 catalog. I'm almost completely sure that the snapshots are they're there on the LTO tape because RS 6.1 shows me all of them when attempting a restore. Is it possible that the snapshots didn't get written to the LTO tape by RS 6.1? Some setting I might have overlooked? I hope I didn't explain that too poorly. Well, I'm starting to give up on the idea of consolidating everything to LTO tapes running on one machine. Just doesn't seem doable. It is a big plus to have the data on LTO tapes, even if it's still running on v6.1; it consolidates so many 8mm tapes and it's so much faster. I truly thought this was going to end up different. Maybe it's pilot error, could very well be. I'll keep trying. Thanks for everyone's help, it's much appreciated.
  23. oslomike, Based on announcements made at the time of its 2019 acquisition by StorCentric, Retrospect Inc. had about 20 employees—with most working from home. It has never in its 30-year history had any hardware-related capability. In fact before Dantz Development Corp. was acquired by EMC in 2004, Dantz used to get driver source code from the manufacturers of various kinds of tape drives—and hire contractors to rewrite that code so it would interface with Retrospect Mac and Windows. That's how Retrospect at the time of its acquisition by EMC had cornered 90% of the market for Mac backup software, and more Windows users than Mac users. (EMC end-of-lifed Retrospect Mac after disk-destination Time Machine was released.) Sometimes the manufacturer's driver code would have bugs, and sometimes the contractors would introduce bugs—which is probably why Retrospect Mac 6.1 can't use the hardware compression capability of my HP DAT72 tape drive. A lot of Retrospect's terrible reputation among IT old-timers, which they've expressed to me in my 4-year-old Retrospect thread on the Ars Technica Mac forum, results from the defects of its tape drivers—note that the linked-to post says another Windows 2000 app's AIT driver worked better. It sounds as if there might be a bug in the Retrospect Mac 10.5 AIT driver code, although it might use an AIT driver provided by Apple in later versions of Mac OS X. Your idea of copying your AIT Tape Backup Set to an LTO tape using Retrospect Mac 6.1 is excellent, because LTO is an industry-standard tape format with less flexibility for drive manufacturers.
  24. Does Retrospect have a division of the company that can recover tapes? I'll have to look into that. Thanks for the tip David. Regarding the original problem with the one bad tape, I have a little more info I wish to share. Originally, I was trying to rebuild a catalog with v10.5 of retrospect, which can read v6 media sets. RS 10.5 can indeed read this tape, which is a 6.x media set, but I got that pesky error at the end of the first tape. So, I tried rebuilding that same tape set with the earlier v6.1 Retrospect and alas, it reads the tape just fine, no errors. Go figure. So, in light of that, I managed to get the PCI card to connect my LTO to the v6 machine and I'm just now trying out a transfer/copy of some File sets to a new LTO tape media set. I will then try to rebuild that LTO tape with RS v10.5 and see if the new catalog also contains all of the snapshots. I'll let you know how it goes
  25. oslomike, I, too, don't have any knowledge of "inexpensive data recovery companies in the UK that specialise in tape recovery". However you could easily get a quotation from this company, by clicking the "Get a quotation" button on the web page and filling in the details—which include an explanation of your problem. That page sounds as if they might have special software that can copy your one particular AIT tape that has a problem and put a proper end-of-file marker on the copy—regardless of Retrospect's proprietary format, assuming the EOF marker is what you want to know about.
  26. 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.
  27. Earlier
  28. Hi Nigel! Thanks for your insight on what you think is best. It does seem like a good way to go. As you said, It'll probably take longer to get them combined but I think I''ll try that. It's worth a try. You mentioned if it's worth to keep old archives, in my case, the data from 10 year back in time are all multitrack music productions I've worked on, and I'm being surprised all the time by people asking if I can make a new version of a song for a film or something similar. Lucky them I have the archives, though it's not my responsibility. BTW, are there any inexpensive data recovery companies in the UK that specialise in tape recovery? I'm just wondering in case I ever need to get data off a tape that has problems. We have one here in Norway, but it's expensive.
  29. 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.
  1. Load more activity