Advice on upgrade from 7.0.4 to 7.5.3
Posted: Mon Aug 01, 2005 2:15 pm
I currently have two live servers running 7.0.4 on RH3 - at present I have used things like ART's Automatic Secondary DNS and ART's Anti-spam/Anti-virus RPMS for qmail and its been working great. However it is shortly coming to the end of my first year subscription so I would like to maximise my free upgrade time with SWSOFT and also becuase I have found a few bugs in the stats, with mailman etc. So I have decided to upgrade to version 7.5.3.
I have done some reading for this here and on the SWSOFT forums and put together an action list for completing this task. I would like any feedback on this before I jump in, as both servers are live and critical. Although with a dump before hand I hope to have a good get out by moving all files over to the other server should I get problems.
My questions start with a ##
1. Decide on upgrade path
Most people seem to suggest that going from 7.0.4 to 7.1.7 first would be a good step. Then from 7.1.7 to 7.5.3
2. Stop services on machine to upgrade
3. Use PSADUMP from command line to get a system backup in case of failure
4. Transfer system backup dump file to other machine
5. Download YUM RPM from http://www.atomicrocketturtle.com/atomic/art/3ES/RPMS/
## Is it best to use Yum or up2date on RHE3?
6. Install YUM RPM
7. Configure /etc/yum.conf to include following channels
# THIS CHANNEL CONTAINS MY PSA COMPATIBLE RPMS (php, mysql, qmail-scanner, etc)
[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[atomic-app-vault]
name=Atomic Rocket Turtle - $releasever - Atomic PSA App Vault RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/app-vault/
[psa-7.0]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.0 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[psa-7.1]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.1 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[psa-7.5]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[base]
name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-p ... eleasever/
[updates]
name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-p ... eleasever/
8. Run the YUM updates in two stages
yum install psa/yum update psa
yum install psa-horde psa-imp psa-kronolith psa-mnemo
## The SWSOFT forum seems to suggest that you will need a new license key when doing the upgrade. If so when will this be asked for?
## 9. Reconfigure previous work on secondary DNS servers etc?
10. Restart services
## 11. For future upgrades should I use the new autoupdater within plesk if I am really dealing with a personalised version of PLESK i.e ART stuff on secondary DNS, antivirus etc.?
Thank you in advance for any responses.
I have done some reading for this here and on the SWSOFT forums and put together an action list for completing this task. I would like any feedback on this before I jump in, as both servers are live and critical. Although with a dump before hand I hope to have a good get out by moving all files over to the other server should I get problems.
My questions start with a ##
1. Decide on upgrade path
Most people seem to suggest that going from 7.0.4 to 7.1.7 first would be a good step. Then from 7.1.7 to 7.5.3
2. Stop services on machine to upgrade
3. Use PSADUMP from command line to get a system backup in case of failure
4. Transfer system backup dump file to other machine
5. Download YUM RPM from http://www.atomicrocketturtle.com/atomic/art/3ES/RPMS/
## Is it best to use Yum or up2date on RHE3?
6. Install YUM RPM
7. Configure /etc/yum.conf to include following channels
# THIS CHANNEL CONTAINS MY PSA COMPATIBLE RPMS (php, mysql, qmail-scanner, etc)
[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[atomic-app-vault]
name=Atomic Rocket Turtle - $releasever - Atomic PSA App Vault RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/app-vault/
[psa-7.0]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.0 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[psa-7.1]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.1 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[psa-7.5]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
baseurl=http://www.atomicrocketturtle.com/atomi ... eleasever/
[base]
name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-p ... eleasever/
[updates]
name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-p ... eleasever/
8. Run the YUM updates in two stages
yum install psa/yum update psa
yum install psa-horde psa-imp psa-kronolith psa-mnemo
## The SWSOFT forum seems to suggest that you will need a new license key when doing the upgrade. If so when will this be asked for?
## 9. Reconfigure previous work on secondary DNS servers etc?
10. Restart services
## 11. For future upgrades should I use the new autoupdater within plesk if I am really dealing with a personalised version of PLESK i.e ART stuff on secondary DNS, antivirus etc.?
Thank you in advance for any responses.