Skip to content
CA Service Management - 17.1
Documentation powered by DocOps

Pre-Planning for an Upgrade

Last update April 9, 2019

This article contains the following topics:

Planning Considerations

Planning well ensures upgrade readiness before starting the actual upgrade process. Before proceeding with the actual upgrade process, review, consider, and plan for the following tasks:

Task Additional Information

Download CA Service Management 17.1 Installer from CA Support.

For more information, see CA Support.
Review the Release Notes For more information, see CA Service Management 17.1 Release Notes.
Operating Systems and Database Compatability For more information, see Supportability Matrix.
Ensure that your environment meets all minimum version requirements For more information, see Supported Upgrade Paths.
Backing up the Operating Systems and database For more information, see CA SDM Database Backup and CA SDM Database Restore.
Backing up all customizations.
  • Are there any customizations you have performed in your environment?
  • Do you need these customizations after upgrading?

    For more information, see Pre-Upgrade Tasks

Environment Scalability

  • Whether your Current Environment is meeting your business needs?
  •  Is it scalable?
New Features/Enhancements from Latest Release
Which Applications must be upgraded first?
  • CA Process Automation and CA Embedded Entitlements Manager must be upgraded first as this allows the CA Service Management installer to automatically integrate these products.
     
  • If you have installed CA Asset Portfolio Management in your environment, upgrade it first. The order in which you upgrade CA Service Desk Manager and CA Service Catalog does not matter. 
Integration


  • Are there any CA Service Management Integrated Products in your environment?.
  • Will they need to be upgraded too?
    For more information, see Integrating


Create a Backup Plan

Plan to take a full backup of your database and ensure it is validated. Plan to take multiple snapshots or a backup of the entire installation folder during the course of the upgrade procedure. This saves time, in case, you need to revert to a certain point while upgrading. Temporarily allocate additional disk space for backups.

For more information, see CA SDM Database Backup and CA SDM Database Restore.

Decide the Upgrade Method to Use

For more information, see Upgrade Tools.

  • Decide the type of architecture you want to use for CA SDM: Conventional or Advanced Availability.
  • Identify the product components on all systems in your environment.
  • Synchronize production data over to the development environment (Production > Development).
  • Prepare a checklist of all tasks that needs to be performed during the upgrade/migration process.
  • If time permits, plan a test upgrade to capture actual migration time, validate tasks, and record any possible issues and provide resolutions.
  • Ensure that you have the necessary administrative privileges for performing the upgrade procedures.

Plan for Environments

Plan for at least two environments: Development and Production environments. If a test or development environment is not available, consider Swing Box as the development environment. For more information about Swing Box Migration Method, see Use the Swing Box Method for Upgrading.

Scaling the Environment

In case of CA SDM Conventional Configuration, limit the number of components installed on a Primary Server for a better upgrade experience, scalability, and better application performance. For more information, see CA Service Management Deployment Architecture.



Was this helpful?

Please log in to post comments.