Zimbra Collaboration Administrator Guide

Zimbra Mailbox Server

Backing Up the Mailbox Server

Zimbra Collaboration includes a configurable backup manager that resides on every Zimbra Collaboration server and performs both backup and restore functions. You do not have to stop the Zimbra Collaboration server in order to run the backup process. The backup manager can be used to restore a single user, rather than having to restore the entire system in the event that one user’s mailbox becomes corrupted. Full and incremental backups are in /

opt/ zimbra/backup

. See Chapter 16, Backup and Restore.

Each Zimbra mailbox server generates redo logs that contain current and archived transactions processed by the message store server since the last incremental backup. When the server is restored, after the backed up files are fully restored, any redo logs in the archive and the current redo log in use are replayed to bring the system to the point before the failure.

Mailbox Server Logs

A Zimbra Collaboration deployment consists of various third-party components with one or more mailbox servers. Each of the components may generate its own logging output. Local logs are in

/opt/zimbra/log

.

Selected Zimbra Collaboration log messages generate SNMP traps, which you can capture using any SNMP monitoring software. See

Chapter 15,

Monitoring ZCS Servers.

Note: System logs, redo logs, and backup sessions should be on separate disks to minimize the possibility of unrecoverable data loss in the event that one of those disks fails.

Zimbra Collaboration Network Edition 39

Administrator Guide

40 Network Edition Zimbra Collaboration