Abstract: Techniques are described for dynamically generating a disaster recovery plan. In an embodiment, a set of topology metadata is determined for a first site on which a multi-tier application is deployed and a second site where the multi-tier application will be activated in the event of switchover/failover. The topology metadata may include metadata that identifies a set of targets associated with a plurality of tiers on the first site on which the multi-tier application is deployed and also on the second site where the multi-tier application would be activated in the event of disaster recovery operation like switchover or failover. Based, at least in part, on the topology metadata for the first site and second site, a disaster recovery plan is generated. The disaster recovery plan includes an ordered set of instructions for deactivating the multi-tier application at the first site and activating the multi-tier application at a second site.

Abstract: Techniques are described for validating a disaster recovery plan. In an embodiment, a request is received to perform a validation of a disaster recovery operation plan that includes a set of instructions for performing a disaster recovery operation with respect to a first site and a second site. In response to receiving the request to perform the validation of the disaster recovery operation plan, a set of one or more validation operations is performed with respect to the disaster recovery operation plan. Based on the set of one or more validation operations, a report is generated that identifies one or more issues that may prevent the disaster recovery operation plan from executing properly.

Abstract: Techniques are described for providing error management capabilities for disaster recovery operations. In an embodiment, first user input is received that identifies a first error mode to assign to a particular step of a disaster recovery plan that includes a set of steps for performing a disaster recovery operation. In response to receiving the first user input, the particular step is associated with the first error mode. In response to determining that an error occurred while processing the particular step of the disaster recovery plan, the error mode that is associated with the particular step is determined. Error handling is performed for the particular step based, at least in part, on the error mode that is associated with the particular step of the disaster recovery plan.

Abstract: Techniques are described for providing error management capabilities for disaster recovery operations. In an embodiment, first user input is received that identifies a first error mode to assign to a particular step of a disaster recovery plan that includes a set of steps for performing a disaster recovery operation. In response to receiving the first user input, the particular step is associated with the first error mode. In response to determining that an error occurred while processing the particular step of the disaster recovery plan, the error mode that is associated with the particular step is determined. Error handling is performed for the particular step based, at least in part, on the error mode that is associated with the particular step of the disaster recovery plan.

Abstract: Techniques are described for dynamically generating a disaster recovery plan. In an embodiment, a set of topology metadata is determined for a first site on which a multi-tier application is deployed and a second site where the multi-tier application will be activated in the event of switchover/failover. The topology metadata may include metadata that identifies a set of targets associated with a plurality of tiers on the first site on which the multi-tier application is deployed and also on the second site where the multi-tier application would be activated in the event of disaster recovery operation like switchover or failover. Based, at least in part, on the topology metadata for the first site and second site, a disaster recovery plan is generated. The disaster recovery plan includes an ordered set of instructions for deactivating the multi-tier application at the first site and activating the multi-tier application at a second site.

Abstract: Techniques are described for validating a disaster recovery plan. In an embodiment, a request is received to perform a validation of a disaster recovery operation plan that includes a set of instructions for performing a disaster recovery operation with respect to a first site and a second site. In response to receiving the request to perform the validation of the disaster recovery operation plan, a set of one or more validation operations is performed with respect to the disaster recovery operation plan. Based on the set of one or more validation operations, a report is generated that identifies one or more issues that may prevent the disaster recovery operation plan from executing properly.

Abstract: Various arrangements for managing access to unstructured data are presented. A plurality of access requests may be received from a plurality of remote computer systems to a plurality of business entities stored by a content management server. In response to receiving a request for access to a business entity of the plurality of business entities stored by a content management server from a remote computer system, an identifier request may be transmitted to the content management server. A response from the content management server may be received in response to the identifier request. A resource locator that comprises the identifier may be created. The resource locator may be transmitted to the remote computer system for use in accessing the business entity.

Abstract: Various arrangements for managing access to unstructured data are presented. A plurality of access requests may be received from a plurality of remote computer systems to a plurality of business entities stored by a content management server. In response to receiving a request for access to a business entity of the plurality of business entities stored by a content management server from a remote computer system, an identifier request may be transmitted to the content management server. A response from the content management server may be received in response to the identifier request. A resource locator that comprises the identifier may be created. The resource locator may be transmitted to the remote computer system for use in accessing the business entity.