Anytime I’m in a discussion that deals with server or desktop virtualization, the topic usually heads to high availability. I usually get asked about live migration features like XenMotion. Honestly, there are many scenarios where it doesn’t make sense, but that is a discussion for later. What does matter is that your implementation continues to operate even if something has failed.
Let me give you an example of what I mean. When I design a XenDesktop environment, I typically recommend, at a minimum, two Provisioning Services server even if the environment is capable of running with a single server. We typically refer to this as N+1. The reason is that if one server fails, the other can take over the load. I’m hoping this isn’t a new idea for you as this is how many people deal with fault tolerance. However, how do we take this to the next level? How do we make our XenDesktop environment as bullet-proof as possible? Where do we need to focus our attention on?
Another example… I’ve seen many people do N+1 on their Web Interface servers. Again, this is a good practice. But now the question is how are those servers being load balanced? Are you using intelligent monitoring that checks not only availability but also that the service is functioning appropriately?
These are just two areas that will be covered in the Synergy Session “SYN208 Guaranteeing availability and scale for XenApp and XenDesktop deployments“.
- When is this session? October 6, 17:30
- Where is the session? Synergy Berlin
- Why attend? Because it will be good
Looking forward to seeing you there
Daniel – Lead Architect