Changes

It is necessary to backup the old server & then restore to the new server. }}

It is necessary to backup the old server & then restore to the new server. }}

====With a backup via usb drive====

The simplest way to do this is via a Console Backup to attached USB disk (on old server).

 

* Backup the '''old server''' via a Console Backup to attached USB disk

====Upgrade via Console backup to USB drive====

* Log in as admin & Backup the '''old server''' via a Console Backup to attached USB disk. This may take many hours if you have a lot of data on your server, depending on USB port speed, USB drive speed, & types of files being backed up ie whether already compressed or not etc. Typically for 250Gb of data on your server hard drive, 2 to 4 hours.

* Install the SME 9.x OS from CD on the new hardware (on new server).

* Select to do a Restore on first boot of the newly installed SME Server 9. Only attach USB containing the backup file, when asked on first reboot. Restore may take a few hours depending on data size etc. Make sure you wait for the Restore complete message.

 

* On the old server in server manager, configure the required backup in the Backup or Restore panel. Schedule the backup to run at a suitable time. This backup can be to a workstation desktop for systems with a smaller amount of data, which creates a smeserver.tgz backup file, or to a locally connected USB drive or to a network share, & creates xx...xx.dar files, split into multiple parts if configured & data size is large. This may take many hours to run depending on data size etc.

* On the new SME9 server, manually configure the '''identical''' backup job in the server manager Backup or Restore panel. The backup job MUST point to the exact same location that the original backup file is saved to.

 

====Upgrade using command line restore via ssh or USB====

* It is possible to use the command line to transfer a backup file via ssh (or USB) to the new server & then to run the restore. Standard & non standard backup concepts & procedures are outlined in the Backup server config Howto, http://wiki.contribs.org/Backup_server_config If using any non standard method, then the integrity of your SME server data cannot be guaranteed.

* To do a standard backup & restore using CLI, on the old server log in as admin & perform the Console Backup to USB drive (to a locally connected USB). Alternatively using suitable commands, a smeserver.tgz backup file could be created & saved to / folder, refer Howto.

* Install the SME 9.x OS from CD on the new hardware (on new server).

* Install the SME 9.x OS from CD on the new hardware (on new server).

* Select to do a Restore on first boot of the newly installed SME Server 9 (attach USB when asked on first reboot).

* Answer No when asked if you want to restore from USB during the first boot.

 

 

* On the old server do:

(where zzzz = port number)  

 

====With a backup via the network====

* If you saved the backup file to USB, then transfer the smeserver.tgz backup file from USB to your new server

Alternatively use one of the Backup & Restore options available in server manager panel. On the new SME9 server

* Log in as root or a root user on the new server & do:

* Configure the identical backup job in the server manager Backup or Restore panel.

* Select the Restore function within server manager.

cp /media/usbdisk/Backup-date-folder/smeserver.tgz /

* Basic networking configuration of the server will be required if different from original server.

(replace usbdisk with actual mount point name & Backup-date-folder with actual folder date name)

* After the backup file has been copied to the new server, on the new server do:

tar -C / -xzvf smeserver.tgz

* On new server do:

*Note the backup & restore may take many hours to complete depending on data size etc.

* After restore, the Configuration of the new server should be identical to the old server.

* Note with two servers connected during ssh copying operations, basic networking configuration of the new unrestored SME9 server will need to be temporarily different to the old server to avoid clashes

====Add-ons Contrib====

====Reinstall Contribs after restore====

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.  

Add on contrib rpm packages will need to be re-installed on the new SME 9.x server as these are NOT included in the backup. Contrib data & configuration is included in backups & will be restored, but its usefulness will depend on the contrib design being unchanged between older (SME7/el4 or SME8/el5) & SME9/el6 package versions.  

====Manual tweaks====

====Delete & Reconfigure Manual tweaks====

Other manual tweaks eg custom templates, will need to be deleted & recreated in line with SME 9.x template code.  

Other manual tweaks eg custom templates or scripts, will need to be deleted & recreated in line with SME 9.x template code & base 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.

Where extensive modifications have been made to the "old server (eg SME8.1)", 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.