Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning VMware vRealize Automation

You're reading from   Learning VMware vRealize Automation Learn the fundamentals of vRealize Automation to accelerate the delivery of your IT services

Arrow left icon
Product type Paperback
Published in Feb 2016
Publisher Packt
ISBN-13 9781785885839
Length 230 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Sriram Rajendran Sriram Rajendran
Author Profile Icon Sriram Rajendran
Sriram Rajendran
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. vRealize Automation and the Deconstruction of Components FREE CHAPTER 2. Distributed Installation Using Custom Certificates 3. Functional Validation – Phase 1 and Installing Secondary Nodes 4. Configuring a Guest OS for vRealize Automation vSphere Blueprints 5. Functional Validation – Phase 2 and Zero to VM Provisioning 6. Testing Failover Scenarios for vRealize Automation Components 7. vRealize Orchestrator in High Availability via the NSX Load Balancer 8. The Power of Advanced Service Designer (ASD) Index

Failover of DEM Worker and proxy agent


Both DEM Worker and the proxy agents follow the active-active HA configuration and failover process is automatic.

DEM Worker

If the worker service stops or loses its connection to the repository (Model Manager Web), the DEM Orchestrator clears all the associated workflow instances to the nonfunctional DEM Worker, thus allowing the other DEM Workers to pick up the workflow. This explains why the failover process is seamless and fluid without the requirement of any extra steps for it to function during and after the failover.

Proxy agents

If you have more than one vCenter endpoints, then you have to install an additional vSphere Agent. It's a 1:1 mapping between the vCenter endpoint and vSphere Agent. You can have multiple agents talking to the same vCenter endpoint in case of high availability but each agent should be on a different server, and they all should have the same name; otherwise, you will run into many issues. For example, if you have three agents...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image