Data Center Relocation…Take One! - BICSI

1 data Center One!Joseph E. Ford, RCDDC raig A. Lowe, RCDD/OSP,LEED APRobert G. Hall, MCSDBala Consulting Engineers, Enterprise One or more of the following: data Center over about 100 devices Enterprise with 24x7 operations Dealing with life safety or finances Complex applications Growing well and improving IT management to match Setting goals Measuring progress Managing to expectations Smaller DC need less time but the same stepsProject PlanBenchmark View Start the Project Build New DC Facility Information Transport System Establish LAN / WAN / SAN Move Equipment / Server Waves Decommission Old DC Close the ProjectProject Management View

2 Charter Discover Requirements Design (and Budget) Validation Build / Execute Test Review and Close5% Project Charter Establish relationship with champion and PM Select initial core team Kickoff meeting Logistics and meeting schedule Start Project Plan and PresentationPrepare for data Center relocation As you do discovery, you will find systems that cannot be moved as they are This is a placeholder for projects that must be monitored to assure they are on track for the move Examples: Eliminate equipment that is too fragile to move (but probably running very important programs that nobody living knows how to support) Systems that depend on hard coded IP addresses that will not transfer to the new data Center Applications that must be virtualized so they can move electronicallySidebar Projects These are subprojects that may develop in addition to moving equipment These are usually separate because they are funded separately Examples.

3 Confirming that the Operation Center will function as expected Projects to design future changes to be compatible with the new data centerDiscovery for Facility Establish Inventory of hardware units Extend into power, cooling, and cabling estimate Extrapolate technology and growth changes Add summary to Presentation Client signs off Basis of DesignDiscovery for Facility Assist with floor plan for cabinets and racks Add floor plan to Presentation Monitor MEPS design process of DC, MDF, IDF, NOC Review fire suppression, security, and environmental design Review new building access for services and docks Add summary to Presentation Help with budget approval(s)Build and Commission Facility Monitor construction schedule Guest internet at new DC Confirm walls, floors, ceilings, electrical, cooling, etc.

4 Commissioning Add summary to PresentationInformation Transport System Discovery Add connection information to inventory Design Design prototype cabinet(s) for topology modeling Assist in topology decisions Design patch and switch elevations Add prototype and elevations to Presentation Manage bidding and leveling Help with budget and purchase ordersSingle Line Diagram Pull Schedule Plan ViewData Center Plan Tray Plan Cabinet ElevationsInformation Transport System Build Coordinate schedules for cabinets, racks, trays.

5 UTP and fiber Connect PDU to power strips Confirm demarcation points Test Test inventory and labeling of cables Test switch patching Design WAN LAN SAN & Storage WAN connects other business locations and the two data Centers LAN and SAN must be operational at both locations If refreshing equipment or changing technology, you may buy new for the new data Center Otherwise, you may rent equipment for the old data Center so you can move your equipment to the new data Center Long lead times for WAN LAN & SAN Communication services New storage equipment may be burned in with the network Design must allow a couple of devices to provide a period of solid service before real hardware wavesOK Where Are We?

6 HW inventory is verified with power and service connection fields noted Location is chosen and facility changes are underway Service connections are enumerated and ordered Network topology has been selected Information Transport System is at least being designed and is probably out to bid WAN, LAN and SAN design is settled and equipment ordered Cabinets and racks are ordered along with power strips, security and KVM equipmentOK Where Are We?What Can Go Wrong From Here? You can shut down critical systems in error You can forget part of a system A piece of equipment may not come up You can lose a truck You can move too much at one time You must know how to connect each device Networks must be ready for applications We must finish discovery and plan a safe move during facility outfitting.

7 What Can Go Wrong From Here?Discovery Beyond Hardware Get application blueprinting Match applications to inventory Identify 'Fragile Artifacts Identify unique parts risks Map telephony Check both the routes and detours Walk and ride and walkWhat s an Application Blue Print? An application centered view of how devices connect and service business transactions Includes: Devices (on inventory) IP addresses and network rules OS/DB versions and patch levels Virtual and physical attributes Recovery and DR conceptsCollecting Application Blueprints AppOwner: The Application Owner May be in one of several places in IT or be an internal customer depending on the enterprise Think about who approves scope changes in the application BPT.

8 The BluePrintTeam Members from Architecture, Application Development, DBA, SA, networking and business relationship Think about all groups that make a change to install or change an application Think about who will be the scribePrepare About 2 weeks Identify AppOwner Request an interview AppOwneragrees on resources Invite the team and work out invitation countersCapture Interview (1-4hr) White board Capture data Identify gaps Assign tasks Follow-up (1-2day) BPT documents & formats data BPT creates diagramsValidate BPT sends to interviewee Interviewee reviews diagrams and data sheets (2-3day) Interviewee &BPT reconcile changesSignOff BPT sends proposed diagram and data sheets to AppOwner AppOwnerreviews for accuracy (1 week)

9 AppOwnersigns offDistribute BPT provides copies to Operations, Application Development, Architecture, and Operations teamsIterationsApplications Move Together Cross reference devices and applications Every device should have known applications Every applications devices should be known Reduce unnecessary cross dependency Migrate storage, over time an enterprise tends to develop spider webs of applications sharing resources with each otherDesign the Actual relocation Decide on optimal waves size Plan physical and virtual servers in waves Publish the wave plans Arrange for smart hands and movers Assign locations in new DC Assign all patching Print initial copies of documents for wavesDesign the Waves Rehearsal Make sure players understand the process Include essential services: Domain controller, DNS, etc.

10 Base equipment for a VM farm Low hanging fruit Power and IP (UTP or Fiber) only Test case on each service Complex SAN connections, telephony, unique parts The rest of the story Fragile artifacts, redundant gear, retries But do NOT save the worst for lastPreparing for a Wave Confirm pre-test compliance Schedule a fix and test OS patches and software upgrades IP address and telephony changes Power down and power up Freeze machine Schedule backup, SA, DBA, testers Confirm core and edge patching Update, print and post (communicate!)