Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by DavidHertzberg

  1. LTO-5 drive not found by Retrospect 11.5, Windows 10

    afripp, I notice that, at least in your fourth paragraph, you seem to want to treat this LTO-5 drive as an LTFS device. You should be aware that, although Retrospect Windows 12 announces new support for LTFS, this is only for the Duplicate function—not for Backup or Archive. Do you have a non-LTFS driver for your LTO-5 HP Ultrium 3000 tape drive installed on your HP Z620 workstation with an LSI 9207-8e HBA?
  2. Backup to AWS

    First of all, ggirao, your immediately-preceding post quoted me as saying something I didn't say—you said it. Being a suspicious person, I'm inclined to believe that you did that just to generate a notification to me so I would look at this thread. If you do that again, I won't respond to your false-quote post. The polite way to get me to respond is to send me a notification, which you can do by clicking the bell icon at the top right of a Forums page and following the prompts. However the reason there is no documentation regarding Cloud Backups in the Retrospect Mac 14 User's Guide is explained in this post in another thread. I won't repeat that explanation here, because the head of Retrospect Technical Support would undoubtedly feel that I was beating his department over the head about a set of gross Retrospect Inc. errors that he wasn't responsible for. Some cloud-vendor-specific information was later documented in 16 Knowledge Base articles here, but the more-generalized info mentioned in the third paragraph of the post I linked to in the first sentence of this paragraph got completely wiped out. Did you—ggirao—bother to phone Retrospect Sales about why the drop-down option for Cloud is greyed-out in the first attachment of your post yesterday? I did a few minutes ago, and Werner told me that the option is grayed-out until you first set up an Amazon S3 account as described in the appropriate Knowledge Base article. I won't link to it, because I think it would do you good to find it yourself.
  3. Backup to AWS

    ggirao, To begin with, you didn't tell us what version of Retrospect Mac you are running, or what version of macOS your "backup server" is running under. So I'll assume you're running Retrospect Mac 13, since the last post you made on these Forums—in this thread in fact—was in October 2016. I'll further assume that you are some kind of consultant who can't ask the person who installed Retrospect, since otherwise you'd know (or remember—if you installed it yourself). And I'll further assume that your real question is why the Cloud item in the drop-down menu shown in your first attachment is greyed-out. Therefore I'd first suggest that you read page 192 of the Retrospect Mac 13 User's Guide, which discusses the Licenses preferences pane. You can reach that by clicking the second-from-the-right icon shown at the top of your second attachment in the quoted post. Next select the topmost license code listed in that pane—but write it down on a slip of paper first, and click the Register button in that Preferences pane. That will give you a Web page, into which you should enter the license code you have written down and then click Next. The Support page that will take you to will tell you whether you have a trial version. Any questions you have resulting from that should be directed to Retrospect Sales. Please excuse the somewhat-unfriendly tone of this post, but last week I dropped my crystal ball while taking it out of the dishwasher. It broke, and I'm still unhappy (insert appropriate emoticon here).
  4. E-mail notification failed: error 592 (invalid response from SMTP server)

    The OP should try doing what this post in a 2015-2016 thread says, namely leaving the username and password fields blank. I should point out that, in the last post in that thread, that thread's OP says "The email stopped working for me. I set up a free google account and it's able to send from the google account. Probably the easiest workaround." The next-to-last post, by the very knowledgeable Don Lee, says "FYI - tcpdump is your friend, if you want to "see" the exchange between the server and the server" and gives directions for doing so. If the OP wants to know how I found that thread and several others about error -592, he/she can read the last paragraph in this post in a very recent thread about another Retrospect error code.
  5. As recounted in previous posts in this thread, and in a previous thread, I find the "drop and add client " solution works for only a week or two. Since my last two sets of hardware changes (attaching a pair of 100Mbps-speed and then gigabit-speed Ethernet switches), it hasn't worked at all. My current solution is to Pause all running scripts during the "sacrificial script" run, whose running I've prolonged to 10 minutes with Preferences changes, and to then Locate my MacBook Pro—which always works within a couple of seconds. After that I Resume all scripts, Stop the "sacrificial script", and the real backup script finds the MBP and runs OK.
  6. Thank you, Scillonian. As a strictly-Mac administrator, I had not understood the full implications of running using the Retrospect Windows Launcher service—which are only described in the first paragraph of this Knowledge Base article (I'd read it, but evidently not fully understood it). My gosh, I'm sorry for you poor people! This raises an important question: Why does derek500 have to auto-launch Retrospect? He considered the possibility of not using auto-launch in this earlier post in the thread, but said "The only solution I see at this time is to leave the console [by which I now think he meant Retrospect.exe in GUI-open mode] open and never log off but I don't like the idea of leaving disconnected RDP sessions." First of all, derek500 might not need to use RDP at all. Assuming he only needs to access a constantly-running Retrospect.exe from another machine on the same LAN, he could use a VNC variant instead. He could just connect to the VNC client—either directly or via a web browser—when he needs to, and the VNC server on the machine that is running Retrospect.exe would allow him to control it. The "Security" section of the Wikipedia article linked-to in the second sentence of this paragraph mentions several VNC variants that have encryption. The "Limitations" section of that same Wikipedia article on VNC mentions and links to Windows RDP. It is supposedly more efficient than VNC variants, but derek500 may not need efficiency just for some limited interaction with the Retrospect.exe GUI. Pages 434-436 of the Retrospect Windows 12 User's Guide mention RDP under the heading "Terminal Services and Remote Desktop". Page 68 of that same UG says "If Retrospect is running and you want to close the control window, disconnect from the Terminal Services session, but leave the session running. The next time you connect, the same session will be running and Retrospect will be unaffected." That's what derek500 was talking about in the section of a previous post I quoted in the second paragraph of this post. If I were he and decided after all to use Windows RDP, I'd first have an IT person double-check the instructions on pages 434-436; a User's Guide that still uses the obsolete term Terminal Services may not have been updated for changes in Windows subsequent to Retrospect Windows 8. P.S.: The combination of Retrospect Engine and Retrospect Console that is running on my Mac Pro "backup server" is currently—while it is backing up the last of my local drives—only using a maximum of 675MB real memory (virtual, shmirtual, is what us fuddy-duddies say). That is probably roughly equivalent to what Retrospect.exe would use while backing up on a Windows "backup server" with the GUI visible. And now that my backup script has finished running, the combination of Retrospect Engine and Retrospect Console has dropped to 250MB real memory. IMHO derek500's installation ought to be able to afford reserving that continuously. (Why in my day, the IBM 704/709/709x series could address a maximum of 192KB at a cost of US$3 million; and that's while I was bicycling 4 miles to and from high school—uphill both ways. You young whipper-snappers have no idea ....) And I know, because I occasionally start the Retrospect Engine on my Mac Pro before a script is due to run, that the Engine—whose capabilities I'm sure Retrospect.exe also has—will automatically start running a script when it is scheduled to begin without needing any Launcher service (which Retrospect Mac doesn't have).
  7. saskia, Presumably you don't have a WAN between your home and your workplace, so you must communicate between them using the Internet—which is what Chrome Remote Desktop uses. However Monafly, in the OP of this thread, says he/she is retiring and "my replacement sits at a PC". In this later post, he/she says "It may be possible to install the Mac engine close enough to the Windows machine to use a KVM or some such. " So why mess with something that requires a functioning Internet connection between the two machines, which is also true of TeamViewer, if a LAN connection at most is sufficient?
  8. While I appreciate mbennett's explanation, I think he has missed the idea I was trying to get across in this post. So I'll spell it out: Whenever derek500 wants to do things with Retrospect such as "reviewing how a script was set up, or rescheduling an upcoming script, or grabbing a status list ", either Retrospect.exe is already running on his "backup server" or it isn't. Using the Dashboard will tell him which is the case. If Retrospect.exe isn't already running, he can just start Retrospect.exe from the Dashboard and do whatever he wants. If Retrospect.exe is already running, derek500 will not want to start it from the Dashboard if there are any running jobs that doing so would kill. In that sub-case, he should instead then use a VNC variant to share the desktop of the "backup server" from another machine—which will enable him to directly access the GUI of the running Retrospect.exe to do whatever he wants without disturbing running jobs. (This is IMHO an easier up-to-date variation on using Windows RDS—referred to in the Retrospect Windows User's Guides by its obsolete name of Terminal Services.) Of course derek500 could simply leave a VNC variant running all the time on another machine as a Windows equivalent to the Retrospect Mac Console , which would enable him to dispense with the Dashboard entirely. If he doesn't like that idea, he could instead keep the Dashboard running all the time on his "backup server" in an account other than the one used to run Retrospect.exe. I thought he might not like that idea, which is why I posted this question aimed at finding a way to kill the Dashboard without starting Retrospect.exe.
  9. Error scanning network 1116

    Here's one post from 2010 that provides an answer, which may or may not be applicable. Here's another post from 2003, by the head of Retrospect Tech Support; it too may or may not be applicable, but the post below it in that thread by AmyJ looks like she had an answer with a more-general explanation. Another post from 2008 points to a permission problem with a NAS drive; it links to a Knowledge Base article that was on the old Dantz website whose links now go to a British glove company, but I think I've found an updated—or recreated—version. The 2016 thread that continues from this post includes posts by the very-knowledgeable Scillonian and Lennart_T. If I were ITRESULT, I'd look there first. And how, ITRESULT may ask, did I find all these posts (and 89 others) on error -1116? The answer is that I used the Forum's Search capability, starting by clicking the word "Search" in the stretched-out-oval box with the magnifying-glass icon at the upper-right of the page—below the user's "handle". That popped-out a drop-down menu labeled "All Content", from which I selected the "Advanced Search" item. I then typed "-1116", including surrounding quotes to avoid getting posts that included the number 1116, into the "Search Term" box to the right of the magnifying-glass icon at the top of the page selecting that item gave me. Next I clicked the "Search Content" button at the lower-right of the page. That gave me a multi-page list of posts; I clicked the thread title at the top of any list item whose excerpted content sounded interesting.
  10. mbennett, derek500, or anyone else: In regard to my post immediately above this and this post by derek500, does 'close the Dashboard [which is what I assume derek500 means by "console"] or log off' automatically start Retrospect.exe in Retrospect Windows 12.6.1? If so, isn't there a Windows equivalent of macOS's Force Quit Applications that would kill the Dashboard program without starting Retrospect.exe?
  11. derek500, I think the way to immediately get what you want would be: [1] Use the Retrospect Windows 12.6.1 Dashboard to see if Retrospect.exe is running. [2] If it is, use a VNC variant—as I suggested in the second paragraph here—to access the Retrospect.exe GUI and "tell all unstarted/pending jobs to delay start but let the actively running jobs keep running". I don't know what VNC variant would be best to run for Windows-controlling-Windows desktop sharing; RealVNC and TightVNC and UltraVNC are possibilities that I or others raised per this Windows-controlling-Mac post on the Mac forum. As I've said before in this thread, I don't think you should hold your breath until a Retrospect Windows Console actually sees the light of day.
  12. derek500, Your Dashboard "'easier' workaround" sounds quite reasonable to me. It also sounds as if the mechanism for implementing it quickly might exist in Retrospect Windows, since "Retrospect for iOS"—page 578 of the Retrospect Windows 12 User's Guide—supposedly has the capability "Run from afar— Just tap on a script to run it." If you want to submit this as a feature request, here's why and how to do that (in case you don't already know). Getting the feature into Retrospect Windows 13.0 seems like a stretch, since that's probably due out the first week in March 2018. However getting it into Retrospect Windows 13.5 seems possible, since that is probably due out the first week in September 2018, unless—and I'll be pleasantly surprised if this happens—one of those two releases contains a first version of the Retrospect Windows Console. Actually, it now occurs to me that your feature request should also suggest as an alternative that the ""'easier' workaround" be implemented in Retrospect for iOS—since that may be easier for Retrospect Inc. engineers either technically (inter-process communication) or schedule-wise. Get that feature request in ASAP, and good luck! P.S.: As I have already communicated to derek500 in a message, my reasoning behind the Retrospect for iOS alternative is as follows: If you read Scillonian's previous post in the thread, you'll see that it may not be possible for the Retrospect Windows Dashboard application to interact directly with a running Retrospect.exe. Don Lee—under his former "handle" of iCompute—got a Retrospect Mac Console to sort-of communicate with Retrospect.exe in Windows, but that used the inter-process communications capabilities that were carefully left in Retrospect.exe. Those same capabilities seem to be what make it possible for Retrospect for iOS to communicate with Retrospect.exe, and are what would make it comparatively simple to give Retrospect for iOS the ability to "tell all unstarted/pending jobs to delay start but let the actively running jobs keep running" .
  13. mbennett, As a Retrospect Mac administrator, it seems to me the question I'd want to ask is: If you open the Dashboard from its separate icon, and Retrospect.exe turns out to be running as auto-launched, do you have the option of simply observing any running activities from the Dashboard without clicking the Dashboard's "Launch Retrospect" button? That, IMHO, would give a Retrospect Windows administrator almost the functional capabilities of the Retrospect Mac console. If so, the only thing that a Retrospect Windows administrator couldn't do—when Retrospect.exe has been auto-launched—that a Retrospect Mac administrator can do is to create/modify/submit either scripts or Immediate-ops while other scripts or Immediate-ops are running.
  14. New Windows user wants advice

    It appears that, per mbennett (formerly known as ProFromGrover), Retrospect Windows 12.6.1 has more or less solved this problem. No, it turns out that the fixed stand-alone Dashboard doesn't really solve the problem for the OP in that thread—who wants to run Retrospect.exe under the Retrospect Launcher but be able to modify scripts etc. without killing running scripts. However this later post by me in that same thread offers an alternative proposal, which involves leaving Retrospect.exe running constantly—but not under auto-launch.
  15. Page 85 of the Retrospect Mac 13 User's Guide has instructions on "To add a share as a backup location". However I believe you may first have to add the NAS as a Source (Retrospect Mac AFAIK needs any volume it deals with—even as a Destination— to be in the Sources list); this is covered on page 84 of the UG under "Adding a Server or NAS as a Source". Here is a short YouTube video, created by the head of Retrospect Tech Support, on "Adding NAS Source Volumes with Retrospect 10"; it shows adding an AFP source, but I'm sure you can adapt that to using an SMB name or address. HTH
  16. I woke up this morning well before the 3 a.m. scheduled time for the first of the two Sunday-through-Friday Backup scripts for my MacBook Pro. As promised in the last sentence of the first paragraph of the post directly above, I swapped in lower-speed Ethernet switches (which used to work) before deleting and adding the Client on the MBP (and then adding the MBP client back to the appropriate scripts, dragging it to the top of the Summary panel when necessary). The "sacrificial script"—that uses the No Files option—scheduled for 3 a.m. really ran OK, although as usual I had forgotten that in recent versions of Retrospect Mac adding a client defaults to the All Volumes option—including "pseudo-volumes" that only the client-adding logic can see (I've reported this in a separate Support Case, only to be met by the Tech Support reply that the volumes must be there if Retrospect can see them—insert wincing smiley here). I changed the client option to Startup Volume by the time that the "real" Sunday-through-Friday Backup script ran at 3:05 a.m., so that ran perfectly. Note that the Client software I installed on my MBP is the Retrospect Mac 14.1 version, because I had problems 4 months ago with the 14.6 Client even though I use the 14.6 Engine and Console on my Mac Pro "backup server". The acid test will come tomorrow, when I intend to not boot my "backup server" until sometime distinctly after 3:05 a.m.. If the "sacrificial script" gets a -530 error (or even runs OK) but the "real" Saturday Backup script—which does a Recycle backup of 6 drives and takes 8 hours—runs OK, then I'll be back to the situation I had before I started experimenting—as described in the P.S. of this December post. Then we'll see how long that situation lasts, based on the problems maxhowarth and boomcha have been having.
  17. Client Restore to New Hardware

    rfajman: You should look at this 2014 Knowledge Base article. To my intense surprise (insert appropriate smiley here) its title is "Error -3045 (There is insufficient storage space to complete the operation) and -3405 (Cant backup system state)". It sounds to me as if Retrospect thinks the 512GB SSD on your new machine is too small to restore the partition on the old machine that contains the operating system. Do consider the first and last paragraphs in the article, concerning extra space that will apparently be required on your 512GB SSD.
  18. maxhowarth and boomcha: The test I ran early this morning, pausing my "sacrificial script" run and using a Sources->select client->Refresh, didn't work; my"real" daily incremental backup run failed, and I had to do a Sources->select client->Locate before manually re-running the backup script. I will try swapping in lower-speed Ethernet switches (which used to work) before deleting and adding the Client on the machine I backup daily. I suggest that maxhowarth submit a Support Case for -350 Bug 3; why and how to do so are here, and he could also mention boomcha's experience I had the same experience with the fix stopping working as maxhowarth and boomcha nearly two years ago, but I'm not going to report it now because it is too stale. Besides Retrospect Tech Support might think I'm making a career of reporting multiple separate -530 Bugs, since I already have a long-standing Support Case in for -530 Bug 1 and my version of -530 Bug 2. You can tell them I suggest that they have the Retrospect engineers create what I call an "instrumented beta version" of the Retrospect Engine and Retrospect Client software, and distribute that version to a number of users who are experiencing -530 Bug 3. Each initial "instrumented beta version" would have code that compares its networking configuration file at the end of a script run to a stored version as of the beginning of the script run; that should enable the engineers to identify the script situation that causes a change in the networking configuration file to occur. After they've done that, the engineers should distribute a new version of the "instrumented beta version" with the comparison code moved earlier in the Engine or Client code; thus gradually they should be able to pinpoint the place in the code where the configuration file gets corrupted. Please tell Tech Support that I volunteer to run a copy of the "instrumented beta version", since I'm still chasing down a new -530 error of my own.
  19. Retrospect does not finish backup

    pplicit: I am not a Retrospect Windows administrator. However the Knowledge Base document "Retrospect 10 for Windows System Requirements" says, under "System Recommendations", "For Windows 10, Retrospect requires the 64-bit version". Is the 64-bit version of Windows 10 what you're running on your "backup server" machine?
  20. maxhowarth and boomcha: I suggest that you first read this post again, so that I can use terminology I've already defined. (Don't worry that the thread is defined on a Retrospect Windows forum; I defined the terminology based on my experience as a Mac administrator.) If your affected Macs can be backed up after you successfully execute a Sources->select client->Locate, then you have one or more types of -530 Bug 2 occurring. These range from the -530 Bug 2 I have been having for the past year—where the -530 seems to be caused by some sort of Ethernet speed mismatch between components of my LAN—to the -530 Bug 2 I had for about 5 months starting two years ago—where the -530 seemed to be caused by some kind of automatic software updating being applied to a client machine simultaneously with its being backed up. In the first case the Retrospect Inc. engineers ought to be able to fix the bug with careful attention to the "backup server"'s networking code, while in the second case the bug might be difficult for them to fix without instituting some kind of "timeout" limit for simultaneous software updating. You may be able to fix the cause of the -530 Bug 2 yourselves with hardware or software changes. If your affected Macs can be backed up without a -530 error if the "backup server" machine has been booted 10 minutes or more before the script starts to execute, and if otherwise you get a -530 error only on the first client machine being backed up, then you have a -530 Bug 1 occurring. This is obviously caused by some kind of "too-slow waking up" problem in the Retrospect Engine code, but the Retrospect engineers have so far not gotten around to fixing it—probably because doing so would require too much work. You may be able to work-around the cause of the -530 Bug 1 error, regardless of the existence of a -530 Bug 2 error, by either scheduling a "sacrificial script" to run first or by not scheduling your backup script to run until 10 minutes after the "backup server" machine is booted. If you—as maxhowarth and others including me have experienced—have fixed either a -530 Bug 2 or -530 Bug 1, only to have the the fix fail after a few days, then you have what I must now term a -530 Bug 3. The fix that eventually fails is typically the removing and adding of client machines in the Retrospect Console. This appears to be caused by some kind of corruption in a Retrospect configuration file, although whether that file is in the Engine software or in the Client software I cannot yet say. Right now I am getting some indications that a Sources->select client->Refresh may again temporarily fix the problem; I'll know more tomorrow morning. If that works, a Sources->select client->Refresh for each affected client would be faster than the the removing and adding of client machines in the Retrospect Console, with its required re-adding of client machine to Retrospect scripts. Please reply with additional posts in this thread specifying under precisely what circumstances of "backup server"-bootup-timing and client-position-in-backup-script you get -530 errors.
  21. Disaster Recovery Disk Method

    And here's one place (second paragraph and also here lower down in the same Wikipedia article) Scillonian could have read it.
  22. Cannot "move" disk media set

    Likewise oops; I missed that wiped-out capability in this post, to which I've now added a mention of it. Do you get the feeling, Don Lee, that the two of us should maybe be watching out for an information-suppression hit squad from Walnut Creek? (insert appropriate smiley here)
  23. stevejh, You're welcome. However I see now that item [2] in the first paragraph of my preceding post in this thread did you a substantial injustice. The second "bulleted" item in your OP says "Reinstalled Retrospect 11 from an app stored on a NAS", so you are not guilty of failing to state your version of Retrospect (I'll say nothing about stating your version of macOS). Referring to the Retrospect Mac 11.5 User's Guide, my second paragraph in that post should have referred to pages 164-168, and my third paragraph in that post should have referred to pages 161-163. It's a good thing that in those two paragraphs I also gave the titles of the applicable UG sub-sections. Sorry for my error. I strongly recommend that you download a .PDF of that UG onto your NAS, so that in case of future disaster you can refer to it even before you reestablish access to the Web on your "backup server".
  24. How fast are your network backups?

    In researching a newer topic in the Retrospect Windows Server forum, I came across this thread from 2010. It's interesting that the test results are very similar to mine, even though the OP was using Retrospect Mac 8. It's also interesting that a possible method of speedup, from the OP in that thread, was similar to what I was implicitly suggesting in this post above.
  25. AWS virtual tape library

    An interesting question, to which I don't know the answer. Someone (I see now it was blm14) asked the same question about 2 years ago, but didn't get an answer. However here is a list of iSCSI-interfaced VTLs which have been qualified to work with Retrospect Windows. However another interesting question is whether blm14 should do this, assuming he/she can. There is a non-trivial hardware cost associated with it, as described under "Storage Requirements: Tape gateway" here. And what blm14 would be getting for that cost is "low-latency access to data through transparent local caching". If I understand it correctly, that "transparent local caching" would be Amazon's tape gateway automatically deciding which files should be backed up onto local disk vs. backed up to the AWS cloud. Certainly that would be less work for blm14's organization than managing a disk-to-disk-to-(virtual) tape backup system, in which the decision of which files would remain on local disk would be left up to the grooming strategy. But would the organization really be served well, especially for less-than-catastrophic disaster recovery? There is also the question of cloud storage cost associated with Amazon's VTL. After an AWS S3 (and Google Cloud)-compatible cloud storage capability was introduced with Retrospect Windows 11, there was a distinct falling-off of interest after administrators discovered how much it would cost for a large installation to store data using it. Not surprisingly, Retrospect Windows 12.0 added a Backblaze B2 capability with a storage cost less than 20% of that of Amazon's. Moreover Retrospect Windows 12.5 certified Wasabi, a provider whose cloud storage costs are nearly as low as Backblaze B2's but which—unlike Backblaze B2—has API compatibility with AWS. blm14 certainly couldn't use Amazon's VTL with Backblaze B2; I don't know whether he/she could use it with Wasabi. P.S.: For those administrators who don't understand what blm14 is asking about, here is a video about the use of the Amazon VTL with another enterprise client-server backup application. I found it as a reference in the LAN/WAN/Cloud subsection of DovidBenAvraham's added section of the Wikipedia "Backup" article. My point in the second paragraph of this post about non-trivial hardware cost is briefly alluded to as "on-premise appliance" at minute:second 0:25 in the video. P.P.S.: Here is a more-detailed YouTube video about the use of a third client-server backup application with the AWS Storage Gateway VTL. If you look shortly after minute:second 3:50 in the video, you'll see it talks about an "unique inquiry string " that is coded into both this app and the one covered by the video in the preceding paragraph for use in the Medium Changer Type field of the Storage Gateway VTL. I'd suggest that blm14 ask Retrospect Sales (they'll undoubtedly check with Tech Support) if this "inquiry string" is an option in the Retrospect "backup server"; if it is then he/she can use it, if not then probably not.