November 27, 2011 at 7:39 pm
Hi SQL Experts,
Our production cluster server(active/passive) is maintained by a hosting company. There was a power outage 11/24 and hosting company brought everything up and online in around 24 hours (issues with SAN and firewall, sharing environment).
I checked the server – SQL server services are up and running and I can access databases
windows shutdown event
Log Name: System
Source: EventLog
Date: 11/24/2011 10:42:37 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxx.xxxxx.sjz.xxxxx-int.com
Description:
The previous system shutdown at 7:25:06 AM on 11/24/2011 was unexpected.
sql server log
Date11/24/2011 11:43:59 AM
LogSQL Server (Current - 11/27/2011 12:01:00 AM)
Sourcespid7s
Message
Starting up database 'master'.
Date11/24/2011 11:44:00 AM
LogSQL Server (Current - 11/27/2011 12:01:00 AM)
Sourcespid7s
Message
37 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
I checked for all databases- 0 transactions are rolled back, and x number of transactions are rolled forward
Will SQL server take care of recovery process with no rollback transactions??
Question:
1)How can I find out the exact sql service down time and duration?
2)How can I check whether we lost any data during sql recovery
3)Is there any other things to check which is important
4)We are still waiting for a incident report from hosting company, what type of report we should ask them to provide
Appreciate your help. Thank you.
November 28, 2011 at 12:24 am
Will SQL server take care of recovery process with no rollback transactions??
In recovery, SQL Server roll forward commit transactions & rollback uncommitted transactions.
1) How can I find out the exact sql service down time and duration?
Check Logs.
2) How can I check whether we lost any data during sql recovery
It doesn't look like you lost any data (committed). Please verify your logs for any warning / error messages.
3) Is there any other things to check which is important
I don't think so. Regular consistency checks should be fine.
4) We are still waiting for a incident report from hosting company, what type of report we should ask them to provide
I would ask for reasons for power outage. So that we can include them in Disaster Recovery Plans.
November 30, 2011 at 10:06 am
Thanks for your reply.
11/24 7:24:40 AM system shutdown unexpectedly due to power outage.
11/24 10:43 OS started
11/24 11:43 :58 AM sql server started
As per my understanding since all the committed transactions are rolled forward with no issues.
So as part of recovery process sql server recovered the database up to 7:24:40 am and rolled forwarded the committed transactions. and whatever the uncommitted transactions are rolled back and not written to disk. I understand that we lost the uncommitted transactions.
SO my question is do we get any queries from users saying they entered the data that time but could not see in database or reports. what actions need to be taken...do we need to inform to clients about power outage?? kind of new to this...please advice.
as per our hosting company --
we have confirmed the root cause of the power outage to be the physical activation of the EPO(emergency power off ) by a company employee.
No we did not recover the database, so whenever such thing (power outage) happens and after that once database server comes back online, SQL server goes for an automatic recovery which in inherited feature of the database.
During automatic recovery process all transaction which were committed would be committed to the database and all transactions which were uncommitted would be rolled back.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply