Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


x509 last won the day on December 11 2019

x509 had the most liked content!

Community Reputation

22 Excellent

About x509

  • Rank

Recent Profile Visitors

706 profile views
  1. David's story is interesting. Prior to using Retrospect, I also had a "fling" with Backup Exec. Prior to doing disk-to-disk backup, I went through QIC-tape and then DAT tape backup machines. But LTO tape drives cost more than a so-so used car, and the tapes are darn expensive, so I "embraced the inevitable" and went to disk-to-disk backup. I do use a separate backup drive for each year, for the cost of maybe 2-3 LTO tape cartridges. That Ars Technica poster is a damn fool. Maybe he will be OK, and maybe he won't. At the time we got that Lenovo laptop for my wife, I was extremely pressed for time. For about $60, I got a Laplink utility that essentially migrated all the programs and config settings from the old system to the new one. From experience, that's 2 full day process.
  2. Replying to several recent posts, I run backups late evening, after we are both finished "working" (if that's the word when people are retired ...) so my wife isn't doing anything funky. In any case, I'm the "IT guy" in this marriage. Not that I could get a real job doing IT admin, but I have sufficient skills to (mostly) keep the home LAN and its systems in good order. However, I believe that the Lenovo bloatware on her system, client "L" may be the problem. I keep deleting it or stopping those services, and like a weed, they keep coming back. On client "D", which is also a Lenovo machine, it started life out with Windows 7 and then got upgraded to Windows 10. But that was a clean install, using a retail copy of Windows, not a Lenovo OEM install. I probably should have done the same with my wife's system when it was new, but too much time has passed now. Agree about needing to figure out the underlying problem. That said, it's frustrating that I simply can't restart the Retrospect client, that I need to do a reboot.
  3. Yes, client "L" is a system with name Lenovo730. It's my wife's system and she chose that name. My other laptop client is also a Lenovo T-series, with a name starting with "D." I would like a solution that doesn't require constant maintenance. I'm not quite there yet. x509
  4. Since the client in question is a windows machine I can't run "sudo." However, I have never given any attention to scripts. Right now, I look at the History tab, and if I see error messages, that's an indication of a problem or issue. I like the scripts idea, though.
  5. That's usually a temporary "lock" file that isn't being cleared. Killing processes won't do it, but you can manually delete it or reboot (which generally clears temp files). My Windows troubleshooting can be summed up as "turn it off and on again", so I reckon you did the right thing 🙂 -- but maybe MrPete will chip in at this point? --------- Nigel, I think Occam's Razor applies here. The idea of a lock file being present is a lot simpler than all the energy around IP addresses. In any case, if I knew what lock file to delete (or even how to find it), I would just set up a daily script to delete that file. As things stand now, I have to inspect Retrospect logs to see when my client "L" is not being backed up.
  6. After futzing around for a while, and then futzing around some more, I think I discovered the issue that I'm having, and it's only on one of two laptop clients. Retrospect client status is OFF, and there is no way for the client to turn itself back on. How is that? So I used Windows Task Manager to shut down all Retrospect tasks. Then I ran the main Retro client program again. No luck. The ONLY way to get the Retrospect Client to be ON was to reboot Windows. Note that I have two laptop clients, both running Windows 10 but Retrospect client operation on the second machine has been problem-free. I'm currently running the last version of Retrospect 16 on both the main system and clients. x509
  7. Ignoring the two spam messages by this newcomer, I have read through this thread, and just thrown up my hands. I have not been to this forum because of distractions for other important issues ( but I don't have Covid-19 !!). So I'm going to pay The Man for the V17 upgrade, try to see if subnet detection works (or not) and then file a support case. About a month ago, I slowly, somewhat painfully edited my router's IP address assignment table so that all devices on the LAN now have assigned IP addresses. But that is a band-aid, and could get problematic to manage if I add an Access Point to to the home Wi-Fi to deal with recent performance issues. Honestly, I've had to devise several band-aids around managed scripts. I know I'm only a home user, small potatoes, but Retrospect, or whatever they call themselves these days, should stand behind their product. Also just wondering if anyone has had any experience with Drobo NAS systems? In various forums, Drobo is hardly ever mentioned, and everyone seems in love with Synology.
  8. rjafman, Can you post this script. Thanks.
  9. I can't offer you any suggestions, but I'd like to describe a problem that I had when I tried to create a recovery USB drive for my laptop. The Retrospect windows that control the creation of the recovery USB are simply too tall to fit within the WinPE environment. it has everything to do with the native display parameters of my laptop, which is a Lenovo T560. If anyone has any suggestions, I would appreciate them.
  10. Last night, clients suddenly were NOT being backed up. Had I changed any network settings? No. Had there been a Windows update? I don't think so, because I configure updates to be run manually. So I checked all the Windows networking settings. Everything looked good. I checked the clients via Windows networking. Yup, they were both there. So what is Retrospect's problem here? As an experiment, I tried to ADD a new client. Same error message. So the issue isn't on the client side. In desperation, did a search on the Retrospect Knowledge Base and found this article https://www.retrospect.com/au/support/kb/error_code_table#stq= backup client%3A network interface unavailable&stp=4 So I clicked on the Interfaces button on one of the clients. I was using the default of course, and the current IP address of the interface was correct. So I played around with the various settings for the Default Interface, but didn't actually save any changes. Holy tape drives, Batman. Now the clients are being backed up. x509
  11. This thread, plus some of the weird things Windows updates does to network settings, probably explains why there is such grief around Windows networking. Way back in the 1980s, I was a product manager for networking protocols and stacks. That was before TCP/IP took over the world. Aside from LAN protocols, I dealt with SNA and DECNet, also oddballs like Banyan Vines. Thinking back on those days, I can't imagine what i was thinking. When TCP/IP became the One Protocol To Rule Them All, and Microsoft aligned its LAN networking around TCP/IP, life was supposed to get better. I must have been smoking some strong stuff back then. I like the belt and braces approach above.
  12. Since I personally don't have scripting skills beyond Windows CMD files, and not very good even at that a fixed IP for all clients (as David suggests) is probably the best approach for me. Right now, I'm busy with covid projects from my wife for fixing up things around the house, but I will get into my router's IP assignments table soon enough. To reprise an earlier comment, networking is the weakest part of Windows 10, since there is no one screen or set of screens to control all the entire TCP/IP stack or all the processes that can affect networking. Add to that the ways that a Windows update can silently reset some settings, and I spend way too much time on this issue. Retrospect client discovery is only one relatively small aspect of the overall issue. In my humble home LAN, all Retrospect clients and the server are wireless. One less issue.
  13. x509

    Retrospect 17 and low-end users

    If there were improvements in the UI of the client, as well as its performance, then I would have a solid reason to upgrade now. Otherwise I'll wait until 17.1 or 17.5, whatever its called. Any idea of when that upgrade might be released?
  14. In the Norton firewall, I added a rule for Port 497, for both TCP and UDP. Didn't fix the problem. Neither Configure -> Devices method discovered the clients. To respond to your point above, the Norton firewall has a concept of "trusted" networks devices. But as you say, Windows is notorious for changing network status in multiple ways. Sometimes after updates, sometimes for no apparent reason. Networking is to me, the biggest single source of grief and unwanted maintenance work in Windows. Perhaps PC networking works much better in a domain with an Active Directory server, but home networking is a hot mess. It's much easier to throw in the towel and use Direct IP Addresses for clients.
  15. Please see next message. This forum doesn't have the same reply formatting flexibilty as others.