Bug 463230
| Summary: | RFE: CRM #1375564 'Cyrus database backup and checkpoint features not well documented' | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Daniel Riek <riek> |
| Component: | cyrus-imapd | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE <qe-baseos-auto> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.3 | CC: | dkovalsk, riek, rvokal, syeghiay, tao |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-22 18:16:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 246473 | ||
| Bug Blocks: | |||
|
Comment 1
Ivana Varekova
2008-11-13 12:28:57 UTC
This bugzilla was reviewed by QE as a non-FasTrack request. It has since been proposed for FasTrack. The qa_ack has been reset. QE needs to re-review this bugzilla for FasTrack. I'm still trying to get some answers, but there are no sources. Actual result: > o Listing of database files "checkpointed" Checkpointed are these databases (under dbdir=/var/lib/imap): quotas.db tls_sessions.db deliver.db statuschache.db annotations.db mailboxes.db ptclient/ptscache.db > o Description of checkpoint format > - "ls /var/lib/imap" suggest two sets of checkpoint database are retained. I don't completely understand this question??? AFAIK there are two types of databases (depends on backends). > - Description of checkpoint configuration options, if any, to control checkpoint sets only configuration option for checkpoint is interval of checkpoints. /etc/cyrus.conf : checkpoint ..... period=30 > o Checkpointed image backup requirements Not exactly sure what you mean here. AFAIK you only need the database in db.backup{1,2} - it's rotated. > o Appropriate cross-references to utilities used to determine > database corrution requiring recovery proceadure I'm not sure there really exists such a thing despite the list archives. Cyrus runs a -r when it starts to verify the database. So it seems, it's regular job when starting cyrus. /etc/cyrus.conf START { # do not delete this entry! recover cmd="ctl_cyrusdb -r" > o Appropriate recovery procedure when invocation > with "-r" vs. "-r -x' is required. I think -x is needed only for debugging purposes. I wasn't able to find/get any info about this. Only someone used '-r -x' when only '-r' hanged. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1120.html |