7 Replies - 527 Views - Last Post: 22 January 2011 - 11:20 AM

Site Backup Problem

Posted 18 January 2011 - 11:12 AM

I know I am going against a bit of the tide here by not mentioning feedback like changing nickname colors or adding some kind of social flair... but I thought I would bring up the recurring problem of midnight backups (12am New Mexico time.... 11pm PST). I am often on around 11pm and right at the stroke of 11pm this site pretty much lags to all hell and even appears to go offline. Normally it is for 2 minutes or so, but the other night it was 16 minutes. I was right in the middle of answering a question when suddenly the site was unreachable.

As this site grows into a site that never sleeps, might be advantageous for DIC to come up with a way to solve the problem or it will just get worse.

Replies To: Site Backup Problem

Re: Site Backup Problem

Yeh, I got the server down notice just after midnight. Our server management folks sent a reboot request to the NOC and it didn't come back up on the first try. Not sure what happened.

I'll contact them about making those backups smoother. Maybe they've got some ideas. For a while we weren't having problems, so I'm not sure what's causing it now. Especially having the database server on it's own dedicated box.

It's something that's definitely on my radar as it wakes me up every night the server monitor goes off.

Re: Site Backup Problem

Posted 20 January 2011 - 12:43 AM

Serever management team made some changes that reduced the backup priority so it didn't take things offline. I'll have to verify they actually ran in the morning, but it doesn't look like it took the server offline tonight.

Let me know if you notice any other issues (slowness, etc.) as we deployed several changes to the configuration of the web server today.

Re: Site Backup Problem

Posted 22 January 2011 - 11:20 AM

Backups ran last night with little problem it looks like. Continuing to monitor the situation. We did have a little hiccup last night that was code related, but shouldn't have affected logged in users.