Since this error occurs after loading and backup is completed, the resulting database is complete and can be safely used. Two things that should happen but are prevented by this issue:
The backup is not registered in the admin db, leading to an "unknown" snapshot record
Older backups are not pruned (but will be after this issue is resolved)
Release 0.3.1's backup administration can be flaky, due to the lack of an explicit close method on the RocksDB connection.
See this upstream issue: https://github.com/twmht/python-rocksdb/issues/10 It was nearly fixed, but the merged PR can be unreliable: https://github.com/twmht/python-rocksdb/pull/40
Since this error occurs after loading and backup is completed, the resulting database is complete and can be safely used. Two things that should happen but are prevented by this issue: