Error when trying to configure S3 Copy "The cpmdata policy must be configured before 'Copy to S3' can be used".

When trying to create an S3 Repository in the CPM Manager screen you will get an error if the cmpdata policy

is not configured and enabled like this:

"The cpmdata policy must be configured before 'Copy to S3' can be used".

Resolution:  

Please create a policy named "cmpdata" by selecting the Policies tab in the N2WS Manager screen. Then click on the "New Policy Button"

 

Please enter the Name the policy as  "cpmdata" and make sure that the Status is enabled and that a valid schedule is applied to this policy under Schedules. Then click the Apply Button.

You will now see the newly created cpmdata policy in the screen.

Once this is completed you can now go back to the create Repository screen by hitting the S3 Repositories button at the top of the screen.

Please fill in the requested information Repository Name, User, Account, AWS Region, and AWS Bucket Name.

Note: AWS S3 bucket names are globally unique. This means that if someone else has a bucket of a certain name,

you cannot have a bucket with that same name. te

Please click the Create Button:

You get a progress indicator stating it is creating the Repository.

Then the new S3 Repository will appear in the below section.

accepted

• Related Articles

• Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy

  Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy. This means that you are trying to create the "cpmdata" policy using an account that isn't the ...

• cpmdata policy might fail with error volume does not exist

  Issue: If the volumeID of the CPMDATA volume(EBS) changes (due to restoring CPM from snapshot for example),  This might cause the cpmdata policy to fail, still showing the old VolumeID: Solution: try to run cpmdata policy ASAP

• Cleanup from S3 or S3 copy fails with error: Worker configuration not found

  Issue: When running a Copy to S3 policy, you may receive an error that states Worker configuration not found Or when S3 cleanup runs, you may see similar error in S3 cleanup logs. Solution The error will specify the region and/or account that a ...

• N2WS-21963 - Copy to S3 fails with Failed to stop processor(s)

  Issue: Copy to S3 is failing with following error ERROR: add_error(segment_handler.py:322) copy of md table of segment 1 of volume vol-12345678, instance i-0987654321, backup 123 fail : Failed to stop processor(s): not all blocks were processed ...

• Must Gather information for CPM: how to collect relevant details for support.

  When opening a support ticket, please provide the following information. You can attach the collected files (preferably in a single archive) to the ticket or an email reply (up to 20MB). For larger files, please ask the support team for FTP ...