vRanger 3.x.x - Create a virtual machine for vmware server with the ESX3 VM / Ranger 3.x.x tvzc (4046618)

How to restore a vRanger 3.x.x backed up ESX 3.x VM to VMware Server ( non-ESX )

This document offers a detailed explanation of how to run esxRanger Professional backups from VMware Infrastructure 3 (VI3) on VMware Server or GSX Server.

Proviso message: This is only for use in running VI3.x VMDKs on a contingency basis in VMware Server or GSX Server.

It is always recommended that you restore your esxRanger Professional backups to VI3.

But in the event that you are using a high performance laptop or PC that can run VMware Server or GSX Server, this "how-to" document outlines the process to restore an esxRanger Professional VI3 VMDK to disk for use with VMware Server.
Process:

• Copy esx Ranger backup TGZ to where VMware Server is installed.
  • If your backups are on a VMFS or Linux volume, use FTP, WinSCP or SFTP (SSH) to copy them to the locations where VMware Server/GSX Server is installed.
  • If your backups are on a Windows® unit other than where the VMware Server is installed, then copy the TGZ to the unit running VMware Server/GSX Server.
• Install & uncompress the *TGZ archive using bsdtar – available at http://www.vizioncore.com/downloads/ProductSupport/bsdtar.zip
  • We have a Reg key that can be downloaded. Once imported, this key will provide the functionality to just double click a TGZ and it will automatically extract in the same directory.

Example of working bsdtar command >

• • The Reg key bsdtar.reg is located in the bsdtar.zip downloaded from the location referenced above. Run it by double clicking on it.
• Once the files are uncompressed, you will need to rename the test.vmdk.vzsnap to test.vmdk This file should be 1K in size. Text editors such as UltraEdit-32 can be used to edit the header file.

Support Technical Document 11/21/2006

A working VMware Server header file looks like this:
# Disk DescriptorFile
version=1
CID=e311f426
parentCID=ffffffff
createType="monolithicFlat"
# Extent description
RW 4096000 FLAT "Jason-M-flat.vmdk" 0
# The Disk Data Base
#DDB
ddb.geometry.cylinders = "1000"
ddb.geometry.heads = "128"
ddb.geometry.sectors = "32"
ddb.virtualHWVersion = "4"
ddb.toolsVersion = "7201"
ddb.adapterType = "lsilogic"
*Exact notation in the header file is critical*

Your VI3 header file will need the following lines changed to support VMware Server.

createType="vmfs"
Change To
createType="monolithicFlat"

RW 4096000 VMFS "Jason-M-flat.vmdk"
Change To
RW 4096000 FLAT "Jason-M-flat.vmdk" 0

ddb.adapterType = "legacyESX"
Change To
ddb.adapterType = "lsilogic"

If the ddb.adapterType is lsilogic or buslogic, nothing has to be done with this line.

Note: items in bold are what needs to be changed.

After completing this process, create a new virtual machine (VM) in VMware Server/GSX Server, directing the new VM wizard at the header file VMDK at the prescribed time.
This should result in a normal VM boot. If you get a virtual device error message or the standalone VM handler prompts you to create a new VMDK on boot attempt, recheck your header notation.