Jump to content

DavidHertzberg

Members
  • Content count

    539
  • Joined

  • Last visited

  • Days Won

    18

DavidHertzberg last won the day on December 9 2017

DavidHertzberg had the most liked content!

Community Reputation

30 Excellent

About DavidHertzberg

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
    Male
  • Location
    New York, NY
  • Interests
    Retired applications programmer, with a few Macs at home.

Recent Profile Visitors

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

    afripp, Have you installed the May 2013 firmware update for your LTO-5 HP Ultrium 3000 tape drive? If you haven't, I'm not sure where you can get it, because of the HP-HPE split. There's also this, but I'm not sure it applies to your tape drive.
  2. "Completing restore" won't quit

    drtomblinn, You don't say what version of Retrospect Mac you are running on your "backup server", nor what version of macOS you are running it under on your "backup server" or your "client". However, if you want to submit a Retrospect Inc. Support Case for your bug, here is why and how to do so.
  3. x509, Actually I'm pretty sure you can eliminate the repeated Restore runs mostly by using the Retrieve Just Files option on page 123 in the Retrospect Windows 12 User's Guide, combined with "Specifying the Search Criteria" on page 124. I did a Restore test after I wrote the preceding post this morning, followed by another test just now. The tests were on my Mac Pro "backup server", but what I did seems equivalent—although the Retrospect Mac GUI is a bit different. The trick will be to specify the file name, but then to click the More Choices button in the dialog. This will enable you to create a custom Selector, as described on pages 456-464 of the UG. Pay most attention to "Universal Selector Conditions" on page 462, which will tell you you can specify Size. If the custom Selector replaces the specification of Name on page 124, then your custom Selector will also have to specify Name as part of the custom Selector—and combine the Name and Size with And as described on pages 464-465.
  4. x509, I'm going to assume that you at least know the name of the corrupted 66MB file. You should first watch this YouTube tutorial, called "Using Find Files to Restore Data with Retrospect for Windows", which will tell you how to select only the file with the specific name you want. Then you have two options, depending on whether you know the date of the last good backup of that file. If you don't know that date and don't trust Retrospect, then IMHO what you should do is to repeatedly run Restore->Find Files—always specifying the file name and selecting on each run a single last backup date that is earlier than the one you restored on the preceding run. After each run, look in the folder created by the Retrospect restore at the size of the file you just restored to see if it is 1KB or 66MB. If it's 66MB, then you've just restored the last un-corrupted backup of the file—and you can move that restored version to replace the corrupted version. The fourth paragraph of this post by the very-knowledgeable twickland alludes to this procedure, and also mourns the loss in Retrospect Mac of an earlier facility that would have eliminated the need for repeated Restore runs. But you are running Retrospect Windows, and IMHO still have this facility. If you do know the date of the last good backup of that file or if you trust Retrospect's reporting of file sizes, then you can get fancy in order to eliminate the repeated Restore runs. Read pages 451-454 in the Retrospect Windows 12 User's Guide, and specify the name of your corrupted file and the size or date of the un-corrupted version. Then you should be able to build a custom Selector that will allow you to make a single Immediate Restore run, or simply checkmark the latest backed-up version with the desired size and Restore that version.
  5. Backup to AWS

    ggirao, I think I owe you a bit of an apology over my reaction to your first post in this thread. I now believe that you really meant to write "Could be because [my emphasis] this is a trial version?", and you simply left out the word "because" as a result of what I presume is your unfamiliarity with English. So you knew you were working with a trial license of Retrospect Mac, and meant to say that, so I shouldn't have devoted a paragraph telling you how to find that out. However this is an introduction to my telling you that, as an experiment, I tried to create a Cloud Media Set on my own non-trial copy of the Retrospect 14.6 "backup server" earlier this morning. The Cloud option in the drop-down menu was not greyed-out, even though I had not first set up an Amazon S3 account (I have never used Cloud backup, because my upload speed is too slow). So it now looks as if there is in fact a "feature" in trial-license copies of Retrospect Mac 14.6 that stops the user from setting up a Cloud Media Set. My guess is that the Retrospect Inc. engineers didn't tell Werner, who is the head of Retrospect Sales, about this "feature" because they didn't think that any sane administrator would go to the trouble of setting up an AWS S3 account while having only a trial license for Retrospect Mac. I should have double-checked what Werner told me, because as a retired applications programmer I should know that programmers frequently have trouble imagining what application users might do. So I owe you an apology for believing that a salesperson had the full facts, without first having done a test myself. My suggestion now is that you telephone Retrospect Support at 00-31-207-219-220, explain that you are trying to test Cloud backup and ran into a problem with having only a trial license, and find out if you can buy a permanent license for Retrospect Mac 14 but still get your money back if you discover in less than 45 days that it just isn't what you need.
  6. 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?
  7. 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.
  8. 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).
  9. 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.
  10. 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.
  11. 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).
  12. 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?
  13. 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.
  14. 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.
  15. 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?
×