...
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, 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. 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.
| Info |
|---|
In the screenshots in this section, the screen on the left in blue is the Source (v6v7.1), and the screen on the right in purple is Destination (v7.2). |
Migration Steps
Start the process on each server
Select the Migrate the Receive menu option on the Source server, and the Receive the Migrate from 7.1 menu option on the Destination server.
Enable Receive Files on the
...
Source
On the Destination 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 Destination the Source server is waiting for the Source the Destination to send request files at from it, the next step is to tell the Source Destination server where to send retrieve the files. Provide the IP Address or Hostname of the Destination Source server to the Source Destination server and select Ok.
Note: This needs to be done within 60 seconds of the Destination Source server starting to wait, or the Destination Source server listener will timeout and stop waiting.
Waiting for the transfer to complete
The Source The Destination server will send copy 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 the Destination server will let you know the results of the transfer. Only once it has completed at the Source the Destination should the Ok button be pressed on the Destination the Source server.
The Destination 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.
...