Corrupted db when data files are copied in

Greg_Stewart · May 26, 2023, 1:12am

Hey guys! I’m sure there is a straightforward solution, I’m running a Mongodn service thusly:

Epic-Breakfast-Productions/OpenQuarterMaster/blob/e213b73c0a93cad99f4c816cf73fae62b73deb02/software/Infrastructure/mongo/open+quarter+master-infra-mongodb.service

# Service file for running an instance of MongoDB.
#  Author: Greg Stewart
#  https://www.freedesktop.org/software/systemd/man/systemd.service.html
#
#  Mongo tags: https://hub.docker.com/_/mongo?tab=tags
#
#  TODO:: figure out better username/password situation
#    - https://lzone.de/blog/Using-Linux-keyring-secrets-from-your-scripts
#
# TODO:: Figure out what's wrong on first run to cause issues with base station complaining about not being primary or secondary

[Unit]
Description=Mongo server for Open Quartermaster. Version ${version}, using MongoDB tagged to "4".
Documentation=https://github.com/Epic-Breakfast-Productions/OpenQuarterMaster/tree/main/software/Infrastructure
After=docker.service
Wants=network-online.target docker.socket
Requires=docker.socket

[Service]
Type=simple

This file has been truncated. show original

I’m having docker map the host’s /data/oqm/db/mongo/ directory, and looks like this works fine; looking from the host I see the directory populated when run. This setup seems to work fine between restarts and persists fine.

However, when I try backing up and restoring the data by copying the data in this directory out then back in (while the mongo service isn’t running), when trying to bring the service back up, Mongo barfs, claiming the data is corrupted. Any ideas?

I am trying this method as described: https://www.mongodb.com/docs/manual/core/backups/#back-up-with-cp-or-rsync