Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

How to install a Protector master or client on a Windows cluster

Before you begin

The Protector Master or Client capability can be installed on servers in a Windows cluster. Before starting the installation, review the following:

  • Ensure that all servers meet the software prerequisites that are outlined in How to install/upgrade Protector on Windows and Linux.
  • Confirm that a cluster environment is set up and working correctly.
  • For Master installations only, ensure that you have all the required license keys for Protector. A separate license key is required for each node in the cluster.

Protector installation for a cluster environment involves performing the following sub-tasks:

Procedure

  1. Install Protector on each node in the cluster (see How to install Protector on a node in a cluster).

  2. Add the Cofio Hub service (see How to add the hub service to a cluster).

  3. For Master installations only:

    1. Add Protector licenses for each node (see How to add licenses to a clustered master).

    2. Add an authentication domain for the cluster (How to configure authentication for a cluster).

How to install Protector on a node in a cluster

To install Protector on a Windows Failover Cluster node:

Procedure

  1. From the Windows Failover Cluster Manager console, identify the cluster server node that is currently in control (i.e. the node which has access to the shared disks).

  2. Install Protector on the controlling node by running Protector-m.n-m.n.n.nnnnn-WIN-ppp.exe.

    The Protector Setup dialog is displayed. Click Next.
  3. Read and accept the license agreement, then click Next.

  4. Change the Installation Directory to the shared drive where you want install Protector. If Protector is already installed on another node in the cluster then select that install location. Click Next.

    For example, if your shared drive is E:\ then the installation path might be on the shared drive: E:\Hitachi\Protector.
    NoteThe Protector Installation Directory must be the same for all nodes in the cluster.
  5. Select either the Master or Client installation type, then click Next.

  6. Change the default Node Name to one that represents the entire cluster. If Protector is already installed on another node in the cluster then use that name. Click Next to start the installation.

    NoteThe Protector Node Name must be the same for all nodes in the cluster.
  7. If the Master is being installed:

    1. Select a local User Account for logging on to the Protector web user interface immediately after installation is complete. You must know the password associated with the selected account. The account used can be changed after installation of the Master. Click Next.

    2. Accept or edit the Protector User Interface Port used to connect to the web based UI.

  8. If a Client is being installed:

    1. Enter the Master Hostname or IP address or a DNS resolvable name of the Master node.

  9. When the wizard indicates that it is ready to begin the installation, click Next.

  10. When the wizard indicates that the installation is complete, click Finish.

  11. Open a Command Prompt to stop and delete the dcefltr service as follows:

    sc query dcefltr
    sc stop dcefltr
    sc delete dcefltr
  12. Open the Windows Services console, stop the Cofio Hub service and set its Start Up Type to Manual.

    The Cofio Hub service will be controlled by the Failover Cluster Manager in a clustered configuration.
  13. From the Failover Cluster Manager console, invoke failover to the next node in the cluster, then repeat the above procedure.

How to add the hub service to a cluster

Complete the following steps on the active node in the cluster.

Procedure

  1. In the Failover Cluster Manager console, configure a Generic Service for the cluster using the High Availability Wizard.

  2. Select the Cofio Hub service from the list.

  3. Name the service (e.g. CofioHubSvc) and assign an IP address, then click Next.

  4. Select the shared disk that Protector is installed on.

  5. Do not replicate any registry settings.

  6. Confirm that all settings are correct and then proceed with configuring the service for high availability.

  7. Review the report to ensure that the service was configured correctly, then click Finish.

  8. If a Master is being installed, make a note of Cofio Hub service's IP address shown in the Failover Cluster Manager console. This will be used for accessing the Protector web UI.

    NoteIf the web UI is not accessible at this address, check your firewall for the following:
    1. Ensure that Protector is not blocked by the firewall.
    2. Enable port 30304 (Protector) and port 443 (HTTPS).
  9. If a Client is being installed, authorize the node in the Nodes Inventory.

  10. Force a fail-over, to confirm that the Protector node remains online in the Nodes Inventory.

How to add licenses to a clustered master

Before you begin

Install the Protector Master on each of the nodes in the Windows cluster as described in How to install a Protector master or client on a Windows cluster.

Because each machine in the cluster has a different machine ID, a separate license is required for each node:

Procedure

  1. Navigate to the Protector web UI using the IP address for the Cofio Hub service.

  2. Log in using the local machine credentials of administrator@master.

  3. Add the license key for this machine following the procedure described in How to Add a License.

  4. To add the licenses for the remaining cluster nodes, browse to the installation directory, then navigate to the subdirectory db\config

  5. Right click License.xml and open the file with WordPad.

    The following XML is displayed showing the license key for the active node:
    <licenses> 
        <entry>ADYFKAE9PMM9BM2KXDNWCEO8PSABE244U8GA</entry> 
    </licenses> 
  6. Copy line 2 (the license key for the currently active cluster node) and insert it as a new line below line 2.

  7. Change the license key on line 3 to match the one provided for the second cluster node.

    The following XML should be displayed:
    <licenses> 
        <entry>ADYFKAE9PMM9BM2KXDNWCEO8PSABE244U8GA</entry>
        <entry>DFGA54AGFDFHDJK675HH86453GHTFGD553DR</entry> 
    </licenses> 
  8. Repeat for each additional node.

  9. Save and close the file.

How to configure authentication for a cluster

Before you begin

Install Protector on each of the nodes in the Windows cluster as described in How to install a Protector master or client on a Windows cluster.

During installation, a local administrator account is used. To complete a cluster installation, a domain administrator account must be set up within Protector that is available to all nodes in the cluster:

Procedure

  1. Navigate to the Protector web UI using the IP address for the Cofio Hub service.

  2. Log in using the local machine's administrator@master credentials.

  3. Add an Authentication Space that will perform authentication for the cluster (see How to create an Authentication Space).

    1. Specify the Authentication Space Name.

    2. Select the required authentication type (e.g. Active Directory).

    3. Select the cluster node as the Proxy.

    4. Enter the Active Directory Domain Name.

  4. Add an ACP Association that will provide administrator level access to Protector (see How to create an Access Control Profile Association).

    1. Specify the ACP Association Name.

    2. Select the User ACP Association type.

    3. Browse for the required User Name from the Authentication Space specified in the previous step.

    4. Add the Default Administrator from the Available Profiles listed.

  5. Log out of the web UI.

  6. Log back into the web UI using the new User@Domain credentials specified in the above steps.

  7. Force a fail-over, then log in again using the new credentials to confirm that Protector is still accessible.

  8. Finally, refer to one of the following topics to setup accounts for those users that required access to the Protector user interface.