just as we had it configured before with Zarafa Bricklevel Backup, we’ve cronjob’ed 2x daily + 1 week- and monthly Kopano Backups.
We’ve noticed the following:
- the backup process is painfully slow and causes varios alerts in Nagios and Veeam because of the high CPU load. Multi-Core is disabled at the moment because this really brought down the whole server (Debian/UCS virtual 4-Core [Host: Xeon E5645] with 8 GB RAM, 15 Clients). No application whatsoever has managed to do this 'till now. Now since the first full backups have gone through, the load only lasts for a few seconds. Still - it doesn’t seem to be decent.
- One one account, the Backup logs fatal errors but continues. It doesn’t seem to be able to handle the “Conversation Action Settings”, “Einstellungen fÃŒr QuickSteps”, “Einstellungen fÃŒr Unterhaltungsaktionen” and one folder containing very old mail archives. I can’t find the culprit messages with Microsoft tools. See the log below:
2017-01-30 23:00:14,688 - backup0 - INFO - backing up folder: Conversation Action Settings 2017-01-30 23:00:14,843 - backup0 - ERROR - Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 4227, in log_exc try: yield File "/usr/lib/python2.7/dist-packages/kopano_backup/__init__.py", line 567, in dump_rules etxml = ElementTree.fromstring(ruledata) File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1301, in XML parser.feed(text) File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1643, in feed self._raiseerror(v) File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1507, in _raiseerror raise err ParseError: not well-formed (invalid token): line 1, column 0
I’d be happy to debug this if someone could guide me!