Important Update: Cohesity Products Documentation

All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.

InfoScale™ 9.1 Installation and Upgrade Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.1)
Platform: Windows
  1. Preinstallation and planning
    1.  
      About the Arctera 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 Arctera License Audit Tool
    8.  
      About telemetry data collection in InfoScale
    9.  
      About InfoScale and UEFI Secure Boot
  2. Installing the Arctera 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
    10.  
      Setting up key management for volume encryption
  3. Upgrading the 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 Arctera 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 SQL Server service packs
        1.  
          Upgrading SQL Server to a compatible 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

Setting up key management for volume encryption

The volume encryption feature of InfoScale supports the following options for managing keys:

  • Key Management Interoperability Protocol (KMIP)-based Key Management Service (KMS)

    The volume encryption feature has been tested with the IBM KMS server. However, you can choose any KMIP-compliant KMS server.

  • Cloud-based (non-KMIP, Software as a Service--SaaS) KMS

    Currently, InfoScale supports AWS and Azure as cloud-based KMS providers for volume encryption.

Both these options can be use to configure volume encryption on InfoScale hosts, regardless of whether they are deployed on-premises or as VM instances in the cloud. However, only one type of KMS configuration is supported on an InfoScale host or in an InfoScale cluster at a time.

To configure a KMIP-based KMS server for volume encryption

  1. Copy the following certificate files received from the KMS provider to the C:\Program Files\Veritas\VERITAS Object Bus\bin directory on the InfoScale host.

    If you plan to implement volume encryption in a Volume Replicator (VVR) configuration, copy these files on the InfoScale hosts at the primary as well as the secondary sites.

    Key file: enc-kms-client-key.pem

    Certificate file: enc-kms-client-cert.pem

    CA certificates: enc-kms-cert.pem

  2. Open the KMS configuration file, enc-kms-kmip.conf, located at C:\Program Files\Veritas\VERITAS Object Bus\bin, and enter the following details:
    host = <KMS_host_IP>
port = <KMS_server_port>
keyfile = C:\Program Files\Veritas\VERITAS Object Bus\bin\enc-kms-client-key.pem
certfile = C:\Program Files\Veritas\VERITAS Object Bus\bin\enc-kms-client-cert.pem
cacerts = C:\Program Files\Veritas\VERITAS Object Bus\bin\enc-kms-cert.pem
ssl_version = PROTOCOL_TLSv1_2

Note:

The volume encryption feature is tested with the IBM KMS server, but you can choose any KMIP-compliant KMS server.

To configure a cloud-based KMS for volume encryption

  1. Before you can configure cloud-based KMS for volume encryption, remove any existing KMIP-compliant KMS configuration.

    If no other KMS configuration is place, but a default KMIP configuration file (for example, enc-kms-kmip.conf) is installed on the system, make sure to remove or rename the file.

  2. Edit the %VIP_PATH%\cloudkmsclient.yaml file as necessary.

    This file is used for cloud-based KMS configurations and it includes details about the supported cloud platform and the credentials required to connect to the KMS.

    Administrative permissions are required to edit this configuration file.

    The %VIP_PATH% environment variable typically points to the C:\Program Files\Veritas\VERITAS Object Bus\bin directory.