Webcast: Panic! SQL Disaster Strikes: 5 Best Practices to Recovery
No matter how much we prepare, when disaster strikes we all feel a moment of panic. For some that panic quickly passes as we get down to work to fix the problem. For others the panic continues to grow as we search for a solution. Of course back up is crucial, but in this session Sarah will provide useful real world best practices that will show how to recover from disaster and more importantly how to prepare for the inevitable. Specifically how to recover from common disaster scenarios. For example, what to do when the master database is corrupt, a drive array with half your database files fails, a hardware failure, a SQL injection attacks wipes out whole tables and many more.
Presented by: Sarah Barela
Webcast: Avoiding a SharePoint Disaster
Whether you’ve already implemented SharePoint, or are only preparing to, backup and recovery should be a priority. Discover how to use SharePoint’s out of the box backup and restore capabilities to protect your data in case of calamity. This session will take a quick trip through the built in backup options available with SharePoint; suggest some tips, tricks, and best practices; and focus on some techniques concerning how to restore that data before disaster strikes. Presented by: CA Callahan
> Register Now
> Live date: 2/3/2010 at 12:00 Pacific
IT Leverage, IT Expertise and In the Trenches Experiences
Greg writes "I ran up against what you say a couple years ago.
I work evening shift in a K-12 school district. Supposed to go home about midnight. When I started there 16 years ago, I was in bliss – full access to all things in the datacenter. I used to work until 3/4/5am to learn about things as they were being done. I came more from a programming background, so I learned, cautiously, but was able to learn as the infrastructure was put in place – the networking aspects, the server aspects, the web aspects, DNS, etc…
I wasn’t actually doing much of the building at the start, as it needed to be done right, but was learning as it got done, and then able to troubleshoot things along the way. They promoted somebody to LAN/WAN Admin, and my network access went out the window. No access to the firewall, routers, etc… to see what was going on and how it was moving forward.
Our student system is fairly recent, and now has a parent/student portal on a DMZ that talks to SQL internal.
It’s had some hiccups… We’ve had an annoying problem that pops up once in a while – dmz web server gets an error page at a specific point in the data stream coming from internal SQL – connection resets mid-page.
When it happens, it’s repeatable down to a very minimal page containing just the query pieces, and a display of the info. The app developer along with MS SQL Support said it’s a problem with the firewall. The network guy along with his Cisco consultant said it’s a problem with the SQL server. Both are certain the problem is not in their area, yet we still have the problem. And nobody who has access to all the pieces, and an understanding of how the pieces all fit together, in a way that will be able to fix the problem.
Changing the MTU on MS SQL side to send packets at a more VPN friendly size helped some, but the problem still happens at times. Changing the app to use a serverside cursor (the developer uses mainly clientside cursors in the ASP pages) also seems to help fix the problem, but is not realistic to think the developers will change their coding style for such an intermittant problem.
So the problem persists, intermittantly, because we no longer have somebody to work on the problem in an overall way looking at all the pieces without regards to which parts are theirs.
Many of our servers have now been migrating to vmWare boxes, and I like the concept. But I’m not the vmWare guy. So I see another layer of things I can use to troubleshoot disappearing.
And another layer of ‘overall-ness’ understanding disappearing with it as well.
The bright side in it all, I guess, no more 3/4/5am nights – at least not at the ‘day job’ – the smaller the scope of access, the less hours needed to understand it."