119.a_VM_COLD_ Migration_SMOP.

doc

EMERGENCY CHANGE REQUEST? Emergency Authorized by: _____________________

OVERVIEW & TRACKING INFORMATION

Customer Name: Tecumseh

IDC/Site ID(s): Annapolis Target Impl Window Duration: 9 hr
SMOP Author(s): William Duffy Estimated Change Duration: 90 min
CSM/LCM Name: Estimated Test Duration: 30 min
HCCB-CR Tracking # Estimated Back-Out Duration: 90 min
ALL FIELDS REQUIRED IN THIS SECTION

SMOP Assessment Matrix (instructions follow):

Change/Procedure Risk Minimum Skill Onsite Client

Target Assessment Set Required Rqrd Notify*

Single Client Component Med Open Migrator N

Single Client Component Med Cisco MDS N

Description of Change Request:

Migration of Tecumseh VMs for mdesxfm13 3Par Disks to new VMAX Array. PreMigration stage;
iChange #

Impact of Change Request:

All disks migrated to VMAX Storage Array

Parties Involved, Resources/Skills Required for Change Request Execution:

GCSC
Tier II Platform (EMC)

Back-Out Preparation Steps:

N/A – fallback steps covers requirement

Customer URLs to be Tested Prior to Start of AND After Completion of Change:

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 1 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

Post-migration Checklist:
Verify that the following post-migration steps have been completed after Detailed Change Execution
completes.

Validate all original san volumes in use have a full backup prior to migration (step 1)
Validate all required logins and access to complete migration (step 2)

Detailed Change Execution Steps:

Alarms suppression IS required IS NOT required

[A choice MUST be made, then proceed to step 1. Remove Instructions When Done.]

------------------------------------

Section 1 – Pre-Migration

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 2 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

------------------------------------

1. Validate all volumes mounted on the system have a full backup.

Confirmation required from AT&T.

2. Validate all required system access is available.

a. Login and validate connections as required to all hosts, storage, san and management
systems.

------------------------------------

Section 2 – Migration
------------------------------------

Migration of the volumes will be accomplished in parallel using robocopy with the applications in an offline
state. The host will need to see both new and old volumes at the same time.

1. Confirm migration is complete and disk configs have been backed up.
Confirmation required from AT&T

The Source 3Par Devices

Source
Source Devide ID Source Array Size (GB)
3par-vmfs-Tecumseh_Exchange_L14 3Pardata 209
The Source 3Par Devices
Source
Source Devide ID Source Array Size (GB)
vmds3aex03_18 3Pardata 18
vmds3aex03_15 3Pardata 120
vmds3aex03_19 3Pardata 18
vmds3aex03_16 3Pardata 120
vmds3aex03_20 3Pardata 18
vmds3aex03_17 3Pardata 120
vmds3aex03_27 3Pardata 100
The Source 3Par Devices
Source
Source Devide ID Source Array Size (GB)
vmds3aex04_21 3Pardata 120
vmds3aex04_25 3Pardata 18
vmds3aex04_22 3Pardata 120
vmds3aex04_26 3Pardata 18
vmds3aex04_23 3Pardata 120
vmds3aex04_24 3Pardata 18

.
2. AT&T shuts down application and set to not start on reboot.

3. Perform remediation actions recommended in Section 4 of this document.

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 3 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

4. Complete the migration.

##################### ROBOCOPY COLD MIGRATION ##################################

NOTE: robocopy must be available on the host and ready for use to perform this migration method.

a. Validate applications are shut down, services must be set to not start on system restart.

b. Backup configuration of existing disks

use diskpart to create a backup of all existing disks on the host

#diskpart
#list disk
#select disk “#”
#detail disk

Repeat select disk / detail disk for every disk listed in first part of command

c. Configure disk letter other than original disk letter for all RDM based volumes

Use disk mgmt tool to change drive letter on all existing volumes to selection outside currently used
drive letters.

d. Configure new disks

use disk mgmt tool to write signature on new disks

create NTFS partitions on new disks
assign original drive letters to new partitions

NOTE: if drive letters used originally for the 3par volumes are not available, the system will need to be
restarted to clear the lock on the drive letters.

e. Robocopy the data on the original drives to the new drives

Open a cmd shell

#robocopy “old drive letter”:\ “new drive letter”:\ /s /e /R:3 /SEC /Z /TIMFIX

old drive letter == newly assigned drive letter other than original drive letter
new drive letter == newly assigned original drive letter on VMAX based disks

Repeat command set for all volumes being copied. All should run in parallel.

f. Watch copy sessions until they complete.

g. Validate all file systems are fully available on new original drive letters and new storage.

END cold copy of RDMs.

##################### ROBOCOPY COLD MIGRATION ##################################

5. Complete VMWARE guest migration

A. Log into the vCenter:

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 4 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

Pinnacle – Annapolis

Perform a shutdown of VM only

Select Datastore | Select Virtual Machines tab | Right-click VM and select “Shut Down Guest”

3par-vmfs-Tecumseh_Exchange

Cluster VM Description VMHost VMDK check

-----------------|-----------------|--------------------------------------------|----------------|--------------
mdesxfm13 vmds3aaa01 Win2003-32bit 2vmdk + 0 RDMs
mdesxfm13 vmds3aeb01 Win2003-32bit 2vmdk + 0 RDMs
mdesxfm13 vmds3aeo02 Win2003-32bit 2vmdk + 0 RDMs
mdesxfm13 vmds3aex03 Win2003-32bit 2vmdk + 7 RDMs
mdesxfm13 vmds3aex04 Win2003-32bit 2vmdk + 6 RDMs

5. For Virtual Machines with RDMs, Remove the source RDMs **AND** target RDMs from VM

Select Datastore view |Select Virtual Machines tab | Right-click VM and select Edit Settings
Select Harddisk for RDM and Remove | Click Finish

vmds3aex03
3Par EMC
18 XX
15 XX
19 XX
16 XX
20 XX
17 XX
27 XX

vmds3aex04
3Par EMC
21 XX
25 XX
22 XX
26 XX
23 XX
24 XX

6. Migrate VMs to new datastore on existing VMHost

Select Datastore view | Select Virtual Machines tab |Right-click VM and select Migrate
Select Cluster | Select VMHost |Click Next for validations |Select to use new datastore
Click Next | Click Finish

vmds3aaa01 - No RDMs

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 5 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

vmds3aeb01 - No RDMs
vmds3aeo02 - No RDMs
vmds3aex03
vmds3aex04

Source Datastore: Target Datastore:

3par-vmfs-Tecumseh_Exchange emc-vmfs-Tecumseh_Exchange

7. Add the target RDMs

Select Datastore view | Select Virtual Machines tab | Right-click VM | select Edit Settings
Click Add | Select Hard disk | click Next |Select Raw Device Mappings | click Next
Select RDM LUN | click Next | Leave the defaults and click Next | Click Finish

Add the following target RDMs

vmds3aex03
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX

vmds3aex04
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX

8. Power on VMs and watch for errors on console

Select Datastore view | Select Virtual Machines tab | Right-click VM and select Power On

vmds3aaa01
vmds3aeb01
vmds3aeo02
vmds3aex03
vmds3aex04

9. Windows administration to confirm and verify RDM data

11. Inform Applications/DBA to startup Applications/databases

Confirmation required from AT&T

This completes VMWARE guest cold migration

6. Validate Host operations and applications.

Confirmation required from AT&T

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 6 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

------------------------------------

Section 3 – Fail-back
------------------------------------

NOTE: Fail-back will require software removal, system application shutdown, host reboots, patching
and zoning change.
NOTE: Zoning and fabric changes will require re-establishing original patching.

For the affected VM(s)

1. Confirm applications/dB have completed shutdown

Confirmation required from AT&T

2. Perform a shutdown of VM only

3. Perform Cold VM migration back to original datastore

4. Power on VM(s) and watch for errors on console

5. Log into VM(s) and check visibility of drives and data

6. Attach original RDM devices from 3par

7. Discover devices in the host using disk management rescan disks

8. Change drive letters back to original configuration on original 3par RDMs

9. Restart applications.

10. AT&T to validate original configuration is working correctly.

Notification Requirements
N/A – transition Change to successful

Documentation Modification Requirements

N/A

Scheduled Job Impact

N/A

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 7 of 8
 119.a_VM_COLD_ Migration_SMOP.doc

Additional Relevant Links/Resources

N/A

*** END OF SMOP (CR) ***

AT&T – PROPRIETARY RESTRICTED

Solely for Authorized Persons having a Need to Know
Pursuant to Company Instructions Page 8 of 8