Changes

2,416 bytes added , 01:52, 13 December 2023

add info from Bug re graphic res

Line 1: Line 1:

<noinclude>{{Languages}}</noinclude>

−

===Installing And Configuring Your SME Server Software===

==Installing And Configuring Your SME Server Software==

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

{{Note box|It is recommnded that a user take note of details in the [[https://wiki.koozali.org/SME_Server:10.0#Installing | Release Notes for SME10 - Installing ]] and in particular the section covering [[https://wiki.koozali.org/index.php?title=SME_Server:10.0&mobileaction=toggle_view_desktop#Known_issues_upgrade_from_SME9 | Known Issues ]]

}}

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

Line 12: Line 16:

The installer will generally pick the correct options for the install but these can be overwritten if you have another preference, please see the install boot options below and the RAID page https://wiki.koozali.org/Raid for more details.

−

When the installer sees a single disk whether on virtual or physical hardware it will not install any RAID functions for obvious reasons, but LVM will be selected: you may prefer to not use LVM depending on your deployment plan. This can be ~~specifed~~ as shown below.

−

====Licensing Terms and Conditions====

===Licensing Terms and Conditions===

In installing the SME Server software, you are agreeing to the open source licensing terms and conditions associated with it. You can read these terms and conditions in Chapter 1.2. of this guide under the title Software Licensing Terms and Conditions .

−

====RAID Support (Disk Mirroring and striping)====

===RAID Support (Disk Mirroring and striping)===

With SME Server, you have the ability to set up disk mirroring and striping, also called RAID. In disk mirroring, your data is written to two separate hard disks installed in your server. One is the mirror of the other. Should the primary disk experience a hardware failure, the mirror disk will continue operations as if nothing had happened. All of your data will be protected from the single disk failure. This does NOT replace the need for backups! Other levels of RAID offer similar protections with more disks incorporated.

Line 28: Line 32:

=====Hardware RAID=====

−

With hardware RAID, you use a special RAID disk controller to perform the actual striping across multiple disks. As RAID is performed in hardware, the performance may be faster than software mirroring, depending on the capabilities of the various hardware. Additionally Hardware RAID can simplify configuration and array rebuilds because to the operating system, the entire RAID disk system looks like one single disk. You should be able to use any supported SATA or SCSI hardware RAID controller. NB: other options than mirroring may be supported by the controller.

With hardware RAID, you use a special RAID disk controller to perform the actual striping across multiple disks. As RAID is performed in dedicated hardware, the performance may be faster than software mirroring, depending on the capabilities of the various hardware. Additionally Hardware RAID can simplify configuration and array rebuilds because to the operating system, the entire RAID disk system looks like one single disk. You should be able to use any supported SATA or SCSI hardware RAID controller. NB: other options than mirroring may be supported by the controller.

−

====Upgrading From A Previous Version====

===Upgrading From A Previous Version===

Upgrading is somewhat more complex than a clean install on a system as settings and data from the old system need to be preserved. For this reason, we start with the Upgrade procedures.

Please make sure to be familiar with - https://wiki.koozali.org/SME_Server:10.1 - in particular Known issues updating from SME10.0

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

Line 40: Line 46:

{{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 and then restore to the new server. Contribs will need to be reinstalled.}}

−

~~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 the ~~server manager~~ panel, i.e. 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, e.g. using SSH. Many virtual servers can also be configured to pass-through USB ports from the host to the hosted machines allowing a USB drive to be mounted, but this is an advanced topic and cannot be covered here: consult the documentation of the virtual host system in use.

With a physical server 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 the Server Manager panel, i.e. 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, e.g. using SSH. Many virtual servers can also be configured to pass-through USB ports from the host to the hosted machines allowing a USB drive to be mounted, but this is an advanced topic and cannot be covered here: consult the documentation of the virtual host system in use.

−

{{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.}}

{{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) and cannot be used to restore using the "Restore on first boot" function, it can only be used for restores from the Server Manager. The new install must have its backup to workstation configured as per the old install.}}

{{Note box|msg=It is highly recommended that USB drives to be used for backing up '''SME 9.x''' servers prior to an upgrade to 10.n be formatted with a Linux file system. When formatting a USB to use for restore it can be type FAT or FAT32, and is preferred to be ext3 or ext4. If ext4 it should '''not''' be formatted with an OS more recent than RHEL6 for SME9; this is because ext4 has seen multiple incompatible options added with time that are not back-compatible with earlier releases. So, the simple way is to mount the USB dive to the SME 9.x server you wish to back up and format it ext 3 or 4. Ensure that is is then unmounted. The USB drive must '''not''' be mounted before running console/Server Manager backup or the backup will fail to find the drive.}}

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

−

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

* Log in as admin and Backup the '''old server''' via a [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|Console Backup]] to an attached USB disk. This may take many hours, even days, 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, i.e. 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 Koozali SME 10.x OS ~~from CD~~ on the new hardware (on new server).

* Install the Koozali SME 10.x OS on the new hardware (on the new server).

−

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

* Select to do a Restore on first boot of the newly installed Koozali SME Server 10. Only attach the USB containing the backup file, when asked on first reboot. Restore may take a few hours or longer 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>======

−

* 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, and 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, file size, etc.

−

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

* 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 Koozali SME 10 server will be required if different from original server.

Line 71: Line 78:

mount /media/usbdisk

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

−

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

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

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

cd /

Line 99: Line 106:

Where extensive modifications have been made to the "old server (eg SME9.2)", it is recommended to carry out a test backup and restore upgrade first, to discover any problems and ascertain suitable fixes and workarounds. Removing contribs and custom templates before upgrading is recommended.

−

====Installing the Software====

===Installing the Software===

{{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| A user reported install failing to complete with no readily found reason, went through a number of attempts finally found resetting systems Graphic Resolution to a lower than default, set to 800x600 enabled the install to complete without error see [[Bugzilla:12432]]}}

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.

Line 176: Line 186:

{{Warning box|The installation (or upgrade) process rewrites the boot sector on your hard drive. This may cause machines with BIOS boot sector virus detection to not boot unattended. This detection should be disabled in your system's BIOS.}}

−

====Restart after install====

===Restart after install===

On restart, when rebooting from the installed Koozali SME Server Linux image, you will see this screen:

Line 184: Line 194:

====Option: Restoring a Backup====

−

~~the~~ next screen offers to restore. If you have a tar backup (usually smeserver.tgz) you are prompted if you wish to restore. Enter your media, CD, DVD, USB Disk or Tape drive

The next screen offers you the opportunity to restore from tar backup. If you have a tar backup (usually smeserver.tgz) you are prompted if you wish to restore. Enter your media, CD, DVD, USB Disk or Tape drive

[[Image:13.restart-atofferofrestore.jpg|center|850px]]

−

If you have a DAR backup perform your restore from the server-manager after configuration.

If you have a DAR backup you must perform your restore from the server-manager after intial configuration.

−

====Configuring your Koozali SME Server====

===Configuring your Koozali SME Server===

{{Tip box|To change configuration settings, you have set during install, at a later date you can login as admin user to your server console and choose the option to Reconfigure your server. You will be take through the configuration routine just like during installation. Make your necessary changes or use the Keep option to preserve the settings you have set previously.}}

Once your system has restarted (so that it is no longer booting from the installation CD), you are ready to configure your system.

Line 248: Line 258:

Your SME Server needs information about your local network in order to communicate with the other computers on your network. This includes the IP address and the subnet mask on your server's internal interface. Because your server acts as a gateway and firewall, these will differ from the IP address and subnet mask on the external interface.

−

{{Warning box|If you configure your server in server-gateway mode make sure the IP address for the internal interface and the one for the external interface are in different ranges that do not overlap. Unless you know why you don't want to do so, it is best to use addresses from the ARIN reserved IPv4 blocks as follows:

*10.0.0.0/8 IP addresses: 10.0.0.0 – 10.255.255.255

*172.16.0.0/12 IP addresses: 172.16.0.0 – 172.31.255.255

*192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255

Do please note "that only a portion of the “172” and the “192” address ranges are designated for private use. The remaining addresses are considered “public,” and thus are routable on the global Internet". The 172 block can be problematic and is perhaps best avoided.}}

If you plan to operate in server and gateway mode (explained in greater detail below), your server will act as a relay between your local network and the Internet. Because no computer on your local network, other than your server, directly interacts with the external world, the IP addresses assigned to those computers need only be unique with regards to your local network. (It doesn't matter if a computer on someone else's local network uses the same IP address, because the two machines will not be in direct contact.) As a result, we are able to use special "non-routable IP addresses" for your local network, including the internal interface of your server.

Line 261: Line 276:

If, however, you are operating your server in "server-only" mode and there are already servers on your network, you will need to obtain an unused IP address for your local network.

{{Tip box|The careful admin will "ping" the intended address from any available workstation on the network to be certain it is not in use.}}

Next, you will be prompted to enter the subnet mask for your local network. If you are adding your server to an existing network, you will need to use the subnet mask used by the local network. Otherwise, unless you have a specific need for some other setting, you can accept the default setting.

Line 290: Line 307:

=====Option 3: Server-only mode=====

−

Server-only mode is appropriate if you do not wish to use the gateway capabilities of your server. In this configuration, your server connects only to the local network and does not connect directly to the outside world (although it may connect indirectly through your firewall or another server).

{{Warning box|SME 9.2 ISO only, DO NOT enable nic bonding on an initial install when server only mode is selected. See [[SME_Server:9.2|HERE]] for details }}

−

{{Warning box|Because the server "trusts" the local network to be secure in server-only mode, it must be behind a firewall of some type. Under no conditions should it be directly connected to the Internet.}}

{{Warning box|Because the server "trusts" the local network to be secure in server-only mode, it must be behind a firewall of some type. Under no conditions should it in server-only mode be directly connected to the Internet.}}

Your network will resemble the image below:

Line 352: Line 369:

PPPoE is the Point-to-Point Protocol over Ethernet . Essentially, it is an implementation of the popular PPP protocol used for dialup connections - only configured to run over an Ethernet connection. Many ISPs that provide fibre and ADSL connections use PPPoE as the method of connecting their customers to the Internet over ADSL.}}

−

=====Configuring Dynamic DNS=====

<!-- =====Configuring Dynamic DNS=====

If you choose either of the DHCP options or PPPoE, you will be presented with an additional screen where you can choose which dynamic DNS service you wish to use.

Line 360: Line 377:

NB. the script for "dyndns.com - Commercial service" doesn't work, if you wish to use this service select custom and write your own script.

-->

====Configuring the Server for Server and Gateway Mode - Dialup Access====

Line 432: Line 450:

We recommend configuring your server to use DHCP to configure all of your network clients. IMPORTANT! You should not do this if there is an existing DHCP server on your network as there should typically be only one DHCP server per network.

−

[[Image:~~Select_dhcp_server_config~~.png|center|850px]]

[[Image:Dhcp.png|center|850px]]

=====Configuring the DHCP Address Range=====

Trex

Administrators

1,574

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/39664...42411"

Changes

SME Server:Documentation:Administration Manual:Chapter5 (view source)

Revision as of 01:52, 13 December 2023

Navigation menu

Search