Upgrade Guide › How to Upgrade CA CloudMinder › Make Sure You Have Backup Files from Previous Installations or Upgrades

Make Sure You Have Backup Files from Previous Installations or Upgrades

Important! After completing the initial installation of CloudMinder, you must back up the file /tmp/properties.sh file on each server component to a secure location. You need this file for future upgrades because this file contains password information. If you do not have this file backed up from a previous installation or upgrade, you cannot proceed with new upgrades.

Make sure to back up the properties.sh file from the /tmp directory immediately after your initial installation.

The upgrade overwrites these files. After you update the servers in the environment, you use the backup versions of the files to complete the upgrade.

Important! Do not create back-up versions in the /tmp directory, as this directory is volatile. Copy the properties.sh files from your prior installation to each server. In the example below, replace /tmp with the location of your secure backup.

The following procedure places back up files in a serverkit directory.

Follow these steps:

1. On each CA Directory server system, enter the following commands:

   mkdir /serverkit
   

   cp /tmp/properties.sh /serverkit
   

2. On each Provisioning Server and CA IAM Connector Server system, enter the following commands:

   mkdir /serverkit
   

   cp /tmp/properties.sh /serverkit
   

3. On each CA SiteMinder Policy Server, enter the following commands to back up the properties file:

   /tmp/properties.sh 
   

   mkdir /serverkit
   

4. On each SPS system, enter the following commands:

   /tmp/properties.sh 
   

   mkdir /serverkit
   

   cp /tmp/properites.sh /serverkit
   

5. On each Identity Management server, enter the following commands:

   mkdir /serverkit
   

   cp /tmp/properites.sh /serverkit
   

Important! If there is more than one server of each type, back up each properties file on each system. For example, if you have two Directory servers, you must back up each, separate properties file under a unique name and move them to the serverkit folder.

Back Up User Tasks

You must back up all tasks in the Identity Management Management Console. The following procedure allows you to back up and export the tasks, upgrade the environment, and re-import the tasks.

Note: When you import a previously exported environment, Identity Management displays a log in a status window in the Management Console. To see validation and deployment information for each managed object and its attributes in this log, select the Enable Verbose Log Output field on the Environment Properties page before you export the environment. Selecting the Enable Verbose Log Output field can cause significant performance issues during the import.

Follow these steps:

1. Click Environments in the Management Console.
2. Select the environment that you want to export.
3. Click the Export button.
4. Save the ZIP file to a location that is accessible to the production system.
5. Click Finish.

   The environment information exports to a ZIP file that you can import into another environment.