Jump to content

Search the Community

Showing results for tags 'system state'.

More search options

  • 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 1 result

  1. I am using Retrospect Professional 7.6.123. I am testing its use for a full restore after loss of the hard drive. The Disaster Recovery CD will not work -- the ISO image is too large. I've thus opted for a method that involves a temporary installation of my current OS (XP SP3), installation of Retrospect, restoration of a small "secondary" OS on another partition, a boot to that alternate OS where Retrospect is already installed, deletion of the temporary XP install, and, finally, restoration of the primary OS, apps and data to their respective partitions. I was surprised (and disappointed) to see that when Retrospect restores the system state from the secondary OS to the primary OS (which contains a WINDOWS directory tree), the restore claims to have succeeded but it does not restore the registry to system32\config. Apparently, the system state restore has to occur from within the primary OS. (This is counterintuitive.) So, I used a manual registry backup (made routinely with ERUNT) to allow the primary OS to boot and restored the system state with Retrospect from within the primary OS. Again, the restore claimed to be successful. The History pane shows 0 files restored, which doesn't make sense. SInce the system state is backed up via an API, there are 0 files backed up, but there are certainly files restored, the registry hives among them. After the reboot, the registry had indeed been rewritten, but MetaBase.bin (a system state component in the system32\inetsrv directory) was not restored. (I have now added it to my manual registry backups so it will be available in case of a calamity.) Is there a complete list of the files that are rebuilt by a system state restore? I need to ensure via this trial run, that all of the files are restored. If not, I need to ensure that they're backed up manually. (When I searched for "system state" or "registry" or "metabase.bin" in the knowledgebase, I found nothing useful. In Retrospect, "Help" had little to say.)