Re: Manual Backup & Restore Procedures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

Quoting peter@xxxxxxxxxxxxxxx:

Nightly backups is going to be our approach for now. We may add a replicated server at a later date, but not now.

You're right, I didn't word my question well. I'm looking for a clear list of which files need to be backed up/restored. The closest I've seen in the docs is: https://www.cyrusimap.org/imap/download/upgrade.html#backup-and-copy-existing-data


You need the backup most of folders configured (or the default path) in imapd.conf

The most important folder are the ones cofigured by the following options.
- configdirectory:
- partition-*
- sievedir:
And if configured
- metapartition-*
- archivepartition-

Also, is restoring as simple as (1) stop cyrus, (2) restore files, (3) start cyrus? Are there any additional steps required when starting cyrus after restoring the filesystem?

Depending on your type of backup and if it is a partial or complete restore you will need a step between 2 and 3 to restore some databases (mailboxdb, quota, search indices).
Most important command is "reconstruct"

To go back to your broader question:

For Cyrus-Backup there are different solutions, depending on your scenarions, needs and ressources

1. "expunge_mode: delayed" and "delete_mode: delayed" imapd.conf options will delay the removal of mails and folders from the filesystem for some time and allow them to be restored by an admin. This also allows other backup solutions to catch mails that have been receivend and deleted between
   two backup runs

   Pro: easy to use, solves most "user deleted mails/folder by accident"
   Con: does not help in case of disk error corruption or disaster recovery

2. File Based incremental Backup solutions with/without snapshots

   Pro: can do disaster recovery, can use cheep storage
   Con: slow backup/restore (heavy IO load)
        can miss mails received and deleted between backups

3. Cyrus Replication

   Pro: fast disaster recovery and easy failover for maintanace
   Con: need of "standby" system (twice the storrage), no

4. Cyrus Replication-Backup

I have not used this backup system jet. But form my understanding is it a combination of
   Cyrus-Replication and Delayed expunge.

From my understanding of the documentation this brings faster backup/restore as file based backup,
   but requires nearly as much resources as cyrus replication.


On our Servers we us a combination of the first 3 options.
1. Recovery of deleted folders/mails for 30 Days (delayed expunge)
2. Recovery of deleted folders/mails 31-90 Days (file base backup)
3. Maintenace/Disaster Recovery (Cyrus Replication)







--------------------------------------------------------------------------------
Michael Menge                          Tel.: (49) 7071 / 29-70316
Universität Tübingen                   Fax.: (49) 7071 / 29-5912
Zentrum für Datenverarbeitung mail: michael.menge@xxxxxxxxxxxxxxxxxxxx
Wächterstraße 76
72074 Tübingen


------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T144a76b1af41bdee-Mc45d577496f36dbec33b88e2
Delivery options: https://cyrus.topicbox.com/groups/info/subscription




[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux