Support Policy for Migrating CA Identity Manager 14.5 to AWS using Rubrik or Third-Party Backup Services
search cancel

Support Policy for Migrating CA Identity Manager 14.5 to AWS using Rubrik or Third-Party Backup Services

book

Article ID: 437380

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

 A customer is planning to migrate their on-premises CA Identity Manager (IDM) 14.5 environment to AWS application servers. They intend to use Rubrik Cloud Data Management to back up the on-premises application servers and restore them directly into the AWS environment. The customer needs to know if this migration method is supported and if IDM 14.5 will function correctly after the restoration.

Environment

  • Product: CA Identity Manager
  • Version: 14.5
  • Source: On-Premises Standalone Installation
  • Target: AWS (Amazon Web Services)
  • Migration Tool: Rubrik Cloud Data Management

Cause

Standard migration procedures for CA Identity Manager standalone installations require following official documentation, which typically involves fresh component installation and configuration/data migration. Using third-party tools to "clone" or "image" a server from on-premises to a cloud environment falls under the category of environment cloning.

Resolution

Broadcom does not officially support the migration of CA Identity Manager via environment cloning or third-party image restoration tools for standalone installations.

While third-party solutions like Rubrik are certified for protecting VMware Cloud workloads, their use for migrating the application layer of Identity Manager is subject to the following conditions:

  1. Unsupported Workflow: Migration via cloning is not a documented or supported procedure for standalone IDM environments. Support is limited to installations and migrations performed using official Broadcom guides.
  2. Configuration Requirements: For the application to potentially function, the restoration must maintain exact consistency, including:
    • Server Fully Qualified Domain Names (FQDNs)
    • Static IP addresses (if referenced in configurations)
    • Database connection strings and underlying data integrity
  3. Support Limitation: Should issues arise following a migration performed via Rubrik or similar cloning tools, Broadcom Support may require the customer to reproduce the issue in a standard, supported installation before providing further assistance.

Recommendations:

  • Follow Official Guides: Use the supported migration and component replacement procedures found in the CA Identity Manager 14.5 Documentation.
  • Enhancement Request: To request official certification for Rubrik as a supported migration tool, please submit a Product Enhancement Request.
  • Test Migration: Perform a full validation in a non-production environment before attempting this migration method in production.

Additional Information