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 the components of your SharePoint environment


Before creating a DR plan, you should take a complete inventory of each component of your SharePoint environment. This inventory should include the following:

  • The physical architecture, such as the servers, the database, and the network

  • The logical architecture, such as web applications, service accounts, service applications, and apps

  • Custom software installed in the farm

Physical architecture

You should begin the process of taking an inventory of each component of your SharePoint environment starting with the physical architecture. The physical architecture should include all farms and related components in your SharePoint environment, including any development, testing, staging, QA, and production farms.

Although the other SharePoint farms aside from your production farm may not be part of your SharePoint DR plan, it is good practice to make sure that you have an inventory of each farm. You may need to utilize individual components of...