Virtualisation strategy

Modernise virtualisation without forcing a single path.

Build a new integrated platform with eEVOS, or strengthen an existing VMware or Hyper-V environment with euroNAS storage. The right architecture depends on workload compatibility, availability, recovery objectives and operational strategy.

Compare the two pathsExplore architectures
eEVOS platformVirtualisation, storage, HA, backup and DR
VMware & Hyper-V storageShared file or block storage for existing estates
Controlled migrationAssessment, import, validation and staged cutover
Hardware choiceArchitectures based on standard enterprise servers
Two valid strategies

Choose what should change—and what should remain.

Virtualisation projects do not always begin with the same constraint. Some organisations want an independent platform that consolidates infrastructure functions. Others need to preserve VMware or Hyper-V while improving the storage and availability layer.

Integrated alternative · Primary path

Move virtualisation to eEVOS

Operate virtual machines, storage, high availability, networking, backup and disaster recovery through one hardware-independent platform.
  • Replace or reduce dependency on an existing hypervisor stack
  • Import workloads from VMware, Hyper-V, KVM and Xen environments
  • Select local, mirrored, shared or Ceph-based storage
  • Use integrated Backup & Disaster Recovery workflows
Explore the eEVOS platform →
Storage modernisation · Supporting path

Keep VMware or Hyper-V and modernise storage

Retain the existing VMware or Hyper-V application model while introducing euroNAS Premium, HA Cluster or eEKAS as an appropriate storage layer.
  • Preserve established VMware or Hyper-V operations and application support
  • Use NFS, iSCSI, Fibre Channel or NVMe-oF where supported
  • Design multipath and high-availability storage where required
  • Scale from a single storage server to HA or distributed storage
Explore storage for existing hypervisors →

No universal winner: application certification, operational experience, licensing, hardware compatibility, RPO/RTO and support requirements determine which path is appropriate.

Decision criteria

Start with the business and workload constraints.

A sound decision is based on measurable requirements, not only on the current hypervisor or the newest storage protocol.

01 · COMPATIBILITY

Application support

Identify workloads tied to a specific hypervisor, operating model or vendor certification.
02 · RESILIENCE

Availability objectives

Define acceptable interruption, failover behaviour and the infrastructure failures the design must tolerate.
03 · RECOVERY

Backup and DR

Separate rapid operational recovery from independent backup copies and off-site disaster recovery.
04 · OPERATIONS

Skills and complexity

Compare migration effort and daily administration with the long-term cost of multiple infrastructure silos.
Reference architectures

Scale from one host to distributed infrastructure.

The platform and storage topology should follow the workload. These patterns provide starting points for technical validation.

Compact

Single-host eEVOS

Virtualisation, local storage and integrated protection for branch, edge, laboratory or independent workloads.
Two nodes

Mirrored eEVOS

Two hosts synchronously mirror storage to provide a compact highly available virtualisation platform with seamless failover and no separate storage array.
Flexible host count

Shared-storage eEVOS cluster

Not restricted to a one- or two-node topology: connect multiple eEVOS hosts to centralised block storage over Fibre Channel, shared SAS, NVMe-oF or iSCSI. Multipathing and highly available storage preserve access while virtual machines move or hosts fail.
Existing estate

VMware or Hyper-V with euroNAS HA

Hypervisor hosts connect to a resilient euroNAS storage pair through suitable file or block protocols and multipathing.
Flexible scale-out

Ceph-based hyperconverged infrastructure

With eEVOS, Ceph pools storage across cluster hosts in a hyperconverged model broadly comparable to platforms such as VMware vSAN: capacity, performance and resilience can grow as nodes are added. eEKAS applies Ceph differently—as a dedicated scale-out storage platform. The products are not presented as feature-for-feature equivalents.
VSA

Deploy euroNAS as a Virtual Storage Appliance

Depending on the selected product and architecture, euroNAS can run as a virtual appliance and provide file or block storage without a dedicated physical storage server. This can suit branch offices, edge locations, laboratories, staged migrations and other software-defined deployments.Resource reservations, storage placement, boot dependencies, availability and failure domains must be validated for every virtual-appliance design.
Operational perspective

Evaluate the operating model—not only the feature list.

eEVOS consolidates core infrastructure workflows. A VMware- or Hyper-V-based architecture preserves the familiar hypervisor while euroNAS focuses on the storage layer.

Consideration eEVOS platform Existing hypervisor with euroNAS storage
Virtualisation Integrated eEVOS hypervisor management Existing VMware or Hyper-V environment remains in place
Storage Local storage, synchronous mirror, external shared storage or Ceph-based options. euroNAS Premium, HA Cluster or eEKAS selected for the required topology
Protection model eEVOS provides integrated VM Backup, Instant Backup & Recovery, NAS/S3 backup and remote DR VM backup remains part of the hypervisor and backup design; separate euroNAS Premium or HA storage can add ZFS snapshots and asynchronous ZFS replication where configured
Migration Guided import from common hypervisors, including VMware vCenter discovery No hypervisor migration; storage transition must be planned and validated
Best fit Organisations seeking consolidation, independence and a new operating model Organisations retaining VMware or Hyper-V compatibility, skills or application certification
eEVOS in operation

One view from cluster health to workload migration.

The R7 interface brings infrastructure status, virtual machines and migration workflows into a consistent operational environment.

Controlled transition

Modernise in stages rather than in one disruptive step.

Whether the destination is eEVOS or new storage for VMware, migration should preserve rollback options and validate application behaviour before production cutover.

AssessInventory workloads, dependencies, capacity, latency and recovery requirements.
PilotValidate representative applications, storage paths, backup and failover behaviour.
MigrateMove controlled workload groups while the existing platform remains available.
OperateDocument recovery, monitoring, ownership and capacity processes for the new design.
Protection by design

Backup & Disaster Recovery must be part of the architecture.

Recovery requirements influence storage placement, network design and migration decisions. eEVOS integrates several protection methods; VMware and Hyper-V environments require a coordinated hypervisor, backup and storage strategy.

Instant recovery

Rapid operational recovery points for complete eEVOS virtual machines and individual files.

Independent backup

NAS and S3-compatible targets separate protected data from the production environment.

Off-site DR

Remote eEVOS environments support recovery planning beyond the primary location.

euroNAS Premium / HA: ZFS storage protection

For separate euroNAS Premium and HA storage platforms, ZFS snapshots and asynchronous ZFS replication protect data at storage level. The recovery point depends on the last successfully replicated state; this complements—but does not replace—workload-consistent VM backup.

Explore eEVOS Backup & Disaster Recovery →

Architecture first

Map the workloads before choosing the platform.

We can review application constraints, VMware dependencies, storage protocols, availability targets and recovery objectives and turn them into a practical reference architecture.
Discuss your architectureExplore eEVOS in detail
Scroll to Top