This is a follow-on post from this and is serious enough to warrant a separate post.
I'm running eGW 1.6001 on Centos 5.2. On July 2, I applied the latest SyncML patch, and tried to sync my Palm using Synthesis client. It didn't work, but the next day I noticed the patch had updated, so I uninstalled the older, and installed the newer one. (using the instructions on that page)
My next sync attempt was a partial success (phone client need to be set to sync at SyncML 1.2 protocol). It synced calendar but not all of my contacts. On each sync attempt, the phone client logged 2100 out of 2800 contacts had errors and therefore refused to update my phone, and for the remaining 700 contacts it'd duplicate them into my phone, and then back into eGW on next sync etc etc ad infinitum ... grrr. duplicates aaaah.
Anyway, this is where the main problem arose.
I have set eGW to autobackup each night. So in order to clear those duplicates etc, I decided to restore an older backup. It was corrupt! Nothing appeared upon restore, all data gone. and I had no admin panel to continue restoring.
I had to drop the mysql table and start from scratch to get it working, the whole eGW install process incl header.inc.php file needed to be done again.
Each backup was corrupt until I reached the 1st July, the night before I'd first done my SyncML patch work. Interestingly the size of the 1st July backup was 1.7 meg, and the next day onwards they were 1.4mb, so I could see SOMETHING was awry
Nothing else happened on my system at that time except the SyncML patching, so I believe
the SyncML patch install/uninstall/update process either allowed corruption of the database or tampered with eGW backup procedure and prevented proper backup.
I should mention that throughout the whole period of time, the live database was fine. It was only the backed-up and then restored databases that were corrupt.
This is a rather serious problem since no one is likely to discover it until they try to restore their data from backup.
