ClearFoundation

Hi Andy, the only real way you can shrink the InnoDB database is to dump it and reimport it again. This is known 'issue' with InnoDB databases and how they operate. Note that with time the database will reuse the 'empty' space within the database before growing again...as you have found removing the attachments will not necessarily shrink the actual database filesize.

I have successfully dumped and imported a Zarafa database from between ClearOS installs before, but you have to rehook your user stores if the user UID's are different (zarafa-admin tool). I posted some steps for Zarafa migration to ClearOS 6.2 but the steps are broadly the same with the exception that it uses the 'zarafa' user for Mysql instead of root.
docs.google.com/document/d/1Sei3F6uJDkRY...DLYiYuXUD3CDd1A/edit

This page might also help
stackoverflow.com/questions/3927690/howt...gine/4056261#4056261

If you login via phpMyAdmin you can also select the Zarafa database, and then a table and carry out 'optimisation' on a per table basis to try and reduce the overhead. I'm not sure if this will actually reduce the storage footprint though...

Thanks Tim - that explains so much and appreciate the guidance here. I'll have a go at that.

I think the immediate issue then for me is to actually move mySQL so can you confirm if there is anything specific I need to consider in moving the mySQL - I followed the official guide to moving the db, editing paths, assigning permissions, config files etc but Zarafa Webaccess couldn't see the moved database. Is there ClearOS and/or Zarafa changes that need to be made when the database is moved?

This was the guide I used for moving the database - it may be useful for others assuming you don't see any flaws in it

crashmag.net/change-the-default-mysql-da...with-selinux-enabled

I suppose...in summary...following the above guide breaks Zarafa Webaccess.

Andy

Hi Tim,
nothing work
Could not find update match for zarafa
No Packages marked for Update

@Andy Steven i move database file ibdata1 to new localization, edit my.cnf config and change datadir= new patch.
Run mysql (for my system-mysql.) everythings work perfect zarafa, webaccess.

Tim,
That repo doesn't work it says it requires FileDigests and PayloadIsXz
When doing --nodeps I get : error: unpacking of archive failed: cpio: Bad magic

So I am using the beta again, I have actually installed the beta on another client and it has the same log level issues there.
Also I can't get zarafa upgraded to 7.0.7. from your repos either even after doing a cleanall it's just not there in the upgrade.

I can probably install z-push manually given about 45 minutes or so working with it but will take some time due to clients are working now and I can't really disrupt anything until about 6pm London time. However would be nice if you can get a repo upgrade or a rpm for clearos 5.2 if possible .

Will you be working on doing 7.0.8. for clearos 6.2 in the near future or are you waiting for 7.1. to release?

Hi James, I've just uploaded a build of Z-push 2.0.1 for ClearOS 5.2, and Zarafa 7.0.8 into the timb-testing repo

I'll find out the build system process for 7.0.8 on ClearOS 6.2 and get back to you

Timb, doing a cleanall I can't seem to upgrade the zarafa although I can see the repos in your ftp site. I updated the z-push from your repos however I still get these errors using z-push-admin.php

PHP Notice: Use of undefined constant LOGLEVEL - assumed 'LOGLEVEL' in /usr/share/zarafa-z-push/lib/core/zlog.php on line 185
PHP Notice: Use of undefined constant LOGLEVEL - assumed 'LOGLEVEL' in /usr/share/zarafa-z-push/lib/core/zlog.php on line 104
PHP Notice: Use of undefined constant LOGUSERLEVEL - assumed 'LOGUSERLEVEL' in /usr/share/zarafa-z-push/lib/core/zlog.php on line 108

Hi Tim,
What is the correct syntax for an upgrade?
I have tried:
yum --enablerepo=timb-testing upgrade zarafa zarafa-webaccess
and it did not work.
I get No Packges marked for update ......

Hmm something up with the mirror...i'll investigate!

In the mean time you can grab the rpm's direct from ftp://timburgess.net using 'wget' and then install with 'yum localinstall zarafa*.rpm'

Thanks but no luck,
After running 'yum localinstall zarafa*.rpm'
I get:

--> Finished Dependency Resolution
Error: Missing Dependency: libmapi = 7.0.8-1.clearos is needed by package zarafa-devel
Error: Missing Dependency: php-mapi = 7.0.8-1.clearos is needed by package zarafa-webaccess
Error: Missing Dependency: zarafa-client = 7.0.6-1.clearos is needed by package libmapi

I have downloaded libmapi and php-mapi to the same directory.
Thank you.

Mirrors should be ok again now, please try normal method

yum --enablerepo=* clean all
yum --enablerepo=timb-testing upgrade zarafa zarafa-webaccess