Veritas InfoScale 7.0 Installation and Upgrade Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.0)
Platform: Windows
  1. Preinstallation and planning
    1. About the Veritas InfoScale product suite
      1.  
        About the Dynamic Multi-pathing for VMware component
    2.  
      Supported hardware and software
    3.  
      Disk space requirements
    4. Installation prerequisites
      1.  
        Requirements for installing InfoScale Storage in a Microsoft Failover Cluster
    5. Recommendations and best practices
      1. Verifying the system configuration using the Windows Data Collector
        1.  
          Installing the Windows Data Collector
        2.  
          Running the verification reports
    6. About InfoScale licenses
      1.  
        Licensing notes
      2.  
        vxlicrep command
  2. Installing the Infoscale products
    1.  
      About installing Veritas InfoScale products
    2.  
      About InfoScale products co-existence
    3. Installing the server components using the product installer
      1.  
        Applying the selected installation and product options to multiple systems
    4. Installing the server components using CLI
      1.  
        Parameters for setup.exe
    5.  
      Available product options and supported DMPW DSMs
    6.  
      Registering InfoScale Storage resource DLLs
    7.  
      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 SFW upgrade in a Windows Server Failover Cluster environment
        2.  
          Failing over application to secondary site
        3.  
          Preparing the primary site for SFW upgrade in a Windows Server Failover Cluster environment
      3.  
        Upgrading VCS
      4. Upgrading SFW HA
        1.  
          Preparing the primary and secondary sites for upgrading SFW HA 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 DMPW
    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 Windows Server Failover Cluster environment
    4.  
      Reconnecting DMPW DSM paths after the upgrade
    5.  
      Re-configuring the Veritas Scheduler Service
    6.  
      Re-configuring the VxSAS service
    7.  
      Importing the configured rules
    8.  
      Upgrading the dynamic disk group version
    9.  
      Reinstalling the custom agents
    10.  
      Including custom resources
  5. Administering InfoScale product installation
    1.  
      Adding or removing product options
    2.  
      Managing InfoScale licenses
    3.  
      Repairing the InfoScale product installation
    4.  
      About reinstalling the InfoScale products
  6. Uninstalling InfoScale products
    1.  
      About uninstalling InfoScale products
    2.  
      Uninstalling the InfoScale products using the product installer
    3.  
      Uninstalling the InfoScale products using the command line
  7. Performing application upgrades in an InfoScale environment
    1. Upgrading Microsoft SQL Server
      1. Upgrading SQL Server 2008 to SQL Server 2008 R2
        1.  
          Preupgrade tasks for upgrading SQL Server 2008 to SQL Server 2008 R2 in a disaster recovery environment
        2.  
          Upgrading SQL Server 2008 to SQL Server 2008 R2 on the first cluster node
        3.  
          Upgrading SQL Server 2008 to SQL Server 2008 R2 on additional failover nodes
        4.  
          Modifying the SQL Server 2008 service group configuration
        5.  
          Deleting the SQL Server 2008 service group and creating the SQL Server 2008 R2 service group
      2. 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 2007 to a service pack
        2.  
          Upgrading Exchange Server 2010 to a service pack
      2. Upgrading the SQL Server service packs
        1.  
          Upgrading SQL Server 2008 or 2008 R2 to a service pack
        2.  
          Upgrading SQL Server 2012 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 3rd party multi-pathing solution to Dynamic Multi-pathing
    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 DMPW for Active/Active load balancing in a cluster

Re-enabling Volume Replicator in a non-clustered environment

After upgrading in a non-clustered environment where Volume Replicator replicates data from a primary site to a secondary site, you must re-enable Volume Replicator.

In the procedure for preparing the primary site for upgrade, you migrated the primary role to the secondary site.

After both the primary and secondary sites have been upgraded, you may want to migrate the role of the primary back to the original primary site. To do this, you perform a migrate operation again as described in the following procedure.

To migrate the applications back to the original primary

  1. On the current primary site, stop the application that uses Volume Replicator to replicate data between the sites.
  2. From the command line, type:

    vxprint -lVP [-g diskgroup_name]

    This command lists the RLINK and RVG records.

  3. Verify that the data on the Replicator Log is written to the secondary site by running the following command on the primary:

    vxrlink [-g diskgroup_name] status rlink_to_secondary

    This command displays the replication status of the secondary represented by the specified RLINK.

    Verify that the data volumes on the secondary site are consistent and up-to-date with the primary before proceeding to the next step.

  4. To migrate the primary RVG perform one of the following procedures:

    • From the VEA, right-click the primary RVG and select the Migrate option. Select the required secondary host from the Secondary Name option list. Click OK to migrate the primary role to the secondary.

      The primary and secondary roles will be interchanged.

    • From the command line, type:

      vxrds [-g diskgroup_name] migrate local_rvg new_primary_hostname

      Where the secondary host is specified by the new_primary_hostname parameter.

  5. Perform any necessary steps to start the applications on the new primary (old secondary).