|
Description:
|
|
Moving a data center from one place to another is one of the most complex challenges a network engineer is likely to face. In this Packet Pushers Weekly Show, Ethan Banks is joined by Chris Church and Richard Alexander to discuss just such a project from the viewpoint of having done one or more data center moves in our careers. We go back and forth on approaches to DC moves, reminiscence about the things we did right (and wrong), all while outlining an approach that you yourself can use as a template to move your own data center.
The outline we reference in the show is found below, and is largely the work of Chris. We hope the show is helpful to you as you do more designing and building in your day to day work.
Show Outline
- Intro
- 3 Approaches to the migration
- U-Haul Migration aka Lift & Shift
- Shut it down, move it, bring it back online
- Physical moves often take longer than estimated
- Labor intensive
- Proper insurance coverage
- Physical security of the equipment during move
- Data protection and integrity
- New build-out
- Build new and gradually migrate services
- Lower risk, higher cost
- Maintaining a presence in two data centers can be costly and complex
- Cloud/Hybrid
- Migration of a subset of services/applications to the cloud
- On-demand migration
- Some services remain on-prem or in colo
- Lower capital outlay
- Potential for added complexity
- Combination of a , b or c
- Planning
- Facilities
- HVAC and power
- Connectivity (availability, diversity, resiliency)
- Present and future space requirements
- Access controls and security
- Identify and inventory applications and services.
- Identify dependencies
- Identify SME s and stakeholders.
- Communication with customers and team members.
- Over-communicate.
- OOB communcation method for meatspace (don t rely on the gear your moving for UC.)
- Do you have mobile phone (cell) coverage?
- Coordination with vendors and availability of vendor support.
- Timing and projected duration of service outages.
- Connectivity at the new site. Hot cuts vs. new circuits.
- External DNS changes.
- TTL
- Access to make changes
- Equipment delivery to new facility.
- Physical access for required team members.
- Details (cables, cords, rack hardware, PDU s, KVM, crash cart, flashlights, etc)
- Validation plan.
- Preparation
- Assemble the team.
- Outline the plan and distribute to team members.
- Peer review
- Develop a checklist.
- Gather the required tools.
- Communicate!
- Execution
- Final checks.
- Ready, set, GO!
- Periodic notification to stakeholders.
- Validation.
- Lessons learned — post-mortem discussion
About Christopher Church:
Church has worked in the technology industry since the early 1990s, primarily with SME customers. He’s currently an Enterprise Architect for a managed services provider based in Little Rock, AR. He provides design, implementation, and management services for customers globally.
About Richard Alexander:
Alexander is an ex-financial services techie who survived a major core network overhaul and DC migration. Following that, he decided to move into technical pre-sales for the UK VAR arena, and was involved in countless migrations, ranging from moving a single service to the cloud all the way to global DC migrations for international trading platforms. Currently Chief Technologist in Networking, Security and Mobility for Logicalis UK, Alexander is responsible for the Business Unit technology blueprints and technical delivery capability.
The post Show 246 Design & Build #4 Data Center Migration appeared first on Packet Pushers.
|