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 do you write up the perfect DR documentation?


Writing the DR plan is generally not performed in a single clean swoop of activity, so sort out the good, the bad, and the ugly. Fix the obvious first, such as system account information, server names, and disk space.

Good technical documentation is a challenge because at one extreme, technical documentation is often written by technical experts who dislike writing and give it as little effort as possible, with no formal criteria. Or at the other extreme, the documentation is written by artisan technical writers who lack the formal technical criteria needed to evaluate the effectiveness of the product in view of the needs of the readers.

The previous chapters of this book have stated what is needed in a DR plan. This question really asks how you write the required information to an acceptable level where the documentation is readable and actionable. In essence, a technical resource can read the document and know what steps are required to be...