IBM XIV Storage System Copy Services and Migration

Finally, we can define the AIX host to the XIV as a host using the XIV GUI or XCLI. InExample 7-21 we use the XCLI to define the host and then add two HBA ports to that host.Example 7-21 Define Dolly to the XIV using XCLI>> host_define host=dollyCommand executed successfully.>> host_add_port fcaddress=10:00:00:00:c9:53:da:b3 host=dollyCommand executed successfully.>> host_add_port fcaddress=10:00:00:00:c9:53:da:b2 host=dollyCommand executed successfully.Once the zoning changes have been done and connectivity and correct definitions confirmedbetween XIV to ESS and XIV to AIX host, we take an outage on the volume group and relatedfile systems that are going to be migrated. In Example 7-22 we unmount the file system, varyoff the volume group, and then export the volume group. Finally, we rmdev the hdisk devices.Example 7-22 Removing the non-XIV file systemroot@dolly:/# umount /mnt/redbkroot@dolly:/# varyoffvg ESS_VG1root@dolly:/# exportvg ESS_VG1root@dolly:/# rmdev -dl hdisk3hdisk3 deletedroot@dolly:/# rmdev -dl hdisk4hdisk4 deletedroot@dolly:/# rmdev -dl hdisk5hdisk5 deletedIf the Dolly host no longer needs access to any LUNs on the ESS 800 we remove the SANzoning that connects Dolly to the ESS 800. In Example 7-18 on page 233 this was the zonecalled ESS800_dolly_fcs0.Chapter 7. Data migration 235