Installing MongoDB V3.2.12 on a separate remote system

You can install MongoDB V3.2.12 on a separate remote system. Update the backup script that you plan to use for the Cloud APM server upgrade to include the host name or IP address of the new version of MongoDB. This procedure does not require you to stop the Cloud APM server.

Complete the following steps as a root user:

1. Install MongoDB V3.2.12 on a remote system.
   Follow the steps in Installing a remote MongoDB.
2. Complete one set of the following steps depending on the type of server upgrade that you are completing:
   • If you are planning to upgrade the server side-by-side, see steps 1 to 4 in Upgrading the server side-by-side.
   • If you are planning to upgrade the server on a single system, see steps 1 to 4 in Upgrading the server on the same system.
3. Run the backup.sh script without parameters from the tools directory on the system where the V8.1.3 Cloud APM server is installed. The script outputs the name of the backup file.
   For example:

   [root]# /root/min/tools/backup.sh
   The server is configured with a remote DB2. This script must additionally be run on the DB2 machine to backup the database.
   The log file was created at "/opt/ibm/ccm/logs/backup_20160424_005922.log".
   Starting components of the IBM Performance Management server and verifying the passwords...
   Performing a backup...
   Processing the "install" component...
   Processing the "oslc" component...
   Processing the "ccs" component...
   Processing the "apmui" component...
   Processing the "spark" component...
   Processing the "min" component...
   Processing the "min_config" component...
   Processing the "cscs" component...
   Processing the "oidc" component...
   Processing the "oauth2" component...
   Processing the "scr" component...
   Processing the "mongodb" component...
   Processing the "itmcdp" component...
   Processing the "supports" component...
   Processing the "biagent" component...
   Backup operation completed.
   Starting the components...
   Creating the backup file...
   All tasks finished successfully. Your backup is available in the following file:
   /opt/ibm/backups/backup_20160424_005922.tar

   For more information about running the backup script when a non-default user name is configured for the Cloud APM UI administrator user name, see step 6 of Upgrading the server on the same system.
4. Copy the backup file to the system where you plan to install the V8.1.4 Cloud APM server.
5. Update the backup file to use the MongoDB V3.2.12 host name or IP address during the upgrade procedure.
   1. Go to the directory where your backup file is stored.

      cd directory_with_your_backup_file

   2. Create a directory, backup.extracted.

      mkdir backup.extracted

   3. Go to your new directory.

      cd backup.extracted

   4. Extract the backup tar file.

      tar -xf ../backup_timestamp.tar 

   5. Open the ./min_config/ibm_min_config_backup.json file.
   6. In the JSON file, find the line that contains the host name or IP address of your V3.x MongoDB.

      \"service\":\"com.ibm.tivoli.ccm.mongo\",\"name\":\"hostname\",\"value\":\"Remote_MongoDB_v3.x_IP_address_or_hostname\"

      Tip: Search for the text com.ibm.tivoli.ccm.mongo and move your cursor forward character by character until you locate the IP address or host name of your V3.x MongoDB.
   7. Update the host name or IP address with the value for your V3.2.12 MongoDB. For example:

      \"service\":\"com.ibm.tivoli.ccm.mongo\",\"name\":\"hostname\",\"value\":\"mongodb3.example.net\" 

   8. Edit the ./mongodb/mongo.properties file. Change the property

      mongo.hostname=Remote_MongoDB_v3.x_IP_address_or_hostname

      to

      mongo.hostname=Remote_MongoDB_v3.2.12_IP_address_or_hostname

      For example:

      mongo.hostname=mongodb3.example.net

   9. Create a backup file in the backup.extracted directory.

      tar -cf ../backup_timestamp.updated.tar *

opt/ibm/mongodb/bin/uninstall-mongodb.sh