Topic: MySQL structure differences between new install and upgrade - iRedMail
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.8
- Linux/BSD distribution name and version: CentOS 7.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? N
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Hi Zhang Huangbin,
I am preparing to migrate to a new server (Same OS).
The new server is a fresh install of iRedMail 0.9.8
The old server is 0.9.7 upgraded to iRedMail 0.9.8 as per upgrade doc:
https://docs.iredmail.org/upgrade.iredm … 0.9.8.html
I have done a recursive MySQL table structure comparison to ensure the data migrate will be successful.
In doing so I have identified a few small anomalies that I thought you may want to fix.
I used "show create table ....." and piped into "diff -dby"
For sake of brevity, I have reduced the output to the command and the line(s) that are different.
Left side is the upgraded system........ Right side is the clean, new install.
mysql -D iredadmin -e "show create table log;"
`msg` text, | `msg` text NOT NULL,
mysql -D sogo -e "show create table sogo_quick_contact;"
`c_hascertificate` int(11) DEFAULT '0', | `c_hascertificate` int(11) DEFAULT NULL,
mysql -D sogo -e "show create table sogo_user_profile;"
`c_defaults` longtext, | `c_defaults` text,
`c_settings` longtext, | `c_settings` text,
I don't think this will affect my migration.
It was more for accuracy of the upgrade process match that of a clean install.
Thanks, Rob.
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.