Field note / 15 November 2011
A session on avoiding avoidable farm failures
The best disaster recovery talk is often a list of ordinary decisions that prevent the disaster.
A session about resilience can drift into a tour of backup products. The more useful framing is to ask how a farm gets into trouble in the first place. Most incidents are not caused by a single dramatic event. They accumulate through undocumented changes, optimistic capacity plans and recovery steps that were never rehearsed.
The presentation looked at the choices that make a later recovery possible: knowing what is installed, keeping configuration records, testing restores and separating the people who approve a change from the people who assume it worked.
Make the failure path visible
Pick one critical service and trace what happens if it disappears. Who notices, what is the first diagnostic step and which record tells you how it was configured? If the answer depends on one person’s memory, the process has a single point of failure before the technology does.
Then test a restore on a schedule that matches the business risk. A successful backup job is not a recovery test. The test should include the time to restore, the validation of content and the communication path while users wait.
The short list
Checks worth running
- Trace one service failure from detection to recovery.
- Test a restore and record the elapsed time.
- Identify the decision maker and the communicator for an incident.
Resilience is built from small, repeatable acts of preparation. The session was a reminder that the least exciting habits often prevent the most expensive surprises.
Outside reading
Reference shelf
Official documentation and independent community reading for the subjects in this note.
- Microsoft Learn: SharePoint administration (opens in a new tab)Operational guidance for service settings, site management and the modern admin experience.
- Microsoft Learn: SharePoint documentation (opens in a new tab)The starting point for current SharePoint administration, development and hybrid guidance.
- Microsoft Tech Community (opens in a new tab)Community discussion, product announcements and practical posts from Microsoft teams.
- Microsoft Tech Community: SharePoint (opens in a new tab)SharePoint announcements, community articles and product team updates.
- Microsoft Learn Q&A (opens in a new tab)A community question and answer space hosted by Microsoft.
- SharePoint Stack Exchange (opens in a new tab)An independent question and answer community for SharePoint practitioners.
- Microsoft Support (opens in a new tab)Support articles, troubleshooting steps and product help from Microsoft.
- Microsoft 365 Patterns and Practices (opens in a new tab)Community maintained guidance and samples for Microsoft 365 work.
- Microsoft Download Center (opens in a new tab)Official downloads for Microsoft tools, updates and supporting packages.
- Microsoft Security Response Center (opens in a new tab)Security advisories, update guidance and vulnerability response information.
- Microsoft Security blog (opens in a new tab)Microsoft guidance on security research, response and platform protection.
- SharePoint community on Reddit (opens in a new tab)An independent discussion space for administrators, developers and users.
- Microsoft Learn: Azure Architecture Center (opens in a new tab)Reference architectures and design guidance for resilient cloud workloads.
- Microsoft Learn: SQL Server documentation (opens in a new tab)Official reference material for database engine configuration, performance and recovery.
- Microsoft Learn: SharePoint search (opens in a new tab)Documentation for search architecture, crawling and result management.