Summary

The Side-by-side Migration process involves running steps on both the Source and the Destination server, within a specific time period, and you should prepare the migration environment completely before starting the process.

The migration steps are performed by logging into each server as the snare user via SSH. After a successful login each server will present the Snare Server or Snare Central Administration Menu, from which the migration is launched. Before starting the migration, you should SSH into both servers in two different terminal windows to make sure everything is working as it should be and you can access both at the same time.  It is also recommended that you check the Snare Health Checker and ensure that there are no database issues before migrating.

Once you have a stable SSH connection to each server, you can begin the migration process.

Migration Steps

Start the process on each server

Select the Receive menu option on the Source server, and the Migrate from 7.1 menu option on the Destination server.

Enable Receive Files on the Source

On the Source server, read through the dialog regarding the Receive Files step, and then select Yes when you are ready to continue to the next step.

You will be asked to provide the sudo password for the snare user to authenticate the request before the process will begin.

Note that for a migration from 7.1 to 7.2, the Source server will simply receive rsync requests (rather than files) from the Destination server. The 7.2 Destination server will copy files from the Source.

Provide the Destination address or hostname

Now that the Source server is waiting for the Destination to request files from it, the next step is to tell the Destination server where to retrieve the files. Provide the IP Address or Hostname of the Source server to the Destination server and select Ok.

Note: This needs to be done within 60 seconds of the Source server starting to wait, or the Source server listener will timeout and stop waiting.

Waiting for the transfer to complete

The Destination server will copy all of the required data automatically. This process may take some time to complete.

Finalising the Migration

Once it has finished the Destination server will let you know the results of the transfer. Only once it has completed at the Destination should the Ok button be pressed on the Source server.

The Destination server will run various upgrade scripts to make the required changes to the migrated data, and will finish back on the Administrative Menu.

Finished

Once the Destination process goes back to the Administration Menu, the migration has been completed. You should now be able to login to the user interface using the user credentials from the Source server. All Objectives and user data will have been migrated across, as well as the Event Archive data.

Note: There may be a small delay in the new event data being accessible after this process as the metadata system processes the new data.