Linux scripts may start failing after upgrading to a new CPM version (using AMI) or migrating CPM to a different account/region

• Related Articles

• How to migrate a CPM Server to a different region

  Here are the steps for migrating a CPM Server to a different region: 1) Stop your existing instance (when no backups/DR are running). 2) Take a snapshot of the data volume 3) Copy that snapshot to the target region 4) Create an EBS volume from the ...

• How to migrate a CPM Server to a different account

  Attention: this procedure only applies to non-BYOL editions. BYOL customers should contact sales@n2ws.com and ask to add the new account to their license prior to attempting a migration using the process described below. Important: Before performing ...

• Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error

  Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error: Error - snapshot of independent volume vol-0123456789abcdef failed to start. Reason: The volume 'vol-0123456789abcdef' does not exist This error may ...

• Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed" and "Could not migrate database to version 2.6.0 scheme"

  Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed". The following error may be printed in the "config_shell_commands.log" file: perform_shell_commands(:629) Could not migrate database to version 2.6.0 scheme, ...

• CPM Server may fail to finish configuration when upgrading from v2.1.3 to v2.1.3a using AMI

  At the end of configuration, when clicking at the "Click here to start CPM" link, CPM may go back to a page asking to enter instance id. Rebooting the instance and going directly to the /console URL doesn't help. The following error can be found in ...