1. CTS Quarterly Customer Meeting
12/27/2018
CTS Quarterly Customer Meeting
CTS Disaster Recovery (DR) Project
October 22, 2014

2. Agenda Definitions CTS DR Current State CTS DR Upcoming Enhancements
CTS DR Project

3. COOP and DR Definitions

4. COOP / DR Continuity of Operations Plan Disaster Recovery Plan (DR)
12/27/2018
COOP / DR
Continuity of Operations Plan
Guided by FEMA established policies, definitions and assumptions that form the framework for emergency preparedness.
Includes the activities ensuring that essential functions which enable agencies to provide vital services, exercise civil authority, maintain the safety and well being of the general populace, and sustain the industrial/economic based in an emergency are performed.
Disaster Recovery Plan (DR)
Recovery of information technology assets, data, and services required to support critical business functions
One of the first lessons learned by the project team is that there are many different perceptions of COOP and DR.
Note: Backup/Recovery are different from Disaster Recovery

5. Business Impact Analysis
12/27/2018
Business Impact Analysis
When creating Disaster Recovery Plans, agencies identify their critical systems and document the operational, legal, and financial impact from a disruption or disaster affecting any computer or telecommunication service area of the agency.
We are asking that Agencies work with CTS to collaborate regarding critical systems which are dependent on CTS systems.
Fema - Business Impact Analysis (BIA) – A method of identifying the effects of failing to perform a
function or requirement.

6. Disaster Recovery Terms
When planning for recovery, agencies identify RTO and RPO for their systems.
A recovery time objective (RTO) is the period within which systems, processes, services, or functions must be recovered after an outage.
A recovery point objective (RPO) is more specific to information systems. It is the amount of data that can be lost measured by a time index.
Agencies should work with CTS to collaborate regarding recovery objectives that are dependent on CTS systems.

7. DR Site and Data Replication Terms
DR Site Options/Methodologies
Hot (space, equipment, and data already present - only minor configurations changes needed)
Warm (space and equipment is in place but typically has to be built/configured/data restored)
Cold (space reserved with no equipment)
Data Replication Options/Methodologies:
Active/Active (synchronous)
Active/Passive (asynchronous)
Restoration from backup

8. CTS Disaster Recovery

9. CTS Services with DR - Current State
12/27/2018
CTS Services with DR - Current State
Eastern United States:
IBM and Unisys Mainframes, TSM, DES Print
Eastern WA Node Site:
Shared Services (Exchange, Virus Protection, Filtering, Secure )
Enterprise Active Directory (Active Directory Federated Services, Domain Controllers)
Domain Name Services (DNS) (Hosted in Oregon)
Security Services (Secure Access Washington®; Secure File Transfer; SSL VPN)
Redundant SGN Internet Service Providers (ISPs)
Liberty Lake, WA (TierPoint):
Customer disaster recovery equipment
Gary shared information at the iCOOP meeting regarding the CTS services with DR.

10. CTS DR Upcoming Enhancements
Avamar and VTL Projects
TSM Service (for physical tape backups) is sunsetting and will be replaced by Avamar (virtual backups)
Mainframe Virtual Tape Library will expand to eliminate need for physical tapes
CTS’ Private Cloud
Roadmap includes DR
Load Balancing
Mobile Device Management
Implementing a Software as a Service (SaaS) Solution

11. CTS Disaster Recovery Project

13. DR Project Background DR Site Survey Project Findings
No government-owned data center in Eastern Washington met the requirements and/or allowed sufficient room for expansion to meet CTS needs
Existing Spokane Node DR site not a suitable long term DR Facility
TierPoint contract was nearing end of life
Decision was made to secure a contract with a Vendor to provide colocation data center services.

14. DR Project Status Scope
Identify Requirements for a single site DR location
Develop and publish RFP for DR site procurement
Released 7/29/14.
Review and select appropriate site
Responses were received 9/4/14. Announcement planned for 9/26/14.
Build out core Network and Security Infrastructure
Move existing CTS DR services to new DR colocation data center.
Define CTS’ future DR roadmap
Implement and expand DR in a phased approach
Establish new CTS DR service offering

15. DR Colocation Site ASV Sabey Data Center Properties, LLC
Over 3 million square feet of data center space
Close to 2 million square feet of data center space in Washington
Quincy, Wenatchee, and Seattle
Sabey’s DC in Quincy was selected
525,000 square feet of data center space
Concurrently maintainable facility
70 megawatts of power
Security personnel on site 24/7
Dedicated Office and Storage Space available

16. High Level DR Site Requirements
Some of the requirements include:
Within the State of Washington and east of the Pacific Crest Trail
Service Availability of %
Vendor background checks
HIPPA Business Associates Agreement compliance
NIST Security and Privacy Controls for Federal Information Systems and Organizations compliance
ANSI/TIA-942 A-1 Telecommunications Infrastructure Standard for Data Center compliance
24/7 hours of operational and physical access
Vendor provided enclosures
Concurrently Maintainable Facility (facilities components can be shutdown w/o disruption)
Technician Support Services (remote/smart hands)
Dedicated office space and equipment storage space
Staff facilities during declared disaster

17. DR Timeline Through June 2015

18. Questions Mark Quimby Heidi Brownell DR Architect
Consolidated Technology Services
(360)
Heidi Brownell
Chief Project and Planning Officer
Consolidated Technology Services
(360)