Community AlphaAlpha MUADMINS
ESEspañol
Iniciar sesión
En MuADMINSConfig ScannerSube el zip de tus archivos: rates, drops, spots, límitesAbrirEn MuADMINSEncuéntranos en DiscordPide ayuda, comparte lo que estás creando y habla de MU con otros dueños de servidores.Abrir
← Todas las soluciones

OpenMU in Docker: how do I back up and restore the PostgreSQL database, and fix 'permission denied for schema config' after a restore?

Escrito por MuADMINS a partir de la fuenteNot verified

Herramienta: openmu-docker (nolt)

  1. The openmu-db-backup container of nolt/openmu-docker runs pg_dump -Fc every BACKUP_INTERVAL seconds (default 86400), checks the dump and keeps gzipped files in ./backups/ for RETENTION_DAYS (default 7). A manual run: docker exec openmu-db-backup /usr/local/bin/backup.sh.
  2. To restore, stop only the game server: docker compose stop openmu (never down -v, which deletes the data volume).
  3. Restore: gunzip -c backups/openmu_YYYYMMDD_HHMMSS.dump.gz | docker exec -i openmu-postgres pg_restore --clean --if-exists -U postgres -d openmu, then docker compose start openmu.
  4. 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.
  5. *permission denied for schema config* or 28P01 at startup happens after a restore into a fresh, empty Postgres cluster: the login roles config, account, guild and friend are 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.
¿Te sirvió?

¿Sigues atascado? Buscar en MuGPS Pregúntale al Asistente MU

MuADMINS Community Alpha: gratis, hecho por la comunidad y en desarrollo activo.