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

Identifying DR scenarios within SharePoint and its associated technology stack


Tackling DR in a SharePoint environment is often a struggle for both seasoned SharePoint administrators and newbies, because of the different ways in which the platform can be deployed within an organization. Furthermore, it can prove to be challenging to apply existing DR experience to SharePoint, due to the distributed and componentized nature of SharePoint and the supporting technologies that need to be in place for SharePoint to function. SharePoint relies on technologies such as Microsoft SQL Server, Active Directory Domain Services (ADDS), Internet Information Services (IIS), and .NET framework just to name a few, so there are a lot of dependencies and points of failure to identify during the DR planning stage.

Note

It is not enough to think it is being backed up so we can restore it easily. It is more, what has failed and what parts need to be restored to be operational again.