Considerations for upgrading secure VCS 5.x clusters to VCS 6.0 and later

Description

Considerations for upgrading secure VCS 5.x clusters to VCS 6.0 and later

When you upgrade a secure VCS 5.x cluster to VCS 6.0 and later, you must consider the following:

  • The HA commands that you run in VCS 6.0 and later are processed by the new broker by default. To ensure that the HA commands are processed by the old broker, set the VCS_REMOTE_BROKER environment variable as follows:

    # export VCS_REMOTE_BROKER=RootBrokerIPaddress,2821

    You must re-create any domains (for example, LDAP domains) that were configured on the old broker in the new broker.

    See the VCS installation documentation for information on enabling LDAP authentication for secure clusters.

  • VCS 6.0 and later do not prompt non-root users who run HA commands for passwords. In 5.x, non-root users required a password to run HA commands. If you want non-root users to enter passwords before they run HA commands, set the VCS_DOMAINTYPE environment variable to unixpwd.

  • Trust relationships are not migrated during the upgrade. If you had configured secure GCO or secure steward, ensure that trust relationships are recreated between the clusters and the steward.

    See the VCS installation documentation for information on setting up trust relationships.

When the old broker is not used anymore, you can delete the old VRTSat package.

See About upgrading secure VCS 5.x clusters to VCS 6.0 and later

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)