Skip to content

Migrating and Protecting VMware Workloads Without VDDK

Gavin YoungPublished 1 min read
Virtual machines flow from VMware servers through a secure replication gateway to CloudStack, bypassing an unused stack of VDDK libraries and APIs.

The Short Answer

Broadcom’s revocation of public download access to the VDDK has created new challenges for VMware backup, replication and migration solutions that rely on customers being able to obtain and deploy the toolkit. Sendense native VMware integration solves that problem by removing the need for VDDK.

Sendense native VMware integration

Broadcom’s recent change to the availability of the VMware Virtual Disk Development Kit (VDDK) has created new challenges for VMware backup, replication and migration solutions that rely on customers being able to obtain and deploy the toolkit.

For CloudStack providers helping customers migrate away from VMware, that dependency can now be a significant consideration.

Sendense provides backup, disaster recovery and cross-hypervisor replication for service providers and enterprises, with native support for VMware and Apache CloudStack.

And Sendense doesn’t depend on VDDK.

VMware workloads can be backed up, protected and continuously replicated to CloudStack without VDDK, while retaining the storage compatibility, performance and reliability required for production workloads.

With Sendense, CloudStack CSPs can:

  • Migrate VMware workloads to CloudStack using incremental replication and low-downtime cutover
  • Back up VMware workloads without VDDK
  • Continuously replicate VMware → CloudStack for Disaster Recovery as a Service
  • Replicate CloudStack → VMware where required
  • Protect workloads after migration with ongoing CloudStack backup and DR
  • Support all VMware storage types, without requiring customers to move workloads onto NFS or another specific storage platform
  • Use their preferred CloudStack storage backend
  • Deliver the same performance and reliability without relying on VDDK

There is no VDDK for the customer or CSP to obtain, distribute or maintain, and no need to redesign the source VMware environment around the migration or protection platform.

Migration can be the start, not the end - Sendense isn’t just a VMware migration tool.

A CSP can use the same platform that migrates a customer’s workloads into CloudStack to provide ongoing Backup as a Service and Disaster Recovery as a Service once they’re there.

It means a VMware exit project can become an ongoing managed protection service, rather than ending when the final VM is migrated.