KFS DR Validation Process Overview

Validation Process Overview

The goal of a DR validation effort is to provide substantiative proof that the DR site implemented as a result of the agreement between UConn and rSmart is in fact viable and usable in a disaster situation. The testing process will focus on pre-selected key business functions that must be available and functioning in order for the minimum acceptable level of business to continue during a disaster.

The DR validation environment will include the test disaster site implemented in the cloud, and a local disaster environment implemented here at UConn.  These sites are intended to mirror one another in data content and software version. The plan involves establishing the local DR and the Cloud DR using the same application, system, and data files.  The testing process involves the execution of a predefied set of test scripts and scenarios against the cloud DR. Once this testing is completed successfully, the process of restoring local operations from the cloud will be executed. Following the successful restore process, actvities will be conducted in the local DR that are designed to validate that the data generated in cloud is present and intact. Lastly, functionality known to be at risk from the database export/import process will be tested.

The intention behind this effort is to formalize and document a validation process that can be to utilized to perform quaterly DR validation in an effort to ensure the readiness of both our DR provider and our internal support organizations should the unexpected occur.

DR Validation will be performed on a quarterly basis.  Each event is expected to take 5-6 business days to complete (see Project Plan).