Replibit Recovery Toolkit Version 3.5

Replibit Recovery Toolkit Version 3.5

Table of Contents Bare Metal Restore Guide... 4 Dissimilar Hardware Driver Injection... 8 Recovering from Windows Bootloader issues after a Bare Metal Restore... 11 Post Recovery... 12 Troubleshooting... 13 Repairing Broken / Missing Windows SRP or Boot Partitions... 13 Update or Replace Storage Drivers... 13 Extremely Poor Network Performance with Hyper-V... 13 Manual Bare Metal Restore (Advanced)... 14 Manual Bare Metal Restore Procedure... 14 Recovering UEFI Systems Backed-Up Prior to Replibit version 2016.03.16... 19 Creating a USB RRT Disk that can boot either UEFI or BIOS mode... 21 Troubleshooting... 22 Update or Replace Storage Drivers... 22 VMware Recovery Options... 23 NFS Recovery... 23 iscsi Recovery... 24 Relocating Back to Local Storage... 24 Hyper-V Recovery Options... 26 NFS Recovery... 26 iscsi Recovery... 27 Relocating Back to Local Storage... 27 Replibit Recovery Recovery Toolkit... 28 Recovering Deleted Files... 28 Disk Defragmentation... 29 Partition Management... 29 Secure Erase... 30 Offline Registry Editor... 30 Partition Table Recovery and Repair... 31 2

Windows NT Password Editor... 32 Hardware Device Identification... 32 File Backup, Comparison, and Synchronization... 33 Benchmarking... 33 Anti-Virus Utilities... 34 Portable Toolkit... 34 Creating a Bootable USB Stick... 35 3

Minimum System Requirements 3GB RAM 1Ghz CPU Bootable DVD or USB Support Bare Metal Restore Guide 1. Download the Replibit Recovery Toolkit (RRT) ISO from http://replibit.com/downloads/ 2. Note: There are two versions of the RRT ISO, x86 and x64 If you are recovering a system using UEFI, you must use the correct architecture 3. Boot your destination system from the RRT ISO. 4. Wait a minute once the Desktop loads for the Network wizard to start networking 5. Locate the "Replibit Recovery Wizard" icon on the Desktop and Double-Click it 6. This will launch the Replibit Recovery Utilities as shown below. For Legacy BIOS systems select "MBR Boot Partition". For UEFI BIOS systems or Data Partitions select Data/UEFI Boot Partition 4

Enter the Appliance or Vault IP information and the login credentials and click next. Please note: If you are doing a BMR from a vault, you will need the customer credentials that you created in the licensing portal, NOT the admin user. 7. Select the protected system out of the drop down list that you wish to restore. You can choose a specific date to display snapshots from or you can bring up a list of the most recent snapshots. After you have made your choices, press next. 5

8. Select the snapshot you wish to restore from and click next. 9. You will see the iscsi initiator service start and connect, once complete, press next. Note that it may take several seconds for iscsi services to start before Next is available 6

10. Select the Disk Volume(s) you wish to recover. Next, select the disk you wish to recover it to. (Usually Disk 0). 11. This begins the restore job. When you see restore complete, you can reboot your server into the OS. If you are restoring to different hardware, you can continue to the Dissimilar Hardware Driver Injector and Recovering from Windows Bootloader issues after a Bare Metal Restore Sections below. NOTE: If you receive any Format Disk pop-ups, select Cancel 7

12. For restoring additional data drives, repeat the above process by selecting the Data Partition Recovery at step 4. Dissimilar Hardware Driver Injection 1. Open Disk Management or AOMEI Partition Assistant. 2. Verify the volume letter of the partition that you restored the operating system to. (Remember the Drive Letter). 8

3. Launch the "Replibit Recovery Wizard" from the Desktop icon. 4. Once the Replibit utilities launch, select Driver Injector. 5. When the driver injector launches, you will need to set some things. First is the Target Analyzer Output. This will always be: X:\BMRReplibit\devices.pmq. Next is the Driver Search Directory. Select browse and browse to the CDROM Drive (Y:\) and select the Drivers folder. Lastly, you will need to select offline and enter the drive letter of the recovered windows volume along with the windows directory (Sample: C:\Windows). Once everything is entered, press next. (Note: My drive letters are specific to my environment, please note, your drive letters will vary from the image below.) 9

6. The driver search will begin. 10

7. Once it is completed, verify the drivers and click next. 8. The Driver Injector will install the drivers. Once it is completed, you can close the wizard and reboot the system to your recovered windows instance. 9. Reboot the recovered system and verify that Windows loads normally. If you encounter a Windows Bootloader error message, perform the next steps Recovering from Windows Bootloader issues after a Bare Metal Restore 1. Boot the system from the Replibit Recovery Toolkit Note: If you have just completed a BMR restore with the Replibit Recovery Wizard, reboot from the RRT disc before proceeding to clear open iscsi connections and relabel Disk volumes 2. Open a Command Prompt using the icon on the Desktop 3. Run CD \ 4. Run bcdedit.bat <Drv:> where <Drv:> is the drive letter containing Windows (i.e C:) 5. Locate the Windows Startup Repair tool in the Taskbar and click it 11

6. Once the Startup Repair Wizard has completed, reboot the system to Hard Disk 7. Select Start Windows Normally if prompted If Windows still is not booting, perform the following to repair storage controller drivers 1. Run the Driver Injector as above and identify the storage controller and driver files 2. Exit Driver Injector 3. Copy the driver files to a new folder B:\Driver 4. Open a Command prompt 5. Run DISM /Image:<Drv:\> /Add-Driver /Driver:B:\Driver 6. (Replace <Drv> with the drive letter that contains the Windows folder) 7. Reboot the System. Select Start Windows Normally if prompted Post Recovery IMPORTANT!!! After performing a full system recovery, regardless of the method used, it is imperative that a new Full Backup be run from the Appliance to synchronize the recovered system with the backup image. Failure to perform a full backup may result in the loss of all future data changes made on the protected system. 12

Troubleshooting Repairing Broken / Missing Windows SRP or Boot Partitions If the SRP partition is lost or corrupted, or the Windows Bootloader files are broken, perform the following steps to recreate the BCD boot records. This may also be necessary if you have ever recovered the system from another Disaster Recovery solution that has created a small Disk 0 that contains only the SRP partition. (In this case, delete Disk 0 entirely and perform the steps below to recreate /Boot on C: ) 1. If a separate SRP partition exists, use Disk Manager to assign a drive letter to it 2. If the partition is corrupted, perform a format to FAT32 3. Open a Command Prompt 4. If there is an existing /Boot folder on C: or in the SRP partition, change Dir to /Boot and rename the BCD file 5. Run the following commands BootRec /FixBoot BootRec /FixMbr (Only if using MBR disk, not UEFI) BootRec /RebuildBcd (Select Windows Install When Prompted) Update or Replace Storage Drivers When recovering to new hardware it is often necessary to update or replace the storage controller drivers in order for the recovered system to successful boot. Complete the following steps to manually install a new OEM storage controller driver 1. Boot the recovered system from the Replibit Recovery Toolkit (RRT ISO) 2. Identify the drive that contains the Windows folder on the recovered system (DstPath) (i.e. C:\) 3. Copy the new drivers to a USB stick or network folder location accessible from the BMR environment. Note the full path to the folder containing the driver files (DrvPath) Note: You may place multiple drivers in the folder for simultaneous installation 4. Open a Command prompt and execute the following: DISM /Image:<DstPath> /Add-Driver /Drivers:<DrvPath> /Recurse 5. Reboot the recovered system normally Extremely Poor Network Performance with Hyper-V Ensure that you using a Legacy mode network adapter on the Hyper-V guest when booting from the Replibit Recovery Toolkit CD. Using the native Hyper-V adapter can cause extremely slow network performance during the recovery 13

Manual Bare Metal Restore (Advanced) Manual Bare Metal Restore Procedure The following procedure will document recovery steps to perform a manual BMR process. This procedure is useful for recoverying systems with more than two disk volumes, GPT disks, UEFI boot volumes, OEM partitions, and other scenarios where the recovery wizard fails to properly recover the system. This process may also be used as a general disk cloning tool and can copy disks not part of the Replibit backup set. Requirements: Replibit Recovery Toolkit ISO 2GB+ System Memory (3GB+ for x64) Network Connectivity (for iscsi communications with Replibit Appliance or Vault) Destination disk at least as large as source disk To begin, boot the bare metal system from the RRT ISO. (This machine may be virtual) 14

Next, from the Replibit Appliance or Vault, select the protected system, choose a recovery point to recover from and select iscsi Start. Select the iscsi tab from the left menu and verify that the disks have been exported 15

Return to the BMR environment on the destination server. Verify that the network stack has started and the Appliance or Vault is reachable. Mount the exported iscsi disk using Microsoft iscsi Initiator. From the dock bar on the right side of the screen, launch Microsoft iscsi. Select Yes to start the iscsi services. Once the iscsi Initiator Properties window opens, locate the Target field. Enter the IP address of the Appliance or Vault and click Quick Connect. The target address should be added to the Discovery tab and the available disk targets should be connected. (If the targets are not connected, select them and click on Connect) Select the Volumes and Devices tab and click Auto Configure. Make a note of the drive letters that belong to the iscsi mounted volume(s) Click OK to close Microsoft iscsi Properties 16

Open AOMEI Partition Assistant (Or Disk Management from Manage Computer) Refer to the driver letters you noted above and identify the disk number(s) that contain those drives. These drive(s) are the *SOURCE* disks to be referenced later. Also identify which drive number(s) you intend to overwrite with the recovered data. These are the *DESTINATION* disks to be referenced later. (In the above case, drive 1 is the source, and drive 0 is the destination.) 17

Perform the disk copy Open the command prompt from the desktop and change directory to X:\BMRReplibit Run the following to begin the drive copy process: FastClone.bat src=x dst=y [-b] Where x and y are the numbers of the source and destination disks as identified by DiskManager Include b if this disk is the boot volume Read the warning, verify your disk choices and enter Y to continue with the copy process. THE DESTINATION DISK WILL BE OVERWRITTEN!! ANY EXISTING DATA WILL BE LOST!! 18

Wait for the copy process to complete. If copying a boot disk you may be prompted to enter the drive letter of the Windows system disk. Open Disk Manager and identify the current drive letter on the DESTINATION disk that contains the Windows system folder. Once the copy has completed, perform cleanup. Stop iscsi exports on the Appliance or Vault. Remove the RRT Recovery CD from the protected system and reboot. If Windows does not boot normally, perform the following to repair the Windows boot process Boot from the RRT Recovery CD once again From the Dock toolbar or Windows Start Menu under Replibit BMR Tools folder run Windows Startup Repair. Remove the RRT Recovery CD and reboot into Windows Note: Do *NOT* run Windows Startup Repair while the source disk is still connected to the recovered system. This will cause multiple instances of Windows to be added to the BCD record and likely cause the system not to boot properly Recovering UEFI Systems Backed-Up Prior to Replibit version 2016.03.16 UEFI systems that were backed up prior to UEFI supported agents will not restore properly using the Recovery Wizard. The following manual procedure may be used to perform a recovery of these systems 1. Boot from the latest x32 or x64 Replibit Recovery Toolkit (RRT) ISO. Be sure to boot using UEFI mode, not Legacy BIOS mode Note: If using a USB drive and not an ISO or physical DVD, see notes below on how to create a UEFI bootable USB image of the RRT ISO 2. Prepare the Destination disk for UEFI a. From a CMD prompt run DISKPART b. Select Disk x (where x is the drive number of the target recovery disk) c. Clean (WARNING: This will erase the disk, make sure you selected correctly!) d. Convert GPT e. Create Partition efi size=x (Windows 2008 x=100, Windows 2012 x=350) f. Select partition 1 g. Format Quick FS=fat32 h. Assign i. Create Partition Primary (optional: Size=x) j. Select Partition 2 k. Format Quick FS=NTFS l. Assign m. Exit 3. Using Firefox on the RRT Disc, Connect to the Appliance and iscsi Start the Recovery Point 4. Open Microsoft iscsi Initiator from the Windows Taskbar. Enter the IP address of the Appliance and click Quick Connect. (The exported iscsi disk should display as connected. If not manually connect the required disk) 19

5. Open Disk Management from the Desktop and verify the drive letters for Source and Destination for the partition that contains the Windows system folder 6. Open FastCopy.exe from X:\BMRReplibit Set Source and DestDir to the correct path Check ACL and Estimate Click Execute and wait for the file copy to complete 7. Once the copy is complete, Stop iscsi from the Appliance Web GUI 8. Open Microsoft iscsi Initiator and remove the drive connections a. Delete all entries from the Favorites tab b. Delete all entries from the Discovery tab c. Disconnect all drives from the Targets tab (Wait 1 minute if the disk is busy and retry) 9. Recreate the Windows BCD boot records and EFI System files a. Open a CMD prompt and run the following commands b. Bootrec /FixBoot c. Bootrec /RebuildBCD (Enter Y when prompted) d. Bcdboot x:\windows (Replace x with the Destination drive letter) 10. Run Windows Startup Repair from the Taskbar 11. Remove the DVD/USB and reboot the system in UEFI mode 20

Creating a USB RRT Disk that can boot either UEFI or BIOS mode 1. Download the latest Rufus USB Tool https://rufus.akeo.ie/ 2. Download the latest Replibit Recovery Toolkit (RRT) ISOs http://ftp.replibit.net/iosdownlod Attach a USB device at least 4GB in size 3. Run Rufus 4. Select the following settings MBR Partition scheme for BIOS or UEFI File System Type: Fat32 Enter a Label (Optional) Set Create a Bottable Disk Using option to ISO Browse and select the ISO image Click Start (and wait a WHILE for the file copy to complete) 21

Troubleshooting Repairing Broken / Missing Windows SRP or Boot Partitions for Legacy BIOS If the SRP partition is lost or corrupted, or the Windows Bootloader files are broken, perform the following steps to recreate the BCD boot records. This may also be necessary if you have ever recovered the system from another Disaster Recovery solution that has created a small Disk 0 that contains only the SRP partition. (In this case, delete Disk 0 entirely and perform the steps below to recreate /Boot on C: ) 6. If a separate SRP partition exists, use Disk Manager to assign a drive letter to it 7. If the partition is corrupted, perform a format to FAT32 8. Open a Command Prompt 9. If there is an existing /Boot folder on C: or in the SRP partition, change Dir to /Boot and rename the BCD file 10. Run the following commands BootRec /FixBoot BootRec /FixMbr (Only if using MBR disk, not UEFI) BootRec /RebuildBcd (Select Windows Install When Prompted) Update or Replace Storage Drivers When recovering to new hardware it is often necessary to update or replace the storage controller drivers in order for the recovered system to successful boot. Complete the following steps to manually install a new OEM storage controller driver 1. Boot the recovered system from the Replibit Recovery Toolkit (RRT) ISO 2. Identify the drive that contains the Windows folder on the recovered system (DstPath) (i.e. C:\) 3. Copy the new drivers to a USB stick or network folder location accessible from the BMR environment. Note the full path to the folder containing the driver files (DrvPath) Note: You may place multiple drivers in the folder for simultaneous installation 4. Open a Command prompt and execute the following: DISM /Image:<DstPath> /Add-Driver /Drivers:<DrvPath> /Recurse 5. Reboot the recovered system normally 22

VMware Recovery Options Any of the Bare Metal Recovery options previously discussed may be used when rescuing protected systems back into a VMware environment. In addition, the following options are also available. NFS Recovery In a VMware environment it is possible to utilize the NFS Export feature of the Replibit Appliance or Vault to simplify and expedite recovery of protected systems when the underlying storage of the host server has been compromised, but the physical host is still in operation. In order for this method to be employed, verify that there is sufficient free space remaining on the Appliance or Vault to hold the entire thick provisioned disk size for all protected systems you intend to recover. If insufficient disk space remains, refer to VMware iscsi Recovery below. To begin recovery of the affected protected systems, from the Web GUI select a recovery point for each protected system that you wish to restore and choose EXPORT. Select VMDK as the format and start the Export process. Monitor the progress of the operation from the Jobs menu on the Conversion tab. For better performance it is recommended not to select Export to USB. If you require additional space to perform the export, it is recommended to use the VMware iscsi Recovery method instead. From the Web GUI navigate to the NFS Exports menu and select Enable NFS Exports. On a Vault, you will have to be logged in as a user account in order to see this option. If not already present, click Add Allowed IP and add the IP address of the VMware host server. In multi-server environments, add all hosts addresses if desired to enable vmotion operations between hosts. From the VMware Client, connect to each host and add the Replibit device as an NFS storage location. Select Configuration and then choose Storage. Click Add Storage and choose Network File System, then click Next. For Server enter the IP address of the Replibit device. For Folder enter /export/admin for an Appliance or /export/<username> for a Vault, where <UserName> is the customer name for the protected systems you are trying to restore. Do NOT select Mount NFS Read-Only. Enter a name for the new datastore (i.e. Replibit ) and click Next, then click Finished. If successful the new datastore should appear in the list of storage locations. Once the Export jobs have finished for each protected system that you intend to recover, create a new guest server within the VMware Client. Choose the Replibit data store as the server location, and configured the desired system resources and settings. When selecting disk drives, choose Use an Existing Hard Disk and browse to the exported disk volume in the Replibit storage folder. If necessary, edit the final gust server configuration and add any additional disks to the system. Power on the guest server and complete any required configuration changes to the running system to return it to service. The recovered system may be run indefinitely from Replibit storage while waiting for repair or replacement of the failed host system storage array. 23

iscsi Recovery If disk space on the device is constrained, iscsi export can be used to expose the protected system disks to VMware. This has the advantage of being faster, as we do not have to wait for the Export conversion process, but iscsi is also more fragile. Currently, iscsi exported disks are not persistent through a reboot of the Replibit device. The disks will have to be rediscovered and guest servers will have to reconfigured if the Replibit device is rebooted. Data changes applied to the iscsi disks may be lost in this event. It is recommended to use iscsi Export with caution, and at present NFS Export is to be preferred. If using this iscsi Export method, ensure that protected system backups are proceeding successfully and increase the backup frequency to alleviate possible data lost in the event of a device reboot while the recovered systems are running from Replibit storage. Complete the steps listed above to enable NFS Exports and add the Replibit device as an NFS storage location to your physical VMware hosts. This will provide a location to hold the Guest server definition and temporary file storage. Configure each VMware host to allow iscsi discovery from the Replibit server. From Configuration select Storage Adapters. If not already present, add the Software iscsi Adapter to the host. For ESX 5.1 and newer, configure iscsi network communications as follows: From Networking select a virtual switch whose physical network adapters are connected to the same physical network as the Replibit device. (Typically this is vswitch0) If not already present, select properties and add a new VMKernel Adapter to the switch. Give it an available IP address in the same subnet as the Replibit device. In complete networks, assign the VMKernel adapter to the correct VLan. If more than one physical network adapter is associated with this vswitch, edit the properties of the VMKernel adapter. On the Nic Teaming page move all but one network adapter to Unused, so that there is only a single network card active. From the Storage Adapters configuration page, edit the Software iscsi adapter. Add the new VMkernel adapter on the Networking page and save settings. For each protected system, choose a recovery point and click iscsi Start to export the disks. From the VMware Client, select Storage Adapters from the Configuration page. Select the Software iscsi adapter and click Rescan All from the top right of the page. Once complete the newly exported iscsi disks should appear in the lower storage management window. It is recommend to change the default LUN names to a friendly name to simplify identification later. (i.e. change to <Server>_<Drive>) As with the NFS Recovery procedure above, create a new Guest server stored on the Replibit data store. When selecting disks, choose Raw Disk and select the discovered iscsi disks exported from the Replibit device. Boot the new Guest server on the VMware host and complete any reconfiguration necessary to return the system to service Relocating Back to Local Storage Once the host server storage has been repaired, perform the following steps to migrate the recovered systems from Replibit back onto local storage. If you own VMware licensing and have a vcenter server you may use Storage Migration from the VMware Client to easily relocate the guest system and storage back to the host. Enterprise license owners can perform this operation while the guest is up and running, others will be required to power off the protected system first. From the VMware Client, attach to vcenter and select the desired guest. Right-click and select Migrate. Chose Change Host and 24

Storage Location and complete the remaining steps to pick a new host and storage location for the system. If recovering using iscsi, in order to force the conversion of the Raw Disk (RDM) volumes into a VMDK, when choosing the storage location choose Advance. For each disk, explicitly select either Thick or Thin as the destination format. Those without vcenter licensing will have to perform a migration from the ESX host shell. If you have not already done so, enable and start the ESXi Shell and optionally the SSH server on the host. From Security Profile in host Configuration, select Properties from the Services section. Start ESXi Shell, and optionally SSH to enable access to the server command line interface. Use vmkfstools to perform a disk conversion of the protected systems disks and onto local storage. Shut down the protected system and log in to the ESX shell as root. Copy the Guest virtual machine definition onto local storage: cp -R <src> <dst> (i.e. cp -R /vmfs/volumes/replibit/server01 /vmfs/volumes/datastore1) Run the conversion command as follows: vmkfstools -I <src path> <dst path> -d <thick thin> (i.e. vmkfstools /vmfs/volumes/replibit/server01_2016_02_01_11_00_00_pm_vmdk/ 57501948_e06c_4d4a_91e6_7ef6b7b689fe_C.vmdk /vmfs/volumes/datastore1/server01/c.vmdk -d thin) Note that when typing names in the shell you may use the tab completion to make entering long file paths easier. Type the first few letters and press <Tab> to complete the name. If the name is not unique, press <Tab> twice to list all matching possibilities. Type a few more letters and press tab again. There is not progress displayed during the conversion. Wait for the shell command to return a new command line prompt. You can monitor activity from the Performance tab by observing disk read/write statistics. Once the conversion is complete, perform the following: From the VMware Client, select the protected system and remove it. (Do not delete from disk!) From Configuration select Storage and browse the local Datastore. Open the folder containing the recovered server, right-click the.vmx file and import the Guest into ESX. Edit the Guest configuration and remove all hard disks. (Do not delete from disk!) Save and edit the Guest again and then Add Disks. Browse to the converted VMDK files within the local Datastore. Save and boot the Guest. 25

Hyper-V Recovery Options Any of the Bare Metal Recovery options previously discussed may be used when rescuing protected systems back into a Hyper-V environment. In addition, the following options are also available. NFS Recovery In a Hyper-V environment it is possible to utilize the NFS Export feature of the Replibit Appliance or Vault to simplify and expedite recovery of protected systems when the underlying storage of the host server has been compromised, but the physical host is still in operation. In order for this method to be employed, verify that there is sufficient free space remaining on the Appliance or Vault to hold the entire thick provisioned disk size for all protected systems you intend to recover. If insufficient disk space remains, refer to Hyper-V iscsi Recovery below. To begin recovery of the affected protected systems, from the Web GUI select a recovery point for each protected system that you wish to restore and choose EXPORT. Select VHD as the format for Windows Server 2008 or Windows Server 2012 (Gen 1) guest, or VHDX for Windows Server 2012 R2 (Gen 2) guests. Click Start to begin the Export process. Monitor the progress of the operation from the Jobs menu on the Conversion tab. For better performance it is recommended not to select Export to USB. If you require additional space to perform the export, it is recommended to use the Hyper-V iscsi Recovery method instead. From the Web GUI navigate to the NFS Exports menu and select Enable NFS Exports. On a Vault, you will have to be logged in as a user account in order to see this option. If not already present, click Add Allowed IP and add the IP address of the Hyper-V host server. In multi-server environments, add all hosts addresses if desired to enable failover cluster operations between hosts. Install and configure NFS Client services on the Windows Hyper-V hosts. Run Server Manager and select Roles and Features. On Windows Server 2008/R2 select Features, expand File Services Tools and select Services for Network File Systems Tools. On Server 2012/R2 choose Add Roles and Features, select Role Based or Feature Based installation and then select the local server. Enable Client for NFS under Features selections. For all version of Windows, mount the remote NFS share from a command prompt. Run the following for an Appliance: Mount o fileaccess=777 \\<Appliance IP>\export\admin <Drive:> (i.e. mount \\192.168.0.10\export\admin Z:) Run the following for a Vault: Mount o fileaccess=777 \\<Appliance IP>\export\<Customer> <Drive:> (i.e. mount o fileaccess=777 \\192.168.0.10\export\customer1 Z:) Create a new Hyper-V Guest as per normal. When selecting hard disks, Hyper-V does not allow virtual disks to be located on NFS storage. You will have to first copy the disk images to local storage on the host server. Browse to the location that you copied the disk volume images to and selected the exported VHD/VHDX file(s). Power on the guest server and complete any required configuration 26

changes to the running system to return it to service. The recovered system may be run indefinitely from Replibit storage while waiting for repair or replacement of the failed host system storage array. iscsi Recovery If disk space on the device is constrained, iscsi export can be used to expose the protected system disks to Hyper-V. This has the advantage of being faster, as we do not have to wait for the Export conversion process, but iscsi is also more fragile. Currently, iscsi exported disks are not persistent through a reboot of the Replibit device. The disks will have to be rediscovered and guest servers will have to reconfigured if the Replibit device is rebooted. Data changes applied to the iscsi disks may be lost in this event. It is recommended to use iscsi Export with caution, and at present NFS Export is to be preferred. If using this iscsi Export method, ensure that protected system backups are proceeding successfully and increase the backup frequency to alleviate possible data lost in the event of a device reboot while the recovered systems are running from Replibit storage. Complete the steps listed above to enable NFS Exports and add the Replibit device as an NFS storage location to your physical Hyper-V hosts. This will provide a location to hold the Guest server definition and temporary file storage if necessary. For each protected system select a recovery point and click iscsi Start to expose the disks to Hyper-V. From Administrative Tools on the Hyper-V host run iscsi Initiator. Enter the IP address of the Appliance or Vault in the Target field and click Quick Connect. Select each discovered disk and click Connect to attach it. Click Done when finished. Note: When adding additional servers you can click refresh to discover the new disk LUNs. In order to enable a disk to be eligible for use as a pass-thru disk to a Guest system, the disk must be offline. Open Computer Manager and expand Storage, Disk Management. Identify the new system disks and set them Offline if necessary. Open Hyper-V Manager and create a new Virtual Machine. If your primary storage array has been lost you may select Store the virtual machine in a different location and browse to the NFS share. Make a new folder for Virtual Machine definitions. Complete the creation of the Guest and assign resources as desired. When choosing hard disk options, select Attach a Virtual Disk Later Once completed, edit the settings of the new Virtual Machine. Select the IDE (Gen 1) or SCSI (Gen 2) controller and add a hard disk. Select Physical Disk and choose the desired disk to assign. Relocating Back to Local Storage Once the host server storage has been repaired, perform the following steps to migrate the recovered systems from Replibit back onto local storage. Shut down the Guest Virtual Machine, as this process cannot be completed while the machine is running. For systems using iscsi disks, you must first enable access to for the Hyper-V host. Open Computer Management, expand Storage and select Disk Management. Right-click the disk label and select Online to enable access to the host server. Open Hyper-V Manager. Right-Click Hyper-V from the left toolbar and select New Disk. Select disk format (VHD or VHDX) and type (Fixed or Dynamic, do not choose Differencing) and specify a location. For NFS Exported disks, select Copy the contents of an existing virtual disk and browse to the virtual disk 27

file. For iscsi Exported disks select copy the contents of a physical disk and select the appropriate disk. Click Finish and wait for the conversion process to complete. When completed, edit the virtual machine and replace the existing disks with the newly created virtual disk files. If the Virtual Machine definition was created on Replibit NFS storage, delete the virtual machine and recreate it on Local Storage. Attach the virtual disks created above and reboot the server. Replibit Recovery Recovery Toolkit NOTICE: These tools are provided for emergency data recovery purposes only. Using any of these tools in production is strictly AT YOUR OWN RISK. Replibit does not support the usage of these tools in any way and will not be held liable for any damages caused, whether accidently or intentionaly, by any usage of these utilities. Replibit specifically refuses to respond to any ticket or support requests involving usage of any of these tools or applications. WARNING: Usage of any of the following tools or utilities on your production environment may cause irretrievable data lost or disk corruption if used improperly. Usage of these tools is unsupported and STRICTLY AT YOUR OWN RISK Recovering Deleted Files Data Recovery is a portable file undelete utility. Scans local disks for deleted files and attempts to recover them if possible. Note that deleted files may be damaged or partially overwritten and recovery may not be possible. Select the drive to scan, enter an option search string and click Scan to look for files. Select files found and click Recover to restore deleted files 28

Disk Defragmentation Auslogic DiskDefrag is a free and powerful disk defragmentation utility that supports analysis, file defragmentation, and file system optimization for SSD drives. Partition Management AOMEI Partition Assistant Lite is a free and powerful partition management utility. Create, Delete, Copy, Move, Resize, Split, or Copy partitions. Also available are options to perform an integrity check or alter the partition alignment on disk. 29

Secure Erase Disk Wipe is a free utility to perform secure disk erase operations. Choose the desired disk, click Wipe Disk and complete the wizard to set the disk erase options. Offline Registry Editor Remote Regedit is a utility for manipulating the registry of an offline Windows system. Launch Remote Regedit from the Taskbar. The application normally auto-detects the offline Windows environment, but if it fails to locate it a popup will appear. Select the Windows folder from the system you wish to edit. 30

Partition Table Recovery and Repair TestDisk is a powerful free data recovery application. It was primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software: certain types of viruses or human error (such as accidentally deleting a Partition Table). Notice: This application directly modifies disk partition tables and file systems and CAN DESTROY YOUR DATA if used improperly. Please consult the included documentation and be sure you understand what you are doing before using this application. Use of this program is strictly AT YOUR OWN RISK and Replibit will not be responsible for any damages or lost data incurred by usage of this utility. Replibit offers no support or assistance with this or any other data recovery utility in this distribution. 31

Windows NT Password Editor NTPasswordEdit is a free utility to reset or clear user passwords on an offline Windows environment. Select the SAM database file of the offline Windows environment. Discovered users are enumerated. Select a user account and click Unlock or Change Password to modify it. Note: If used on a Windows Domain Controller, this application will modify the Active Directory Recovery user password, NOT the Active Directory domain users. Hardware Device Identification PCI-Z is a free and user friendly hardware device discovery tool. System hardware is interrogated and a list of discovered devices is presented, showing manufacture and model, etc. 32

File Backup, Comparison, and Synchronization FreeFileSync is a powerful file comparison and folder synchronization tool. Replicate files and folders between different hard drives, network shares, or even cloud storage via SFTP. Compare and highlight differences between folders, including extra, missing, or changed files and folders. Benchmarking Parkdale is a fast, simple disk speed benchmarking utility. Profile read and write speed, as well as measure random seek performance and IOPS. 33

Anti-Virus Utilities Included in the toolkit are links to Eset and BitDefender online virus scanning tools. Note that both of these utilities will only run under Firefox when launched from within the recovery environment. Also, both utilities are extremely memory intensive and will fail to launch properly with less than 3GB of RAM Note: Currently, the Antivirus scanning utilities only run under x86 mode. Portable Toolkit Many of the utilities included within this distribution are just as useful in a live environment as they are when recovering or troubleshooting a failed system. With this in mind, we have included an Autorun menu utility to make these utilities available anywhere. Just insert your RRT DVD or USB drive in any running system, and Windows Autorun will launch the menu. 34

Creating a Bootable USB Stick Use Rufus (Included in the Portable Apps folder) to create bootable USB images of the source ISO Note, after selecting the ISO image file, be sure to reset the File System type to FAT32 35