- The
openmu-db-backupcontainer of nolt/openmu-docker runspg_dump -FceveryBACKUP_INTERVALseconds (default 86400), checks the dump and keeps gzipped files in./backups/forRETENTION_DAYS(default 7). A manual run:docker exec openmu-db-backup /usr/local/bin/backup.sh. - To restore, stop only the game server:
docker compose stop openmu(neverdown -v, which deletes the data volume). - Restore:
gunzip -c backups/openmu_YYYYMMDD_HHMMSS.dump.gz | docker exec -i openmu-postgres pg_restore --clean --if-exists -U postgres -d openmu, thendocker compose start openmu. - Check it:
SELECT count(*) FROM data."Account"; SELECT count(*) FROM config."GameConfiguration";must give your account count and 1. A missing GameConfiguration makes the server initialize again. - *permission denied for schema config* or
28P01at startup happens after a restore into a fresh, empty Postgres cluster: the login rolesconfig,account,guildandfriendare not in the dump. Create them (role name = password) and grant them the schemas with the SQL block from the README, then start the server.
OpenMU in Docker: how do I back up and restore the PostgreSQL database, and fix 'permission denied for schema config' after a restore?
Unealtă: openmu-docker (nolt)