System and method for reversing changes executed by change management

Abstract

In an example embodiment, updated repository instances are typically developed on a development system, transferred to a testing system, and after testing, transferred to a production system. Such an updated instance may comprise content, sources and a data dictionary. As an updated instance is moved from one system to another, the change is applied to an original instance. A shadow copy of content is kept for the original instance. In another example embodiment, a shadow copy of content is created as part of the change process. The sources and data dictionary may have their own versioning mechanism. To undo the applied change, the sources and data dictionary are rolled back to their pre-change state. The content is retrieved from the shadow copy and restored to the original instance. Finally, stranded data is restored according to appropriate policies.

Dependencies are inferred from the claim text.