US 11,924,354 B2
Data center recovery pod systems and methods
Nick Rosenberg, Flower Mound, TX (US); Jonathan Elvers, St. Albans (GB); Antonio G. Jarufe, Holmdel, NJ (US); and Scott D. Valentine, Carneys Point, NJ (US)
Assigned to JPMORGAN CHASE BANK, N.A., New York, NY (US)
Filed by JPMORGAN CHASE BANK, N.A., New York, NY (US)
Filed on Mar. 19, 2021, as Appl. No. 17/206,576.
Prior Publication US 2022/0303142 A1, Sep. 22, 2022
Int. Cl. H04L 9/32 (2006.01); G06F 11/14 (2006.01); G06F 16/23 (2019.01); G06F 16/27 (2019.01)
CPC H04L 9/3247 (2013.01) [G06F 11/1469 (2013.01); G06F 16/2365 (2019.01); G06F 16/278 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method for ingesting data artifacts into a multi-zone recovery pod, comprising:
identifying, by a first controller for a first data zone in the multi-zone recovery pod, a data artifact for ingestion into a first data zone datastore;
pulling, by the first controller, the identified data artifacts into the first data zone datastore;
confirming, by a second controller for a second data zone in the multi-zone recovery pod, that a first airlock between the first data zone and the second data zone is closed, and that a second airlock between a third data zone of the multi-zone recovery pod and the second data zone is closed;
opening, by the second controller, the first airlock thereby allowing data to be communicated between the first data zone and the second data zone;
identifying, by the second controller, the data artifacts in the first data zone datastore;
pulling, by the second controller, the identified data artifacts in the first data zone datastore into a second data zone datastore through the first airlock;
closing, by the second controller, the first airlock thereby preventing data from being communicated between the first data zone and the second data zone and confirming that the first airlock and the second airlock are closed;
opening, by the second controller, the second airlock thereby allowing data to be communicated between the second data zone and the third data zone;
identifying, by a third controller for the third data zone, the data artifacts in the second data zone datastore;
pulling, by the third controller, the identified data artifacts in the second data zone datastore into a third data zone datastore through the second airlock; and
closing, by the second controller, the second airlock thereby preventing data from being communicated between the second data zone and the third data zone;
wherein the first data zone is a least secure data zone in the multi-zone recovery pod, and the third data zone is a most secure data zone in the multi-zone recovery pod.