In-Action
Backup as a Service
Last updated
Was this helpful?
Backup as a Service
Last updated
Was this helpful?
Backup service for hosted workloads in Moro Cloud
Login to your Moro Cloud Organization with Tenant Admin credentials. More → Data Management v2
Your Backup policy defines the retention for the Backups. Backups are taken every day at 12:00 AM. Below are the different Backup Policies available to choose from, during your Moro Cloud On-Boarding:
Bronze: Daily Backup with 7 days + Weekly Backup with 4 weeks + Monthly Backup with 1 month retention period.
Silver: Daily Backup with 7 days + Weekly Backup with 4 weeks + Monthly Backup with 3 month retention period.
Gold: Daily Backup with 14 days + Weekly Backup with 8 weeks + Monthly Backup with 6 month + Yearly with 1 year retention period.
Platinum: Daily Backup with 30 days + Weekly Backup with 8 weeks + Monthly Backup with 12 month + Yearly with 5 year retention period.
You can self-manage backups for VMs in Moro Cloud Portal using BaaS plugin. This enables you to:
On-Demand Sanpshot
Assign Protection
Recover VAPP
Export In A VAPP
VM Exclusion
Events
Show Deleted VAPPS
Reports
Let’s walk through a demo environment that we will use throughout this guide to demonstrate how BaaS works. Below is an example of a demo tenant named Tenant1.
The customer has a single Virtual Data Center, within which they have deployed 2 vApps containing a total of 3 VMs.
This is a new tenant who has subscribed to Backup-as-a-Service (BaaS) in Moro Cloud and has chosen the Silver Policy for VM backup protection. During the onboarding process, the Moro Cloud Admin will create and assign the selected Backup Policy to the customer's Moro Cloud tenant.
Note: At this stage, the Backup Policy has been mapped to your Moro Cloud tenant; however, the VMs will not be protected until the Tenant Admin assigns the Backup Policy to each individual vApp. This is a one-time task for each new vApp created by the customer.
To assign Backup policy to vApps, select “Data Management v2” from home page.
“Protection” tab→ “Select vApps” → It will list all the vApps in the selected VDC. Select the vApp and Click on Assign Protection to which the Backup Policy should be assigned. (Tenant1-DB-VAPP in this demo)
In “SLA Assignment” wizard → select the “SLA/Backup Policy” → Next. In this demo “Silver” policy is available to select, which was assigned to Tenant1 by Moro Cloud Admin.
Review the SLA details and click Done.
Once SLA is assigned, you can see the SLA under the “SLA Name” section. First backup is done as soon the SLA is assigned and post that backups are done at midnight every 24 hours.
Apart from schedule backup, you can take an on-demand snapshot(Backup) when needed.
After Backup has been configured, we can perform below tasks to perform recovery when needed.
Recover vApp
An entire vApp, or one or more virtual machines in a vApp, can be replaced through recovery.
Recover Files
To recover individual file from the Backups.
Export vApp
Exporting some or all VMs from one vApp to another vApp or VDC.
VM Exclusion
Exclude VM from protection from the Protected vAPP.
Events
View the status and progress of BaaS events and tasks.
Show Deleted VAPPS
View vApps that have been deleted but not yet permanently removed from the system.
Restoring vApps can be performed to recovery partial or full VMs within the vApp. This can only be performed for individual vApps. First, select the vApp for Recovery and select Recover vApp.
Screenshot 13 Baas Workflow 2
First, select the vApp for Recovery and select Recover vApp
We can then select which VMs we want to perform recovery against; select the VMs, and then select Next to see a list of valid snapshots:
Select the specific snapshot, and select Next
Finally, as part of the last step, we need to confirm the network and startup settings for the VMs, the following options are available:
Do not connect - This leaves the Network Adapters in place, but does not connect them
Remove - This will remove all NICs from the selected VMs when they are restored so they cannot conflict with existing values
Connect - This will allow to choose available Networks on a per NIC basis and re-assign the networks during the restore. This needs to be Confirmed before proceeding.
Once we press Done the restore will proceed. We can see the activity on this by checking the Events button for the specific vApp.
The plugin also supports file restores on a per-VM basis. We can select the vApp associated with the virtual machine and choose "Recover Files," which will open the File Recovery wizard.
First, we must select the VM that had the file we are trying to restore:
Select the specific snapshot, and select Next
Click "Next" to proceed to the search view. Enter a filename in the "Name to search for:" field and click "Search." This will find all files matching the search term and display a list, from which you can use the dropdown to select:
After selecting the file, the chosen files and directories will be displayed, and you can add additional files for recovery by clicking the "ADD MORE" option.
After selecting Next, we are presented with the restore options, these are as follows:
Overwrite Original
Restore to Separate Folder
Regardless of which option selected, we will then be asked to the provide the following restore method:
RBS Backup Service - Rubrik Backup Service is a connector running on the VM that allows Rubrik to interact at a service level, if selected, the file recovery is only possible the Service is running
Use VM Guest Credentials - Using VM Guest Credentials will use the VM login details via VMware Tools to restore the file (always select this option)
Finally, if we restore to a separate folder, we will also need to provide the path for a successful restore:
Within Export, the functionality exists to perform the following actions:
Export/Restore all VMs from one vApp to a new vApp
Export/Restore some VMs from one vApp to a new vApp
Export/Restore some VMs from one vApp to an existing vApp
Select the vApp for which you want to start the EXPORT → Click "Export vApp." This will open a wizard that will prompt you to confirm whether you want to export “All VMs” or a “Partial” selection.
Select either "All VMs" or "Partial" and select the VMs to export:
Select a snapshot with the relevant date
Select Next and we will be presented with a list of VDCs available for export:
Name the new vApp and suffix the VMs (Blank will not suffix anything other than a generated 4 letter string):
Finally, you will be prompted to configure the VM's Power State, Network Settings, and Storage Policy (keep the storage policy set to "VDC Default").
Once we press Done the Export will proceed. We can see the activity on this by checking the Events button for the specific vApp.
You also have the option to Export any vApp that has been deleted by enabling the "Show Deleted vApps" option.
Note: Deleted vApps will be kept in "Relic" according to the SLA retention policy.
The dashboard will provide the following information:
SLA Compliance Metrics
Capacity Metrics
Protection Metrics
Recovery Metrics
Activity Log
Reports
Backup Tasks
SLA Compliance
Capacity Over Time
Recovery Tasks
Customer Moro cloud Organization/Portal link:
In case of any urgent requirements that may arise, you can reach out to Moro Support Center on 2266, Or .