Guest mode. Compare every platform freely. Saving comparisons and downloading Word, PowerPoint, Excel or diagram files need a free niyyasoft.com account.

Sign in Create account

Scale Computing · Turnkey appliance

Scale Computing SC//Platform (SC//HyperCore)

SC//HyperCore is a KVM-based hypervisor with the SCRIBE block storage engine built into the hypervisor (no controller VM), plus the AIME self-healing engine, managed from a web UI on any node and optionally from the cloud-hosted SC//Fleet Manager for up to 50,000 clusters. It runs on Scale appliances (HE100/HE500 edge and HC1000/HC3000/HC5000 series), on certified Dell, HPE, Lenovo and Supermicro servers, or on reused Dell VxRail nodes. It targets edge, retail, ROBO and SMB sites from a single node up to 8-node data-centre clusters, and is sold per node as an all-inclusive subscription with ScaleCare support.

Add to a comparison Compare its editions OEM product page ↗

Hypervisor
SC//HyperCore (KVM-based)
Cluster size
1–8 nodes
Two-node
No · witness
Management
SC//HyperCore web UI on any node (no management VM) + optional SC//Fleet Manager (cloud)
Data reviewed
2026-09-19

Strengths

  • Hypervisor and storage in one lightweight stack with no controller VM (about 4 GB RAM on small nodes).
  • SC//Fleet Manager zero-touch provisioning, updates and app lifecycle across up to 50,000 clusters.
  • Self-healing AIME engine and one-click rolling updates of the whole stack.
  • All-inclusive per-node subscription with replication and snapshots, and one vendor for appliances.
  • Runs on Scale appliances, certified Lenovo/Dell/HPE/Supermicro servers or reused VxRail nodes.

Considerations

  • Clusters scale to about eight nodes; no stretched clusters or synchronous replication.
  • Two-copy mirroring with no primary-data dedupe, compression or erasure coding raises raw capacity needs.
  • No storage-layer encryption at rest, SDN, microsegmentation or self-service portal.
  • Pricing is quote-based and Severity 1 response objective is 2 hours.
  • Ownership changed in 2025 (Acumera merger); smaller partner and skills ecosystem.

Use-case fit

Server virtualisation & consolidation

Simple, self-healing virtualization for small and mid clusters, limited to 8 nodes and without dedupe.

VMware exit / Broadcom alternative

Low-touch replacement for small vSphere estates, including reusing VxRail nodes, but a smaller ecosystem.

VDI & end-user computing

Only niche VDI brokers are listed and there is no dedupe for desktop images.

ROBO & edge sites

Built for edge: tiny nodes, ZTP, self-healing and fleet management of thousands of sites.

Business-critical databases & tier-1 apps

NVMe nodes help, but no QoS, sync replication or stretched clusters.

Private cloud & self-service IaaS

No self-service portal, SDN or multi-tenancy.

Kubernetes & modern applications

Containers only inside VMs; no integrated Kubernetes.

AI, ML & GPU workloads

Edge inferencing on L4 GPU appliances only; not a GPU platform.

Disaster recovery & secondary site

Built-in replication down to minutes and simple failover, but no sync replication or runbooks.

Hybrid cloud

Cloud-hosted fleet management only; no public-cloud footprint.

SMB & lean IT teams

All-inclusive subscription, minutes to deploy and one vendor for hardware and software.

Regulated, sovereign & air-gapped

Runs disconnected, but no at-rest encryption at the storage layer or formal certifications.

Test, development & labs

Instant clones and APIs, but no free edition.

Every comparison point

Architecture & platform
Hypervisor(s)Which hypervisor runs the virtual machines, and whether a choice of hypervisor is supported.

SC//HyperCore, a type-1 hypervisor built on KVM components and integrated with the storage layer. No choice of hypervisor.

SC//HyperCore Virtualization Suite data sheet ↗
Architecture modelSoftware-defined (bring your own certified hardware), turnkey appliance, or disaggregated HCI (dHCI).

Mostly turnkey appliances (HE100/HE500 edge, HC1000/HC3000/HC5000), plus SC//HyperCore software on HCL servers from Dell, HPE, Lenovo and Supermicro, including reused Dell VxRail nodes.

SC//HyperCore Virtualization Suite | Scale Computing ↗
Storage engineHow the distributed storage is implemented - controller VM, in-kernel, or a separate storage layer.

SCRIBE block engine runs alongside the hypervisor in the kernel, with no controller VM or VSA; wide-striped two-copy mirroring across all disks, HEAT automated flash/HDD tiering.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Minimum nodes per clusterThe smallest supported production cluster.

Single-node appliances are supported; a highly available cluster starts at three nodes.

scalecomputing.com ↗
Maximum nodes per clusterThe largest supported cluster, and how further scale is achieved.

Scale says clusters grow from a single edge node to eight nodes in the data centre; more capacity means more clusters under Fleet Manager.

SC//HyperCore Virtualization Suite data sheet ↗
Single-node deploymentWhether a one-node cluster is supported, and with what limits.

Native single-node appliance configurations (HC1000, HC1150DF, HC5150D) with built-in replication to another node or cluster as often as every 5 minutes; no local HA.

scalecomputing.com ↗
Two-node cluster & witnessTwo-node support and what it needs as a witness or tie-breaker.

No true 2-node HA cluster; options are a replicated pair of single nodes (async, manual failover) or two nodes plus a storage-only node acting as local witness.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Stretched / metro clusterOne cluster spanning two sites with synchronous mirroring and automatic failover.

No stretched or metro cluster.

SC//HyperCore Theory of Operations (replication and recovery) ↗
Independent scaling (compute-only / storage-only nodes)Whether compute and storage can grow separately.

Nodes of different sizes and storage types can be mixed; a storage-only mode exists for witness use, but no compute-only nodes.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
External storage (SAN / NAS) alongside HCIWhether existing SAN or NAS arrays can be attached to the same hosts.

Existing SANs can be used over iSCSI or NFS (LUNs/shares attached for VMs, backup and archive), outside SCRIBE protection.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
All-flash / NVMe supportAll-NVMe support and any NVMe-optimised storage architecture.

HC3000 and HC5000 appliances are all-NVMe (U.3); HE100 uses M.2 NVMe; HEAT tiers flash and HDD in hybrid nodes.

Scale Computing Hardware Data Sheet ↗
Host & VM maximumsPublished maximums per host or per VM - cores, memory, VMs.

Largest appliances: 2x Xeon up to 32 cores each and up to 2 TB RAM (HC-series dual-socket); edge HE153 NUCs 16-96 GB RAM. HyperCore itself needs about 4 GB RAM on small nodes.

Scale Computing Hardware Data Sheet ↗
Storage & data services
Deduplication & compressionInline or post-process data reduction, and which editions include it.

Current Theory of Operations and data sheet describe space-efficient snapshots and clones (shared, reference-counted blocks) but no inline deduplication or compression of primary data; replication traffic is compressed.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Erasure coding (RAID-5/6)Capacity-efficient parity protection instead of full mirroring.

Not available; SCRIBE always keeps two mirrored copies (RAID 10 equivalent).

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Data resiliency (failures tolerated)Replication factor / failures-to-tolerate options and fault domains (rack, block).

Two copies of every chunk across nodes; tolerates a disk or a whole node failure, re-mirrors automatically into free space without hot spares. One failure domain level only.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Snapshots & clonesSpace-efficient snapshots and clones, and their limits.

Allocate-on-write VM snapshots (thousands per VM with little impact), instant promote/revert, instant thin clones and file-level recovery by mounting cloned disks.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Data-at-rest encryption & KMSSoftware encryption of the datastore, self-encrypting drives, and key management options.

No storage-layer encryption at rest; customers encrypt in the guest (BitLocker, LUKS) using a vTPM. Replication is AES-256 encrypted in flight.

Scale Computing Information Security Technical White Paper ↗
Storage QoSIOPS / throughput limits or guarantees per VM or volume.

No IOPS limits; HEAT gives per-virtual-disk flash priority (0-11 slider) on tiered nodes.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
File services (SMB / NFS)Native file shares served by the platform.

No native file services; partner options such as Nasuni run as VMs.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Object storage (S3)Native S3-compatible object storage.

No native S3 object storage.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Block storage for external hostsPresenting volumes to physical servers or other clusters over iSCSI or NVMe-oF.

Not supported; SCRIBE storage serves only VMs on the cluster.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Data protection & DR
Asynchronous replication (RPO)Native async replication and the lowest supported RPO.

Built-in per-VM cluster-to-cluster replication, change-tracked and compressed, running continuously; Scale cites replication as often as every 5 minutes. Included at no extra cost.

SC//HyperCore Theory of Operations (replication and recovery) ↗
Synchronous replication (zero RPO)Zero-data-loss replication between sites.

Not available.

SC//HyperCore Theory of Operations (replication and recovery) ↗
DR orchestration & runbooksAutomated failover, failback and non-disruptive DR testing.

One-click promote of replicated snapshots and reverse replication for failback; runbooks and DR tests must be scripted with Ansible or the REST API.

SC//HyperCore Theory of Operations (replication and recovery) ↗
Native backupBackup built into the platform, without a third-party product.

Snapshots, file-level restore and remote replication are built in (Scale sells this as integrated backup/DR); no separate catalogued backup application.

SC//HyperCore Theory of Operations (replication and recovery) ↗
Immutable snapshots & ransomware protectionTamper-proof snapshots, ransomware detection and recovery features.

Snapshots are not documented as immutable; immutable backups come via Veeam integration.

scalecomputing.com ↗
Third-party backup ecosystemSupport from Veeam, Commvault, Rubrik, Cohesity, HYCU and similar.

Veeam 12.3.2 supports SC//HyperCore (agentless integration); Acronis and Storware partners; fewer options than VMware.

scalecomputing.com ↗
DR to public cloudUsing a public cloud as the recovery site.

No run-in-public-cloud recovery; Scale mentions a DR-as-a-service option and partners such as Wasabi and Acronis for cloud copies.

Scale Computing Hardware Data Sheet ↗
Networking & security
Software-defined networkingOverlay networks, VPCs, distributed routing and load balancing.

Standard VLAN-based networking with bonded LAN and backplane; no overlay SDN. SD-WAN is a separate product (SC//Connect).

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Microsegmentation / distributed firewallEast-west VM firewalling enforced at the hypervisor.

No distributed firewall; traffic is directed only to specified virtual NICs and an internal firewall isolates the cluster.

Scale Computing Information Security Technical White Paper ↗
RBAC, SSO & MFARole-based access control, directory / SAML integration and multi-factor authentication.

Per-cluster RBAC (e.g. read-only, backup roles); OpenID Connect to Azure AD/ADFS with MFA enforced by the IdP; Fleet Manager SSO via Google or Microsoft.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Platform hardeningSecure boot, TPM, hardened baselines (STIG), automated drift remediation.

Closed, vendor-controlled hypervisor stack with internal firewall and isolated backplane; UEFI Secure Boot and vTPM for VMs. No STIG baseline published.

Scale Computing Information Security Technical White Paper ↗
Security certificationsFIPS 140, Common Criteria, DISA STIG and similar attestations.

Security practices aligned with ISO/IEC 27001 and SOC 2 (per Scale); appliances imaged in an ISO 9001 facility. No FIPS 140 or Common Criteria listing found.

Scale Computing Information Security Technical White Paper ↗
Management & operations
Management consoleThe day-to-day management interface.

Browser UI served by any node (no management VM or master node); optional cloud-hosted SC//Fleet Manager for multi-cluster.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Multi-cluster / fleet managementManaging many clusters and sites from one place.

SC//Fleet Manager manages 1 to 50,000 clusters: zero-touch provisioning, fleet updates, application lifecycle management, Secure Link remote access, Fleet Metrics and Fleet APIs.

SC//Fleet Manager Edge Orchestration | Scale Computing ↗
Lifecycle management (full-stack upgrades)Rolling, non-disruptive upgrades of software, drivers and firmware.

One-click, rolling, non-disruptive updates of hypervisor, storage and firmware; minor updates apply in place without reboots; fleet-wide from Fleet Manager.

Scale Computing Support & Services Reference Guide ↗
APIs & automationREST API, Terraform, Ansible, PowerShell and CLI coverage.

REST API, Terraform provider, Red Hat certified Ansible collection, cloud-init, plus fleet-level REST APIs in Fleet Manager.

SC//HyperCore Virtualization Suite data sheet ↗
Monitoring, analytics & capacity planningBuilt-in health, performance analytics, forecasting and right-sizing.

AIME self-healing monitors hardware, software and VMs and remediates automatically; Fleet Metrics keeps up to a year of CPU, memory and storage history for planning.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Self-service & private-cloud portalCatalogues, projects, quotas and chargeback for consumers.

No tenant self-service portal, quotas or chargeback.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Live migration & HALive migration, automatic restart on failure and load balancing (DRS-like).

Live migration, automatic VM restart within minutes after node failure, affinity rules and automatic placement; no DRS-style continuous balancing documented.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Cloud, containers & AI
Kubernetes & containersNative or integrated Kubernetes, and persistent storage for containers.

No integrated Kubernetes; run containers or K8s in VMs with a container-optimised OS. Fleet Manager ALM and partner Avassa help deploy containerised edge apps.

SC//HyperCore Virtualization Suite data sheet (containers support) ↗
Hybrid / public cloudThe same stack in a public cloud, or cloud services managing the on-premises cluster.

Management plane (Fleet Manager) is cloud-hosted, but there is no HyperCore instance in public clouds.

SC//Fleet Manager Edge Orchestration | Scale Computing ↗
VDI / end-user computingValidated VDI brokers - Citrix, Omnissa Horizon, Azure Virtual Desktop and others.

VDI partners are Parallels, Leostream and 10ZiG; no Citrix or Omnissa Horizon validation listed.

Technology Alliance Partners | Scale Computing ↗
GPU & AI workloadsGPU passthrough and vGPU, and packaged AI / inference offerings.

Edge AI positioning with GPU appliances (e.g. HC5000 with NVIDIA L4 24 GB) for inferencing and computer vision; no vGPU-sharing platform or AI stack.

Scale Computing Hardware Data Sheet ↗
Database servicesBuilt-in database provisioning and lifecycle (DBaaS).

No database service.

SC//HyperCore Virtualization Suite | Scale Computing ↗
Deployment & hardware
Deployment method & timeHow a cluster is installed, and how long that typically takes.

Nodes ship pre-imaged; rack, cable and initialise in minutes, or use Fleet Manager zero-touch provisioning (Scale claims 90% less install time).

SC//Fleet Manager Edge Orchestration | Scale Computing ↗
Hardware optionsAppliances, certified / validated nodes and compatibility lists.

Scale appliances (HE100, HE500, HC1000, HC3000, HC5000) or SC//HyperCore on HCL hardware via the imaging service, including Dell VxRail 14G-16G nodes.

SC//HyperCore Hardware Compatibility ↗
Hardware OEMsWhich server vendors ship or certify nodes.

Appliance and HCL partners: Lenovo, Supermicro, Dell, HPE, SimplyNUC (SNUC), Intel, ASRock Industrial, Asus; Arrow Intelligent Solutions integration.

SC//HyperCore Hardware Compatibility ↗
Edge / ROBO suitabilitySmall footprints, remote management and low-touch operation for branches.

Purpose-built for edge: NUC-size nodes with about 4 GB hypervisor overhead, self-healing, ZTP and fleet management of thousands of sites.

SC//HyperCore Virtualization Suite | Scale Computing ↗
Air-gapped / disconnected operationRunning and updating without any internet or cloud connection.

Clusters run fully locally with no management VM or cloud dependency; Fleet Manager is optional. Updates for disconnected sites need manual staging.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Migration tooling (e.g. from VMware)Built-in or vendor tools for moving VMs onto the platform.

SC//Move (powered by Carbonite) for near-zero-downtime migration, Acronis convert-to-VM, Veeam restore, and Scale migration services; documented VxRail re-imaging path.

SC//HyperCore Theory of Operations (technical white paper, v16) ↗
Licensing & subscription
Licence modelSubscription, term, perpetual or free, and the usual term lengths.

All-inclusive SC//HyperCore subscription per node (compute, storage, virtualization, HA and data protection) with ScaleCare support; appliances bundle hardware.

scalecomputing.com ↗
Licence metricWhat is counted - physical cores, sockets, nodes, TiB, or VMs.

Per node (appliance or certified server).

Pricing | Scale Computing ↗
Licensing minimumsMinimum cores per CPU, minimum order quantities and similar rules.

No published minimum; one node for single-node sites, three nodes for an HA cluster.

Pricing | Scale Computing ↗
EditionsThe editions or packages sold.

Single feature set for all customers; the choice is hardware (Scale appliance vs HCL server) and support type (Full vs Software-only).

Pricing | Scale Computing ↗
Free / community editionA no-cost edition, and what it is licensed for.

No free edition; a browser-based Remote Edition sandbox for prospects and a Workbench Edition for partners.

scalecomputing.com ↗
Guest OS (Windows Server) licensingWhat the platform does, or does not do, for Windows Server guest licensing.

No Windows Server rights included; license Windows per physical core of each node.

Pricing | Scale Computing ↗
Licence portabilityMoving the licence between hardware vendors, or into a public cloud.

Same subscription model on Scale appliances or certified third-party servers; not usable in public clouds.

Pricing | Scale Computing ↗
Support & lifecycle
Support offeringsThe support levels sold, and their hours.

ScaleCare Full Support (updates plus hardware failure analysis and replacement) or Software-Only Support. 24x7x365 phone for critical issues; chat and email Mon-Fri 2 AM-10 PM ET.

Scale Computing Support & Services Reference Guide ↗
Single point of support (hardware + software)One call for the whole stack, or separate vendors for hardware and software.

On Scale appliances ScaleCare covers hardware and software, including next-business-day part shipment in the US.

Scale Computing Support & Services Reference Guide ↗
Critical-issue responseTarget response time for a severity-1 issue on the top support tier.

Severity 1 initial response objective 2 hours (24x7 by phone); Scale reports phone calls answered in 13 seconds on average (2023).

Scale Computing Support & Services Reference Guide ↗
Release & update cadenceHow often feature and maintenance releases ship.

Frequent in-place updates on the GA branch plus periodic feature releases; exact cadence not published.

Scale Computing Support ↗
Lifecycle policyHow long a release is supported, and long-term-support options.

Updates included with an active subscription; no published fixed-length release lifecycle found.

Scale Computing Support ↗
Cost
Published list pricingWhether the OEM publishes prices, and the headline list price.

Online pricing tool gives list quotes. The hardware data sheet (2024) lists per-node prices incl. hardware and a 1-year subscription from $3,000 (HE153) to about $25,400 (dual-socket HC).

Scale Computing Hardware Data Sheet ↗
TCO drivers & hidden costsAdd-ons, minimums, hardware premiums and other costs that move the total.

Mirroring doubles raw capacity with no primary dedupe; 8-node cluster ceiling; HA needs three nodes; third-party backup or VDI tools extra; appliance refresh ties hardware to Scale.

Pricing Tool | Scale Computing ↗
Vendor & ecosystem
Vendor & ownershipWho owns and develops the platform, and recent ownership changes.

Scale Computing, Inc. (Austin, TX). Acumera acquired Scale Computing on 2025-07-31 and adopted its name; backed by Oaktree Capital; also owns Reliant and bought Adaptiv Networks (Feb 2026).

scalecomputing.com ↗
Ecosystem & communityPartners, certified applications, skills availability and community.

Smaller ecosystem: Lenovo, Supermicro, Intel, SNUC, Veeam, Acronis and niche edge partners; active user community but fewer skilled admins in the market.

Technology Alliance Partners | Scale Computing ↗
Lock-in & exit optionsOpen formats, standard hypervisors and how hard it is to leave. A higher score means less lock-in.

Proprietary storage and management on a KVM base; runs on commodity certified hardware and VMs can be exported, but it is a single-hypervisor platform.

SC//HyperCore Virtualization Suite | Scale Computing ↗
Regional availability & sovereigntyWhere the platform is sold and supported, and sovereignty considerations.

Sold through partners worldwide with global 24x7 phone support; US-headquartered private company.

Scale Computing Support & Services Reference Guide ↗

Editions

EditionModelMetricPrice / unit / yrBasisSupportBest for
SC//HyperCore on edge appliances (HE100 / HE500) ↗ Subscriptionper node / host $1,000 Estimate ScaleCare Full Support (24x7 phone for critical, hardware replacement)Stores, branches and industrial edge sites with a few VMs.
SC//HyperCore on HC-series appliances (HC1000 / HC3000 / HC5000) ↗ Subscriptionper node / host $2,500 Estimate ScaleCare Full Support (24x7 phone for critical, hardware replacement)SMB data centres and larger sites wanting 3-8 node HA clusters.
SC//HyperCore software on certified servers (HCL / VxRail reuse) ↗ Subscriptionper node / host $2,000 Estimate ScaleCare Software-Only SupportReusing Dell, HPE, Lenovo or Supermicro servers (including VxRail nodes) after leaving VMware.

Hardware routes

Support

  • ScaleCare Full Support ↗
    24x7x365 phone for critical; chat/email Mon-Fri 2 AM-10 PM ET · Sev-1: 2 hours (objective) · Software updates, hardware failure analysis and replacement (next business day shipping in continental US).
  • ScaleCare Software-Only Support ↗
    24x7x365 phone for critical; chat/email Mon-Fri 2 AM-10 PM ET · Sev-1: 2 hours (objective) · Software updates, documentation and community; no hardware replacement.

Deployment

Networks
LAN (management and VM traffic), Private backplane (storage and intra-cluster)
NICs
Four ports per node: two bonded LAN and two bonded backplane (1/2.5/10/25 GbE by model); 1-2 port edge nodes carry the backplane on a tagged VLAN
Switching
Redundant switches recommended; backplane on its own isolated subnet or VLAN
Witness
No external witness; a storage-only node can act as local witness
Time to deploy
Under an hour per cluster once racked; minutes with ZTP

Reference diagrams

Drawn for the default workload (200 VMs → 5 nodes). Build a comparison to size them for yours.
Logical architecture Sign in to download
Scale Computing SC//Platform (SC//HyperCore) - logical architectureLayers, services and management planes as the OEM names them. Generated by HCI Hero for "Scale Computing profile".ConsumersUsers & applicationsIT operationsWorkloadsWindows Server VMsLinux VMsPlatform servicesAIME self-healingengineSC//Reliant PlatformSC//AcuVigilnetworkingVeeam integrationVirtualisationHypervisor: SC//HyperCore (KVM-based)Distributed storageSCRIBE block engine with HEAT tieringSnapshots & clonesNetworking & securityNetworking: Bonded LAN and privatebackplane, VLANsSecurity: RBAC with OIDC, Secure Bootand vTPM for VMsHardware (5 nodes)Node 1x86 serverNode 2x86 serverNode 3x86 serverNode 4x86 serverNode 5x86 serverHardware routes: Scale Computing (Intel NUC platform), Scale Computing, Lenovo, Supermicro, Dell / HPE / othersMANAGEMENT PLANESC//HyperCore UI + SC//Fleet Manager- Lifecycle & upgrades- Monitoring & capacity- REST API & IaC- Multi-cluster / fleet- RBAC & SSOPROTECTION & DRSnapshots and cluster-to-clusterreplication- Native backupRecovery sitenative replicationSC//Fleet Manager(cloud-hosted)Sources: https://www.scalecomputing.com/sc-hypercore · HCI Hero by Niyyasoft
Implementation design Sign in to download
Scale Computing SC//Platform (SC//HyperCore) - implementation design5-node cluster · 2 x 32 cores · 1,024 GB RAM · 46.08 TB raw per nodeCore / aggregation network & WANTop-of-rack switch ATop-of-rack switch BMLAG / vPC peer linkOut-of-band management switch(BMC: iDRAC / iLO / XCC / IPMI)Cluster: 5 nodes · SC//HyperCore (KVM-based) · SCRIBE block engine with HEAT tieringNode 12x32c · 1,024 GB46.08 TB rawSC//HyperCore (KVM-base…Node 22x32c · 1,024 GB46.08 TB rawSC//HyperCore (KVM-base…Node 32x32c · 1,024 GB46.08 TB rawSC//HyperCore (KVM-base…Node 42x32c · 1,024 GB46.08 TB rawSC//HyperCore (KVM-base…Node 52x32c · 1,024 GB46.08 TB rawSC//HyperCore (KVM-base…BMC (1 GbE)RECOVERY SITE (optional)Snapshots and cluster-to-clusterreplication.Management: SC//HyperCore web UI on any node (no management VM) + optional SC//Fleet Manager (cloud) - runs as: SC//HyperCore UI + SC//Fleet ManagerNETWORKS & SUGGESTED VLANSVLAN 10 LAN (management and VM traffic) 10.20.10.0/24VLAN 20 Private backplane (storage and in… 10.20.20.0/24IMPLEMENTATION STEPS1. Size and quote with the Scale pricing tool2. Order pre-imaged appliances (or imaging service for HCL servers)3. Rack, cable LAN and backplane, power on4. Initialise the cluster from the CLI or via Fleet Manager zero-touch provisioning5. Configure networks, users and OIDC6. Migrate VMs (SC//Move, Veeam or Acronis)7. Set snapshot and replication schedules8. Register the cluster in SC//Fleet ManagerNICs: Four ports per node: two bonded LAN and two bonded backplane (1/2.5/10/25 GbE by model); 1-2 port edge nodes carry the backplane on a tagged VLANSwitching: Redundant switches recommended; backplane on its own isolated subnet or VLANTypical deployment time: Under an hour per cluster once racked; minutes with ZTPVLAN IDs and subnets are placeholders to replace with your own addressing plan. Sources: https://www.scalecomputing.com/documents/Data-Sheets/SC-Hardware-Data-Sheet.pdf

OEM references

HCI Hero by NiyyasoftHelp
ENEnglishDeutschFrançais