Azure Local

Two-node switchless Azure Local clusters

Two machines, storage cabled directly between them, no storage switches. It is the smallest highly available Azure Local design, and the one our public deployment factory automates.

What we do

Scope of the work

  • Confirm the two-machine design fits the workload and the growth plan
  • Design direct storage links, management and compute networks and the uplinks
  • Install both machines remotely through their management controllers
  • Configure the witness, register with Azure Arc, validate and deploy
  • Test a machine failure and a storage link failure before handover
What you receive
  • A two-machine cluster that keeps running with one machine down
  • A cabling diagram and the deployment parameter record
  • A failure test report

Billed at $150.00 per hour. Ask Keith for an estimate.

Field notes

What we check first.

Cabling is the design

With no storage switches, a wrong cable is a wrong configuration. We check link by link before deployment.

Capacity with two machines

A two-way mirror keeps two copies, so about half the raw capacity is usable. We size for that and for rebuild space.

Adding a third machine

A switchless two-machine cluster cannot simply take a third machine: Microsoft supports growing from two to three machines only with switched storage. If growth is likely, we design switched storage from the start or plan the conversion.

How an engagement runs

Four steps, written down.

I
Scope

A call with Keith

You describe the goal, the estate and the deadline. Keith turns it into a written scope with an hour estimate at the hourly rate.

II
Design

A written design by Gus

Gus reviews the environment and gives you a written design with each decision and its reason.

III
Build

Hands-on implementation

Gus implements in your tenant and your racks, remotely or on site, with every change logged as it is made.

IV
Hand over

Documents and a named contact

You receive the as-built record and the runbooks. Keith stays on as your account and project manager.

Questions

Asked before every engagement.

Is a two-machine cluster really highly available?

Yes, with a witness. Virtual machines restart on the surviving machine when one fails. It does not protect against the loss of the whole site, which needs a disaster recovery design.

Do we still need switches?

Yes, for management and workload traffic. You do not need separate high-speed storage switches, which is the saving.

What does the consulting cost?

Consulting is billed at $150.00 per hour. Keith sends a written hour estimate after the scoping call, and work starts when you approve it.

Rate and contacts

One rate. Two people.

Consulting is billed at $150.00 per hour. Keith runs sales, project management and your account. Gus does the architecture, the design and the implementation.

Hourly rate
$150.00

per consulting hour, for every consulting service

Sales, project management and account management

Keith

keith@apexvanguard.ai
Architecture, design and implementation

Gus

gus@gusitllc.com

Independent practice, not affiliated with Microsoft. Azure Local consulting is part of the infrastructure consulting practice of Gus IT LLC, an independent firm. It is not affiliated with, endorsed by or sponsored by Microsoft Corporation, Dell Technologies, Fortinet or any other vendor named on this site. Microsoft, Azure, Azure Local, Azure Stack HCI, Azure Arc, AKS, Azure Virtual Desktop, Hyper-V and Windows Server are trademarks of Microsoft Corporation. Dell, PowerEdge, PowerSwitch and iDRAC are trademarks of Dell Inc. Microsoft Entra, Active Directory, SQL Server, FSLogix and BitLocker are also trademarks of Microsoft Corporation. Fortinet and FortiGate are trademarks of Fortinet, Inc. VMware and vSphere are trademarks of Broadcom Inc. Kubernetes is a registered trademark of The Linux Foundation. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Linux is the registered trademark of Linus Torvalds. All other marks belong to their respective owners and are used for description only. Product capabilities follow each vendor's documentation and change between releases; we confirm the current state during scoping.