Restoring the client machine through 's Recovery CD
supports creating an image of entire disk or specific partitions in Windows machines and then backing it up. In case the Windows client machine crashes completely or if a specific drive gets corrupted, it can be recovered from the 's backed up image.
The restored image can be directly applied to the disk in the case the disk to be restored is accessible from the machine where the restore is run. This is covered in detail here.
However, often the client machine may be in a different location or the disk may not be accessible from the machine where the image restore is run. In such cases, the restored image has to be shipped to the client's location and the image has to be applied through 's Recovery CD.
This recovery is a two step process.
- The image that is backed up by the client needs to be restored from the backup location. More details on it can be found here.
- Through 's Recovery CD, the restored image file can then used to either restore the entire disk and boot up the client machine (in case the image is of a boot - OS disk) or can be used to restore the specific partition (in case it is an image of a specific partition). This second step is explained in detail in this document.
's Recovery CD can also be used to convert the restored image (.vhd) file into a virtual image. The image file can be converted into one of the following two formats
VMDK - VMWare's virtual machine image format. Image converted into VMDK format can be launched as a virtual machine on a VMWare Server.
VHD - Microsoft Hyper-V virtual machine format. uses VHD image format for backups. But if you opted encryption,compression, while taking backup, It must be decrypted and(or) decompressed before, used in Hypper-V Servers. Though you can use incremental VHD files directly, we suggest to use Fixed Size VHD Image. Image converted into VHD format can be launched as a virtual machine in a Hyper-V environment.
How to create a Recovery CD(ISO)
For step by step documentation of generating recovery cd, click here.
Recovering the Client Machine with the restored Image file
- Follow the steps mentioned here to recover the image file. In step 4, select the first option as shown below
Download the Recovery CD ISO from here and burn it into a CD. Boot up the crashed machine with this CD.
Recovery welcome wizard page will be displayed as shown below. Select Next to continue
The tasks that can be performed with the Recovery CD will be listed as shown below. Select the Recover entire Disk or Partition and click Next.
The next page will let you select the backup file to restore.
Click Browse button and select the folder where the backup image was restored in the first step as described earlier in this document.From the list of Vhd file you may choose to select , which incremental vhd you wish to recover.
From the selected vhd file select either Disk or Partition in the disk to restore.
Select the target Disk or Partition from the Target Device List to which you want to restore the image and click Next. Make sure selected disk is as large as the original disk.
Depending on the used space the restore will take some time. After restore is completed click Finish button to restart the machine
Convert Physical Disk Image to a Virtual Image (P2V)
Run the Recovery CD and select the Physical to Virtual Conversion option and click Next.
Click Browse button and select image file that was restored from the backup data.
Enter the target folder path where you want to store the converted virtual image file.
Select the virtual environment type - VMWare or Hyper-v
Time for virtual conversion depends up on the size of the disk. After the conversion, click Finish button to restart the machine
NOTE:The image backup data can be restored as a virtual image directly during the restore as described here: here
Restore OS to Dissimilar Hardware
While you restore a image backup to Different hardware, Os which restored in that volume may not contain the necessary drivers for the new hardware. So it will not boot and show blue screen. You can use following options to fix this problem.
In Recovery CD, select 'Advanced Options' and it will give a window like below screenshot,
Following section explains the each of the components and their usage
From the Recovered volume drop-down-list, user have to select a volume in which, he wishes to inject drivers or want to fix issues.
If there are no valid windows volume found, application will show a warning.
Possible reasons for a volume not listed are,
If utility haven't found any windows volumes some of features will be disabled .
Once you selected a volume, from the Recovered volume drop-down-list, you can see the Windows version info, which is installed in that volume.
- Physical connection issues
Check the bios whether the disk is listed. If not fix the cables which connecting them
- Required Drivers not available in the Recovery CD
Install the driver using "Install drivers for recovery environment" option in RecoveryConsole tab
it is used to recheck the available windows volumes, in case you installed required storage drivers.
- Driver Injection
- Inject Driver
- It is used to inject drivers into the selected windows volume.
User needs all the required driver files to use driver injection.
Browse and select the driver inf file and click "Inject Driver" button
If you don't know which devices is present, click, "Don't know which file inject" button.It will give list of storage devices present in the current machine and its driver provider names.
- Install std IDE Drivers
- Installs the standard IDE Controller Drivers, and registry entries, which are natively supported by windows. Note that although this method might enable the restored system disk to start successfully, other hardware differences can lead to other problems.
- Fix Incompatible Services
- It will fix problems like moving from Intel processor to AMD processor by disabling unnecessary services
- Inject VMWare Drivers
- Injects the necessary drivers needed for Vmware servers after doing P2V.
- HAL Update
Windows Operating system uses HAL (Hardware Abstraction Layer) to communicate with devices. Windows versions below Vista (XP,2003)
won't automatically update their hal component always, when moving to different hardware. So this option allows, users to manually change the
correct HAL component.
User have two option
- Auto - Utility decides the correct HAL automatically
- Manual - User can force the utility to install specific HAL. But it is not recommended to update otherwise asked by technical team. because updating incompatible HAL will cause boot errors.
- When do use this option?
- Restored operating system is Windows XP or Windows 2003
- Unable to boot the machine and while opening in Advanced Options in Recovery Console getting warning "HAL type mismatch found. Please update HAL"
- How to update HAL ?
- Auto :
This is the recommended mode of hal updation.
- Select Auto radio button . It is enabled only when the HAL updation is necessary
- Click Update HAL button
- Manual :
Use this method only if asked to use by technical team. Updating incompatible HAL would cause booting problems.
- Select Manual radio button.
- Select a Haltype from the drop-down-list.
- Click Update HAL button
- MBR update
Select the correct system volume from the System Volume drop-down-list. In Windows, "System volume" is the volume which contain it's boot files. For XP and 2003 windows system volume contain boot.int and ntldr files. For Vista and above OSs, it contain bootmgr and BCD files. Backup and restoring a windows volume without system volume will not boot.
- Update MBR
It is used to fix the corrupted master boot record of the disk which have been selected.
- Update VBR
It is used to fix/update the corrupted volume boot sector of the selected system volume
- Fix BCD/boot.ini
- If the Restored Os is Vista or above, it will fix the BCD info for that. Otherwise it would open boot.ini for user to
manually update the os list.
- Other Fixes
- Disable Auto Reboot
- Normally when windows fails to boot it will restart the machine. Using this option you can disable rebooting.
- Recovery Console
- Install Driver for Recovery Environment
It is used to install drivers for Recovery Environment which you are currently running. For example you have booted the machine in Recovery CD and inside that you couldn't access the network or a volume because of driver problem
Recovery Environment may not have all the required driver for all attached devices. So we cannot inject driver to required volume until Recovery Environment can detect and list the disk. We have to provide required driver for storage devices. Current Recovery CD is based on "Windows 7" 32 bit. So you have to provide driver files for Windows 7. Application will ask to select a folder which have required driver files(in the .inf,.sys format). It may contain subdirectories.
Driver installed in this method won't update Recovery Environment permanently. Once reboot into recovery environment you have to do the same again. To permanently install driver in Recovery Environment you have to install it while you building the Recovery CD itself.
Failed to boot and shows "Disk Read Error Occurred. Press CTRL ALT DEL to restart"
- Open BIOS setting by pressing F2 or Del or any other keys depending on the motherboard configuration
- The required disk available in the disk list
- The disk is in top off the boot order
- If the above test are successful, then boot with Recover CD
- In the advance options select the System drive and click Fix MBR
Failed to boot and keep on restarting
While booting press F8 and disable auto restart. Or use Disable Auto Restart option in Recovery CD.
Failed to boot after restore with BSOD and with 0x7B error
- If you are getting warning "Some system settings are incompatible with current machine configurations" in Advanced Options use Fix Incompatible Services in Driver Injection section
- Try Inject std IDE drivers if you restored data to a IDE/SATA disk
- Inject the drivers for storage devices like RAID,SATA controller using Inject Driver in Driver Injection section
Failed to boot after restore
Select the system volume in advanced option MBR Update section, and set as active.
Select Fix BCD/boot.ini in the Advanced options of Recovery Task list
If the above test are successful, then boot with Recover CD
- Select the system volume in advanced option and set as active.
- If the os is XP or 2003 check the HAL type conflict.
- If you have moved from different motherboards with different vendors click Fix Incompatible Drivers
Failed to load in virtual environment after P2V conversion
Inject the Vmware driver by using Inject Vmware Drivers in Driver Injection section
Select Inject std IDE Drivers option