Zarafa server database is one of the deserving application for the substitute of Microsoft Exchange Server. Same as Exchange server database, Zarafa is also integrates with MS Outlook to provide very flexible email platform in adding to its own software ‘WebAccess’.
It is very easy to use for the all types of user so that Zarafa is very popular among its clients. The look provided by the both email service provides is same. Zarafa also provides many other facilities to its users. It utilizes the open source database MySQL, where data like emails, contacts, and schedules are stored as records within tables. For user’s information, this email client uses InnoDB as storage engine that employs the two files: .ibdata and .frm.
Some common tables created in Zarafa database are given bellow:
- Users table
- Properties table
- Acl table
- Lob (large objects) table
- Usergroup_acl table
- Outgoingqueue table
When you get unable to access stored information and face any error or any abnormal behavior of the application, then it is sure that Zarafa database gets corrupt or damaged due to whatever reason. After corruption it displays various error messages when user tries to access the corrupted database:
“one row in innodb corrupt”
The causes of Zarafa database corruption may comprise any of the following:
- Virus/Trojan and other malware infections
- Power surges
- Damaged/Corrupted file system
- Software malfunctioning
- Improper termination of application
- If any hardware device gets faulty on network
- Damaged hard disk
- Corruption of File header
In order to fix such types of error a professional Zarafa Database recovery tool is recommended by many professionals because this tool is reliable and powerful. It is also very simple to use because it provide very simple user interface and one can operate it without need of any professional instruction.
Other problems occur when a database is not tuned. If you haven’t installed Zarafa then you first require optimizing the MySQL configuration. Add or Modify the following given settings to the configuration file to tune MySQL:
innodb_log_buffer_size = 32M
max_allowed_packet = 16M
max_connections = 500
If you have an existing Zarafa system then tunes it as follows:
- Take a backup of your database
- Stop the process of Zarafa server
- Wait until the process gets completed and verify it if MySQL transaction logs are not present.
- Stop MySQL server.
- Make sure that Shutdown system has been executed by MySQL through the logs.
- In /etc/my.cnf, change innodb settings.
- Transfer the old ib_logfiles from mysql datadir to /tmp.
- Start MySQL.
- If the changes were made to innodb_log_file_size, check it.
- Do a check for errors in MySQL logs.
- Start Zarafa server process.
By executing the above given step you will tune your existing Zarafa environment. But it is necessary to execute the above step under the moderation of any professional to avoid unwanted issues.