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

The 3 Cs of SharePoint Development


The classic definition of software development is most often associated with programming or writing code, but to leverage the vast power of SharePoint, we must start to think of it as Solution Development, which could include: configuration, customization, and coding. In fact, it is not appropriate to use the word "could" when in nearly every solution it "will" involve all three C's – Configure, Customize and Code. These are defined in the following figure:

The first C of development, configuration, happens all over SharePoint, at the list, library, or site level using their respective settings, or at the site collection or farm level. By configuring SharePoint features, we enable or tune the functionality to best suit our desired purpose. For example, a contract management solution would undoubtedly require version control, workflows, check in/check out, and content approval.

These settings can be standardized, and are discussed later in the chapter, but...