Veritas InfoScale 7.3.1 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- Installing the Veritas InfoScale products
- Upgrading to InfoScale products
- Preparing the systems for an upgrade
- Performing the product upgrade
- Upgrading SFW or SFW Basic in a non-clustered environment
- Upgrading SFW or SFW Basic in a Windows Server Failover Cluster environment
- Upgrading SFW HA
- 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
- Configuring the Oracle database and listener to use the virtual IP address
- 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
Requirements for installing InfoScale Storage in a Microsoft Failover Cluster
The following table lists the InfoScale requirements for installing InfoScale Storage, in an active Microsoft Failover Cluster.
These requirements are applicable in addition to the InfoScale product-specific installation pre-requisites, and must be satisfied on all the Microsoft Failover Cluster nodes, where you plan to install InfoScale Storage.
Table: InfoScale requirements for Microsoft Failover Cluster
One CD-ROM drive is accessible to the node on which you are installing InfoScale Storage.
The node has the required disk space available.
The required storage hardware is configured to access the shared storage. SCSI or Fibre channel host bus adapters (HBAs) can be used.
Three network adapters (two NICs exclusively for the private network and one for the public network) are available on each cluster node, and each private NIC is routed through a separate hub or switch to avoid single points of failure.
To prevent lost heartbeats on the private networks, and to prevent the Microsoft cluster from mistakenly declaring a system down, Veritas recommends disabling the Ethernet auto negotiation options on the private network adapters.
Static IP addresses are used for the public network and private network cards, and the DNS name resolution is configured for each node.
This is required if you plan to configure replication using VVR.
DNS and Active Directory Services are available and a reverse lookup zone exists in the DNS.
Refer to the Microsoft documentation for instructions on creating a reverse lookup zone.
Each cluster node is in the same Windows Server domain, and uses the same operating system version.
The user account has administrative privileges on the cluster nodes.