Before upgrading, you need to make sure that your systems meet the minimum product versions. You must also do some general preparation for the upgrade.
To upgrade to SFW or SFW HA 5.1 SP2, your system must have version 5.0RP1a or higher of SFW or SFW HA already installed. The previously installed version of SFW or SFW HA must meet this minimum product version, which the product installer checks before it upgrades.
Meeting the requirements:
If your current installation does not meet the minimum level required by the installer, you must manually apply the appropriate product upgrades to meet the minimum product level required before proceeding with the installer
It highly recommended to verify that your hardware configuration matches the Hardware Compatibility List (HCL):
The HCL contains a list of supported drivers and firmware for HBAs, disk arrays, and switches that are compatible with Storage Foundation.
The HCL also contains numerous footnotes regarding issues that are specific to certain hardware and configurations.
Please note, You can use the same license key to upgrade from 5.X to 5.1 SP2. If you are using an old version of Storage Foundation such as 4.X you need to obtain a different license key for SFW\HA5.1 SP2 . Ensure that you have already obtained all the require license before you start the upgrade.
Binary Installation Location:
It also recommended to ensure the following had been meet before the installation.
Reviewing the PATH Statement
In many environments, the PATH variable is limited to 1023 characters. Ensure that there is enough unused space within this variable to accommodate the any paths that are added by the SFW installation. A typical installation of SFW can add over 300 characters to this statement. If the statement already contains numerous paths, the SFW installation may not complete properly
Insufficient DCOM (Distributed Component Object Model) permissions will cause an installation of SFW to fail. Information about checking and configuring DCOM permissions can be found in the following article: http://support.veritas.com/docs/284474
· Log into a console session. Start any Remote Desktop sessions with the "console" switch or use different method such as ILO or KVM.
· Verify that Driver Signing is set to Ignore
· Run the installation from a local drive or disk