Are there any best practices relating to the migration/replacement of our CA Release Automation Management and/or Execution Server?
This article is meant to highlight points to consider when migrating a CA Release Automation Management and/or Execution Server. Migration is used in different ways. In this article it assumes you want to move either the CA Release Automation Management and/or Execution Server to a different machine.
CA Release Automation 188.8.131.5240
I'm not sure if you installed any non-out of the box action packs into your environment. But if you did then you might find that steps inside of your jobs gets cancelled. This article describes how to resolve those kinds of issues:
One option to avoid the cancelled jobs might be to backup/restore the nexus sonatype repository. I've included a link under the artifact management section below.
Before following these steps it is recommended to first backup the folder/files (or vm) so that you can revert should things not work as expected.
The link below is the recommended procedure for backing up and restoring a nexus sonatype repository. This can help avoid cancelled steps in your deployment jobs (if action packs were installed) as well as access to any artifact files that might have been registered to the local artifact repository used by release automation.
When migrating CA Release Automation servers it is recommended to identify if execution servers will also be migrated. If the idea is to migrate/replace old execution servers with new execution servers then it is recommended to identify a strategy that works for your situation and what that involves so you can plan accordingly.
These links are meant to hep provide as much additional information as possible.