Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Reply to DavidHertzberg: I only installed "HPE OpenStore Standalone" to confirm that it recognized the tape drive and worked (because Retrospect was not working). I do not intend to use it. Re Lennart-T: I tried your suggestion and disabled the device, but with no improvement. The really frustrating things is that it was working on this machine before. I thought perhaps the problem was related to antivirus software (Eset NOD32) so I disabled that completely - but Retrospect still does not find the tape device. It really puzzles me what Retrospect is doing, because my other tape utilities and backup applications can see and use the connected Ultrium 3000 drive, just not Retrospect 11.5. Andy
  3. Years ago, with an older Retrospect, an older Windows and an older LTO drive, the solution was to disable the tape station (and loader) in Windows Device Manager. That way Retrospect was able to find and use the LTO drive and loader. Hope this (still) helps.
  4. 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?
  5. Last week
  6. Retrospect 11.5 under Windows 10, 64 bit does not find my LTO-5, HP Ultrium 3000 drive. Windows 10 is up-to-date. The hardware is an HP Z620 workstation with an LSI 9207-8e HBA. The HBA and tape drive show up in Windows Device Manager. The tape drive is also identified quickly by "HP Library and Tape Tools" and passes all tests. Since having the problem with Retrospect I installed the "HPE OpenStore Standalone" LTFS application as a test. It also picks up the tape drive immediately without any difficulties. I have re-installed Retrospect several times and under the Configure/Devices, Environment tab, I have "refreshed" devices numerous times, but no improvement. In the past, Retrospect was finding the drive (although intermittently) but it is now a consistent fail. I previously was using an LSI-9200-8e HBA and had the same problem so I upgraded to the 9207-8e, but it has made no difference. This seems to be a Retrospect problem specifically, because it is only Retrospect that cannot find the drive. Help, please. Andy
  7. Error scanning network 1116

    Hi Scillonian, Thanks for your response. Typing in the UNC path works a treat so at least i can now add new sources to the backup script. Good to know i can use a virtual machine. No doubt i will utilize that in the near future.
  8. Backup to AWS

    Hi David, First of all sorry false-quote post. This post auto saved the quote option and then I filled information without seeing that... I will read docs, thank you
  9. 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.
  10. Error scanning network 1116

    Retrospect will run successfully in a virtual machine. For many years I successfully ran Retrospect in a VMware Workstation virtual machine. Do you have both IPv4 and IPv6 enabled on your network? I have come across instances where you can browse the local network over IPv6 but not over IPv4. This is not a problem for applications that are IPv6 aware but for applications that are IPv4 only, such as Retrospect, any attempt to browse the network from that application will fail. Personally I gave up on trying to browse the 'Microsoft Windows Network' years ago because it so very rarely worked and instead enter the UNC for the desired Source using the 'Advanced...' button.
  11. 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).
  12. Backup to AWS

    Hello People, I need to configure AWS for cloud backup with retrospect but the options aren't available. Could be this is a trial version? (Check attachments)
  13. Error scanning network 1116

    Hi David Hertzburg, Yes I have already extensively searched the forum and can't find anything to resolve this particular issue. Its difficult to nail down the problem when the error is so generic. I am running this particular instance of Retrospect on a server that is also a domain controller. Would that potentially cause issues within Retrospect? I know it tends to be a no go for a lot of software. Can the retrospect server be run on a virtual machine? That may be my easiest current option if the domain controller is best left alone.
  14. 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.
  15. I haven't been able to get email notifications from Retrospect lately. In my efforts to troubleshoot the problem, I changed "Networking" from 3 to 7 in Secret Preferences. The operations report has the following log entries: performClientHandshake: begining handshake performClientHandshake: sending token received from InitializeSecurityContextW doClientHandshakeLoop: scRet error after InitializeSecurityContextW, 0x90320 E-mail notification failed: error -592 (invalid response from SMTP server) I can't find any information about what this means in Retrospect. I have found in some unrelated forums that error 0x90320 typically signifies an invalid Client Authentication certificate, but I do not know how that would apply to Retrospect. I first started having problems when my ISP rolled out a new email server, and I was unable to send messages from any applications for more than a month. That has been resolved, except that I am still having trouble with Retrospect notifications. The only setting I have changed in Retrospect is the email password. I am using Retrospect Desktop for Windows version, running on Windows 10. My outgoing mail server is set to smtp.windstream.net:465. I have checked the boxes for "My outgoing server requires authentication" and "My outgoing server supports SSL." These are consistent with the settings I use to send email from other email clients (Thunderbird, and my cell phone email). If I uncheck either of these options I get an error 519 (Network communication failed) when I try to send a test message. I have tried contacting the ISP and they could not help. They claimed the problem had to be with Retrospect since other email clients are able to send messages. Any suggestions on how to proceed from here with troubleshooting?
  16. Restore to a different folder

    Thank you Lennart for your help Alan
  17. Restore to a different folder

    When you restore "files and folders", you can only select the destination volume. The restore will be placed in a new folder on that volume and the folder will be named after the backup set name. In your case: C:\BackupSetName\Folder1\Contents of folder1 After the restore is finished, you can (in Windows Explorer) create C:\Folder5. Then move the restored files there and finally delete the (now) empty folders C:\BackupSetName\Folder1
  18. 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.
  19. Restore to a different folder

    Hi, I would like to restore to a different drive and folder. Restore files and folders from "Folder1" that was backed up with the complete "D" drive To destination "C" drive "Folder5". When the backup is complete I would like to have C:\Folder5\Contents of Folder1 Thanks Alan
  20. Earlier
  21. 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).
  22. 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?
  23. I find that Retrospect sometimes gives a -530 error after having been successful for months and that I can get going again by forgetting and then adding the client again at the server end. A nuisance. There is no change of IP address involved since all of the addresses are statically assigned. I also have clients where the boot partition shows up but not the other partition until I re-install
  24. I use Chrome Remote Desktop between Macs from home to work
  25. This will not work where Retrospect.exe is launched by the Retrospect Launcher service. From Windows Vista onward applications that run as a Windows Service, and any application(s) that they may launch, are not allowed to have* a GUI. (*Although it is the same Retrospect.exe that has GUI functionality when launched by a user, that functionality is disabled/suppressed when it is launched by the Retrospect Launcher service.) Applications that run as a Windows Service from Windows Vista onward are also not allowed to interact directly with a user. This is why dashboard.exe exists in Retrospect for Windows to allow indirect user interaction with Retrospect.exe when it has been launched by the Retrospect Launcher service. (I don't know if dashboard.exe communicates directly with Retrospect.exe or through the Retrospect Launcher service.)
  26. Duplicate always erases all files first

    This could be because you are duplicating the files from the Windows NTFS file system to macOS HFS+ or APFS file system. There are attributes on NTFS which do not exist on HFS+/APFS that will have to be emulated such as file and folder security information. If you are only interested in the file contents and not the security information you could try disabling the duplication of the file and folder security information in the Duplicate script. From the Duplicate script's Edit dialog select Options > Windows > Security and deselect the file and folder security options.
  27. 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.
  1. Load more activity