Home
HCL Sametime® Administration Guide 12
Migrating and Upgrading
This section provides information on migrating data from an earlier release to Sametime 12.
Upgrading from Meetings 11.5 and 11.6
Upgrade in place is possible for both Docker and Kubernetes. This section provides information on updating from Sametime 11.6 to Sametime 12.
Upgrading Sametime 11.5 and Sametime 11.6 Docker deployments

HCL Sametime® Administration Guide 12
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
  - Planning for migration to Sametime 12
    This section describes the best practices for planning migration from an earlier Sametime release.
  - Setting the same community ID for all servers in the environment
    To ensure that clients recognize all servers in the environment as belonging to a single community, add a ST_COMMUNITY_ID value to the sametime.ini file.
  - Installing a fix pack
    Fix packs contain updates to incorporate bug and other fixes. You do not need to remove your current Sametime 12 installation when installing a fix pack.
  - Migrating from older Sametime versions
  - Upgrading from Meetings 11.5 and 11.6
    Upgrade in place is possible for both Docker and Kubernetes. This section provides information on updating from Sametime 11.6 to Sametime 12.
    - Upgrading Sametime 11.5 and Sametime 11.6 Docker deployments
    - Upgrading Sametime 11.5 and Sametime 11.6 Kubernetes deployments
- Notices

Upgrading Sametime 11.5 and Sametime 11.6 Docker deployments

Before you begin

To upgrade from Sametime 11.5 or Sametime 11.6 to Sametime 12, the following conditions must be satisfied:

HCL Sametime Meetings 11.5 or Sametime 11.6 must be installed and configured.
Sametime has access to a MongoDB server. You can re-use your existing MongoDB server.
Note: There are no special configuration steps required for the database. It automatically creates when the Sametime server connects to MongoDB.
Prepare migration steps before upgrading to the latest Sametime version. The upgrade gives you a new community and proxy component that replaces your existing components.
- Have a back-out plan. Create a backup of the following files.
  - docker-compose.yml
  - custom.env
  - .env
Docker Compose 1.29 or higher must be installed in your Sametime environment.

About this task

Upgrading Sametime 11.5 or Sametime 11.6 Docker deployments are done in the custom.env file. The upgrade requires access to the MongoDB server. For this example, we will use the following directory structure for simplicity:

/opt/STMeetingServer

Procedure

In /opt/STMeetingserver, stop the Sametime Meeting server by executing:
```
> docker-compose down
```
Unzip the sametime.meeting archive to /opt/STMeetingServer - this will overwrite several files in the folder.
```
> unzip sametime-meetings.zip -d /opt/STMeetingServer
```
Run the script below:
```
> ./install.sh
```
Follow the prompts to provide the information as required. You can copy the encoded secret from sametime.ini or create a new one with this update. Sametime detects an upgrade or full install.
Update the new sametime-config folder to change TLS certificates or other custom settings as needed. Be sure to follow the standard procedures for that.
After upgrade is complete, clear the browser cache to refresh the authentication tokens that may be stored.

Revert to the previous version

About this task

If you encounter a problem, run the command below to roll back to the previous version.

in /opt/STMeetingServer issue
>docker-compose down

in /opt/STMeetingServer_bak issue
> docker-compose up -d