Crisis averted
Alright it was less terrible than I originally thought and it goes to show it's not what happens to you but how you react. I didn't get much sleep last night so encountering a problem right away in the day I wasn't ready to deal with something that was broken.
Turns out the transaction logs on the SQL server had grown quite large and filled the volume. Treesize and a few 20gigs deleted later, life is better and no one needs to know that the reboot wasn't exactly what fixed the server. The server most definitely needed to be rebooted, I had a new version of anti-virus that was waiting to finish installing.
I'm just paranoid about this server it failed on me before, and I was stressed when I saw that the monthly full backup had failed to complete (the password reset from the co-worker leaving pissed off the backup service). In the end it all worked out fine. The monthly full this month is going to be a little spotty in terms of restoring, it is currently running and only about 20% after 5 hours. 1 terabyte of data to backup FTW? We normally let it run from on Friday night and it goes all day Saturday. The backup averages 22 hours and only a few things have been locked at the exact moment someone was trying to use them today so for the most part most people won't even notice.
Wow! Just needed to be restarted! Thats life!
ReplyDeleteJust try to be patient while restarting.
ReplyDeleteAh technological problems. At least it's fixed for now.
ReplyDeleteI agree with Tipota
ReplyDelete