d.
Collect all support data of the original storage subsystem.
e.
In the host servers, stop all programs, services, and processes that access the
logical drives that are defined in the migrated hard disk drives. Also, ensure
that no programs, services, or processes that write data to the logical drives
are running in the background.
f.
Unmount the file systems to flush I/O from the server cache to disks.
Note:
1)
If you are using a Windows operating system, remove the drive letter or
the mount points of the drive-to-LUN map definitions, instead of
unmounting the file systems.
2)
See your operating-system documentation for information about the file
system unmount procedure.
g.
If the original subsystem contains FDE drives that were configured as part
of a secured array, save the storage subsystem security (lock) key to unlock
the drives. Without this key, the controllers cannot unlock the
security-enabled FDE drives. Save the key in a safe location and not on the
logical drives that are mapped from the original storage subsystem. Use the
Validate Security key
menu function in the storage manager subsystem to
validate the saved security key file and associated pass-phrase. The storage
subsystem security (lock) key must be saved with both local or external
FDE key management policies.
h.
Perform an incremental backup of the data that was changed since the full
backup that you performed in step 1h on page 47.
i.
Ensure that the environmental service modules (ESMs) and hard disk drives
in the original storage subsystem are updated to the latest firmware version.
To download the latest firmware version, go to http://www.ibm.com/
systems/support/storage/disk/.
4.
Upgrading the controller firmware.
To upgrade the controller firmware, complete the following steps:
a.
Use the following flowcharts to determine the firmware version that is
required in the new storage subsystem. To download the latest firmware
level, go to http://www.ibm.com/systems/support/storage/disk/.
Note:
The controller firmware is normally listed as either xx.yy.zz.aa or
xxyyzzaa, where xx.yy or xxyy is the controller firmware version used for
compatibility checking. If the first x is 0, it might not be identified. For
example, 08.20.09.00 is the same as 08.20.09.00. The firmware version that is
used for compatibility checking in this example is 8.20.
48
IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Summary of Contents for System Storage DCS Series
Page 89: ......