Transcript 10174A_13 - See So Clear

Module 13
Implementing Business
Continuity
Module Overview
• Protecting and Recovering Content
• Working with Backup and Restore for Disaster Recovery
• Implementing High Availability Solutions
Lesson 1: Protecting and Recovering Content
• Configuring Version Control
• Configuring and Managing the Recycle Bin
• Importing and Exporting Content
Configuring Version Control
Version Control is used to maintain historical elements of a
document or list item
Version Control has the following options:
• No versioning
• Major version
• Major and minor versions
Configuring and Managing the Recycle Bin
The Recycle Bin is a means of simple content recovery
that users can perform in a Microsoft® SharePoint® 2010
implementation
The Recycle Bin has 2 stages:
• Stage 1—users can recover their items
• Stage 2—administrators must assist in the recovery
The process to go from Stage 1 to Stage 2 depends on the
configuration of the Recycle Bin settings
Importing and Exporting Content
• Based on Content Migration API
• Can target Sites, Lists and Libraries
• Can be done using Central Administration, STSADM and
Windows PowerShell
• Not a backup/restore replacement
Lesson 2: Working with Backup and Restore for
Disaster Recovery
• Defining Disaster Recovery
• Protecting Content Using Backups
• Protecting the Farm Using Backups
• Backing Up Configuration Settings and Service Applications
• Protecting Customizations
• Working with Restore
• Using System Center Data Protection Manager
Defining Disaster Recovery
Disaster recovery is not a technology, but rather a
combination of process definition and procedures
This is normally defined:
• Recovery Point Objective (RPO)—this defines the amount
of data intended to be recovered in the event of failure
• Recovery Time Objective (RTO)—this defines the time that
will elapse to be in operational soundness
Protecting Content Using Backups
• Content is perhaps the most critical element to protect in a
SharePoint configuration because it represents the vast
amount of effort that users have put into the system
• Backup and Restore of Site Collections

Using PowerShell

Using Central Administration

Using STSADM

Using SQL Server Backup
Protecting the Farm Using Backups
• A farm backup is intended to capture the elements of a
defined server or topology
• It also includes content and configuration for the farm
• Consider warm standby solutions
• Special considerations
Backing Up Configuration Settings and Service
Applications
• Configuration settings are included in farm backups, but
cannot be restored independently
• Configuration-only backups allow for this to be treated as
a separate safety layer
• It includes only elements that do not present constraints
to restore that would be tied to specific machine names
• Service applications allow for specific functionality in
SharePoint that implement settings or specific content to
be stored in databases
Protecting Customizations
• When there is customization by code, it is important to
consider them in your backup strategy
• It is likely you will need to have a copy or packaged
solution to increase effectiveness in saving this information
• This includes assemblies, features, site definitions, etc.
Working with Restore
Before you restore a Microsoft SharePoint 2010 farm,
ensure that the following requirements are met:
•
You must be a member of the Farm Administrators group
•
You must be a member of the SharePoint_Shell_Access role
•
You must be a member of the WSS_ADMIN_WPG local group
•
The Microsoft SQL Server® account, the Timer service account,
and the Central Administration application pool account must
have Read permissions to the backup locations
•
The database server's SQL Server account must be a member of
sysadmin fixed server role
•
Your login account must have Read permissions to the backup
locations
Ensure that the SharePoint Foundation Administration
service is started on all farm servers
Using System Center Data Protection Manager
Production farm
CMP
4
3
1
DPM
Server
2
Recovery
Database
Server
Web FrontEnd
Database
Servers
Lesson 3: Implementing High Availability Solutions
• Understanding High Availability
• Understanding SharePoint Roles and Services
• Working with Load Balancing
• Implementing SQL Server Clustering
• Implementing SQL Server Database Mirroring
• Implementing Log Shipping
• Working in Read-Only Mode
Understanding High Availability
• Allows for uninterrupted server uptime
• Can be used to satisfy SLAs
• Requires extra hardware and time resources to configure
Understanding SharePoint Roles and Services
SharePoint is defined by servers providing access to different
services
The roles are identified as:
• Web Front-End
• Application Servers
• Database Server
Working with Load Balancing
Client Request (10.1.1.1)
Network Load Balancing Host
Dedicated IP: 10.1.1.2
Virtual IP: 10.1.1.1
Accept?
No
Network Load Balancing Host
Dedicated IP: 10.1.1.3
Virtual IP: 10.1.1.1
Accept?
No
Network Load Balancing Host
Dedicated IP: 10.1.1.4
Virtual IP: 10.1.1.1
Accept?
Yes
Client
Network Load Balancing Host
Dedicated IP: 10.1.1.5
Virtual IP: 10.1.1.1
Accept?
No
Network load balancing provides high availability and scalability
for services
Implementing SQL Server Clustering
In a failover cluster, a group
of servers work together to
increase the availability of a
set of applications and
services
Failover Cluster
Client
Client
Implementing SQL Server Database Mirroring
• Defined as a protection level that is intended to cover the
database marked as primary by having redundancy of
data
• Scope of protection—database
Implementing Log Shipping
• Overview
• Operations
• Roles
• Combining Technologies
Working in Read-Only Mode
SharePoint 2010 supports Read-Only databases
The user experience of a read-only site is characterized by the following:
• Common tasks that do not require writing to the content
database are fully available
• Most of the common tasks that require writing to the
content database are not available
• Several common tasks that require writing to the content
database appear to be available, but return errors
Lab A: Implementing a Backup Strategy
• Exercise 1: Backing Up SharePoint Using Central
Administration
• Exercise 2: Investigating SharePoint Backup Logs and Files
• Exercise 3: Automating SharePoint Backup Using Windows
PowerShell
Logon information
Virtual machine
10174A-CONTOSO-DC-E
10174A-SP2010-WFE1-E
Administrative user name
CONTOSO\Administrator
CONTOSO\SP_Admin
Password
Pa$$w0rd
Pa$$w0rd
Logon user name
Estimated time: 30 minutes
Scenario
You have recently set up a Microsoft SharePoint 2010 farm.
Your corporate IT policy states that all mission critical
application be backed up nightly and if database-based,
have transactional logs turned on. You have been tasked
with implementing an automated backup strategy that
fulfills this policy requirement.
Lab B: Implementing a Restore Strategy
• Exercise 1: Restoring a Web Application Using Central
Administration
• Exercise 2: Investigating SharePoint Restore Logs and
Files
• Exercise 3: Performing a Partial Restore
Logon information
Virtual machine
10174A-CONTOSO-DC-E
10174A-SP2010-WFE1-E
Administrative user name
CONTOSO\Administrator
CONTOSO\SP_Admin
Password
Pa$$w0rd
Pa$$w0rd
Logon user name
Estimated time: 30 minutes
Scenario
You have recently set up a Microsoft SharePoint 2010 farm
and an automated nightly backup process. Corporate IT
policy requires you to test your backups every 60 days.
You have been tasked with testing the latest by restoring it
to a staging environment. As part of the policy, you must
also test that you can perform a partial restore of a site
collection, site, and list.
Module Review
• Review Questions