Embed Size (px)
DESCRIPTION
VMware View Failover Automation - failover for persistent and non-persistent desktops using VMware vCenter Orchestrator
Citation preview
THIS PRESENTATION
IS
BYTELIFE PREPARED
www.bytelife.com
VMware View
Failover Automation
December 2013
www.bytelife.com
Agenda
• Challenge and Solutions
• View Automation Features
• Technical overview
• Demo
• Wrap-up
www.bytelife.com
Challenge
• Virtual desktops not suitable for highly available
workplaces
• Additional complicated service to recover during
disaster
www.bytelife.com
Solution1 – Virtual Storage
• Storage virutalization layer
handles the access to the storage
• If on site storage is down, other
site will be used, with no
interuption for applications
• If the hosts are also down,
standard VMware HA will start the
service in other site
www.bytelife.com
Solution2 – VMware SRM
• Not supported for VMware View
• Failover for VM-s, not linked
clones
• User assignment information is
lost
www.bytelife.com
Solution3 – VMware Mirage
• Mirage for View not yet available
• Only handles the persistent
desktops
www.bytelife.com
Solution4 – Manual Work
• Quite complex
• Another headache during disaster
www.bytelife.com
Help, Google, Help!
www.bytelife.com
Value Proposition
Extend the VDI use case to
mission critical workplaces
www.bytelife.com
Key Features
• General
• Persistent and non-persistent pool desktop failover
• Option for using more than 2 sites
• Active-active approach
• Based on VMware vCenter Orchestrator workflows
• No VMware vCenter Site Recovery Manager needed
• No changes in VMware View administration
• Simple protection configuration wizard
• No overhead – it’s rather automating the manual tasks
www.bytelife.com
Key Functions
• Failover
• Automated failover within minutes after launch
• Minimum effort during failover
• Migration
• Load balancing and failback possibility
• Minimized downtime window for recompose large environments
www.bytelife.com
How it Works - Failover
ReplicaConnection
Server
Linked ClonePool 1
Recovery
Manual Pool
Linked ClonePool 2
Linked ClonePool 2
Recovery
vCenter& VCO
ConnectionServer
Replicated
StorageNot Replicated
Replicated
StorageNot Replicated
Replication
Persona
vCenter& VCO
Linked ClonePool 1
www.bytelife.com
How it Works - Failover
ReplicaConnection
Server
Linked ClonePool 1
Recovery
Manual Pool
Linked ClonePool 2
Linked ClonePool 2
Recovery
vCenter& VCO
ConnectionServer
Replicated
StorageNot Replicated
Replicated
StorageNot Replicated
Persona
vCenter& VCO
Linked ClonePool 1
www.bytelife.com
How it Works - Migration
ReplicaConnection
Server
Linked ClonePool 1
Recovery
Manual Pool
Linked ClonePool 2
Linked ClonePool 2
Recovery
vCenter& VCO
ConnectionServer
Replicated
StorageNot Replicated
Replicated
StorageNot Replicated
Persona
vCenter& VCO
Linked ClonePool 1
Replication
www.bytelife.com
DEMO
www.bytelife.com
Wrap Up
• Persistent and non-persistent desktop failover
• Single tool and simplified failover
• No SRM needed
• Multiple sites supported
• Non-propieritary – based on vCO workflows
www.bytelife.com
Conclusion
• DR for VMware View is possible and it can be
automated
• Orchestrator platform can be used for further
automation initiatives
www.bytelife.com
http://www.bytelife.com/view-failover-automation/
www.bytelife.com
Questions?
