44

Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Embed Size (px)

Citation preview

Page 1: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349
Page 2: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Disaster Recovery for SharePoint 2013 with AzureNeil Hodgkinson M349

Page 3: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Neil HodgkinsonPre-MicrosoftProcess Chemist (Drugs, Poisons and Explosives)

CSC SharePoint Specialist – 5 Years

Microsoft (2005-)SharePoint PFE - 5 Years

SharePoint Service Engineering O365 - 3 Years

Office 365 CXP CAT - Current

MCSM SharePoint Instructor Team

ContactEmail – [email protected]

Twitter - @nellymo

Page 4: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Agenda

Disasters and Recovery (DR) DR Terms DR scenarios DR tools ASR Setup And Configuration SharePoint specifics

Page 5: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Disaster Types

Forecasted event - the impact can be foreseen (such as a weather system event such as a hurricane) and can be mitigated through prior planning.

Un-forecasted event - the organization cannot provide a mitigation plan due to the immediate timing of the event itself (such as an earthquake or cyber security attack) or the realization of previously accepted risk factors.

5

Page 6: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Disaster Recovery• “The process, policies, and procedures that are related to

preparing for recovery or continuation of technology infrastructure which are vital to an organization after a natural or human-induced disaster.”

• Disaster Recovery is about recovering the critical operations that enable the business to function

A company denied access to its mission-critical data for more

than 48 hours will likely be out of business

within the year

1 in 4 businesses never

re-open their doors after a disaster

Page 7: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Define Business Continuity ManagementBusiness Continuity Management (BCM) is a management process or program that defines, assesses, and helps manage the risks to the

continued running of an organization.

Focuses on creating and maintaining a business continuity plan, which is a roadmap for continuing operations when normal business

operations are interrupted by adverse conditions. These conditions can be natural, man-made, or a combination of both.

A disaster scenario is not a business as usual scenario

How long can my business NOT perform this function without suffering

Page 8: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Planning and DriversMulti stage planning process

AnalyseDefineDocumentImplement

Most – ImportTEST it and TEST it again

A business impact analysis

A threat and risk analysis

A definition of the impact scenarios

A set of documented recovery requirements

Solution design or identified options, an implementation

plan, a testing and organization acceptance plan, and a maintenance

plan or schedule

Page 9: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Disaster Recovery Terms

RTO Recovery Time Objective Fail over in Minutes. DR Drill each action recorded for total time.

RPO Recovery Point Objective. How much data loss? Near-Synchronous as low as 30 second replication.

Page 10: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Disaster Recovery Options and Tools

SharePoint Backup/Restore SQL Server

Log Shipping Mirroring Always On Availability Groups

Third Party Options Azure Site Recovery !

Page 11: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

ASR – Azure Site Recovery

Replication of Machines based on admin defined policies. Supported Technologies

SQL AlwaysOn Hyper V System Center VMware VMs to VMware VMs NetApp/HP/EMC SAN replication And………..more…..

Page 12: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Protect Customer’s ApplicationOn-premises to Azure protection with ASR

Key features include:

Use Azure as your replication site

Automated VM protection and replication

Remote health monitoring

Customizable recovery plans

No-impact recovery plan testing

Orchestrated recovery of tiered applications

NEW: Support for heterogeneous environments

Replication into Azure for SMBs and remote branch offices without System Center

Orchestrationand replication

Microsoft Azure Site Recovery

Enterprise & HSP

primary site

Windows Server

Orchestrationand replication

Microsoft Azure Site Recovery

Enterprise, SMB & HSP

primary site

VMware/Physical

GA

Orchestrationand replication

Microsoft Azure Site Recovery

SMB & branch

primary site

Windows Server

Page 13: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Protect Customer’s Applications On-premises to on-premises protection with ASR

Key features include:

Use customer’s replication site

Automated VM protection and replication

Remote health monitoring

Customizable recovery plans

No-impact recovery plan testing

Orchestrated recovery of tiered applications

NEW: Support for heterogeneous environments

Microsoft Azure Site Recovery

Communication channel

Replication channel:

Hyper-V Replica or SAN

replication

Primarysite

Windows Server

Recovery site

Windows Server

Microsoft Azure Site Recovery

Download ASR Scout

Replication and orchestration

channel

Primary site

VMware/Physical

Recovery site VMware

Page 14: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

ASR – Azure Site Recovery

Can be Synchronous Near-Synchronous Or whatever the business requirement is Can store way points to restore to. Single Button TRUE Failover

Paired with System center – Automated SUPER Cheap insurance

Page 15: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

ASR – Azure Site Recovery

Costs – mileage will vary 2 WFE, 3 APP, 1 AlwaysOn (2 SQL) = $378 USD month $54 USD per instance, per month OnPrem-Azure

NO add. costs VMs stored in StorageOnly cost more via IaaS when you fail overvia EA = 100GB storage, 100GB fail backOther purchased plans don’t include storage

$16 USD per instance, per month OnPrem-OnPrem

Page 16: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

ASR – Azure Site Recovery

Data Costs First time Sync FULL VHD needs to be pushed over the wire After full sync, only deltas are pushed Only the data used in the VHD (not the virtual size) will be sent to

Azure and stored in Azure* 3rd party compression tools are available and more coming

Page 17: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

ASR – Azure Site Recovery

Connection needed: Public internet - Default Site-2-Site VPN ExpressRoute

Doesn’t actively “support” VHDX yet. Doesn’t support Gen2 (yet)

Page 18: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Physical to Azure

Mobility Service auto installed on each physical Intercepts changes in workloads sends to Process Server Encrypts and sends changes to Master Target Writes those changes to the Target committing them to Azure

Storage / IaaS

Required: Config Server. Fill in the blanks Azure can build it for you!

Page 19: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Physical 2 Azure Requirements Server 2012 R2, Server

2012 or Server 2008 R2 SP1

Hostname, Mount Points, Device Names and system path in English only

OS on C Drive Firewall open to reach

Azure

Max 31 disk protected per server

less than 1023 GB No Clustered Servers UEFI not supported No bitlocker Server Names 1-63

char.

Page 20: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

DR Planning - Revisited

Trade-offs between Cost and RPO/RTO ASR supports all options! DR with RPO of 5 minutes and RTO of 1 HourLeverage ASR Host or Guest based replication for all tiers of the application.

DR with RPO of 5 minutes and RTO of ~30 minutes

Leverage AD replication for AD, SQL Availability Group for SQL and ASR replication for Web and Middle Tiers.

DR with 0 RPO (No data loss)Leverage SAN based replication support of ASR

Test failover – measure and improve

Page 21: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Physical to Azure - Walkthrough

Neil Hodgkinson

Page 22: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

View step-by-step guidance

QUICK START

2

A group for servers to represent Site or Branch.

CREATE SITE

3

Register Hyper-V Server

REGISTER

4

Define protection policy

CONFIGURE PROTECTION

5

Step by Step

6

Replicate disks to Azure

PROTECT VIRTUAL MACHINES

8

Test the deployment

RUN DR DRILL

Customer selects recovery region

CREATE VAULT

1

Define DR Plan

CREATE RECOVERY PLAN

7

Page 23: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

POC Requirements (1 Host)

One Hyper-V 2012 R2 Host Connectivity to Azure from Host either direct or through proxy One Azure account – free trial sign-up. Every ASR Instance you protect is free for 31 days. Getting started for Branch office to Azure DR

https://azure.microsoft.com/en-us/documentation/articles/site-recovery-hyper-v-site-to-azure/

Page 24: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

What about SharePoint?

Page 25: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Enable DR of SharePoint server using ASRProtect your SharePoint Server farm

Each component of the SharePoint farm needs to be protected to enable farm replication and recovery. Protection of Active Directory Protection of SQL Tier Protection of App and Web Tiers Protection of Search Service Application Networking configuration

Page 26: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Active DirectoryReplicate AD to Azure

For small environments where failover will be for entire site

Extend AD to secondary site

For more complex environments where partial failover may be required

Page 27: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

SQL Server Databases• Always On Availability

Groups• Three availability groups• Content• Search• Services

• One availability group can simplify azure deployment

Node 3Node 1 Node 2

W a h id Sa le e m i

Default Instance Default Instance Default Instance

Availability Group: AG_Content

Primary Replica

Secondary Replica

Secondary Replica

Availability Group: AG_Search

Primary Replica

Secondary Replica

Availability Group: AG_Services

Primary Replica

Secondary Replica

Secondary Replica

Storage Storage Storage

Windows Server Failover Cluster (WSFC)

Availability Group ListenerVirtual Network Name

Availability Group ListenerVirtual Network Name

Availability Group ListenerVirtual Network Name

Primary DatacenterNetwork Subnet 1

Alternate DatacenterNetwork Subnet 2

WSFC QuorumFile Share

sync sync

sync sync

sync sync

W a h id Sa le e m i

async

W a h id Sa le e m i

async

Search Databases

With ASR only, Asynchronous Replication ofFarm Configuration DatabaseAdmin Content DatabaseFULLY SUPPORTED

Page 28: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

SharePoint Servers

Configure Virtual Machine Protection

Page 29: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

NetworkingFor the App and web tier VMs configure network settings in ASR so that the VM networks get attached to the right DR network after failover.

Ensure the DR network for these tiers is routable to the SQL tier.

White Paper on ASR Networks : https://gallery.technet.microsoft.com/Designing-Your-Network-a849fa98

Page 30: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

DNSFor internet facing sites, create an instance of Traffic Manager in the Azure subscription and configure it and your DNS in the following manner.

Where Source Target

Public DNS Public DNS for SharePoint sites

Ex: asrsponprem.obs-test.com

Traffic Manager

contososharepoint.trafficmanager.net

On-premises DNS

sponprem.obs-test.com <Public IP on the on-premises farm>

Don’t forget to add the cloudapp.net DNS domain as an AAM

Page 31: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

ASR Replication is Asynchronous

SharePoint search requires Database and Index Synchronisation

Must follow search service application backup and restore guidance https://technet.microsoft.com/en-us/library/ee748654(v=office.15).aspx

Alternative approach is to use new search service application and crawl

Restore Search

Page 32: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

The Big Picture

NAT

Azure10.0.0.0/24

On Premises192.168.0.0/24 S2S

SQL Always On

ASR replication

ASR replication

ASR/AD replication

Database

SP App

SP Web

ADDNS

Database

SP App

ADDNS

Public

EndPointPublic

EndPoint

ATM

Public DNS

Failover

SP Web

Page 33: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Failover and Failback

Page 34: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Failover

Different Modes Test Planned Unplanned

SharePoint config cache flush – Required for all

Page 35: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Test Failover – No impact on Prod

Select Network to fail over toValidate failoverMark as completeAuto cleaned up

Page 36: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Planned and Unplanned

Select Network to fail over toValidate failoverUnplanned requires confirmation

Page 37: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Config Cache FlushAdd-PSSnapin -Name Microsoft.SharePoint.PowerShell –erroraction SilentlyContinue Stop-Service SPTimerV4 $folders = Get-ChildItem C:\ProgramData\Microsoft\SharePoint\Config foreach ($folder in $folders) { $items = Get-ChildItem $folder.FullName -Recurse foreach ($item in $items) { if ($item.Name.ToLower() -eq "cache.ini") { $cachefolder = $folder.FullName } } } $cachefolderitems = Get-ChildItem $cachefolder -Recurse foreach ($cachefolderitem in $cachefolderitems) { if ($cachefolderitem -like "*.xml") { $cachefolderitem.Delete() } } $a = Get-Content $cachefolder\cache.ini $a = 1 Set-Content $a -Path $cachefolder\cache.ini read-host "Do this on all your SharePoint Servers - and THEN press ENTER" start-Service SPTimerV4

Page 38: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Failback

Failback SQL Always On Failback ASR Recover Search Flush Config Cache

Page 39: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Wrap Up !

Page 40: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Currently Available Application-Aware ASR Solutions Workload

Hyper-V VMWare

Site to Site Site to Azure Site to Site Site to Azure

AD, DNS Infra

COMING SOON!

Web Apps IIS

SQL

SCOM

SharePoint

SAP*

Exchange**COMING SOON

Remote Desktop/VDI

Linux (OS & Apps)

Dynamics

AX

CRM COMING SOON

COMING SOON

Oracle DBCOMING SOON

COMING SOON

File Server

Supported and Certified by workload teamSupported – Certification by workload team in process

SAP Site to Azure for un-clustered setups.

Exchange 2013 Non-DAG setups

View based on in-market solutions

***

Page 41: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Related Ignite NZ Sessions

Use Azure Site Recovery to mitigate DR risk at VMware sites Ballroom 2 Wed 13:55

Find me later at… Hub Happy Hour Wed 5:30-6:30pm Hub Happy Hour Thu 5:30-6:30pm Closing drinks Fri 3:00-4:30pm

1

Azure Infrastructure As A Service Overview & What’s NewM318 Wed 11:55am

Getting ready for SharePoint 2016M311 Tue 9:00am

SharePoint deployment automation with PowerShell Desired State Configuration M388 Thu 11:00am

1

2

3

4

Page 42: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Resources

TechNet & MSDN FlashSubscribe to our fortnightly newsletter

http://aka.ms/technetnz http://aka.ms/msdnnz

http://aka.ms/ch9nz

Microsoft Virtual AcademyFree Online Learning

http://aka.ms/mva

Sessions on Demand

Page 43: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

Complete your session evaluation now and be in to win!

Page 44: Disaster Recovery for SharePoint 2013 with Azure Neil Hodgkinson M349

© 2015 Microsoft Corporation. All rights reserved.Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or

other countries.MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.