Kopano-backup errors



  • I’ve recently upgraded from ZCP to Kopano 8.3.0 and I’m working out the kinks in the new backup system.

    First: I found that a worker_processes of 1 in the backup.cfg file took a ridiculous amount of time to complete. and 20 maxed out the box and made it un-usable. I finally settled on 10 which puts a heavy load on the server, but in the middle of the night, I don’t care.

    Second: I find that after I start the backup, even after the process appears to end, there at 10 additional kopano-backup threads running in the background - always.

    Third: I see these errors constantly in the backup.log file??

    2017-05-30 09:47:43,239 - backup8 - ERROR - Too many retries, skipping change
    2017-05-30 09:47:43,285 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
    2017-05-30 09:47:49,721 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
    2017-05-30 09:47:56,160 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
    2017-05-30 09:48:02,598 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)
    2017-05-30 09:48:09,042 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=4/5)
    2017-05-30 09:48:15,475 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=5/5)
    2017-05-30 09:48:21,882 - backup8 - ERROR - Too many retries, skipping change
    2017-05-30 09:48:21,912 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
    2017-05-30 09:48:28,389 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
    2017-05-30 09:48:34,835 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
    2017-05-30 09:48:41,284 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)
    2017-05-30 09:48:47,735 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=4/5)
    2017-05-30 09:48:54,182 - backup8 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=5/5)
    

    Fourth: I’ve found that the kopano-backup executable doesn’t seem to work like the MAN page says it should. For instance:

    kopano-core:~# kopano-backup --help
    Usage: kopano-backup [PATH] [options]
    kopano-core:~# kopano-backup /srv/backup/brick-level-backup/
    Traceback (most recent call last):
      File "/usr/sbin/kopano-backup", line 6, in <module>
        sys.exit(kopano_backup.main())
      File "/usr/lib/python2.7/dist-packages/kopano_backup/__init__.py", line 703, in main
        assert len(args) == 0, 'too many arguments'
    AssertionError: too many arguments
    

    I guess I’m wondering what those errors mean? Why is the backup threads running forever? And am I doing something wrong?


  • Kopano

    Hi @robertwbrandt,

    @robertwbrandt said in Kopano-backup errors:

    First: I found that a worker_processes of 1 in the backup.cfg file took a ridiculous amount of time to complete. and 20 maxed out the box and made it un-usable. I finally settled on 10 which puts a heavy load on the server, but in the middle of the night, I don’t care.

    yes, it was the same with the old zarafa-backup. it uses one thread by default. the amount of threads you can use depends on your hardware, amount of users and configuration of server.cfg, so its hard to give a general recommendation.

    @robertwbrandt said in Kopano-backup errors:

    Second: I find that after I start the backup, even after the process appears to end, there at 10 additional kopano-backup threads running in the background - always.

    please contact our support for this, since you have a subscription

    @robertwbrandt said in Kopano-backup errors:

    Third: I see these errors constantly in the backup.log file??

    please contact our support for this, since you have a subscription

    @robertwbrandt said in Kopano-backup errors:

    Fourth: I’ve found that the kopano-backup executable doesn’t seem to work like the MAN page says it should. For instance:

    the path is needed when items should be restored from an existing set only. please have a look at the examples at the end of the man page, to see if this clears things up for you.


Log in to reply
 

Looks like your connection to Kopano Community Forum was lost, please wait while we try to reconnect.