This a attempt to share my approach for larger complex datacenter migrations

1. Case Study for Data migration
An Approach
By
Ganesh Iyer
A simple thought process to build solid foundation forcomplex & huge data migration

2. Datacenter Migration Patterns
Decisions
• Moving to New Headquarter in NA .
•Datacenter Migrations.
•CTO Vision on new datacenter
•Budget
•Timeliness
•Avoid Vendor Locking
•Merger of organization
Categorize
•The Knows
•The Unknowns
Analyze
•Current Landscape.
•Future Landscape.
•Business Requirements.
•Data patterns.
•Available resources
Act
•Build a sound Foundation
•Build Capacity
•Develop Migration approaches
•Nemawashi approaches.
•Build Factory assembly approach.

3. Manufacturing and Sales organization North America Merger challenges!!
Internal reorganization.
 Who is responsible for decision making.
 Who will bring everyone together and
run the show.
 who can provide and authenticate
information
 Will there a transformation or lift and
shift etc..?
 Cultural and working style differences.
 Vendor dependences and their
influence.
Organization wise discovery
Programs .
 External Consultant hired for discovery
of IT infrastructure.
 Vendor challenges about sharing
information's.
 Future Hardware assessments and
recommendations.
 To be state for applications
 Associates relocations to new State.
Merger
Reorganization
Enterprise decisions.
Approvals
Methodology
Migration
Employee transfers
Travels
Existing Assets and Technology
Discovery
Vendor unlocking Application to be State
Categorize Act
Analyz
e
Decisions

4. Knows
Business application supported today.
Technologies supported.
Future technology and Hardware availability
Migration from Engineered system to
converged systems or commodity hardware.
Core Services required.
Future Datacenter for each environment for
Sales and manufacturing.
Unknowns
What is budget for Migration ?Technology
aspect.
How to convince which approach to use for
migration?AndWhom to approach?
Do we consolidate core services?
What objectives would help Management
onboard business –Feel good factors?
IT Resource availability such Network ,storage
etc..
Capacity requirements – Forecast &
approvals.
Categorize
ActAnalyzeDecisions
Categorize

5. Connect the DOTS (Diverse OrganizationalTechnology Services!)
Foundation
Captured , built &Validate data from various source.
Architected FutureTechnology- Hardware and
software
Divide & Conquer.
Build Patterns to
each streams
X-Factor Architect
Solution-
Tribal knowledge &
Business criticality
Technology
Breakdowns
Benchmark Business
SLA’s
Architectural
foundation
ActAnalyzeDecisions Categorize

6. • Unknowns to Knows
• Approached existing Stakeholders for their buy in for approving conceptual and logical models.
• This helped in approval after reorganization (or even after change in Stakeholders)
• Build the multipleArchitectural Patterns with pros and cons. (With available technologies)
• This helped in building the budget instead of first anticipating the budget.
• BuildingCore service first to support the existing business .
• This assured quick on boarding of application to start migration.
• Objectives where classified as
• Proof ofTechnology (POT) , Proof Of concept & Proof of System.
• Plan with minimal resource availability.
• This helped to fail quick.
• Allowed us to know what area we had success and failure.
• Build a multiple smaller framework with information gathered.
• More accurate and easy to manage
• Helps capacity planning.
• Helps provisioning future requirements.
Journey
Connect the DOTS (Diverse OrganizationalTechnology Services!)
ActAnalyzeDecisions Categorize

7. Migration
Patterns
Make
Knows as
Foundation
Unknowns
to Knows
ActAnalyzeDecisions Categorize
Results !!