ZCS88-zxbackup-Disaster-Recovery: Difference between revisions
No edit summary |
|||
Line 115: | Line 115: | ||
</pre></code> | </pre></code> | ||
At this point, you should be up and running; however, as an option, you may want to check the user BLOBs, you can refer to this [https://wiki.zimbra.com/wiki/ZCS88-zxbackup-Missing-BLOB guide]. | At this point, you should be up and running; however, as an option, you may want to check the user BLOBs, you can refer to this [https://wiki.zimbra.com/wiki/ZCS88-zxbackup-Missing-BLOB guide].<br> | ||
==<font size="6">Scenario II - Single Server with corrupted mysql beyond repair</font>== | |||
You have been running ZCS-88 using the Next Generation Suite, and you have just discovered a lot of errors in the /opt/zimbra/mysql_error.log file<br> |
Revision as of 18:46, 24 August 2017
Scenario I - Single Server
You have been running ZCS-88 using the Next Generation Suite, and you have a dedicated disk for /opt/zimbra/, something like...
/dev/mapper/vg_zcs-lv_root
xxG xxxG xxG xx% /
tmpfs /dev/shm
/dev/sda1 /boot
/dev/sda2 /opt/zimbra/
But something has happened to the server node, effecting the operating system, which will require a reinstall of the operating system, and ZCS-88.
Reinstall the Operating System
When you reinstall the operating system, make sure the disk containing /opt/zimbra/ is not mounted yet.
Reinstall ZCS-88 with Next Generation Modules
When you are ready to reinstall ZCS-88, make sure the /opt/zimbra/ is now mounted.
If it's possible, rename your production /opt/zimbra/ directory.
mv /opt/zimbra/ mv /opt/zimbraSAVE/
Now, run the installer as the root user using the software option.
./install.sh -s
*OR*
./install.sh --software
During the ZCS-88 Software Reinstall
Observe at the end of the software install, you will see the following
Running Post Installation Configuration:
Software Installation complete!
Operations logged to /tmp/install.log.SviTipi8
Now observe, you have two zimbra directories
drwxr-xr-x 30 root root 4096 Aug 24 14:29 zimbra
drwxr-xr-x 30 root root 4096 Aug 17 13:20 zimbraSAVE
Since the software install had created the /opt/zimbra/ directory, lets move it out of the way
mv /opt/zimbra/ /opt/zimbraSOFTWARE_INSTALL/
Now, lets put our production directory back into place
mv /opt/zimbraSAVE/ /opt/zimbra/
After putting your production /opt/zimbra/ directory back into place, switch to the zimbra account, and start Zimbra
su - zimbra
zmcontrol start
Host test3.zextras.local
Starting ldap...Done.
Starting zmconfigd...Done.
Starting logger...Done.
Starting convertd...Done.
Starting mailbox...Done.
Starting memcached...Done.
Starting proxy...Done.
Starting amavis...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting opendkim...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
Starting service webapp...Done.
Starting zimbra webapp...Done.
Starting zimbraAdmin webapp...Done.
Starting zimlet webapp...Done.
Starting imapd...Done.
Check the status
zmcontrol status
Host test3.zextras.local
amavis Running
antispam Running
antivirus Running
convertd Running
imapd Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Running
opendkim Running
proxy Running
service webapp Running
snmp Running
spell Running
stats Running
zimbra webapp Running
zimbraAdmin webapp Running
zimlet webapp Running
zmconfigd Running
At this point, you should be up and running; however, as an option, you may want to check the user BLOBs, you can refer to this guide.
Scenario II - Single Server with corrupted mysql beyond repair
You have been running ZCS-88 using the Next Generation Suite, and you have just discovered a lot of errors in the /opt/zimbra/mysql_error.log file