IS-12 Recovery Level & Tier Information
This table lists out the Recovery Level classification as described in the IS-12 policy. We added 5 additional columns to map the recovery levels to disaster recovery tiers.| IS-12 Recovery Level | Currently In Scope for IS-12? | IS-12 Description | Recovery Time Objective (RTO) | Disaster Recovery (DR) Tier | Recovery Point Objective (RPO) | Technology Description | Tier Definition | DR Strategy |
|---|---|---|---|---|---|---|---|---|
| 5 | Yes | Core technology and infrastructure | Up to 15 minutes | 0 | Up to 15 minutes | Real time data replication between data centers (Active Directory, DNS, DHCP). | Core technology infrastructure that requires multiple data centers to be able to serve production without manual intervention. | Geographically Clustered (Active-Active) |
| 4 | Yes | Critical 1 - Life/safety/alternatives not sustainable | Up to 6 hours | 1 | Up to 4 hours | Dedicated DR environment at alternate data center. Servers are racked, configured, tested, and ready to use at alternate data center. Asynchronous replication of business data and system states to available hardware. | Systems critical to campus Life/safety, financial operations, UCI core services and support systems. Failure to function for even a short period of time could have a severe impact on campus operations. Manual downtime procedures are planned, but cannot be sustained for a long period of time. | Hot/Warm Standby |
| 3 | Yes | Critical 2 - Alternatives sustainable up to 24 hours | Up to 24 hours | 2 | Up to 24 hours | Servers are provisioned and configured at alternate site. Replicated snapshots throughout day to available hardware. | Systems are required in order to perform critical Campus and business operations, but can allow for manual processes for up to 1 day as a reasonable workaround. | Warm Standby |
| 2 | No | Necessary | Up to 5 days | 3 | Up to 24 hours | Hardware and servers are reserved or allocated at an alternate data center. Backup restoration to hardware with horizontal scaling and ship on-demand hardware. | Systems are necessary to UCI operations, but short-term interruption or unavailability of 1 to 5 days is acceptable. | Cold Standby |
| 1 | No | Deferrable | Up to 30 days | 4 | Up to 24 hours | Quick ship agreements may be possible with preferred vendors for delivery at time of disaster. No hardware in place at alternate site. | The functions affected do not jeopardize life/safety, financial operations, core services or support systems and manual procedures could be used until system is available. | ATOD (At Time of Disaster) |