Jump to content

x509

Members
  • Content count

    99
  • Joined

  • Last visited

  • Days Won

    5

x509 last won the day on July 30 2017

x509 had the most liked content!

Community Reputation

17 Good

About x509

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am running the very latest Retrospect 15.6 (see, I did upgrade) on a Windows 10 Pro system with 32 GB of RAM. The CPU is a "Sandy Bridge" Intel 3930K model, six-core 3.2 GHz with 3.8 GHz Turbo Max. Not the latest generation, but a very respectful performer. This system has no problem with normal workloads for Photoshop or Lightroom. Yet, the Retrospect Dashboard is a terrible, simply awful performer on this system. It cripples my ability to run Retrospect to manage my backups. I have these issues: If I so much as click on the scroll bar on the right side of the Dashboard window, the entire Windows desktop dims for about 30-60 seconds. I can't seem to bring up the main Retrospect window using the Dashboard. Dashboard says that Retrospect is active, even at 9 am. All my scripted backups are scheduled to start after 9.30 pm. I don't see any way to simply stop the Dashboard. Every time I launch Retrospect the Dashboard starts. If the Dashboard has really hung up my system, say for 2 minutes, and I use Task Manager to kill that process, when I restart Retrospect, I get the ..... Dashboard. I once heard the term, "Error loop for life," and I think that applies to this behavior. The only reliable way to start Retrospect is to reboot my system, and start Retrospect right away. But once a backup runs, I'm stuck again with the Dashboard. I would like to go back to the simple Retrospect main window that I had with earlier versions of Retrospect. I'm just an advanced user running Professional with single-unit execution disk backup only. Depending on the day of the week, I run 3-5 backup scripts each evening. I don't need the kind of management that an IT professional requires when running Multi-Server with multiple execution units, with both disk and tape, dataset rotation, etc. So what can I do, aside from reverting back to something like Retrospect 6? x509
  2. I think the solution to this problem is to change the Drive ID or serial number, but I don't know how to do that. I seem to recall doing this change years ago. Here is my situation: I just had a complete failure of my Retrospect drive, which is Drive G: in my Windows 10 system. Right now I'm running Retrospect 12.6, but I'm planning to upgrade to the latest 15.x as soon as I can find some "quality time" for that project. I keep a "backup of the backup drive," which I keep offline. It is simply a copy of all the Retrospect folders and files. Unfortunately, the last time I did a backup of the backup drive was mid-August, but that's better than losing all of my 2018 backups. I do a fresh set of backup data sets every years. Even though I renamed that backup of the backup to "Backup 2018," which was the name of my original backup drive, and set it up as the same Drive G:, Retrospect says that it can't find any backup sets of that volume. So how do I fix this situation?
  3. I was just trying to start Retrospect Professional (v12.6) and I got this error message. Does Retrospect still have some 16-bit code? I'm running Windows 10 Pro 64.
  4. x509

    Error -1103 after Windows 10 April Update

    I know this is an old thread, but I wanted to post my experience. The 1803 upgrade was forced on me about 10 days ago, on my server machine and one of the LAN clients. Another client still hasn't been force-upgraded yet. I'm still on Retro 12.6.1, still need to upgrade to 15. I'm running Win 10 Pro 64 on all three systems. Since the upgrade on the server system I have run multiple Retrospect backup operations every night. I back up my C drive, which has Windows and programs installed, as well as various other drives with various kinds of data files, on different schedules. I've also run several grooming operations, optimizing for storage. No problems, no error messages, nothing out of the ordinary. x509
  5. MrPete, I really appreciate your efforts here.
  6. The newer systems are all UEFI/GPT with UEFI boot. the older systems are MBR with BIOS boot. One of the UEFI/GPT systems is the Retrospect (Professional) server. So I think you're saying that I would need at least two DRDs. Do I need a different DRD for clients and the server system? In all cases, I would want to restore to the existing hardware, so changes in partition sizes is not an issue. I recently had a "scare" where I thought I had lost my system, so that I want to prepare DRDs before I really need them. A few months ago, I did a test restore of one of the clients by first installing Windows, then doing the restore, but that didn't quite work, and I'm not sure why. I suspect it was some kind of permissions issue. I'm assuming that the DRD method is more foolproof if disk partitions are unchanged. Thanks for the clarification about restore to "dissimilar hardware." x509
  7. I have five different Windows 10 Pro 64 desktops and laptops in my home LAN. All are based on Intel CPUs, and three of them are Lenovo laptops of different generations. Should I create DRDs for each individual system, or can I use just one DRD? Is the "restore to dissimilar hardware" feature an issue here?
  8. I currently am using Retrospect 12.6.101, but I am planning to upgrade to 15 when I "free up from other things." Right now I have a need to do a bare metal restore on a Windows 10 Pro 64 system. The manual for Retrospect 12 talks about support for Windows 8 and 8.1 and the Microsoft ADK. Is it safe to use a Disaster Recovery Disk created with Retrospect 12, or should I first upgrade to Retrospect 15?
  9. In my previous message, I explained that I had to redo the PROGRAMS dataset from scratch, because of corruption with the old dataset. Client APH was the first system to be backed up. I'm not sure why this communication problem occurred (because the Power Plan was ALWAYS ON), but the backup log included these lines:
  10. Reviving an old thread. I have a multi-boot desktop system, but it's multiple installs of Windows 10, and no Linux (so far). Steve, how did you configure Retrospect so that it would backup changes to your Linux partition? If it matters, the disk holding the multiple installs is UEFI/GPT based. x509
  11. David, This approach does sound nice, but I am still on Retro V.12 (Windows). My plate is way filled right now, so I was planning to do the upgrade to 15 probably in mid-July. Believe me, with the 1803 update from Microsoft, it's knd of urgent that I uprade to V.15. About EU and GDPR. Even though I live in the USA, I'm sure that I will benefit at least somewhat to the GDPR, and that's a good thing. /rant Here in the USA, users are treated only as commodities, as revenue sources, and to the devil with issues like data privacy or security breaches. When Equifax announced that they had been breached and all the data of 143 million Americans (almost half the total population of the USA), had been stolen, including Social Security numbers, there was some grumbling,. But no executive has been charged criminally, the company hasn't been fined to the tune of multiple billions, and life goes on as if nothing had happened. Or we can talk about the corporate strategy for disregard of user privacy at Facebook. Willful disregard. And aside from some handwringing and a few critical blogs and such, nothing has happened to them, Zuckerberg completely snowed Congress in his testimony and no one has called him out. rant/ x509
  12. Thanks all. To retrieve files from the actual tapes, I have to rehab a really old machine that has SCSI support, etc. Probably in July.
  13. While doing the Grooming operation that Scillonian recommended to me recently, my Win 10 Pro system blue-screened (very rare) such that the backup set was corrupted. So I deleted it and restarted the PROGRAMS script with a fresh copy of the dataset. LAN client APH was the first sytem to be backed up. Retrospect Server APH was the second system to be backed up. Note that here, the UEFI system partition was also backed up, but was not backed up for client APH. Do I need to change any configuration parameters? I assume that without UEFI System partition being backed up, I could not do a full restore of the client. Is this correct? x509
  14. Done. Is there any way to delete just selected files or folders within a snapshot or session?
×