Deploy the OVA Template in ESX

You must deploy the OVA template before installing the Mirage Gateway server.

About this task

The .ova file is located in the Mirage installation package.

Prerequisites

Verify that VMware ESX® is installed to deploy the OVA template.

Procedure

Double-click the.ova file and click Run to start the deployment wizard.
Provide login credentials for the Mirage, and click Login.
In the Mirage console, select File > Deploy OVF Template to start the deployment wizard.

Deploy the OVA template and click Next.

Option	Description
File	You can specify a location that is accessible from your computer, such as a local hard drive, a network share, or a CD/DVD drive. To select a file location, click Browse.
URL	You can type a URL to download and install the OVA package from the Internet.

Option

Description

File

You can specify a location that is accessible from your computer, such as a local hard drive, a network share, or a CD/DVD drive.

To select a file location, click Browse.

URL

You can type a URL to download and install the OVA package from the Internet.

After the OVA template is verified, a green check mark appears next to the publisher name.

Verify the OVA template details and click Next.
Accept the end user license agreement and click Next.
Enter a name, select a location for the deployed template, and click Next.
Select the host and cluster and click Next.
Select the resource pool and click Next.
Select a storage destination for the virtual machine files and click Next.

Select the disk format and click Next.

Option	Description
Thick Provision Lazy Zeroed	Create a virtual disk in a default thick format. Space required for the virtual disk is allocated when the disk is created. Data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine. Virtual machines do not read stale data from the physical device.
Thick Provision Eager Zeroed	Create a type of thick virtual disk that supports clustering features such as Fault Tolerance. Space required for the virtual disk is allocated at creation time. In contrast to the thick provision lazy zeroed format, the data remaining on the physical device is zeroed out when the virtual disk is created. It might take longer to create virtual disks in this format than to create other types of disks.
Thin Provision	Use this format to save storage space. For the thin disk, you provision as much datastore space as you expect the disk to require based on the value that you enter for the virtual disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations. If the thin disk needs more space later, it can grow to its maximum capacity and occupy the entire datastore space provisioned to it. Thin provisioning is the fastest method to create a virtual disk because it creates a disk with just the header information. It does not allocate or zero out storage blocks. Storage blocks are allocated and zeroed out when they are first accessed.

Option

Description

Thick Provision Lazy Zeroed

Create a virtual disk in a default thick format. Space required for the virtual disk is allocated when the disk is created. Data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine. Virtual machines do not read stale data from the physical device.

Thick Provision Eager Zeroed

Create a type of thick virtual disk that supports clustering features such as Fault Tolerance. Space required for the virtual disk is allocated at creation time. In contrast to the thick provision lazy zeroed format, the data remaining on the physical device is zeroed out when the virtual disk is created. It might take longer to create virtual disks in this format than to create other types of disks.

Thin Provision

Use this format to save storage space. For the thin disk, you provision as much datastore space as you expect the disk to require based on the value that you enter for the virtual disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations. If the thin disk needs more space later, it can grow to its maximum capacity and occupy the entire datastore space provisioned to it.

Thin provisioning is the fastest method to create a virtual disk because it creates a disk with just the header information. It does not allocate or zero out storage blocks. Storage blocks are allocated and zeroed out when they are first accessed.

Complete the deployment wizard.

Results

The OVA template is deployed.