System Requirements
This section provides information about the system requirements for all elements of the system.
Anvil (Metadata Server)
It is important that Anvil is given sufficient resources to deliver low-latency metadata to the clients. The Anvil will take full advantage of the resources assigned as it runs continuous optimizations on the metadata and placement of data. It is normal for the Anvil to operate at 50% or higher CPU utilization even with a modest metadata load in large file environments. If the system becomes heavily loaded, it will, for example, automatically reduce the amount of system resources that are dedicated to continuous optimization.
The following section provide the minimum recommendations for virtual and bare-metal deployments.
Anvil Requirements for Enterprise Scale Configuration
| Virtual Machine | Bare-metal | |
|---|---|---|
| CPU Cores | 24 vCPU | 24+ cores Intel based 2.5+ GHz processor(s) |
| Memory | 64+ GB. 1 GB/vFilO Share | 64+ GB. 1 GB/vFilO Share |
| Boot disk | 200 GB | 200 GB (Hardware RAID recommended) |
| Additional disk drives for metadata storage | (2x) 400 GB backed by SSD. Supports up to 200 million files | (2x) 400 GB. NVMe recommended. Hardware RAID is not needed |
| Network adapter | (2x) 10 GbE. One link is dedicated to HA services | (2x) 10 GbE. One link is dedicated to HA services |
Anvil Requirements for Mid-Market Configuration
| Virtual Machine | Bare-metal | |
|---|---|---|
| CPU Cores | 8 vCPU | 8+ cores Intel based 2.5+ GHz processor(s) |
| Memory | 16+ GB. 1 GB / vFilO Share | 16+ GB. 1 GB / vFilO Share |
| Boot disk | 200 GB | 200 GB (Hardware RAID recommended) |
| Additional disk drives for metadata storage | (2x) 400 GB backed by SSD. Supports up to 20 million files | (2x) 400 GB. NVMe recommended. Hardware RAID is not needed |
| Network adapter | (2x) 10 GbE. One link is dedicated to HA services | (2x) 10 GbE. One link is dedicated to HA services |
DataCore vFilO Data Services (DSX)
The resources required for DSX depends on what services are in use. For example, if a single DSX is used for Portal, Store and Cloud Connector and Mover, then it will need more resources vs. if multiple DSX nodes are deployed. The specifications below will match what is needed to get started. DSX nodes can be easily added (and removed if needed) after the initial installation to match a scale-as-you-grow deployment.
DSX Requirements for Enterprise Scale Configuration
| Virtual Machine | Bare-metal | |
|---|---|---|
| CPU Cores | 8+ vCPU | 8+ cores Intel based 2.5+ GHz processor(s) |
| Memory | 16+ GB | 16+ GB |
| Boot disk | (1x) 100 GB | (1x) 100 GB (Hardware RAID recommended) |
| Additional disk drives for metadata storage | Only needed when Data service instance is providing additional storage | Only needed when Data service instance is providing additional storage |
| Network adapter | (1x) 10 GbE | (1x) 10 GbE |
DSX Requirements for Mid-Market Configuration
| Virtual Machine | Bare-metal | |
|---|---|---|
| CPU Cores | 4+ vCPU | 4+ cores Intel based 2.4+ GHz processor(s) |
| Memory | 8+ GB | 8+ GB |
| Boot disk | (1x) 100 GB | (1x) 100 GB (Hardware RAID recommended) |
| Additional disk drives for metadata storage | Only needed when Data service instance is providing additional storage | Only needed when Data service instance is providing additional storage |
| Network adapter | (1x) 10 GbE | (1x) 10 GbE |