Veritas InfoScale 7.0 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- Installing the Infoscale products
- About installing Veritas InfoScale products
- About InfoScale products co-existence
- Installing the server components using the product installer
- Installing the server components using CLI
- Available product options and supported DMPW DSMs
- Registering InfoScale Storage resource DLLs
- Installing the client components
- Upgrading to InfoScale products
- Performing the post upgrade tasks
- Deployment scenarios and applicable post upgrade tasks
- Re-enabling Volume Replicator in a non-clustered environment
- Re-enabling Volume Replicator in a Windows Server Failover Cluster environment
- Reconnecting DMPW DSM paths after the upgrade
- Re-configuring the Veritas Scheduler Service
- Re-configuring the VxSAS service
- Importing the configured rules
- Upgrading the dynamic disk group version
- Reinstalling the custom agents
- Including custom resources
- Administering InfoScale product installation
- Uninstalling InfoScale products
- Performing application upgrades in an InfoScale environment
- Upgrading Microsoft SQL Server
- Upgrading SQL Server 2008 to SQL Server 2008 R2
- Preupgrade tasks for upgrading SQL Server 2008 to SQL Server 2008 R2 in a disaster recovery environment
- Upgrading SQL Server 2008 to SQL Server 2008 R2 on the first cluster node
- Upgrading SQL Server 2008 to SQL Server 2008 R2 on additional failover nodes
- Modifying the SQL Server 2008 service group configuration
- Deleting the SQL Server 2008 service group and creating the SQL Server 2008 R2 service group
- Upgrading to later versions of SQL Server
- Upgrading SQL Server 2008 to SQL Server 2008 R2
- Upgrading Oracle
- Upgrading application service packs in an InfoScale environment
- Upgrading Microsoft SQL Server
- Appendix A. Services and ports
- Appendix B. Migrating from 3rd party multi-pathing solution to Dynamic Multi-pathing
Installation prerequisites
Before you install an InfoScale product, you must ensure that all the systems satisfy the installation pre-requisites.
The following table lists the InfoScale product-specific installation pre-requisites:
Table: Installation pre-requisites
Pre-requisites | Veritas InfoScale Foundation | Veritas InfoScale Availability | Veritas InfoScale Storage | Veritas InfoScale Enterprise |
|---|---|---|---|---|
Spyware monitoring and removal software is disabled | ✓ | ✓ | ✓ | ✓ |
The ports and services that are used during installation for both, inbound and outbound communication are enabled For a list of required ports and services, | ✓ | ✓ | ✓ | ✓ |
Three network adapters are available | X | ✓ | X | ✓ |
Minimum one IP address that is not assigned by Dynamic Host Configuration Protocol (DHCP) is available | X | X | ✓ | ✓ |
At least two IO paths from the server to the storage array for load balancing | ✓ | X | ✓ | ✓ |
Microsoft Failover Cluster is configured (Applicable only if you plan to configure a Microsoft Failover Cluster) | X | X | ✓ | X |
Microsoft .NET Framework 4.5 is installed (This requirement applies to both, server as well as client-only components.) Note: On a Windows Server 2008 R2 Server Core SP1 system, Microsoft .NET Framework 2.0 SP2 must be enabled before Microsoft .NET Framework 4.5 is installed. If you plan to install the client components on a Windows XP SP3 system, Microsoft .NET Framework 4.0 must be installed. | ✓ | ✓ | ✓ | ✓ |
Computer Browser Service is enabled | ✓ | ✓ | ✓ | ✓ |
Microsoft Windows Service (WMI) is activated | ✓ | ✓ | ✓ | ✓ |
No parallel installations, live updates, or Microsoft Windows updates are in progress | ✓ | ✓ | ✓ | ✓ |
Microsoft Visual C++ 2010 SP1 (x64) and the Microsoft Visual C++ 2010 SP1 (x86) re-distributable package is installed on the systems where you would want to launch the client consoles (VEA, Java Console, SCC etc) | ✓ | ✓ | ✓ | ✓ |
The user account is included as a domain user and has local administrators privileges on all the systems | ✓ | ✓ | ✓ | ✓ |
The user account has write permissions for the Active Directory objects corresponding to all the systems | ✓ | ✓ | ✓ | ✓ |
The user account has administrative privileges on all the systems to load and unload device drivers | ✓ | ✓ | ✓ | ✓ |
All systems are in the same domain | ✓ | ✓ | ✓ | ✓ |
Remote systems are accessible over the network and the user account has local administrative privileges to all the systems | ✓ | ✓ | ✓ | ✓ |
Trust relationship is set up for systems in different domains (Applicable only if you plan to configure a disaster recovery setup in which the systems at the primary site and the secondary site are in different domains) | X | ✓ | X | ✓ |
For IPv4 network, the required IP addresses are available | ✓ | ✓ | ✓ | ✓ |
For IPv6 network, the IP address configuration is "stateless automatic", the IP address format is "Global unicast" or "Unique localcast", and the prefix is advertised | ✓ | ✓ | ✓ | ✓ |
The system is a part of Windows Active Directory domain | ✓ | ✓ | ✓ | ✓ |
DNS Service is available | ✓ | ✓ | ✓ | ✓ |
The host has an HBA (host bus adapter) port for each path to the SAN switch | ✓ | X | ✓ | ✓ |
The host has one SCSI or fiber cable per host bus adapter port | ✓ | X | ✓ | ✓ |
In case of iSCSI, each host bus adapter port has a unique SCSI ID | ✓ | X | ✓ | ✓ |
Only one path is connected during product installation | ✓ | X | ✓ | ✓ |
The Windows Storport driver is installed | ✓ | X | ✓ | ✓ |
Correct hardware drivers for the DMPW DSMs are installed | ✓ | X | ✓ | ✓ |
The MPIO server feature is enabled | ✓ | X | ✓ | ✓ |
No other third-party DSMs are installed for the same array | ✓ | X | ✓ | ✓ |