Running a Test Clone

A workload can be tested in cloud using a Test Clone.

This is especially useful prior to migration as a Test Clone leaves the on-premises VM running, moves an identical clone (snapshot) of the VM to the cloud of choice, and similar to the Run In Cloud operation, the workload is up and running in the cloud within minutes. Some additional notes:

  • It is highly recommended that a Test Clone be used in an isolated environment, to prevent network collisions with the on-premises live workload.
  • The Test Clone cloud instance is created in write-isolation storage mode (all changes are committed only in cloud and are not persisted back on-premises).
  • Only one Test Clone can be used for any specified VM at a time.
Run a Test Clone in GCP

1. On the vSphere Web Client, select the desired Virtual Machine.

2. Right-click on the VM and select Velostrata Operations > Test Clone.

3. Select the Velostrata Cloud Extension from the drop-down menu.

4. Give the Test Clone a new VM Name (optional, can use default populated value if desired).

5. Click Next.

6. Select the Instance Type (VM size) using the rightsizing recommendations as desired and click Next.

Additional notes: 

  • The prices are for compute cost only and do not include disk and network costs. 
  • If the VM has not been monitored for a sufficient period (7 days), a message appears indicating that the activity duration may be insufficient for accurate recommendations.
  • If the online price list is not available, no cost-optimized recommendations are provided.  

7. Select the desired subnet from the drop-down menu.

8. Enter the required Network Tags (comma separated), for example, velostrata. Network tags are used by networks to identify which instances are subject to certain firewall rules and network routes. For example, if you have several VM instances that are serving a large website, tag these instances with a shared word or term and then use that tag to apply a firewall rule that allows HTTP access to those instances.

9. Select the Instance Service Account (if desired) from the drop-down menu.

10. From the Configure Private IP drop-down list, select Auto to allow an available address on the subnet to be automatically assigned, or Static if a specific address assignment is required.

A. If you select Static, a Static IP field appears. Enter the required static IP for the instance or specify an ENI ID (e.g. eni-xxxxx) to associate a reserved Elastic Network Interface.

11. From the Edge Node drop-down list, select the required node.

12. Enter the External IP address name. This is the name for an external IP address created on the GCP console previously. If you select static, define that in the field that appears.

13. Click Next.

14. Review the summary and then click Finish.

The process of running the VM in the cloud can be viewed in the Cloud Instance Information portlet on the VM Summary page (or by monitoring the created vSphere task).

For clouds supported in previous editions of Velostrata:

AWS: To run a test clone:

Select the type of Windows license to use, that is, either reuse your on-premises license (Azure Hybrid Use Benefit) or use a cloud-provided license:

  • The Azure Hybrid Use Benefit is designed to help you to migrate to Azure without paying twice for the Windows license. If you have an existing on-premises Windows Server/Client license with active Software Assurance (SA), select to apply the Azure Hybrid Use Benefit. This enables you to reuse your on-prem license in the cloud.
  • When using the cloud-provided license, the Windows license is included in the instance charges, and may be as much as 40% of the instance cost. 

There is a built-in recommendation engine that provides cost- and performance-optimized recommendations. In order to provide an effective recommendation, Velostrata recommends monitoring the VM usage for at least 7 active days. For more information, see Monitoring VM Usage.

  1. On the vSphere Web Client, select the desired Virtual Machine.
  2. Right-click on the VM and select Velostrata Operations > Test Clone.
  3. Select the Velostrata Cloud Extension.
  1. Click Next.
  2. Select the Instance Type (VM size). Three options are recommended for performance-optimized VMs, and three options are recommended for cost-optimized VMs.
    Note: The prices are for compute cost only and do not include disk and network costs. Spot and reserved instances may also have price reduction plans.
    Note: If the VM has not been monitored for a sufficient period (7 days), a message appears indicating that the activity duration may be insufficient for accurate recommendations.
    Note: If the online price list is not available, no cost-optimized recommendations are provided.  
  3. Select On-Demand or Spot Market Bid for the Pricing Model. If you select Spot Market Bid, select the Defined Duration (No reservation or between 1 and 6 hours) and enter the $USD maximum price you are willing to pay for the spot.

Note: If you want to review the spot pricing history on the AWS site, click Pricing History.

  1. Click Next.
  1. Select the required Network Security Group.

Note: If you do not enter a Network Security Group the default Network Security Group configured for the Cloud Extension is used.

Note: If public access if required from the internet to the VM, a DMZ is required with an associated security group, including appropriate inbound and outbound rules.

  1. Click Next.
  1. Select a Subnet. Typically, the selection here would be of a private network subnet. When Cloud Edge nodes (A, B) are placed in different AZs, the Cloud Edge node in the same AZ as the selected subnet is automatically used, otherwise a manual node selection is required.
  1. From the Configure Private IP drop-down list, select Auto to allow an available address on the subnet to be automatically assigned, or Static if a specific address assignment is required.
  2. If you select Static, a Static IP field appears. Enter the required static IP for the instance or specify an ENI ID (e.g. eni-xxxxx) to associate a reserved Elastic Network Interface.
  3. From the Edge Node drop-down list, select the required node. When Cloud Edge nodes are placed in the same Availability Zone (AZ), a manual selection of the Cloud Edge node to use is required.
  4. Click Next.

Note: If you select to run your VM in a CE that is in the AWS Marketplace, the License Type is Marketplace.

 

  1. Review the summary and then click Finish.

The process of running the VM in the cloud can be viewed in the Cloud Instance Information portlet on the VM Summary page, and by monitoring the created vSphere task.

You can connect to the VM when the Remote Console field in the Cloud Instance Information portlet turns green and reads "Ready". You can connect to the VM using the private IP address or FQDN.

Azure: To run a test clone:

There is a built-in recommendation engine that provides cost- and performance-optimized recommendations. In order to provide an effective recommendation, Velostrata recommends monitoring the VM usage for at least 7 active days. For more information, see Monitoring VM Usage.

  1. On the vSphere Web Client, select the desired Virtual Machine.
  2. Right-click on the VM and select Velostrata Operations > Test Clone.
  3. Select the Velostrata Cloud Extension.
  1. Click Next.
  2. Select the Instance Type (VM size). Three options are recommended for performance-optimized VMs, and three options are recommended for cost-optimized VMs.
    Note: The prices are for compute cost only and do not include disk and network costs. Spot and reserved instances may also have price reduction plans.
    Note: If the VM has not been monitored for a sufficient period (7 days), a message appears indicating that the activity duration may be insufficient for accurate recommendations.
    Note: If the online price list is not available, no cost-optimized recommendations are provided.  
  3. Select the Resource Group and Availability Set.
  4. Select whether to use a Cloud-provided license, or if you have an existing on-premises Windows Server/Client license with active Software Assurance (SA), select Hybrid Use Windows Server or Hybrid Use Windows Client to apply the Azure Hybrid Use Benefit.
  5. (Windows) Select whether to use a Cloud-provided license, or if you have an existing on-premises Windows Server/Client license with active Software Assurance (SA), select Hybrid Use Windows Server or Hybrid Use Windows Client to apply the Azure Hybrid Use Benefit.
  1. Click Next.
  1. Select the required Network Security Group.

Note: If you do not enter a Network Security Group the default Network Security Group configured for the Cloud Extension is used.

  1. Click Next.
  1. Select a Subnet. Typically, the selection here would be of a private network subnet.
  1. From the Configure Private IP drop-down list, select Auto to allow an available address on the subnet to be automatically assigned, or Static if a specific address assignment is required.
  2. If you select Static, a Static IP field appears. Enter the required static IP for the instance or specify an ENI ID (e.g. eni-xxxxx) to associate a reserved Elastic Network Interface.
  3. From the Edge Node drop-down list, select the required node. A manual selection of the Edge Node to use is required. Select Node A or Node B. The default selection is Node A.
  4. Click Next.

 

  1. Review the summary and then click Finish.

The process of running the VM in the cloud can be viewed in the Cloud Instance Information portlet on the VM Summary page, and by monitoring the created vSphere task.

You can connect to the VM when the Remote Console field in the Cloud Instance Information portlet turns green and reads "Ready". You can connect to the VM using the private IP address or FQDN.