> Essential > Storage > Distributed Storage

System Requirements for Distributed Storage

Verify that your environment meets the system requirements for Distributed Storage.

Hardware Sizing Guidelines for Distributed Storage

Three storage servers configured similarly form the base cluster. Configuration is based on raw capacity of servers (HDDs). The current recommended data resilience method is erasure-coding (4+2) for backup workloads and RF3 for copy data management workloads. Here are the supported configurations when Commvault software is used for data-protection:

Description

Small

Medium

Large

Jumbo

Raw capacity per node

144 TiB

288TiB

336TiB

384TiB

Dual Boot Disk

2 x 480 GB SATA RI SSD or M.2

2 x 480 GB SATA RI SSD or M.2

2 x 480 GB SATA RI SSD or M.2

2 x 480 GB SATA RI SSD or M.2

RAM

512 GB

512 GB

512 GB

768 GB

CPU

2 x Intel Silver 4214R - 12 core

2 x Intel Silver 4214R - 12 core

2 x Intel Silver 4214R - 12 core

2 x Intel Silver 4214R - 12 core

Data Storage (HDD/Flash)

12 x 12 TiB SAS HDD

24 x 12 TiB SAS HDD

24 x 14 TiB SAS HDD

24 x 16 TiB SAS HDD

Power Supply

Dual

Dual

Dual

Dual

NIC

Dual Port - 10 GB/25 GB

Dual Port - 10 GB/25 GB

Dual Port - 10 GB/25 GB

Dual Port - 10 GB/25 GB

NVMe (Metadata)

1 x 6.4 TiB

~*Metadata is stored on dedicated flash storage that can consist of Mixed Use (MU) SAS, SSD, and NVMe types.~

2 x 6.4 TiB

~*Metadata is stored on dedicated flash storage that can consist of Mixed Use (MU) SAS, SSD, and NVMe types.~

2 x 6.4 TiB

~*Metadata is stored on dedicated flash storage that can consist of Mixed Use (MU) SAS, SSD, and NVMe types.~

2 x 6.4 TiB

~*Metadata is stored on dedicated flash storage that can consist of Mixed Use (MU) SAS, SSD, and NVMe types.~

Hardware RAID Controllers

OS Mirroring

OS Mirroring

OS Mirroring

OS Mirroring

Note

Commvaultperforms deduplication for backup workloads, and Distributed Storage performs deduplication for copy data management workloads.

Port Requirements for Distributed Storage

Storage Nodes

The following ports must be opened on the storage nodes in bond1 or the private storage network:

Protocol

Port

Description

TCP

22

SSH

TCP

80

UI

TCP

443

https

TCP

2181

Zookeeper client

TCP

7000 - 7010,

7100, 7500,

8000 - 8100,

11001, 11002,

15000

gossip, thrift

UDP

1024 - 65535

UDP high ports

ICMP

N/A

icmp

Storage Proxies

The following ports must be opened on the proxies in bond1 or the private storage network:

Protocol

Port

Description

TCP

22

SSH

TCP

111

rpcbind

TCP

875

rquotad

TCP

2049

NFS

TCP

2224

pcsd

TCP

3121

pacemaker

TCP

3260

iSCSI

TCP

21064

dlm

TCP

33333

mountd

TCP

50000 - 50008, 50022

cvm thrift

UDP

111

rpcbind UDP

ICMP

N/A

icmp

The following ports are required by Commvault software when firewalls or port restrictions are in place in bond0 or the data protection network:

From

To

Protocol

Port

Description

All Clients

Network gateway

TCP

8403

Network gateway tunnel port

MediaAgents

Network gateway

TCP

8403

Network gateway tunnel port

CommServe

Network gateway

TCP

8403

Network gateway tunnel port

All Clients

MediaAgent

TCP

8400

CVD (Commvault Communications Service)

All Clients

MediaAgent

TCP

For comprehensive information on port requirements for Commvault software, see Network TCP Port Requirements.

To avoid issues introduced by the antivirus software, we recommend excluding the following directories in Distributed Storage proxies / MediaAgents from read, write and scan options, based on your company's policies for setting up antivirus software.

Note

The information provided is not a complete list of exclusions as the product may change with updates, versions, and innovation to existing or new software modules. It is recommended to test the functions of the software's features and monitor the processes and how they interact with the antivirus software during normal operations and work with the antivirus software vendor to achieve proper configuration and tuning of the antivirus software. The goal is to allow operations on the proxies,, so that the rules and schedules for the antivirus software operations do not interfere, impede or prevent successful operations on the storage device.

  • Disk library folders

    *:/**/CV_MAGNETIC/**

  • Deduplication database folders

    *:/**/CV_SIDB/**

    /ws/ddb/**

  • Hedvig binaries

    /hedvig/**

    /ws/hedvig/**

  • Mount folders

    /mnt/d?/**

  • Commvault binaries

    /opt/commvault/**

  • Directory to extract installation binaries

    /tmp/.gxsetup/**

    /var/log/.gxsetup/**

  • Log folders

    /var/log/commvault/**

Disclaimer

Implementing the anti-virus exclusions described in this document may increase the attack vulnerability risk to computers or network by malicious users or by malware or viruses. Before making these changes, it is recommended that the attack vulnerability risks that are associated with implementing these settings be evaluated. It is up to the discretion of the reader's and their company's policies whether to implement the guidelines recommended within this document. Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with a specific application or operating system. Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.

Loading...