Submit a Ticket
S3 copy fails with error: Error - Worker configuration not found
An error may be recieved stating “A Problem Occurred (500)” when restoring an instance with multiple NIC’s
Worker did not establish connection / 0% S3 copy progress for extended period of time
CPM may mark a backup as successful although not all snapshots succeeded
CPM may abort Tag scanning with error "New policy xyz has more than one template”
Instance may be removed from the policy once a tag scan is performed
A wrong account may be listed in the Snapshot View Report for cross account replicated snapshots
DR may fail with "DR encountered an internal problem and failed" instead of printing the actual permissions issue
Permission check may fail with the error "User not found", if CPM was deployed using CloudFormation
How to improve CPM’s performance or overcome high memory consumption by creating a swap partition
AD FS may produce “An error occurred” page when logging in or performing Test Connection
Encrypted Snapshot Recovery from DR account may fail with the “Given key ID is not accessible” error
Encrypted Snapshot may fail DR with the “Given key ID is not accessible” error
DR of an encrypted snapshot may fail with the “Not Authorized to use key” error
Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error
Some backups may not run on schedule while other backups still run using the same schedule
CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use"
CPM server may display error "Signature validation failed. SAML Response rejected"
CPM Server may display error "Problem Occurred (500)" during the Identity Porvider configuration
Failed to open IdP login page or to test connection with the errors: "HTTP Error 503. The service is unavailable." or "404 - File or directory not found."
Login to the CPM using an IDP may fail with the "Invalid issuer" error message
DR copy may fail with "Failed looking for source KMS. Error: Request limit exceeded” error
DR snapshots may get encrypted with default encryption key on target region instead of custom key
Restoring an instance may not restore tags
Add support for Cross account DR of RDS and Aurora snapshots which are encrypted with custom shared key
Cross account Recovery of an encrypted snapshot with shared custom encryption key may fail
Explore may fail with "Invalid value '/dev/xvdp' for unixDevice"
CPM may not retry Tag Scanning if scanning fails due to RequestLimitExceeded
Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x
CPM may generate an error in the logs when creating snapshots with tags that begin with “aws:”
CPM supports custom encryption keys for DR
Basic API example for CPM login and retrieving the list of CPM users using powershell
Cross-region DR copy of encrypted snapshot may fail with "Copy failed due to an AWS limitation regarding default encryption key” error
Scan tags operation may hang if there are many Aurora clusters in an account
CPM instance backups may hang after upgrading to 2.3.0
CPM may restore "AMI only" snapshots with wrong volume type
Cleanup process may end abruptly with UnboundLocalError after upgrade to v2.3.x
Backup scripts may fail after upgrading to CPM 2.3.0
CPM may fail to clear “Explore” sessions which are not properly closed
Cross Account and Cross region DR of encrypted RDS may fail
"DR was trivial - no snapshots to copy" message may appear in the backup logs
Recovery of a dedicated host may fail
CPM Configuration Wizard may not allow to set the "AWS Authentication" option, resulting in "Could not authenticate with AWS" error
"Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade
How to setup AWS CloudTrail tracing for CPM Issues
CPM IDP configuration may fail if CPM is configured with custom DNS
File Level Recovery may fail with error "The reason could be missing/unsupported file system"
File-level recovery may fail with "Reason: In order to use this AWS Marketplace product you need to accept terms and subscribe"
A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error
Recovery of an encrypted volume may fail: "Not authorized to use key"
Show more Solutions
Help Desk Software
by Zoho Desk