Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by DavidHertzberg

  1. Joriz, Veeam won't back up directly to tape; you have to do a tape backup of the output of Veeam disk backup jobs. Since each of those jobs creates lots of small files in a Veeam repository, when you use Retrospect to back up a repository directly to tape you are writing to the tape inefficiently. Therefore you should be using disk-to-disk-to-tape, as Lennart_T and Nigel Smith suggested. If you ever used BE (you named the product in your OP, but I don't want to upset the head of Retrospect Technical Support by naming it again) to backup to tape, I think you were actually using disk-to-disk-to-tape. BE makes it extremely easy to set up a D2D2T operation with templates.
  2. Joriz, Nigel Smith is correct about self-cleaning of LTO drives. (I recently re-started backing up my old G4 Digital Audio Mac to a DAT drive after 4 years, because Retrospect Mac 16 eliminated the ability to back up PowerPC "clients" over the LAN, but DAT isn't self-cleaning—so I let Retrospect Mac 6 remind me to use a cleaning cartridge.) Every Saturday morning I do a Recycle backup of two sources, one an HDD and one an SSD, that are internal to my 2010 "cheesegrater" Mac Pro "backup server"—a somewhat-faster version of your 2008 Mac Pro. They both back up (copying phase) at around 2.2MB/minute. That's the almost the same disk-to-disk speed as with AFP shares as sources, per the fourth paragraph of this 2010 post. Because I started using Retrospect in 1995 to back up to a rather-unreliable tape drive, and because the Saturday script also does a LAN backup of a MacBook Pro "client", out of excessive (because my destinations are now portable USB HDDs) caution I continue to let my Recycle script's Options->Backup default to Thorough Verification. For internally-attached drives that means byte-by-byte comparison, which takes just about as long as the copying phase. Although pages 97-98 of the Retrospect Mac 16 User's Guide don't say so, I believe that drives that are connected to the "backup server" via SMB are treated as if they were internal (this section of an ancient Knowledge Base article seems to imply that by saying "If you back up a mounted AFP volume using the method listed above, privileges are not preserved and can not be restored. The only way to back up and restore privileges from a volume over a network is to back up the computer using Retrospect Client Software.") . You may want to live a bit dangerously and change your Options->Backup to Media Verification, or even—because your tape drive is LTO with built-in verify-after-write—to No Verification. Either of those changes—if you haven't made them already— should speed up your Backup script's total execution time by shortening/eliminating the verification phase.
  3. Joriz. First I suggest you read this April 2019 thread—the whole thread all the way through the final post. The OP in that thread discovered that he was backing up a lot more data than he thought he was. He also found the data was mostly pre-compressed, so that what really mattered was the native capacity and speed. Second, the OP in that thread also found that the tape library was never cleaning its heads—so he was getting un-recoverable errors after only a fraction of a particular tape was used. Your "backup server" machine is quite old; are you sure whoever was responsible for it before didn't just cable-up a new tape library without finding out how to set up head cleaning? That's one reason why Nigel Smith asked the make/model question. See pages 50-52 of the Retrospect Mac 16 User's Guide for instructions on how to set up cleaning for libraries and drives. Third, you write "a manual file transfer of the same source is utilizing the 1Gbit network card". That sounds as if there might be more than one network card on either your "backup server" and/or your SMB-attached source machine—which brings up another set of questions. After you've looked into those questions, I would suggest you phone U. S. Retrospect Technical Support at (925) 476-1030; the people on these Forums are just volunteers like me‬. If your organization installed Retrospect Mac 16 within the past 30-45 days, you are entitled to free personalized support. Because it sounds as if your native language is not English, and because you posted so early in the morning even compared to New York time, it seems that you may be located in Europe. I've heard that European Retrospect Tech Support is handled by a contractor, whose personnel don't know that much about Retrospect (probably especially about Retrospect Mac). May I suggest you put your Location in your Forums profile?
  4. DavidHertzberg

    Can scheduled operations be done without retrorun

    NoelC, Although I am a Mac user, I think you fail to recognize how much more Windows knowledge you have than the average backup administrator, as DovidBenAvraham describes her/him in the last sentence of the lead of the appropriate Wikipedia article. This Digital Citizen article says "Unfortunately, not many people know about this tool, as Windows does not advertise it as much as it deserves." The article starts out describing how to open Windows Task Scheduler, but that description only applies to Windows 7 and later. Windows 7 wasn't made generally available until late October 2009 and was adopted by users over the next 3 years. By March 2014 Retrospect Inc. had introduced the Dashboard, which the engineers evidently believed would be an easier-to-use generalized within-the-application-UI solution for Retrospect Windows (but they didn't attempt to fix its glaring bugs until 2017). In 2013, the engineers must have felt that building a UI solution into Retrospect Windows would be easier than trying to teach backup administrators to use a separate facility in a version of Windows that was just then achieving critical mass—and a scan of these Forums will show you that many Retrospect Windows administrators are forced by their organizations to work with obsolete versions of Windows.
  5. DavidHertzberg

    unistall engine

    Lennart_T, I am shocked that you of all people would say such a thing (see the second and third paragraphs) about the UG. Since I'm sure you're just as tired as I am of dealing with the lack of UG updating, I suggest you write (which I've done) to Rod Harrison—the Chief Technology Officer of Drobo who probably now has some influence at Retrospect "Inc". If you want to impress him with a Swedish-stamped "snail-mail": Drobo Attn.: Mr. Rod Harrison, CTO 1289 Anvilwood Ave. Sunnyvale, CA 94089 USA However, if you are willing to enroll in LinkedIn—which I am not because of delete-finger tiredness—you should be able to get an e-mail address for Harrison there. P.S.: What Lennart_T and I said about the User's Guide not being updated is still valid; Nigel Smith's post below goes beyond what the UG says.
  6. DavidHertzberg

    Can scheduled operations be done without retrorun

    NoelC, With Retrospect Mac, the Retrospect Mac Engine task normally starts when the Mac is booted as a particular user, and is not stopped except by going to System Preferences. The Retrospect Mac Console (non-Web) is a separate GUI task that can be started and stopped and re-started from the Mac Dock. The Retrospect developers were trying to implement this same Engine/Console split for Retrospect Windows, but—as the first paragraph here says—Gates and Ballmer made that impossible (unless the Engine was given a built-in Web server—which the Retrospect developers either couldn't or didn't want to do). The Retrospect "Inc." developers are, as I write this, preparing to release an enhanced version of the Web-based Management Console that should—based on hosting the Console on Heroku—finally allow Retrospect Windows to have the same Engine/Console split as Retrospect Mac. Then you'll be able to let the Retrospect Windows Engine run 24/7, while using nothing except paged-out memory when no operation is running. P.S.: And here's my brief discussion of the Web-based Management Console, which was released on 1 October 2019.
  7. DavidHertzberg

    Can scheduled operations be done without retrorun

    NoelC, I'm a Retrospect Mac administrator, so I don't have the possibility of any retrorun service—since Retrospect Mac 8.0 in 2009 eliminated it. However this 2017 post seems to tell how to use Windows Task Scheduler. OTOH the 2018 thread starting with this post seems to tell how to use the Retrospect Launcher Service. There's also this 2019 Knowledge Base article, which may not be applicable to your setup. Finally Retrospect Windows does not quit after an operation—backup or otherwise—is complete if there is another operation scheduled within the "look ahead time", which defaults to 12 hours. This is discussed under "Schedule Preferences" on pages 397-398 of the Retrospect Windows 16 User's Guide. I think the feature applies whether or not you're using retrorun, but again as a Retrospect Mac administrator I'm not an expert on it..
  8. karma, I do indeed have a Digital Audio G4 booting OS X 10.3.9 (I couldn't afford a 10.4-compatible ATTO SCSI card) on a SCSI drive I added, and Mac OS 9.1 on its two ATA drives. When I upgraded to Retrospect Mac 16 I decided the easiest thing to so was to backup the G4 weekly using Retrospect Mac 6.1—which I installed on the SCSI drive—onto my still-working HP DAT 72 tape drive. If that hadn't worked I would have used Retrospect Mac 15 on my "cheesegrater" Mac Pro's spare third HDD to be the "backup server" for the G4's drives using the Legacy Client. However I would have either had to buy 3 more portable USB3 HDDs to be used in rotation as destination Media Sets, or to take the chance that Media Set format hasn't changed between Retrospect Mac 15 and 16. That would have been a chance worth taking, since I don't use the Retrospect 16 Storage Group feature. However re-booting my Mac Pro to run Retrospect Mac 15 would have been a nuisance, and I can run Retrospect Mac 6.1 on my G4 in parallel with the Retrospect Mac 16 LAN backup of my MacBook Pro. Doing so actually speeds up the elapsed time for my Saturday Recycle backup routine, although the 3-hour LAN backup of my G4 drives has been replaced by a 5-hour tape backup (the tape drive is slower than my LAN, and my Compare phases—an absolute necessity when backing up to tape—are byte-by-byte instead of MD5-digest) You'll have to read that old thread more thoroughly than I'm prepared to, but I don't think either of the European administrators participating in it tried disabling Instant Scan in Retrospect Mac 15 for their APFS drives. If that works it might slow down your backup of the APFS drive by about 10%, but I'm not prepared to test it out—especially to find out if it works.
  9. x509, DovidBenAvraham was editing the Wikipedia NetBackup article early this afternoon, to correct links he had put there because of the split-off of the Enterprise client-server backup article (which of course is based mostly on Retrospect features but made application-neutral). In doing so he was reminded of NB's Web-based Management Reporting feature, to support which—based on our quick look—it is documented that a NB "backup server" has a small embedded Web server. My guess is that in 2008 EMC's Retrospect developers, who were under tremendous management pressure, didn't have the ability to make or buy such an embedded Web server—and may have loathed that adding one would "embiggen" Retrospect Windows. In fact what they eventually did in Retrospect 16 was to implement the Web-based Management Console as a hosted service (second paragraph); I have now been able to locate the name of the service provider—it's Salesforce Heroku. I am in thorough sympathy with your views. However I would strongly recommend against expressing them in these Forums; I've had posts deleted in the past by the head of Tech Support for the real reason that they were critical of management. If you read between the lines of this WP article section, and also read its references, you will understand why long-time employees of Retrospect Inc. have what used to be known among baseball players/fans as "rabbit ears".
  10. x509, My "better memory about old posts" is embodied in the Search box in the upper-right corner of the Web page for the Forums. The Search box used to have more facilities before the Forums software was "upgraded", but—if you check-mark "Find results that contain... All of my search term words"—it's still usable. AFAICT, a Web-based console is the best Retrospect Windows administrators are going to get; see the first paragraph of this section of the Wikipedia article. AFAIK all the other backup applications whose "backup servers" run on Windows have such Web-based consoles, because Gates and Ballmer made a Retrospect-Mac-style non-Web console impossible starting with Windows Vista and Windows Server 2008. My hope is that, since the StorCentric acquisition probably signals the failure of Retrospect Product Management's "go big or go home" strategy, StorCentric management will convince Product Management that EMC's venerable "soak the rich" strategy also isn't going to work any longer. If my hope is realized, Retrospect Windows administrators will be able to set up a two-way Web console without paying for an additional license. The alternative will be your "small price to pay" at every "backup server" reboot..
  11. karma, you bet your bippy there there have been APFS-related improvements and fixes in Retrospect Mac 16! First, it's Searching the Retrospect Website is Fundamental time. You should start with the Retrospect Mac Cumulative Release Notes here, beginning going down from the top with "Engine: Scanning faster on APFS volumes" for Mac In practice that refers to the problem—described in the thread ending in this post—other administrators had with Instant Scan for APFS in Retrospect Mac 15.6.1. I recommend that—after upgrading your license code per the next paragraph—you install the latest version of Retrospect Mac 16 on your "backup server" machine (mine is still running Sierra) and your Mojave-running "client" machine, and then Remove and re-Add on your Console's Source panel the Client for that "client" machine. After you re-Add, make sure in Options that Instant Scan for that machine is un-checked. In each of your applicable Scripts, you will then have to re-checkmark that "client" in the Source pane and—after clicking the Save button—drag that "client" into its desired backup sequence in the Summary pane. Since a view of your posts shows you upgraded to Retrospect Mac 15 in February 2019, you are AFAIK entitled to a free upgrade to Retrospect Mac 16. I recommend that you phone Retrospect Sales, although you may be able to request the upgraded license code in an e-mail.
  12. Oh my, x509, it appears you're back to the same situation I responded to here in a post last fall. My first suggestion would be to follow whichever of the alternatives is appropriate from the first paragraph of that post. My second suggestion would be to update your Support Case on the problem, but this time tell Support to tell Engineering that you'll go to Rod Harrison—CTO of Drobo and probably by virtue of that position now de-facto StorCentric "enforcer" at Retrospect formerly-Inc. Engineering—if you don't get some work-around in Retrospect Windows 16.5 (which I hear is due out around 20 September). A snail-mail address for Harrison is : Drobo Attn.: Mr. Rod Harrison, CTO 1289 Anvilwood Ave. Sunnyvale, CA 94089 However, if you are willing to enroll in LinkedIn—which I am not because of delete-finger tiredness—you should be able to get an e-mail address for Harrison there. My third suggestion would be to "go with the flow", and setup the Web-based Management Console per this Knowledge Base article. Of course I haven't had to do that because, as a Retrospect Mac administrator, I've had a perfectly-adequate non-Web-based Console since I upgraded to Retrospect Mac 12 (from Retrospect Mac 6.1 on a "backup server" machine that died in 2010) in 2015. P.S.: In response to x509's post below, I'd think "royally pissed" would be expressed by the following emoji:
  13. DavidHertzberg

    How to restore files on top of what's there?

    It could have been either model; the IBM 2314 was basically a larger-capacity version of the 2311, with 11 platters instead of 6. My first job as a programmer (initially a trainee after two weeks of reading)—starting in June 1964—was with C-E-I-R Inc., the pioneer of non-manufacturer service bureaus. We had professional operators in the air-conditioned computer room, who would have broken my fingers if I dared to touch hardware—with a pencil eraser tip or even pushing a switch. IBM 026 card keypunches were used for input to 2nd-generation computers such as the IBM 1401, beloved because it was so easy to program in assembly language (as in this example whose statement labels and field names are in programmer-chosen abbreviated German but the operation codes are IBM-standardized abbreviated English). IBM 029 keypunches were a later model used for input to IBM System/360 computers, to which 2311s and 2314s were attached.
  14. Briefly returning to motivation for the merger, this very-interesting article based on a phone interview with Mihir Shah has actually been linked to on the "Latest News" PR section of this website—which you can view by signing on to your Portal. A quote says "The big vendors focus on $30m-per-year customers and 'forget about everyone else', according to Shah." That sounds to me like a criticism of the "go big or go home" strategy that, in a previous post in this thread, I suggested Retrospect Product Management was trying to follow—evidently without great sales success. The next quote says "StorCentric will focus on selling affordable products to the everyone elses, said Shah. Things that just work." But IMHO here's the really interesting indirect quote from the interview: "What next? Surya Varanasi, co-founder and CTO of Vexata, is developing a technology roadmap for StorCentric. Shah didn’t expand on that, apart from saying two new Drobo products are due in the next six months and a Drobo+Retrospect backup appliance is being considered [my emphasis]." Since I corrected a previous post in this thread because I found out that Retrospect can already use a Drobo as either a source or destination for a backup, I can only assume what is being considered is using a Drobo as a "backup server". Drobo appliances apparently already use a version of Linux as their OS, so it doesn't seem impossible for the Retrospect engineers to convert the source code for the Retrospect Mac "backup server"—which is already running on a macOS that is mostly enhanced BSD Unix underneath the GUI. Starting in the early 2000s with a "backup server" that ran only under Linux/Unix, the TOLIS engineers developed a version of BRU that runs on macOS. If the Retrospect engineers make the converted "backup server" code run on other versions of Linux besides the Drobo, that would be a "go wide or go home" marketing solution. And I'll bet a cheap add-to-your-LAN-then-install-user-Clients Drobo+Retrospect backup appliance would sell like hotcakes to under-funded local government organizations, which must be worried about this all-too-real menace. IMHO forced client-server backup of users' computers is much easier to implement than a 100%-effective "don't click on any links in e-mails" training program. Obviously DovidBenAvraham can't yet discuss this in the "Retrospect" article, because discussing software under development is taboo for a Wikipedia article. However he can probably get away with using the interview article as a reference, since it has a section that recapitulates the past history of StorCentric.
  15. In applicable Wikipedia news, an kindly Australian woman editor with the "handle" Melcous did extensive edits to the "Backup" article on 10 August and 18 August 2019. She somewhat over-simplified the "Near-CDP" sub-subsection, but DovidBenAvraham later rectified that to clarify that personal (non-client-server) backup applications at most have a near-CDP capability. Retrospect non-V. doesn't have even that—since scripts can only be scheduled to run as frequently as once an hour; that's probably because Apple's venerable HFS+ filesystem doesn't have a "snapshotting" capability—which Apple's new APFS filesystem finally adds. R. V. does near-CDP, not true CDP—a feature of only a handful of very-expensive and tricky enterprise applications. DBA has now made each of the feature descriptions in the "Enterprise client-server backup" article a separate Wikipedia subsection. This has enabled him to make direct links to these features from the "Backup" article, eliminating the wordiness of previous links that had text allowing a reader to find the proper feature description within a link to its section—a pet Melcous peeve. DBA has also changed such links in the "Retrospect" article, and in internal links in the 3 articles. DBA's posting of an Administrative Noticeboard Incident seems to have scared Pi314m out of trying to merge the "Enterprise client-server backup" article back into the "Backup" article. The ANI was not successful in getting any kind of banning imposed on Pi314m, IMHO primarily because—having never posted an ANI before—DBA made his first paragraphs too wordy for the WP administrators. However DBA later added a couple of concise paragraphs detailing Pi314m's merging of 10 related articles into the "Outsourcing" article in early 2019, deleting most of the text of those articles without prior discussion. That kind of merging appears to be a violation of Wikipedia rules, and we're sure Pi314m realizes that DBA will bring it up again if some kind of post-holiday letdown leads Pi314m to try merging again in early 2020.
  16. DavidHertzberg

    Queueing Jobs Manually

    jhg, If you want to submit an enhancement request, here's why and how to do it. However I suspect that Retrospect Tech Support's answer will be along the lines of "it's already the way we'd like it to be". Their explanation would be that anyone who submits two Immediate operations whose destination is the same Backup Set is more likely than not to have made an error. Starting with version 8.0 in 2009, Retrospect Mac did away with Immediate operations; clicking the Backup button in Retrospect Mac generates a script scheduled for the current date-time with whatever source-destination-etc. you specify. A few weeks ago, doing an experiment for other purposes, IIRC I clicked the Run button in the Scripts panel to schedule the same script twice with exactly the same source-destination-etc.. Retrospect Mac 16 wouldn't submit the results of my second Run click, but would do so if I added a Repeat Never schedule of the same script 2 minutes later. That smells to me as if the engineers took the trouble to convert the Retrospect Windows behavior you don't like so that it works the same way in a dramatically-revised GUI. If I paraphrased H. L. Mencken to say "Nobody ever went broke underestimating the competence of backup administrators", I suspect the engineers would say they already have the equivalent statement on a wall plaque in Walnut Creek CA.
  17. DavidHertzberg

    How to restore files on top of what's there?

    Thanks for the info, MrPete, For hysterical reasons I have been alternating between the use of two drives for Retrospect versions on my "cheesegrater" Mac Pro "backup server", one HDD and one SSD. ATM I have Retrospect Mac 16 on my SSD, with Retrospect Mac 15 on my HDD. However I've elected to keep my Catalog Files on the HDD, just in case I have to switch back or upgrade forward. Retrospect Inc. (should I still call them that?) is kind enough to provide new point-releases of Retrospect Mac 16 about every 3 months, which I'm sure they do just so I can refresh my SSD. I was vaguely aware that SSDs had a shorter lifetime than HDDs, but I thought progress had been made on that problem. Now you're saying it hasn't, so what was good enough in the 1970s is still better over the long term than its replacement. Spinning rust forever!
  18. About 6 weeks ago I started getting -559 network connection timeout errors after about 2 hours while running my weekly "Sat. Backup" full backup of my MacBook Pro (the first of 3 drives plus a Favorite Folder backed up in that script). There had not been any change in any of my software or hardware, so I guessed that at least one of my two Netgear Gbps Ethernet switches was starting to feel its age. I replaced both switches with non-Netgear 100Mbps switches I had lying around, and the problem went away—without slowing anything down except (moderately) the MBP's Compare phase of "Sat. Backup". Since NewEgg was having a US$15 sale on TP-Link 8-port Gbps switches (Heavens to Betsy, my home LAN is becoming obsolete because I'm not upgrading it to 10Gbps ), I ordered a pair of them. Even though replacing both 100Mbps switches with the Netgear Gbps switches one at a time didn't cause the -559 problem to recur, a week ago Sunday I replaced both switches with the newly-arrived TP-Link Gbps switches. The -559 problem still didn't recur last Saturday, so Sunday night I went into experimental mode and Deleted-Added my MBP with Use Multicast. Both a pre-scheduled "sacrificial" "NoOp Sun.-Fri Backup" script and "real" "Sun.-Fri Backup" script failed with -530 errors when I booted my Mac Pro "backup server" machine after the time when they were scheduled to run. I therefore Deleted-Added my MBP with Add Source Directly, and have had no further problems. IMHO this experience proves that my -530 Bugs 1 and 2 are not caused by a "security improvement" that was made solely in Netgear's Gbps Ethernet switches. Because I started getting -530 Bug 1 immediately after I replaced the failed D-Link 100Mbps switch in my study with a Netgear Gbps switch on 30 January 2017, without any change in my then-current Verizon DSL "gateway" router, my guess is that the "security improvement" was made to several manufacturers' Gbps Ethernet switches. And no doubt there is a contributing factor of Retrospect's implementation of its Multicast feature failing to keep up with the "security improvement".
  19. DavidHertzberg

    .mkv files and backups in Retrospect v.16

    CherylB, Here's a Retrospect 8 Forum thread from early 2011 that discusses this problem. IIRC Retrospect Mac 9 wasn't released until late in 2011. A key question is whether your user's .mkv files have the .mkv extension on the name of the file. If not you've got a problem, unless you restrict what is scanned via Favorite Folders etc. as later posts in that thread suggest. BTW, this "Retrospect Mac bug reports" forum is no longer routinely looked at by anyone from Tech Support, so you might as well have posted your problem in the parent "Retrospect 9 or higher for Macintosh" forum. Besides, it seems the problem isn't a Retrospect bug so much as a Retrospect limitation—it can't tell the type of a file that doesn't have an extension on its name.
  20. DavidHertzberg

    AWS virtual tape library

    blm14, What Nigel Smith said. Let me add two pieces of information. First, it is a not-evident fact (see page 225 of the Retrospect Windows 11 User's Guide; last I heard you were still using that version) that Transfer Backup Sets operations can use Selectors. You could use Selectors in running Transfer Backup Sets operations whose source is a regular Amazon S3 bucket and whose destination is a Glacier bucket, specifying a date to separate the "archival" backups from the "recent" backups. But that would still leave you with the "archival" backups also in regular S3. It is a fact that, if you upgraded to at least Retrospect Windows 15, you could use Selectors in Grooming scripts to groom out the "archival" backups from regular S3 after you have migrated them to Glacier. This Knowledge Base article talks about using Selectors in Grooming scripts specifically for satisfying GDPR requirements, which is why the Selector capability was added to Grooming scripts in Retrospect 15. My guess is that you could specify the faster and cheaper (no Amazon download fees) Performance-Optimized Grooming in those scripts, since your grooming Selector would specify a date—not the name of an individual customer having a "right to be forgotten". In any case, my impression from this article is that you would have to have an on-premises appliance in order to use an AWS VTL. because that would require some kind of "intermediary" local storage. Since you seem to have an aversion to taking local tapes or disks off-site, how would that differ from Nigel's proposal? P.S.: Here's rforgaard's 2016 post on how to setup AWS S3 cloud backup for Retrospect Windows 11. Here's the only-slightly-later KB article; here and here are other applicable KB articles. P.P.S.: Just to make it crystal-clear, blm14, I don't think you need an Amazon VTL. Transfer Backup Sets in Retrospect Windows 11 gives you the capability to transfer "archival" backups from a local tape Backup Set directly to Amazon Glacier (after a 1-day stay in regular AWS). Retrospect Windows 15's enhanced Grooming scripts would give you the capability to keep the "recent" backups in regular AWS, without duplicating what you have in Retrospect Glacier. If you need multiple "conceptual tape" Backup Sets to keep the "recent" vs. "archival" dates straight, you'll probably have to pay for extra hardware even if Retrospect can interface with an Amazon VTL—and I don't know if it can (or needs to). P.P.P.S.: Here and here are articles discussing VTLs. The bottom of the second page of the first article discusses a solution that "is available either as a fully-built appliance or as a software component of ***'s Virtual SAN SDS solution that can run on a customer's existing hardware." The STK L700 is a physical tape library originally from StorageTek; my impression is that its instruction set is widely emulated. Again, I don't see why you can't simply run Transfer Backup Sets scripts to copy your "recent" backups to either local HDDs or regular AWS, and then run Transfer Backup Sets scripts to move the "archival" data to Glacier—followed by Grooming it from the "recent" backups.
  21. DavidHertzberg

    AWS virtual tape library

    blm14, I still suggest contacting Retrospect Sales. Did you do that, as I suggested in the P.P.S. of my preceding post in this thread? Also, I said in the P.S. of that same post, AFAIK there would be a non-trivial hardware cost; however a re-listen to the brief mention in the NB video and Google search suggests that may be replaced by a virtual appliance in an AWS EC2.
  22. I'll end my comments on the merger with a bit of pure speculation on what the synergy might be for Drobo. I found this 7-year-old blog post, briefly updated over two years ago. Its "Why I'm done with drobo" section basically says that if your Drobo box dies, you have no choice other than to replace it with another Drobo box because its BeyondRaid formatting is proprietary. In the meantime the data on the HDDs that were contained in that Drobo box are inaccessible; one commenter on that blog said 4 years ago that she couldn't get files off her crashed Drobo, a model that is out of production with no parts available, so her only option was purchasing a new Drobo model. The Wikipedia article on Drobo has the same criticism. There is one backup application whose maker partners with Drobo, but it only backs up to the cloud—which may be rather expensive for an administrator with many large files on their Drobo. So why not give Retrospect Inc., now a subsidiary of Drobo's parent company, the proprietary format for BeyondRaid—enabling backup of a Drobo to tapes or a big-but-non-RAID HDD? I'm not saying the Retrospect engineers could add this capability in a week, but they've already done the equivalent for Avid Media Composer. "And now that you've paid US$49 [ or maybe nothing—my marketing genius tendencies are telling me to double-cross the maker of the cloud-only backup application ] for your license to Retrospect Solo with Drobo Capability, how about upgrading to Retrospect Desktop Edition with Drobo Capability for another US$35?" P.S.: A Forums search indicates Retrospect has long been able to use a shared Drobo as a source, although some Retrospect Mac administrators have reported problems here and here. By a not-so-strange coincidence, a new Knowledge Base article has just been posted—whose "Retrospect Setup: Add Drobo as a Source" section consists of two YouTube videos narrated in the dulcet voice of the head of Technical Support. So my speculation about Retrospect needing Drobo's proprietary format information seems wide of the mark.
  23. henry-in-florida, Read all of my OP in that same thread. I believe it answers all your bulleted-point questions except the third one. Nigel Smith's final post in that thread recaps my experience doing a suggested upgrade from Sierra to High Sierra, but we're not sure how the Apple Support person found an installer that enabled me to do that—and we're pretty sure we couldn't find one ourselves.
  24. henry-in-florida, The bottom of this April post contains my method for fully restoring a machine after a bare-metal Erase and Install of the High Sierra OS on a MacBook Pro with an SSD. As discussed in the OP of that thread, it has been combat-tested ; I'm pretty sure it will also work for Mojave and Retrospect Mac 16. In the last post of that thread, the worthy Nigel Smith gives the method his blessing.
  25. DavidHertzberg

    Request to increase size of disk backup set is being ignored

    You can get a free 45-day trial of Retrospect Windows here. If you talk to Sales at (888) 376-1078 or (925) 476-1030, they can probably check with Tech Support to see if that release fixes your problem—and if so tell you how much it will cost you to permanently upgrade. If it does, you can presumably find some disk drive on which to install it.