Systems and methods for restoring bus functionality
US-12181993-B1 · Dec 31, 2024 · US
US2018165185A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018165185-A1 |
| Application number | US-201615372837-A |
| Country | US |
| Kind code | A1 |
| Filing date | Dec 8, 2016 |
| Priority date | Dec 8, 2016 |
| Publication date | Jun 14, 2018 |
| Grant date | — |
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 test application running on a first platform in a first data center is configured for disaster recovery. A first request is sent to the test application, including determining that the first request is processed by a first test application instance in the first data center. A second request is sent to the test application to generate test data. A third request is sent to a second platform in a second data center to switch traffic for the test application from the first instance to a second instance running in the second data center. A fourth request is sent to the test application, including determining that the fourth request is processed by the second instance. A fifth request is sent to the test application to validate data replicated from the first data center to the second data center. A determination is made as to whether disaster recovery is successful.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method, comprising: configuring a test cloud application running on a first cloud platform in a first data center for disaster recovery; sending a first request to the test cloud application including determining that the first request is processed by a first instance of the test cloud application in the first data center; sending a second request to the test cloud application to generate data associated with the test cloud application; sending a third request to a second cloud platform in a second data center to switch application traffic for the test cloud application from the first instance to a second instance of the test cloud application running on the second cloud platform in the second data center; sending a fourth request to the test cloud application including determining that the fourth request is processed by the second instance in the second data center; sending a fifth request to the test cloud application to validate data replicated from the first data center to the second data center; and determining whether disaster recovery is successful for the test cloud application based on a response received to the fifth request. 2 . The computer-implemented method of claim 1 , wherein configuring the test cloud application for data recovery includes enabling replication of data associated with the test cloud application from the first data center to the second data center. 3 . The computer-implemented method of claim 1 , wherein the generated data includes persistent data stored by the first instance of the test application in the first data center and data stored in association with one or more cloud services running in the first cloud platform. 4 . The computer-implemented method of claim 1 , wherein the response received to the fifth request includes information indicating whether the generated data matches data retrieved by the second instance of the test application from the second data center. 5 . The computer-implemented method of claim 1 , wherein the application traffic is switched using a Domain Name Service (DNS) system. 6 . The computer-implemented method of claim 1 , wherein the test cloud application is associated with a disaster recovery service. 7 . The computer-implemented method of claim 1 , wherein the configuring, the sending of the first, second, third, fourth, and fifth requests, and the determining whether disaster recovery is successful are automatically performed on a periodic basis. 8 . A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising: configuring a test cloud application running on a first cloud platform in a first data center for disaster recovery; sending a first request to the test cloud application including determining that the first request is processed by a first instance of the test cloud application in the first data center; sending a second request to the test cloud application to generate data associated with the test cloud application; sending a third request to a second cloud platform in a second data center to switch application traffic for the test cloud application from the first instance to a second instance of the test cloud application running on the second cloud platform in the second data center; sending a fourth request to the test cloud application including determining that the fourth request is processed by the second instance in the second data center; sending a fifth request to the test cloud application to validate data replicated from the first data center to the second data center; and determining whether disaster recovery is successful for the test cloud application based on a response received to the fifth request. 9 . The computer-readable medium of claim 8 , wherein configuring the test cloud application for data recovery includes enabling replication of data associated with the test cloud application from the first data center to the second data center. 10 . The computer-readable medium of claim 8 , wherein the generated data includes persistent data stored by the first instance of the test application in the first data center and data stored in association with one or more cloud services running in the first cloud platform. 11 . The computer-readable medium of claim 8 , wherein the response received to the fifth request includes information indicating whether the generated data matches data retrieved by the second instance of the test application from the second data center. 12 . The computer-readable medium of claim 8 , wherein the application traffic is switched using a Domain Name Service (DNS) system. 13 . The computer-readable medium of claim 8 , wherein the test cloud application is associated with a disaster recovery service. 14 . The computer-readable medium of claim 8 , wherein the configuring, the sending of the first, second, third, fourth, and fifth requests, and the determining whether disaster recovery is successful are automatically performed on a periodic basis. 15 . A computer-implemented system, comprising: a computer memory; and a hardware processor interoperably coupled with the computer memory and configured to perform operations comprising: configuring a test cloud application running on a first cloud platform in a first data center for disaster recovery; sending a first request to the test cloud application including determining that the first request is processed by a first instance of the test cloud application in the first data center; sending a second request to the test cloud application to generate data associated with the test cloud application; sending a third request to a second cloud platform in a second data center to switch application traffic for the test cloud application from the first instance to a second instance of the test cloud application running on the second cloud platform in the second data center; sending a fourth request to the test cloud application including determining that the fourth request is processed by the second instance in the second data center; sending a fifth request to the test cloud application to validate data replicated from the first data center to the second data center; and determining whether disaster recovery is successful for the test cloud application based on a response received to the fifth request. 16 . The computer-implemented system of claim 15 , wherein configuring the test cloud application for data recovery includes enabling replication of data associated with the test cloud application from the first data center to the second data center. 17 . The computer-implemented system of claim 15 , wherein the generated data includes persistent data stored by the first instance of the test application in the first data center and data stored in association with one or more cloud services running in the first cloud platform. 18 . The computer-implemented system of claim 15 , wherein the response received to the fifth request includes information indicating whether the generated data matches data retrieved by the second instance of the test application from the second data center. 19 . The computer-implemented system of claim 15 , wherein the application traffic is switched using a Domain Name Service (DNS) system. 20 . The computer-implemented system of claim 15 , wherein the test cloud application is associated with a disaster recovery service.
Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title
for test design, e.g. generating new test cases · CPC title
for test results analysis · CPC title
for test execution, e.g. scheduling of test suites · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.