Central Server Migration Guide

Use this guide to migrate an existing SecOps on-premise installation to a new server, such as when replacing the existing server or moving the deployment to a new virtual machine.

Recommended before migration: Before starting the migration, remove all assets from the existing SecOps installation. This allows the existing agents to receive the removal or uninstall instruction while the current installation is still available. If the assets remain registered during the migration, you may need to manually remove the SecOps agents from those machines after the new installation is completed

The migration consists of two parts:

1. Current server: Run the Server Migration utility. The utility authorizes the migration and removes the existing SecOps installation from the current server.
2. New server: Install SecOps using the standard on-premise deployment process and register it using the same email address and license key provided by the migration utility.

Important: The migration process removes SecOps and its data from the current server. This operation cannot be undone.

Before starting the migration, review the following requirements.

The standard server migration process does not transfer any data from the existing installation. The existing SecOps installation and its associated data are permanently removed from the current server as part of the migration.

This includes, but is not limited to, asset information, scan results, patch history, reports, configuration, uploaded files, and other data associated with the existing installation.

The new server starts as a completely fresh SecOps installation. Existing assets, historical results, configurations, and other data are not carried over automatically.

If you need to preserve or transfer any data from the existing installation, do not run the Server Migration utility. Contact the SecOps Solution Support team at [email protected] before proceeding.

The current server must have internet access during the migration. The Server Migration utility communicates with SecOps Solution to authorize the migration before making changes to the existing installation.

If the server cannot reach api.app.secopsolution.com, the migration will not proceed and the existing installation will remain unchanged.

Before starting the migration, ensure that the new server is provisioned and meets the SecOps on-premise deployment prerequisites.

Download the Server Migration Utility and copy it to the existing SecOps server. The utility can be placed in any directory.

Log in to the existing server using the ubuntu user.

Navigate to the directory containing the migration utility, make it executable, and run it:

The utility displays the email address and license key associated with the current SecOps installation.

Review the displayed information carefully.

To proceed with the migration, enter: MIGRATE , and press Enter.

Any other input cancels the operation and leaves the existing installation unchanged.

The utility first authorizes the migration and then prepares the existing server for removal.

The process may take several minutes.

Important: Keep the terminal session open and do not interrupt the utility until the migration has completed successfully.

After the migration is completed, the utility displays the email address and license key required to configure SecOps on the new server.

For example:

Save both values securely. You will need the same email address and license key when registering SecOps on the new server.

Note: Restart the current server before installing any other software on it.

After the migration is successfully completed, install SecOps on the new server by following the standard on-premise deployment guide.

During the deployment, pay particular attention to the following:

When completing the registration form, enter the same email address displayed by the Server Migration utility.

A different email address will not be recognized as part of the migration.

When prompted for the license key, enter the same license key displayed by the Server Migration utility. 

Do not request or use a new license key for the migrated installation.

The remaining deployment steps are the same as a standard SecOps on-premise installation.

Once the installation is complete, access SecOps at:

Replace <new-server-ip> with the IP address of the new server.

Will I need a new license?
No. The existing license is transferred to the new server as part of the migration.

Can I perform another migration later?
Yes. Each migration authorizes one new installation. If you need to move SecOps again in the future, run the Server Migration utility on the server where the active SecOps installation is currently running.

What happens if the migration utility encounters an error?
If the utility encounters an error before completing the migration, the existing installation remains unchanged.
You can retry the migration. If the issue persists, contact the SecOps Solution Support team at [email protected] and provide the migration log: /tmp/secops_server_migration.log

Can I transfer my existing SecOps data to the new server?
Not through the standard Server Migration process.
If preserving existing scan results, patch history, reports, configuration, or uploaded files is required, contact [email protected] before starting the migration.

For assistance with the server migration process, contact the SecOps Solution Support team at:
[email protected]