The Daily Backlog | Day 22

T.K.O.

Happy Wednesday fellow backloggers!!

Well, as some of you may know, yesterday was a pretty rough day for the website. After what seemed like a freak crash the blog’s database became corrupted and pretty close to unrecoverable. Luckily, I did have some database backups at the ready to repair it, but unfortunately I still lost about a month’s worth of posts including all of the most recent Daily Backlog entries. I will say this though, I’ve learned more Linux and MySQL database administration in one day than I have for the entirety of running this blog! For better or worse.

At first I thought the corruption could have been caused by a virus or worm trashing the file system and database directories. But what it actually turned out to be was the website was consuming more memory than it was allocated. So when the database was trying to handle things like updating posts or uploading images, it just flat out ran out of memory and crashed! And apparently it must have happened during an update or something because that proceeded to corrupt some of the most important parts, including the ones that contained all of the blog’s posts, pages and other high jinks. To say it was a bit distressing is an understatement!

But, through perseverance, stubbornness and an entire day of troubleshooting and experimenting I was able to get the website back to a state that I’m relatively happy with. To somewhat guarantee it doesn’t happen again, I’ve also allotted more physical memory for the site which should hopefully prevent any crashes in the near future. It’s going to increase the monthly cost of running the blog a bit, but for the security of not losing anymore content makes it worth it. That and I’m glad I got back what I did.  I mean, one month of lost content is much much better than four. Mostly because in the last four months I put a lot of work into the blog. Including all of the pages and feed related to the podcast! It’s not like this content is wiped from existence either. Luckily I’ve been pretty vigilant about having it all backed up on a separate drive so really all it’ll take to put it back is time.

INSERT INTO BACKLOG_DAYS SET COUNT = 22;

On the brightside, it seems the website was using more memory due to an increase in traffic so thank you all for sticking with me and visiting the blog! I really appreciate it and I look forward to messing around with these backlog shenanigans and sharing them with all of you!

Unfortunately because of this mess I didn’t get much done at all with regards to the backlog so nothing to report there. I still have a bit of work reposting the lost content, but I think the worst is over and I’ll report back tomorrow with hopefully our regularly scheduled programming!

Until then my friends, have a great day!


Currently Playing

Monster Hunter: World (Xbox One)

Fairy Fencer F: Advent Dark Force (Switch)

Total Backlogged Game: 741…My heart rate after the site crashed!

Total Completed Games: 3 …the number of times I almost cried


Want to contribute to the website or the podcast? You can send your written or audio submissions to the below emails!

Written: [email protected]

Audio: [email protected]

Want to know what other shenanigans I’ve been up to? Then follow me on Twitter @BacklogOdyssey