Veritas InfoScale™ 7.4.1 Installation and Upgrade Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.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
      3.  
        About Veritas License Audit Tool
    8.  
      About telemetry data collection in InfoScale
  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.  
      Managing the Veritas Telemetry Collector
    4.  
      Repairing an InfoScale product installation
    5.  
      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 later to a compatible 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

Managing the Veritas Telemetry Collector

The Veritas Telemetry Collector on your server sends telemetry data to the edge server. You can manage the Veritas Telemetry Collector on each of your servers by using theTelemeteryCollector.exe binary.

The path to the TelemeteryCollector.exe is stored in the environment variable %VPIPATH%. Navigate to the InfoScale Installation directory on your local computer by entering %VPIPATH% in the Windows Run utility. Once you are in the directory containing the TelemeteryCollector.exe binary, open command prompt and type the required command.

See the following table for a list of operations that you can perform to manage the Veritas telemetry collector along with examples of each of the commands.

Table: Commands used to manage the collector

Operation

Description

Register an edge server and start the collector

Use the following command to register an edge server with the collector. Note that the collector is automatically started after running this command.

TelemetryCollector.exe -start --hostname=<hostname_or_IP> --port=<port_number>

  • <hostname_or_IP> is the host name or IP address of the edge server you want to register.

  • <port_number> is the port number of the edge server that is used for communication.

Example:

TelemetryCollector.exe -start --hostname=telemetry.veritas.com --port=443

Start the collector (if the collector is not already running)

Use the following command if you want to start a collector that is not sending telemetry data to the edge server.

TelemetryCollector.exe -start

Restart the collector (if the collector is already running)

Use the following command to restart the collector that is sending telemetry data to the edge server.

TelemetryCollector.exe -restart

Check whether the collector is running or not

Use the following command to check the status of the collector on your server.

TelemetryCollector.exe -status

Check whether the collector is registered with an edge server

Use the following command to check whether the collector is registered with an edge server.

TelemetryCollector.exe -registered

Update the host name, IP address, or port number of the edge server

Use the following command to update the host name or IP address and port number of the edge server.

TelemetryCollector,exe -update --hostname=<hostname_or_IP> --port=<port_number>

  • <hostname_or_IP> is the host name or IP address of the edge server you want to register.

  • <port_number> is the port number of the edge server that is used for communication.

Examples:

  • TelemetryCollector.exe -update --hostname=telemetry.veritas.com --port=443

  • TelemetryCollector.exe -update --port=443

Configure how often telemetry data is sent to the edge server

Use either of the following commands to define how often you want the collector to send telemetry data to the edge server.

  • To send telemetry data once every month:

    TelemetryCollector.exe -update --d=<day>

  • To send telemetry data once every day:

    TelemetryCollector.exe -update --h=<hour>

  • To send telemetry data once every week:

    TelemetryCollector.exe -update wday=<weekday>

Use the following variables in the above commands.

  • <day> is the day of the month that you want the collector to send telemetry data.

  • <hour> is the hour when you want the collector to send the telemetry data..

  • <weekday> is the day of the week that you want the collector to send telemetry data.

Examples:

  • TelemetryCollector.exe -update --wday=MON

  • TelemetryCollector.exe -update --h=6

  • TelemetryCollector.exe -update --d=14