Changes

The following sections explain in detail the process of installing the SME Server software.

The following sections explain in detail the process of installing the SME Server software.

{{Note box|If you have previously installed and configured a server and are reinstalling the software, please be aware that you should use the procedure described in section 1.5.3. Upgrading From A Previous Version in order to preserve your existing configuration and data. Simply performing a new installation will erase all previously existing user accounts, user directories, i-bay contents and web site and configuration parameters. If you have not already done so, you may wish to back up the contents of your server onto one of your desktop computers. You can do so easily by selecting "Backup or restore" from the server manager, as explained in chapter 10.1.||

{{Note box|If you have previously installed and configured a server and are reinstalling the software, please be aware that you should use the procedure described [[#Upgrading_From_A_Previous_Version|here]] in order to preserve your existing configuration and data. Simply performing a new installation will erase all previously existing user accounts, user directories, i-bay contents and web site and configuration parameters. If you have not already done so, you may depending on the size of the data wish to back up the contents of your server onto one of your desktop computers. You can do so easily by selecting "Backup or restore" from the server manager, as explained in chapter 10.1.||

}}

}}

=====Upgrade from 9.x to 10.x=====

=====Upgrade from 9.x to 10.x=====

{{Note box|msg=In-place upgrades to SME 10.x using yum or CD are not supported due to design constraints imposed by CentOS.  

{{Note box|msg=In-place upgrades to SME 10.x using yum or CD are NOT supported due to design constraints imposed by CentOS and the move to systemd.  

It is necessary to backup the old server & then restore to the new server. Contribs will need to be reinstalled.}}

It is necessary to backup the old server & then restore to the new server. Contribs will need to be reinstalled.}}

The simplest way to do this is via a Console Backup to attached USB disk on the old server. Alternatively use one of the Backup & Restore options available in server manager panel, ie backup to desktop, or backup to workstation (either to attached USB or network share). Other non standard options exist to Backup virtual servers that do not have USB ports etc, & Restore to similar virtual systems, eg using ssh.  

The simplest way to do this is via a [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|Console Backup]] to a USB disk attached to the old server. Alternatively use one of the Backup & Restore options available in server manager panel, ie backup to desktop, or backup to workstation (either to attached USB or network share). Other non standard options exist to Backup virtual servers that do not have USB ports etc, and Restore to similar virtual systems, eg using ssh.  

{{Tip box|msg=The Restore from USB on first boot function (on a newly installed SME 10 server), will only utilise backups that are saved as smeserver.tgz files, which are the Console backup to USB or the server manager backup to Desktop. The server manager backup to Workstation (either to USB or network share) creates a "backupdate.dar" type filename (or multiple split parts) & cannot be used to restore using the Restore on first boot function, it can only be used for restores from server manager. The new install must have its backup to workstation configured as per the old install.}}

{{Tip box|msg=The Restore from USB on first boot function (on a newly installed SME 10 server), will only utilise backups that are saved as smeserver.tgz files, which are the [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|Console Backup]] to USB or the server manager backup to Desktop. The server manager backup to Workstation (either to USB or network share) creates a "backupdate.dar" type filename (or multiple split parts) & cannot be used to restore using the Restore on first boot function, it can only be used for restores from server manager. The new install must have its backup to workstation configured as per the old install.}}

======<big>Upgrade via Console backup to USB drive</big>======

======<big>Upgrade via Console backup to USB drive</big>======

* 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.

* Log in as admin & Backup the '''old server''' via a [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|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, and 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. Multiple terabytes may take multiple days.

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

* Install the Koozali SME 10.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.

* Select to do a Restore on first boot of the newly installed Koozali SME Server 10. 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.

======<big>Upgrade via server manager backup to Desktop or Workstation (USB or network)</big>======

======<big>Upgrade via server manager backup to Desktop or Workstation (USB or network)</big>======

* 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 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.

* On the new Koozali SME10 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.

* Select the Restore function within server manager & select the full backup you want to restore from. This may take many hours to run depending on data size, network speed etc. Make sure you wait for the Restore complete message.

* Select the Restore function within server manager & select the full backup you want to restore from. This may take many hours to run depending on data size, network speed etc. Make sure you wait for the Restore complete message.

* Basic networking configuration of the new and/or restored SME9 server will be required if different from original server.

* Basic networking configuration of the new and/or restored Koozali SME 10 server will be required if different from original server.

======<big>Upgrade using command line restore via ssh or USB</big>======

======<big>Upgrade using command line restore via ssh or USB</big>======

* 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.

* 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.

* 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 Koozali SME 10.x OS from CD on the new hardware (on new server).

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

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

* If you created or have the backup file on the old server, transfer the smeserver.tgz backup file via ssh from your old server to your new server. Both servers must be connected & remote access enabled

* If you created or have the backup file on the old server, transfer the smeserver.tgz backup file via ssh from your old server to your new server. Both servers must be connected & remote access enabled

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

* 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.

* 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.

======<big>Migrate using the Lazy Admin Tools</big>======

======<big>Migrate using the Lazy Admin Tools</big>======

====Installing the Software====

====Installing the Software====

{{Tip box|For Koozali SME Server 10 there are options that can be appended to the intial command to specify whether LVM, RAID and XFS are used. See below.}}

{{Tip box|For Koozali SME Server 10 there are options that can be appended to the initial command to specify whether LVM, RAID and XFS are used. See below.}}

{{Tip box|You have some command Line Options that you can use to set some parameters such as LVM (activated by default), '''SME9 only''' - software Raid option (none,0,1,5,6). You can use the function keys F1 to F5 to get more information about different boot options. For SME9 only see [[Booting]]}}

{{Tip box|You have some command Line Options that you can use to set some parameters such as LVM (activated by default), '''SME9 only''' - software Raid option (none,0,1,5,6). You can use the function keys F1 to F5 to get more information about different boot options. For SME9 only see [[Booting]]}}

After showing the boot prompt for some time SME will start the installation process automatically. By default the option to test the installation medium will be selected, and the system will then proceed to the install. Alternatively you can select to go directly to the install, wither in grpahical or text mode.  

After showing the boot prompt for some time SME will start the installation process automatically. By default the option to test the installation medium will be selected, and the system will then proceed to the graphical mode install. Alternatively you can select to go directly to the install, either in graphical or text mode.  

In text mode: you choose which language you want to use for the following installation process.

In text mode: you choose which language you want to use for the following installation process.

{{Note box|For SME 9.2: If you are configuring your system with RAID1 support, notice that your step 4 below will be slightly different. If you skipped section 5.2 RAID1 Support (Disk Mirroring), it would be advisable to read it before proceeding.}}

<!--{{Note box|For SME 9.2: If you are configuring your system with RAID1 support, notice that your step 4 below will be slightly different. If you skipped section 5.2 RAID1 Support (Disk Mirroring), it would be advisable to read it before proceeding.}}-->

'''Step 1''': Insert the USB or CD-ROM media.  

'''Step 1''': Insert the USB or CD-ROM media.  

'''Step 2''': You will be given the option of testing the media before beginning installation.  Choose '''Test this media and install...''' to test the media and after success run the installer or choose the default grpahical install or the text mode install as you prefer. The graphical mode screens are shown below.

'''Step 2''': You will be given the option of testing the media before beginning installation.  Choose '''Test this media and install...''' to test the media and after success run the installer or choose the default graphical mode install or the text mode install as you prefer.

{{Note box|The '''text mode installer''' uses text-based screens but follows the same sequence: see [[Text-mode installer sequence]]}}

{{Note box|The '''graphical mode''' screens are shown below. The '''text mode installer''' uses text-based screens but follows the same sequence: see [[Text-mode installer sequence]]}}

 

{{Note box|The installation shown below is for the full iso image. The net install image follows the same sequence in either mode but the network MUST be enabled for the machine to download its executables}}

[[Image:1.initialinstallmenu-noselection.jpg|center|850px]]

[[Image:1.initialinstallmenu-noselection.jpg|center|850px]]

Currently these are:  

Currently these are:  

*nolvm  - Do not enable LVM

*nolvm  - Do not enable LVM

*noraid - Do not enable RAID

*noraid - Do not enable RAID (this is the default for a single target disk installation)

*noxfs  - Do not use XFS as the default filesystem as is standard for CentOS 7

*noxfs  - Do not use XFS as the default filesystem as is standard for CentOS 7

}}

}}

'''Step 4''': Select the defaults to use.

'''Step 4''': Select the defaults to use.

{{Warning box| At this juncture the partioning scheme and treatment of multiple disks is automated by the customised Koozali install routines and any options you set eg 3 HDs eguals Raid 1 with a hotspare: See the wiki [https://wiki.contribs.org/Raid Raid]. If you select the item "'''Installation Destination'''" those customised setups will be removed and the installer will fall back to the standard install of auto partitioning where the default CentOS scheme is used ie EFI if needed, boot and one huge LVM using all the remaining space on ALL disks are treated as one and a single large LVM. If you are sure of the process you may enter the "'''Installation Destination'''" section and setup your customised partioning, Raid, LVM and file system, '''Beware''' an above average understanding and knowledge of the procedure is required}}

{{Warning box| At this juncture the partioning scheme and treatment of multiple disks is automated by the customised Koozali install routines and any options you have set as above, eg 3 HDs equals RAID 1 with a hotspare: See the wiki [https://wiki.contribs.org/Raid Raid]. If you select the item "'''Installation Destination'''" those customised setups will be removed and the installer will fall back to the standard install of auto partitioning where the default CentOS scheme is used ie EFI if needed, boot and one huge LVM using all the remaining space on ALL disks are treated as one and a single large LVM. If you are sure of the process you may enter the "'''Installation Destination'''" section and setup your customised partioning, Raid, LVM and file system.

'''Beware''' if you do this an above-average understanding and knowledge of the procedure is required}}

[[Image:6.installsummaryscreen-dateandkeyboardtod.jpg|center|850px]]

[[Image:6.installsummaryscreen-dateandkeyboardtod.jpg|center|850px]]