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

Can this whole process be outsourced to an external party?


Not really. There are plenty of companies that provide this kind of service, but it is not recommended to have a third party spend weeks writing up documentation which is really an "insurance policy" in case things go wrong.

As discussed in this chapter, writing the documentation is only the first step of a DR plan. It also needs to be set up, improved, and executed.

These resources need to be internal where management has direct authority over, them rather than through an account manager of the vendor. The DR plan needs to be internalized versus an adaptation of someone's ideal process or conceptual notion.

Do not delegate this role to an employee (or a summer intern…yes this has been witnessed) who has never written a complicated technical publication before, and who may lack the authority and leverage to do it well. Ironically, the writing of online documentation is often entrusted to the same administrators who write cryptic screens...