cies or restore a -1hr backup would not be
an acceptable policy for this type of data.
Regards,
Anatoli
*From:* Andrew Morgan
*Sent:* Friday, May 11, 2018 02:05
*To:* Anatoli
*Cc:* Info-cyrus
*Subject:* Re: Backup methods
On Fri, 11 May 2018, Anatoli wrote:
There may be an argument that could be m
On Fri, 11 May 2018, Anatoli wrote:
There may be an argument that could be made for 2 backup stratagies
That's the point. In the context of SME environments (Small and Medium-sized
Enterprises, i.e. from 5 to 50 employees normally, up to 250 in some
countries) that we were talking about, a r
ts is just the most
obvious use-case. There could be others... up to the admin to decide.
*From:* Alvin Starr
*Sent:* Thursday, May 10, 2018 23:55
*To:* Info-cyrus
*Subject:* Re: Backup methods
On 05/10/2018 06:29 PM, Anatoli wrote:
Actually, mysqldump performs a lock on the records it'
Backup for 100 users has different requirements than backup for 10
users so why not support a few different backup strategies.
*From:* Jason L Tibbitts Iii
*Sent:* Thursday, May 10, 2018 18:41
*To:* Anatoli
*Cc:* Info-cyrus
*Subject:* Re: Backup methods
"A" == Anatoli writes:
A&
;cat > /bkp/`date +%y%m%d_%H%M`.sql.xz". With a couple
of pipes more you can encrypt the data on the fly so it's secure to
store it in a cheap VPS overseas... or you could upload it to dropbox.
*From:* Jason L Tibbitts Iii
*Sent:* Thursday, May 10, 2018 18:41
*To:* Anatoli
*Cc:* In
> "A" == Anatoli writes:
A> What about mysqldump > dump.sql, then mysql < dump.sql? Also a wrong
A> way and didn't have to be implemented?
No, that's exactly my point. Thanks for making it for me! The analog
to the way you indicated that you would like it to work would be having
the mysql
d (like cron mysqldump
--routines --all-databases | xz -9 > /bu/`date
+%y%m%d_%H%M`_full.sql.xz), though there are replication solutions
available too. The Unix way is about minimalist, modular software.
*From:* Jason L Tibbitts Iii
*Sent:* Thursday, May 10, 2018 16:38
*To:* Anatoli
*Cc:* Info-cy
something like
1 min.
*From:* Albert Shih
*Sent:* Thursday, May 10, 2018 17:32
*To:* Anatoli
*Cc:* Info-cyrus
*Subject:* Re: Backup methods
Le 10/05/2018 à 10:38:28-0300, Anatoli a écrit
Not very sure to understand that. It's always true isn't ? If you have XTo of
data and y
Le 10/05/2018 à 16:08:32-0300, Anatoli a écrit
Hi.
> In both cases, a copy of the master data is made, which requires twice the
> space of real usage (Cyrus Backups tries to apply compression on stored data,
> not sure how well it works).
In ZFS with lz4 (standard compression on ZFS) you got 1.1
Le 10/05/2018 à 10:38:28-0300, Anatoli a écrit
> > Not very sure to understand that. It's always true isn't ? If you have XTo
> > of
> data and you want n backups you will need X*(n+1) To ?
>
> The replication as it is designed means that you create an additional
> (replica)
> instance of Cyrus t
> "A" == Anatoli writes:
A> What you mention is highly related to the replication backup
A> we were talking about in the previous mails.
Well, sort of. It is a method that is actually focused around doing
backups. It happens to make use of the replication protocol because
that is actually
be in the exact same state as when the backup
took place. This is discussed in the github issue mentioned in the
previous mail.
*From:* Jason L Tibbitts Iii
*Sent:* Thursday, May 10, 2018 14:10
*To:* Arnaldo Viegas De Lima
*Cc:* Info-cyrus
*Subject:* Re: Backup methods
Cyrus does have an integrate
Cyrus does have an integrated backup system (see
https://cyrusimap.org/imap/reference/admin/backups.html) which I'm not
sure has been mentioned in this thread. But you still have to have
enough space to keep the compressed backups on disk in order to move
them to tape or whatever archival storage
One alternative, if you are running VMs (such as VMWare or Hyper-V) is resort
to a VM backup program that will uses native change tracking (VMWare CBT and
Hyper-V RCT). This allows for a consistent and incremental backup of the VM’s.
It’s quite fast and saves lots of space. The backup is increm
elivery attempt will occur, etc.), never turn
off your incoming MTA.
*From:* Albert Shih
*Sent:* Thursday, May 10, 2018 04:14
*To:* Anatoli
*Cc:* Info-cyrus
*Subject:* Re: Backup methods
Le 10/05/2018 à 02:44:18-0300, Anatoli a écrit
Hi,
The replication is reasonable only if you have more th
Le 10/05/2018 à 02:44:18-0300, Anatoli a écrit
Hi,
>
> The replication is reasonable only if you have more than one server in your
> deployment (and both servers with the same level of security, if not you risk
> to compromise the user data) or "spool size/available disk space" is low,
> otherwis
enbach Via Info-cyrus
*Sent:* Wednesday, May 09, 2018 06:42
*To:* Info-cyrus
*Subject:* Re: Backup methods
Am Mittwoch, 9. Mai 2018, 11:19:54 CEST schrieb Albert Shih:
I would like to know what's kind of backup method are recommended for
cyrus-imapd.
My cyrus-imapd host (only one currently) a
Le 09/05/2018 à 11:42:35+0200, Niels Dettenbach a écrit
> Am Mittwoch, 9. Mai 2018, 11:19:54 CEST schrieb Albert Shih:
>
> This is relatively inefficient, but a working option if anything from cyrus
> data is on that VM - i.e. the complete mail spool and the database files
> (possibly plus sieve fi
Am Mittwoch, 9. Mai 2018, 11:19:54 CEST schrieb Albert Shih:
> I would like to know what's kind of backup method are recommended for
> cyrus-imapd.
>
> My cyrus-imapd host (only one currently) are running under FreeBSD jail
> (something like systemd-nspawn, lxc) & ZFS so I'm intend to use this
> m
19 matches
Mail list logo
