Search Tips   |   Advanced Search

Back up IBM Connections DBs and file systems

  1. Stop the IBM WAS instances hosting IBM Connections.

  2. Use native database tools, back up the databases.

  3. Back up the WAS DMGR_PROFILE:

  4. Back up the Connections deployment.

    1. Create a back-up of the Connections install directory:

    2. Create a back-up of the WAS profile directory:

      If Connections applications are deployed on separate profiles, archive each profile.

    3. Create a back-up of the profileRegistry.xml file, located under...

    4. Back up the local and shared data directories:

  5. Back up the Shared Resources directory:

    For shared and remote network file system requirements, review footnotes in the system requirements.

  6. Back up the Installation Manager data directory:

    This step is necessary only if we are planning an in-place migration of Connections; that is, where you use the same systems to host the new deployment.

      non-root user: /home/user/var/ibm/InstallationManager

    The Installation Manager's shared data directory needs to be backed up as well. If there is a need to go back to the older Connections installation after an upgrade, a conflict might occur if the IIM shared folder has not been backed up and restored in parallel. The IIM relies on the data inside the shared folder to work correctly. If the version of Connections that IIM thinks is installed differs from the version of Connections that was restored on the file system, then IIM will not function correctly.

    The following folder should be backed up :

    • Windows 2008:

      • C:\IBM\Installation Manager
      • C:\IBM\SSPShared
      • C:\ProgramData\IBM\Installation Manager

    • Windows 2003:

      • C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
      • C:\IBM\Installation Manager
      • C:\IBM\SSPShared

    • Linux:

      • /opt/IBM/InstallationManager
      • /var/ibm/InstallationManager
      • /opt/IBM/SSPShared

    • AIX:

      • /var/ibm/InstallationManager
      • /usr/IBM/InstallationManager
      • /usr/IBM/SSPShared

  7. Back up any customized configuration files.

Parent topic:
Update and migrate

Back up and restore data
Save the customizations
Maintain application databases
Uninstall a deployment before migration
Update 4.0 and 4.5 Oracle databases manually
Update 4.0 and 4.5 SQL Server databases manually