Rank 3: Container
Direct container shell
Votes
1
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
Direct container shell
do you still have access to the old server?
and the old db?
Rank 3: Container
Yeah
Rank 3: Container
Yeah
okay try these commands. I'm not a docker expert, so please bear with me lol
Rank 3: Container
No Problem
docker compose exec mariadb sh -c 'exec mysqldump --all-databases --add-drop-database -u"$MYSQL_USER" -p"$MYSQL_PASSWORD"' > ./dump.sql
make sure to run this in the same directory as appwrite's doker-compose.yml
docker compose exec -T mariadb sh -c 'exec mysql -u"$MYSQL_USER" -p"$MYSQL_PASSWORD"' < dump.sql
use this to restore on your other server
Rank 3: Container
Doing now
let me know
add a sudo if you're not root
Rank 3: Container
LOCK TABLES _console_webhooks_perms WRITE;
/*!40000 ALTER TABLE _console_webhooks_perms DISABLE KEYS /;
/!40000 ALTER TABLE _console_webhooks_perms ENABLE KEYS /;
UNLOCK TABLES;
/!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE /;
/!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS /;
/!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS /;
/!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT /;
/!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS /;
/!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION /;
/!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2023-03-21 5:13:27
well it seems like it worked?
Rank 3: Container
I got a Backup.sql file but its 0Kb
Rank 3: Container
0 kb
Rank 3: Container
Sorry dump.sql
Rank 3: Container
Is it okay?
i dont think so
Try looking at this, along with the comments
this should be able to help you
Rank 3: Container
now its working. It shows 967kb
Admin
Make sure you're you're using the same docker-compose.yml and .env file from your old server on the new server