Disaster recovery rehearsals
Various systems and methods for configuring and performing DR rehearsal operations. One method involves initiating a disaster recovery rehearsal for an application. The method involves generating a snapshot of a first storage element used by the application. The method also involves configuring a second storage element and starting an instance of the application. Starting the instance of the application utilizes the snapshot and the second storage element. Generating the snapshot, configuring the second storage element, and starting the instance of the application are performed in response to initiating the DR rehearsal.
1. A method comprising:
initiating a disaster recovery (DR) rehearsal for a multi-tiered application, wherein
the initiating comprises
quiescing the multi-tiered application, and
in response to the quiescing, inserting a marker into a stream of data that is being replicated, wherein
the marker is inserted into the stream of data that is being replicated after the multi-tiered application has been quiesced, and
the marker indicates that the multi-tiered application has been quiesced, and
transmitting the stream of data that is being replicated, which comprises the marker, from a primary site to a secondary site;
generating a snapshot of a first storage element used by the multi-tiered application, wherein
the generating is performed in response to detecting the marker in the stream of data that is being replicated, and
the snapshot is application-consistent with regard to at least two tiers of the multi-tier application;
configuring a second storage element;
starting an instance of the multi-tiered application using the snapshot and the second storage element; and
performing the disaster recovery rehearsal, wherein
the disaster recovery rehearsal is an application-consistent disaster recovery rehearsal,
the performing comprises using the marker without querying any log files to determine where the multi-tiered application was quiesced, and
the generating, the configuring, the starting, and the performing are performed in response to the initiating.
2. The method of claim 1 , wherein
the first storage element and the second storage element are located in a cloud computing environment.
3. The method of claim 1 , wherein
the first storage element and the second storage element are isolated from one another.
4. The method of claim 1 , further comprising:
identifying one or more storage elements associated with the multi-tiered application; and
synchronizing a pause of updates to the one or more storage elements.
5. The method of claim 1 , further comprising:
replicating updates to the first storage element, wherein
the updates are being replicated to the first storage element concurrently with performance of the DR rehearsal.
6. A non-transitory computer readable storage medium comprising program instructions executable to:
initiate a disaster recovery (DR) rehearsal for a multi-tiered application, wherein
initiating the DR rehearsal comprises
quiescing the multi-tiered application, and
in response to the quiescing, inserting a marker into a stream of data that is being replicated, wherein
the marker is inserted into the stream of data that is being replicated after the multi-tiered application has been quiesced, and
the marker indicates that the multi-tiered application has been quiesced, and
transmitting the stream of data that is being replicated, which comprises the marker, from a primary site to a secondary site;
generate a snapshot of a first storage element used by the multi-tiered application, wherein
generating the snapshot is performed in response to detecting the marker in the stream of data that is being replicated, and
the snapshot is application-consistent with regard to at least two tiers of the multi-tier application;
configure a second storage element;
start an instance of the multi-tiered application using the snapshot and the second storage element; and
perform the disaster recovery rehearsal, wherein
the disaster recovery rehearsal is an application-consistent disaster recovery rehearsal,
performing comprises using the marker without querying any log files to determine where the multi-tiered application was quiesced, and
generating the snapshot, configuring the second storage element, starting the instance, and performing the disaster recovery rehearsal are performed in response to initiating the DR rehearsal.
7. The non-transitory computer readable storage medium of claim 6 , wherein
the first storage element and the second storage element are located in a cloud computing environment.
8. The non-transitory computer readable storage medium of claim 6 , wherein the first storage element and the second storage element are isolated from one another.
9. The non-transitory computer readable storage medium of claim 6 , wherein the program instructions are further executable to:
determine all storage elements associated with the multi-tiered application; and
synchronize a pause of updates to the all storage elements.
10. The non-transitory computer readable storage medium of claim 6 , wherein the program instructions are further executable to:
replicate updates to the first storage element, wherein
the updates are being replicated to the first storage element concurrently with performance of the DR rehearsal.
11. A system comprising:
one or more processors; and
a memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to:
initiate a disaster recovery (DR) rehearsal for a multi-tiered application, wherein
initiating the DR rehearsal comprises
quiescing the multi-tiered application, and
in response to the quiescing, inserting a marker into a stream of data that is being replicated, wherein
the marker is inserted into the stream of data that is being replicated after the multi-tiered application has been quiesced, and
the marker indicates that the multi-tiered application has been quiesced, and
transmitting the stream of data that is being replicated, which comprises the marker, from a primary site to a secondary site;
generate a snapshot of a first storage element used by the multi-tiered application, wherein
generating the snapshot is performed in response to detecting the marker in the stream of data that is being replicated, and
the snapshot is application-consistent with regard to at least two tiers of the multi-tier application;
configure a second storage element;
start an instance of the multi-tiered application using the snapshot and the second storage element; and
perform the disaster recovery rehearsal, wherein
the disaster recovery rehearsal is an application-consistent disaster recovery rehearsal,
performing comprises using the marker without querying any log files to determine where the multi-tiered application was quiesced, and
generating the snapshot, configuring the second storage element, starting the instance, and performing the disaster recovery rehearsal are performed in response to initiating the DR rehearsal.
12. The system of claim 11 , wherein
the first storage element and the second storage element are located in a cloud computing environment.
13. The system of claim 11 , wherein
the first storage element and the second storage element are isolated from one another.
14. The system of claim 11 , wherein the program instructions are further executable to:
determine all storage elements associated with the multi-tiered application; and
synchronize a pause of updates to the all storage elements.
15. The system of claim 11 , wherein the program instructions are further executable to:
replicate updates to the first storage element, wherein
the updates are being replicated to the first storage element concurrently with performance of the DR rehearsal.