Allocate the data volumes of the similar sizes for MSDP to have better load balancing performance.

Each data volume size is more than 4 TB.

Have multiple data volumes for each engine to gain better throughput.

Split a bigger backup policy to smaller ones

In most cases, one backup job goes to one MSDP engine at the same time even if multistream is enabled for the backup policy. If the current MSDP engine, which is taking a backup job hits the high space watermark, the following backup data would be sent to a second MSDP engine. If the backup data is too big for up to 2 MSDP engines to persist, the backup job fails. When more MSDP engines are added, the backup jobs may not be evenly balanced on each MSDP engine at the first a few hours or days. If the situation keeps longer beyond your expectation, consider to re-plan the backup policies, by splitting a bigger backup policy to two smaller ones, to help MSDP Scaleout to balance the new backup jobs more faster.

After scaling up, the memory and CPU of the existing node group may not meet the performance requirements anymore. In this case, you can add more memory and CPU by upgrading to the higher instance type to improve the existing node group performance or create another node group with higher instance type and update the node-selector for the CR accordingly. If you create another node group, the new node-selector does not take effect until you manually delete the pods and deployments from the old node group, or delete the old node group directly to have the pods re-scheduled to the new node group.

Ensure that each EKS node supports mounting the number of data volumes plus 5 of the data disks.

For example, if you have 16 data volumes for each engine, then each your EKS node should support mounting at least 21 data disks. The additional 5 data disks are for the potential MDS pod, Controller pod or MSDP operator pod to run on the same node with MSDP engine.