Book Image

Microsoft SharePoint 2013 Disaster Recovery Guide

By : Peter Ward
Book Image

Microsoft SharePoint 2013 Disaster Recovery Guide

By: Peter Ward

Overview of this book

Where does it all go wrong with disaster recovery? Yes, why a disaster recovery plan fails the business and costs IT staff their jobs or a promotion? This book is an easytounderstand guide that explains how to get it right and why it often goes wrong. Given that Microsoft's SharePoint platform has become a missioncritical application where business operations just cannot run without complete uptime of this technology, disaster recovery is one of the most important topics when it comes to SharePoint. Yet, support and an appropriate approach for this technology are still difficult to come by, and are often vulnerable to technical oversight and assumptions. Microsoft SharePoint 2013 Disaster Recovery Guide looks at SharePoint disaster recovery and breaks down the mystery and confusion that surrounds what is a vital activity to any technical deployment. This book provides a holistic approach with practical recipes that will help you to take advantage of the new 2013 functionality and cloud technologies. You will also learn how to plan, test, and deploy a disaster recovery environment using SharePoint, Windows Server, and SQL tools. We will also take a look at datasets and custom development. If you want to have an approach to disaster recovery that gives you peace of mind, then this is the book for you.
Table of Contents (19 chapters)
Microsoft SharePoint 2013 Disaster Recovery Guide
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
4
Virtual Environment Backup and Restore Procedures
Index

How and why assumptions can sink a DR plan


Assumptions are the foundation upon which failure can occur. As part of the DR plan every assumption needs to be questioned:

  • To what environment would recovery occur?

  • Can we gain access to our DR site in the event of a disaster?

  • Will key staff be reachable in the event of a disaster?

  • Will key staff be able to commute in the event of a disaster?

  • Will internet access be available to key staff during a disaster?

  • If a disaster is widespread, will many companies converge onto and overwhelm the planned DR site?

Small changes still have the ability to prevent Central Administration from coming up

Deploying or retracting a web part that is only loaded on a single page can cause catastrophic failure. One example of when this can occur is when trying to perform a retract via the Central Administration user interface of a SharePoint solution that is deployed to Central Administration itself. For any such solution, Central Administration happily tries to retract the solution and it fails. The author ran into this when trying to uninstall Powerpivotwebapp.wsp. The solution was to perform the retract via PowerShell. During several initial retract attempts, the Central Administration in production was rendered inaccessible. All attempts to repair Central Administration failed. Luckily, rollback was possible.

Tip

Lesson learnt: Have a development environment identical to production, and release through development, staging, and production, with change requirement documentation signed.