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

System database backup and restore


Backing up SQL Server system databases (everything) will restore and recover the SQL Server system in the event of a system failure, such as the loss of a hard disk. The system databases backup include msdb, master, and model. If replication is being used, the distribution database is required.

Note

The backup frequency and retention are usually based on the company's policy. As a general rule of thumb, take a daily full backup, followed by before and after backups when adding a new database or making structural changes to the SQL Server instance.

Backing up DB using SQL Server Management Studio

  1. Connect to your instance in the SQL Server database engine; on the left hand side, click on the server name to expand the tree.

  2. Click on the + to collapse the databases, then depending on the database, either select a user database or expand System Databases and select a system database.

  3. Right-click on the database, point to Tasks, and then click on Back Up. The Backup...