ZCS Administrator Guide 8.0
ZCS Administrator Guide 8.0
Network Edition


Backup and Restore > Restoring from Different Failure Scenarios

Restoring from Different Failure Scenarios
The restoration steps are similar for most server failures you may encounter. If a failure occurs, review the disaster recovery section to understand the process and then follow the steps below for the specific type of failure.
Restore When LDAP is Corrupted
1.
2.
Find the label for the LDAP session to restore. Run the zmrestoreldap -lb <label> command, with no arguments to restore all accounts, domains, servers, COS, etc. for the LDAP server.
3.
Restore After Replacing Corrupted Partitions
1.
2.
zmrestore -a all
The zmrestore process automatically retrieves the list of all mailboxes on the specified mail host from the backup date and iterates through each mailbox to restore the mailboxes to the last known good state.
Restore After Corrupted or Unreadable Redo Log
If the redo log becomes unreadable, the mailboxd service stops and cannot restart. If this happens, inspect the hardware and software to find the source of the problem before proceeding.
Without the latest redo log, the Zimbra mailbox server cannot be returned to the most current state. The Zimbra mailbox data can be restored to the latest archived redo log state. A new redo log for current transactions is created after the Zimbra mailbox server is restored.
Important: The mailboxd service must not be running, and all accounts must be in maintenance mode before beginning.
1.
zmprov md <domain> zimbraDomainStatus maintenance
2.
zmrestoreoffline
The offline restore process begins by retrieving the list of all mailboxes on the specified mail host from the backup.
The offline restore than iterates through each mailbox to:
Restore all incremental backups for that mailbox in order, since the last full backup. This involves replaying the redo logs from the backup target area
Because the redo log for current transactions is not available, the mailbox server is returned to the state of the last archived redo log.
3.
zmcontrol startup
4.
When the Zimbra mailbox server is up, run a full backup of the Zimbra server. The full backup must be run immediately to have the latest data backed up, because the latest redo log is not available.
Copyright © 2012 VMware Inc.