Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Disaster In The Real World - #2 Expand / Collapse
Author
Message
Posted Friday, July 19, 2002 12:00 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Today @ 12:51 PM
Points: 6,808, Visits: 1,938
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/disasterintherealworld2.asp>http://www.sqlservercentral.com/columnists/awarren/disasterintherealworld2.asp

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #5595
Posted Friday, December 14, 2012 10:28 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 7:42 PM
Points: 635, Visits: 2,215
The one thing I've done a lot is is created a scheduled task based off the sp_help_revlogin SP. It dumps the data to disk every 8 hours. Then the file is replicated to another server.

In a different job, I also had a script to create the restore scripts as well. That ran on a regular basis as well.

I also create my maintenance plans, etc by standardized scripts as well.

Having the logins with the right SIDs and the and the SQL backups, it allows me to not worry about recovering the system database and just do a fresh install of SQL Server. Then I worry about the user databases.




----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Post #1396748
Posted Saturday, December 15, 2012 9:18 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, November 6, 2014 1:00 PM
Points: 5,333, Visits: 25,277
gloing73 (12/15/2012)
very good website:

===== http://www.globalmarket.name// =====

The website wholesale for many kinds of fashion shoes, like the nike, jordan, prada, also including the jeans, shirts, bags, hat and the decorations.

WE ACCEPT CREDIT CARD /WESTERN UNION PAYMENT
YOU MUST NOT MISS IT!!!


This particular post in this forum reported as SPAM


If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Post #1396965
Posted Monday, December 17, 2012 1:39 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, September 30, 2014 7:42 AM
Points: 3,688, Visits: 72,435
Hey Andy,

Just to be sure I read this right...

Win2k, SQL2k? In 2012?

Wow... makes me glad that management lets me upgrade to newer stuff than that!




--Mark Tassin
MCITP - SQL Server DBA
Proud member of the Anti-RBAR alliance.
For help with Performance click this link
For tips on how to post your problems
Post #1397411
Posted Friday, January 4, 2013 6:00 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, December 9, 2014 2:33 PM
Points: 18, Visits: 259
Hi, Andy,
I'd read your initial article a couple times to ensure I understood the chain of events and the timing of the issues. I've ran into a similar situation within the last year, and wanted to compare notes after the holiday. I'm uncertain whether your event was preventable, but we've determined ours was.

Firstly though, can you confirm your environment specs? We're most likely not comparing apples to apples, as we're running Windows 2k8 and SQL 2k5, currently, with a plan to skip 2k8 for 2012. In one case far in my past, the simultaneous outage for Exchange and SQL were caused by a single system issue, as the business had been stingy on funding a separate server for each. A simple drive fill caused by a mislocated tempdb caused the system failure. In the recent past, the issue was caused by and unscheduled & uncommunicated security alteration from the separate AD group in the company. In your case, it sounds more like a specific OS registry corruption on the Exchange server, and a separate but coincidental total failure of your RAID5 drive configuration for the SQL server.

Ignoring the mail server issue for a moment, was there monitoring for drive failure within your SQL RAID configuration? In addition, does your SQL instance use the Exchange server as the SMTP destination for any server alerts thru DBMail? Perhaps it wasn't as much of a coincidence after all.

I look forward to your comments in response. Hopefully, an alteration to the current recovery standards will help minimize recovery times in case of another event.

Cheers!
Jonathan
Post #1402832
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse