Setting up failover nodes
Verify that the owner of the Control-M/EM cluster group is the primary node on which you installed the full Control-M/EM installation.
On each failover node, perform the following:
- Bring the primary Disk, IP address, and Network Name cluster resources online.
- Ensure that the Control-M CORBA Naming service remains online.
- Perform a failover of the Control-M/EM group from the primary node to the secondary node.
- Ensure that the Disk, IP address, and Network Name resources are online on the failover node.
- Open a command prompt and run Setup_files\3RD\setup_em.bat from the installation DVD. If you are using Windows 2008, you must run the command prompt as an administrator.
The following step applies only for a PostgreSQL installation.
- On a PostgreSQL installation, give Log On as a Services permissions to the local NT user that was created for PostgreSQL by performing the following steps:
- From the command line (Start -> Run), run Services.msc
- Locate PostgreSQL for Control-M/EM version xxx
- Locate .\<name of user> and save this name for later.
- Exit Service.msc
- From the command line (Start -> Run), run secpol.msc
- Browse to Security Setting -> Local Policies -> User Rights Assignments and select Log On as Service policy
- Click Add user or group
- Click Locations
- Select the current node name
- In Enter the object name to select, enter a name for the this account service. This name is the <name of user> you saved in step c.
- Check that the current node of Control-M/EM cluster group is online by performing the following steps:
- Issue the Bring Online command to bring the Control-M/EM cluster group on this node online.
- Verify that the current node is online in the Windows Cluster Administrator window.
NOTE: When changes are made using orbconfigure (for example, when the active jobs database is configured for SSL, or the Listening Port number is changed), the Naming Service must be online. Otherwise the changes will not be set permanently.