June 14, 2021 at 12:00 AM UTC
40m of downtime.
June 14, 2021 at 2:40 AM UTC
I am going to begin the process of migrating Mobilizon to the new server
at 00:00 UTC (20:00 EDT). I don’t know for sure how long the process
will take but expect at least 2 hours of downtime. In general,
migrations look like this:
- Upgrade the application on the old server
- Stop all related processes
- Back everything up
- Copy backups to the new server
- Import databases
- Ensure file permissions are correct
- Start processes
- Implement automated backups with tarsnap
Step 4 will take the longest by far; the limited bandwidth of the old
system results in terribly slow network operations. Because of the
database size, the limited bandwidth caused Pleroma’s migration to take
hours; I don’t expect Mobilizon to be quite as bad but it very well
(22:53 UTC — Jun 13)
I’m leaving processes stopped so data doesn’t change between the backup
and restore points.
- Data is backed up and transferring to my PC now. The archive is 372M
so it shouldn’t take too long.
(01:13 UTC — Jun 13)
- While that’s transferring, I’ve updated DNS records to point to the
new server. This will allow the change some time to propagate as I get
everything set up.
(01:14 UTC — Jun 13)
- Data’s still being transferred but I’ve downloaded the latest release
and set most everything else up. This should allow me to simply drop
the data back in place and get up and running fairly quickly.
(01:21 UTC — Jun 13)
- Transfer is finished so it’s time to get started.
(01:25 UTC — Jun 12)
Aside from some odd behaviour that may be an upstream bug(? going to
test), I’m fairly certain everything is back to normal.
(02:49 UTC — Jun 13)