High availability requirements

Before installing, upgrading, or uninstalling in a High availability environment, ensure the following:

• The secondary Control-M/EM Configuration Agent and Control-M/Server Configuration Agent is down.
• The Control-M/EM database and Control-M/Server database must always be up at the time of the installation.
• The installation must be performed on the primary and then on the secondary or distributed.
• After installing on the primary, you must install on the secondary before starting up the secondary Configuration Agent.
• High availability is not available until you install on the secondary.

The following table lists the supported components, operating systems, and databases for Control-M High availability.

The following requirements must be met if you are using Control-M/Server with PostgreSQL:

• The secondary Control-M/Server and PostgreSQL database server must be on the same computer.
• You must provide a shared drive on a third server, that is always available, to back up the replicated data. It is used if the primary or secondary are temporarily unavailable.
  • Both the primary and secondary hosts must have read/write permissions on the shared drive.
  • The shared drive must have at least 15 GB of available disk space.
  • Both the primary and secondary UNIX accounts must have the same group ID and the shared drive must have the permissions for the group. To change the shared drive directory, see Running the ctmchangeshdir utility.

The following shared drive requirements must be in a Windows environment:

• The primary and the secondary installations must use the same Domain user
• The Control-M/Server service Log On as must be set to This account with the same Domain user
• Verify that the Domain user has full privileges for the entire Control-M/Server directory and for the shared drive.
• To run Control-M/Server utilities in batch or online, you must use the same Domain user or another user with full access to the shared drive.