Implementation of N2WS Veeam Cloud Protection Manager (CPM 2.3.0d)

Click on the Lunch instance Menu on AWS

Under AWS Market place, select the right version (Here I will be selecting the free-tier for testing)

Step 1. Cloud Protection Manager Free Edition

Note: You can select whatsoever edition is applicable to you from here. In the future after testing I will have to use a different Edition to support my need.
When this AMI is selected, this will be prompted below to show the product details etc.

Step 2: Select the instance type:

Step 3: Select all right Instance configuration Details,
Such as Network, subnet, IAM role, etc.

Step 4: Add storage

Add Tags additionally in the next steps (not applicable to me)

Step 5: Select an existing Security Group or Create a new Security group

Step 6: Now review and relaunch. This is basically how an EC2 instance is created.

Note: Remember to create a new keypair or select an existing keypair or else, you wouldn’t be able to access this newly created instance and download this keypair.

And the username is inbuilt in the AMI: which is cpmuser.

Step 7: Finally click on launch this instance.

Locate the newly created EC2 instance and associate it with an EIP Address. (This is needed in order to be able to connect to it over the internet).

Here, you will need the PuTTY Key Generator (Load the .pem file in order to be able to download the private key.)
– If you are a Mac OS user, this process is a bit different. (Select the instance and click on connect, here you can see the instructions).

Part 2:  Create a role for AWS permission/roles for CPM Operation

– Create a policy and this policy can be found in this link below.
https://support.n2ws.com/portal/kb/articles/what-are-the-required-minimal-aws-permissions-roles-for-cpm-operation

  • Create a policy on AWS
  • Create an EC2 Role

And attach the policy to it above

Click on next and enter the role name and create.

Now locate the server under EC2
– Right click on the server and perform the follow steps

Select the role and click on apply

Step 4: Next step is to create an IAM user with the Administrative privilege

Part 3

Now proceed to access the site by entering the URL as shown below. Note, https:// must be included or else no access will be. You can create a DNS record for this to have a human readable name (FQDN) instead of using just the IP Address.

https://xx.xxx.xx.1xx/

Copy the CPM Instance ID and click on next

Accept the License Agreement and click on next

Enter the account information as shown in step 2 below. This will be the administrators root account to CPM. PLEASE fill in the information.

Select the configuration as it suits you below.

Select according to your need here (I will leave all as default as this is a test server) and come back to finish the configuration.

Note: You are free to choose any port but ensure you have this rules allowed in the NACL and also on the Security Group.

Next step is to register the account. This is the account is needed should incase CPM wish to contact you.

If all rights (policies), Role attached to the server and IAM Administrative rights are attached,

Now sign-in and access the CPM – Cloud Protection Manager

Step 4: After Signing in, you are dropped into this window (console)

Now Assign an account to Cloud Protection Manager,
– Click on Add Accounts in the console above

Enter the information but ensure you chose the role defined to avoid asking for Access Key ID etc. when using the IAM User

As shown below

After successful creation, the window below will be displayed

Step 5:
Now create a backup scheduler and a policy (What you would like to backup)

Click on schedule
– Add new Schedule

Schedule Windows Opens up as shown below
– Enter the name and the possible backup days and start time etc. in the schedule window below and click on Apply.

After entering the schedule information above, This window will be displayed

Now create the Policy

The policy window opens up (Here you can associate the policy to the Account created previously),
– Select the generations to be saved and associate the policy also to the schedule). Currently, 34 is the highest generation to save and I will select 7 since we are backing up for seven days

And click on Apply. To have our instances backup, we will configure the policy by selecting the Backup Targets 

Now click on Add Instances or whatever service you wish to backup (My focus is on instances and I will demonstrate this now).

And the Add instance Window Opens up.
Note: You can select any region you wish to backup (We will do this for 6 different regions).
– Lets start with EU(Frankfurt region) 

Note: You can select multiple instances and use the search button above and click on close.

Henceforth, the CPM will start creating operational backup and you do not needed to worry at all.  Also when you navigate to Policies, you can also create a DR (Disaster recovery) as well.

You can also run the backup manually as shown below and the green status signifies backup will run shortly.

And also, in this window, you can create a Disaster Recovery here by clicking on the DR icon above. So should in case there is a disaster in any region, N2WS CPM will create a DR into another region.
Note: Multiple region can be chosen here.

Just have it enabled and select your desired region(s)

To watch the instance backup, we can go to the Backup Monitor and view the status (progress) of our backup

Logs showing backup status

    • Tue 05/15/2018 04:15:54 PM – Info – Backup is agentless, managed by CPM Server
    • Tue 05/15/2018 04:15:54 PM – Info – Starting. Fired by schedule: Immediate/ASAP
    • Tue 05/15/2018 04:15:57 PM – Info – All snapshots started successfully
    • Tue 05/15/2018 04:16:17 PM – Info – snapshot of instance Server – xxxxxxxx, volume vol-xxxxxxx7 completed successfully.
    • Tue 05/15/2018 04:23:01 PM – Info – snapshot of instance (Server – xxxxxxxx), volume vol-0xxxxxxxxff completed successfully.
    • Tue 05/15/2018 04:24:32 PM – Info – instance i-0xxxxxxxxxxxb AMI completed successfully.
    • Tue 05/15/2018 04:27:34 PM – Info – snapshot of instance Server2 – xxxxxxxx, volume vol-0xxxxxxxxxff completed successfully

After a successful backup, as shown below. The Status ‘backup successful‘ will be displayed.

Note: For your information, since this is incremental, the first backup will usually take longer.

See the next article on how to recover an instance using N2WS CPM