This procedure describes how to convert an existing server that boots from its local drive to a SAN-booted server. After the server is converted, the server’s local hard drive is not used to boot the server to its OS. In fact, the drive must be completely disabled. No local disks should be available as boot devices when the conversion is complete.
To convert an existing server that locally boots from hard disk to a SAN boot system, you will perform various parts of this procedure on the server and Oracle’s Fabric Interconnect.
If multiple partitions are created on the disk, capturing the image is more complex. You will have to modify the tools listed below to capture both the small boot partition where the BootMGR and boot configuration database (BCD) exist as well as capturing the partition where the OS is installed.
For this procedure, assume that the SAN LUN is h:.
Do not attempt to install the OS to the SAN LUN.
If needed, update the HCA firmware and Option ROM to the correct version for your hardware type. See, Confirm the OS Version.
add server-profile webapps1
The LUN should be the appropriate size to contain the OS and applications you intend to install.
add vhba vh1.webapps1 8/1
set server-profile webapps1 connect webserver1@Director1:ServerPort18
diskshadow.exe /s backupscript.script
When this script runs, it captures the local disk and places a copy onto the LUN.
SET CONTEXT PERSISTENT NOWRITERS SET VERBOSE ON BEGIN BACKUP ADD VOLUME C: ALIAS systemVolumeShadow CREATE EXPOSE %systemVolumeShadow% p: EXEC w2k8_clone_diskshadowImage.cmd END BACKUP
imagex.exe /CAPTURE /boot P: c:\SanBoot.wim "Windows Server 2008 R2" format.com h: /q /V:Sanboot /y bootsect.exe /nt60 h: /force imagex.exe /APPLY c:\SanBoot.wim 1 H: /VERIFY diskshadow.exe /s removescript.script call FixBCD.cmd call FixBootSector-2k8.cmd call fixregistry.cmd
delete h:\Boot\BCD
bcdboot.exe c:\Windows /s h:
This executable creates a new BCD on the LUN and forces the new configuration information into the new BCD.
bcdedit.exe -store h:\boot\bcd /set {bootmgr} device boot bcdedit.exe -store h:\boot\bcd /set {default} device boot bcdedit.exe -store h:\boot\bcd /set {default} osdevice boot
When this file is executed, it updates the boot database with the new boot partition information.
bootsect.exe /nt60 h: /force
When this file is executed, it places the boot sector on the new LUN.
reg.exe load hklm\sanboot h:\windows\system32\config\system reg.exe delete hklm\sanboot\mounteddevices /va /f reg.exe unload hklm\sanboot
When this file is executed, it removes any previously assigned drive letters. If the old drive letters are not removed, the system will boot to the h: drive. If the local disk controller had more than just the boot information and the OS, any additional drive letters will have to be reassigned once the server boots to SAN.
delete shadows exposed p:
Use the set server profile name san-boot VHBA WWPN LUN ID command.
set server-profile webapps1 san-boot vh1.webapps1 11:22:33:44:55:66:77:88 1
If disabling the on-board storage is not preferable, you can remove the physical hard drive(s) from the server, but be aware that some array controllers behave unpredictably if the drives are removed.
The next time the server boots, it uses the bootable VHBA.