With Vultr’s upcoming price hike, I’m planning to migrate this instance storage bucket to a more affordable alternative. Unfortunately, it’s rather large, (over 700 GB in thumbnails), so it’s going to take a while to transfer.
Long story short: the bot will be not be posting new content for a couple of days - probably about a week.
All migrations and updates have completed. The server is now all up to date again, and the bot is playing catch up.
Small update
So it’s been over 4 days of file transferring. There are about 13.6 million files in the source buckets, and yesterday we passed 14 million file checks.
So I’m guessing that means it needs to do multiple checks per file. I’m hoping it’s 2 checks per file, meaning the process is over half way.
The good news that most of the data has been transferred over (source shows 727GB used, destination shows 713 GB).
The bad news is that due to how the files are structured, it’s incredibly hard for the sync process to estimate which files it still has to move over, so it does need to check them all one-by-one.Ironically, me posting this image above would mean there’s 1 file more that has to be synced over. But I’m willing to let it be a casualty of this war ;)
Dropping by for another update:
- Server has had Lemmy updated from 18.4 to 19.3
- pictrs has been updated from 0.4.x to 0.5 - that also took a nearly a day
- Just updated postgres from 15 to 16
There are still some updates and migrations left to do, but things are looking up, I think the worst is behind us.
Having said that, I’ll be taking the server offline now for the rest of the updates - hope this comment was properly propagated :D
Appreciate keeping us updated!
Good news everyone, the bucket migration has finished! At first glance everything seems to be in working order.
To make the most out of the downtime, I’ll continue with an attempt at upgrading to a more recent Lemmy version this weekend. So there might be a bit more downtime, but then we should be good for a while.
All right, the server has been updated to the latest stable version.
I initially intended to leave it running for a few hours to make sure everything is stable, but somewhere along the server reboots, the bot got activated once more and errr, well… it’s been posting happily for some time now.
I guess that answers my question whether or not it’s still compatible with the new server version.
Took me a few days to find this post to figure out what’s up. ‘Preciate the update!