Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Transatlantic datacenter migration with v sphere


Published on

Slide Deck presented at the London Vmware Usergroup on 10/2/2001 by Chris Dearden from

Published in: Technology, Business
  • Be the first to comment

Transatlantic datacenter migration with v sphere

  1. 1. Transatlantic Datacenter migration with vSphere<br />Chris Dearden <br />J.F.V.I (<br />London VMware User Group<br />
  2. 2. Sorry about the Shirt…<br />
  3. 3. Large Professional Services Company<br />Existing Datacenters in the UK and US<br />~ 2000 Servers over 4 Datacenters( at the time ) <br />65% Virtual<br />Multiple environments & AD Forests for Different Lifecycles (DEV/Int , QA )<br />Systems for Business Continuity also in place (BCP)<br />SituationOverview<br />
  4. 4. Lease on non Production DC in the US due for renewal<br />Workload 100% Virtualised systems<br />Quad Socket Rackmountedhosts<br />HP EVA 8000/6000 Series SAN<br />Legacy Environment<br />
  5. 5. Migrate to UK Based Secondary DC in Docklands<br />Space at a premium , plenty of power density<br />Initial Design to use multiple C-Class HP Blade Chassis<br />Cost/Performance sweet spot calculations<br /> BL460G6 +96Gb RAM + Flex10 + HBA <br />Ideal Design<br />
  6. 6. Design presented to Senior management<br />No budget for a redesign aside from seed hardware, it would require a “lift & shift methodology”<br />Servers & Storage to be physically moved.<br />Provision additional storage to handle additional DEV/QA workload<br />Life isn’t Ideal!<br />
  7. 7. All Aboard<br />Servers to be shipped from outside Atlanta to London<br />Build out core infrastructure<br />Replicate servers from US using Doubletake Backup<br />Sync up backup repositories<br />Restore vm’s & re-ip<br />7<br />
  8. 8. “Seed” hardware deployed ahead of schedule – deployed with ESXi 4.0<br />Build out of Key systems while initial hardware was on the boat<br />2 Complete AD forests with associated “DMZ”(20+ Global Catalogs ) <br />Doubletake Backup recovery assistants & repositories<br />Some delays in system due damage in transit<br />Sewing the Seeds<br />
  9. 9. Legacy Datacenter ran NBU based system ( out of maintenance )<br />UK Datacenter only had BCP systems on it so no backup infrastructure.<br />Had to get backups running in a very short timeframe.<br />Deployed Veeam backup v4 on “spare” hardware<br />Great for initial backups but had to upgrade as environment grew<br />Erm….Backups ?<br />
  10. 10. Rate of Data migration faster than the rate of server shipping.<br />Led to some heavy squeeze on RAM (175% overcommit) – no serious problems from a CPU perspective.<br />Lets not forget this is a pre production environment.<br />Stuck in Transit…time to Overcommit.<br />
  11. 11. Arrival of more hosts over time boosted to 10 Hosts per cluster. Last seen running ~ 800 VM’s <br />Upgrade of Veeam server to quad socket allowed heavy job concurrency.<br />Deployment of IBM XIV SAN for primary Storage eased heavy contention on legacy HP EVA.<br />Fleshing the Solution out<br />
  12. 12. Secondary DC was not originally sized to take so many hosts<br />Rolling RAM upgrades until assets depreciate enough to replace with more space efficient blades.<br />Upgrades to 4.1 along with SAN firmware enhancement to allow VAAI and larger cluster size.<br />An Admins Job is never done.<br />
  13. 13. Find out the budget BEFORE you design a solution<br />Where possible migrate the workload , not the hardware.<br />Make sure you start with all the pieces of the puzzle.<br />Fresh start facilitated the transition to ESXi<br />What I learnt on my Datacenter Migration.<br />
  14. 14. But First……<br />SWAG for questions.<br />I make it Beer O’Clock<br />