Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Kristen
Test
22859 Posts |
 Posted - 2004-08-18 : 15:28:46
|
| The other though coming out of todays debuncle was "what trashed the database"The server is on a UPS circuit in a room full of servers. Turns out it was not part of the circuitry to inform the server that there was a powercut, so there was no orderly shutdown. But SQL should survive that. (OK, so the disk subsystem caching may have been at fault ....)In fact it looks like it did survive the first 3 reboots. But with a UPS why were there so many reboots?The best guess is that the batteries were drained from a prolonged power cut. The server went off when the batteries drained, the power came back on and everything restarted.However, there was then a further series of very short powercuts - probably due to surge once the power came back on, and the server rebooted a further 3 times in about 10 minutes. One of those caused some unfortunate timing issue, in the middle of a reboot's "recovery" process, and on the next reboot a bunch of DBs were toast.At that time there was probably NO reserve power in the UPS, so when the power went off the UPS died almost immediately.Is there some [cost effective!!] way to get immunity from this particular scenario?Kristen |
|
|
MuadDBA
628 Posts |
Posted - 2004-08-18 : 15:40:21
|
| Yeah, set up your server so that after a power outage causes a shutdown, you have to manually power it up. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-08-18 : 16:32:28
|
| Hmmm ... that's a good idea. At least I get to get the culprit that failed to set up the UPS correctly out of bed at 4am !Kristen |
|
|
|
|
|
|
What trashed my database?