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

Horror stories that the authors have witnessed


Every IT veteran has a horror story; the following are just a few horror stories that the authors have witnessed.

Backups only

Many organizations have suffered from this simple oversight. Backups are scheduled, and methodically taken. When a restore is needed, the backups are found to be non-functional. Due to be bad media or faulty backup configuration.

Tip

Lesson Learned: A backup has no value if it can't be restored. A DR plan has to include testing a restore.

Pixar's near loss of Toy Story 2

A worker at Pixar accidentally ran a command that wiped out 30 years of work on the movie Toy Story 2. The local nightly backup had been silently failing for over a month. In the end, a backup was found on a director's laptop.

Tip

Lessons learned: Test the backups. Ensure they can be restored.

This is explained further in the following link:

http://www.zetta.net/blog/pixar-deleted-toy-story-2-cloud-disaster-recovery-hero/

SharePoint backup encrypted

For security reasons, a hedge fund encrypt their backups. Sounds good until they tried to do a restore. The encryption keys were on the backup.

Tip

Lessons learnt: Test the restore process. Practice makes it perfect.

Solution retraction caused web application failure

Retracting a solution can cause web applications including Central Administration to fail. This occurred when uninstalling an older version of a great tool (Idera SharePoint Manager) and also trying to uninstall the SP Diagnostic toolkit.

Tip

Lessons learnt: Try retracting first in development.