624
edits
Changes
From SME Server
Jump to navigationJump to searchupgrade Notes improved
Line 73:
Line 73:
+
+
+
+
+
+
===Notes===
===Notes===
−{{Note box|msg=In-place upgrades are not supported. It is necessary to backup and then restore.}}
+{{Note box|msg=In-place upgrades to SME 9.x using yum or CD are not supported due to design constraints imposed by CentOS.
+It is necessary to backup the old server & then restore to the new server.
+The simplest way to do this is via a Console Backup to attached USB disk (on old server).
+Then install the SME 9.x OS from CD on the new hardware (on new server).
+Then select to do a Restore on first boot of the newly installed SME Server 9 (attach USB when asked on first reboot).
+Alternatively use one of the Backup & Restore options available in server manager panel. On the new SME9 server, configure the identical backup job in the server manager Backup or Restore panel, & then select the Restore function within server manager, basic networking configuration of the server will be required if different from original server.
+Note that all add on contribs will need to be re-installed on the new SME 9.x server. Contrib data & configuration will be restored, but its usefulness will depend on the contrib design being unchanged between older (el4 or el5) & el6 versions.
+Other manual tweaks eg custom templates, will need to be deleted & recreated in line with SME 9.x template code.
+Where extensive modifications have been made to the "old eg SME8.1" server, it is recommended to carry out a test backup & restore upgrade first, to discover any problems & ascertain suitable fixes & workarounds. Removing contribs & custom templates before upgrading is recommended.}}
/boot partition is always RAID 1.
/boot partition is always RAID 1.
