Before migrating or updating IBM® Connections, back up your databases and applications.
About this task
Follow these steps to back up your IBM Connections deployment. You can use this
backup to restore your existing deployment if the migration or update
fails. This procedure backs up your entire deployment; you cannot
use it to back up individual applications within IBM Connections.Note: Pay attention to the
version of IBM Connections you
are backing up. If you must restore the backup later, it can only
be restored to the same version of IBM Connections,
as described in the following details:
- Content only can be restored to the same major/minor release that
it was backed up from. For example Cumulative Refresh (CR) releases
for Connections 5.0 are considered part of the Connections 5.0 release.
- Content cannot be restored to Connections 5.0 if it was backed
up on Connections 4.5 (CRx).
- Content cannot be restored to a later release if it was backed
up on Connections 5.0 (CRx).
- The /provision subdirectory in the shared
content folder only can be restored to the exact version that it was
backed up on. It is generally not safe to restore the /provision subdirectory
to a version with a CR or an interim fix different from the version
the directory was backed up from.
Procedure
- Stop the IBM WebSphere® Application Server
instances that are hosting IBM Connections.
- If you installed Connections Content Manager, back up the FileNet® Storage Area and the
Engine-ws.ear file.
By default the FileNet Storage Area is located in the following
directory:
By default, the Engine-ws.ear is
located in the following directory:
- For Linux, AIX, or zLinux: <connections_root>/addons/ccm/ContentEngine/tools/configure/profiles/CCM/ear
- For Windows :<connections_root>\addons\ccm\ContentEngine\tools\configure\profiles\CCM\ear
- Determine if the filenetAdmin user (usually
the same as the ConnectionsAdmin user) is a local
WIM user and, if so, back up the local fileRegistry.xml file
to restore it after migration.
- Find the user that is used by Connections to contact FileNet.
From
the WebSphere Application
Server administrative console, navigate to and make note of the User ID of the filenetAdmin.
- Determine whether this user is in a local file-based
repository.
- From the WebSphere Application
Server administrative console, navigate to .
- In the search box, enter the User ID of your filenetAdmin from
the J2C authentication data and click Search.
If
the unique name of the user ends with o=defaultWIMFileBasedRealm,
then your FileNet administrator
is from a local file-based repository and not LDAP and you should
continue to the next step to back up the fileRegistry.xml file.
Ensure
you also have added an LDAP group to the administrative access of FileNet as described in Setting an LDAP group to be domain administrator
in addition to, or instead of, a specific user.
- Back up the existing fileRegistry.xml file.
For example on Linux:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/ICCell/fileRegistry.xml
- Using native database tools, back up the databases. To
back up Connections Content Manager databases, include both FileNet databases: Global Configuration
Database (FNGCD) and Object Store (FNOS). If the update or migration
fails, use this backup to restore the databases.
For
more information about backing up IBM Connections
data, see the Backing up and restoring data topic.
- Back up the WebSphere Application
Server Deployment Manager profile directory: profile_root/Dmgr01.
For example: D:\WebSphere\AppServer\profiles\dmgr.
- Back up your IBM Connections
deployment.
- Create a backup of the IBM Connections
installation directory: connections_root.
- Create a backup of the WebSphere Application Server profile directory: profile_root
Note: If IBM Connections
applications are deployed on separate profiles, archive each profile.
- Create a backup of the profileRegistry.xml file,
located under app_server_root/properties.
- Back up the local and shared data directories:
- Back up the Shared Resources directory:
Note: For shared and remote network file system requirements,
be sure to review the footnotes for each supported operating system
in the detailed
system requirements.
- Optional: Back up the IBM Installation Manager data directory:
Note: This step is necessary only if you are planning an in-place
migration of IBM Connections;
that is, where you use the same systems to host the new deployment.
CAUTION:
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 as follows:- 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
- IBM i:
- /QIBM/InstallationManager
- /QIBM/ProdData/IBM/SSPShared
- /QIBM/UserData/InstallationManager
- /QIBM/ProdData/InstallationManager
- Back up any customized configuration files. For more information,
see the Saving your customizations topic.