Activating OnApp Disaster Recovery as a Service – Part 2 (private DRaaS)
In a previous blog post, I showed how to activate “Public” Disaster Recovery-as-a-Service (DRaaS) in your OnApp cloud.
DRaaS is one of the many ways OnApp helps service providers add value for end users: you can offer real-time replication for critical workloads, as an integrated part of your cloud.
In this post, I’ll explain how to activate DRaaS in “Private” mode, so you can replicate Xen or KVM virtual servers between two of your own OnApp clouds.
Before you start, contact firstname.lastname@example.org so that our team can verify that both OnApp clouds meet the license and configuration prerequisites; and so we can create your account on the DR dashboard at https://draas.io.
When your account is created for the DR dashboard, you will receive an email with instructions to set your password and log in. With that done, you need to follow these steps, in the OnApp UI, for both of your clouds:
Stage 1 – Disaster recovery API access
i. In the configuration page (‘Settings’ > ‘Configuration’) switch on the option ‘Enable DRaaS’, then save.
ii. Choose an existing user account (or create a new account) with the ‘administrator’ role. Note the email address.
iii. In the user account page, generate an API key and make a note of it for later.
iv. Create a whitelist for the user and add the IP address 184.108.40.206
Stage 2 – Add both clouds to the DR Dashboard
i. In the DR dashboard, go to the ‘clouds’ page and start the Cloud registration wizard. In step 1 of the wizard, set the label and subdomain.
ii. In step 2 of the wizard, you will be asked to specify the allowed IPs.
The IP addresses can be found by running the following command on every compute node in the zone:
curl -s checkip.dyndns.org | sed -e 's/.*Current IP Address: //' -e 's/<.*$//'
iii. In step 3 of the wizard, enter:
- The cloud URL as the API address
- The email address from before as the Admin email
- The API key from before as the API token
Remember to complete these actions for both of your clouds.
Stage 3 – Add the replication provider zone to the DR Dashboard
i. In the DR dashboard, go to the ‘Clouds’ page to see the list of clouds. Find the replication provider cloud and select the tools button and ‘view’ option. From here, you can begin the ‘Register New Hypervisor Zone’ wizard.
ii. Choose the ‘Private Provider’ type in step 1 and the desired compute zone in step 2.
iii. In step 3 (‘Select Transitional networks’), select networks that should not be used for the replication traffic. Ie:
- They contain IP addresses which are moveable
- They contain IP addresses which are unreachable by the replication client zone compute nodes
* Note: every zone should have at least 1 network that is not a Transitional network.
iv. Once the wizard has been completed, open the zone’s info page and take a note of the private key.
Stage 4 – Add the replication client zone to the DR Dashboard
i. In the DR dashboard, go to the ‘Clouds’ page to see the list of clouds. Find the replication client cloud and select the tools button and ‘view’ option. From here, you can begin the ‘Register New Hypervisor Zone’ wizard.
ii. Choose the ‘Private Client’ type in step 1 and the desired compute zone in step 2.
iii. Enter the private key in step 3.
iv. In Step 4 (‘associate Transitional networks’), find and assign networks with moveable IP addresses. All other networks should be set to ‘Public’.
That’s it. If you’d like to learn more about OnApp DRaaS, you can read about it here – or contact your account manager. Thanks!