Migrate to a Multiple-Host Cluster

Migrate a functional single-host cluster to a master host for use in a multiple-host cluster.

Before migrating your host, check the following:
  • That you have a functional single-host cluster

  • That you have the guide titled Planning and Installing Your Cluster on Windows

  • That, at a minimum, you read and performed the necessary actions listed in "Chapter 2: Plan Your Cluster" in Planning and Installing Your Cluster on Windows. For example,

    • You prepared the additional management hosts and compute hosts to be added to your cluster

    • You set up your file server (HostF) with a shared directory accessible to other hosts in the cluster (C:\EGOshare shared as \\HostF\EGOshare)

After successfully testing your single-host cluster, you may wish to convert your host into a master host for use in a multiple-host cluster. To do this, you need to reconfigure your host to function in a cluster containing more than one host.

This appendix is intended to be a replacement for "Chapter 3: Install the Master Host" in the Planning and Installing Your Cluster on Windows guide, because you do not need to install a new master host if you migrate your host to a master host.

The database installed with a single-host cluster functions with a multiple-host cluster, but is not supported in a production environment. To make the Reporting feature work in a production cluster, you will have to move to a commercial database, as described in Administering Platform EGO.

The following steps summarize the migration of your single-host cluster to a master host for use in a multiple-host cluster.

  1. Create the shared directory

  2. Shut down the cluster

  3. Reconfigure the single-host cluster

  4. Start the host

  5. Test that the host is only a management host

Reconfigure the single-host cluster

Reconfigure your single-host cluster for use as a master host in a multiple-host cluster.

Your host currently stores its configuration files in a local directory. You need to redefine your host to store its configuration files in a shared directory so you can add other management hosts to your cluster. This is necessary to convert your single-host cluster into a multiple-host cluster.

Create the shared directory

Create and share an empty directory on a suitable file server host, for example, \\HostF\EGOshare.

Shut down the cluster

  1. Log on to the host as egoadmin.
  2. Log on to EGO as cluster administrator. For example, run egosh user logon -u Admin -x Admin
  3. Run egoshutdown.bat to shut down the cluster.

Redefine the host as a management host only

Redefine your host as a management host only, using configuration files on the shared directory.

You are logged on as egoadmin.

Take this step on every management host, including all master candidates.

  1. Start the command console.
  2. Run the egoconfig mghost command:

    egoconfig mghost shared_dir user_name password

    where shared_dir is the shared directory that contains important files such as configuration files to support failover, user_name is the egoadmin account, and password is the egoadmin password.

    For example
    egoconfig mghost \\HostF\EGOshare DOMAIN\egoadmin mypasswd

After you run egoconfig mghost, the host:

  • Has access to important system files on the shared directory

  • Belongs to the ManagementHosts resource group.

  • Uses egoadmin to run services instead of the Windows LocalSystem account.

Remember:

The shared directory is the same for all management hosts.

The configuration does not take effect until you close and re-open the command console to reset the environment.

Start the host

Start EGO on the Windows host.

You are logged on as egoadmin.

To start the local EGO Windows host, perform the following steps:

  1. Start the command console.
  2. Start EGO:

    egosh ego start

You have now started EGO on the host.

Test that the host is only a management host

  1. Start the command console
  2. Look for the host in the ComputeHosts group in your cluster:
    egosh resource group ComputeHosts
    If you cannot see the host name in the Resource List list in the ComputeHosts group, the host is successfully configured as a management host only.
    Note:

    This test only detects hosts that are running.