Upgrade Guide › Upgrading Server and Endpoint Components › Before You Begin to Upgrade › Upgrade vs. Migrate--Advantages and Limitation

Upgrade vs. Migrate--Advantages and Limitation

Before you begin, choose whether to perform an upgrade or to migrate the environment.

Consider the following advantages and limitations before you upgrade:

• When you upgrade an environment, you install the new server components and endpoints to replace the installed components in succession. You upgrade all the server components and endpoints before you can enable users to access CA ControlMinder.
• During upgrade all CA ControlMinder services are suspended which prevents users from accessing endpoints, managing shared accounts, generating reports and more.
• You cannot upgrade 12.5.x Enterprise Management Servers or endpoints to the latest release. Install more software patches and fixes before you can upgrade your environment.
• Perform an upgrade if you can suspend CA ControlMinder services during the process and if you did not implement CA ControlMinder in high availability or disaster recovery modes.

Consider the following advantages and limitation before you migrate your environment:

• To migrate an Enterprise Management Server deployment, you set up a duplicate of the source environment. During the migration, user access to the source deployment remains uninterrupted. You can install and test the destination system without any downtime.
• You create a duplicate of your existing environment to enable migrating your environment, including all hardware and software that is used in your environment.
• You create a duplicate if your high availability or disaster recovery environments, including all hardware and software that is used in your environment.
• During migration, you clone the database. As users continue to access the existing environment, the source database changes. You migrate the updates from the source database to the cloned database after you install the new environment.
• You cannot migrate the existing Advanced Policy Management data during the migration process. You migrate the policies manually after you installed the new Enterprise Management Server.
• You cannot migrate the Report Portal. You configure the Enterprise Management Server to the Report Portal after you migrate to the new environment.
• Note all customizations that you have performed in the source environment, so you can repeat them on the destination server
• Export the role definitions from the Enterprise Management Server using the CA IdentityMinder Management Console. The export ensures that you can import the role definitions back into the Enterprise Management Server if the migration process does not complete successfully.
• Pending account requests are not migrated in this process. After switching to the new environment, inform users to submit requests in the destination system from now on.
• If users change SAM passwords in the source environment after the database was copied, these changes are missing in the destination environment. Record any additional password changes and restore them manually.
• Migration is supported on CA ControlMinder 12.6.01, 12.7 and 12.8.