Nope no Robert Downey Jnr in this one you’ll have to wait until April 30th for that (in the UK at least). This was Mike Watson (a man who used to play with tanks on a professional basis) taking the SharePoint Evolution attendees through the major enhancements to SharePoint which will make high availability solutions a little easier to architect and deploy.
Mike started with a rundown of the major issues with SharePoint 2007:
- Granular Recovery – ah that look on a client’s face when you tell them just exactly what they will have to go through now that 1k text document they deleted has exited the recycle bin (cue exasperated sighs stage left). Just a simple matter of recovering that backed up database to a web app and then finding the document concerned – a doddle
- Disaster Recovery – a small list of laundry for this one that can only truly be satisfied by a sub list:
- No native support for mirroring – let’s do the swap over by hand or rely on some cludgy scripts
- Everything can be made redundant, apart from that indexy bit and if that goes and you’re reliant on search apps? Just how many documents do you have to crawl? You weren’t planning on doing anything over the next couple of days/weeks/months were you?
- Robust backup – let’s back up everything. Yip content, config… you want to restore config? Ok but that’s you unsupported as far as Microsoft is concerned. They didn’t mention that?
Ok various vendors have spent millions and made millions producing tools to sort these issues out. But does SharePoint 2010 handle them in anyway?
Mike Watson seems to believe… sometimes. Here is what I gleaned concerning these issues.
Granular Recovery – well the good news is you won’t have to restore the content DB backup to a SharePoint Farm, Hidden in the depths of 2010 Central Administration is a command called Granular Recovery from unattached database. And backup now goes down to the list level. Certainly an improvement but I doubt the likes of Quest and AvePoint will be packing up their tools and leaving the SharePoint scene anytime soon. Anybody who has used one of these tools to search and retrieve an item from a backup file (no restoring to SQL) will know why.
Native support for mirroring – Now you can tell your SharePoint sites where the failover database is. If SharePoint cannot contact the principal node (I think it’s in 10 seconds) then it will attempt to contact the failover. This in my humble (well not so I am blogging after all) is brilliant. Unfortunately you still need to set up the SQL side from SQL but when combined with a witness server this could be a very useful addition.
Index Server – this is now the Crawl Server, I know you just get used to one set of names and acronyms and then they change (wait until you find out about BDC, still a SharePointy acronym but doesn’t quite mean what it used to). Anyway, with the brand new service architecture the single point of failure is gone in 2010. It’ll even support mirroring if you really want to (more redundancy and you know what redundancy makes? Yep license sales).
Robust backup – the reason Microsoft didn’t support mirroring and restore for the config database in 2007 was the sheer volatility of the data. In 2010 they do support backup and restore. The config backup saves settings to an XML file which could even be restored to a completely separate farm, in theory. Mr Watson was quick to point out that he hadn’t seen it done.
So some great improvements, especially around redundancy and mirroring. Should make complying to those SLAs a little easier.