Zimbra Next Generation Modules/DR/Disaster Recovery - MariaDB data loss or corruption: Difference between revisions

(Step 1 completed)
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
WORK IN PROGRESS
#REDIRECT [[Zimbra_NG_Modules/DR/Disaster_Recovery_-_MariaDB_data_loss_or_corruption]]
 
=Introduction=
This step-by-step guide contains all the information needed to restore lost or corrupted MariaDB data. It applies to both single-server and multi-server infrastructures with only a single MariaDB server.
 
=Step 1: Database re-initialisation=
The first step in order to restore the database to a consistent state is to re-initialise the database itself to its initial state.
 
To do this:
* Stop all services by running <code>zmcontrol stop</code> as the zimbra user.
* Rename *or* empty the current Database folder - default <code>/opt/zimbra/db/data/</code>
** Rename: <code>mv /opt/zimbra/db/data/ /opt/zimbra/db/data_old/</code>
** Empty: <code>rm -rf /opt/zimbra/db/data/*</code>
* After cleaning up the database, re-initialise it by running <code>/opt/zimbra/libexec/zmmyinit</code> as the zimbra user:
<pre>
* Creating required directories
* Generating mysql config /opt/zimbra/conf/my.cnf
* Creating database in /opt/zimbra/db/data
* Starting mysql server
* Loading schema /opt/zimbra/db/db.sql
* Loading version from /opt/zimbra/db/versions-init.sql
* Loading version from /opt/zimbra/db/backup-version-init.sql
* Setting random passwd for mysql root user in zimbra localconfig
* Setting random passwd for mysql zimbra user in zimbra localconfig
* Changing mysql root user password
* Changing mysql zimbra user password
* Changed zimbra mysql user password
</pre>
Database passwords as well as mailbox IDs will not be changed.
* After re-initialising the database, start all services by running <code>zmcontrol start</code> as the zimbra user
 
If everything succeeded, after all services are initialised you should see that mailboxgroups have been created anew:
<pre>
ls -la /opt/zimbra/db/data/
total 1099868
drwxr-x--- 16 zimbra zimbra      4096 Aug 28 12:09 .
drwxrwxr-x  3 zimbra zimbra      4096 Aug 25 18:03 ..
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 chat
-rw-rw----  1 zimbra zimbra 524288000 Aug 28 12:11 ib_logfile0
-rw-rw----  1 zimbra zimbra 524288000 Aug 28 12:03 ib_logfile1
-rw-rw----  1 zimbra zimbra  77594624 Aug 28 12:11 ibdata1
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup1
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup2
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup3
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup4
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup5
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup6
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup7
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup8
drwx------  2 zimbra zimbra      4096 Aug 28 12:09 mboxgroup9
-rw-rw----  1 zimbra zimbra        0 Aug 28 12:03 multi-master.info
drwx------ 2 zimbra zimbra      4096 Aug 28 12:03 mysql
drwx------  2 zimbra zimbra      4096 Aug 28 12:03 performance_schema
-rw-rw----  1 zimbra zimbra    24576 Aug 28 12:03 tc.log
drwx------  2 zimbra zimbra      4096 Aug 28 12:03 test
drwx------  2 zimbra zimbra      4096 Aug 28 12:03 zimbra
</pre>
=Step 2: Data Restore=
 
=Step 3: Volume Deduplication=

Latest revision as of 12:16, 29 November 2017

Jump to: navigation, search