Jump to content

Search the Community

Showing results for tags 'Disaster recovery'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 12 results

  1. I replaced the motherboard, CPU, and RAM in my Windows 10 PC and I'm having trouble restoring the C drive from a NAS backup using Retrospect 18.1. The first problem was that with the old motherboard, I was using the legacy BIOS mode with MBR disks, and now with the new motherboard (ASRock Z590 Taichi) I want to use UEFI with GPT disks. The second problem is that the C drive was actually a RAID-1 mirror with two 500 GB SATA SSD drives (not m.2). After several attempts before understanding the first problem, I lost the data on the RAID volume. But I created a full backup of it on a NAS drive a couple of days ago, before upgrading the motherboard. To convert the two SSD drives from MBR to GPT, I found that the easiest way was to install Windows 10 on each of them separately, and it takes care of it as well as creating the reserved and system partitions. Next, I set the motherboard to disable CSM and Fast Boot, and changed the SATA Mode from AHCI to RAID (actually "Intel RST Premium With Intel Optane System Acceleration (RAID Mode)"). I then created the RAID-1 volume with the two SSD drives. My plan was to then restore the whole C drive back to the RAID volume. That's when the problems with Retrospect started. I booted from a Retrospect Disaster Recovery USB drive but it didn't see any of the local hard drives (neither the RAID volume nor the 3 other non-RAID SATA drives). It only saw the X drive and the 32 GB USB drive with WinPE. I also tried having Retrospect load the Intel Rapid Storage Technology driver that came with the motherboard, and it loaded ok but it still wasn't able to see the local hard drives. (Side note: Retrospect DR isn't able to load drivers from folders that contain spaces in the name. It returns an error for each individual word in the folder name.) To get it to see the local drives, I had to change the SATA Mode back to AHCI. But of course then I lost the RAID volume again. After multiple failed attempts at various things, I got the idea to leave CSM disabled but set the SATA Mode to AHCI (for Retrospect DR), install Windows 10 on each of the SSD drives (to setup GPT and the partitions), and then use Retrospect DR to restore the whole C drive back to each of the two SSD drives individually. My thinking was that if that worked, I could then switch the SATA Mode to RAID and create the RAID-1 volume again. However, when I tried to do the restore using the DR drive, it started by deleting the files that didn't need to be there, and then it just stopped the restore process without copying any of the files that needed to be restored. The history didn't explain why, but it showed 1 error: "The system state could not be restored": So instead of using the Retrospect DR drive, I decided to just boot into Windows 10 from one of the other non-RAID drives, install Retrospect, and do the restore from there. I remembered that you can't restore the C drive while you're booted off of it, but in this case I was booted off of a different drive. I set the SATA Mode back to RAID, created the RAID-1 volume, and then used Retrospect in Windows to do the restore to that volume. It copied all the files, but then ended with the same error above, saying the System State couldn't be restored. When I try to boot the restored volume, it gives a blue screen error 0xc000000e saying, "A required device isn't connected or can't be accessed". So now I'm stuck. Question 1: What's the best way to convert an MBR drive to GPT, and get all the partitions setup correctly? Question 2: When I create the RAID-1 volume in the UEFI settings, how much of the two SSD drives have to be identical first? Can I just have data on one of them, and it'll copy it to the other drive? If so, which one is the parent? Or will it even keep the existing data? Question 3: Why isn't Retrospect restoring the System State? I have a perfectly good backup of the entire C volume but I can't restore it, either while booted off a different Windows drive, or from the DR drive. Thanks! Russell
  2. I have Retrospect for Windows Desktop with Dissimilar Hardware Restore. Up to now, I have been backing up the computer running Desktop and two clients to four hard disks, in rotation. Now I have gotten a new machine and want to restore the operating system and data files from one of the old machines to the new machine. The old machine has a 1 TB SSD, partitioned with two volumes, one for the operating system and one for data, plus, of course, the UEFI system and the recovery partitions. The new machine has two SSDs: 1 TB for data (replacing the OEM hard disk) and 512 GB for the operating system (replacing the OEM SSD). The 1 TB SSD currently has the original operating system on it (copied from the OEM SSD by Samsung migration software). The 512 GB SSD is empty, except for being partitioned and formatted. The UEFI system and the recovery partitions were copied from the 1 TB SSD. I've been having trouble restoring the operating system volume to the 512 GB SSD using the Disaster Recovery client. I have installed the driver for that SSD into the DR client. The otherone does not need a special driver. The most recent error I've gotten is + Executing Restore from Backup at 2/1/2018 3:10 PM 2/1/2018 3:10:42 PM: Connected to minint-d36kkvn To volume Programs Disk (C:) on minint-d36kkvn... - 2/1/2018 3:10:42 PM: Restoring from Backup Set 1, Snapshot Dell15R, 2/1/2018 4:43:44 AM [*] T-29: VssWBeginRestore: PreRestore failed, winerr -2147212270, error -3045 2/1/2018 3:11:16 PM: Execution incomplete Duration: 00:00:09 (00:00:03 idle/loading/preparing) I got other errors before this, the most significant being Retrospect telling me that it was going to wipe out information on the other SSD, not the one I told it to restore to. To stop it from saying that, I first changed the drive letter on the volume I didn't want Retrospect to write to and, when that didn't work, I took the volume offline. Then I tried taking the whole disk offline. Still no joy. So now I am at a loss. I know that, as a last resort, I can reinstall the operating system, but why should I have to? I hope that, if I do that, Retrospect will at least let me restore the data. .
  3. Hello, I am using Retrospect Desktop for Windows, version One of my hard drives (not the system drive) failed on my desktop PC so I replaced it and decided to boot from the recovery CD to restore the files to the new drive. Unfortunately my catalog files were on the failed drive, but after every backup I copy the catalog folder to the drive that the retrospect backup files reside on. When I booted to the CD and tried to restore I was prompted to find the catalog file. I drilled down to the file and when trying to open it I received a dialog box "File Not Found". When I tried the other catalog files in the folder I received the same message. My next step was to download a backup from my Backblaze remote backup onto a USB drive. Once again I received the same message. I gave up using the disaster recovery option. I booted the PC and copied the Backblaze Retrospect catalog file onto my C:\ (system) drive. When I opened the file from within Retrospect it loaded fine and I am using it to restore my drive as I write this. I've used the recovery CD in the past with no problems. This is concerning since I would need to use it to recover a system drive. Thanks for any help. Greg Noelken
  4. I have a notebook that I dual boot between Windows-8 and Linux-Ubuntu-12.04. After the main drive went bad and was replaced, I realized that it appeared impossible to restore the system from my Retrospect Backups. I booted the Disaster Recovery CD that I made and restored the C: drive, but it wouldn't boot because the MBR had been modified by Linux to point to the Linux /boot parition which didn't exist yet! Is there any way to build and later restore a Windows/Linux dual boot system? If I was able to modify the MBR back to the way Windows had it prior to the Linux dual boot modification, I would be all set. Unfortunately, I couldn't find a tool that worked. They all produced the error message "Repair Unsuccessful".
  5. I'm using a Disaster Recovery Disk created by Retrospect 12.0 to restore the contents of my failing (getting SMART errors) system hard disk onto a new disk. "Restoring an entire volume" from a full backup set created with Retrospect 9.5 results in this error: + Executing Restore from Backup at 4/9/2017 6:55 PM To volume OS (D:)... - 4/9/2017 6:55:04 PM: Restoring from Backup Set A2, Snapshot CB-17R, 3/26/2017 10:11:36 AM 4/9/2017 6:57:40 PM: Finished deleting 191,345 unnecessary files and 28,542 unnecessary folders on destination 4/10/2017 5:53:07 AM: Creating folders 4/10/2017 5:53:30 AM: Finished creating 66,387 folders 4/10/2017 5:53:30 AM: Copying VSS writer files 4/10/2017 6:04:02 AM: Finished copying VSS writer files 4/10/2017 6:04:02 AM: Copying properties for 66,387 folders Folder "\\?\Volume{c36d2647-0c55-11e2-80ce-806e6f6e6963}\\Users\Default User\.": can't write security information, error -1119 (directory not empty) 4/10/2017 6:07:15 AM: Finished copying properties for 66,387 folders System configuration restored, please reboot the computer. 4/10/2017 6:07:21 AM: 1 execution errors Completed: 510480 files, 696.2 GB Performance: 1074.6 MB/minute Duration: 11:12:10 (00:08:58 idle/loading/preparing) While the resulting system disk will boot, it's worthless. Files are locked, application links are gone, etc. I've already solved the problem by using Paragon's Disk-to-Disk OS Migration software to copy my old disk onto my new disk, but I really want to solve this problem in case a true disaster strikes! Thanks in advance for any help.
  6. I'm currently busy with a machine where a 1TB drive was partitioned into three approximately 330GB partitions. "C" became full and an adjacent partition was deleted so that the space could be allocated to "C" 1. Since the deleted partition was on the LEFT of "C", allocating this unpartitioned space to "C" proved impossible from within Windows 7 as this only allows merging with partitions to the RIGHT of "C" ... and then also not always. 2. The next option was to do a Retrospect Disaster Recovery onto a 'test' 500GB drive, just to check if all's well. I could then delete existing "C" completely, restore the backup onto a resized partition and create a second partition once the computer reboots. This also proved impossible: apparently the restore drive has to match the physical size of the entire drive (not just the partition) from which "C" was backed up. 3. I then tried "restoring an entire volume" onto the 500GB drive from within Retrospect in Windows 7. This also proved impossible ... the computer wouldn't boot from the restored drive. Tried re-creating the MBR etc. from the System Repair disc, but still no booting PC. Tried the System Repair disk ... still no luck. My last option is to load Windows 7 onto the 500GB drive, and then restore the Retrospect backup. This should boot up. If yes, then I can safely delete the 1TB drive and restore the backup onto a suitably-sized partition ("2" above should then not be a problem). All this work simply to create more space for "C"! If I had known the headache this would cause I would simply have bought Acronis Disk Director 12 and resized, merged, shifted the partitions as required (unfortunately Powerquest Partition Magic is no longer supported - this software was literally 'magic'). Comments would be welcome.
  7. I’m running Retrospect Professional 9.5 under Windows 10. After reading a number of documents on the Retrospect Website, I still have questions about which files must be backed up to ensure that Windows 10 could be recovered after a hard crash of the hard disk. The Retrospect 9.5 for Windows user guide says simply: “it is first necessary to have a complete Retrospect backup of that computer’s boot volume”. To reduce backup size (and time required), I’m wondering: (1) Do I need to use the “All Files” selector, or will “All Files Except Cache Files” be OK? (2) Do I need to backup temporary files, or would it be OK to add and exception for the Windows Special Folders selector “TEMP Folders”? (3) How is “TEMP Folders” defined?
  8. Every time I do a back up, Retrospect asks me to create a disaster recovery disk. It started happening after I purchased the dissimilar hardware option for version 9 and the message continues in version 10. I have created several disaster recovery discs, the latest last week, but the message continues to appear and Retrospect will not exit until I cancel that request. How do I get rid of it once and for all? Retrospect 10 on Windows 7 x64.
  9. I'm unable to get past downloading the WADK step and selecting the copype.cmd file, basically because it never downloads such a file. I can either install or download the WADK from Microsoft, but NEITHER version comes with this copype.cmd file. Where do I get that file?
  10. I'm running Retrospect on WIndow XP SP3. If I use Retrospect to create a disaster recovery disk, it wants to download the deployment kit for Windows 8.1. There are changes to NTFS between XP and 8.1 and I don't think that XP would be very happy using a filesystem prepared by 8.1. Is it still possible to create a disaster recovery disk for Windows XP? If so, how? Thanks ++PLS
  11. I sure hope that someone can help me. I'm using Retrospect 7.7 with Windows 7 os. I've booted up with the recovery disc and and rebuilding the catalog from my backup drive to my reformatted hard drive. However, after a 3+ hour "recreating catalog" process, when I try to go through the next steps on the restore wizard, the new catalog file is not recognized. Why is this happening?
  12. I have two and a half questions about this: Firstly, where exactly are the installation files for Backup Agent? (I have both 7.7 Professional and 7.7 Server for Windows.) I have read the instructions, but the files I have found so far only seem to open the Professional installation when I install them! Can I download them, rather like the Disaster Recovery Disk? Secondly, can I install the backup agent on a Windows 7 workstation that already has Professional installed, or will this cause a conflict? Finally, for an extra point, is the Retrospect Disaster Recovery Disk specific to the machine it was created on, or will it work with any machine that has (or had) Retrospect installed on it? (For example, does it copy driver files for installed SCSI adaptors, and will a Recovery Disk created on a Windows 7 Workstation work on a Windows server?)
  • Create New...