User:Iilluzion: Difference between revisions

From Alpine Linux
(Upgrading ISP Mail server from 1.10.x to 2.x)
 
No edit summary
Line 3: Line 3:


It's assumed that currently your server is running under Alpine Linux 1.10.x. The goal of this document is to describe how to upgrade "ISP Mail Server" to run under Alpine Linux 2.2. An upgrade process involves several significant changes in application configuration and database data and schema handling. Applications that come with Alpine Linux 2.x have a lot of bug and security fixes as well as new functionality. Upgrading of some components will require changing configurations files, update database schema and export/import data.
It's assumed that currently your server is running under Alpine Linux 1.10.x. The goal of this document is to describe how to upgrade "ISP Mail Server" to run under Alpine Linux 2.2. An upgrade process involves several significant changes in application configuration and database data and schema handling. Applications that come with Alpine Linux 2.x have a lot of bug and security fixes as well as new functionality. Upgrading of some components will require changing configurations files, update database schema and export/import data.
'''NOTE:''' The ISP Mail Server can be run in RAM having directories for data such as Postfix mailboxes, PostgreSQL databases to be mounted on hard drive RAID/LVM partitions.


== System Preparations before upgrade ==
== System Preparations before upgrade ==
Line 14: Line 16:
Remove services from auto-start:
Remove services from auto-start:


  rc-update del lighttpd dovecot postfix freshclam clamd clamsmtpd slapd postgresql cron
  rc-update del lighttpd
rc-update del dovecot
rc-update del postfix
rc-update del freshclam
rc-update del clamd
rc-update del clamsmtpd
rc-update del slapd
rc-update del postgresql
rc-update del cron


Stop services except ''postfesql'':
Stop services except ''postfesql'':
Line 51: Line 61:
== Upgrading Alpine Linux ==
== Upgrading Alpine Linux ==


Follow instructions described on page: http://wiki.alpinelinux.org/wiki/Upgrading_Alpine_-_v1.9.x.
'''NOTE:''' We recommend to upgrade to Alpine Linux version not earlier than 2.2, since release 2.2 has a lot of important fixes for bugs and security issues.
 
Follow instructions described on page: http://wiki.alpinelinux.org/wiki/Upgrading_Alpine_-_v1.9.x. After system reboot proceed with next parts of this documents to complete upgrade.
 
== Import data to PostgeSQL ==
 
Make sure that file ''/etc/conf.d/psotgresql'' contains:
PGDATA="/var/lib/postgresql/9.0/data"
 
Check if you need any special setting in ''/var/lib/postgresql/9.0/data/pg_hba.conf'' and ''/var/lib/postgresql/9.0/data/postgresql.conf''. In most cases these files could remain unchanged.
 
Start PostgeSQL (It will setup itself since by default AUTO_SETUP=yes
)
 
/etc/init.d/postgresql start
 
 
rc-update add postgresql
 
Import previously dumped data:
 
 
su - postgres
 
cd <Path to datadump directory>
psql -f postgresql.bak.8.4.2 postgres
 
exit
 
 
 
== Start other services ==
 
Other services do not require any changes of their current configurations, you may just start them:
 
/etc/init.d/clamd start
/etc/init.d/freshclam start
/etc/init.d/clamsmtp start
/etc/init.d/postfix start
/etc/init.d/lighttpd start
/etc/init.d/slapd start
/etc/init.d/cron start
 
Add these service to boot sequence:
 
rc-update add lighttpd
rc-update add freshclam
rc-update add clamd
rc-update add clamsmtpd
rc-update add postfix
rc-update add slapd
rc-update add cron
 
== Update Dovecot configuration and start ==
 
Since Dovecot has many configuration settings changed since 1.x version, the best way is to parse old configuration with ''doveconf'' tool:
 
cd /etc/dovecot
 
doveconf -n > dovecot.conf-new
 
mv dovecot.conf dovecot.conf-old
 
mv dovecot.conf-new dovecot.conf
 
/etc/init.d/dovecot start
 
 
 


'''NOTE:''' We recommend to upgrade to Alpine Linux version not eralier than 2.2, since release 2.2 has a lot of important fixes for bugs and security issues.


* Upgrading Alpine Linux
:* Notes about systems running in RAM
== Final Notes ==
* Upgrading Ligihttpd and PHP
* Upgrading Postgress
:* Export and Import databases
* Upgrading Postfix
* Upgrading Dovecot
:* Changing main configuration
:* Changing Quota configuration
* Upgrading Virus Scanning
* Upgrading RoundCube Webmail
:* Upgrading database schema
* Upgrading OpenLDAP
* Final notes

Revision as of 07:07, 2 May 2011

A Full Service Mail Server Upgrade to 2.x

It's assumed that currently your server is running under Alpine Linux 1.10.x. The goal of this document is to describe how to upgrade "ISP Mail Server" to run under Alpine Linux 2.2. An upgrade process involves several significant changes in application configuration and database data and schema handling. Applications that come with Alpine Linux 2.x have a lot of bug and security fixes as well as new functionality. Upgrading of some components will require changing configurations files, update database schema and export/import data.

NOTE: The ISP Mail Server can be run in RAM having directories for data such as Postfix mailboxes, PostgreSQL databases to be mounted on hard drive RAID/LVM partitions.

System Preparations before upgrade

IMPORTANT NOTE: Please perform full system backup including system configuration and user data. Make sure sure that backup is valid.

We recommend you to stop all user services permanently until system fully upgraded and tested. While system tests are being perform block user access for all users.

NOTE: One of the ways to block user access is to use firewall rules.

Remove services from auto-start:

rc-update del lighttpd
rc-update del dovecot
rc-update del postfix
rc-update del freshclam
rc-update del clamd
rc-update del clamsmtpd
rc-update del slapd
rc-update del postgresql
rc-update del cron

Stop services except postfesql:

/etc/init.d/lighttpd stop
/etc/init.d/slapd stop
/etc/init.d/dovecot stop
/etc/init.d/postfix stop
/etc/init.d/clamsmtpd stop
/etc/init.d/freshclam stop
/etc/init.d/clamd stop
/etc/init.d/cron stop

Dump PostreSQL databases

Since version 9 has significant changes in compare to version 8 you must dump all postgresql databases and later restore data after postgresql is upgraded.

Create a directory where data will be dumped:

mkdir <Path to datadump directory>
chown postges <Path to datadump directory>

Login as postgres and dump data:

su - postgres
cd <Path to datadump directory>
pg_dumpall > postgresql.bak.8.4.2
exit

Stop PostgreSQL services:

/etc/init.d/postgresql stop

IMPORTANT NOTE: Please perform backup of dumped data and PostgeSQL data directory /var/lib/postgresql/8.4. Make sure sure that backup is valid.

Upgrading Alpine Linux

NOTE: We recommend to upgrade to Alpine Linux version not earlier than 2.2, since release 2.2 has a lot of important fixes for bugs and security issues.

Follow instructions described on page: http://wiki.alpinelinux.org/wiki/Upgrading_Alpine_-_v1.9.x. After system reboot proceed with next parts of this documents to complete upgrade.

Import data to PostgeSQL

Make sure that file /etc/conf.d/psotgresql contains:

PGDATA="/var/lib/postgresql/9.0/data"

Check if you need any special setting in /var/lib/postgresql/9.0/data/pg_hba.conf and /var/lib/postgresql/9.0/data/postgresql.conf. In most cases these files could remain unchanged.

Start PostgeSQL (It will setup itself since by default AUTO_SETUP=yes )

/etc/init.d/postgresql start


rc-update add postgresql

Import previously dumped data:


su - postgres
cd <Path to datadump directory>
psql -f postgresql.bak.8.4.2 postgres
exit


Start other services

Other services do not require any changes of their current configurations, you may just start them:

/etc/init.d/clamd start
/etc/init.d/freshclam start
/etc/init.d/clamsmtp start
/etc/init.d/postfix start
/etc/init.d/lighttpd start
/etc/init.d/slapd start
/etc/init.d/cron start

Add these service to boot sequence:

rc-update add lighttpd
rc-update add freshclam
rc-update add clamd
rc-update add clamsmtpd
rc-update add postfix
rc-update add slapd
rc-update add cron

Update Dovecot configuration and start

Since Dovecot has many configuration settings changed since 1.x version, the best way is to parse old configuration with doveconf tool:

cd /etc/dovecot
doveconf -n > dovecot.conf-new
mv dovecot.conf dovecot.conf-old
mv dovecot.conf-new dovecot.conf
/etc/init.d/dovecot start




Final Notes