01 · Starting point
Situation
The existing infrastructure was to be virtualised. Platform choice, virtual networks, storage, server operations and recovery had to be assessed as one shared target design.
Constraints
- Changes within an already established IT environment
- Short, clearly scoped engagement
- Internal system and operating details remain confidential
02 · Responsibility
My scope of responsibility
I analysed requirements, planned the virtualisation, configured the environment and prepared monitoring, backup, disaster recovery and administrator training.
- I assessed systems and requirements for virtualisation.
03 · Technical work
Documented scope of work
Key decisions
Base the platform choice on operating and recovery requirements rather than consolidation alone. Virtualisation only creates lasting benefit when network, storage, monitoring and recovery suit the chosen platform.
- I planned and configured virtual networks, storage and servers with VMware and Hyper-V.
- I integrated backup and disaster recovery processes and trained the administrators.
04 · Technical context
Technology in use
VMware
VMware was part of the documented toolset in this Virtualisation & Operations engagement.
Hyper-V
Hyper-V was part of the documented toolset in this Virtualisation & Operations engagement.
Virtual Networking
Virtual Networking was part of the documented toolset in this Virtualisation & Operations engagement.
Storage
Storage was part of the documented toolset in this Virtualisation & Operations engagement.
Disaster Recovery
Disaster Recovery was part of the documented toolset in this Virtualisation & Operations engagement.
05 · Factual basis
Evidence and limits
The virtualisation gained a complete operating model rather than pure server consolidation.
- Role
- Virtualisation Consultant
- Period
- December 2008 — February 2009
Lesson from the engagement
A virtualisation platform is only production-ready when operations, monitoring and recovery are designed in from the start.
Confidentiality note: Internal architecture and operating data of this engagement are not published.