Re: Cyrus doesn't preserve hard-links on replication

2019-11-18 Thread Adrien Remillieux
By shuffling the keywords on my google searches I was able to find this: https://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-March/021405.html Apparently there is a few settings to set to avoid copying the same message multiple times. This would be a nice addition to the cyrus docs on replicati

Re: Cyrus backups and deleted (users, mailboxes)

2019-11-18 Thread Deborah Pickett
But without rolling replication, or with mailboxes that were already DELETED.* before the backup service was configured, I'm not sure what to expect. I'm not sure if this is a case that I considered and did something for, but have since forgotten about, or if it's a case that I hadn't consid

Re: Cyrus doesn't preserve hard-links on replication

2019-11-18 Thread Adrien Remillieux
Sorry for the multiples emails... The option "provide_uuid=1" I found in my last message seems to be unrecognized by cyrus now (It's probably on by default). It's probably only useful for new messages anyway. So I'm back to square one and my google-fu failed me. If someone know how to solve that p

Re: Backup compaction optimization in a block-level replication environment

2019-11-18 Thread Deborah Pickett
Food for thought. Maybe instead of having one "%SHARED" backup, having one "%SHARED.foo" backup per top-level shared folder would be a better implementation? I haven't seen shared folders used much in practice, so it's interesting to hear about it. Looking at your own data, if you had one "%S