Granted Patent B2

US 12,524,285 · App. 18/603,636 · Granted Jan 13, 2026

Inventors: Ankit Kothari (Plano, TX); Ann Hawkins (Midlothian, VA); John Samos (Glen Allen, VA)

Assignee: Capital One Services, LLC

G06F11/008G06F11/2023G06F11/2048G06F11/2092G06F11/2094G06F11/321H04L43/026

Abstract

Claims (59)

1 . A computer-implemented method for testing failover, comprising:

determining a risk score associated with performing failover of an application from operation in a first region of a cloud environment to a second region of the cloud environment by evaluating risk factor data for the application with a risk scoring model;

in response to determining that the determined risk score is lower than a predetermined risk score, performing failover of the application to the second region of the cloud environment;

isolating the second region of the cloud environment from the first region of the cloud environment for a predetermined period of time; and

monitoring operation of the application in the second region of the cloud environment during the predetermined period of time.

2 . The computer-implemented method of claim 1 , further comprising:

detecting, based on the monitoring of the operation of the application in the second region of the cloud environment, one or more of an error, an issue, or an incident with the operation of the application; and

determining, based on the detecting, whether to perform one or more of a halt or pause action.

3 . The computer-implemented method of claim 2 , wherein the determining includes comparing the one or more detected error, issue, or incident with a predetermined threshold.

4 . The computer-implemented method of claim 2 , wherein the determining includes applying a weighting to the one or more detected error, issue, or incident, the weighting based on one or more of an associated severity, impact, or magnitude.

5 . The computer-implemented method of claim 2 , wherein the one or more halt or pause action includes causing a user interface to display a recommendation to one or more of pause or stop the failover.

6 . The computer-implemented method of claim 2 , wherein the one or more halt or pause action includes automatically pausing or stopping the failover.

7 . The computer-implemented method of claim 6 , further comprising:

receiving, via a Graphical User Interface (GUI) of a system, an override command; and

in response to receiving the override command, cancelling the one or more halt or pause action and resuming the failover.

8 . The computer-implemented method of claim 7 , wherein the GUI is configured to only permit receipt of the override command from an authorized user.

9 . The computer-implemented method of claim 2 , further comprising:

storing information associated with the one or more detected error, issue, or incident;

generating a report based on the stored information associated with the one or more detected error, issue, or incident; and

causing a Graphical User Interface (GUI) of a system to display at least a portion of the report.

10 . The computer-implemented method of claim 9 , wherein the portion of the report is displayed by the GUI after the failover is complete.

11 . The computer-implemented method of claim 9 , wherein the portion of the report is displayed and updated during performance of the failover.

12 . The computer-implemented method of claim 2 , further comprising:

determining an impact of the one or more detected error, issue, or incident, wherein the determining of whether to perform the one or more halt or pause action is based on the impact.

13 . A computer-implemented method for testing failover, comprising:

determining a risk score associated with performing failover of an application from operation in a first region of a cloud environment to a second region of the cloud environment by evaluating risk factor data for the application with a risk scoring model;

in response to determining that the determined risk score is lower than a predetermined risk score, performing failover of the application to the second region of the cloud environment;

displaying, via a user interface, information indicating progress of the failover of the application to the second region of the cloud environment;

isolating the second region of the cloud environment from the first region of the cloud environment for a predetermined period of time; and

monitoring operation of the application in the second region of the cloud environment during the predetermined period of time, wherein the monitoring of the operation includes determining whether the application is dependent on resources provided by regions of the cloud environment other than the second region of the cloud environment.

14 . The computer-implemented method of claim 13 , further comprising:

detecting, based on the monitoring of the operation of the application in the second region of the cloud environment, one or more of an error, an issue, or an incident with the operation of the application;

determining, based on the detecting, whether the one or more of the error, the issue or the incident is a critical condition; and

upon determining that the one or more of the error, the issue or the incident is a critical condition, executing a failback of the application to the first region of the cloud environment.

15 . The computer-implemented method of claim 13 , further comprising:

detecting, based on the monitoring of the operation of the application in the second region of the cloud environment, one or more of an error, an issue, or an incident with the operation of the application; and

determining, based on the detecting, whether to perform one or more of a halt or pause action, wherein the determining includes comparing the one or more detected error, issue, or incident with a predetermined threshold.

16 . The computer-implemented method of claim 15 , wherein the determining includes applying a weighting to the one or more detected error, issue, or incident, the weighting based on one or more of an associated severity, impact, or magnitude.

17 . The computer-implemented method of claim 15 , wherein the one or more halt or pause action includes causing the user interface to display a recommendation to one or more of pause or stop the failover.

18 . The computer-implemented method of claim 15 , wherein:

the one or more halt or pause action includes automatically pausing or stopping the failover; and

the computer-implement method further comprises:

receiving via a Graphical User Interface (GUI) of a system, an override command; and

in response to receiving the override command, cancelling the one or more halt or pause action and resuming the failover.

19 . The computer-implemented method of claim 15 , further comprising:

storing information associated with the one or more detected error, issue, or incident;

generating a report based on the stored information associated with the one or more detected error, issue, or incident; and

causing a Graphical User Interface (GUI) of a system to display at least a portion of the report.

20 . A system for testing failover, comprising:

a cloud environment, including a first region and a second region;

an application configured to operate in the first region;

at least one memory storing instructions and a risk scoring model;

a user interface; and

at least one processor operatively connected to the at least one memory, to the cloud environment, and to the user interface, and configured to execute the instructions to perform operations, including:

determining a risk score associated with performing failover of the application from operation in the first region of the cloud environment to the second region of the cloud environment by evaluating risk factor data for the application with the risk scoring model;

in response to determining that the determined risk score is lower than a predetermined risk score, performing failover of the application to the second region of the cloud environment;

displaying, via the user interface, information indicating progress of the failover of the application to the second region of the cloud environment;

isolating the second region of the cloud environment from the first region of the cloud environment for a predetermined period of time; and

monitoring operation of the application in the second region of the cloud environment during the predetermined period of time, wherein the monitoring of the operation includes determining whether the application is dependent on resources provided by regions of the cloud environment other than the second region of the cloud environment.

Assignments (1)

Continuity (3)

References Cited (15)