Non Utility Disaster Recovery

Disaster Recovery of Non-Utility Storage

Case for exemption and removal from cost base

Business Case:

Our Newco corporate policy requires disaster recovery for all Production application systems that support critical Business Functions. These production systems that consume Mainframe processing and storage are commonly classified as Utility computing.

Non-Utility is defined as non-production or ad-hoc Mainframe processing or storage that is initiated by a user rather than a production system. Typical reasons for non-utility consumption is testing in a development environment or computing and storage of ad-hoc reports for use in the business.

Currently our DR strategy is to mirror the entire Mainframe environment, regardless of whether it is Utility or Non-Utility.

Our recommendation is that Non-Utility computing not be required for inclusion in Disaster Recovery. This is based on the definition of the current policy and the ad-hoc nature of this data which in most cases has low to no critical business need

By disabling Disaster Recovery of Non Utility consumption across Newco the business could potentially save $6.2MM annually, including both business consumption and Newco Tech's own internal consumption. Not only would the business partner notice the savings but it would also reduce the amount of expense recovery needed in Technologies.

Recommendations:

- Determine business criticality of retaining Disaster Recovery of Non Utility

- Work with Disaster Recovery team to assess opportunities and technical feasibility

Opportunity Sizing:

All Disaster Recovery costs associated with Non-Utility storage consumption:

Known Issues:

- There are automated ids that possibly run jobs that have a critical business need but we have identified those ids and they could be excluded from the DR disabling list

- Resources from the DR team in Newco Tech are being fully utilized to address existing gaps in