VMware Defends Decision to Restrict Access to Virtual Machine Backup SDK

Why VMware Says the SDK Was Never for Cross-Platform Migrations

VMware has defended its decision to stop offering public downloads of a software development kit used for backing up and migrating virtual machines, stating the license was never intended to facilitate moving workloads to competing platforms. The clarification came from the company’s APAC editor, Simon Sharwood, on September 10, 2026, amid growing concern among IT administrators and backup vendors who rely on the SDK for routine data protection and cross-environment workload management. VMware insists the restriction aligns with its long-standing licensing terms and does not constitute a new barrier to customer mobility.

The SDK in question has historically enabled third-party backup and disaster recovery solutions to interact with VMware’s virtualization layer, allowing for efficient snapshots, replication, and migration of virtual machines. While VMware acknowledges the tool’s utility in backup scenarios, it maintains that the license agreement explicitly prohibited using the SDK for direct migration to non-VMware hypervisors. The company says recent enforcement of download restrictions is merely a clarification of existing policy, not a sudden shift in strategy. VMware emphasizes that customers retain full ability to move virtual machines using supported, documented methods such as OVF/OVA exports or VMware’s own migration tools.

What Does This Mean for Backup Vendors and IT Teams?

VMware officials argue that the SDK’s purpose has always been limited to data protection, monitoring, and integration within VMware-centric environments. According to internal licensing documentation cited by Sharwood, the permitted use cases include backup, archival, and performance monitoring—but not the creation of portable virtual machine images designed for immediate deployment on rival platforms like Microsoft Hyper-V or KVM. The company states that allowing such use would violate the spirit of its commercial agreements and could undermine its investment in platform-specific optimizations. VMware says it remains committed to interoperability through standardized formats and official migration pathways.

Backup providers that have built tools around the SDK may need to adjust their integration approaches, potentially relying more on VMware’s official APIs or agent-based solutions. While VMware says no existing licenses are being revoked, the end of public downloads could affect new deployments or updates to backup software. IT administrators are advised to review their current toolchains and consult with vendors about compatibility under the updated access model. VMware suggests that any disruption can be minimized by using its supported interfaces, which it says are equally capable for backup and recovery tasks when properly implemented.

Why did VMware restrict access to the SDK now? VMware says it is not introducing new restrictions but enforcing existing license terms that were always in place, clarifying that the SDK was not meant for cross-platform migrations.

Frequently Asked Questions

Can customers still back up their VMware virtual machines? Yes, VMware confirms that backup operations remain fully supported through its official APIs and other documented methods, which it recommends for reliable and compliant data protection.

Will this affect my ability to move VMs to another hypervisor? VMware states that customers can still migrate virtual machines using standard formats like OVF/OVA or its own migration tools, which are designed for secure and supported cross-platform movement.