Skip to content
Beta

Hystax Acura Live Migration

Last updated on

Overview

Section titled “Overview”

Hystax Acura Live Migration supports automated, VM-centric Relocate scenarios from VMware, bare metal, and other supported source platforms to STACKIT. It replicates machine data and metadata in the background, creates target-specific migration plans, and lets teams validate workloads through isolated test migrations before a planned cutover.

Hystax publicly documents STACKIT as a target cloud type. The integration uses STACKIT service-account credentials for cloud discovery, replication, and recovery workflows in a target project.

Typical capabilities

Section titled “Typical capabilities”
  • Background replication: Synchronizes VM data and metadata while source workloads continue to run, using internal or external replication agents depending on the source platform.
  • Isolated test migrations: Runs repeated functional and performance tests in an isolated target environment before the final migration window.
  • Migration plans and transformation: Orchestrates application startup order and supports P2V and V2V transformation with target-specific compute, storage, network, and boot settings.
  • Controlled cutover and rollback: Provides a planned final switchover with a rollback path when acceptance criteria are not met.
  • Multi-tenant operations: Gives service providers one control plane for migration projects across multiple customers.
  • Disaster recovery: Supports active-passive protection, test failover, and failback workflows in addition to one-time migration projects.
  • Storage and ransomware controls: Supports configurable replication storage and can detect abnormal incremental replication growth to suspend affected machines.

Typical fit criteria

Section titled “Typical fit criteria”
  • Large or heterogeneous VM estates: Useful when many workloads must move from VMware, bare metal, or multiple supported clouds through a consistent process.
  • Downtime-sensitive workloads: Background replication and rehearsed test migrations reduce the work left for the final cutover window. Actual downtime depends on workload startup and validation time.
  • Migration factory or provider model: Multi-tenancy, migration plans, and repeated tests support parallel customer projects and migration waves.
  • Combined migration and recovery needs: Suitable when the same deployment should also support ongoing replication, failover testing, or disaster recovery after migration.

STACKIT deployment prerequisites

Section titled “STACKIT deployment prerequisites”
  • Hystax Acura controller: A STACKIT VM created from the Hystax Acura golden image with 8 vCPUs, 16 GB RAM, and a 200 GB SSD disk.
  • Cloud agent capacity: A target or failover project must permit a cloud-agent VM with 2 vCPUs, 4 GB RAM, and a 20 GB disk.
  • Authentication and networking: A dedicated STACKIT service account, its key, the documented ingress rules, and routable connectivity between the controller and cloud-agent network are required.
  • Platform services: Deployment requires an SMTP server with TLS or SSL encryption and a Hystax license key.
  • Workload validation: Confirm source-platform support, dependencies, target sizing, network mappings, recovery objectives, acceptance criteria, and rollback triggers before each wave.

Reference

Section titled “Reference”
Asset historyActive 6 of the last 12 weeksLWUpdatedNo updates · 1 bar = 1 week i
Maintainers
LWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 10 of the last 12 weeks · 47 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081TMTobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 12 of the last 12 weeks · 168 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172??Name not publicThe Cloud Framework team knows who this is. The name is not shown on the site.Contributed in Hystax
Show full history (6 more)