100%(5)5 out of 5 people found this document helpful
This preview shows page 11 - 14 out of 25 pages.
§Complete inventories of existing systems and interdependencies.§Identify future system requirements (pipeline for growth).§Create a step-by-step decommissioning and equipment rebuilding plan, including health and safety procedures.§Determine interim equipment requirements to keep systems operational during the migration.§Devise a contingency plan to include illness, accidents and damage to equipment.DC3 DCR3§Define connectivity requirements and allocate adequate time for new connections.§ LAN design/WAN detailed diagram.§Consider company’s operational requirements and plan the move to cause minimal disruption.Objective Ref. No.RequirementRef. No.Requirement Description§ Undertake a “dry run” to test if the plan is achievable.§ Review deployment team’s tasks and timelines.
§ Plan new space configuration and reference racks grid.§Install andtestnew data cabling (certification to be issued).§Ensure all identified processes and procedures are followed.§ Checking on connectivity between hardware equipment.§ Test network and application components.§Arrange for M&E engineers, hardware and software experts to be on call.§Advise users of changes and provide contact points for issues.DC4 DCR4 § Post implementation review.§ Rebalance air-flow systems.§ Check electricity quality.§Closely observe all building and equipment monitoring systems.§ Test security systems§ Detailed diagrams rack/network/ patching/LLconnectivity.§Infrastructure deployment complete signoff from the customer.DC5 DCR5 Data center migration is essentially a managed disaster-recoveryevent for which the IT environment will be re-established at adifferent location, disaster recovery is the most pertinent area tothe success of the project. A thorough disaster recoveryplan provides key information about the interrelationshipsbetween the infrastructure and the business, the criticality ofapplications and data, and the mechanisms to mitigate risk.
3. CHANGE MANAGEMENT (CHAPTER 4)Change management is the process that approves and schedules the change in order to ensure the correct level of notification and minimal user impact. These are the key steps for change management:1. Assign a change controller who can run change management review meetings, receive and review change requests, manage change process improvements, and act as liaison for user groups.2. Hold periodic change review meetings to be attended by system administration, application development, network operations, and facilities groups, as well as general users.3. Document change input requirements, that includes change owner, business impact, risk level, reason for change, success factors, back out plan, and testing requirements.