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.