Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


x509 last won the day on July 3

x509 had the most liked content!

Community Reputation

21 Excellent

About x509

  • Rank

Recent Profile Visitors

566 profile views
  1. What did I end up doing? Funny you should ask. After a few go-arounds with restoring files and folders, I gave up and did a new Windows install, which means lots of Windows configuration, and then installing a boatload of programs, which of course also need configuration. Fortunately, I keep my data files in different partitions than Windows and programs, so all that was OK. I also wrote a strong letter to a Retrospect C-level manager, at the encouragement of people in this forum. I got back a response which said, paraphrasing: You did that restore wrong. You should have used a Recovery Media restore. Too late. Right now, as we speak, I'm trying to restore a laptop, and this time I am using Recovery Media. I dutifully followed the directions in the manual, and got a USB Recovery drive. But, but, but (and with Retrospect, there is often a but.) On thjs laptop, the Recovery Media windows are too tall to be displayed completely on the laptop's screen. ( On two different desktops, and a different laptop, there is no such issue.) This thread describes the issue: And this thread on a different forum explores a solution. I haven't finished the process of isolating the driver in question, listed in message #6. I will possibly get to that work today. https://www.tenforums.com/drivers-hardware/142045-need-nvidia-driver-laptop-needs-recovery-media-restore-how.html I'll keep everyone posted.
  2. True, but the Retrospect 16 manual includes these paragraph, which I think was inspired by my support issue from earlier this year. These paragraphs appear at the very start of the Disaster Recovery Chapter:
  3. MrPete, In the interest of history. If I remember correctly, the "Multics" system at MIT when I was a grad student there was a Honeywell 635 system with virtual memory. I worked at Shugart Associates during the time that they started to build low-cost "Winchester" drives, all modeled after some IBM drive that had sealed head-disk assemblies. Thanks to a very friendly salesperson, I "got" a customer sample SA 1004, which was an 8" HDD with all of 10 MB. I hooked it up to my CP/M system, and it was like a whole new world, compared with the typical dual-floppy system. Shugart Associates was late to the 5 1/4" HDD market, and they went out of business a few years later; fortunately I had left by then. But while it lasted, it was a great time.
  4. There are so many, many frustrations in using Retrospect. Why do I (or anyone else) stick with it? This client not found issue seems like a self-inflicted wound.
  5. I solved my own problem. 😲 In the Client Windows, I selected the Access tab and then clicked on the Direct button. Then I entered the client's TCP/IP address. It worked. Lesson learned.
  6. This post is not about Retrospect, but I'm posting this in case anyone here who is a system admin or network admin runs into this problem with updating a Lenovo BIOS. If you have recent my recent postings, you may know that a Retrospect support engineer recently asked me to update the UEFI BIOS in my Lenovo T 560 laptop. He even gave me the exact link for the page for BIOS updates for my machine. (Kudos to Marc!) Since Windows is not running on the laptop, I download the ISO file which would be used for a CD or USB boot, to run the BIOS update. It turns out that an ISO file isn't really an ISO file where Lenovo is concerned. I could not create a bootable USB drive using that ISO file using Rufus, a standard tool for this purpose. Yesterday I spent well over one hour, on hold and talking to five separate people to ask for help or some workaround with the ISO file. The final answer was, "Since you machine is out of warranty, we won't help you, and NO!, you can't talk to a supervisor." This is incredible. I never heard of a hardware vendor who effectively limits BIOS update support to the one-year warranty period for the system. After that I posted to a Lenovo forum, and almost immediately a very help guy posted a response, giving me a link to another thread, which explained in detail how to use the Windows executable running on a different system to create a bootable USB. https://forums.lenovo.com/t5/Other-Linux-Discussions/Update-ThinkPad-BIOS-with-bootable-flash-drive/ta-p/3743440. Once I followed this procedure, I was able to update the BIOS without incident. x509
  7. 10 days ago, Retrosect suddenly could no longer connect with client "LENOVO730." No changes in the home LAN, which is a Windows workgroup, other than normal Windows background updates. I just verified that the client on LENOVO730 is active. I can ping the client by name in a Windows cmd-box. In Retrospect, I did a TEST in the Network Access window and got this result: So Retrospect Desktop has detected the client at its correct IP address. But right after I got this result, I clicked on the Refresh button for Lenovo730 Client properties. I don't know if this is a Retrospect issue or a Windows issue. I've been using Windows networking since the Windows for Workgroups 3.11 days, and I think that networking issues are responsible for the vast majority of issues on systems in my home LAN. If you go to this forum, https://www.tenforums.com/network-sharing there are endless threads about Windows networking issues with missing clients, missing network shares, etc., etc. So I don't know where the issue lies. Are there any additional steps I can take to rule out a Retrospect issue?
  8. I have to say that Retrospect support has been quick and helpful. I got a quick response from Robin Mayoff and then when I replied with my issue about window size, I got a quick and very helpful response from a support engineer. His recommendation was to update my laptop's BIOS, which I did, but the window size problem remains.
  9. The last thing I want to do is reformat my laptop's SSD, because then I have to do a full reload of Windows and applications. Probably two days worth of work. Nigel, David, and everyone else. I figured out the issues, mostly, and I'm gobsmacked. (https://www.merriam-webster.com/dictionary/gobsmacked ) Just for grins, I booted up my desktop system using that recovery media. It all worked as far as I took the process, because I don't need to recovery anything to the desktop system. It all worked because that Welcome screen had NEXT and FINISH buttons at the very bottom of the Welcome window. On my laptop, that same Welcome window is too tall to fit in the laptop display. It's a fixed size and cannot be dragged up, so as to show the bottom of the window. 😱 So the issue is that Retrospect made that Welcome window too tall. Truly a Whiskey-Tango-Foxtrot moment. So I replied to the support thread about my recovery media issue to explain this situation. That reply was late in the day, so I guess I'll need to wait for a day or two to get a response. I am just astounded that a silly issue like screen height is preventing me from doing a full restore.
  10. The laptop does boot a Windows image, specifically the update for release 1809. And I can go through various trouble-shooting options so that I can get a command prompt. I ran bootrec /rebuildBCD, which detected 0 windows partitions. In fact, there are two, since I multi-boot between my "production" installation and a scratch partition which I use for test installs, tryouts, etc. In that cmd window, I can do dir for drives C and D. Only those drives contain data, and the two Windows partitions are not detected. That has me concerned. Of course, once I get this recovery media issue straightened out, i'll just restore the System Reserved partition, plus the two Windows partitions. I submitted a bug report to Retrospect this morning, and even though I did not buy ASM, I got a quick and helpful response from Robin Mayoff, which I do appreciate. His comment was that there was a probable problem with the Media Recovery drive. I still need to work through the issues with Robin.
  11. David, I want to restore a system to itself. How is that "dissimilar" hardware, except by a tortured reading of the English language? If you are right, how am I supposed to create a recovery media on a client? More, that approach is hardly scaleable. I'm going to file a support case with Retrospect. The media creation process did not run smoothly. I had to COPY file copype.cmd file from a subdirectory of the Windows Assessment and Deployment Kit into the main directory for the Windows Assessment and Deployment Kit. Then the media creation process proceeded automatically. So I'm wondering if the media creation process somehow left off some additional programs, and if I could manually add those programs to the recovery media. I just filed a support case.
  12. I had assumed since all my systems are running Win 64 Pro on Intel CPUs, that one recovery disk would be suitable for all my systems. Apparently not.
  13. So earlier today, I had a laptop go completely south, well past the Equator, I might say. My only hope is a Retrospect recovery. So I followed the instructions starting on p. 316 of the Retrospect 16 manual, and I ended up with a recovery program on a USB drive. (The manual is out of date about the media creation process. Read carefully p. 316-317, and look at the screen shots.) I used the newly created USB Recovery Media to boot up the problem laptop. All I got was a Welcome screen with a checkbox at the bottom left. 20 minutes after I checked that box, I still don't see this window: So what do I do? I really need this laptop working again. start rant: I feel like I have again been made an involuntary, unpaid member of Retrospect's Quality Assurance team. end rant. x509
  14. Since my home LAN is not exactly a "larger organization," I certainly won't be paying for it. I have managed to work around the issue of the completely non-responsive console. Not pretty, but it has the benefit of being simple and effective.
  15. x509

    Dissimilar Hardware Restore

    Noel, I have the impression that even without this extra cost option, you can restore to "moderately" dissimilar hardware. Windows 10 apparently has advanced capabilities for re configuring itself if you move a Windows install to a new system. I suspect that Windows has no problem if you are doing an Intel-to-Intel or AMD-to-AMD move, as long as the target hardware is same or newer generation than the source hardware. It's worth a try before you shell out all that extra money. I am editing this message to add the point that "moving" a Windows install sometimes means installing a new motherboard. On this website, you can see lots of threads where people discuss how they can replace their motherboard without doing a fresh install of Windows: https://www.tenforums.com/ x509