I will also only touch on how to change VM reservations. I will cover them in the order that these tasks would usually be performed if you were to fail over vRA to DR: In my opinion, there are two important aspects that are missing from the aforementioned document, which I want to cover in this blog post: restoring VM UUIDs and changing vRA IP address. vRealize Suite 7.0 Disaster Recovery by Using Site Recovery Manager 6.1.Site Recovery Manager (or another replication product) is required to protect vRA in a DR scenario, which is described in more detail in the following document: Generally speaking, HA covers redundancy within the site and is not intended to protect from full site failure. There is a clear distinction, however, between high availability and disaster recovery. Additionally, in vRA 7.3 VMware added support for automatic failover of vRA appliance’s embedded PostgreSQL database, which was a manual process prior to that. For medium and large deployment scenarios VMware recommends using a load balancer (Citrix, F5, NSX) to distribute traffic between vRA appliance and infrastructure components, as well as database clustering (such as MS SQL availability groups) for database high availability. VMware has invested a lot of time and effort in vRealize Automation high availability.
0 Comments
Leave a Reply. |