Hello, Im moving my apps to a consolidated region, from qro to dfw, but I’m facing a problem with the database of one of my apps. Its a db app with a single machine and a single volume storing my mysql db, but after running fly volumes fork <vol_id>–region dfw –, the new volume is being created empty, any idea why?
Also, the volume is 2.4~ gigs in size, I ssh into it and saw it is because a couple of 800m binary logs, should I delete them or keep them, the volume already backups daily so it seems overkill?
If you actually mount the forked volume onto a machine, are you able to see any of the expected data on the disk? The volume size reported in the dashboard / flyctl is only updated once the volume has been mounted at least once, so that may be why it’s showing as empty initially.
Otherwise, once the forked volume has reached the created state, it should have all data.
Whether you want to keep all the files in the volume is your choice to make The extra 800mb shouldn’t make any material difference to the forking speed. A 2.4GB volume should fork quite quickly
The extra 800mb shouldn’t make any material difference to the forking speed. A 2.4GB volume should fork quite quickly