Home
Backing up Lotus Connections
Before applying updates, back up your databases and your Lotus Connections deployment.
Follow these steps to back up your Lotus Connections deployment. You can use this back-up to restore your existing Lotus Connections deployment if the update fails.
- Stop the WebSphere Application Server instances that are hosting Lotus Connections.
- Create a backup copy of the databases using native database tools. If the update fails, use this backup to restore the databases.
- Network deployment only: Create a back-up copy of the WebSphere Application Server dmgr profile that contains Lotus Connections clusters: profile_root//Dmgr01. For example: D:\WebSphere\AppServer\profiles\dmgr.
- Back up your Lotus Connections deployment.
- Create a back-up copy of the Lotus Connections installation directory: LC_ROOT.
- Create a back-up copy of the WebSphere Application Server profile directory: profile_root
If Lotus Connections features are deployed on separate profiles, archive each profile.
- Create a back-up copy of the profileRegistry.xml file, located under app_server_root/properties.
- Back up the Communities forum content store: LC_ROOT/Data/communities/content.
You do not need to back up other 2.0.1 content store directories because they are not affected by the database wizard during migration.
- Back up any customized configuration files. For more information, see the Saving your customizations topic.
Updating Lotus Connections 2.5
Related tasks
Prepare Lotus Connections for maintenance
Migrating to Lotus Connections 2.5
Migrating a stand-alone deployment
Migrating a network deployment