Download Zarafa Collaboration Platform - The Administrator - NIT
Transcript
Chapter 11. Appendix A; Pre-5.2x upgrade strategies This perl script upgrades the database from 4.2x to the 5.0 format. This script calculates and adds a store column to the properties table. This makes the table sorted on the disk, increasing data throughput. Execute this script as described for the db-convert-4.1-to-4.2 script. Depending on the size of the database and the speed of the system, this script might take a while, but it will probably complete within 10 to 30 minutes on a fast machine. Note It advisable to start this script with screen, so this script can continue in the background. 11.2. Upgrades from 5.0 to 5.1x and up The Zarafa 5.10 server can upgrade the database itself. It can do this from the database version which is needed in 5.0. When upgrading from 4.x installations to 5.10 or higher, the database first needs to be upgraded with the scripts described above to the 5.0 format. Then the 5.10 server can be started which will finalize the upgrade from 5.0 to 5.10 itself. Later versions of Zarafa can always upgrade from a 5.0 database format or newer. 11.3. Important changes since 4.x and 5.x A configuration option in the server.cfg has been changed since 4.20. The option server_name has been renamed to server_bind. A configuration file with typing errors in the option names or non-existing options will render a service inoperable, and it will not start. All the errors found in the configuration file will be printed. For the 5.0 version some unused options have been removed from the server configuration. SQLite support was removed, so the option internal_path was also removed. If this option is in the server.cfg file, please remove this line before starting the zarafa-server process. Options not set in a configuration file will keep their default value. Default values can be found in the example configuration file found in /usr/share/doc/zarafa/example-config. Alternatively the specific manual page for the service can be read: man zarafa-<service>.cfg The Zarafa services did not daemonise in versions before 5.0. However, versions 5.0 and newer do daemonise, and run in the background. To revert this behavior, use the -F switch of a service to keep it running in the foreground. Other configuration changes are found in the gateway. The defaults for the ssl_private_file_key and ssl_certificate_file have been changed. The default directory is now /etc/zarafa/ gateway/, to distinguish it from the service ssl files. 110