Migrating data in-place
Prepare to update your HCL Connections™ 5.0 or 5.5 databases to version 6.0.
Before you begin
Updating databases in-place overwrites your existing database schema while leaving data intact. Ensure that you have backed up your databases before beginning the update. If the update fails, you can minimize downtime by restoring the backup.
When you use the in-place strategy to update the databases to Connections 6.0, you can no longer use your Connections 5.0 or 5.5 deployment. Also, this strategy increases the system downtime because you must stop the 5.0 or 5.5 deployment.
About this task
The in-place strategy is a good option when you have limited system resources because it minimizes the resources required. Instead of migrating your data, you simply update the 5.0 or 5.5 databases. If you want to keep your 5.0 or 5.5 databases, use the side-by-side data migration strategy.