In my last post, I covered the steps to Automat vRA distributed deployment using vRSLCM.In this post I will describe about Guidelines for Planning vRealize Automation Backups.
vRealize Automation Preparations for Backup
A system administrator backs up the full vRealize Automation installation on a regular basis. Plan the backup around efficiencies and periods of low activity.
You can use several strategies, singly or in combination, to back up vRealize Automation system components. For virtual machines (VMs), you can use the Snapshot function to create snapshot images of critical components or use native tools like Veritas NetBackup and vSphere Data Protection. If a system failure occurs, you can use these images to restore components to their state when the images were created. Alternatively, and for non-virtual machine components, you can create copies of critical configuration files for system components, which can be used to restore these components to a customer configured state following reinstallation
vRealize Automation complete backup includes the following components
- vRealize Automation appliance
- PostgreSQL database. Applicable only for legacy installations that do not use an embedded appliance database
Infrastructure MSSQL database(Optional) Software load balancers
Guidelines for Planning Backups
Use the following guidelines to plan backups:
When you back up a complete system, back up all instances of the vRealize Automation appliance and databases as near simultaneously as possible, preferably within seconds.
Minimize the number of active transactions before you begin a backup. Schedule your regular backup to when your system is least active.
Back up all databases at the same time.
When you back up the vRealize Automation appliance and the IaaS components, disable in-memory snapshots and quiesced snapshots.
Create a backup of instances of the vRealize Automation appliance and the IaaS components when you update certificates.
vRealize Automation Backup Order
You must back up the VMs for vRealize Automation components in a specific order.
When you use backup tools to schedule backups for your vRealize Automation deployment, you must back up the components in the following order:
If you have multiple components on a VM, select the order considering the latter component on the VM from the list.
If vRealize Orchestrator is a standalone component, then it should be backed up in no particular order before vRealize Automation components.I hope you have enjoyed reading my blog..Feel free to bookmark or post to your timeline for reference later!