BACKGROUND IMAGE: iSTOCK/GETTY IMAGES
IT administrators can perform a complete VMware vRealize Automation backup and restoration or focus on certain software components that are critical to the business.
Back up vRealize Automation
Generally, a complete vRealize Automation backup usually includes the vRealize Automation appliance -- typically, a virtual appliance that deploys the vRealize Automation server -- the principal database, such as a Microsoft SQL database that typically contains detailed infrastructure data; identity and access management components, such as certificates or certificate chains; load balancers used to distribute work between multiple components in high availability environments; and various infrastructure-as-a-service components that are created by the platform, such as IaaS websites.
Backups can employ conventional VM snapshots, more traditional full, incremental or differential backups using comprehensive backup tools or even simple copies of critical files. The actual choice of backup approach will depend on the available backup tools, prevailing business goals and the degree of protection desired for the vRealize Automation deployment.
But resilience isn't limited to vRealize Automation backup practices. IT administrators can also employ failover techniques. For example, administrators can configure failover for the Manager Service host, allowing a secondary (passive) Manager Service server to accept promotion and serve as the primary Manager Service host when problems arise. Failover techniques typically rely on two or more server nodes operating through a load balancer.
Everything you need to know about backing up vRealize Automation
Use a variety of techniques and tools for backing up the vRealize Automation appliance, pay special attention to protecting infrastructure-as-a-service components and employ these general tips for vRealize Automation backup and restoration.
Restore vRealize Automation
When a failure occurs, vRealize Automation can be restored from snapshots and/or backups. A restoration usually starts with databases, such as the Microsoft SQL database. Next, the vRealize Automation appliance is restored, followed by load balancers and any virtual appliances managed by load balancers. vRealize IaaS components are restored next, such as IaaS websites, Manager Service hosts and any load balancers that those components utilize. This is typically followed by restoring Distributed Execution Manager orchestrators and workers, finishing with the reinstallation of any IaaS agents in the environment. The actual number of components that are restored or reinstalled will depend on the nature and extent of the failure -- it might not be necessary to restore every part of the vRealize Automation infrastructure.
Navigate updates to vRealize Automation 7
Deploy a specific vRealize Orchestrator design
Take advantage of vRealize Network Insight
Dig Deeper on Disaster recovery, failover and high availability for virtual servers
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.