Infrastructure driven auto-scaling of workloads
US-2024419470-A1 · Dec 19, 2024 · US
US10084858B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10084858-B2 |
| Application number | US-201715821148-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 22, 2017 |
| Priority date | Oct 22, 2013 |
| Publication date | Sep 25, 2018 |
| Grant date | Sep 25, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system for providing reliable availability of a general workload and continuous availability of a priority workload over long distances may include a first computing site configured to execute a first instance associated with the priority workload, wherein the first instance is designated as an active instance, a second computing site configured to execute a second instance of the priority workload, wherein the second instance is designated as a standby instance, a third computing site configured to restart a third instance associated with the general workload, and a workload availability module configured to synchronize a portion of data associated with the third instance with a corresponding portion of data associated with the second instance.
Opening claim text (preview).
What is claimed is: 1. A method for providing restore operations, the method comprising: when a primary computing site becomes unavailable, switching to a secondary computing site by designating standby instances of primary and general workloads executing at the secondary computing site to active instances of the primary and general workloads; when the primary computing site becomes unavailable, executing primary and general workloads at a third computing site as standby instances using dormant instances copied to a mirrored storage volume at the third computing site before the primary computing site became unavailable; monitoring for an input comprising a restore command that restores an original operative configuration upon the primary computing site being once again available; upon receipt of the restore command: halting execution of the primary and general workloads at a third computing site; restarting, at the primary computing site, the primary and general workloads that were executing at the third computing site using corresponding dormant instances copied to a mirrored storage volume at the primary computing site from the third computing site; during the restart, synchronizing data related to priority and general workloads at the primary computing site with current active workload data from the secondary computing site to resolve any data inconsistencies resulting from the data related to the priority and general workloads at the primary computing site having become obsolete due to updates performed at the secondary computing site while the primary computing site was unavailable; switching to active the priority and general workloads that were restarted at the primary computing site to return execution to the primary computing site; and replicating the data related to the priority and general workloads maintained in a hardware storage unit at the primary computing site to a hardware storage unit at the third computing site, wherein, during the restart, the synchronizing of the data related to priority and general workloads at the primary computing site with current active workload data from the secondary computing site is performed within a period of time required by the restart of the primary and general workloads at the primary computing site to reduce an exposure time of the primary computing site being unavailable.
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
Physics · mapped topic
by checking availability · CPC title
Physics · mapped topic
Techniques for rebalancing the load in a distributed system · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.