Question about Back-end Size for Disk Storage

Question

I’m a little confused about Back-end Size for Disk Storage in our MAs.

Back-end Size for Disk Storage

	Extra large	Extra large	Large	Large	Medium	Medium	Small	Extra small
Grid 9 10	1 DDB location per node	2 DDB locations per node	1 DDB location per node	2 DDB locations per node	1 DDB location per node	2 DDB locations per node	1 DDB location per node	1 DDB location per node
1 Node	Up to 250 TB	Up to 500 TB	Up to 150 TB	Up to 300 TB	Up to 75 TB	Up to 150 TB	Up to 50 TB	Up to 25 TB
2 Node	Up to 500 TB	Up to 1000 TB	Up to 300 TB	Up to 600 TB	Up to 150 TB	Up to 300 TB	Up to 100 TB	Up to 50 TB
3 Node	Up to 750 TB	Up to 1500 TB	Up to 450 TB	Up to 900 TB	Up to 225 TB	Up to 450 TB
4 Node	Up to 1000 TB	Up to 2000 TB	Up to 600 TB	Up to 1200 TB	Up to 300 TB	Up to 600 TB

We are planning to deploy 2000TB for each 2 physical Node MAs. By my undertanding, using 2 DBBs in 2 Nodes, the maximum would be 1000 TB.

My question: This is a point of failure and can limit the writing or anything else?

Thanks (first post).

Page 1 / 1

Hi renan,

This basically says, to support 2pb we would expect to need 4 MAs, and the DDB would be 6 partitions (max) spread out among those. This is what we’ve tested.

It doesn’t mean it will immediately break if you go over these numbers, but there could be performance issues down the road if undersized.

Thanks @Jon Kuzmick I will talk to our architeture teams to see what we can do before we deploy these servers.

Reply

Jon Kuzmick · Answer

Hi renan,This basically says, to support 2pb we would expect to need 4 MAs, and the DDB would be 6 partitions (max) spread out among those. This is what we’ve tested.It doesn’t mean it will immediately break if you go over these numbers, but there could be performance issues down the road if undersized.

Back-end Size for Disk Storage

Reply

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded