Veritas InfoScale 7.1 Installation and Upgrade Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.1)
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 requirements
    5.  
      Requirements for installing InfoScale Storage in a Microsoft Failover Cluster
    6. 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
    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 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 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 the dynamic disk group version
    8.  
      Upgrading clusters for stronger security
    9.  
      Reinstalling the custom agents
    10.  
      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 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 or SQL Server 2014 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

Preupgrade tasks for upgrading SQL Server 2008 to SQL Server 2008 R2 in a disaster recovery environment

Before you proceed to upgrade the cluster nodes in a disaster recovery (DR) configuration, perform the following tasks on the secondary site for the SQL Server instances that you want to upgrade:

  1. Freeze the service group using the VCS Cluster Manager (Java Console).

  2. Obtain the drive letter on which the system database and the analysis service reside using the following command:

    hadiscover -discover SQLServer2008 StartUpParams:InstanceName

    The following is a sample output:

    <Discovery>
    <Attr_Name>
    StartUpParams:INSTANCE2K8
    </Attr_Name>
    <Discover_value>
    <Scalar_value>
    SQLDataPath: E:\Program Files\Microsoft SQL Server\
    MSSQL10.INSTANCE2K8\MSSQL\DATA\
    </Scalar_value>
    </Discover_value>
    <Discover_value>
    <Scalar_value>
    SQLErrLogPath: E:\Program Files\Microsoft SQL Server\
    MSSQL10.INSTANCE2K8\MSSQL\LOG\ERRORLOG
    </Scalar_value>
    </Discover_value>
    <Discover_value>
    <Scalar_value>
    OLAPDataPath: E:\Program Files\Microsoft SQL Server\
    MSAS10.INSTANCE2K8\OLAP\Data
    </Scalar_value>
    </Discover_value>
    </Discovery>
    
  3. Attach a temporary disk and create a volume with the drive letter same as that for the instance on which the system database resides.

    Note:

    If you are upgrading more than one SQL Server instance that have the system database path and the OLAP data path on separate volumes, you must complete the upgrade of each instance on both the sites and then proceed to upgrade the next instance.

  4. Review the SQLDataPath, SQLErrLogPath and the OLAPDataPath directories and create the same directories on the temporary disk.

    Note:

    In case the directory path exists on different volumes, create the similar volumes first and then create the required directory paths.

  5. Copy the following files from the primary site to the data path that you created on the secondary site:

    • master.mdf

    • mastlog.ldf

    • model.mdf

    • modellog.ldf

    • MSDBData.mdf

    • MSDBLog.ldf

    • tempdb.mdf

    • templog.ldf