Veritas InfoScale 7.3.1 Installation and Upgrade Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.3.1)
Platform: Windows
  1. Preinstallation and planning
    1.  
      About the Veritas InfoScale product suite
    2.  
      Supported hardware and software
    3.  
      Disk space requirements
    4.  
      Installation requirements
    5.  
      Requirements for installing InfoScale Storage in a Microsoft Failover Cluster
    6.  
      Recommendations and best practices
    7. About InfoScale licenses
      1.  
        Licensing notes
      2.  
        vxlicrep command
  2. Installing the Veritas InfoScale products
    1.  
      About installing the InfoScale products
    2.  
      About the co-existence of InfoScale products
    3.  
      Installing the server components using the installation wizard
    4.  
      Applying the selected installation and product options to multiple systems
    5.  
      Installing the server components using the command-line installer
    6.  
      Parameters for Setup.exe
    7.  
      Available product options and supported DMP DSMs
    8.  
      Registering the InfoScale Storage resource DLLs
    9.  
      Installing the client components
  3. Upgrading to InfoScale products
    1. Preparing the systems for an upgrade
      1.  
        About the supported upgrade paths and the supported minimum product versions
      2.  
        General preparations
      3.  
        Recommendations and considerations for product upgrade
    2. Performing the product upgrade
      1. Upgrading SFW or SFW Basic in a non-clustered environment
        1.  
          Preparing the primary site for upgrade in a non-clustered SFW environment
      2. Upgrading SFW or SFW Basic in a Windows Server Failover Cluster environment
        1.  
          Preparing the secondary site for upgrade in a Windows Server Failover Cluster environment
        2.  
          Failing over application to secondary site
        3.  
          Preparing the primary site for upgrade in a Windows Server Failover Cluster environment
      3.  
        Upgrading VCS
      4. Upgrading SFW HA
        1.  
          Preparing the primary and secondary sites for upgrade in a Volume Replicator environment
        2.  
          Associating the replication logs and starting the replication
        3.  
          Re-enabling Volume Replicator in a VCS cluster
      5.  
        Upgrading DMP
    3.  
      About transitioning between the InfoScale products
  4. Performing the post upgrade tasks
    1.  
      Deployment scenarios and applicable post upgrade tasks
    2.  
      Re-enabling Volume Replicator in a non-clustered environment
    3.  
      Re-enabling Volume Replicator in a Microsoft failover cluster environment
    4.  
      Reconnecting DMP DSM paths after the upgrade
    5.  
      Reconfiguring the Veritas InfoScale Messaging Service
    6.  
      Importing the configured rules
    7.  
      Upgrading clusters for stronger security
    8.  
      Reinstalling the custom agents
    9.  
      Including custom resources
  5. Administering the InfoScale product installation
    1.  
      Adding or removing product options
    2.  
      Managing InfoScale licenses
    3.  
      Repairing an InfoScale product installation
    4.  
      About reinstalling InfoScale products
  6. Uninstalling the InfoScale products
    1.  
      About uninstalling the InfoScale products
    2.  
      Uninstalling the InfoScale products using the installation wizard
  7. Performing application upgrades in an InfoScale environment
    1. Upgrading Microsoft SQL Server
      1. Upgrading to later versions of SQL Server
        1.  
          Upgrading SQL Server on the first cluster node
        2.  
          Upgrading SQL Server on additional failover nodes
        3.  
          Creating the new SQL Server service group
    2. Upgrading Oracle
      1.  
        Performing the post upgrade tasks
      2.  
        Associating the updated Oracle database with the listener
      3. Configuring the Oracle database and listener to use the virtual IP address
        1.  
          Setting the dispatchers parameter in PFILE
        2.  
          Setting the dispatchers parameter in SPFILE
      4.  
        Configuring Oracle and listener services
      5.  
        Modifying the ServiceName attribute for the netlsnr resource
    3. Upgrading application service packs in an InfoScale environment
      1. Upgrading the Exchange Server service packs
        1.  
          Upgrading Exchange Server 2010 to a service pack
      2. Upgrading the SQL Server service packs
        1.  
          Upgrading SQL Server 2012 or SQL Server 2014 or SQL Server 2016 to a service pack
      3.  
        Upgrading SharePoint Server 2010 to a service pack
  8. Appendix A. Services and ports
    1.  
      InfoScale ports and services
  9. Appendix B. Migrating from a third-party multi-pathing solution to DMP
    1.  
      Migrating from EMC PowerPath
    2. Migrating from Hitachi Dynamic Link Manager (HDLM)
      1.  
        Uninstalling HDLM in a non-clustered environment
      2.  
        Uninstalling HDLM in a clustered (MSCS or VCS) environment
    3.  
      Configuring DMP for Active/Active load balancing in a cluster

Configuring the Oracle database and listener to use the virtual IP address

All databases and listeners configured must use the same virtual IP. Update the Oracle files to set the virtual IP address.

Setting the virtual IP address involves the following tasks:

  • Creating a virtual IP address.

  • Verifying the initialization file settings.

  • Updating the Oracle configuration files.

Use the following procedures to configure the Oracle database and listener.

To create a virtual IP address

  1. Open the Network Connections.
  2. Right-click the public network connection to be used and click Properties.
  3. Select Internet Protocol (TCP/IP) and click Properties.
  4. Click Advanced.
  5. In the IP Settings tab, click Add to add a virtual IP address and subnet mask.

To verify the initialization file settings, if a PFILE is used

  1. Open the Registry Editor.

    From the Start menu, choose Run. In the Open field, enter regedit and click OK.

  2. Double-click the ORA_SID_PFILE registry key at HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME_ID\.

    The variable SID represents the database instance.

  3. Verify that the Value data field specifies the correct path at which the initialization file, init.ora, is located.

To verify the initialization file settings, if an SPFILE is used

  1. Run sqlplus.exe.
  2. Connect to the database.
  3. Verify the following query returns the correct path of the SPFILE.
    select value from v$parameter where name = 'spfile'

To update the Oracle configuration files

  1. In the listener.ora and tnsnames.ora files, change the host name for all the TCP protocol address databases to the virtual IP address that you created.

    Replace

    HOSTNAME=machine_name
    					

    with

    HOSTNAME=virtual_IP_address
    					
  2. In the initialization file, change the dispatchers parameter.

    Oracle requires an initialization file, a PFILE or an SPFILE, to start database instances. Choose the appropriate reference depending on the initialization file you use.

  3. Restart the Oracle and listener services.