Installing the vCloud Availability On-Premises Client

 

This guide walks through deploying and configuring the vCloud Availability (vCAV) client appliance in your on-premises vSphere environment.

Prerequisites

Before you begin, ensure you have:

  1. Subscribed to the DRaaS Service: Contact your manager to activate the service and obtain the necessary attachment point address.

  2. Network Prepared: Verify your Edge Gateway is correctly configured with the required networks and SNAT rules.

  3. Downloaded the Appliance: Download the OVA file from the VMware Customer Connect portal (requires registration):
    Download VMware vCloud Availability Appliance 

 

Step 1: Deploy the OVA Template

Deploy the downloaded OVA file into your on-premises vCenter using the standard deployment workflow.

  1. Provide a Name and select a Folder/Cluster for the appliance.

  2. Select a Resource (host/cluster) for deployment.

  3. Review Details and accept the EULA.

  4. Select a Storage destination and a Network for management.

Step 2: Configure the Appliance

During OVA deployment, you will be prompted to configure the initial template settings:

  • Root Password: Set a strong temporary password for the root user. (You will be forced to change this upon first login).

  • NTP Server: Enter the address of your organization's NTP server for time synchronization.

  • Network Settings: Configure the IP address, subnet mask, gateway, and DNS for the appliance.

Complete the deployment and power on the virtual machine.

Step 3: Initial Setup via Web Console

  1. Note the IP address assigned to the VM from the vSphere console.

  2. Open a web browser and navigate to the admin portal: https://<appliance_ip_address>/ui/admin

  3. Log in with the username root and the temporary password you set during deployment. You will be prompted to set a new password.

  4. Click Run initial setup wizard to begin configuration.

Step 4: Connect to vCenter and the Cloud

In the setup wizard, provide the following information:

  1. Lookup Service Connection:

    • Address: The URL of your local vCenter Server SSO (Lookup Service).

    • Credentials: The username and password for a vCenter Single Sign-On administrator account.

    • Certificate: Accept the vCenter SSL certificate when prompted.

 

2. Public API Endpoint:

  • Address: https://vcav-m14.cloud4y.ru:443/ (Provided by your manager)

3. Organization Credentials:

  • Admin: user_name@name_tenant (Your vCloud Director organization administrator account)

  • Password: The password for the above account.

4. Cloud Access:

  • Enable Allow Access from Cloud. This permits vCloud Director administrators to access your on-premises vCenter for migration tasks. This can be enabled or disabled as needed for security.

5. Local Placement (Optional):

  • If you enable Configure local placement now, you can pre-define where VMs migrated from the cloud to your on-premises vCenter will be placed.

6. Click Finish to complete the initial client installation.

 

Step 5: Initiate Migration

Once configured, you can start migrations from within your vCloud Director portal.

  1. In vCloud Director, navigate to More > vCloud Availability (M14).

  2. Choose Migration Direction:

    • From On-Prem: To migrate from your local vCenter to the public vCloud.

    • To On-Prem: To migrate from the public vCloud back to your local vCenter.

Have you tried Cloud4U services? Not yet?

Visit Website

Try for free

  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

vCloud Availability Overview

vCloud Availability is a VMware solution that enables disaster recovery and migration for your...

Getting Started with vCloud Availability (vCAV)

vCloud Availability (vCAV) enables disaster recovery and live migration for your workloads. For a...

Working with vCloud Availability (vCAV)

vCloud Availability (vCAV) is a comprehensive solution for disaster recovery and seamless...

Getting Started with CLOUD4U Object Storage

Cloud4U Object Storage is an S3-compatible storage service built on the Cloudian platform. It...