Backing up IBM Connections 

Before applying any updates, back up your databases and your IBM Connections deployment.


About this task


Follow these steps to back up your IBM Connections deployment. You can use this back-up to restore your existing IBM Connections deployment if the update fails.


Procedure

  1. Stop the IBM WAS instances that are hosting IBM Connections.

  2. Create a backup copy of the databases using native database tools. If the update 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.

  3. Create a back-up copy of the WAS dmgr profile directory: profile_root/Dmgr01. For example: D:\WebSphere\AppServer\profiles\dmgr.

  4. Back up your IBM Connections deployment.

    1. Create a back-up copy of the IBM Connections installation directory: lotus_connections_root.

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

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

    3. Create a back-up copy of the profileRegistry.xml file, located under app_server_root/properties.

  5. Back up any customized configuration files. For more information, see the Saving your customizations topic.


Parent topic

Update and migrating

Related concepts
Saving your customizations
Update to IBM Connections 3.0.1 from version 3.0
Update IBM Connections 3.0.1
Backing up and restoring data


Related tasks


Preparing IBM Connections for maintenance
Migrating to IBM Connections 3.0.1 from version 2.5


April 11, 2011 6:55:02 AM
   

 

Apr 11, 2011 6:55:02 AM 1

});