VMware vRealize Automation allows administrators to construct services and then provision those services to servers and desktop systems across the enterprise. Such provisioning can take place on bare-metal (physical) systems and VMs, as well as private, public and hybrid cloud environments. This is the infrastructure-as-a-service functionality in vRealize Automation. Administrators can install IaaS components, and those components are available through the vRealize Automation interface.
IaaS system components
There are six interrelated components of the IaaS system. A model manager is the basis for constructing services that integrate with external systems and data sources. It handles version control, security, persistence and distribution of service models. The manager service handles communication between elements. An IaaS database retains details about the machines being managed, along with its own elements and policies. The IaaS website offers the main interface for authoring service models. A Distributed Execution Manager (DEM) acts as an orchestrator that handles the business logic applied to service models. Various integration, management, virtualization proxy and windows management instrumentation agents are installed to facilitate the integration and communication with external systems.
IaaS component backups
Backing up IaaS components is an important part of the vRealize Automation backup process. This protects any services and workflows that are created for the business using vRealize Automation. But the number of components that constitute the IaaS system can make the backup process somewhat convoluted.
Generally, administrators can back up IaaS components using snapshots of proxy agents -- such as virtualization proxy agents -- any DEMs, the manager service and IaaS websites -- usually in that order. It's best practice to disable in-memory and quiesced snapshots when using snapshots to backup these components.
But IaaS component backups often need more than snapshots alone. Administrators will also need to record some details and copy key configuration files to ensure a complete backup of IaaS components. For example, agent backups can require administrators to record the agent and endpoint names, as well as copy the configuration files, such as the VRMAgent.exe.config and RepoUtil.exe.config files. As another example, DEM backups require administrators to record the corresponding agent name along with associated configuration files, such as the ManagerService.exe.config and policy.config files. Website backups must include a note of the Internet Information Services (web server) instance name, as well as a backup of the primary web node's ConfigTool folder and the policy.config and web.config files located in multiple folders.
This requires administrators to manually create additional notes and file backups and retain those backups along with any snapshots. It's easy to miss one or more steps here. Administrators can benefit from creating and following detailed backup and restoration procedures when conducting these processes.
Understand the evolution of the IaaS market
Realize the benefits of public IaaS
Decide between IaaS and platform as a service for microservices
Dig Deeper on Disaster recovery, failover and high availability for virtual servers
Related Q&A from Stephen J. Bigelow
Learn how load balancing in the cloud differs from a traditional network traffic distribution, and explore services available from AWS, Google and ... Continue Reading
Access management is critical to securing the cloud. Understand the differences between AWS IAM roles and users to properly restrict access to AWS ... Continue Reading
Containers have rapidly come into focus as a popular option for deploying applications, but they have limitations and are fundamentally different ... Continue Reading