11 min read

Learning Objectives

By the end of this module, you will be able to:

  • Evaluate Private Cloud as a dedicated VMware environment: its stack, its cluster sizing ceilings, and the split of responsibilities
  • Decide when dedicated VMware wins over VDC compute, and when it does not
  • Position Private Cloud on operator sovereignty and cost predictability, with compliance claims scoped to the location
  • Design the hybrid pattern that links a dedicated VMware core to an elastic VDC edge
  • Contrast the migration and protection mechanics that Unit 7.4 builds on

Unit 4.4: Private Cloud (Dedicated VMware)

Introduction

FinCorp's VMware estate holds core-banking systems that the operations team runs with vSphere skills, VMware tooling and runbooks built over a decade. Rebuilding them as VDC workloads is possible, but it moves risk into the migration. Private Cloud offers the other path: a dedicated VMware environment operated by IONOS CLOUD, in which those workloads keep their operating model.

This is a design unit. Private Cloud is managed through the Cloud Panel, the vSphere Client and NSX-T Manager, not on the DCD canvas, so the decisions here are about fit, sizing, connectivity and responsibility. Unit 7.4 turns them into a migration plan.

1. What the Service Is Made Of

1.1 The Stack and the Responsibility Split

Private Cloud is a cluster of at least three dedicated physical servers that provides a VMware Software-Defined Data Center (SDDC). The components are:

Layer Component
Hypervisor VMware vSphere Enterprise Plus, on dedicated servers
Management VMware vCenter Server appliance
Networking VMware NSX-T Standard
Storage VMware vSAN Standard, aggregating host-based storage into a shared data store

The VMware licenses are included in the host prices, so there is no separate license contract to manage. You get access to the vSphere Client and NSX-T Manager and design the virtual data center inside. The dedicated servers are servers without administration rights: IONOS CLOUD maintains, patches and upgrades the hardware, the physical infrastructure and the VMware stack.

The boundary runs above the stack. IONOS CLOUD support covers its user interfaces, account questions, the hardware and VMware stack, SDDC software updates and emergency patches, and access to vSphere and NSX-T. It does not cover virtual machine configuration, the virtual network infrastructure, resource management, VM updates and patches, role and rights management, operating system and application licensing, VM monitoring, data security, external firewall rules or load balancers. You are also responsible for backing up and restoring everything you create in the Private Cloud, including virtual machines, content libraries, data and port groups. The service terms state that using Private Cloud requires a thorough knowledge of VMware software and network technologies. Plan the team before the cluster.

1.2 Provisioning, Sizing and Price

Private Cloud is provisioned and scaled vertically on demand, as self-service. A cluster includes a minimum of three hosts, and you can add hosts up to the provisioning maximum for your organization, at most 24 hosts per cluster. The service is available in Berlin, Logroño, Niederlauterbach and Worcester; for FinCorp, Berlin is the German location. A free 30-day test is available through the IONOS CLOUD sales department, which discusses requirements with you first.

The following tables list the current host models in the EUR price list.

Basic bundle (Cluster consisting of 3 hosts, incl. VMware licenses) Price per month Price group
M-512 7.500,00 € PG 1p
L-768 11.700,00 € PG 1p
XL-1024 15.000,00 € PG 1p
Additional host (incl. VMware licenses) Price per month Price group
M-512 2.100,00 € PG 1p
L-768 3.600,00 € PG 1p
XL-1024 4.500,00 € PG 1p

As shown above, the unit of purchase is a three-host basic bundle plus single hosts. A move to another hardware model costs a one-time fee of 300,00 €. Billing is per minute and invoiced monthly, and traffic is not charged. Add-ons are priced separately: an NFS datastore at 72,00 € per TB per month (minimum 2 TB), the IPsec VPN service at 50,00 € per month, and additional IP addresses from 5,00 € per month.

1.3 Capacity Is Your Job

vSAN capacity management is a customer obligation with hard numbers. You must keep at least 30% slack space in the vSAN datastore, and if free space reaches or falls below 25%, the environment may no longer be functional. A RAID 1 storage policy needs at least three hosts. Storage efficiency (none, compression only, or deduplication and compression) and encryption are set in the Cloud Panel, and changing them reformats all disks, affects performance and blocks new Cloud Panel actions until the process completes. Choose these settings before the first workload lands.

When storage grows faster than compute, an NFS datastore adds capacity without adding hosts: from 2 TB up to 32 TB in standard provisioning, and up to 128 TB in total, with scheduled and manual snapshots managed in the Cloud Panel.

2. When Private Cloud Wins

The choice is per workload, not per company. The following table contrasts the two environments.

Criterion Private Cloud VDC compute (Units 4.1 to 4.3)
Tenancy Single-tenant cluster of dedicated hosts Dedicated cores or shared vCPUs on the multi-tenant platform
Operating model vSphere, NSX-T and vSAN, managed in the vSphere Client and NSX-T Manager DCD, Cloud API, IONOS CLOUD managed services
Unit of growth A host, at most 24 per cluster A core, a GB of RAM, a server, a replica
Cost shape Flat monthly bundle including VMware licenses; no traffic charge Per-hour resources; Savings Plans for committed floors
Workload change on migration VMware-native replication with VCDA Image conversion and guest preparation (Unit 1.3)
Elasticity Capacity planned in hosts, with vSAN slack Live resize and VM Auto Scaling

As shown above, Private Cloud wins where four conditions meet: compliance or risk policy asks for single-tenant hardware, performance must be predictable at the host level, the team's value lies in VMware skills and tooling, and a large VMware estate would otherwise be rebuilt under time pressure. It loses for workloads that are stateless and elastic, that consume managed services, or that are small enough that a three-host minimum dominates their cost.

3. Positioning: Operator Sovereignty and Cost Predictability

Two arguments carry Private Cloud in a regulated sale. The first is the control plane. Unit 1.4 showed that sovereignty depends on who operates a service and under which law, not only on where data sits. In Private Cloud, the hosts are dedicated, IONOS CLOUD operates the hardware and the VMware stack, and you control the virtual layer. When you compare dedicated VMware offerings, ask who operates the management plane and under which jurisdiction, not only in which region the hosts stand.

The second is predictability. The monthly price covers the hosts and the VMware licenses, billing is per minute, and traffic is not charged. The cost of a cluster is therefore a function of host count, which the capacity plan already fixes. Ask the same of any alternative: whether licenses, traffic and support for the VMware stack are inside the quoted price.

Keep compliance claims scoped. The Berlin data center, operated by IONOS CLOUD Group, holds BSI IT-Grundschutz and ISO 27001 credentials at the facility level. Private Cloud is not among the services named in the scope of the IT-Grundschutz certificate in Unit 1.4, and C5 scope is confirmed per service against the attestation report. FinCorp's compliance mapping therefore cites the Berlin facility credentials for the Private Cloud estate and records the service-level position explicitly.

4. The Hybrid Pattern

Private Cloud sits beside the VDC model as a connected site (Unit 1.2). The pattern is a dedicated VMware core for the regulated, VMware-bound systems and an elastic VDC edge for the portal, the APIs and the AI tier, linked over hybrid connectivity.

The links have specific shapes:

  • Management access. OpenVPN connects to the vSphere management network by default and allows only one end device at a time. For team access and site links, the IPsec VPN service in the Cloud Panel uses an automatically provided VyOS backend gateway, supports one or more IPsec connections to different endpoints, and authenticates with a pre-shared key. The encryption settings must match those of the remote device.
  • Workload connectivity. Each cluster includes one static public IPv4 address, and further addresses are billed separately. With Bring Your Own IP (BYOIP), you use your own ranges, announced with the IONOS ASN AS8560 or with your own ASN; this requires a route object and an RPKI ROA, and each NSX segment subnet must be more specific than the BYOIP range.
  • Management from inside. The management level can be enabled in the Cloud Panel, which creates an NSX network segment so that VMs, for example monitoring or automation tools, can reach the vSphere management plane.

One cost rule shapes the edge: in the IONOS CLOUD price list, outgoing traffic to Private Cloud is recorded as regular public traffic. A chatty integration from the VDC edge to the core therefore counts as public traffic on the VDC side, so keep the high-volume data paths on one side of the link.

FinCorp applies the pattern. The core-banking systems move to a Private Cloud cluster in Berlin, sized in hosts with vSAN slack. The portal and AI tiers stay in the Frankfurt VDCs. An IPsec connection from the Private Cloud's IPsec VPN service to the VPN Gateway in fc-prod-fra-core (Unit 3.6) carries the integration traffic, and the address plan of Unit 3.1 is checked against the NSX segments before the link goes live.

5. Migration and Protection Mechanics

VMware Cloud Director Availability (VCDA) is the migration and protection path into Private Cloud. It is a Disaster Recovery-as-a-Service (DRaaS) solution that protects vApps and virtual machines with asynchronous replication, migrates them, performs failover, and reverses failovers. An on-premises appliance (VCDA-CUST) pairs with the appliance in the Private Cloud (VCDA-CLOUD), which IONOS CLOUD publishes on the main IP address of the Private Cloud on port 55443; the on-premises side connects outbound on TCP 443. The documented version is 4.7.x.

The commercial model matters for wave planning: only protected VMs are invoiced, at 50,00 € per VM per month, and the migration feature can be used free of charge. Migration waves therefore cost nothing in VCDA licensing; ongoing protection is a per-VM decision. For backups of the Private Cloud estate, the Backup Service can be used together with Private Cloud. Its virtual machine, acronis-customer_cloud, must keep its network adapter settings. Unit 7.4 builds the wave plan, the cutover and the rollback on these mechanics.

Decision Summary

Question Choose Private Cloud when Choose VDC compute when
Tenancy Policy requires single-tenant hosts Logical isolation and service-scoped credentials suffice
Skills and tooling The team operates vSphere, NSX-T and vSAN and must keep doing so The team operates through the DCD, the API and managed services
Estate A large VMware estate must move with minimal change, via VCDA Workloads are rebuilt, containerised or small
Growth Capacity can be planned in hosts, with 30% vSAN slack Demand is elastic and needs live resize or auto scaling
Cost A flat monthly cluster price with licenses included fits the budget Per-hour resources and commitments on the floor fit better
Hard constraints At least three hosts, at most 24 per cluster; you own VM, network, roles, monitoring and backup Compute class limits from Unit 4.1

Summary

Private Cloud gives a dedicated VMware SDDC, with vSphere Enterprise Plus, vCenter, NSX-T Standard and vSAN Standard on at least three dedicated hosts, licenses included, provisioned and scaled on demand. IONOS CLOUD operates the stack; you own everything above it, including vSAN capacity and backups. It wins for single-tenant, VMware-bound estates with VMware skills, and it links to the elastic VDC edge over IPsec, with VCDA as the migration path.

Key Points:

  • A cluster has 3 to 24 dedicated hosts; host prices include the VMware licenses, billing is per minute, and traffic is not charged.
  • Support covers the hardware and VMware stack; VMs, virtual networks, roles, monitoring, data security and backups are yours.
  • Keep at least 30% vSAN slack; at 25% free space or less, the environment may stop working.
  • Management access uses OpenVPN by default (one device) or the IPsec VPN service (pre-shared key, multiple connections).
  • VCDA migration is free; protection costs 50,00 € per VM per month.

Important Terminology:

  • SDDC (Software-Defined Data Center): the virtualised compute, storage and networking stack that Private Cloud delivers on dedicated hosts.
  • Slack space: the free vSAN capacity you must keep to absorb fluctuations and avoid excessive rebalancing.
  • VCDA: VMware Cloud Director Availability, the replication, migration and failover service used to move VMs into Private Cloud.