Saturday, May 3, 2014

VMWare Horizon View Design Best Practices

This blog post talks about designing a basic VMware View deployment that will cover up to 500 desktops. 

For enterprise setup, I plan to do a more elaborate extension to this post where I would talk about areas such Storage, Networking, Load Balancing, POD architecture and best practices around them.

The basic components and what strategy to take around them to avoid single point of failure.

2 vSphere Clusters 
Its not wise to run one vSphere cluster for both your server infrastructure and your desktop infrastructure.  Don't be cheap, separate these clusters.

2 View Connection Servers
The View Connection Server is the brokering server, they establish the connection to the View Agent.  While redundancy is built into the product, all you have to do is install a second "replica server".  Also, keep in mind if you want to do external PCoIP connections you will need 4 View Connection Servers . Two of these servers will be used for internal redundancy, two will be used for external.

2 View Transfer and Security Servers
On similar lines as Connections server based on the functionality.  

2 vCenter Servers
You'll need to use vCenter Heartbeat, as its the only way I know how to make vCenter Servers redundant,. Its a little bit expensive but VMWare doesn't say that you need to make the vCenter server redundant, however vCenter service being down is catatrophic event. For the most part you don't need vCenter, except when you need to boot a linked clone VM

2 SQL Servers
Use SQL 2008 with Microsoft Failover Clustering.  Make this redundant  Well, vCenter DB is on this, Events DB is on this, View Composer DB is on this.  Basically every component of a View setup has a DB, so its advisable to have these DBs on a redundant back end. 

No comments:

Post a Comment