Hello,
I'm trying to configure backupd in rolling mode as a final setup.
Running a first backup on few users
sync_client -A -n bck -z -v -v
after a while the process die with:
cyrus/sync_client[9540]: MESSAGE received NO response:
IMAP_PROTOCOL_ERROR Protocol error
cyrus/sync_client[9540]:
Hi Marco,
On Thu, Jun 18, 2020, at 10:19 PM, Marco wrote:
> Hello,
>
> I'm trying to configure backupd in rolling mode as a final setup.
> Running a first backup on few users
>
> sync_client -A -n bck -z -v -v
>
> after a while the process die with:
>
> cyrus/sync_client[9540]: MESSAGE rece
Hi Ellie,
Il 19/06/2020 03:01, ellie timoney ha scritto:
I think you might need to add the usual recover entry to the START section:
recover cmd="ctl_cyrusdb -r"
I notice this is missing from the backups documentation -- please let me know
if it this sorts it out, and I'll fix it
Hi Marco,
On Fri, Jun 19, 2020, at 6:44 PM, Marco wrote:
> wow, yes, it works. With this config, after the Cyrus restart the
> mailboxes.db and the skipstamps dbs are created and the error disappears
> from syslog.
Great! I've updated the documentation, and the website should update shortly.
>
Hello,
On 22/06/2020 03:29, ellie timoney has written:
[...]
So like, maybe a user has deleted some stuff, and you don't want to mess around figuring out which
individual messages they need restored, so you just want to restore everything, and let the user
figure it out. This is what -x is fo
> I think there isn't a all-in-one command for this use case: a user
> expunged some messages and deleted some folders somewhere. I want to
> recover all expunged messages and all the deleted folders which are no
> more present in the original IMAP server (because they were expired from
> cyr_e
On 19/06/2020 03:01, ellie timoney has written:
Rolling mode only makes incremental updates, so if you're starting from a
server that already has existing data, you should do the first manual initial
backups before enabling the rolling mode.
Hello,
about this error, I retried more times. It
On Wed, Jul 1, 2020, at 11:57 PM, Marco wrote:
> Uhm...
Wow, that's wierd.
I notice that the users that worked correctly with "sync_client -A" don't have
dots in their address localparts. If you create another user that also has a
dot, does it fail under -A in the same way?
Does it fail in th
Hello,
On 03/07/2020 05:08, ellie timoney has written:
I notice that the users that worked correctly with "sync_client -A" don't have
dots in their address localparts. If you create another user that also has a dot, does
it fail under -A in the same way?
I copied the content of the failing
Hi Marco,
On Tue, Jul 7, 2020, at 12:17 AM, Marco wrote:
> I copied the content of the failing mailbox into another mailbox with a
> name without dots:
Oh that's very curious. It suggests that something about the mailbox contents
is causing it to fail under -A but not under -u. I was hoping i
Hi Ellie,
On 08/07/2020 06:23, ellie timoney has written:
Oh that's very curious. It suggests that something about the mailbox contents
is causing it to fail under -A but not under -u. I was hoping it would just be
the dot in the name, cause something like that should be fairly easy to
repr
11 matches
Mail list logo