All case studies

Infrastructure case study

A 100-VM Hyper-V Private Cloud: Design, Build and Ongoing Management

Novaguard designed, built, and operates a private cloud platform with 10 Hyper-V hosts, 100TB of SSD storage, and approximately 100 virtual machines. The platform includes redundant WAN links, virtual and physical firewalls, and off-site object-storage backups.

By , Director, Novaguard Technology Group

Brisbane-based, with remote support Australia-wide. Client details are anonymised.

The project

The engagement covered the design, build, and ongoing operation of a private cloud platform. Its requirements included compute capacity, storage, network redundancy, segmentation, and backups held independently of the primary site.

What Novaguard built

Compute and storage

Ten Hyper-V hosts support approximately 100 virtual machines, with 100TB of SSD storage. Capacity was planned to accommodate a host failure.

Network and security

Redundant WAN links and dual uplinks reduce dependence on a single network connection. Virtual and physical firewalls provide segmentation at the perimeter and between workloads.

Off-site backups

Backups use object storage independent of the primary site. This provides a recovery source separate from production infrastructure.

Ongoing operation

Novaguard continues to manage patching, monitoring, capacity, and backup verification. Operational responsibility remained part of the engagement after the build.

Results and verification

The delivered platform runs approximately 100 VMs and remains under our management. The specifications describe the deployed environment; they are not a published uptime benchmark or a guarantee of uninterrupted failover.

Network redundancy, spare compute capacity, and off-site backups address different failure scenarios. This case does not present measured recovery times or a like-for-like public-cloud cost comparison.

When this approach is relevant

Private infrastructure can be considered where workload predictability, data volume, latency, or licensing makes it worth evaluating. Compare hardware, support, facilities, connectivity, recovery, and ongoing operation against the public-cloud alternative for the actual workload.

For project scoping, explore IT consulting and project delivery and our project method.

Questions about this engagement

What does Novaguard manage after the build?

We continue to manage patching, monitoring, capacity, and backup verification for this platform.

Does this case prove private cloud is cheaper than public cloud?

No. It documents a deployed platform and its management scope. A cost comparison needs the workload, service requirements, and full operating costs of each option.

What information helps decide whether private infrastructure is suitable?

Start with the workloads: how consistently they run, their storage and performance needs, application dependencies, and any licensing constraints. Then define recovery and support requirements. A useful comparison includes facilities, connectivity, hardware replacement, backups, and ongoing management. This case demonstrates our delivery scope, while the decision for your organisation needs its own technical and cost assessment.

How should we assess resilience in a proposed design?

Ask which failures the design addresses and what recovery would involve in each case. A failed host, lost network connection, unavailable storage, and loss of a site are different scenarios. The platform described here includes spare compute capacity, redundant links, and off-site backups. Any required recovery times and validation exercises should be agreed as part of your project scope.

Can Novaguard manage infrastructure after a project is delivered?

Yes. This engagement includes ongoing operation as well as the original design and build. Our responsibilities include patching, monitoring, capacity, and backup verification. For a new project, define operational ownership before handover: who receives alerts, approves changes, maintains documentation, and handles recovery. Those responsibilities should be clear alongside the technical design and delivery milestones.

Got workloads that don't fit neatly into public cloud?

That's a scoping conversation rather than an off-the-shelf product. Tell us what you're running and we'll give you a straight view on whether owning it makes sense.

Discuss your project