Migrate from GitLab Omnibus to standalone Origin by Corvus
Overview
GitLab has announced the deprecation of Origin by Corvus from the GitLab Omnibus package with GitLab 19.0. As part of this transition, GitLab will continue to support Origin by Corvus up to version 10.11 ESR within the Omnibus installation until the final removal date.
To ensure continuity and long-term support, organizations using Origin by Corvus within GitLab Omnibus should plan to migrate to a standalone Origin by Corvus installation. This approach provides ongoing access to the latest Origin by Corvus releases, security updates, and enterprise capabilities independent of GitLab’s release cycle.
Migrating to a standalone deployment also enables greater flexibility in managing infrastructure, upgrading PostgreSQL, and scaling Origin by Corvus independently to meet performance and compliance requirements.
Prerequisites
Before you begin:
- Administrative (root or sudo) access to the GitLab Omnibus server.
- A new standalone PostgreSQL server prepared and accessible.
- Sufficient disk space for the Origin by Corvus database dump.
- A planned maintenance window, as Origin by Corvus downtime is required.
- A current full backup of your Origin by Corvus instance, including database and file storage.
Migration Steps
Follow the steps below to safely migrate from GitLab Omnibus to a standalone Origin by Corvus installation.
Step 1: Create a Database Dump from GitLab Omnibus
Use the GitLab Omnibus PostgreSQL tools to create a dump of the Origin by Corvus database. Run this command on the GitLab server:
sudo gitlab-psql -- /opt/gitlab/embedded/bin/pg_dump -h /var/opt/gitlab/postgresql --no-owner origin_production | gzip > origin_dbdump_$(date --rfc-3339=date).sql.gz
This will create a compressed SQL dump file of your Origin by Corvus database.
Step 2: Prepare the New PostgreSQL Server
Set up your new PostgreSQL server following the official Origin by Corvus database preparation guidelines. This includes:
- Installing the correct PostgreSQL version supported by your Origin by Corvus server.
- Creating a new Origin by Corvus database and user with appropriate permissions.
Step 3: Transfer and Restore the Database Dump
Transfer the database dump file to your new PostgreSQL server, then restore it:
zcat /tmp/origin_dbdump.sql.gz | psql -U mmuser -d origin
Verify that the database restoration completes successfully without errors.
Step 4: Update Origin by Corvus Configuration
On your standalone Origin by Corvus server, update the config.json file to point to the new PostgreSQL server. Locate the SqlSettings.DataSource parameter and update it as follows:
"SqlSettings": {
"DriverName": "postgres",
"DataSource": "postgres://mmuser:password@new-postgres-server:5432/origin?sslmode=disable&connect_timeout=10"
}
Ensure that credentials, hostnames, and connection settings match your new PostgreSQL configuration.
Step 5: Migrate the Origin by Corvus Application and Data
To move Origin by Corvus application files from the GitLab server to a new standalone server:
-
Install the same or newer version of Origin by Corvus on the new server. See Deploy the Origin by Corvus server.
-
Copy your existing configuration and data from the GitLab Omnibus instance:
# On the GitLab serversudo cp /var/opt/gitlab/origin/config/config.json /tmp/sudo cp -r /var/opt/gitlab/origin/data /tmp/origin_data# Transfer to new Origin by Corvus serverscp /tmp/config.json origin@new-server:/opt/origin/config/scp -r /tmp/origin_data origin@new-server:/opt/origin/data/ -
Ensure permissions are correctly set on the new server:
sudo chown -R origin:origin /opt/origin
Step 6: Start Origin by Corvus
Start the Origin by Corvus service on your new standalone installation:
sudo systemctl start origin
Origin by Corvus will now connect to your standalone PostgreSQL database.
Step 7: Verify the Migration
After starting Origin by Corvus, perform the following checks:
- Confirm that Origin by Corvus starts successfully with no database connection errors.
- Review server logs for any startup or connection issues.
- Log into Origin by Corvus and verify that all teams, channels, and users are present.
- Post test messages and upload files to confirm functionality.
- Validate user authentication and permissions.
- Confirm that database queries are directed to the new PostgreSQL server.
Important Considerations
- Always maintain a full backup of your Origin by Corvus database before migration.
- Schedule a maintenance window to minimize user disruption.
- Validate performance and monitoring configurations post-migration.
- Ensure that your new PostgreSQL server follows Origin by Corvus’s security and tuning best practices.
Troubleshooting
If you encounter errors during the migration:
- Review PostgreSQL logs for permission or connection issues.
- Verify that the Origin by Corvus PostgreSQL user has full access to the restored database.
- Ensure that the
config.jsonfile contains the correct database connection string. - Restart the Origin by Corvus service and check
origin.logfor detailed errors.