Migrating existing SAN boot images

If you have a host that runs the Windows® 2000 Server, Windows Server 2003, or Windows Server 2008 operating system, and existing SAN boot images that are controlled by storage controllers, you can migrate these images to image-mode virtual disks (VDisks) that are controlled by the SAN Volume Controller.

1. If the existing SAN boot images are controlled by an IBM® storage controller that uses SDD as the multipathing driver, you must use SDD v1.6 or higher. Run the SDD command datapath set bootdiskmigrate 2145 to prepare for image migration. See the IBM System Storage® Multipath Subsystem Device Driver User's Guide for more information about this command.
2. Shut down the host.
3. Perform the following configuration changes on the storage controller:
   1. Remove all the image-to-host mappings from the storage controller.
   2. Map the existing SAN boot image and any other disks to the SAN Volume Controller.
4. Zone one port of each host bus adapter (HBA) to one of the SAN Volume Controller ports that is associated with the I/O group for the target image-mode VDisk.
5. Perform the following configuration changes on the SAN Volume Controller:
   1. Create an image-mode VDisk for the managed disk (MDisk) that contains the SAN boot image. Use the MDisk unique identifier to specify the correct MDisk.
   2. Create a host object and assign it to the HBA port that you zoned to the SAN Volume Controller port in step 4.
   3. Map the image mode VDisk to the host. For example, you might map the boot disk to the host with SCSI LUN ID 0.
   4. Map the swap disk to the host, if required. For example, you might map the swap disk to the host with SCSI LUN ID 1.
6. Change the boot address of the host by performing the following steps:
   1. Restart the host and open the BIOS utility of the host during the booting process.
   2. Set the BIOS settings on the host to find the boot image at the worldwide port name (WWPN) of the node that is zoned to the HBA port.
7. Boot the host in single-path mode.
8. Uninstall any multipathing driver that is not supported for SAN Volume Controller hosts that run the applicable Windows Server operating system.
9. Install a supported multipathing driver.
10. Restart the host in single-path mode to ensure that the supported multipath driver was properly installed.
11. Zone each HBA port to one port on each SAN Volume Controller node.
12. Add HBA ports to the host object that you created in step 5.b.
13. Configure the HBA settings on the host by using the following steps:
    1. Restart the host and open the host's BIOS utility during the booting process.
    2. Ensure that all HBA ports are boot-enabled and can see both nodes in the I/O group that contains the SAN boot image. Configure the HBA ports for redundant paths.
    3. Exit the BIOS utility and finish booting the host.
14. Map any additional VDisks to the host as required.