Supported operating systems and features

Any x360Recover Direct-to-Cloud (D2C) protected system (regardless of OS version) may be recovered using Recovery Center.

Supported operating systems for running Recovery Center include:

• Server 2008 R2 or newer 
• Windows 8 64-bit or newer

Note: Recovery Center installation is not supported on a Windows domain controller.

For Hyper-V virtualization, supported operating systems are:

• Server 2012 R2 or newer, with Hyper-V role enabled 
• Windows 10 64-bit or newer, with Hyper-V feature enabled 

Release 1.5.0 supports file and folder recovery, virtual disk export, and manual or wizard-ized Hyper-V virtualization. 

Bare metal recovery (BMR) from local cache is supported separately with the x360Recover Recovery Toolkit ISO. 

Rapid data recovery for offsite protected systems

Recovery Center provides quick access to your offsite protected systems, whether they are located on an Axcient-hosted vault or a self-hosted private vault. Recovery Center is optimized to function best with D2C protected systems employing a local cache repository (which accelerates data recovery.) However, any system present on the vault may be recovered over the WAN.  

Note: You may use Recovery Center to perform file and folder recovery for any protected system resident on a vault, with or without local cache, although performance without local cache will be subject to download bandwidth performance and, therefore, will potentially run much slower.

Install Recovery Center

Recovery Center is a 64-bit Windows application which supports various forms of  recovery for protected systems, natively, from within a Windows environment.

Note: A Linux-based version of Recovery Center is planned for the future.

We recommend that you install Recovery Center on one of the following:

• A 64-bit Windows system that is being protected via Direct-to-Cloud (D2C) backup
• A Hyper-V host that may be used to perform virtualization of systems being protected using Direct-to-Cloud with local cache
• A client or partner administrative workstation you wish to use for performing recovery operations

STEP 1. To install Recovery Center, download and run the latest installer package.

• Download Recovery Centerhere:

1.1. From the initial Setup page, click Next to continue:

1.2. On the Choose Installation Directory screen, specify the application folder where Recovery Center will be installed.

Then select the working directory:

After selecting the target installation locations, click Next to continue.

1.3. On the Select Components screen, accept the default selection and click Next to continue.

1.4. On the License Agreement screen, select I accept the license to accept the end user license agreement and click Next to continue.

1.5. On the Start Menu Shortcuts screen, specify or select the default Start Menu application folder and click Next to continue.

1.6.  On the Ready to Install screen, click Install to proceed with installation

If prompted, select Yes to elevate permissions and install the application as ‘Administrator’.

Recovery Center installation will proceed.

After installation has completed, click Finish.

Recovery Center component: Jobs Service

The xCloud Recovery Center Service runs in the background on the system to manage recovery jobs.  

This service is responsible for creating, managing, and deleting recovery jobs constructed via the User Interface on demand, as well as providing for persistence of job states through reboots and system shutdowns.

A recovery job defines:

• type of recovery to be performed (currently limited to file and folder recovery)
• client
• protected system
• backup snapshot to recover data for
• authentication information
• how the selected protected system disk volumes will be presented to the local machine.   

Recovery Center component: Virtual Disk Service  

The xCloud Virtual Disk Service is the core of the recovery engine, providing the means to transform remote recovery points into locally mounted block storage devices for data retrieval. 

Jobs defined in the User Interface and managed by the xCloud Recovery Center Service are executed by the xCloud Virtual Disk Service.  

Cloud metadata is used to define the physical disks and volumes.  Data is retrieved first from the local cache repository (if present) then over the WAN from the vault.  The local machine is then presented with virtual block storage devices matching the selected protected system recovery point.  The disk volumes from the selected protected system can be mounted to the local machine, either as new drive letters or as sub-folders within a selected folder.

The constructed recovery volumes are read-only in File Recovery mode, and employ a high performance copy-on-write layer in Virtual Disk and Virtualization modes to make volumes read/write.

Recovery Center component: DRAL 

The Disaster Recovery Access Layer (DRAL) is a service running on the vault, providing a secure data transport layer, authentication system, and metadata retrieval service.  

Recovery Center connects to DRAL in order to authenticate and browse protected systems and recovery points available on the vault. DRAL also transports any data not present within the optional local cache repository.

DRAL services are available on both Axcient-hosted vaults and self-hosted private vaults. Data for both appliance-based systems and D2C protected systems can be recovered with DRAL services

Recovery Center component: (Optional) Local cache 

An optional local cache repository, if available, can be used to greatly accelerate data recovery.  For details on configuring your Direct-to-Cloud backup agent to generate a local cache, see this knowledgebase article.

Steps across all recovery types  [See steps...]

Recovery Types share many steps when you are creating a new recovery process. 

1. Recovery Target 

Click inside the Client field and begin typing to search for a client. You can also scroll the list. You may need to wait for the list of available clients to complete downloading. 

Select the desired client in the Results field.

Once a Client has been selected, the Data Source field will be populated with all vaults containing protected systems for that client. Select the Data Source and Protected System you wish to recover. 

Note: Beginning with x360Recover 10.18.0, you can also select a local appliance as the data source for protected system recovery.

All appliances registered to the client will be displayed in the Data Source list, but only devices accessible from the recovery system’s local LAN network will be accessible for protected system recovery operations.

Why connect to appliances?

Connecting to an appliance with Recovery Center is useful in various scenarios:

• You might wish to run a direct Hyper-V virtualization from an appliance using Recovery Center.
• You might opt to provide file and folder recovery where Active Directory security permissions are required to be maintained -  without the extra complexity of using iSCSI.

2. Recovery Point 

This page initially displays the most recent date for which recovery points exist. Use the calendar select to choose a date. Days with orange highlights have available recovery points. 

After the Snapshot Time field populates, click a Time to select it. 

3. Recovery Path 

You may enter an optional Recovery Description for this recovery job to help identify it on the Recovery Center Home page. 

Use the radio buttons to select Restore directly from cloud or Restore using a local cache. 

• From the Cloud: All data will be accessed remotely over the WAN using the Disaster Recovery Access Layer (DRAL). 
• From Local Cache: The Local Cache repository will be searched first for requested data blocks. If a block is not available, it will then be retrieved over the WAN. 
  • Note: Even if a substantial amount of data is not present in the Local Cache, using Local Cache is recommended to dramatically accelerate recovery. Any missing data will be downloaded directly from the Cloud. 
  • Click Browse to select a Local Cache location on the protected system or attached storage device. 
    • If the Local Cache is located on a network share, you must enter the path in UNC format. For example: 
      \\<server>\<share>\<folder
  • For a Local Cache located on a network share, enter the Network Share Username and Password and click Check Credentials. Otherwise, leave these fields blank. 

4. Confirmation 

You may close this window and the recovery job will continue to run as a background service. Active jobs will be restarted automatically on a reboot of the system.

Virtualize (Hyper-V) [See steps...]

Automatically create a Virtual Machine of the Protected System within the locally installed Microsoft Hyper-V host system. 

1. UNIQUE STEP: Select Make it a Test or Put it in Production. 

• Test Mode: Virtual Machines will default to having no network connectivity. If you choose to add a network connection, ensure the selected network has no access to the internet or the same subnet as the running production version of this protected system. 
  • When deleting Test Mode virtualize jobs from Recovery Center, the default action will be to also delete the Hyper-V guest virtual machine from the host. 
• Production Mode: Virtual Machines will default to at least one network connection. You should ensure the selected subnet has access to the internet, and ideally the same subnet as the original protected system. 
  • When deleting Production Mode virtualize jobs from Recovery Center, the default action will not be to also delete the Hyper-V. You should perform a live storage migration or otherwise take steps to preserve the recovered production system before deleting the Recovery Center job. 

2. Common Step: Recovery Target 

Click Next. 

3. Common Step: Recovery Point. 

Click Next. 

4. Common Step: Recovery Path. 

Click Next. 

5. UNIQUE STEP: Use the checkboxes to select which physical disk(s) present in the snapshot you wish to recover. The disk volumes will be exported in Static or Thick format for better performance. Click Next. 

6. UNIQUE STEP: Enter a Name for the Virtual Machine, specify RAM and CPU Cores to assign the system, and select a Network subnet if desired. You may click Add Network Adapter to assign multiple networks to the virtual machine. 

Recovery Center can usually identify if the Protected System requires Generation 1 or Generation 2. If not, select the appropriate Virtual Machine Type.  

By default, Recovery Center will boot the virtual machine once the virtual disk export is completed and the Hyper-V virtual machine has been created. If this not desired, uncheck the box. 

Click Next. 

7. UNIQUE STEP: If you selected Hyper-V Generation 2 on the previous step, VHDX is required. For Generation 1, choose either VHD or VHDX disks. 

• If your system has any disk larger than 2TB, you must select VHDX to successfully export. 

The Location specifies where the Hyper-V virtual machine definition files will be created. It is recommended to use the default, but you can click Browse to manually select a location.  

Click Next.

8. UNIQUE STEP: Use the radio boxes to choose to Mount to Drive Letter or Mount to Filesystem Path.

One virtual disk will be created for each physical disk in your protected system. These volumes will be created in a virtual NTFS volume that may either be mounted with its own drive letter, or mounted as a subfolder of an existing drive path.

Note: The default file permissions on the synthetic NTFS volume grant full read/write permissions only to the local Administrators and Hyper-V Administrators security groups.

Click Start Virtual Machine to begin the Recovery Job. 

9. Common Step: Confirmation 

Virtual Disk Exports [See steps...]

Export a protected system as Virtual Disk Images. 

1. UNIQUE STEP: Select a Virtual Disk Type. Recovery Center supports all common virtual disk export formats for popular Hypervisor platforms, including a special format compatible with Microsoft Azure Cloud. 

2. Common Step: Recovery Target 

Click Next. 

3. Common Step: Recovery Point

Click Next. 

4. Common Step: Recovery Path

Click Next. 

5. UNIQUE STEP: Use the checkboxes to select which available disk(s) in the snapshot you wish to recover. By default, all disks will be included, and exported disks will be created as Static or Thick volumes. If you wish to export Dynamic or Thin volumes, click the checkbox. 

Click Next.

6. UNIQUE STEP: Use the radio boxes to choose to Mount to Drive Letter or Mount to Filesystem Path.

One virtual disk file will be created for each physical disk in your protected system. These volumes will be created in a virtual NTFS volume that may either be mounted with its own drive letter, or mounted as a subfolder of an existing drive path.

Note: The default file permissions on the synthetic NTFS volume grant full read/write permissions only to the local Administrators and Hyper-V Administrators security groups.

Click Start Virtual Export to begin the Recovery Job. 

7. Common Step: Confirmation 

File & Folder Recovery [See steps...]

Perform basic file and folder recovery with the Recover Files option. 

1. Common Step: Recovery Target 

Click Next. 

2. Common Step: Recovery Point. 

Click Next. 

3.Common Step: Recovery Path. 

Click Next. 

 

4. UNIQUE STEP: Use the radio boxes to choose to Mount to Drive Letter or Mount to Filesystem Path.

The disk volumes of the protected system you are recovering will be mounted to the local system. You can have each volume mounted to individual drive letters, starting with the first letter selected. (i.e. if the protected system has C, E, and F drives, you may choose to have them mounted beginning with drive G.) 

Alternatively, you can mount all volumes to a single file path. Subfolders will be created for each protected system volume. 

Click Start File Recovery to begin the Recovery Job. 

5. Common Step: Confirmation 

Bare Metal Restore [See steps...]

Bare Metal Restore is the process where a protected system image is written directly back to a new hardware system from an offline recovery utility. This is located on the x360Recover Bare Metal Restore Utility ISO, which includes troubleshooting and diagnostics utilities in a Linux Live ISO. 

Perform Hyper-V Recovery

To view, edit, and manage your new virtual machine, open Hyper-V Manager. 

When performing a production recovery, it is best practice to boot and run the virtual machine from the Recovery Center virtual export disks and perform a live migration of the storage volumes, once storage space becomes available. This might be done immediately if deploying to a new Hyper-V host system or after the original has been repaired. 

To perform a storage migration, select the virtual machine within Hyper-V Manager and click Move from the Action menu to open the migration wizard. 

1. Before You Begin:

Click Next. 

2: Choose Move Type: 

Select Move the virtual machine's storage and click Next. 

3. Choose Options for Moving Storage: 
Typically, select Move only the virtual machine's hard disks. The virtual machine definition and swap files are already located on the Hyper-V host and don't normally need to be relocated, unless you are configuring a failover cluster or other complex arrangement. 

The virtual disk files don't exist on storage at this point; they are being synthetically generated by Recovery Center from your backup data and Local Cache repository. To complete a production recovery, you must relocate these virtual disks to permanent storage before shutting down and deleting the job. 

Note: If you must reboot the Hyper-V host, Recovery Center will retain persistent changes made to the virtual machine environment and restart all services and virtual machines once the host has been rebooted.

4. Select Items to Move: 
Select all virtual disks and click Next. 

5. Choose a new location: 
Specify a path for each virtual disk and click Finish. 

Perform Virtual Disk Recovery 

Once the Status on the Home page indicates a job is Running, all disk volumes should be exported and present on the local machine at the path specified in the job creation. Use Windows File Explorer to copy and paste disk image files to another folder, or manually create a virtual machine using Hyper-V Manager on the local system. 

Perform File and Folder Recovery 

Once the Status on the Home page indicates a job is Running, all disk volumes should be mounted and present on the local machine. Use Windows File Explorer to browse, search, copy, and paste files and folders you wish you recover. 

Depending on your mount point selections, the volumes should either be listed as individual mounted drive letters or mounted within the folder path you specified during job creation.

Note: Since the recovery volumes are mounted as locally attached block devices, the original file and folder permissions from the protected system will be maintained.

Use Windows Explorer or other tools to copy files and folders from the mounted virtual recovery volumes back to the original system, network share, or other location. 

In Recover Files mode, all disk volumes are combined into a single virtual disk and mounted as a local block device on the recovery system. This disk is read-only by default and can be seen in Windows Disk Manager for reference. 

When creating the job, you have the option to make the volume Read/Write. If the system (and logged-in user to which you are mounting the volume) does not have Windows ACL permissions to the recovered disk volume(s), you will need to mount the volume in Read/Write mode - to allow making changes to the ACL permissions to enable access.

Note: Any changes made to the recovered volumes are stored locally in the copy-on-write file only. The underlying Disaster-Recovery-Access-Layer volume and the source snapshot are immutable. Deleting the recovery job and recreating it for the same snapshot will revert any changes made to the volume(s) in the previous recovery session.

Original Protected System: 

Recovery Center Volumes:

Specific errors

LoadLibrary failed with error 87

On rare occasions,  the Recovery Center UI may fail to load on certain systems, displaying the following error message during the application launch:

loadlibrary failed with error 87

This error is due to incompatibility with the hardware OpenGL driver.

In most cases, this issue can be resolved by configuring Recovery Center to use software rendering for OpenGL.

To enable software rendering, edit C:\ProgramData\RecoveryCenter\config.json 

and add the parameter “use_software_opengl”: true:

{

    "use_software_opengl": true

}

ATI Radeon bug

There is a known issue with QT and the ATI Radeon catalyst driver which sometimes causes this issue when loading the UI.

QT attempts to load the hardware OpenGL driver -  even when software rendering is requested.

The root cause of the issue is an incorrect registry entry, created when the AMD catalyst (AMD Radeon graphics drivers and application software package) was last installed.

To work around this issue, you may rename 

atig6pxx.dll 

to 

atig6pxx.dll.bak

(This file is usually located in C:\Windows\System32)