Data Cube: Hardware Specifications

Before you deploy Data Cube, use these guidelines to select the appropriate hardware for your index server and content analyzer client.

File System Data Sources

Use these guidelines to select the appropriate hardware for the index server and content analyzer client.

Entity Extraction with Content Indexing

Component

Large

Medium

Small

Objects per node (estimated)

80 million

40 million

20 million

Source data size per node

40 TB

20 TB

10 TB

CPU or vCPU

32 cores

16 cores

8 cores

RAM

64 GB

32 GB

16 GB

Disk space

(SSD class disk recommended)

2 TB

1 TB

500 GB

Content Indexing from Source

Component

Large

Medium

Small

Objects per node (estimated)

100 million

50 million

25 million

Source data size per node

50 TB

25 TB

12.5 TB

CPU or vCPU

32 cores

16 cores

8 cores

RAM

64 GB

32 GB

16 GB

Disk space

2 TB

1 TB

500 GB

Databases, Websites, Salesforce, and Other Data Sources

Use these guidelines to select the appropriate hardware for the index server and content analyzer client.

Entity Extraction

Component

Large

Medium

Small

Objects per node (estimated)

200 million

100 million

50 million

Source data size per node

20 TB

10 TB

5 TB

CPU

32 cores

16 cores

8 cores

RAM

64 GB

32 GB

16 GB

Disk space

(SSD class disk recommended)

1 TB

500 GB

250 GB

Content Indexing

Component

Large

Medium

Small

Objects per node (estimated)

30 million

15 million

7.5 million

Source data size per node

20 TB

10 TB

5 TB

CPU

32 cores

16 cores

8 cores

RAM

64 GB

32 GB

16 GB

Disk space

(SSD class disk recommended)

3 TB

1.5 TB

750 GB

Considerations

  • For content indexing use cases, the following guidance assumes that 50 percent of documents are eligible for content indexing.

  • All of the calculations are approximations and can differ from organization to organization.

  • If you have an environment outside of the following use cases, contact Commvault for assistance.

Loading...