IP Library › Granted Patent US 12,657,163
Granted Patent B2
US 12,657,163 · App. 18/941,272 · Granted Jun 16, 2026

Synchronizing data recovery files in cloud-based database management platforms

Inventors: Jason A. Custodio (Manchester, NH); Raghu Kumar Thukral (Apex, NC); Rabin Gurung (New Hill, NC)
Assignee: FMR LLC
G06F16/178G06F11/1469G06F2201/80
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,657,163
App. No.
18/941,272
Granted
Jun 16, 2026
Kind
B2
Abstract

Methods and apparatuses for synchronizing data recovery files in cloud-based database management platforms include a server that allocates physical storage media for database management platforms hosted in a cloud computing environment and attaches a source database management platform in a first region of the environment to the allocated storage media. The server attaches a target database management platform in a second region of the environment to the allocated storage media. The server establishes a periodic replication job between the source database management platform and the target database management platform, including validating change files associated with differential data changes in a primary database instance and transmitting the validated change files to the target database management platform for replication in a secondary database instance.

Claims (37)

1 . A system for synchronizing data recovery files in cloud-based database management platforms, the system comprising a server computing device having a memory for storing computer-executable instructions and a processor that executes the computer-executable instructions to:

issue requests to a cloud computing environment coupled to the server computing device to reserve resource capacity for deployment of database management platforms in the cloud computing environment, the requests including one or more criteria for the reserved resource capacity and authentication credentials associated with an organization account for a service provider of the cloud computing environment, and the cloud computing environment comprising a plurality of regions;

receive acceptance indicia for the requests to reserve resource capacity from the cloud computing environment, the acceptance indicia confirming that the cloud computing environment has sufficient resource capacity to successfully deploy the database management platforms in the cloud computing environment in association with the organization account;

allocate physical storage media for the database management platforms hosted in the cloud computing environment;

attach a source database management platform in a first region of the cloud computing environment to the allocated storage media, the source database management platform comprising a primary database instance, including creating a first partition on the allocated storage media, creating a first filesystem on the first partition, creating a first mount point in the first filesystem, mounting the allocated storage media to the first mount point, and assigning a universally unique identifier for the first mount point in the source database management platform;

attach a target database management platform in a second region of the cloud computing environment to the allocated storage media, the target database management platform comprising a secondary database instance, including creating a second partition on the allocated storage media, creating a second filesystem on the second partition, creating a second mount point in the second filesystem, mounting the allocated storage media to the second mount point, and assigning a universally unique identifier for the second mount point in the target database management platform;

establish a periodic replication job between the source database management platform and the target database management platform, including validating a plurality of change files associated with differential data changes in the primary database instance, and transmit the validated change files to the target database management platform for replication in the secondary database instance,

wherein files required for replication of the primary database instance to the secondary database instance are synchronized between the primary database instance and the secondary database instance upon completion of the periodic replication job.

2 . The system of claim 1 , wherein upon detecting that the source database management platform is unavailable, the server computing device provisions a temporary database management platform in the first region of the cloud computing environment, attaches the temporary database management platform to the allocated storage media, and creates a temporary database instance comprising the data files of the primary database instance.

3 . The system of claim 2 , wherein the server computing device cancels the periodic replication job upon detecting that the source database management platform is unavailable.

4 . The system of claim 3 , wherein the server computing device establishes a new periodic replication job between the target database management platform and the temporary database management platform, including validating a plurality of change files associated with differential data changes in the secondary database instance and transmitting the validated change files to the temporary database management platform for replication in the temporary database instance.

5 . The system of claim 1 , wherein the first region of the cloud computing environment and the second region of the cloud computing environment are the same region.

6 . The system of claim 1 , wherein the periodic replication job executes at an operating system level of the server computing device.

7 . The system of claim 1 , wherein the physical storage media comprises one or more disk drives.

8 . The system of claim 7 , wherein the source database management platform is attached to the same one or more disk drives as the target database management platform.

9 . The system of claim 1 , wherein the server computing device executes a build pipeline script to initiate the allocation of the storage media and the attaching of the database management platforms to the storage media.

10 . A computerized method of synchronizing data recovery files in cloud-based database management platforms, the method comprising:

issuing, by a server computing device, requests to a cloud computing environment coupled to the server computing device to reserve resource capacity for deployment of database management platforms in the cloud computing environment, the requests including one or more criteria for the reserved resource capacity and authentication credentials associated with an organization account for a service provider of the cloud computing environment, and the cloud computing environment comprising a plurality of regions;

receiving, by the server computing device, acceptance indicia for the requests to reserve resource capacity from the cloud computing environment, the acceptance indicia confirming that the cloud computing environment has sufficient resource capacity to successfully deploy the database management platforms in the cloud computing environment in association with the organization account;

allocating, by the server computing device, physical storage media for the database management platforms hosted in the cloud computing environment;

attaching, by the server computing device, a source database management platform in a first region of the cloud computing environment to the allocated storage media, the source database management platform comprising a primary database instance, including creating a first partition on the allocated storage media, creating a first filesystem on the first partition, creating a first mount point in the first filesystem, mounting the allocated storage media to the first mount point, and assigning a universally unique identifier for the first mount point in the source database management platform;

attaching, by the server computing device, a target database management platform in a second region of the cloud computing environment to the allocated storage media, the target database management platform comprising a secondary database instance, including creating a second partition on the allocated storage media, creating a second filesystem on the second partition, creating a second mount point in the second filesystem, mounting the allocated storage media to the second mount point, and assigning a universally unique identifier for the second mount point in the target database management platform; and

establishing, by the server computing device, a periodic replication job between the source database management platform and the target database management platform, including validating a plurality of change files associated with differential data changes in the primary database instance, and

transmitting the validated change files to the target database management platform for replication in the secondary database instance,

wherein files required for replication of the primary database instance to the secondary database instance are synchronized between the primary database instance and the secondary database instance upon completion of the periodic replication job.

11 . The method of claim 10 , upon detecting that the source database management platform is unavailable, the method further comprising:

provisioning, by the server computing device a temporary database management platform in the first region of the cloud computing environment;

attaching, by the server computing device, the temporary database management platform to the allocated storage media; and

creating, by the server computing device, a temporary database instance comprising the data files of the primary database instance.

12 . The method of claim 11 , further comprising canceling, by the server computing device, the periodic replication job upon detecting that the source database management platform is unavailable.

13 . The method of claim 12 , further comprising establishing, by the server computing device, a new periodic replication job between the target database management platform and the temporary database management platform, including validating a plurality of change files associated with differential data changes in the secondary database instance and transmitting the validated change files to the temporary database management platform for replication in the temporary database instance.

14 . The method of claim 10 , wherein validating the plurality of change files comprises calculating a checksum value for each of the plurality of change files.

15 . The method of claim 10 , wherein the first region of the cloud computing environment and the second region of the cloud computing environment are the same region.

16 . The method of claim 10 , wherein the periodic replication job executes at an operating system level of the server computing device.

17 . The method of claim 10 , wherein the physical storage media comprises one or more disk drives.

18 . The method of claim 10 , wherein the source database management platform is attached to the same one or more disk drives as the target database management platform.

19 . The method of claim 10 , further comprising executing, by the server computing device, a build pipeline script to initiate the allocation of the storage media and the attaching of the database management platforms to the storage media.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 19, 2025
From: CUSTODIO, JASON A.; THUKRAL, RAGHU KUMAR; GURUNG, RABIN
To: FMR LLC
Reel/Frame 070255/0493 →
Continuity (1)
Related Publication 20260133941A1 · May 14, 2026
References Cited (28)
US 7788225B2 · Fish et al. · 2010 [cited by applicant]
US 10374970B2 · Patil · 2019 [cited by examiner]
US 10803048B2 · Johnston · 2020 [cited by applicant]
US 10810229B2 · O'Shaugnessy · 2020 [cited by applicant]
US 10917358B1 · Herle · 2021 [cited by examiner]
US 11645261B2 · Kumar et al. · 2023 [cited by applicant]
US 12321244B1 · Rather · 2025 [cited by examiner]
US 20070136548A1 · Mane · 2007 [cited by examiner]
US 20150370827A1 · Parkison · 2015 [cited by examiner]
US 20160063050A1 · Schoen · 2016 [cited by examiner]
US 20190171650A1 · Botev et al. · 2019 [cited by applicant]
US 20210344559A1 · Kabbinale · 2021 [cited by examiner]
US 20230056217A1 · Rathi · 2023 [cited by examiner]
US 20230129469A1 · Ding · 2023 [cited by examiner]
US 20230224257A1 · Deviprasad · 2023 [cited by examiner]
US 20230229670A1 · Ranjan · 2023 [cited by applicant]
US 20230342658A1 · Tripathi · 2023 [cited by examiner]
US 20230409408A1 · Walshe · 2023 [cited by examiner]
US 20230409540A1 · Singhal · 2023 [cited by examiner]
US 20240126781A1 · Wong et al. · 2024 [cited by applicant]
US 20240126782A1 · Wong et al. · 2024 [cited by applicant]
US 20240126783A1 · Wong et al. · 2024 [cited by applicant]
US 20240302988A1 · Behera · 2024 [cited by examiner]
US 20240394245A1 · Dye · 2024 [cited by examiner]
US 20250078124A1 · Chen · 2025 [cited by examiner]
S. Holliday et al., “Deriving Value from Data for Oracle Database@Azure Workloads with OCI GoldenGate,” Oracle Database Insider, available at https://blogs.oracle.com/database/post/deriving-value-from-data-for-oracle-da… [cited by applicant]
M. Vinson, “Implement Oracle GoldenGate high availability in the AWS Cloud,” AWS Database Blog, available at https://aws.amazon.com/blogs/database/implement-oracle-goldengate-high-availability-in-the-aws-cloud/, Aug. 10… [cited by applicant]
“Replicate data between cloud databases in different regions,” Oracle Cloud Infrastructure Documentation, available at https://docs.oracle.com/en-us/iaas/goldengate/doc/replicate-data-cloud-databases-different-regions.h… [cited by applicant]