johnnymacgo

Yes, it does work. I'm running Windows Multi Server V16.1.2.102 and I was able to CTRL-Click more then one snapshot and it deleted/forgot them.

I updated Retrospect server to V15.6.0.302 on 11/7/2018 and haven't had that problem since.

Me too. Over the weekend I had the same type of freeze\hang with the console stuck at "Finding next-computer-to-backup". I'm running Retrospect for Windows Multi-Server V15.5.0.179 which I upgraded to last week. Before that I was running V15.1.2.100 for a while for no issues. It's on a Windows 2012 R2 server and the only thing that changed was the upgrade of Retrospect. The backup computer is running Windows 10 Pro 1803 64bit agent version V15.5.0.179.

Over the weekend I had the same type of freeze\hang with the console stuck at "Finding next-computer-to-backup". I'm running Retrospect for Windows Multi-Server V15.5.0.179 which I upgraded to last week. Before that I was running V15.1.2.100 for a while for no issues. It's on a Windows 2012 R2 server and the only thing that changed was the upgrade of Retrospect so I suspect its and issue with V15.5.0.179. The backup computer is running Windows 10 Pro 1803 64bit agent version V15.5.0.179.

Well since I started this thread back in 2010 I wanted to let everyone know that it looks like this feature is finally here! This is from the just released V15.5 release notes: FixedSnapshot: Allowed multiple snapshots to be selected for deletion (#7477) Yaa!

BTW, this problem has been fixed in Retrospect V12.1 for Windows.

Hi, You can download V11.5 from here: http://www.retrospect.com/en/support/downloads Your V11 license should work for V11.5. I did for me (I have MultiServer) Johnny Mac

Hi, Since I upgraded our Windows Retrospect Multi-Server from V10.5.0.110 to V11.0.1.106 I'm seeing the following error intermittently: stfiDoBackupOne: error -1101 (File/directory not found) on C:\Windows\wlansvc\Polices\. and 43,392 others stfiWaitForBackupDone: Operation terminated, (file/directory not found) Trouble reading files, Error -1101 (File/directory not found) 8/16/2016 8:11:52 PM: Trouble copying folders, error -1101 (file/directory not found) ddex=48,675 (I'd paste more info from the operation log but for some reason this forum won't let me paste) This problem is new to V11.0.1.106. It happens to different Windows backup clients at different times. It even started happening at another customers site! I logged a call with support and they said I was seeing those because I don't have the Open File Backup license. I find that hard to accept since we never had Open File backup before and never had that error before the upgrade. They also said I was the only one to report it but like I said, It's happening at two totally different customers. The Windows clients were also upgraded to V11.0.0(252). So the reason for this post... Is anybody else seeing this error? Thanks! John

Hi, I'm running Retrospect for Windows Multi Server V10.5 to two USB disks. Retrospect started crashing recently with an Assertion failure at "elem.cpp-1145" while backing up a Windows Laptop that was recently upgraded to Windows 10. I logged a call with Retrospect support. They had me rebuild the catalog file on the USB disk and that fixed it. I hope this saves you some time if you run into this, Johnny Mac

You don't say what version of Retrospect you are using. I use Retrospect for Windows V10.5 Multi-Server and I have already used that method. I had a client/laptop that the hard drive died on. I hooked my usb disk with the latest Retrospect backup on it directly to the laptop (that same disk also has the catalog on it). I then booted the laptop off of the DR CD and prepared the new disk on the laptop. Did a full disk restore. When the restore was done I removed the usb disk and the DR CD and the laptop booted off the newly restored boot disk just fine.

We have had a Dell TL4000 with a 48 library slots and an LT04 tape drive for 7 years and it was very reliable. We just bought a Dell TL2000 with 24 library slots and an LT06 tape drive and so far it's been running great. Both of these are SAS BTW.

Since upgrading from Windows Multi-Server V8.5 to V10.0.2.119 I have had multiple clients that were also upgraded to V10.0.2.119 bind to the wrong IP address (usually on our iSCSI SAN). Working with Retrospect support we finally found that you shouldn't use -ipsave but use /ipsave instead. So the full commands would look something like this: C:\Program Files (x86)\Retrospect\Retrospect Client>retroclient /ipsave 10.10.0.?? I didn't need to restart the Retrospect service. This created the following registry key: HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\Dantz\\Retrospect Client\\6.5\\BindListener This didn't happen to all clients with multiple IP, just some of them. I suspect that one's that worked wouldn't after a reboot until that registry key is created.

Thanks Robin. BTW, Windows 10 has been released in the US Lennart.

Hi, What version of Retrospect Server and Client support Windows 10 fully? Thanks, Johnny Mac

I ended up logging a support ticket with Retrospect to get some answers. Here is their response: Details on the new .xml file can be found at: http://www.retrospect.com/en/support/kb/migrating-from-bak-to-xml-configs Please make sure you are using the 10.0.2 version of Retrospect, since it contains bug fixes related to the .xml file. Yes, both of those files are being used by Retrospect 10. I am not sure when the user's guide will be updated. I will remind our documentation team that this is missing from the docs.