zhdev/griefus
1
0
Fork 0
Code Issues Pull requests Activity

Update database-migration.md

Browse source
This commit is contained in:
Intelli 2025-09-02 15:03:00 -06:00
parent 252de2f233
commit 6155d4e864
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/database-migration.md
View file

@ -32,10 +32,8 @@ The `/co migrate-db` command allows you to seamlessly transfer all your CoreProt
**Before starting the migration:** **Before starting the migration:**
1. **Ensure your server is running** with your current CoreProtect database 1. Ensure your server is running with your current CoreProtect database
2. **Configure your new database** in `config.yml`: 2. Configure your new database in `config.yml` (ensure `use-mysql` is updated correctly)
* For MySQL migration: Set up your new MySQL connection details
* Ensure `use-mysql` is updated correctly in your `config.yml`
3. **Important:** Do NOT restart your server or use `/co reload` after modifying the config 3. **Important:** Do NOT restart your server or use `/co reload` after modifying the config
### Step 2: Execute Migration ### Step 2: Execute Migration
@ -92,21 +90,25 @@ The `/co migrate-db` command allows you to seamlessly transfer all your CoreProt
### Common Issues ### Common Issues
**Migration won't start:** **Migration won't start:**
* Verify you're using a CoreProtect 23.0+ Patreon build * Verify you're using a CoreProtect 23.0+ Patreon build
* Ensure you're not trying to migrate to the same database type * Ensure you're not trying to migrate to the same database type
* Check that no other CoreProtect operations are running * Check that no other CoreProtect operations are running
**Migration interrupted:** **Migration interrupted:**
* Manually delete/wipe the target database * Manually delete/wipe the target database
* Verify server stability before restarting migration * Verify server stability before restarting migration
* Consider migrating during low-activity periods * Consider migrating during low-activity periods
**Performance issues:** **Performance issues:**
* Monitor server resources during migration * Monitor server resources during migration
* Consider temporarily reducing server activity * Consider temporarily reducing server activity
* Large tables may cause temporary slowdowns * Large tables may cause temporary slowdowns
**Data verification failures:** **Data verification failures:**
* Check database connectivity and permissions * Check database connectivity and permissions
* Review server logs for specific error messages * Review server logs for specific error messages
* Ensure sufficient disk space on target database * Ensure sufficient disk space on target database
@ -133,6 +135,7 @@ The migration process includes several advanced features:
* Graceful error handling with detailed logging * Graceful error handling with detailed logging
The migration handles all CoreProtect data types including: The migration handles all CoreProtect data types including:
* Block changes and rollbacks * Block changes and rollbacks
* Container transactions * Container transactions
* Player interactions and sessions * Player interactions and sessions