An update on Seibertron.com's Database Server
Posted: Sat Dec 30, 2023 12:32 pm
Just an update on Seibertron.com ... our database server has been problematic for the past few months. I had been putting off fixing it until after the new year due to how busy our store has been. That server was behaving very much like Seibertron.com's old servers back in the day when the hard drives would go bad, but I've been on cloud servers with SSD for past 8 years and haven't had a problem with these servers since then.
2 days ago, the database server had other things in mind and ended up corrupting the OS and much of the main Seibertron.com database which made fixing the server a top priority. Fortunately, I was able to restore the database from a day old backup of the server so not much data was lost (if you posted on the forums 2 days ago, I apologize that your posts for that one day were lost).
Anyway, after spending time with tech support yesterday and not getting anything resolved plus spending another day working on the database server trying to fix it myself, I decided it was best to move the database server to a new server in hopes that I am right that the old server is corrupted somewhere. I don't have the luxury of waiting for tech support to help me resolve this problem eventually nor do I have the time or patience right now with New Years weekend. So hopefully I'm making the right decision here.
It's nerve-wracking trying to get a new server up and running with everything else I've got going on ... hopefully I don't forget something and hopefully this all works out! Fingers and eyes crossed!
2 days ago, the database server had other things in mind and ended up corrupting the OS and much of the main Seibertron.com database which made fixing the server a top priority. Fortunately, I was able to restore the database from a day old backup of the server so not much data was lost (if you posted on the forums 2 days ago, I apologize that your posts for that one day were lost).
Anyway, after spending time with tech support yesterday and not getting anything resolved plus spending another day working on the database server trying to fix it myself, I decided it was best to move the database server to a new server in hopes that I am right that the old server is corrupted somewhere. I don't have the luxury of waiting for tech support to help me resolve this problem eventually nor do I have the time or patience right now with New Years weekend. So hopefully I'm making the right decision here.
It's nerve-wracking trying to get a new server up and running with everything else I've got going on ... hopefully I don't forget something and hopefully this all works out! Fingers and eyes crossed!