N2WS-22712 - Unable to select S3 source for recovery when N2WS is in recovery mode

• Related Articles

• EBS/RDS DR & Recovery with KMS key

  When copying cross account an EBS/RDS Volume encrypted with custom KMS, a KMS key should also be available in the other account. There are 2 ways that CPM uses for checking KMS key - Alias & Tag KMS Tag When using custom tag, you are telling CPM to ...

• N2WS-23233 - Recovery from DR region might fail or select wrong snapshot

  Issue: During recovery from DR region, wrong snapshot might be selected which can lead to recovery failing or recovering incorrect data. Solution: v4.2.0 & v4.2.1 - upgrade to 4.2.2 and install patch v4.2.2 - install attached patch

• Recovery of an encrypted volume may fail: "Not authorized to use key"

  Issue: Performing a cross account recovery of an encrypted volume, or of an instance containing an encrypted volume may not work if the target account cannot access the encryption key from the source account. Error may appear in the CPM Server log as ...

• Error on Instance recovery - Instance recovery failed: Failed checking snapshot availability

  Issue: Error - Instance recovery failed: Failed checking snapshot availability When running a recovery, first CPM downloads the data from the bucket, then it creates a temporary snapshot and then creates the instance. This error occurs when a timeout ...

• CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation

  CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation Issue: When CPM is in recovery mode being used for DR drills, the original CPM’s process to detect “zombie” worker’s can be ...