Search the Community
Showing results for tags 'Bare Metal'.
Found 2 results
Hello All ! Here's the story... that kept me awake for around 2 days... I have an XP SP 3 VM running under VMWare Fusion 6.0.2 on my Mac OS 10.9.2 Mac Pro (2008), and backed up by a Retrospect 7.7 SBS server. I've been using my VM daily for years, but it was giving signs of malfunctionning (freezes with a black screen after login in). I decided to rebuild it from scratch, by creating a new one with the same characteristics under VMWare Fusion, and then doing a bare metal restoration with the Retrospect 7.7 Rescue CD and my latest backup. It didn't work as intended. I was able to boot the VM from the Rescue CD iso, and got the first dialogs for the restoration. The problem was that the Emergency Recovery Wizard was unable to configure correctly the (virtual) network card: it kept assigning a localhost address (127.0.0.1) which is pretty much useless when you want to connect the Retro Client to the Server in order to restore everything. In fact, the option "Adjust drivers to support new hardware" shown on the documentation page http://www.retrospect.com/en/documentation/user_guide/win/disaster_recovery and that I linked here was missing: http://download.retrospect.com/docs/win/v8.0/user_guide/img/en/addendum_rug-17.jpg I remember doing a bare-metal recovery on a physical PC some years ago using the backup from my server over the network, and it had worked fine. Why isn't this working today anymore ? Is it because I was trying to do it on a VM ? Why is that "Adjust drivers..." option missing from the wizard ? I ended up recreating my VM anyway by first installing Win XP from the CD, then the Retrospect 7.7 client and then doing a full restore on it. After some tweaking around (notably because for some unknown reason the MBR of my VM was messed up, and I had to restore it with the CD console), I finally was able to use it normally. Thanks for your ideas, Paul-Henri
Using Single Server 8.5 to back up a 2012 Win Server that is a basic file and print server. Used Retro for many years, but first time I have not had the open file option add-on package (no more exchange or sql at this site). I see LOTS of 1020 sharing violations for NTUSER.DAT and other files (mostly log files, but not all). If I someday try a bare metal restore of this server, will it fail because I can not use open file option? I am not worried about compare errors, but CAN'T READ NTUSER.DAT doesn't sound so good. Given that level of failure, is there any point to Retrospect for server backup of the C drive for me? Pity a semi-crippled ofo could not included that covered the basic files, but too tricky I guess. My workaround is Windows Backup to a usb disk and then let retro copy that to tape. I set that up already, once I saw these failures. Then I can do this sort of thing: http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Restoring-Windows-Server-Bare-Metal.html Is Windows better at bare metal restore than the basic Retrospect server package? Am I am missing something?