Cloud Protection Manager: N2WS Veeam CPM Guide

Cloud Protection Manager by N2WS stands as a premier solution for enterprise backup, recovery, and disaster recovery needs within the Amazon Web Services (AWS) ecosystem. With a focus on Amazon Elastic Compute Cloud (EC2), Amazon Relational Database Services (RDS), Amazon Redshift, Amazon Elastic File System (EFS), Amazon Simple Storage Service (S3), Amazon Aurora, and Amazon DynamoDB, N2WS offers cutting-edge capabilities to ensure data security and availability.

Kindly refer to these related guides to more on other Veeam products. How to migrate Veeam MsSQL Database to a new MsSQL Server, how to implement N2WS Veeam Cloud Protection Manager (CPM 2.3.0d), and the advantage of using a 3rd party software for Backup (N2WS by Veeam) over AMI.

Kindly follow these steps to recover backup via N2WS Veeam  CPM.

Enhanced Recovery Workflow with Cloud Protection Manager

When utilizing Cloud Protection Manager, as depicted in the image below, the recovery of backup instances becomes notably streamlined. Furthermore, this approach surpasses exclusive AMI reliance, assuring instance configuration preservation, except EIP. Attaching an EIP within a VPC while launching a new instance is not feasible.

Note: When utilizing Cloud Protection Manager, it’s important to note that due to the incremental nature of the process, the initial backup might typically require more time than subsequent ones.
– Next select instance as I wish to recover the whole instance as shown below

Which will prompt the Instance Recovery Window.

In the realm of safeguarding your cloud infrastructure, Cloud Protection Manager steps to the forefront. Follow the guidelines below to input all essential details, which might vary based on your unique situation.

And this will prompt you to confirm performing Recovery Operations.

Select Okay.  The green status showing the successful recovery operation launched

Now Open the resource Monitor to view the progress

Note: In the context of Cloud Protection Manager, the failure in question stems from the persistence of the identical private IP address on the server that was subjected to backup.

Therefore, this goal is successful. And I performed using a dummy device and it worked.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.