Chuck Swiger <[EMAIL PROTECTED]> wrote:

> Bill Moran wrote:
> > Christian Laursen <[EMAIL PROTECTED]> wrote:
> >> If you are running FreeBSD 5, you should be able to make a filesystem snapshot
> >> and rsync from there.
> > 
> > I suppose I should have commented on that ;)
> > 
> > We're not running FreeBSD 5 on these production machines yet ... but it's
> > likely we will be soon, so I'm considering using snapshots.
> > 
> > To my understanding, we still have to stop Cyrus while the snapshot is
> > being created (to ensure consistency) but since a snapshot takes a lot
> > less time than an rsync, this should be a big improvement.  Once the
> > snapshot is created, rsync can take as long as necessary.
> No, snapshots can be taken without significantly interrupting running 
> processes, although I'm not sure how long filesystem access gets blocked while 
> creating the snapshot.  You could also detach a RAID-1 mirror of the data 
> (using vinum, ccd, whatever) and backup that, and then re-attach and resync 
> the mirror drive to the live volume.
> Both of these methods make taking a very current backup easy; they do not 
> provide live replication of the data, however.

Sort of.

The Cyrus docs recommend this, with the warning that "you can potentially have
a couple of inconsistent mailboxes in the snapshot"  Me, I'd rather risk 5
minutes of Cyrus being down in the middle of the night than risk an
inconsistent backup.  Knowing my luck, the inconsistent part would be the
one folder that causes a big stir when it can't be restored.

I figure, if a snapshot takes (let's say) 20 seconds to complete.  You stop
cyrus, take the snapshot, then restart Cyrus ... you can then take all the
time you need to backup from the snapshot.  You're looking at less than 5
minutes fo downtime.  In our case, our customers are mostly regional, so
doing this at 2:00 AM shouldn't disrupt much.

Bill Moran
Potential Technologies
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to