Hystax

Migrating workloads to OpenStack сan be simple and painless

Nick Smirnov (CEO)

Hystax B.V. | © Copyright 2016 - 2018

Differences between Bare Metal machines and hypervisors

Variety of network configurations and settings

Duration of process of migration

Downtime during migration process

Lack of in-house expertise in migration

Migration challenges

Identify workloads to be migrated (machines, networking) Result: a list of machines and network settings (security groups, routes, VPNs etc.)

Identify dependencies between business application components Result: topology of business application used later in a Migration Plan

Recreate network settings

Replication of data (full and incremental)

Orchestrated launch of test migrations – P2V / V2V, configure and test

Final Cutover

End-to-End Cloud Migration

Recreate networking and create Migration Plan with orchestration

Plan and execute final migration

Run unlimited number of test migrations and

build confidence

Identify workloads and replicate

Hystax Acura: Migration to OpenStack

OpenStack: Migration Data Flow

Replication agent

ACP

WebUI

receiver

provides interface 

to upload data

orchestrator

Orchestration of OS 

resources 

(creates \ removes 

VMs, networks, etc)

Sends replicated

machine data

Calls REST API

to start recovery process

V2V

makes Virtual-2-Virtual or

Physical-2-Virtual

conversion

Calls V2V to apply

conversion

Hystax Acura Target Cloud

Replica volume

Snapshot 1

Snapshot 2

Snapshot 3

Creates volume

from snapshot

Restored volume

Fills Replica

volume with data

Applies V2V

Restored machine

Creates machine

from restored

volume Uses restored

volume as source

Source machine

Source environment

Reads data 

from machine

Hystax Acura Migration to OpenStack

Migration and Disaster Recovery: Source and Target Platforms

Contacts

+31 85 888 62 80

info@hystax.com https://hystax.com/

https://www.linkedin.com/company/hystax