Ich habe das Backup im alten Egroupware mit der Backup-Funktion admin gemacht und die Datei db_backup-201701201238.bz2 ins backup-Verzeichnis kopiert. “/filles” bzw. Dateimanger wird von uns noch nicht genutzt.
Beim Einlesen des Backup kommt der Warnhinweis. Danach sind wohl offensichtlich die Datenstrukturen zerstört.
Auf dem Standard Anmeldefenster wird angezeigt:
Invalid SQL: INSERT INTO egw_access_log (session_php,loginid,ip,li,account_id,user_agent,session_dla,session_action) VALUES (‘bad login or password’,‘reichelt@default’,‘192.168.xxx.xxx’,1485509652,0,‘Mozilla/5.0 (Windows NT 6.3; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0’,1485509652,’/login.php’) Unknown column ‘user_agent’ in ‘field list’ (1054)
Ich kann mich dann als admin im Setup anmelden und bekomme den Hinweis dass hier Daten von 1.8 sind die angepasst werden müssen. Nach Bestätigung erscheint sofort die erste Fehlermeldung:
process->pass(): #1 for upgrade processing
process->upgrade(): Incoming : appname: phpgwapi, version: 1.8.004, status:
process->upgrade(): No table upgrade required/availible for phpgwapi
process->upgrade(): Outgoing : appname: phpgwapi, status: C
process->upgrade(): Incoming : appname: emailadmin, version: 1.8, status:
process->upgrade(): emailadmin(1.8 --> 14.3.001): running emailadmin_upgrade1_8() --> 1.9.001
process->upgrade(): emailadmin(1.9.001 --> 14.3.001): running emailadmin_upgrade1_9_001() --> 1.9.002
process->upgrade(): emailadmin(1.9.002 --> 14.3.001): running emailadmin_upgrade1_9_002() --> 1.9.003
process->upgrade(): emailadmin(1.9.003 --> 14.3.001): running emailadmin_upgrade1_9_003() --> 1.9.004
process->upgrade(): emailadmin(1.9.004 --> 14.3.001): running emailadmin_upgrade1_9_004() --> 1.9.005
process->upgrade(): emailadmin(1.9.005 --> 14.3.001): running emailadmin_upgrade1_9_005() --> 1.9.006
process->upgrade(): emailadmin(1.9.006 --> 14.3.001): running emailadmin_upgrade1_9_006() --> 1.9.007
process->upgrade(): emailadmin(1.9.007 --> 14.3.001): running emailadmin_upgrade1_9_007() --> 1.9.008
process->upgrade(): emailadmin(1.9.008 --> 14.3.001): running emailadmin_upgrade1_9_008() --> 1.9.009
process->upgrade(): emailadmin(1.9.009 --> 14.3.001): running emailadmin_upgrade1_9_009() --> 1.9.010
process->upgrade(): emailadmin(1.9.010 --> 14.3.001): running emailadmin_upgrade1_9_010()
Invalid SQL: UPDATE egw_ea_identities SET WHERE You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘WHERE’ at line 1 (1064)
–> 1.9.011
process->upgrade(): emailadmin(1.9.011 --> 14.3.001): running emailadmin_upgrade1_9_011()
Invalid SQL: UPDATE egw_ea_identities SET WHERE You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘WHERE’ at line 1 (1064)
–> 1.9.015
process->upgrade(): emailadmin(1.9.015 --> 14.3.001): running emailadmin_upgrade1_9_015() --> 1.9.016
process->upgrade(): emailadmin(1.9.016 --> 14.3.001): running emailadmin_upgrade1_9_016() --> 1.9.017
process->upgrade(): emailadmin(1.9.017 --> 14.3.001): running emailadmin_upgrade1_9_017() --> 1.9.018
process->upgrade(): emailadmin(1.9.018 --> 14.3.001): running emailadmin_upgrade1_9_018() --> 1.9.019
process->upgrade(): emailadmin(1.9.019 --> 14.3.001): running emailadmin_upgrade1_9_019() --> 14.1
process->upgrade(): emailadmin(14.1 --> 14.3.001): running emailadmin_upgrade14_1() --> 14.2
process->upgrade(): emailadmin(14.2 --> 14.3.001): running emailadmin_upgrade14_2() --> 14.2.001
process->upgrade(): emailadmin(14.2.001 --> 14.3.001): running emailadmin_upgrade14_2_001() --> 14.3
process->upgrade(): emailadmin(14.3 --> 14.3.001): running emailadmin_upgrade14_3() --> 14.3.001
process->upgrade(): Upgrade of emailadmin to 14.3.001 is completed.
process->upgrade(): Outgoing : appname: emailadmin, status: C
process->upgrade(): Incoming : appname: api, version: 14.3.907, status: U
process->upgrade(): api(14.3.907 --> 16.1.005): running api_upgrade14_3_907() --> 16.1
process->upgrade(): api(16.1 --> 16.1.005): running api_upgrade16_1() --> 16.1.001
process->upgrade(): api(16.1.001 --> 16.1.005): running api_upgrade16_1_001() --> 16.1.002
process->upgrade(): api(16.1.002 --> 16.1.005): running api_upgrade16_1_002() --> 16.1.003
process->upgrade(): api(16.1.003 --> 16.1.005): running api_upgrade16_1_003() --> 16.1.004
process->upgrade(): api(16.1.004 --> 16.1.005): running api_upgrade16_1_004()
Invalid SQL: SELECT fs_id,prop_namespace,prop_name,MAX(prop_id) AS prop_id
FROM egw_sqlfs_props
GROUP BY fs_id,prop_namespace,prop_name
HAVING COUNT(*) > 1
Unknown column ‘prop_id’ in ‘field list’ (1054)
Jetzt wird mir angezeigt das die Daten in Version 14.3.907 vorliegen und aktualisert werden müssen (bis dahin bin ich gestern nicht gekommen).
Dann erscheint:
process->upgrade(): Incoming : appname: api, version: 14.3.907, status: U
process->upgrade(): api(14.3.907 --> 16.1.005): running api_upgrade14_3_907() --> 16.1
process->upgrade(): api(16.1 --> 16.1.005): running api_upgrade16_1()
AlterColumnSQL(‘egw_ea_accounts’,‘acc_folder_archive’,Array ( [type] => varchar [precision] => 128 [comment] => archive folder ) ) sql=Array ( [0] => ALTER TABLE egw_ea_accounts ADD acc_folder_archive VARCHAR(128) )
Duplicate column name ‘acc_folder_archive’
–> 16.1.001
process->upgrade(): api(16.1.001 --> 16.1.005): running api_upgrade16_1_001() --> 16.1.002
process->upgrade(): api(16.1.002 --> 16.1.005): running api_upgrade16_1_002() --> 16.1.003
process->upgrade(): api(16.1.003 --> 16.1.005): running api_upgrade16_1_003() --> 16.1.004
process->upgrade(): api(16.1.004 --> 16.1.005): running api_upgrade16_1_004()
Invalid SQL: SELECT fs_id,prop_namespace,prop_name,MAX(prop_id) AS prop_id
FROM egw_sqlfs_props
GROUP BY fs_id,prop_namespace,prop_name
HAVING COUNT(*) > 1
Unknown column ‘prop_id’ in ‘field list’ (1054)
Das ist dann das Ende der Versuchsreihe.
