Recommended instance sizes and volume types for CPM Server instances

Recommended instance sizes and volume types for CPM Server instances

EC2 Instance sizing guidelines

Here are the recommended instance sizes for CPM Server instances:
  1. Up to 200 instances   -  T3.medium
  2. Up to 500 instances   -  M5.large, C5.large, R5.large, C6i.large, R6i.large, M6i.large, C7i.large, M7i.large
  3. Up to 1000 instances  - M5.xlarge, C5.xlarge, R5.xlarge,  C6i.xlarge,  R6i.xlarge, M6i.xlarge,C7i.xlarge, M7i.xlarge
  4. Up to 2000 instances - M5.2xlarge, C5.2xlarge, R5.2xlarge,  C6i.2xlarge,  R6i.2xlarge, M6i.2xlarge, C7i.2xlarge, M7i.2xlarge
  5. Up to 4000 instances - M5.4xlarge, C5.4xlarge, R5.4xlarge,  C6i.4xlarge,  R6i.4xlarge, M6i.4xlarge, C7i.4xlarge, M7i.4xlarge
  6. Over 4000 instances - please move additional instances to a new CPM Server

Important: when using the S3 Backup feature, please upgrade to the next available instance size, but no smaller than "large" - this feature can be very memory consuming

Additional recommendations:
  1. Usage of T3 is not recommended for environments with over 200 protected instances or intensive workload.
  2. CPM is more IO-intensive than CPU-intensive, improving IO performance will usually gain better results than improving CPU performance.
  3. When using burstable instances (T3 type), it is recommended to use unlimited mode:
    https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-unlimited-mode.html
  4. R5 instances are much more cost-effective per GB and have more memory than other types of the same size, if the main sizing issue you have is memory usage, then it is recommended to switch to R Family in the same size instead of increasing the size. 
  5. It is recommended to upgrade instance type to newer version of the same type, for example using R6i instead of R5. newer hardware usually has better performance for the same price. 
Please note:
  1. C5/M5 families are only supported from CPM v2.6
  2. T3 families are only supported from CPM v2.6
  3. R5 families are only supported from CPM v3.0
  4. R6i/C6i/M6i families are only supported from CPM v4.1
  5. C7i/M7i  families are only supported from CPM v4.2

Recovery:
  1. It is highly recommended to conduct recovery drills to ensure that the instance size can effectively manage real-life recovery scenarios.

This recommendation is based on the following assumptions:
  1. Instances have 3 volumes on average.
  2. No more than 20% of instances have Agents performing VSS/scripts.
  3. No more than 20% of instances are being backed up simultaneously (within 60 minutes from each other).
Exceeding these assumptions may require larger instance sizes.
In addition, performing large number number of restores in parallel might also require larger instance size

To resize the instance, please follow this guide:
  1. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html


EBS volumes sizing

Here are the recommendation for the volumes sizing:
  1. GP2 is not supported in versions 3.2.1 and above. 
    Please note: GP3 is 20% cheaper and provide 3000 IOPS (compared to only 100 IOPS in GP2).
  2. If GP3 is not available, you can switch to IO1 or IO2 with minimum 1000 IOPS.
  3. For cpmdata volume
    1. For over 200 instances/targets or 600 volumes, you may need to raise IOPS further
      we recommend to add another 500 IOPS per each 100 instances or 300 volumes above this limit.
Please note:
  1. We added support for IO2 in v3.2.0
  2. We added support for GP3 in v3.2.1

For best results, it's recommended to switch to instance types that are EBS-optimized and review the instance baseline IOPS.  more details available here: 

You can switch the volume's type with zero downtime by following this guide:
  1. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/console-modify.html

Since achieving more IOPS might requires resizing the volume, please follow this guide to allow OS to see the new size correctly:
  1. https://support.n2ws.com/portal/kb/articles/resizing-the-cpmdata-volume
Note: Please make sure to first check AWS documentation for maximum IOPS per GB BEFORE resizing the volume


Using "gp2" volume may cause severe performance issues, including failing backups/DR and unexpected restarts of CPM Agent/Server.

    • Related Articles

    • Recommended VM Types for CPM Server in Azure

      Recommended VM Types for CPM Server in Azure On this page • Azure VM Sizing Azure VM sizing Here are the recommended instance sizes for CPM Server instances when working in Azure: Up to 200 instances - Standard_A2_v2, Standard_B2s Up to 500 instances ...

    • How to change instance type of S3 worker instances CPM

      Some clients may need worker instances with more ram and CPU power. You can use this process to modify the ec2 instance type used for worker instances. We highly recommend not to change size unless it was suggested by the N2WS support team. Otherwise ...

    • How to fully encrypt CPM server root and data volumes in EBS

      The steps below will help you properly encrypt the CPM server root and data EBS volumes for an existing CPM server instance. If encrypting only the data volume, it is still necessary to launch a new CPM server instance. Then during initial CPM ...

    • "Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade

      The following error message may be displayed when trying to upgrade the CPM instance using a new AMI: Could not attach volume vol-1234567890abcdef to instance i-abcdef0123456789. Reason: Cannot attach volume 'vol-1234567890abcdef' with Marketplace ...

    • Resizing the cpmdata volume

      Resizing the cpmdata volume is done like any other ec2 instance. The general procedure can be found here - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html IMPORTANT - Before extending a file system that ...