Migration with EVA using External Storage XP

Rev # 1.0

Description New Document

Date 01/09/08

Revision: 2007-11-07

Table of contents
Notes on usage ................................................................................................................................... 2 Brief overview for migrating from native EVA disk to XP External Storage disk............................................. 2 Windows migration from EVA native to XP external storage...................................................................... 4 Vmware ESX 3.x migration from EVA native to XP external storage. ........................................................ 11 SUSE Linux migration from EVA native to XP external storage. ................................................................ 17 HP-UX migration (standalone) from EVA native to XP external storage. ..................................................... 22 HP-UX migration (cluster) from EVA native to XP external storage............................................................. 29 Migration using Tiered Storage Manager ............................................................................................. 36 Migration using Business Copy XP ....................................................................................................... 39 Expanding a LUN/LUSE online (only windows supported) ...................................................................... 40 Appendix A - SSID............................................................................................................................. 41 Appendix B XP operations................................................................................................................ 42 Appendix C - div ............................................................................................................................... 47 Appendix D Importing disks from EVA5000 ....................................................................................... 48

Notes on usage
Although this paper is specifically titled to work with an EVA as external storage, most steps (all except for those that require the use of Command View EVA) can be translated over to the external storage device of your choice. Things such as Tiered Storage Manager and Business Copy migration work exactly the same across external storage devices and so migration using those tools can be directly applied to other external storage devices.

Supported Verses Recommended

Recommended: Indicating a subset of the larger Supported space of configurations. In addition to Supported, which is considered to be a functional but not necessarily optimal configuration, Recommended is considered to represent a particular sweet spot for optimal customer satisfaction, an is much more likely to have been characterized by finite testing resources. Supported: In that it is not practical to test every possible permutation and combination of components and settings, supported represents the space of we have every reason to believe this to be a functional, although not necessarily optimal configuration and although this specific configuration may or may not have been characterized by finite testing resources, we will stand behind it.

Brief overview of the process for migrating from native EVA disk to XP External Storage disk
The following list of operations is a high level overview of the steps required to move an EVA from a host application perspective from direct host connect to connection to the EVA by way of the XP. For OS specific notes, see the following sections. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Zone the XP-ports to the EVA Zone the XP-port to the host Import EVA array to the XP Create a host group for the new host Present the EVA-device to the XP Import the device to the XP Shutdown the application directly accessing the EVA device Add the imported volumes to the host group Delete the EVA from the zone to the host Restart the application to access the EVA device by way of the XP Confirm that the LUN is accessible and that the data is correct Delete the direct host EVA device mapping

Windows migration from EVA native to EVA via XP external storage

This migration procedure has been verified by HP. Steps 6-10 requires planned application down time. Red text is important to follow exactly. If not, there is a risk of data corruption!!!

PRE PROCEDURE Step 1: Zone the server/cluster with XP host ports (these servers could only see EVA host ports before). Zone EVA host ports to external storage ports on the XP. Step 2: Create a host group for every server in both XP clusters. Add the HBAs WWN to this host group. 1. 2. 3. 4. 5. 6. Log in to Remote Web Console Go in to Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Do not use default host group number 00, see Appendix C Mark and right-click on the XP-port where you want to create the host group Add New Host Group. 7. Insert Group Name 8. Choose Host mode according to SPOCK 00 Linux (most distributions, but check with support matrix) 01 VMware 08 HPUX 2C Windows extension 9. In case of VMware Click Option and mark Option 19 10. Press OK 11. Right-click on the new group (in blue) and choose Add New WWN 12. Choose the hosts WWN from the Drop down list or enter manually 13. Enter a Nickname 14. Press Ok 15. Redo the steps from step 6 for Alternate paths to host. 16. Press Apply

Step 3: Present EVA virtual disks that were presented to the host servers so they are presented instead to the XP. Always use windows as the Operating System Type (from the EVA GUI) when presenting EVA disks to an XP. Take note of the LUN-number used when presenting the EVA virtual disk to the XP. Step 4: Import these EVA virtual disks in the XP as Open-V LDEVs. Import to the correct CLPR (cache partition). Pay attention to what LUN number you are working with, so you import correct EVA virtual disk.

Create only one XP LDEV of per EVA virtual disk. One virtual disk from the EVA should NOT be divided in to several LDEVs in the XP. Do not present these LDEVs to the server yet. Take note of which Virtual EVA disk is mapped to which XP LDEV.

Import the device to the XP, Manual (Select devices mapped to an XP-port) Note: When using an EVA5000 as external storage and the EVA with 3.X firmware, and the XP has 60.01.68 or earlier, use the instructions from Appendix D in order to import the devices. When youre importing devices from an EVA, for the first time. Spread the load over multiple paths by repeating the procedure 4 times (the amount of paths to the EVA) and use step 5a-5f all 4 times. Add the paths in different order to give them different priorities. You might only import 1 disk at a time, depending on how many you are going to import. Note that the LUN# in the EVA is presented in decimal, and in the XP it appears as hexadecimal (characteristics of the device) 1. 2. 3. 4. 5. Log in to Remote Web Console. Enter Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. If the EVA frame is not yet known to the XP: a) Right click Subsystem Add Volume (Manual) (Default Policy) b) Choose EVA Port (on XP) WWNs (ports on EVA) c) Right click on WWN and add paths (Repeat for each XP-port connected the that EVA)

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!!

Cache mode disable Inflow control disable CLPR 2 The number of LDEVs MUST be set to 1

If the EVA frame is already known to the XP as External Storage: a) Expand the EVA from which you wish to import devices b) Right click one of the Path Group # - Add Volume (Manual) (Default Policy). Try to import devices equally to the available Path Groups in order to spread the load. 6. Right click again on devices LDEV Mapping (Auto) 7. Mark the first available ldev (Start top to the left in matrix, select a different CU# if the table is all grey).

8. Delete the devices in the list that should not be imported at this time. 9. Document the CU#, Ldev# and ExG# 10. Press OK 11. If asked for SSID, see SSID-table in appendix A. 12. Press Apply OK

Set path parameters If you have just added new paths between the XP and the EVA you need to adjust some parameters that impact on the paths behaviour. 1. 2. 3. 4. 5. 6. 7. Log in to Remote Web Console Enter Modify Mode Go to External Storage Path operations Choose External Subsystem Mark the EVA where the new paths reside Right click on the WWN of the path Change WWN Parameter Set parameters to Q-depth for external LU (2-128) = 32 I/O TOV (5-240) = 15s (4 paths) I/O TOV 5(240) = 30s (2 paths) Path Blockade Watch (5-180) = 180s 8. Press OK 9. Press Apply 10. Press OK

MIGRATION PROCEDURE Step 5: Within each server, rename the label of each disk so that the volume label includes the drive letter or mount-point used by that disk. In each server, install the recommended HBA drivers and XP multi-path software. In the server, use diskpart to see the disk signature of every SAN-disk. If this is a cluster, be sure to do this on all cluster nodes. The disk signature info should be saved in a text file on the C-disk of the server. Also, keep a copy somewhere else.
C:\Documents and Settings\Administrator>diskpart Microsoft DiskPart version 5.2.3790.1830 Copyright 1999-2001 Microsoft Corporation. On computer: SELDMGT42 DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --Disk 0 Online 68 GB 0B Disk 1 Online 937 GB 0B Disk 2 Online 100 MB 0B DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> detail disk HP LOGICAL VOLUME SCSI Disk Device Disk ID: CAF6CAF6 Type : RAID Bus : 0 Target : 4 LUN ID : 0 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------Volume 0 C NTFS Partition 68 GB Healthy System DISKPART> select disk 1 Disk 1 is now the selected disk.

DISKPART> detail disk HP OPEN-V Multi-Path Disk Device Disk ID: 4EF5DEB9 Type : FIBRE Bus : 0 Target : 0 LUN ID : 0 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------Volume 1 D XP test dis NTFS Partition 937 GB Healthy DISKPART> select disk 2 Disk 2 is now the selected disk. DISKPART> detail disk HP OPEN-V-CM Multi-Path Disk Device Disk ID: 4EF5DEBA Type : FIBRE Bus : 0 Target : 0 LUN ID : 1 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------Volume 2 Partition 100 MB Healthy

Now, we need to determine if we need to run scrubber according to step 9. If needed, install the hotfix now, before shutting down of the server. For more information, please see:

http://support.microsoft.com/kb/277222/en-us

Step 6: Shutdown either the server or the application. If this is a cluster, shutdown all nodes in the cluster. Step 7: Change the zoning so that the server no longer sees the EVA directly. It should only see the XP. Step 8: From the XP, present the imported LDEVs to the servers using one path only. That is: For each disk, only presentation your LDEVs from one XP port to one HBA in each server. Make sure to assign LUN 0 (zero) in each host group. Windows needs to see a LUN 0 from each SAN-target port. Windows will use the disk-signature in NTFS to identify each disk. Therefore, we do not need to keep the same LUN-number ordering as we had when we presented the volume directly from the EVA to the host. Add Volume to a Host group 1. 2. 3. 4. Log in to Remote Web Console Enter into Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog

5. Expand the port where your host is/will be connected and choose the host group of the host. 6. Mark the LDEVs that are to be added to the host 7. Mark the LUN numbers that are going to be mapped 8. Click on Add LU Path 9. Review your changes and click ok 10. Click on Apply Step 9: Boot the servers, or restart the application. Check that you can mount all SAN-disks. Check that the expected file system was mounted in each mount point. If this server is an active directory server with the active directory database located on a SAN-disk, windows will fail to boot because it can not find the SAN-disk. This is the case because the device driver for your disks has not yet been installed. The solution is: Press F8 during boot, then start the server in Active Directory restore mode. Wait for the disk to become accessible. If your disks are dynamic disks in Windows, you will need to activate the disks in Windows Disk Management before they can be accessed again. If your server could see many EVA virtual disks, run scrubber.exe before you reboot the server again. This step is very important on Windows 2000 servers and on Windows 2003 servers that boot with the /3GB switch in boot.ini. In a Windows cluster, it is important to have all clustered disks online on the node that runs scrubber.exe. For more information, please see:

http://support.microsoft.com/kb/277222/en-us

Each presented disk from an EVA8000 counts as 9 devices in the registry (1 mpio dev and 8 EVApaths, assuming all paths are presented). Each presented disk from an EVA5000 counts as 5 devices in the registry (1 Securepath device and 4 EVA-paths, assuming all paths are presented).

Step 10: In the XP, present the redundant paths for your imported LDEVs to the servers. Add Volume to a Host group 1. Log in to Remote Web Console 2. Enter Modify Mode 3. Go to LUN Manager LU Path and Security 4. Expand the Fibre catalog 5. Expand the port where your host is/will be connected and choose the host group for the host. 6. Mark the LDEVs that are to be added to the host 7. Mark the LUN numbers that are going to be mapped 8. Click on Add LU Path 9. Review your changes and click ok 10. Click on Apply

Make sure to assign LUN 0 (zero) in each host group. Windows needs to see a LUN 0 from each SAN-target port. It is suggested to present the LDEVs using the same LUN-number on both XP host

ports so that the multi-pathing software does not see the volume with different LUN-numbers on the different SAN-paths from the server to the XP. On each server, perform a scan for hardware changes in device manager. Check in your multi-path software so that all disks now have 2 paths in the SAN to the XP. Also set the desired load balancing policy. Because Windows installs the device driver for the disk after boot up, it will be a short delay before the disk will be accessible. This can cause applications or shares to fail start up because the application tries to start when Windows starts, and the disks become accessible a little later. Therefore, it is a best practise to perform a second reboot after you have checked that all disk drives are accessible in windows. Now is a good time to perform this second reboot.

POST PROCEDURE

Step 11: Un-present the virtual disks in the EVA so that the server can no longer directly see them. The presentation to the XP still remains. END of Windows migration

10

Vmware ESX 3.x migration from EVA native to XP external storage.

This migration procedure has been verified by HP. Steps 5-10 require planned down time. Red text is important to follow exactly. If not, there is a risk of data corruption!!!

PRE PROCEDURE
Step 1: Zone the ESX-servers (that so far can see only the EVA ports) to be able to see the XP host ports Zone EVA host ports to be able to see the external storage ports on the XP.

Step 2: Create an XP host group for every physical ESX-server in both clusters. Add the HBA WWN to this host group. Create a host group for the new host 1. 2. 3. 4. 5. 6. Log in to Remote Web Console Enter Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Do not use default host group number 00, see Appendix C. Mark and right click the XP-port where you want to create the host group Add New Host Group. 7. Insert the Group Name 8. Choose the Host mode according to SPOCK 00 Linux (most distributions, but check with support matrix) 01 VMware 08 HPUX 2C Windows extension 9. In case of VMware Click Option and mark Option 19 10. Press OK 11. Right click on the new group (in blue) and choose Add New WWN 12. Choose the hosts WWN from the Dropdown list or enter manually 13. Enter a Nickname 14. Press Ok 15. Redo the steps from step 6 for Alternate paths to host. 16. Press Apply

Step 3: Present EVA virtual disks that were previously directly presented to the host to the XP. Always use windows as the Operating System Type when presenting disks to an XP from an EVA. Take note of the LUN number the virtual disk is assigned in the ESX server and what LUN number is used when presenting this virtual disk to the XP. When we later present these volumes from the XP to the ESX server, they must have the same LUN number as they had when they were presented from the EVA.

11

Step 4: Import these EVA virtual disks into the XP as Open-V LDEVs. Use the desired CLPR (cache partition). Pay attention to what LUN number you are working with so you import correct EVA virtual disk. Create only one XP LDEV per EVA virtual disk. One virtual disk from the EVA shall NOT be divided in several LDEVs in the XP. Do not present these LDEVs to the ESX-servers yet. Take a note as to which Virtual EVA disk is mapped to which LDEV.

Import the device to the XP using the Auto method (all devices mapped to an XP-port) 1. 2. 3. 4. 5. 6. 7. 8. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. Right click Subsystem Add Volume (Auto) (Default Policy) Choose EVA Port (on XP) WWN (port on EVA) Right click on WWN and add path (Repeat for redundancy) Press ok

Import the device to the XP using the Manual method (Select devices mapped to an XP-port) When youre importing devices from an EVA that have not previously been configured as External Storage, spread the load over multiple paths. Repeat the procedure 4 times (same as the amount of paths to the EVA) and use step 5a-5f all 4 times and add each paths in a different order in order to give them different priorities. You might only import 1 disk at a time, depending on how many you are going to import. Notice that the LUN# in the EVA is represented in decimal, and in XP it appears as hexadecimal (characteristics of the device) 1. 2. 3. 4. 5. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. If the EVA is not yet configured as External Storage a) Right click Subsystem Add Volume (Manual) (Default Policy) b) Choose EVA Port (on XP) WWNs (ports on EVA)

12

c)

Right click on WWN and add paths (Repeat for each XP-port connected the that EVA)

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!! Cache mode disable Inflow control disable CLPR 2 If the EVA frame is already configured as External Storage c) Expand the EVA from which you wish to import devices d) Right click one of the Path Group # - Add Volume (Manual) (Default Policy). Try to import devices equally to the Path Groups to spread the load. 6. Right click again on devices LDEV Mapping (Auto) 7. Mark the first available ldev (Start top to the left in the matrix, change the CU# if the table is all grey).

13

8. Delete the devices in the list that should not be imported at this time. 9. Document the CU#, Ldev# and ExG# 10. Press OK 11. If asked for SSID, see the SSID-table in appendix A. 12. Press Apply OK

Set the path parameters If you have just added new paths between the XP and the EVA, you will need to adjust some parameters that have impact on the paths behaviour. 1. 2. 3. 4. 5. 6. 7. Log in to Remote Web Console Go to Modify Mode Go to External Storage Path operations Choose External Subsystem Mark the EVA where the new paths resides Right click on the WWN that the path goes to in the right pane Change WWN Parameter Set parameters to Q-depth for external LU (2-128) = 32 I/O TOV (5-240) = 15s (4 paths) I/O TOV 5(240) = 30s (2 paths) Path Blockade Watch (5-180) = 180s 8. Press OK 9. Press Apply 10. Press OK

14

MIGRATION PROCEDURE
Step 5: This step must be done on all physical ESX-servers that the EVA virtual disk was presented to. Change LVM.DisallowSnapshotLun to 0 (default 1) and LVM.EnableResignature to 0 (default 0). (see picture below)

Step 6: Shutdown all virtual servers and the ESX-servers.

Step 7: Change the zoning so that the ESX servers no longer see the EVA. It shall only see the XP. Step 8: From the XP, present the imported LDEVs to the ESX-servers with the correct LUN number. That is, the same LUN number that was used when the disk was presented from the EVA. (VmWare is sensitive to volumes changing LUN number) Add the Volume to an XP Host group 1. Log in to Remote Web Console 2. Go in to Modify Mode 3. Go to LUN Manager LU Path and Security 4. Expand the Fibre catalog 5. Expand the port where your host is/will be connected and choose the host group for the host. 6. Mark the LDEVs that are to be added to the host 7. Mark the LUN numbers that are going to be mapped with that device. 8. Click on Add LU Path 9. Review your changes and click ok 10. Click on Apply

15

Step 9: Boot the ESX-servers. Boot the virtual servers. Step 10: For every physical ESX-server, change back LVM.DisallowSnapshotLun and LVM.EnableResignature to the default Step 11: Check in ESX that you have the correct number of paths from the XP to the physical ESX server.

POST PROCEDURE
Step 12: Un-present the virtual disks in the EVA so that the ESX-servers no longer can see them directly. The presentation to the XP should remain.

END of WMware ESX migration

16

SUSE Linux migration from EVA native to XP external storage.

This migration procedure has been verified by HP in a test environment. Steps 6-10 requires planned down time. Testing has not been performed on either the CIC-server or the clustered gateway server. Red text is important to follow exactly. If not, there is a risk of data corruption!!!

PRE PROCEDURE
Step 1: Zone the Linux server/cluster to see the XP host ports (these servers only see EVA host ports so far). Zone the EVA host ports to see the external storage ports on the XP. Step 2: Create an XP host group for every server in both XP clusters. Add the HBA WWN to this host group. Set host mode 00 (zero zero) for these host groups according to SPOCK. Create a host group for the new host 1. 2. 3. 4. 5. 6. Log in to Remote Web Console Go in to Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Do not use default host group number 00, see Appendix C. Mark and right-click on the XP-port you where you want to create the host group Add New Host Group. 7. Insert Group Name 8. Choose Host mode 00 Linux (most distributions, but check with support matrix) 01 VMware 08 HPUX 2C Windows 9. In case of VMware Click Option and mark Option 19 10. Press OK 11. Right click on the new group (in blue) and choose Add New WWN 12. Choose the hosts WWM from the Dropdown list or enter manually 13. Enter a Nickname 14. Press Ok 15. Redo the steps from step 5 for Alternate paths to host. 16. Press Apply

Step 3: Present EVA virtual disks that were directly presented to the host servers to the XP. Always use windows as the Operating System Type when presenting EVA disks to an XP.

17

Take note of what LUN number the virtual disk is currently assigned to the servers and what LUN number was used when presenting this virtual disk to the XP. When we later present these volumes from the XP to the server, we want to use the same LUN number as they had when they were presented directly from the EVA.

Step 4: Import the EVA virtual disks in the XP as Open-V LDEVs . Assign to the correct CLPR (cache partition) Pay attention to what LUN number we are working with so we import the correct EVA virtual disk. Create only one XP LDEV per EVA virtual. One virtual disk from the EVA shall NOT be divided in several LDEVs in the XP. Do not present these LDEVs to the servers yet. Take note of which Virtual EVA disk is mapped to which LDEV.

Import the device to the XP, Auto (all devices mapped to an XP-port) 1. 2. 3. 4. 5. 6. 7. 8. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right-click Subsystem Check Edit Policy, change if needed, then close. Right-click Subsystem Add Volume (Auto) (Default Policy) Choose EVA Port (on XP) WWN (port on EVA) Right-click on WWN and add path (Repeat for redundancy) Press ok

Import the device to the XP, using the Manual method (Select devices mapped to an XP-port) When youre importing devices from an EVA frame that has not been configured as External Storage before, spread the load over multiple paths. Repeat the procedure 4 times (same as the amount of paths to the EVA) and use step 5a-5f all 4 times and add the paths in different order to give them different priorities. You might only import 1 disk at each time, depending on how many you are going to import.

Notice that the LUN# in the EVA is presented in decimal, and in the XP it appears as hexadecimal (characteristics of the device)

1. 2. 3. 4. 5.

Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. If the EVA frame is not yet configured as External Storage a) Right click Subsystem Add Volume (Manual) (Default Policy) b) Choose EVA Port (on XP) WWNs (ports on EVA)

18

c)

Right click on WWN and add paths (Repeat for each XP-port connected the that EVA)

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!! Cache mode disable Inflow control disable CLPR 2 If the EVA frame is already configured as External Storage e) Expand the EVA you wish to import devices from f) Right click one of the Path Group # - Add Volume (Manual) (Default Policy). Try to import devices equally to the Path Groups to spread the load. 6. Right click again on devices LDEV Mapping (Auto) 7. Mark the first available ldev (Start at the top left in the matrix, change the CU# if the table is all grey).

19

8. Delete devices in the list that should not be imported at this time. 9. Document the CU#, Ldev# and ExG# 10. Press OK 11. If asked for SSID, see SSID-table in appendix A. 12. Press Apply OK Set path parameters If you have just added new paths between the XP and the EVA, you will need to adjust some parameters that have impact on the paths behavior. 11. Log in to the Remote Web Console 12. Go to Modify Mode 13. Go to External Storage Path operations 14. Choose External Subsystem 15. Mark the EVA where the new paths reside 16. Right click on the WWN that the path goes to in the right pane Change the WWN Parameter 17. Set parameters to Q-depth for external LU (2-128) = 32 I/O TOV (5-240) = 15s (4 paths) I/O TOV 5(240) = 30s (2 paths) Path Blockade Watch (5-180) = 180s 18. Press OK 19. Press Apply 20. Press OK

Step 5: For mounted file systems, make note of the disk device names and mount points. This info is good to have ready just in case the OS re-orders the disks after we have migrated to the XP. That is, if the existing device names point to different disks (seen from the OS) after the migration. Also keep a copy of this information in another location.

20

MIGRATION PROCEDURE
Step 6: Shutdown the server or cluster. Step 7: Change the zoning so that the servers no longer see the EVA. It shall only see the XP. Step 8: From the XP, present the imported LDEVs to the servers with the correct LUN numbers. That is, the same LUN number that was used when the disk was presented from the EVA. If the same LUN-number is not used, the OS might reorder the disks as mentioned in Step 5. Add each Volume to a Host group 1. Log in to Remote Web Console 2. Go in to Modify Mode 3. Go to LUN Manager LU Path and Security 4. Expand the Fibre catalog 5. Expand the port where your host is/will be connected and choose the host group of the host. 6. Mark the LDEVs that are to be added to the host 7. Mark the LUN numbers that are going to be mapped with that device. 8. Click on Add LU Path 9. Review your changes and click ok 10. Click on Apply Step 9: Boot the servers. Check that you can mount all SAN-disks. Check that the expected file system was mounted in each mount point. Step 10: On each disk, check that you have 2 paths in the SAN to the XP.

POST PROCEDURE
Step 11: Un-present the virtual disks in the EVA so that the server can no longer see them. The presentation to the XP shall remain.

END of SUSE Linux migration

21

HP-UX migration (standalone) from EVA native to XP external storage.

This migration procedure has been verified by in a test environment HP. Steps 6-10 requires planned down time. This procedure was tested on a temporary installed rx2600 with hp-ux 11.23. Red text is important to follow exactly. If not, there is a risk of data corruption!!!

PRE PROCEDURE
Step 1: Zone the HP-UX server with XP host ports (these servers only see EVA host ports today). Zone the EVA host ports to external storage ports on the XP.

Step 2: Create a host group for every server in both XP clusters. Add HBA WWN to this host group. Create a host group for the new host 1. 2. 3. 4. 5. 6. Log in to Remote Web Console Go in to Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Do not use default host group number 00, see Appendix C Mark and right click on the XP-port you where you want to create the host group Add New Host Group. 7. Insert Group Name 8. Choose Host mode 00 Linux (most distributions, but check with support matrix) 01 VMware 08 HPUX 2C Windows 9. In case of VMware Click Option and mark Option 19 10. Press OK 11. Right click on the new group (in blue) and choose Add New WWN 12. Choose the hosts WWM from the Dropdown list or enter manually 13. Enter a Nickname 14. Press Ok 15. Redo the steps from step 5 for Alternate paths to host. 16. Press Apply

Step 3: Present EVA virtual disks that are presented to the host servers so they are presented also to the XP.

22

Always use windows as Operating System Type when presenting disks to an XP from an EVA. Take a note of what LUN number the virtual disk today is presented to the servers and what LUN number used when presenting this virtual disk to the XP. When we later present these volumes from the XP to the server we want to user the same LUN number as they had when they were presented directly from the EVA.

Step 4: Import these EVA virtual disks in the XP as Open-V LDEVs . Import to the correct CLPR (cache partition) Pay attention to what LUN number we are working with so we import correct EVA virtual disk. Create only one LDEV of every virtual disk that is presented from the EVA. One virtual disk from the EVA shall NOT be divided in several LDEVs in the XP. Do not present these LDEVs to the servers yet. Take a note of which Virtual EVA disk is mapped to which LDEV.

Import the device to the XP, Auto (all devices mapped to an XP-port) 1. 2. 3. 4. 5. 6. 7. 8. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right-click Subsystem Check Edit Policy, change if needed, then close. Right-click Subsystem Add Volume (Auto) (Default Policy) Choose EVA Port (on XP) WWN (port on EVA) Right-click on WWN and add path (Repeat for redundancy) Press ok

Import the device to the XP, Manual (Select devices mapped to an XP-port) When youre importing devices from an EVA, not configured as External Storage since before. To spread the load over multiple paths, repeat the procedure 4 times (same as the amount of paths to the EVA) and use step 5a-5f all 4 times and add the paths in different order to give them different priorities. You might only import 1 disk at each time, depending on how many you are going to import.

Notice that the LUN# in the EVA is in decimal, and in XP it appears as hexadecimal (characteristics of the device)

1. 2. 3. 4. 5.

Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. If the EVA is not configured as External Storage a) Right click Subsystem Add Volume (Manual) (Default Policy) b) Choose EVA Port (on XP) WWNs (ports on EVA)

23

c)

Right click on WWN and add paths (Repeat for each XP-port connected the that EVA)

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!! Cache mode disable Inflow control disable CLPR 2 If the EVA is already configured as External Storage g) Expand the EVA you wish to import devices from h) Right click one of the Path Group # - Add Volume (Manual) (Default Policy). Try to import devices equally to the Path Groups to spread the load. 6. Right click again on devices LDEV Mapping (Auto) 7. Mark first available ldev (Start top to the left in matrix, change CU# if all table is grey).

24

8. Delete devices in the list that should not be imported at this time. 9. Document the CU#, Ldev# and ExG# 10. Press OK 11. If asked for SSID, see SSID-table in appendix A. 12. Press Apply OK Set path parameters If you have just added new paths between the XP and the EVA you need to adjust some parameters that have impact on the paths behaviour. 1. 2. 3. 4. 5. 6. 7. Log in to Remote Web Console Go to Modify Mode Go to External Storage Path operations Choose External Subsystem Mark the EVA where the new paths resides Right click on the WWN that the path goes to in the right pane Change WWN Parameter Set parameters to Qdepth for external LU (2-128) = 32 I/O TOV (5-240) = 15s (4 paths) I/O TOV 5(240) = 30s (2 paths) Path Blockade Watch (5-180) = 180s 8. Press OK 9. Press Apply 10. Press OK

Step 5: - Save LVM config files from every volume group thats being migrated
# vgexport -m /var/tmp/vg01.map -s -p -v /dev/vg01 Beginning the export process on Volume Group "/dev/vg01". vgexport: Volume group "/dev/vg01" is still active. /dev/dsk/c8t0d1 # vgexport -m /var/tmp/vg02.map -s -p -v /dev/vg02 Beginning the export process on Volume Group "/dev/vg02". vgexport: Volume group "/dev/vg02" is still active. /dev/dsk/c8t0d2

- Document volume groups device files

# ll /dev/*/group crw-r----1 root crw-rw-rw1 root crw-rw-rw1 root sys sys sys 64 0x000000 Sep 12 00:24 /dev/vg00/group 64 0x010000 Sep 13 18:02 /dev/vg01/group 64 0x020000 Sep 13 18:03 /dev/vg02/group

25

MIGRATION PROCEDURE
Step 6: - Shutdown any application using the file systems being migrated - Unmount file systems
# umount /dev/vg01/lvol1 # umount /dev/vg02/lvol1

- Deactivate volume groups

# vgchange -a n /dev/vg01 Volume group "/dev/vg01" has been successfully changed. # vgchange -a n /dev/vg02 Volume group "/dev/vg02" has been successfully changed.

- Export volume groups

# vgexport /dev/vg01 # vgexport /dev/vg02

- Verify volume groups exported OK

# strings /etc/lvmtab /dev/vg00 /dev/dsk/c3t2d0s2

(output should only show volume groups NOT being migrated) Step 7: Change zoning so that the servers no longer sees the EVA. It shall only see the XP. Step 8: From the XP present the imported LDEVs to the servers with the correct LUN number. The same LUN number that was used when the disk was presented from the EVA. If the same LUN-nr is not used, the OS might reorder the disks as mentioned in Step 5.

Add Volume to a Host group 1. Log in to Remote Web Console 2. Go in to Modify Mode 3. Go to LUN Manager LU Path and Security 4. Expand the Fibre catalog 5. Expand the port where your host is/will be connected and choose the host group of the host. 6. Mark the LDEVs that are to be added to the host 7. Mark the LUN numbers that are going to be mapped with that device. 8. Click on Add LU Path 9. Review your changes and click ok 10. Click on Apply

26

Step 9: - Identify new devices

# ioscan disk disk disk disk -fC 12 14 13 15 disk |grep -i open 0/3/1/0.4.0.93.0.0.1 0/3/1/0.4.0.93.0.0.2 0/4/1/0.3.0.101.0.0.1 0/4/1/0.3.0.101.0.0.2 sdisk sdisk sdisk sdisk CLAIMED CLAIMED CLAIMED CLAIMED DEVICE DEVICE DEVICE DEVICE HP HP HP HP OPEN-V OPEN-V OPEN-V OPEN-V

- Create device files for new LUNs

# insf -e -H 0/3/1/0 insf: Installing special files for sctl instance 11 address 0/3/1/0.4.0.90.0.0.0 . . # insf -e -H 0/4/1/0 insf: Installing special files for sctl instance 10 address 0/4/1/0.3.0.97.0.0.0

- Create device files for removed volume Groups. Verify that these files have the same minor number as before and that it doesnt exist device files with same minor number.
# mkdir /dev/vg01 # mkdir /dev/vg02 # mknod /dev/vg01/group c 64 0x010000 # mknod /dev/vg02/group c 64 0x020000 # ll /dev/*/group crw-r----1 root sys 64 0x000000 Sep 12 00:24 /dev/vg00/group crw-rw-rw1 root sys 64 0x010000 Sep 14 19:59 /dev/vg01/group crw-rw-rw1 root sys 64 0x020000 Sep 14 19:59 /dev/vg02/group

- Import and activate the volume groups

# vgimport -m /var/tmp/vg01.map -s -v /dev/vg01 Beginning the import process on Volume Group "/dev/vg01". Logical volume "/dev/vg01/lvol1" has been successfully created with lv number 1. Volume group "/dev/vg01" has been successfully created. # vgimport -m /var/tmp/vg02.map -s -v /dev/vg02 Beginning the import process on Volume Group "/dev/vg02". Logical volume "/dev/vg02/lvol1" has been successfully created with lv number 1. Volume group "/dev/vg02" has been successfully created. # vgchange -a y /dev/vg01 Activated volume group Volume group "vg01" has been successfully changed. # vgchange -a y /dev/vg02 Activated volume group Volume group "vg02" has been successfully changed.

- Split the i/o load over different HBAs, Fabrics, and XP cluster. Remove the primary path for every second volume group and add it again.
# vgdisplay -v /dev/vg02 |grep -i "PV Name" PV Name /dev/dsk/c10t0d2 PV Name /dev/dsk/c11t0d2 Alternate Link # vgreduce /dev/vg02 /dev/dsk/c10t0d2 Device file path "/dev/dsk/c10t0d2" is an primary link. Removing primary link and switching to an alternate link. Volume group "/dev/vg02" has been successfully reduced. Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf # vgextend /dev/vg02 /dev/dsk/c10t0d2 Volume group "/dev/vg02" has been successfully extended. Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf # vgdisplay -v /dev/vg02 |grep -i "PV Name" PV Name /dev/dsk/c11t0d2 PV Name /dev/dsk/c10t0d2 Alternate Link

- Backup volume group configuration

# vgcfgbackup /dev/vg01 Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf # vgcfgbackup /dev/vg02

27

Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf

- Mount files systems

# mount /dev/vg01/lvol1 /mnt1 # mount /dev/vg02/lvol1 /mnt2

Check that the expected file system was mounted in each mount point.

Step 10: Start applications

POST PROCEDURE
Step 11: Un-present the virtual disks in the EVA so that the server no longer can see them. The presentation to the XP shall remain.

END of HP-UX standalone migration

28

HP-UX migration (cluster) from EVA native to XP external storage.

This procedure has not been tested completely due to missing equipment. Migration of standalone HPUX system has been fully tested by HP. The steps that differs with clustered HP-UX systems have been tested during other storage migrations in similar production environment. Steps 6-10 requires planned down time. Red text is important to follow exactly. If not, there is a risk of data corruption!!!

PRE PROCEDURE
Step 1: Zone the HP-UX server/cluster with XP host ports (these servers only see EVA host ports today). Zone the EVA host ports to external storage ports on the XP. Step 2: Create a host group for every server in both XP clusters. Add HBA WWN to this host group. Set host mode 08 (zero eight) for these host groups according to SPOCK. Create a host group for the new host 1. 2. 3. 4. 5. 6. Log in to Remote Web Console Go in to Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Do not use default host group number 00, see Appendix C. Mark and right-click on the XP-port you where you want to create the host group Add New Host Group. 7. Insert Group Name 8. Choose Host mode 00 Linux (most distributions, but check with support matrix) 01 VMware 08 HPUX 2C Windows 9. In case of VMware Click Option and mark Option 19 10. Press OK 11. Right click on the new group (in blue) and choose Add New WWN 12. Choose the hosts WWM from the Dropdown list or enter manually 13. Enter a Nickname 14. Press Ok 15. Redo the steps from step 5 for Alternate paths to host. 16. Press Apply

Step 3: Present EVA virtual disks that are presented to the host servers so they are presented also to the XP. Always use windows as Operating System Type when presenting disks to an XP from an EVA.

29

Take a note of what LUN number the virtual disk today is presented to the servers and what LUN number used when presenting this virtual disk to the XP. When we later present these volumes from the XP to the server we want to user the same LUN number as they had when they were presented directly from the EVA.

Step 4: Import these EVA virtual disks in the XP as Open-V LDEVs . Import to the correct CLPR (cache partition) Pay attention to what LUN number we are working with so we import correct EVA virtual disk. Create only one LDEV of every virtual disk that is presented from the EVA. One virtual disk from the EVA shall NOT be divided in several LDEVs in the XP. Do not present these LDEVs to the servers yet. Take a note of which Virtual EVA disk is mapped to which LDEV.

Import the device to the XP, Auto (all devices mapped to an XP-port) 1. 2. 3. 4. 5. 6. 7. 8. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. Right click Subsystem Add Volume (Auto) (Default Policy) Choose EVA Port (on XP) WWN (port on EVA) Right click on WWN and add path (Repeat for redundancy) Press ok

Import the device to the XP, Manual (Select devices mapped to an XP-port) When youre importing devices from an EVA, not configured as External Storage since before. To spread the load over multiple paths, repeat the procedure 4 times (same as the amount of paths to the EVA) and use step 5a-5f all 4 times and add the paths in different order to give them different priorities. You might only import 1 disk at each time, depending on how many you are going to import. Notice that the LUN# in the EVA is in decimal, and in XP it appears as hexadecimal (characteristics of the device) 1. 2. 3. 4. 5. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. If the EVA is not configured as External Storage a) Right click Subsystem Add Volume (Manual) (Default Policy) b) Choose EVA Port (on XP) WWNs (ports on EVA)

30

c)

Right click on WWN and add paths (Repeat for each XP-port connected the that EVA)

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!! Cache mode disable Inflow control disable CLPR 2 If the EVA is already configured as External Storage i) Expand the EVA you wish to import devices from j) Right click one of the Path Group # - Add Volume (Manual) (Default Policy). Try to import devices equally to the Path Groups to spread the load. 6. Right click again on devices LDEV Mapping (Auto) 7. Mark first available ldev (Start top to the left in matrix, change CU# if all table is grey).

31

8. Delete devices in the list that should not be imported at this time. 9. Document the CU#, Ldev# and ExG# 10. Press OK 11. If asked for SSID, see SSID-table in appendix A. 12. Press Apply OK Set path parameters If you have just added new paths between the XP and the EVA you need to adjust some parameters that have impact on the paths behaviour. 1. 2. 3. 4. 5. 6. 7. Log in to Remote Web Console Go to Modify Mode Go to External Storage Path operations Choose External Subsystem Mark the EVA where the new paths resides Right click on the WWN that the path goes to in the right pane Change WWN Parameter Set parameters to Qdepth for external LU (2-128) = 32 I/O TOV (5-240) = 15s (4 paths) I/O TOV 5(240) = 30s (2 paths) Path Blockade Watch (5-180) = 180s 8. Press OK 9. Press Apply 10. Press OK

Step 5: - Save LVM config files from every volume group thats being migrated. This must be run from the node owning the the volume group. Copy map files to the other node so that both nodes have all map files.
# vgexport -m /var/tmp/vg01.map -s -p -v /dev/vg01 Beginning the export process on Volume Group "/dev/vg01". vgexport: Volume group "/dev/vg01" is still active. /dev/dsk/c8t0d1 # vgexport -m /var/tmp/vg02.map -s -p -v /dev/vg02 Beginning the export process on Volume Group "/dev/vg02". vgexport: Volume group "/dev/vg02" is still active. /dev/dsk/c8t0d2

- Document volume groups device files on both nodes

# ll /dev/*/group crw-r----1 root crw-rw-rw1 root crw-rw-rw1 root sys sys sys 64 0x000000 Sep 12 00:24 /dev/vg00/group 64 0x010000 Sep 13 18:02 /dev/vg01/group 64 0x020000 Sep 13 18:03 /dev/vg02/group

- Check what device file is used for the cluster lock disk
# cmgetconf v c cluster_name /etc/cmcluster/cmclconfig.ascii # more /etc/cmcluster/cmclconfig.ascii

32

MIGRATION PROCEDURE
Step 6: - Shutdown any application using the file systems being migrated but leave the cluster running.
# cmhaltpkg v seldoraXXX # cmviewcl

- Export volume groups

# vgexport /dev/vg01 # vgexport /dev/vg02

- Verify volume groups exported OK

# strings /etc/lvmtab /dev/vg00 /dev/dsk/c3t2d0s2

(output should only show volume groups NOT being migrated) Step 7: Change zoning so that the servers no longer sees the EVA. It shall only see the XP. Step 8: From the XP present the imported LDEVs to the servers with the correct LUN number. The same LUN number that was used when the disk was presented from the EVA. If the same LUN-nr is not used, the OS might reorder the disks as mentioned in Step 5. Add Volume to a Host group 1. Log in to Remote Web Console 2. Go in to Modify Mode 3. Go to LUN Manager LU Path and Security 4. Expand the Fibre catalog 5. Expand the port where your host is/will be connected and choose the host group of the host. 6. Mark the LDEVs that are to be added to the host 7. Mark the LUN numbers that are going to be mapped with that device. 8. Click on Add LU Path 9. Review your changes and click ok 10. Click on Apply Step 9: Import of volumes shall be done on both nodes. Complete this step on this node before starting it on the other node. - Identify new devices
# ioscan disk disk disk disk -fC 12 14 13 15 disk |grep -i open 0/3/1/0.4.0.93.0.0.1 0/3/1/0.4.0.93.0.0.2 0/4/1/0.3.0.101.0.0.1 0/4/1/0.3.0.101.0.0.2 sdisk sdisk sdisk sdisk CLAIMED CLAIMED CLAIMED CLAIMED DEVICE DEVICE DEVICE DEVICE HP HP HP HP OPEN-V OPEN-V OPEN-V OPEN-V

- Create device files for new LUNs

# insf -e -H 0/3/1/0 insf: Installing special files for sctl instance 11 address 0/3/1/0.4.0.90.0.0.0 . . # insf -e -H 0/4/1/0 insf: Installing special files for sctl instance 10 address 0/4/1/0.3.0.97.0.0.0 . .

33

- Create device files for removed volume Groups. Verify that these files have the same minor number as before and that it doesnt exist device files with same minor number.
# mkdir /dev/vg01 # mkdir /dev/vg02 # mknod /dev/vg01/group c 64 0x010000 # mknod /dev/vg02/group c 64 0x020000 # ll /dev/*/group crw-r----1 root sys 64 0x000000 Sep 12 00:24 /dev/vg00/group crw-rw-rw1 root sys 64 0x010000 Sep 14 19:59 /dev/vg01/group crw-rw-rw1 root sys 64 0x020000 Sep 14 19:59 /dev/vg02/group

- Import and activate the volume groups

# vgimport -m /var/tmp/vg01.map -s -v /dev/vg01 Beginning the import process on Volume Group "/dev/vg01". Logical volume "/dev/vg01/lvol1" has been successfully created with lv number 1. Volume group "/dev/vg01" has been successfully created. # vgimport -m /var/tmp/vg02.map -s -v /dev/vg02 Beginning the import process on Volume Group "/dev/vg02". Logical volume "/dev/vg02/lvol1" has been successfully created with lv number 1. Volume group "/dev/vg02" has been successfully created. # vgchange -a e /dev/vg01 Activated volume group Volume group "vg01" has been successfully changed. # vgchange -a e /dev/vg02 Activated volume group Volume group "vg02" has been successfully changed.

- Split the i/o load over different HBAs, Fabrics, and XP cluster. Remove the primary path for every second volume group and add it again.
# vgdisplay -v /dev/vg02 |grep -i "PV Name" PV Name /dev/dsk/c10t0d2 PV Name /dev/dsk/c11t0d2 Alternate Link # vgreduce /dev/vg02 /dev/dsk/c10t0d2 Device file path "/dev/dsk/c10t0d2" is an primary link. Removing primary link and switching to an alternate link. Volume group "/dev/vg02" has been successfully reduced. Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf # vgextend /dev/vg02 /dev/dsk/c10t0d2 Volume group "/dev/vg02" has been successfully extended. Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf # vgdisplay -v /dev/vg02 |grep -i "PV Name" PV Name /dev/dsk/c11t0d2 PV Name /dev/dsk/c10t0d2 Alternate Link

- Backup volume group configuration

# vgcfgbackup /dev/vg01 Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf # vgcfgbackup /dev/vg02 Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf

- Deactivate volume group

# vgchange -a n /dev/vg01 Activated volume group Volume group "vg01" has been successfully changed. # vgchange -a n /dev/vg02 Activated volume group Volume group "vg02" has been successfully changed.

- Repeat above steps on the other node. - Start the package and verify
# cmrunpkg v n selduxXX seldoraXXX

If the volume being migrated is the cluster lock disk following procedure must be done. - Edit cluster config file with the new device file for the cluster lock disk. Pay attention to that the cluster lock disk has two entries in below file.
# vi /etc/cmcluster/cmclconfig.ascii

34

- Check if cluster config is correct and ready for compilation.

# cmcheckconf v C /etc/cmcluster/cmclconfig.ascii

- Shutdown the complete cluster after shutdown of packages.

# cmhaltpkg v seldoraXXX # cmhaltcl v # cmviewcl

- Compile a new cluster.

# cmapplyconf v C /etc/cmcluster/cmclconfig.ascii

Step 10: - Start Cluster/Packages

# cmruncl v # cmviewcl

POST PROCEDURE
Step 11: Un-present the virtual disks in the EVA so that the server no longer can see them. The presentation to the XP shall remain.

END of HP-UX Cluster migration

35

Migration using Tiered Storage Manager

In order to migrate a volume from an external volume to an internal volume or vice versa with Tiered Storage Manager, the volumes need to be of the same size (amount of blocks) and of the same emulation (OPEN-V). To create new volumes to match other volumes:

Create a new internal volume in the XP

1. 2. 3. 4. Log in to Remote Web Console Go in to Modify Mode Go to Volume Manager Customized Volume Check the size of the External Volume you want to migrate a) Expand the External catalog b) Find the device and expand the device catalog c) Change to Block in the upper right corner of the right pane d) Click on the device and see the size of the device (in Blocks) in the right pane 5. Expand the Internal catalog 6. Choose the RAID group you want to use and expand the boxes 7. Click on the RAID group 8. Right click and choose Install CV ALWAYS use OPEN-V Change Capacity Unit to Block Specify capacity (Amount of Blocks of the external device) and number 9. Click on set 10. Click on Next 11. Mark the device in the left pane and mark first available ldev in the right pane (Start top to the left in matrix , change CU# if all is grey) 12. Document the LDEV# 13. Click Next 14. If asked for SSID, see the SSID-matrix in appendix 15. Click Next 16. Click OK 17. Click Apply

Migrating existing volumes

1. 2. 3. 4. Log in to Command View Advanced Edition Under Explorer pane - Choose Subsystems Under Subsystems Pane Choose the XP you want to use In the upper right side of the Subsystems pane press Refresh Are you sure you want to execute Refresh Storage subsystem OK

36

5. Under Dashboard pane click on GO for TSMgr 6. Under Storage Domains choose the XP you want to work with 7. In the upper right corner click on Refresh Domain Are you sure that you want to refresh. OK

8. Go Migration Wizard press Next 9. Choose Storage Domain (Which XP)

If the devices you want to migrate, not already exists in a migration group, create a new Migration group. a) Press Create MG b) Enter name of Migration Group

37

c)

Press Add Volumes Here is a number of options to find your devices. If source volumes reside in XP: Under Attribute choose Port/HSD Under Value choose the Port/host group the devices you want to migrate resides in. If source volumes resides in EVA Under Attribute choose subsystem choose your EVA d) Press Search e) Mark the devices you want as source in the right pane and click ok. f) Press OK to move on, or add volumes to add more devices. g) Press Close

10. Choose migration Group and click next. If the devices you want to migrate to, not already exists in a Storage Tier, create a new Storage Tier. a) Press Create Tier b) Enter name Storage Tier c) Under Attribute choose subsystem d) Under Value choose the XP or EVA where the target devices are located. e) Option if needed, add extra filter by clicking the + f) Press Search g) Check that you have target devices that match the source devices. h) Press Close i) j) k) l) Mark for what storage tier to use. Click Next Check that Status are blue, and when you place the mouse on it, it says move Press Next

m) Enter Task Description and Notification Email n) Click Confirm and Finish 11. To start a) b) c) d) migration (if not chosen to be done immediately) In the Explorer pane Click on Tasks Mark the migration/migrations that you want to start. Press Execute Tasks Press Close

Check status of migration. Detailed info if you click on Task ID After migration is completed, delete the Migration group and Storage Tier.

You need to have the devices of the same Size, Emulation in both groups to be able to match the volumes.

38

Migration using Business Copy XP

In order to migrate a volume from an external volume to an internal volume or vice versa with Tiered Storage Manager, the volumes need to be of the same size (amount of blocks) and of the same emulation (OPEN-V). To create new volumes to match other volumes:

Create a new internal volume in the XP

18. Log in to Remote Web Console 19. Go in to Modify Mode 20. Go to Volume Manager Customized Volume 21. Check the size of the External Volume you want to migrate e) Expand the External catalog f) Find the device and expand the device catalog g) Change to Block in the upper right corner of the right pane h) Click on the device and see the size of the device (in Blocks) in the right pane 22. Expand the Internal catalog 23. Choose the RAID group you want to use and expand the boxes 24. Click on the RAID group 25. Right click and choose Install CV ALWAYS use OPEN-V Change Capacity Unit to Block Specify capacity (Amount of Blocks of the external device) and number 26. Click on set 27. Click on Next 28. Mark the device in the left pane and mark first available ldev in the right pane (Start top to the left in matrix , change CU# if all is grey) 29. Document the LDEV# 30. Click Next 31. If asked for SSID, see the SSID-matrix in appendix 32. Click Next 33. Click OK 34. Click Apply Migrating (Copying) Volumes 1. Setup Raid Manager on the server that you wish to control the Business Copy Pair with. (See Raid Manager documentation for specifics) 2. Create the pair by issuing paircreate g GROUP d DEVICE -vl 3. Wait for the pairs to complete the initial copy 4. Stop your application 5. Suspend the pair by issuing pairsplit -S g GROUP d DEVICE 6. Wait for the final updates to the SVOL 7. Move your application pointer to point to the new device (The SVOL in this case) 8. Start your application

39

Expanding a LUN/LUSE online (only windows supported)

When expanding a LUN/LUSE online the host windows host has to have host mode 2C. After the expansion in the XP you need to use diskpart in the same way as you use it when expanding a disk from the EVA.

Expanding a LUN to a LUSE

1. 2. 3. 4. 5. Log in to Remote Web Console Go to Modify Mode Go to Volume Manager LUN Expansion Expand LKDC 00 Click on the CU# where the device you want to expand belongs to. (LKDC:CU:LDEV)

6. Select the LDEV you want to expand 7. Choose LDEV/LDEVS that you want to expand with from the bottom right pane and add to the left. If no LDEVs are free in that CU, choose a higher number. NEVER expand an Internal Volume with an External Volume or vice versa. The # after the LDKC:CU:LDEV marks that it is an External Volume. Or you can see it by the PG (Parity Group). All that starts with an E is an External Volume. Click Apply - Ok

40

Appendix A - SSID
SSID is a number that comes from the Mainframe environment. In the Open-environment we dont use it normally. We only use the SSID setting in some Continuous Access configurations (Without the CU Free option). But the SSID still needs to be defined in every case. Start at giving CU# the SSID number 0004 and then just keep on upwards Example CU SSID table CU 00 CU 01 CU 02 CU 03 CU 04 CU 05 SSID 0004 SSID 0005 SSID 0006 SSID 0007 SSID 0008 SSID 0009

The table continues linear in hexadecimal.

41

Appendix B XP operations
Import the device to the XP via Auto (all devices mapped to an XP-port)
This is used if you want to add ALL devices that are mapped to the XP at the same time. 1. 2. 3. 4. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close.

5. 6. 7. 8.

Right click Subsystem Add Volume (Auto) (Default Policy) Choose EVA Port (on XP) WWN (port on EVA) Right click on WWN and add path (Repeat for redundancy) Press ok

Import the device to the XP via Manual (Select devices mapped to an XP-port)
When youre importing devices from an EVA, not configured as External Storage since before. To spread the load over multiple paths, repeat the procedure 4 times (same as the amount of paths to the EVA) and use step 5a-5f all 4 times and add the paths in different order to give them different priorities. You might only import 1 disk at each time, depending on how many you are going to import. Notice that the LUN# in the EVA is in decimal, and in XP it appears as hexadecimal (characteristics of the device) 1. 2. 3. 4. 5. Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. If the EVA is not configured as External Storage a) Right click Subsystem Add Volume (Manual) (Default Policy)

42

b) Choose EVA Port (on XP) WWNs (ports on EVA) c) Right click on WWN and add paths (Repeat for each XP-port connected the that EVA)

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!! Cache mode disable Inflow control disable CLPR 2 If the EVA is already configured as External Storage k) Expand the EVA you wish to import devices from l) Right click one of the Path Group # - Add Volume (Manual) (Default Policy). Try to import devices equally to the Path Groups to spread the load. 6. Right click again on devices LDEV Mapping (Auto) 7. Mark first available Ldev (Start top to the left in matrix, change CU# if all table is grey).

43

8. Delete devices in the list that should not be imported at this time. 9. Document the CU#, Ldev# and ExG# 10. Press OK 11. If asked for SSID, see SSID-table in appendix A. 12. Press Apply OK

Set path parameters

If you have just added new paths between the XP and the EVA you need to adjust some parameters that have impact on the paths behaviour. 1. 2. 3. 4. 5. 6. 7. Log in to Remote Web Console Go to Modify Mode Go to External Storage Path operations Choose External Subsystem Mark the EVA where the new paths resides Right click on the WWN that the path goes to in the right pane Change WWN Parameter Set parameters to Qdepth for external LU (2-128) = 32 I/O TOV (5-240) = 15s (4 paths) I/O TOV 5(240) = 30s (2 paths) Path Blockade Watch (5-180) = 180s 8. Press OK 9. Press Apply 10. Press OK

Create a host group for the new host

1. 2. 3. 4. 5. 6. Log in to Remote Web Console Go in to Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Do not use default host group number 00 Mark and right click on the XP-port you where you want to create the host group Add New Host Group. 7. Insert Group Name 8. Choose Host mode 00 Linux (most distributions, but check with support matrix)

44

 01 VMware 08 HPUX 2C Windows 9. In case of VMware Click Option and mark Option 19 10. Press OK 11. Right click on the new group (in blue) and choose Add New WWN 12. Choose the hosts WWM from the dropdown list or enter manually 13. Enter a Nickname 14. Press Ok 15. Repeat the steps from step 6 for adding alternate paths to host. 16. Press Apply

Create a new Gold volume in the XP (internal XP-disk)

1. 2. 3. 4. Log in to Remote Web Console Go in to Modify Mode Go to Volume Manager Customized Volume Check the size of the External Volume you want to migrate i) Expand the External catalog j) Find the device and expand the device catalog k) Change to Block in the upper right corner of the right pane l) Click on the device and see the size of the device (in Blocks) in the right pane 5. Expand the Internal catalog 6. Choose the RAID group you want to use and expand the boxes 7. Click on the RAID group 8. Right click and choose Install CV ALWAYS use OPEN-V Change Capacity Unit to Block Specify capacity (Amount of Blocks of the external device) and number 9. Click on set 10. Click on Next 11. Mark the device in the left pane and mark first available Ldev in the right pane (Start top to the left in matrix , change CU# if all is grey) 12. Document the LDEV# 13. Click Next 14. If asked for SSID, see the SSID-matrix in appendix 15. Click Next 16. Click OK 17. Click Apply

Add Volume to a Host group

1. 2. 3. 4. 5. 6. 7. 8. Log in to Remote Web Console Go in to Modify Mode Go to LUN Manager LU Path and Security Expand the Fibre catalog Expand the port where your host is/will be connected and choose the host group of the host. Mark the LDEVs that are to be added to the host Mark the LUN numbers that are going to be mapped Click on Add LU Path

45

9. Review your changes and click ok 10. Click on Apply

Expanding a LUN to a LUSE

1. 2. 3. 4. 5. Log in to Remote Web Console Go to Modify Mode Go to Volume Manager LUN Expansion Expand LKDC 00 Click on the CU# where the device you want to expand belongs to.

6. Select the LDEV you want to expand 7. Choose LDEV/LDEVS that you want to expand with from the bottom right pane and add to the left. If no LDEVs are free in that CU, choose a higher number. NEVER expand an Internal Volume with an External Volume or vice versa. The # after the LDKC:CU:LDEV marks that it is an External Volume. Or you can see it by the PG (Parity Group). All that starts with an E is an External Volume. 8. Click Apply - Ok

46

Appendix C - div
Numbers
Maximum size of 1 internal XP device with 146GB disks, Raid 7+1 = 959731,500 MB Maximum size of an EVA device = 4292870144 Blocks 1GB i EVA = 1024MB i XP (2097152 Blocks)

Do not use Host group 0

When having the secure enable set on a specific port, only the hosts which have WWNs presented in each specific host group can see the LUNs in those host groups. But if by mistake the secure function should be set to disable, all hosts connected to that specific port will be able to see all LUNs in host group 0. Therefore, never use the default host group 0.

47

Appendix D Importing disks from EVA5000

Import the device to the XP, Manual (Select devices mapped to an XP-port) Use this section when youre importing devices from an EVA5000 with a code of 3.x and the XP has the code of 60.01.68 or earlier. The XP cant see the disks from both controllers at the same time. Therefore we need to configure paths to one controller at a time. There is an advantage of presenting many disks at the same time, in order to not use a large number of path groups. To spread the load over multiple paths, Depending on how many disks you want to present at the same time, there are different ways to go. As this is an open area of improvement, please contact an HP XP representative for further details regarding this issue.

Notice that the LUN# in the EVA is in decimal, and in XP it appears as hexadecimal (characteristics of the device)

All devices that you would like to have in the same path group needs to be owned by the same EVA controller when you import the devices, and need to be imported in one configuration operation. For each virtual disk in the EVA, the current owning controller can be seen under the presentation-tab in Command view EVA.

1. 2. 3. 4. 5.

Log in to Remote Web Console. Go in to Modify Mode Go to External Storage Volume Operation Right click Subsystem Check Edit Policy, change if needed, then close. a) Right click Subsystem Add Volume (Manual) (Default Policy) b) Choose EVA Port (on XP) WWNs (ports on EVA) c) Right click on WWN and add paths. Repeat for each XP-port connected to the EVA controller currently owning the LUN/LUNs. You can determine the WWNs that belong to the same EVA controller by looking at the last digit in the WWN. 8 & 9 goes to one controller and C & D goes to the other controller.

48

d) Press ok e) Mark devices to import f) Right click Set External Volume Parameter Choose ExG# depending on which EVA ALWAYS choose OPEN-V !!! Cache mode disable Inflow control disable CLPR 2 Number of LDEVs MUST be set to 1

13. Right click again on devices LDEV Mapping (Auto) 14. Mark first available ldev (Start top to the left in matrix, change CU# if all table is grey).

15. Delete devices in the list that should not be imported at this time. 16. Document the Characteristic#, Ldev# and ExG# 17. Press OK

49

18. If asked for SSID, see SSID-table in appendix A. 19. Press Apply OK 20. If the EVA virtual disk/disks are currently in use by a host server, use the server multi-pathing software to change the active EVA controller for the virtual disk. 21. If the EVA virtual disk/disks are not used by a server yet, use Command View EVA to change the owning controller for the virtual disk/disks. 22. Select the path group you just created. 23. Right click on WWN and choose Configure Cross-subsystem paths 24. Add the remaining paths to the LUN/LUNs the same way as in step 5c 25. Click Ok 26. Click Apply

50