Glossary

A Windows machine used externally from the Appliance host to perform the upgrade. We recommend that you use a laptop for this process because the Forge Hardware Appliance build and the configuration procedure requires a direct connection to the Dell Hardware that is used as the Forge Appliance Host.

Software that uses either a terminal console (getty) or a proprietary, browser-based interface (Forge Appliance Configuration Console or Forge ACC) to connect directly to an appliance for installation and configuration purposes (for example, setting the Host/VM IP addresses, Hostnames, and user password configuration).

The version of appliance management software used to manage network settings on the Forge ESX Host and the Forge Appliance VM. Appliance (version) 1 uses a getty interface, appliance (version) 2 uses the Django Web framework and the ACC interface. Appliance version updates are motivated primarily by changes to the underlying VMware ESX version.

You can determine the appliance version of your Forge unit by using one of the following methods:

• Forge Web Client: Look up the appliance version number in the Help > About page of the ACC. You can only do this if you are reconfiguring Forge.

• Local Configuration Interface Type: Connect a monitor to the appliance and power it on. If the system displays the blue screen of the Forge Console, your appliance version is 1. If the system displays the ESX configuration screen, your appliance version is 2.

• Remote Configuration Interface: Using a Web browser and the IP address of your Forge unit (http://<forge_esx_server>:1000), attempt to launch the Forge Appliance Configuration Console (ACC). If you are able to connect, your appliance version is 2.

The process of exporting existing database data, which includes existing workloads and contracts. This process also backs up the VMs that reside on the datastore local to the Forge Appliance Host.

Exported data for the protection contracts. The upgrade utility stores this in a .zip file.

See also protection contracts.

A Forge Appliance Host containing a virtual machine running a Microsoft Windows OS with Forge software installed.

Dell hardware (PowerEdge 1950, 2950, R610, R710, R620 or R720) shipped by PlateSpin partner Avnet, Inc. The version of PlateSpin Forge you purchase is installed on a particular Dell model. For more information, see Section 1.1, Possible Forge Configurations.

The VMware ESX software running on supported hardware.

The executable file that upgrades the Forge Appliance software. The executable (also referred to as an “upgrade utility,”) is included in the Forge 11 Upgrade Kit.

PlateSpin software engineered by NetIQ to protect a specific virtual workload (that is, an ESX VM’s operating system, middleware, and data) by using virtualization technology. If there is a production server outage or disaster, a virtualized replica of a workload can be rapidly powered on within the target container (a VM host), and continue to run as normal until the production environment is restored.

(Also output folder). The network location where important backup data is stored on the administrative computer. For example, D:\forge_backup\out.

A collection of currently-active settings pertaining to the complete lifecycle of a workload’s protection (Add-inventory, initial and ongoing Replications, Failover, Failback, and Reprotect).

The process of configuring the Forge Dell hardware, the Forge ESX Host, and the Forge Appliance that is running on Windows 2003 Server.

The process of importing existing database data (including workloads and contracts) as it existed prior to backup. The process also restores all local VMs that formerly resided on the Forge Appliance Host.

The network location where the Forge upgrade kit is copied. For example, D:\forge_backup\11.0_kit.