mersenne.ca server migration and probable downtime (Nov 2020)
 

I will be moving mersenne.ca over to a new server this weekend (probably overnight Nov 14-15). I will be taking the site down before I start the migration to avoid getting data out of sync between the two. If everything goes well it'll only be a few hours of offline, but it might be longer. If you want assignments for tf1G or similar you should grab a few days extra supply now.

I'll post back here when I start the migration and when I think it should be finished and working again.

Thank you for sustaining the site and good luck with the migration.

[QUOTE=Ensigm;563161]Thank you for sustaining the site and good luck with the migration.[/QUOTE]+1

:awesome:

Thank you James, and (no, I won't say it before you tell us the migration is complete).

:et_:

Migration is started, but running into some snags. The Plesk Migrator is very handy, but unfortunately when copying databases it simply does a monolithic mysqldump of all tables, uncompressed and then copies that over. Which is fine for smaller sites, but mersenne.ca runs off 1138 (no THX) tables of a total size I haven't yet calculated, but the old server only had about 45GB free, even after I freed another 10GB that wasn't close to enough. So I'm going to have to manually migrate the database table-by-table, which is ok but takes more human-time than letting it run automated.

So downtime for mersenne.ca will be somewhat longer than expected, likely for at least the next 12h or more.

Is it possible to directly dump the backups into the new server (via shared folder)?

Probably, for someone who knows how, but that's beyond my knowledge. I'll just muddle along with what I know works.

[QUOTE=James Heinrich;563237]mersenne.ca runs off 1138 tables of a total size I haven't yet calculated, but the old server only had about 45GB free...[/QUOTE]Turns out the total mysqldump filesize would be 97.3GB (and ~150GB actual disk used including indexes).

[QUOTE=James Heinrich;563252]Turns out the total mysqldump filesize would be 97.3GB (and ~150GB actual disk used including indexes).[/QUOTE]

I take it, the hard part (manual db dump) is complete?

Manual DB dump is complete, I've now got a local backup of all the database files (17GB gzip'd) that I'm currently uploading to the new server while I sleep and then in the morning I'll manually import the missing large tables on the new server. Hopefully with Xeon+SSD that won't be as painfully slow as I've seen previously with Atom+HDD. Nevertheless, importing building ~140GB of database will take some time. I also need to attend to a couple other domains that share this server before I can plug it back in and turn it on. I'm hoping it can be online sometime later tomorrow (i.e. 12-18h from now) but we'll see how it goes. It's now 3:30am and my brain needs some off-time.

[QUOTE=James Heinrich;563254]It's now 3:30am and my brain needs some off-time.[/QUOTE]
:sleep::nick: