One of the services provided by the Enterprise Hybrid Cloud Solution (EHC) is Backup-as-a-Service (BaaS), which enables cloud users to manage and consume data protection backup services through a single user portal. The EHC solution leverages service levels throughout the solution, using policies to control resources such as compute, storage, network, and data protection.
In the EHC solution, a Backup Service Level = an EMC Avamar Backup Policy, but there’s a bit more gets configured under the covers.
EHC Cloud Backup Administrators can create Backup Service Levels through the VMware vRealize Automation (vRA) portal without ever accessing the EMC Avamar Administrator UI. The Backup Service Levels should be configured to satisfy business requirements. Not all virtual machines and applications will require the same level of data protection, therefore it is normal to have multiple backup service levels.
EHC users who have entitlements to the Data Protection Backup service in vRA can select the ‘Create Backup Service Level’ catalog item to initiate the request.
The user will then be guided through a configuration wizard which will prompt for all of the necessary inputs required to create the appropriate Avamar Backup Policy. Once the user has entered a name for the Backup Service Level, which should be descriptive (e.g. 2xDailyBackup, MonthlyBackup, etc), they can then select the Backup Target which can be either Avamar itself, or a Data Domain.
The next couple of steps then create and define the schedule and retention period for the new backup service level.
The Backup Schedule provides 3 options:
- Daily – specify one or more time intervals (for example, 03:00 and 03:30)
- Weekly – specify the day on which the backup will take place (backup time follows the default backup window)
- Monthly – specify the week in which the backup will take place (backup time follows the default backup window)
Click the Retention tab and specify or create a retention policy appropriate for this backup service level.
You can specify or create one of several types of retention policies. You can:
- Retain the backups forever.
- Retain the backups for a certain number of days/weeks/months/years.
- Retain the backups until a certain date.
- Define a custom retention period.
To keep the backups for a certain number of days, weeks, months, or years, select the for option, type a number, and select days, weeks, months, or years from the menu.
To define a backup retention period of forever, select forever. To keep the backup until a certain date, select Until, which enables you to choose any future date.
The Long Term Retention Policy is the length of time that you want to retain a final backup of the virtual machine. This final backup is taken during the VM destroy/decommission process.
While the wizard provides the primary schedule settings, you can also apply a custom retention schedule based on each of the backup types by making selections from all of the possible parameters available.
Once the required inputs have been collected, and the Submit button is clicked, EHC will kick off the CreateServiceLevel vRealize Orchestrator workflow which will take the inputs, validate if the underlying environment is single or multi-site containing Avamar replication, and then go create the required objects such as :
- Avamar Backup Policy (see Avamar Admin UI image below)
- Define Dataset/Schedule/Retention/Proxy servers
- Enable Encryption Method (set to High)
- vCenter Folders
- vRA objects such as the Build Profile and Property Dictionary
- vCenter SRM mappings (if DR environment)
Once the operation has successfully completed, the new EHC Backup Service Level will be available at deployment time to any virtual machines to which Data Protection Backup is applied to their Blueprint, as shown below.
Once the VM is deployed, it is added to the appropriate vCenter folder and Avamar Policy, as shown below:
Later posts will explain how to add EHC BaaS to VM deployments in vRA, what happens under the covers when the scheduled backups kicks off, as well as the on-demand backup and restore operations which are outside of the defined backup schedule.
Hope this helps!