In-Action
Last updated
Was this helpful?
Last updated
Was this helpful?
Login to your Moro Cloud Organization with Tenant Admin credentials. More → vCloud Availability (DC1-AZ1-DXB)
Disaster Recovery as a Service is designed to provide recovery points that are as little as 15 Minutes behind the running VM. Your custom policy has two components RPO and recover points. Which are configured by you Moro cloud Admin. For example:
Target RPO of 30 minutes
Recovery points every 30 minutes for last 24 hours
For details related to your Custom policy please contact you Moro Cloud Team.
Rate of change of the data on a VM can affect the RPO. VMs with a large rate of change in the data will potentially achieve a slightly longer RPO than VMs that have a lower rate of change
You can self-manage your protected environment via Moro Cloud Portal. This enables you to:
Configure new protection
New migration
Test Failover
Migrate
View RPO of the configured replication
Monitor performance of the replication
Let us go through a Demo environment which we will use throughout this guide to demonstrate how DRaaS works.Customer has multisite configuration and 2 Availability Zones (Sites) as shown below.
Here Site 1 is the protected site where my Virtual Machine is running. Site 2(Recovery site) has no Virtual Machines running.
Both the sites have one Network configured with same subnet and connects to respective Edge gateway.
Site 1 is the active site with a vApp01 which contains a single VM01 machine.
Migrate a vApp or a virtual machine to a remote organization, and run the workload in the destination site, by configuring a migration. After a successful replication in the destination site, you can power on the source virtual machine in the destination site.
To create a migration, select “vCloud Availibility (DC1-AZ1-DXB)” from home page.
Outgoing replication → To Cloud → New Migration
In “New Outgoing Replication” wizard Select the vApps and VMs you want to migrate → Next
Select the Target Site → Next
Select Target VDC on Site 2 → Next
Under Protection Settings → Select Storage Policy for migrated Virtual Machine
On “Ready To Complete” page review the settings → Finish
You can review the details of configured migration task. Note: Migration always have 24 Hours RPO by default and cannot be changed
Protect a vApp or a virtual machine from one organization to another, and keep the workload running in the source site, by configuring a protection. If the source site is unavailable, after a successful replication you can fail over and power on the source virtual machine in the destination site.
To create a migration, select “vCloud Availibility (DC1-AZ1-DXB)” from home page.
Outgoing replication → To Cloud → New Protection
Select Target Site 2 → Next
Under Protection Settings → Select Target Recovery Point Objective (RPO), Storage Policy and “Retention policy for point in time instances”. You can enable the Quiesce but this is only supported for windows Operating Systems.
Review settings → Finish
You can review the details of configured migration task
After replication has been configured either based on a Migration Task or Protection Task, we can perform below tasks to perform disaster recovery when needed or do a test.
NOTE: To perform any DRaaS workflows, please check the DR run book for contact Moro Team
Test failover
Validate the data from the source site replicates correctly in the destination site by performing a test failover. You perform a test failover for a replication and then delete the test data.
Failover
If the protected source site is unavailable, in the destination site perform a workload disaster recovery operation.
Reverse Task
After a failover from the source site to the destination site, the migrated workload runs on the destination site. A subsequent reverse task replicates the recovered workload data back to the source protected vApp or virtual machine.
You can check the health of the replication from DRaaS main page where it shows status of all incoming and outgoing replication status. In Below example there is one outgoing replication configured and status is green.
For more details about the replication status, navigate to the Outgoing replication → to Cloud and check the “Replication State” and “Overall Health”
If there are any failures/error, you can find more details under “Replication Tasks”
In case of any urgent requirements that may arise, you can reach out to Moro Support Center on 2266, Or Support@morohub.com.
Customer Moro cloud Organization/Portal link :
