Release Notes

This page documents production updates to Velostrata. You can periodically check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

To get the latest product updates delivered to you, add the URL of this page to your feed reader.

4.2

New features

Migration to Sole Tenants

Velostrata 4.2 introduces migration to Compute Engine Sole Tenant Nodes. After creating nodes on Compute Engine, Velostrata handles migration to Sole Tenants using Waves.

Windows Bring Your Own License (BYOL)

Velostrata 4.2 introduces support for migration to Compute Engine with Windows BYOL. Because of common licensing considerations, we recommend to migrating VMs with Windows BYOL to sole tenant nodes.

Integration with Stackdriver

Velostrata 4.2 can now send logs and telemetry data to Stackdriver. You can enable or disable logs and telemetry data sent to Stackdriver at any point in time.

Requirements and OS Support

See Requirements and Supported operating systems.

Known Issues

#4266: Run-in-cloud and migration operations may fail for Windows Server 2016 workload when Symantec Endpoint Protection (SEP) is installed. This may also happen when SEP appears to be disabled.
Workaround: Modify workload Network interface bindings to remove SEP option. Download Microsoft Network VSP Bind (nvspbind) , Install Microsoft_Nvspbind_package.EXE into c:\temp. , Open Command prompt as an Administrator, and run the following: `nvspbind.exe /d* symc_teefer2`.

#1257: When Velostrata Prep RPM is installed on a SUSE Linux Enterprise Server 11, the VM obtains a DHCP IP address in addition to an existing static IP configuration. This issue occurs when the VM is started on-premises in a subnet that is enabled with DHCP services.
Note: The issue does not occur when the subnet has no DHCP services. There is no connectivity impact for communications with the original static IP address.

#1027: In some cases, when a VM is moved to Run-in-Cloud while a 3rd party VM-level backup solution holds a temporary snapshot, the Velostrata periodic write-back operations will not complete even after the backup solution deletes the temporary snapshot. The uncommitted writes counter on the VM will show an increasing size and no consistency checkpoint will be created on-premises.
Workaround: Select the Run On-Premises action for the VM and wait for the task to complete, which will commit all pending writes. Then select the Run-in-Cloud action again. Note that committing many pending writes may take a while. Do not use the Force option as this will result in the loss of the uncommitted writes.

#1745: After registering the Velostrata plug-in, running the Cloud Extension wizard might generate an error "XXXXXXXXXX" upon "Finish".
Workaround: Un-register the Velostrata plug-in and restart the vSphere Web client service, then re-register the plug-in. Contact support if the issue persists.

#1667: vCenter reboot causes Velostrata tasks in vCenter to disappear from UI. This is a vCenter limitation.
Workaround: Use the Velostrata PowerShell module to monitor Velostrata managed VMs or Cloud Extensions tasks that are currently running.

#1951: With an ESXi host in maintenance mode, if a VM is moved to cloud, the operation will fail and get stuck in the rollback phase.
Workaround: Manually cancel the Run-in-Cloud task, migrate the VM to another ESXi host in the cluster and retry the Run-in-Cloud operation.

#1917: A Run-in-Cloud operation fails with the error - "Failed to create virtual machine snapshot. The attempted operation cannot be performed in the current state (Powered off)".
Workaround: The VMware VM snapshot file may be pointing to a non-existent snapshot. Contact support for assistance in correcting the issue.

#1808: In rare cases, after running a Workload back on-premises - Workload VMDK's are locked. In certain cases, this is due to network disruptions between the Velostrata management appliance and the ESXi host on which the workload is running.
Note: The issue will resolve itself after 1-2 hours.

#2736: During Detach, the operation might fail with the following error message "Operation was canceled".
Workaround: Retry the Detach operation.

#3775: When performing a detach after a cancel detach operation, the action may fail.
Workaround: Retry the operation.

#3682: In the event of certain system failures, Velostrata components disconnect from vCenter. In this case, an event may not be sent, resulting in the alarm either not being set properly or not being cleared properly.
Workaround: Clear the alarm manually in vCenter.

#3320: For workloads with Windows machine using a retail license, when returning from the cloud, the license is not present.
Workaround: Reinstall the license.

#3281: vCenter "Export OVA" operation is available when the VM in cloud is running in cache mode, however, this operation results in a corrupted OVA.
Workaround: Only create OVA after the detach.

#3142: In rare cases, when a cloud component instance is created and system fails before it is tagged, the instance will remain untagged. This will not allow full clean-up or repair of the CE.
Workaround: Manually tag the instance, and then run "Repair".

#4604: Cloud Extension high availability does not work for workloads running Ubuntu OS with LVM configuration.
Workaround: Update the kernel to 3.13.0-161 or higher.

#3199: Suse12: Due to a bug in SUSE kernel older than 4.2, configurations that include BTRFS mounts with subvolumes are not supported.
Workaround: Upgrade to SUSE version with Kernel >=4.2 (SP2).

#3570: When using the Create Cloud Extension wizard, using illegal http proxy address will not generate a warning message.
Workaround: Delete the CE and then create the CE with a valid http proxy address.

#3133: Run on-premises operation succeeded but the status is marked as failed with error "Failed to consolidate snapshots"
Workaround: Consolidate snapshots via vCenter, and clear the error manually.

#5547: PowerShell client for cloud to cloud Runbook reports errors when running on PowerShell 3.0
Workaround: Upgrade to PowerShell 4.0

#5709: When migrating RHEL 7.4 from AWS to GCP, GCP agent will not be installed automatically.
Workaround: Manually remove the AWS agent and install GCP agent

傳送您對下列選項的寶貴意見...

這個網頁
Velostrata - Cloud Migration Software for GCP