Koozali.org: home of the SME Server

Preparing to update to SME 11

Offline wdepot

  • ****
  • 120
  • +0/-0
    • http://westerndepot.com
Preparing to update to SME 11
« on: October 15, 2026, 02:03:19 AM »
Now that SME 11 is finally officially released I am trying to get ready to update an SME 10.1 server by first transferring it to a new SME 11 install on a backup server. The plan is to backup the 10.1 server to a USB 3 flash drive then restore the backup onto the backup server when the new SME11 install asks if you want to restore from USB.

The problem I'm having is, I believe, due to the format of the USB flash drive that I'm trying to use. I logged on to the SME10 server terminal as admin, selected backup from the menu option and chose local disk. The terminal gave me an unable to back up message with the reason listed for the USB drive being shown as SZ. The total size to back up was shown as something like 15GB and the USB drive is a 32GB capacity. However the USB drive is formatted as FAT32 which can only handle files up to 2GB in size. Obviously I need to reformat the drive. On my Windows machine I can directly format it using exFAT or NTFS and if I use Rufus I also have the option of using UDF. Which should I choose?

The other question I have is regarding the MySQL/MariaDB databases. I recall that when I first began testing SME11alpha that I discovered that the table definitions for the system's mysql database changed from SME10 to SME11 and restoring the system backup caused problems because it restored the old SME10 mysql database when it shouldn't. Is there a way to prevent the console backup on the SME10 machine from including any system mysql databases? If I can have it only include the one single user database that would be perfect but if I have to transfer the one database manually that is doable.

Offline bunkobugsy

  • *
  • 359
  • +4/-0
Re: Preparing to update to SME 11
« Reply #1 on: October 15, 2026, 10:47:57 AM »
Maybe try to find a smaller usb stick or partition it, but FAT32 is recommended.
Give https://wiki.koozali.org/Migratehelper a shot after a good read.
https://wiki.koozali.org/SME_Server:11.0_Addendum#Issues_related_to_installs_prior_to_11.0_release should be fixed,
but always do a test migrate before going full production.

Offline TerryF

  • grumpy old man
  • *
  • 1,912
  • +6/-0
Re: Preparing to update to SME 11
« Reply #2 on: October 15, 2026, 10:26:49 PM »
Have had this crop on my own Microserver upgrade, format USB to ext3/4

Do not see this on a VM, so is a FS issue on hardware dependent
--
qui scribit bis legit

Offline Jean-Philippe Pialasse

  • *
  • 3,049
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Preparing to update to SME 11
« Reply #3 on: October 17, 2026, 12:59:36 AM »
best format as ext3/4 or exfat

ntfs would beed installing additional drivers and has not the best support under linux.

i would stay away from udf

Offline david000

  • *****
  • 222
  • +0/-0
Re: Preparing to update to SME 11
« Reply #4 on: October 28, 2026, 03:41:13 PM »
I'm looking at upgrading at the moment.

The documentation suggests it's possible to restore up from a NAS hosted backup set if the backup job in server manager is configured the same ?  From memory this is how I went from v9 to v10.

Is there any benefit from going the USB route ?

The other thing would be that we tend to Roundcube for the webmail - has anyone tried that yet ?  I see it's not listed in contribs as yet.

Any other thoughts and suggestions for someone relatively non technical would be welcome.

 

Offline bunkobugsy

  • *
  • 359
  • +4/-0
Re: Preparing to update to SME 11
« Reply #5 on: October 28, 2026, 08:44:46 PM »
https://wiki.koozali.org/SME_Server:11.0_Addendum#Horde_changed_for_Roundcube and is now core, not a contrib.

How musch data does your server hold? I'd still go the Migratehelper way.

Offline david000

  • *****
  • 222
  • +0/-0
Re: Preparing to update to SME 11
« Reply #6 on: October 29, 2026, 10:06:20 AM »
https://wiki.koozali.org/SME_Server:11.0_Addendum#Horde_changed_for_Roundcube and is now core, not a contrib.

How musch data does your server hold? I'd still go the Migratehelper way.

That's good news on Roundcube.

According to server manager the full system is about 60Gb.

I did read the Migratehelper notes but I'm not super technical. I'll look again.

Offline TerryF

  • grumpy old man
  • *
  • 1,912
  • +6/-0
Re: Preparing to update to SME 11
« Reply #7 on: October 29, 2026, 10:19:09 AM »
According to server manager the full system is about 60Gb.

Using console backup on a sme10.1 system using a WD USB HD ended up with with 98GB backup

restored at first offer on a sme11 install, then the usual update, reinstall contribs etc

Only issue was nexcloud due to my having updated it past the supported version, my bad, just took a little work from the cli otherwise all good
--
qui scribit bis legit

Offline david000

  • *****
  • 222
  • +0/-0
Re: Preparing to update to SME 11
« Reply #8 on: October 29, 2026, 10:26:08 AM »
Using console backup on a sme10.1 system using a WD USB HD ended up with with 98GB backup

restored at first offer on a sme11 install, then the usual update, reinstall contribs etc

Only issue was nexcloud due to my having updated it past the supported version, my bad, just took a little work from the cli otherwise all good

Cheers - I just re-read the Migratehelper notes but don't fully understand some of the implications so I'll stick with plan 'a' via server manager onto a new box and see it goes.  I don't recall using any trixy contribs so it should be vanilla, maybe !

Offline wdepot

  • ****
  • 120
  • +0/-0
    • http://westerndepot.com
Re: Preparing to update to SME 11
« Reply #9 on: October 30, 2026, 11:56:15 PM »
I ran into a couple issues using MigrateHelper that I could use a bit of guidance on. For my first attempt at upgrading an SME10.1 server to SME11 I used Nano to modify the MigrateHelper script and added all of the /home/e-smith/db/mysql dump files to the exclude list except for the one that I actually needed to transfer. I also moved /home/e-smith/files from the exclude list to the include list so I could transfer everything at once. The resulting smeserver.tgz file ended up being just under 12GB.

I installed SME11 on our backup server and had it restore from the USB key when it asked if I wanted to load a backup. I then installed PHPmyAdmin and went in to add the user for the one database I did have transferred and discovered that the user already existed. Browsing the contents of the smeserver.tgz file I discovered that the mysql.privileges.dump file existed even though I thought I had excluded it. Is there somewhere in the script that adds that file into the backup list specifically or it is likely that I just misspelled the file name when I created the exclude list?

Also once I made sure the user and password were properly set for the database I did want transferred I tried accessing the web site in the Primary ibay that uses the database and kept getting a 500 Server error every time. I tried installing the other contribs we use on our SME10 server onto the SME11 backup server to see if that would make a difference but nothing helped. When trying to install the XT GeoIP contribution I ended up getting a dependency error. I looked in the smeserver.tgz file in the /home/e-smith/db folder and discovered that it includes files for yum, namely yum_available, yum_installed, yum_repositories and yum_updates. This would be fine for a backup for the same version of SME but am I right in thinking these files need to be excluded for transfer between SME10 and SME11? After all SME11 does not use exactly the same repositories as SME10. To block these I assume I can add a line to the exclude section of the MigrateHelper script that reads /home/e-smith/db/yum* or will I need to add each of the four files separately?

Now that I've realized what might be causing the problems I had with the first attempt at migrating SME10 to SME11 I've done a fresh reinstall of SME11 on the backup server and updated it and will install the contributions we use first before using MigrateHelper, then do a console restore. Since the Primary web site can create a backup of its MySQL database in its ibay I plan to exclude /home/e-smith/db/mysql/*.dump in the MigrateHelper script as well as the yum related files and will move /home/e-smith/files back to the exclude list and try rsync instead to do that transfer. Are there any other files that should NOT be transferred from SME10 to SME11 that would be included in a normal backup?

Offline Jean-Philippe Pialasse

  • *
  • 3,049
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Preparing to update to SME 11
« Reply #10 on: November 08, 2026, 07:41:07 AM »
I ran into a couple issues using MigrateHelper that I could use a bit of guidance on. For my first attempt at upgrading an SME10.1 server to SME11 I used Nano to modify the MigrateHelper script and added all of the /home/e-smith/db/mysql dump files to the exclude list except for the one that I actually needed to transfer.
why not just migrate them and delete them later, or better cleanup your mysql db before ?

I also moved /home/e-smith/files from the exclude list to the include list so I could transfer everything at once. The resulting smeserver.tgz file ended up being just under 12GB.
then you might have been better just run the console backup. Since SME10 has now an embedded list of all contribs needed folder/files to backup.
migratehelper is really to allow you to migrate without the data files for servers with terabytes of data.

I installed SME11 on our backup server and had it restore from the USB key when it asked if I wanted to load a backup. I then installed PHPmyAdmin and went in to add the user for the one database I did have transferred and discovered that the user already existed. Browsing the contents of the smeserver.tgz file I discovered that the mysql.privileges.dump file existed even though I thought I had excluded it. Is there somewhere in the script that adds that file into the backup list specifically or it is likely that I just misspelled the file name when I created the exclude list?
probably misspelled. However, It might have been filtered out by the import script later.

Also once I made sure the user and password were properly set for the database I did want transferred I tried accessing the web site in the Primary ibay that uses the database and kept getting a 500 Server error every time.
not sure what you mean by that, showing the command you actually did would be more helpful than what was your intention. You must be aware that moving from mariadb 5.5 to maraidb 11.4 comes with big changes with user right management...
e.g. if you manually import sme10 mysql.dump to mariadb11.4 you probably borked your mariadb.

I tried installing the other contribs we use on our SME10 server onto the SME11 backup server to see if that would make a difference but nothing helped. When trying to install the XT GeoIP contribution I ended up getting a dependency error.
have you read this page :https://wiki.koozali.org/SME_Server:11.0_Addendum#Changes_or_issues_migrating_from_earlier_version ?


I looked in the smeserver.tgz file in the /home/e-smith/db folder and discovered that it includes files for yum, namely yum_available, yum_installed, yum_repositories and yum_updates. This would be fine for a backup for the same version of SME but am I right in thinking these files need to be excluded for transfer between SME10 and SME11? After all SME11 does not use exactly the same repositories as SME10. To block these I assume I can add a line to the exclude section of the MigrateHelper script that reads /home/e-smith/db/yum* or will I need to add each of the four files separately?
yum_available, yum_installed,yum_updates do not pose any issue, you can remove them or leave them, we use dnf_* files now.
yum_repositories is used as it. and there you need to read the Addendum page, you are in charge of cleaning it to your need. The same way you are in charge to clean your template-customs

Now that I've realized what might be causing the problems I had with the first attempt at migrating SME10 to SME11 I've done a fresh reinstall of SME11 on the backup server and updated it and will install the contributions we use first before using MigrateHelper, then do a console restore. Since the Primary web site can create a backup of its MySQL database in its ibay I plan to exclude /home/e-smith/db/mysql/*.dump in the MigrateHelper script as well as the yum related files and will move /home/e-smith/files back to the exclude list and try rsync instead to do that transfer. Are there any other files that should NOT be transferred from SME10 to SME11 that would be included in a normal backup?
I would strongly advise not to do so.
First, you must really let the backup handle your mysql migration please do not import manually the mysql.dump from SME10, it needs to be reworked before to not break you mariadb.

Second, the way to do is really:
1- backup
2- fresh install
3- restore backup
4- reboot
5- upgrade
6- install contribs

If you start with contribs, then for complexe contribs like nextcloud you will fail the contrib migration process and just put your system in an unrecoverable state after putting the backup on it.

Offline wdepot

  • ****
  • 120
  • +0/-0
    • http://westerndepot.com
Re: Preparing to update to SME 11
« Reply #11 on: Yesterday at 02:24:35 AM »
The problem I've been having with the SME11 upgrade is that once I've completed the console restore of the smeserver.tqz file created by the migrate helper script and the rsync of /home/e-smith/files/ when I try to access the web site on the SME11 backup server I keep getting a 500 server error and I'm unsure as to where it might be coming from. I originally thought it might be because I was trying to access the site using the local IP address. We had gotten a .store domain from Cloudflare to match the primary .com domain during a time when we were having DDOS issues so I updated the DNS for the .store domain at CloudFlare to point to the backup server. I used this .store domain on the backup server when I did a fresh install of SME11 and after doing the console restore immediately used admin configure to restore it to the .store domain name as well as changing the IP addresses back to the ones for the backup server.

I have successfully managed to block all mysql dump files from being transferred by migrate helper save for the single database used by the web site (which doesn't come from SME at all) so the problem shouldn't be caused by MariaDB. I've also blocked all four yum files from the e-smith db. The only contribs I have installed in advance of the restore and rsync are PHPmyAdmin and WebHosting. The former is so I can create the user/password for the website to use to access its database in advance of the transfer and  the latter so I can double check the ibay settings. I did remember to update SME11 before installing anything or doing the restore.

So from what you are saying it sounds like what I might want to do instead is:
1) Fresh install of SME11 on the backup server
2) MigrateHelper on the old SME10 server
3) Restore this backup onto SME11 and allow the needed reconfigure reboot
3) THEN update SME11 and install needed contribs
4) Finally rsync /home/e-smith/files

Since I do have some custom templates for httpd.conf would it be best to block those from the transfer and add them one at a time to check and see if they cause a problem? They work fine under SME10 but I don't know if there are changes in Apache under SME11 that might cause an issue with older settings.

Offline david000

  • *****
  • 222
  • +0/-0
Re: Preparing to update to SME 11
« Reply #12 on: Yesterday at 10:15:53 AM »
Second, the way to do is really:
1- backup
2- fresh install
3- restore backup
4- reboot
5- upgrade
6- install contribs

If you start with contribs, then for complexe contribs like nextcloud you will fail the contrib migration process and just put your system in an unrecoverable state after putting the backup on it.

That's interesting.  I'm using fetchmail to pull mail from additional pop boxes and installing after the restore means manually adding the fetchmail accounts. Not a deal breaker for me but.   On testing it seemed to work ok.

I'm only fetching mail from 1 additional pop box on a specific domain for a specific user.  I did wonder about redirecting that mail to the catch all domain I use for the mail collection but not sure if it would be possible to sort mail to the specific user.