Patch for cost reduction of copy to S3

Patch for cost reduction of copy to S3

Installation of the patch will reduce costs drastically for customers who are using S3 (Between 5 to 20 times less expensive than previous version)

The improvements are:

  • For copied volumes which are larger than 512GB, worker’s volume type will be sc1 instead of gp2
  • Better data reading performance which results in creating up to 2 Worker volumes instead of up to 10 worker volumes for copying the data to S3

A patch for this issue is included in the latest version of CPM, v2.5.0, please upgrade to see these improvements.
Reference number – N2WS-4951, changed in v2.5
    • Related Articles

    • How to upgrade to the latest CPM version using the patch method

      How to upgrade CPM using a patch This KB article details the steps needed to upgrade the N2WS CPM server instance to the latest version using the patch method. Prerequisites: Make sure you have no active backup policies running or DR ( including ...
    • N2WS-21382 - S3 copy worker issues

      Issues: 1. In some rare cases, worker's volumes are not removed after worker instance is terminated 2. Unnecessary alert is raised when none default worker type is used: Worker i-12345 was launched for FLR as t2.micro, which may not an optimal ...
    • "Cost Explorer Query Failure" alert in CPM 3.0

      After upgrading to CPM 3.0, you may see an Alert in the console which says "Cost Explorer Query Failure".  If you view the Alert, you will see an AccessDeniedException: The cause of this alert is due to the CPM role permissions not being updated with ...
    • Troubleshooting common Cost Explorer issues

      This  document will go through the steps one can take to resolve common issues related to the CPM Cost Explorer feature   1.  Required Permissions Make sure that you have updated the CPM instance role and all users associated with CPM with the latest ...
    • How to upgrade CPM using a patch

      Please note: upgrading using patch does not upgrade Apache General: 1. It is recommended to deploy the patch when you have no active backup policies, DR or recovery running - as it will restart Apache and require few min downtime. 2. When using ...