Building your Server for High Availability and Disaster
Building your Server for High Availability and Disaster Recovery Witt Mathot Danny Krouk
Terminology Whoa! Backups RPO Resiliency Load Balancer Fault Tolerance RTO Redundancy Contingency Federation Disaster Recovery Failover Geographic Redundancy Recovery High Availability SLA Continuity Mission Critical Data Loss Threshold Round Robin Change Management Active-Active BC/BCM Active-Passive
Business Continuity A Spectrum, Not a Switch Backup & Recovery High Availability Geographic Redundancy w/ High Availability
Business Continuity A Spectrum, Not a Switch Cost Momentary Interruption Workday Interruption Business Interruption Days Hours Minutes Recovery Time & Point (decreasing) Seconds
Business Continuity A Spectrum, Not a Switch Tier Criticality Recovery Time (RTO) Recovery Point (RPO) Tier 1 Mission Critical < 4 hours < 1 hour Tier 2 Business Critical < 24 hours < 1 hour Tier 3 Significant < 72 hours < 48 hours Tier 4 No Impact < 1 week
Arc. GIS Your Favorite GIS Desktop Web Device Simple Integrated Web GIS Open portal Server Online Content and Services Available in the Cloud… … or On-Premises
Arc. GIS Your Favorite GIS Simple Integrated Web GIS Open portal Server On-Premises
Arc. GIS The Platform Components Apps Portal GIS Services Data Store Content
Portal Arc. GIS Server Enterprise GDB GIS Services Portal for Arc. GIS Server Data Store Arc. GIS Enterprise Data Store GDB(s)
Portal Arc. GIS Server GIS Services Data Store Portal for Arc. GIS Server Arc. GIS Data Store
Server GIS Web GIS Portal Arc. GIS Server GIS Services Data Store Portal for Arc. GIS Server Arc. GIS Data Store
Server GIS Arc. GIS Server Patterns for High Availability & Disaster Recovery
Arc. GIS Server Single Machine Deployment Arc. GIS Server
Arc. GIS Server Single Machine Deployment Infrastructure Arc. GIS Server Processing (Physical / Virtual) Storage (Local / Shared) Network
Arc. GIS Server Single Machine Deployment
Arc. GIS Server Multiple Machine Configuration Options Silo Configuration Stores Site (shared)
Arc. GIS Server Multiple Machine Configuration Options Silo Site Load Balancer Configuration Store (shared) Configuration Stores
Arc. GIS Server Load Balancing Options Arc. GIS Web Adaptor 3 rd Party Load Balancer • Provided by Esri • Not provided by Esri (e. g. F 5, CSM) • Works w/ Arc. GIS Server sites (not silos) • Works w/ Arc. GIS Server sites & silos • Discovers new machines dynamically • Doesn’t discover new machines dynamically • Availability dependent on web servers • Hardware options typically already fault tolerant • Enables additional security patterns
Arc. GIS Server Load Balancing Options Multiple Web Adaptors w/ 3 rd Party Load Balancer • Leverages existing 3 rd Party Load Balancer • Enables additional security patterns • Discovers new machines dynamically • Fault tolerant • More moving pieces
Arc. GIS Server High Availability Deployment Patterns Key Considerations • Full Fault Tolerance (i. e. no single Web Adaptor) • Web-tier Authentication (i. e. Web Adaptor required) • Publication Workflows & Server Management (i. e. Site vs. Silo) • Highly Available Shared Storage (i. e. Site vs. Silo) • Highly Available Load Balancer (i. e. required!) • Throughput (i. e. active-active or active-passive) • Licensing Fees (i. e. active-active or active-passive) • Functional Limitations (e. g. Silos and async GP, offline maps)
Arc. GIS Server High Availability Patterns Multiple Machine HA w/ 3 rd Party Load Balancer Multiple Machine HA w/ 3 rd Party LB & Web Adaptors Load Balancer Web Adaptors Arc. GIS Servers Configuration Store (shared) • Simpler, less moving parts • More complex • Doesn’t support certain security patterns • Supports additional security patterns
Arc. GIS Server High Availability Patterns Single Machine (Silo) HA Patterns Single Machine HA (active-passive) (active-active) Load Balancer Web Adaptors (optional) Arc. GIS Servers Configuration Stores • Single Machine Throughput • Multiple Machine Throughput • Single Machine Licensing Fees • Multiple Machine Licensing Fees
Demo Arc. GIS Server High Availability
Load Balancer - Port translation - Virtual directory - ‘Public’ domain name Site - ags 1 - ags 2 - Single Cluster Mode - No Web Adaptor - Web. Context. URL Highly Available File Share - Config store - Server directories
Arc. GIS Server High Availability Deployment Patterns Comparison Site w/ Web Adaptor Site w/ 3 rd Party LB Silo, active-active Silo, active-passive Supports web-tier Yes authentication No Yes Publishing Multiple Times No No Yes Requires HA Shared Storage Yes No No Requires 3 rd Party Yes LB Yes Yes Throughput All Machines One Machine Licensing All Machines One Machine Functional Limitations None Many
Disaster Recovery Typical Workflow Global DNS Primary Data Center Secondary Data Center
Disaster Recovery Typical Workflow Global DNS Primary Data Center Secondary Data Center
Arc. GIS Server Disaster Recovery Patterns Managed Publishing Pattern Global DNS LB Arc. GIS Server Managed Publishing Configuration Store Directories Primary Data Center Configuration Store Directories Secondary Data Center
Arc. GIS Server Disaster Recovery Patterns Site Backup / Restore Pattern Global DNS LB LB Arc. GIS Server Site Backup / Restore Configuration Store Directories Primary Data Center Configuration Store Directories Secondary Data Center
Arc. GIS Server Disaster Recovery Deployment Patterns Comparison Managed Publishing Pattern Site Backup / Restore Pattern Operational Impact Managed, concurrent publishing Site Export and Import Script Use Type Active-Active or Active-Passive Supports Automated Failover Yes (note site will be down during import) Additional Considerations Not possible when federating with Portal for Arc. GIS Web Adaptor must be reconfigured after site import Challenging when federating with Portal for Arc. GIS
Server GIS Deployment Patterns Summary • There Are Patterns to Meet Your Non-Functional (IT) Requirements • Consider These Requirements… - Full fault Tolerance (i. e. no single Web Adaptor) - Web-tier Authentication (i. e. Web Adaptor required) - Publication Workflows & Server Management (i. e. Site vs. Silo) - Highly Available Shared Storage (i. e. Site vs. Silo) - Highly Available Load Balancer (i. e. required!) - Throughput (i. e. active-active or active-passive) - Licensing Fees (i. e. active-active or active-passive) - Functional Limitations (e. g. Silos and async GP, offline maps) - Geographic Redundancy (i. e. disaster recovery) … it is possible to achieve RTOs and RPOs of < 1 min!
Web GIS Full-Stack On-Premises Patterns for High Availability & Disaster Recovery (Portal for Arc. GIS, Arc. GIS Server, Arc. GIS Data Store)
Web GIS On-Premises Components Portal GIS Services Data Store Portal for Arc. GIS Server Arc. GIS Data Store
Portal for Arc. GIS A Brief Introduction • Separate install & processes from Arc. GIS Server • Can co-exist on same machine as Arc. GIS Server (not recommended in production) • Has architectural similarities w/ Arc. GIS Server • - Internal application server - Config / Content store on disk - Leverages Web Adaptor Has architectural differences w/ Arc. GIS Server - Has some different internal components - Web Adaptor required for single machine deployments - Web Adaptor cannot load balance multiple machines - Multi-machine configurations limited to 2 machines
Portal for Arc. GIS Load Balancing Options Portal w/ 3 rd Party LB Portal w/ Multiple Web Adaptors & 3 rd Party LB NOTE: The Web Adaptor cannot load balance multiple machines
Portal for Arc. GIS High Availability Pattern Portal HA w/ 3 rd Party Load Balancer Portal HA w/ 3 rd Party LB & Web Adaptors Load Balancer Web Adaptors Portal for Arc. GIS Content Store (shared) • Simpler, less moving parts • More complex • Doesn’t support certain security patterns • Supports additional security patterns
Demo Portal for Arc. GIS High Availability
Load Balancer - ‘Public’ domain name Web Adaptor & Portal - prtl 1 - prtl 2 - Port translation (WA) - Virtual directory (WA)
Web GIS On-Premises Components Portal GIS Services Data Store Portal for Arc. GIS Server Arc. GIS Data Store
Arc. GIS Server’s Role in the Web GIS Federation & Hosting Concepts Portal for Arc. GIS Server Arc. GIS Data Store Registered Services Federated Server Hosting Server
Web GIS On-Premises High Availability Pattern Putting the Pieces Together – Example 3 rd Portal HA w/ Party Load Balancer Multiple Machine HA w/ 3 rd Party Load Balancer Portal for Arc. GIS Servers Content Store (shared) Configuration Store (shared) Multiple Machine Arc. GIS Data Store
Web GIS On-Premises Disaster Recovery • Possible, but very challenging to implement today at 10. 3. 1 • Key Considerations: • - Active-passive Global DNS configuration - Can support hot or cold backups from primary - Restoration in secondary may take time (1 hr+ in some cases) - Machine names need to be identical in both data centers - Esri Professional Services required (done via local DNS or hosts file) Support for full Web GIS backup / restore planned for 10. 4
Server GIS Web GIS Portal Arc. GIS Server GIS Services Data Store Portal for Arc. GIS Server Arc. GIS Data Store
Summary Patterns Site w/ 3 rd Party LB & Web Adaptor Silo, Active-Active Silo, Active-Passive (on-premises) Web GIS Server GIS High Availability Two machines w/ 3 rd Party LB & WA Disaster Recovery Managed Service Publishing Site Backup / Restore Esri Professional Services More Coming at 10. 4
Want to learn more? • • Documentation & Links - Arc. GIS Server Deployment Scenarios - What is Portal for Arc. GIS - Using Your Portal with Arc. GIS Server - Configuring a High Availability Portal Sessions - Arc. GIS Server Reference Implementations - Portal for Arc. GIS: An Introduction
Thank you… • Please fill out the session survey in your mobile app • Select “Building your Server for High Availability and Disaster Recovery” - Use the Search Feature to quickly find this title • Click “Technical Workshop Survey” • Answer a few short questions and enter any comments
- Slides: 47