Hardware Recommendations
Hardware Recommendations
The euroNAS HA Cluster is not tied to specific hardware.hardware Itand runs on standard x86 server hardware.platforms, You havegiving full freedomflexibility for initial deployment and future expansions.expansion.
CPU
For the bestoptimal performance, weserver-grade recommendprocessors thefrom following processors: XEONIntel or AMD serverare CPU.recommended, Dualsuch as Intel Xeon or AMD EPYC. Dual-socket CPU configurations willcan providebe youused withwhere evenadditional bettercompute performance.capacity is required.
Installation Drive
ForThe theoperating best performance of the Enterprise Virtualization OS, itsystem should be installed on ana SSDdedicated SSD, with a minimum sizecapacity of 30250 GB. This installation drive is configuredreserved separatelyfor the system only and is kept separate from the data drivestorage. – itIt is not possibleintended tofor installhosting theapplication VMsdata onor thestorage installation drive.workloads.
HardStorage Drives
The operating system requires its own drive, and for data, you need at least one additional drive. A data drive can be a simple hardseparate drive or a software/hardware RAID.
Itpool is stronglyrequired recommendedfor todata usestorage. server-This can consist of individual disks or RAID configurations, depending on performance and resilience requirements. Server-grade hard drives. Desktop/notebook hard drives are strongly recommended, as consumer-grade disks are not recommended.
for sustained workload or failure scenarios. Hybrid cacheconfigurations functionalityare allowssupported, aallowing mix of slowslower SATA or SAS harddrives drivesto be combined with SSD or NVMe harddevices drives.for caching and performance optimisation.
System RAMMemory
TheA serverminimum should have at leastof 16 GB ofRAM RAM.is required, with additional memory recommended depending on workload and storage configuration.
Network
YouA needminimum atof least 2two network cards.interfaces Multiple,is teamedrequired, networkalthough portsadditional provideinterfaces higherare redundancyrecommended for resilience and performance.
ToThe achievecluster optimalseparates performance,heartbeat ittraffic for node health and coordination, replication traffic for data synchronisation between nodes, and client access traffic for external connectivity.
For best practice, use dedicated interfaces for replication traffic and avoid mixing replication and client traffic where possible. 10 GbE is recommended to use 10 Gbit network cards, especially for mirroring. To save on a switch, it is possiblereplication to connectensure themconsistent directly.
TheDirect clusternode-to-node distinguishesconnections betweencan heartbeat and replication network.
All network controllers notbe used for replication willwhere beappropriate, usedalthough forswitched communication with the outside world and for communication between the nodes.Network cards used for mirroring between the serversconfigurations are partalso of the replication network.supported.
For thehigher bestavailability, performanceuse multiple interfaces with bonding for resilience and highthroughput. availability,Avoid theplacing serverall shouldbonded have 4 individual network interface cards with a minimum bandwidth of 1 Gigabit (10 Gigabit recommended). They should be configured as two separately connected networks. One of the connections should be connected to the corporate network. The other connection should be connected to the other serverlinks on a privatesingle replicationphysical network.NIC, Forand the replication network, we recommend a 10 Gigabit network.Ifwhere dual-port cards are used, each port on the cardports should be assignedsplit across bonds to avoid a separatesingle bond so that the failurepoint of onefailure.
Static doesIP not result in the failure of the entire bond.DHCPaddressing should not be used.The DHCP is not recommended, as IP changes can disrupt cluster would no longer communicate with the other node if the IP address changed.communication.