Lessons Learned to Reduce Time and Worry For SharePoint Continuity of Operations (CooP)

SharePoint disaster recovery

Lessons Learned to Reduce Time and Worry For SharePoint Continuity of Operations (CooP)

By Adam Levithan | August 12, 2015

When supporting the U.S. Federal government five years ago, my former company and its federal sponsors, were very good at outlining the Continuity of Operations (CooP) plan, prioritizing systems for recovery and updating documentation to ensure that agencies are able to perform essential functions during a crisis. One astonishing thing about the process, however, was that information was stored in SharePoint, which was not a high priority system at the time.

Now, we live in a completely digital age, and no-longer is it acceptable to lose connection to your business critical, and even draft, content. Just like me and my previous company, you and your organization spend a lot of time planning, organizing, and building infrastructure to ensure that content is available during planned and unplanned outages. A typical SharePoint scenario to create a CooP is to build two identical farms, copying all content and settings from Production over to the destination – usually called a disaster recovery farm. I’ve assisted in building this structure many times, and it is useful. But now I think there’s a better way without worrying about all of the pieces of SharePoint.

As a result, I’ve now been working with customers to focus on content replication, compared to full disaster recovery. Content replication is a systematic approach to ensuring selected content is continuously live and available during planned and unplanned outages. So now, instead of creating an exact replicate farm, and worrying about deploying all features, solutions, web parts, and styling to the destination, customers can create a smaller footprint that is focused on retaining only the most important content for the organization.

With this capability, an IT organization can now ask their colleagues or business client to define “what information is mission critical?” even if the data is not sitting in a fully mission critical system to the business. Unlike traditional disaster recovery environments, with content replication you can create a true Continuity of Operations plan for mission critical data with the most important content, without worrying and with barely any downtime.

Learn more by watching our webinar: How to Prevent a SharePoint Migration Disaster

Leave a Comment

Add new comment

Adam Levithan 2018

Adam is a Group Program Manager of Secure Collaboration at Exostar and a Microsoft MVP advocating for collaboration by connecting business needs with the right technology. Prior to Exostar, Adam was a Product Manager for Migration at a market leading ISV and a Practice Lead for Office 365 in a cutting-edge Microsoft Consulting firm. Over the last decade Adam has been responsible for moving customers to the cloud, designing and implementing information architecture (SharePoint Farm and content) and increasing user adoption. Adam is an ongoing member of the SharePoint Saturday DC coordinating committee and active speaker at many national events.

Written By: Adam Levithan