Nightly Backups - Page 2

Arden · #9 January 2nd, 2005, 11:15 PM

Not quite, that's why I asked for clarification.

Darkshadow · #10 January 3rd, 2005, 04:44 AM

Quote:

Originally Posted by ScottW

.... we will just be locking the individual database so it will just act slow or non-responsive for about 50-60 seconds then will start working again. ....

That one part answers your question, Arden.

You may be able to post if it's just acting slow, but if you hit it in that whole minute where it might be non-responsive... probably not.

Arden · #11 January 3rd, 2005, 12:04 PM

Quote:

Originally Posted by Darkshadow

That one part answers your question, Arden.

You may be able to post if it's just acting slow, but if you hit it in that whole minute where it might be non-responsive... probably not.

I still don't see the words "You won't be able to post during this time" in there. I would assume I wouldn't be able to post, but what if it tries to post and gives me a database error?

One of the things I picked up from another forum I've frequented in my absence here is that you have to be really clear about what you mean when you post or somebody will either not get it or pick your argument apart. That's why I asked for explicit clarification: will we be able to post while the database is locked? It doesn't seem that difficult to answer yes or no, I don't see why everyone is avoiding the question.

bobw · #12 January 3rd, 2005, 04:24 PM

That's because you may or may not be able to post. It may be slow for up to a minute, or unresponsive.

If you happen to hit it during that 50/60 second period, get a cup of coffee and come back. Just chill out

Arden · #13 January 3rd, 2005, 06:46 PM

Thank you, that's all I wanted in response.

I was thinking that if you had some spare time, you could write a little PHP to announce the backup in, oh, 5 minutes (since I'm sure it's a scheduled thing), disable posting, then set everything back to normal... but that's probably not necessary.

**fryke** · #14 January 5th, 2005, 05:28 AM

Well, if you think about how one usually reads/answers threads, that'd be too much hassle. Because:

You can only answer a thread that's loaded. So assuming you've loaded a thread and the backup kicks in, it shouldn't usually be a problem at all. You write your answer into the quickreply box and probably the 50-60s period is over when you hit 'post'. If not, you'll find the system slow to reply, but that's all. worst case: you'll have to stop the failed loading process and hit post again or something... And the probability that you exACtly hit that minute's field is, well, very low.