-
Notifications
You must be signed in to change notification settings - Fork 2
Backup Recovery and Migration
AshleyThew edited this page Jul 5, 2026
·
1 revision
Bank does not provide a one-click backup command. Safe operations rely on storage-level backups and controlled conversion workflows. This page organizes migration work by subsystem so admins can execute changes safely.
Migration paths:
- Save type migration via
convert.yml(Convert.Confirm,Convert.To.Savetype) - Legacy upgrade workflow via
upgrade.yml - Other plugin imports via
Bank.Converter.*flags inconfig.yml
- Backend conversion subsystem (
convert.yml) - Upgrade conversion subsystem (
upgrade.yml) - External-plugin import subsystem (
Bank.Converter.*) - Backup and rollback subsystem (storage snapshots)
Files used:
convert.ymlupgrade.yml-
config.ymlconverter section -
mysql.ymlandmongo.ymlwhen changing backend
Operational policy:
- Keep conversion flags disabled except during planned migration windows.
- Never change backend and upgrade flags in the same uncontrolled restart.
/bank admin save-
/bank admin reload(not a replacement for full restart during conversion)
Migration operations should be restricted to full admins.
Recommended backup targets before migration:
- SQLite:
plugins/Bank/database.db - MySQL: all
bank_*tables used by Bank - MongoDB: bank database collections
- Config files: full
plugins/Bank/tree
Safe save-type migration checklist:
- Stop or lock player access window.
- Run full backup.
- Validate target backend credentials in
mysql.ymlormongo.yml. - Set
Convert.Confirm: trueand target save type. - Restart server (do not rely on reload).
- Verify conversion completion and reset flags.
- Conversion restarts repeatedly:
Convert.Confirmlikely still true. - Upgrade conversion unexpectedly triggers: inspect
upgrade.ymlconversion flags. - Partial migration outcome: restore backup, reset flags, and rerun migration with server closed to players.
- System Architecture and Lifecycle
- Commands and Permissions
- Account and Balance Model
- Transactions and Money Flow Rules
- Storage and Persistence
- Configuration System
- GUI and Inventory Interactions
- Integrations and Access Modes
- Error Handling and Edge Cases
- Admin Operations and Troubleshooting
- Backup, Recovery, and Migration
- Version Compatibility and Known Limitations
- command_baltop.yml
- commands.yml
- config.yml
- convert.yml
- default_items.yml
- hiscores.yml
- inventories.yml
- itemblacklist.yml
- items.yml
- language.yml
- mysql.yml
- permissions.yml
- sounds.yml
- upgrade.yml
- Discord Support Config:
- command_baltop.yml
- commands.yml
- config.yml
- convert.yml
- default_items.yml
- hiscores.yml
- inventories.yml
- itemblacklist.yml
- items.yml
- language.yml
- mongo.yml
- mysql.yml
- permissions.yml
- sounds.yml Config:
- command_baltop.yml
- commands.yml
- config.yml
- convert.yml
- default_items.yml
- hiscores.yml
- inventories.yml
- itemblacklist.yml
- items.yml
- language.yml
- mongo.yml
- mysql.yml
- permissions.yml
- sounds.yml Config:
- command_baltop.yml
- commands.yml
- config.yml
- convert.yml
- default_items.yml
- hiscores.yml
- inventories.yml
- itemblacklist.yml
- items.yml
- language.yml
- mongo.yml
- mysql.yml
- permissions.yml
- sounds.yml