Axcient Help Center

Export to VMDK

The Export to VMDK tool allows you to deploy VMware-specific, identical virtual machine replicas of physical devices.

The Export to VMDK recovery feature is only available for devices backed up by an Axcient Appliance using AxOS 6.4 or later. To view the AxOS version the Axcient Appliance, refer to the Service Details page of the Web Application User Guide.

Generating the .vmdk Files
  1. On the Web Application, click the Recover button.

  2. On the Recover Something screen, click the Make it Virtual option.

  3. On the Virtualize a Device screen, select the Export to VMDK option.

  4. On the Export to VMDK screen, select the desired device and click the Next button.

    A device with a Running VM Status indicates that a VM is currently running for that device. You can still continue with the recovery process, but you will be prompted to stop the VM to continue. See the VMDK Alert Messages section for more information about alerts you might encounter when selecting a device.

  5. On the Recover From screen, select the desired recovery point and click the Recover button.

  6. A UNC mount point will generate. Copy the UNC mount path and set the UNC mount expiration timer.

  7. Paste the UNC mount path into a File Explorer window. Two .vmdk files will display.

VMDK Alert Messages

You might encounter one of the following alert messages after selecting a device. Below are descriptions of each alert.

Alert: Virtualized Device in Production

You will receive this alert when the selected device is currently virtualized in a Production environment.

Click the Proceed button to stop the VM and generate the VMDK for the selected device.


Alert: Virtualized Device in Test

You will receive this alert when the selected device is currently virtualized in a Test environment.

Currently, Axcient does not support Exporting to VMDK from a Test failover.

You will need to manually shut down the Test VM or select a different device.


Alert: Running BMR

You are unable to use the Export to VMDK feature for a device currently running a BMR.

You will need to wait until the BMR has completed before exporting to VMDK.


Alert: Exposed Mount

The Export to VMDK feature has already been performed on the selected device, exposing a UNC Mount point containing the VMDK files.

Click the Revoke Exposed Mount button to erase the previous UNC mount and generate a new one. Alternatively, click the Back button to select a different device.

Check the Activities of Interest on the Web App Dashboard or Site Details page to view the currently exposed UNC Mount point.


Alert: Device Not Ready

The device is unable to perform the Export to VMDK recovery process because the selected device is currently in use, or is otherwise unavailable.

Click the Close button to exit the Export to VMDK process, or press the Back button to select a different device.

You will need to wait for the device to become available before trying again. You can investigate the device to check if there are any actions that can be taken to make the device available.

Creating a VM using Export to VMDK

The Export to VMDK tool allows you to generate a VMware compatible target to perform failover or recovery to a virtual host. When you complete the export process, you can use the exported files to create a Virtual Machine.

To create a Virtual Machine using an exported .VMDK file:

  1. In the VMware vSphere, select the Host Machine, click the Configuration tab, and then right click the datastore and select the Browse Datastore option.

  2. Click the Upload button and upload both .vmdk files from the UNC mount point generated above.

  3. Create a new virtual machine and configure it as needed.

  4. On the Configuration screen, select the Custom option and continue with configuring the VM as needed.

  5. On the Guest Operating System screen, select the appropriate OS from the drop-down menu. The OS should match that of the device from which the Export to VMDK process was performed. Click Next to continue configuring the VM as needed.

  6. On the SCSI Controller screen, select the SCSI controller:

    1. Select the LSI Logic Parallel radio button for a Windows 2003 OS.

    2. Select the LSI Logical SAS radio button for every other Windows OS.

    Click the Next button to continue.

  7. On the Select a Disk screen, select the Use an existing virtual disk option. Click the Next button to continue.

  8. On the Select Existing Disk screen, click the Browse button to browse the datastore and select the exported VMDK. Click the Next button to continue.

  9. Review the VM configuration. When ready, click the Finish button. If there are no more hard disks, the VM can now be powered on. If more hard disks need to be added, check the Edit the virtual machine settings before completion box and continue to the section below.

  10. On the same Virtual Machines Properties screen, click the Add button.

  11. You will now need to go through the Add Hardware process. On the Device Type screen, select the Hard Disk option from the menu and click the Next button.

  12. On the Select a Disk screen, select the Use an existing virtual disk option, and then click the Next button.

  13. On the Selecting Existing Disk screen, click Browse and navigate to the .vmdk files uploaded above. Although two files were uploaded, you will only see one large .vmdk file.

  14. If necessary, configure any advanced options on the Advanced Options screen. In most instances, no further action is needed unless required on the specific virtual machine environment. Click the Next button to continue.

  15. Review the selected options. When ready, click the Finished button. The new disk has now been added. Repeat this process for as many disks as required.

  • Occasionally, when a customer deploys a VMDK for a Windows 2003, 2008 or 2012 device, the network settings might not be preserved.

    You must manually configure the IP address for the device using the generated VMDK. You can use any preferred method of configuring an IP address for the device.

  • Occasionally, when a customer deploys a VMDK for a Windows 2008 R2 device, one disk might be listed as offline when using any number of extended disks.

    To resolve this issue:

    1. Ensure the device created using the generated VMDK is powered on.

    2. Navigate to the Disk Management utility (sometimes called Computer Management).

    3. Right click the offline drive.

    4. Select the Online option.

    5. Exit the Disk Management (or Computer Management) utility.