Hey, lately I am evaluating Bareos for our NDMP backup to tape. I have several jobs which back up data from our storage via NDMP.
Over the weekend I ran some tests and received following errors: The first one: 10-Sep 17:06 bareos-dir JobId 17: Fatal error: ndmp_fhdb_lmdb.c:188 Unable insert new data at 5341351560: MDB_MAP_FULL: Environment mapsize limit reached Multiple of these messages: 10-Sep 17:06 bareos-dir JobId 17: Fatal error: ndmp_fhdb_lmdb.c:188 Unable insert new data at 5318666995: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid And multiple of these messages: 10-Sep 17:07 bareos-dir JobId 17: Fatal error: ndmp_fhdb_lmdb.c:336 Unable get old data: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid This happened for 2 jobs out of 7. And those 2 jobs did not fail and were still running an writing data on tapes. I have to say that every job has to back up a lot of data (over 40TB). They all are running at the same time each using one drive of a tape library (autochanger). My first guess would be that it has something to do with this job directive: File History Size = <Size64> (default: 10000000) But I am not quit sure what this directive does but if this would be the problem I would have expected to see these errors on every job. It would be nice if someone can help me understand where these errors come from and how I could fix them. Please let me know if you need more information regarding these errors. I will continue testing and keep you updated. Cheers Yannic -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
