derek500 Posted November 13, 2020 Report Share Posted November 13, 2020 Hello all, This is an informative post, I don't have a question. I wanted to share an issue I discovered with Multi Server 17.5.1.102 (17.5). We recently upgraded to this version and when I tried to restore files to one of my clients we received an error we hadn't seen before. The console appeared to complete the restore normally, and showed progress while retrieving our files, but then every restored file was 0KB in size. The Retrospect log showed an error of "File (filename) appears incomplete". I was able to reproduce this error from different backup sets and to different clients. I panicked, then tested a few different approaches to restoring and discovered that restores would only complete IF you restore to the server's local hard drive. This error only happens when restoring directly to a client. I contacted Retrospect support and opened an official case. Robin Mayoff replied quickly to let me know that they were aware of this issue and it was a high priority for them to fix. My options were to downgrade to 17.0.2 or wait for their fix to be released. I opted to wait, now knowing that this was the issue. Fortunately we don't need to do a lot of restores, so having to manually move my restored files isn't a dealbreaker. But if you are trying to do a restore directly to a client, you may be impacted by this bug in v17.5! Just putting it out there in case other people are searching for this issue like I was. Hope it's helpful! -Derek Quote Link to comment Share on other sites More sharing options...
sbeliever Posted November 13, 2020 Report Share Posted November 13, 2020 Yes, i have had nothing but issues with 17.5 thus far; crashes almost immediately, which we have never had before. I'm sticking with 17.0.2 for now as it has been very stable. Quote Link to comment Share on other sites More sharing options...
derek500 Posted November 13, 2020 Author Report Share Posted November 13, 2020 Hi, thanks for the reply. Interesting to hear that. We aren't having any other issues, overall 17.5 has been performing very well for us. This is the only issue I found. We upgraded to 17.5 from 15 which had it's share of issues, so far 17.5 has been a pleasant experience overall. It sounds like sticking with 17.0.2 is a good course of action for many until this issue is fixed. Quote Link to comment Share on other sites More sharing options...
mrogerson Posted November 29, 2020 Report Share Posted November 29, 2020 We had the same type of problem with a Duplicate script. All the files on the destination ended up Zero length and because of that every-time the script ran it deleted all the files and tried to replace them every time it ran. Also just downgraded to 17.0.2 and all is well again. Quote Link to comment Share on other sites More sharing options...
DavidHertzberg Posted December 26, 2020 Report Share Posted December 26, 2020 derek500, I just now looked at this thread, and then—because I knew there had been a Windows 17.5.2.103 release on 9 December 2020—checked the Retrospect Windows cumulative Release Notes. They list this for the release: Quote Windows Clients: Fixed issue where certain restores to Windows 7 resulted in "File appears incomplete" errors (#9134) Is that the bug you discovered? How about your bug, mrogerson; was the destination of your Duplicate also a "client"? sbeliever, There was an Engine bug fixed in the same release that sounds as if it might be yours: Quote Cloud Backup: Fixed rare crash for cloud uploads (#9082) Was it? everybody, There was another Engine bug—whose possible fix is discussed in this and the other posts in another thread, as well as a Linux Client bug fixed in the Windows 17.5.2.103 release; look at the cumulative Release Notes. Quote Link to comment Share on other sites More sharing options...
mrogerson Posted December 26, 2020 Report Share Posted December 26, 2020 2 hours ago, DavidHertzberg said: derek500, I just now looked at this thread, and then—because I knew there had been a Windows 17.5.2.103 release on 9 December 2020—looked at the Retrospect Windows cumulative Release Notes. It lists this: Is that the bug you discovered? How about your bug, mrogerson; was the destination of your Duplicate also a "client"? sbeliever, There was an Engine bug fixed in the same release that sounds as if it might be yours: Was it? everybody, There was another Engine bug, whose possible fix is discussed in this post's thread—as well as a Linux Client bug fixed in the Windows 17.5.2.103 release; look at the cumulative Release Notes. Just installed this update and tried the same Duplicate 'Replacing all contents' from the client to the Retro server machine. This time it works as it should. 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.