Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

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 Central Administration Menu, from which the migration is launched. Before starting the migration, it 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.

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

In the screenshots in this section, the screen on the left in blue is the Source (v6), and the screen on the right in purple is Destination (v7).

Migration Steps

Start the process on each server

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

Enable Receive Files on the Destination

On the Destination 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.

Provide the Destination address or hostname

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

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

Waiting for the transfer to complete

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

Finalising the Migration

Once it has finished the Source server will let you know the results of the transfer. Only once it has completed at the Source should the Ok button be pressed on the Destination 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.

  • No labels