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

General approaches to cloud DR


Disaster recovery in the cloud has not yet truly been standardized. Anyone that you talk to will have their own conceptual version of an accepted DR model, but the rate of change and evolution of the cloud makes it difficult to effectively standardize and codify an accepted model or process before it gets antiquated. Your best bet is to stop waiting, and to look at what's available to you today, through a variety of different lenses, and examine these options using multiple dimensions and criteria. For example, you can assess disaster recovery methods based on granularity—do you want DR at an application level or an infrastructure level? You can gauge your choices based on effort and responsibility—do you follow a do-it-yourself (DIY) approach versus a service-oriented approach? Your organization will undoubtedly start their evaluation with cost. Then there's compliance, or environmental and regulatory constraints that the backup of your applications and data...