US 11,714,797 B2
Logically consistent archive with minimal downtime
Daniel S. Sanders, Provo, UT (US); Peeyush Paliwal, Houston, TX (US); and Polina Alber, Cambridge, MA (US)
Assigned to Micro Focus LLC, Santa Clara, CA (US)
Filed by MICRO FOCUS LLC, Santa Clara, CA (US)
Filed on Jan. 25, 2021, as Appl. No. 17/157,830.
Prior Publication US 2022/0237173 A1, Jul. 28, 2022
Int. Cl. G06F 16/23 (2019.01)
CPC G06F 16/2358 (2019.01) [G06F 16/2343 (2019.01); G06F 16/2379 (2019.01)] 17 Claims
OG exemplary drawing
 
1. A system comprising:
a microprocessor; and
a non-transitory computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by the microprocessor, cause the microprocessor to:
initiate an archive process on an operational database, wherein the archive process comprises a sub-archive and a final archive, wherein the sub-archive comprises a plurality of sub-archives, and wherein the sub-archive and the final archive run in series;
initiate the sub-archive, wherein the sub-archive saves changes in the operational database that have occurred since a previous final archive, wherein a number of sub-archives in the plurality of sub-archives is based on a number of outstanding changes in the operational database since a previous final archive, wherein a delay time between each of the plurality of sub-archives is based on the number of outstanding changes in the operational database since the previous final archive and a series of progressively smaller incremental time values, and wherein changes to the operational database are allowed during the sub-archive;
receive a request from a user to access the operational database, and in response to the request to access the operational database, create a registration record for the user, wherein when the user is done accessing the operational database or when the user's access has been terminated the registration record is deleted; and
determine if the registration record exists: if the registration record exists, then do not initiate the final archive; and
if the registration record does not exist, then initiate the final archive, wherein no changes are allowed to the operational database during the final archive.