CPU: 2 vCPU (min.), 4+ vCPU (recommended, based on use of compression), 8+ vCPU (large-scale use with compression and deduplication)

RAM: 2 GB (min.), 8 GB (medium-scale use), 32+ GB (large-scale use with increased caching)

Additional RAM for Deduplication: 1 GB per 1 TB of deduplicated storage; e.g., 50 TB deduplicated storage = 32 GB (large. scale) + 50 GB for deduplication tables.  This additional memory is required when deduplication is configured for large amounts of storage in order to keep the deduplication tables in memory for best performance

Boot Disk: 30 GB hard disk for Linux boot and system disk

Data Disks: Virtual hard disks (VMDK) for data storage - any VMware-supported datastore is supported; e.g., local disks, fiber-channel SAN, iSCSI SAN, dual-path disks, etc.

Hardware RAID:  If your disk controller supports hardware RAID, then hardware RAID can be used to create VMware host datastores.

Software RAID:  If you prefer SoftNAS to handle RAID, then add VMDK's to the SoftNAS VM and configure software RAID in SoftNAS

iSCSI SAN:  SoftNAS can mount and support all VMware-supported disk configurations, including iSCSI SAN via software or hardware HBA

Networking: 1 GbE (min. for up to 120 MB/sec throughput), 10 GbE (up to 750 MB/sec throughput). Other VMware-supported networks are also supported; e.g., Infiniband.

HA Networking: It is recommended to configure VMware with Active/Active or Active/Passive vSwitch configurations so that SoftNAS running on a VMware host can tolerate a NIC or switch failure.  Use of "full mesh" HA switch configurations are also recommended, so that a switch failure does not interrupt SoftNAS storage access.

HA Host Failover: To support host failover, it must be possible for each host that SoftNAS can operate upon to have access to the Data Disks.  This can be accomplished by use of dual-path disks, such as those supported by HP, for example.  iSCSI or fiber-attached disks are also supported, provided VMware provides drivers.

CPU: 2 vCPU (min.), 4 vCPU (recommended, based on use of compression)

RAM: 2 GB (min.), 4 GB (recommended)

RAM for Deduplication: 1 GB per 1 TB of deduplicated storage

Boot Disk: 30 GB hard disk for Linux boot and system disk

Data Disks: Virtual hard disks (VMDK) for data storage - any VMware-supported datastore is supported; e.g., local VMware Workstation host disk

Software RAID:  SoftNAS can support software RAID; add VMDK's to the SoftNAS VM and configure software RAID in SoftNAS

Networking: NAT networking (default) is recommended; other network options supported by VMware Workstations (e.g., bridged, host) are also supported.

CPU/RAM: Small instance (min.), Medium instance (recommended), Large to High-Memory Instances (large scale)

RAM for Deduplication: 1 GB per 1 TB of deduplicated storage; e.g., 50 TB deduplicated storage = 32 GB (med. scale) + 50 GB for deduplication tables.  This additional memory is only when deduplication is configured for large amounts of storage

Boot Disk: 30 GB hard disk for Linux boot and system disk (all EC2 instance types provide enough space to install and use SoftNAS)

Data Disks: Elastic Block Storage (EBS) provides block data storage on Amazon EC2

Software RAID:  It is highly-recommended to configure EBS disks using SoftNAS software RAID to provide increased performance and data durability

Networking: 1 GbE (min. for up to 120 MB/sec throughput) - Small to Large instances provide up to 1 GbE connectivity.  Use High I/O instances for greater network throughput.

HA Networking:  EC2 does not support HA networking.

HA Host Failover: To support host failover, it is recommended to configure multiple, redundant SoftNAS instances running in separate availability zones or different geographic region data centers for maximum availability.