Veritas InfoScale™ 7.4.1 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- About InfoScale licenses
- Installing the Veritas InfoScale products
- Upgrading to InfoScale products
- Performing the post upgrade tasks
- Administering the InfoScale product installation
- Uninstalling the InfoScale products
- Performing application upgrades in an InfoScale environment
- Upgrading Microsoft SQL Server
- Upgrading Oracle
- Upgrading application service packs in an InfoScale environment
- Appendix A. Services and ports
- Appendix B. Migrating from a third-party multi-pathing solution to DMP
Available product options and supported DMP DSMs
Microsoft Failover Cluster and DMP DSMs are available as the selectable product options. These product options are available depending on the product being installed.
The Microsoft Failover Cluster option installs the SFW component that is required if you plan to configure a Microsoft Failover Cluster.
The following table provides details about whether or not the options are applicable for the respective product:
Table: InfoScale product options
Product | Microsoft Failover Cluster | DMP DSM |
---|---|---|
Veritas InfoScale Foundation | X | ✓ |
Veritas InfoScale Availability | X | X |
Veritas InfoScale Storage | ✓ | ✓ |
Veritas InfoScale Enterprise | X | ✓ |
The following table provides a list of the available DMP DSMs.
Table: List of available DSMs
DMP device-specific modules (DSMs) |
|
For the latest information about the supported DSMs, refer to the hardware compatibility list (HCL) at:
https://sort.veritas.com/documents
Do not use a DMP DSM together with a third-party DSM for the same array. Only one DSM at a time can claim the LUNs in an array. According to Microsoft Multipath I/O (MPIO) documentation, if multiple DSMs are installed, the Microsoft MPIO framework contacts each DSM to determine which is appropriate to handle a device. There is no particular order in which the MPIO framework contacts the DSMs. The first DSM to claim ownership of the device is associated with that device. Other DSMs cannot claim an already claimed device. Therefore, to ensure that the DMP DSM claims the LUNs of an array, no other DSM should be installed for that same array.
If you are upgrading the product using the product installer, do not clear the selection for the DSMs you want to remove. Clearing the default selection does not remove the installed DSMs.
To remove the DSMs, perform any one of the following:
Before you begin to upgrade the cluster, remove the required DSM, using the Windows Add or Remove Programs. Reboot the node and then perform the upgrade.
Upgrade the cluster and then use the Windows Add or Remove Programs to remove the DSM.
Upgrade the cluster and then navigate to %ALLUSERSPROFILE%\Veritas\MPIO\.
From the command prompt, run the following command:
instdsm.exe - u DSMName.inf
Note:
If you clear the default selection during the upgrade, you cannot remove the DSM using the Windows Add or Remove Programs. To remove the DSM in this case, you must run the command that is mentioned earlier.
If you are upgrading the product using CLI, you must specify the previously installed options in the OPTIONS parameter, else they will be uninstalled. To include the previously installed options in this parameter, either specify these options individually in the OPTIONS parameter or specify "Installed" in the OPTIONS parameter to upgrade all options (example: options="Installed,flashsnap" ).
If you install InfoScale Availability on a system where you have already installed Veritas InfoScale Storage and have configured Microsoft Failover Cluster, you must first unconfigure the Microsoft Failover Cluster and remove the SFW component for Microsoft Failover Cluster.
To unconfigure Microsoft Failover Cluster, refer to Microsoft documentation.
To remove the SFW component for Microsoft Failover Cluster, use Windows Add Remove Programs.
If you install InfoScale Storage on a system where you have installed InfoScale Availability, you cannot specify the Microsoft Failover Cluster option.