Use an Alternate Custom Connector Server for Disaster Recovery

In a multi-site cluster environment, you can configure an alternate Custom Connector Server at the secondary site to use if the primary site fails.
capam33
In a multi-site cluster environment, you can configure an alternate Custom Connector Server to be used if your primary site fails and a secondary site is promoted to be the new primary. The alternate Custom Connector Server configuration is replicated to all other members of the cluster but ignored until the
Use Alternate Server
option is set.
Although the alternate Custom Connector Server configuration is replicated to all other members of the cluster, the value of the
Use Alternate Server
setting, which controls whether the alternate Custom Connector Server is used, is not replicated. You must configure it independently on each node in the cluster.
Because credential management work with the Custom Connector Servers is done by the primary site, the Custom Connector Server specified on the secondary nodes (with the
Use Alternate Server
setting) is ignored until the secondary site becomes a primary site.
Also, because this setting is not replicated, you can select
Use Alternate Server
on the secondary site nodes in preparation for a potential secondary site promotion to primary site in the future. Credential management work with the Custom Connector Servers is done by the primary site. In that sense, the Custom Connector Server chosen on the secondary nodes ( the Use Alternate Server setting ) does not come into play until the secondary site becomes a primary site.
In a single-site environment, you can set up an alternate Custom Connector Server as a backup server. The alternate Custom Connector server uses a different TCF instance from the first instance that the main server uses. If your main server becomes inoperative for any reason, you can enable the already configured alternate Custom Connector Server for communication with your custom target connectors and applications.
All target connectors must be configured for each Custom Connector server instance.
To configure an alternate server for disaster recovery (multi-site cluster):
  1. At the primary site, navigate to
    Configuration
    ,
    Custom Connector
    .
  2. On the
    Connector Server
    panel, complete the settings then save the configuration.
  3. Log in to a secondary site member.
  4. On the
    Connector Server
    panel, set the
    Use Alternate Server
    option.
  5. Select the
    Alternate Connector Server
    tab.
  6. Configure the settings then save the configuration.
  7. Repeat this procedure for each member of the secondary site.
If you promote the secondary site to become the primary, the configuration of the alternate Custom Connector Server is used.
To configure an alternate server for manual backup (non-clustered environment):
  1. From the UI, navigate to
    Configuration
    ,
    Custom Connector
    .
  2. Complete
    one
    of the following procedures:
    If the Connector Server is not configured
    :
    1. Complete the settings then save the configuration.
    2. Set the
      Use Alternate Server
      option then select the
      Alternate Connector Server
      tab.
    3. On the
      Alternate Connector Server
      panel, configure the settings then save the configuration.
    4. Return to the Connector Server
    5. Unset the
      Use Alternate Server
      checkbox then save the configuration. Saving the changes updates the configuration to use the primary server.
    If the Connector Server is configured
    :
    1. Set the
      Use Alternate Server
      option.
    2. Select the
      Alternate Connector Server
      tab, configure the settings then save the configuration.
    3. Return to the Connector Server
    4. Unset the
      Use Alternate Server
      checkbox then save the configuration. Saving the changes updates the configuration to use the primary server.
If the Connector Server fails in production, log in to this server and set the
Use Alternate Server
option. This action makes the configured alternate server active and the first server inactive.