IT security & disaster preparednessProject engagement

High Availability for Servers & Storage

Resilient server and storage infrastructure – as a turnkey appliance or software-based, vendor-neutral advice.

Who is it for?

Companies for whom a failure of servers or storage systems would immediately jeopardize operations.

A single server carrying your entire business operation is a single point of failure: if it breaks, your company grinds to a halt until replacement hardware arrives and the backup is restored – which can take hours to days.

  • How long could your company afford a complete server or storage outage?
  • Do you know whether your current infrastructure can survive a hardware failure without downtime?
  • Is a daily backup enough for you, or do you need genuine resilience without interruption?

Three paths to high availability

For your server and storage infrastructure, we offer three approaches: TERRA XALER from Wortmann is a pre-configured two-node cluster appliance – Hyper-V virtualization, storage, and networking already matched to each other in one unit, with synchronous data mirroring between both nodes and automatic failover in the event of a complete outage. Alternatively, we set up a software-based solution with DataCore SANsymphony or StarWind vSAN on your existing or freely chosen hardware – both continuously mirror data synchronously between two (or more) servers, with no physical SAN appliance required. StarWind is specifically built for smaller two-node clusters and remote sites, while DataCore SANsymphony is geared more toward larger, central environments.

If you're already running Proxmox VE as your virtualization platform (see our Virtualization with Hyper-V & Proxmox product), high availability can also be implemented natively via a Proxmox cluster with Ceph as distributed storage: Ceph automatically replicates data across multiple nodes, so if a single server or a single disk fails, no data is lost and your virtual machines automatically keep running on a remaining node. Since both Proxmox and Ceph are open source, this doesn't add any extra licensing cost for the storage layer itself – though Ceph typically needs at least three nodes instead of two for a reliable quorum.

Which solution fits you?

The turnkey appliance is a good fit if you want a fast, predictable rollout without your own integration work. The software-based approach with DataCore/StarWind pays off if you want to keep using existing hardware or choose your platform freely. The Proxmox-Ceph cluster is often the most consistent path if you already run or want to run Proxmox, because high availability is then integrated directly into your virtualization platform instead of running additional storage software. We advise you vendor-neutrally on which path fits your environment and budget.

Frequently asked questions

Do I need this if I already do daily backups?

A backup protects against data loss, but not against downtime: after a hardware failure, restoring from backup often takes hours, while a high-availability cluster switches seamlessly to the second node and your operations keep running.

What's the difference between the appliance and the software solution?

TERRA XALER is a ready-made, pre-configured hardware solution from Wortmann for a fast rollout without your own integration work. DataCore SANsymphony and StarWind vSAN are software that we set up on your existing or freely chosen hardware – more flexibility, potentially lower cost. See the linked product pages for details on both paths.

Why StarWind and not DataCore directly, or the other way around?

Both now belong to the same manufacturer but are positioned differently: StarWind is specifically built for smaller two-node clusters and remote sites, while DataCore SANsymphony is geared more toward larger, central environments. We choose the right fit for your company's size.

Is a second server really enough as a failover?

For terraXaler and the DataCore/StarWind solution, yes – both are specifically built for two nodes. A Proxmox-Ceph cluster, on the other hand, typically needs at least three nodes for a reliable quorum.

Why does Ceph need at least three nodes instead of two?

Ceph needs a majority (quorum) of nodes to reliably decide which data state is correct, even during a failure. With only two nodes, that wouldn't be unambiguous during an outage. In return, the cluster can be extended with additional nodes as needed and is integrated directly into your Proxmox environment.

Get in touch

WhatsAppRequest adviceGet support

Get in touch

Privacy settings

We use cookies and other technologies on our website. Some of them are essential, while others help us improve this website and your experience. Personal data may be processed (e.g. IP addresses), for example for personalized ads and content or ad and content measurement.

There is no obligation to consent to the processing of your data in order to use this offer. You can withdraw or adjust your selection at any time under settings. Please note that due to individual settings, not all functions of the website may be available.

We use technically necessary storage for operating this website. Optional services (statistics, marketing, external media) are only loaded after your consent.

Privacy settings