If you’re upgrading and moving to another server at the same time, we recommend you first to stop the operational service, move your data and then upgrade Sympa on the new server. This will guarantee that Sympa upgrade procedures have been applied on the data.
The migration process requires that you move the following data from the old server to the new one:
mysqldand copy the database directory to the new server.
$EXPLDIRdirectory that contains list configurations.
$SPOOLDIRdirectory that contains the spools.
sympa.conf, and the file
if it exists.
If you plan to upgrade to Sympa 6.2.60 or earlier,
make sure that the
cookie parameter in
sympa.conf won’t be changed.
Some distributions randomly initialize this parameter in new installation.
When upgrading Sympa on a new server, take care that you start with the same value of this parameter, otherwise you might have problems, such as breakage of all passwords for web interface.
The note above won’t be applied to Sympa 6.2.62 or later which no longer
$SYSCONFDIRdirectory that contains customized scenarios, templates and so on.
$ARCDIRdirectory that contains archives.
In some cases, you may want to install the new version and run it for a few days before switching the existing service to the new Sympa server. In this case, perform a new installation with an empty database and play with it. When you decide to move the existing service to the new server:
data_structure.versionfile on the new server to change the version value to reflect the old number.
sympa.pl --upgrade”. It will upgrade the database structure according to the hop you do.
Theme originally designed by orderedlist