US 2026/0169869 A1Published application

Database recovery and database recovery testing

AssigneeInsight Direct USA, Inc.

InventorsShana Meyers, Meghasyam Bokam, Ian Bundock, Larry N. Cotten, JR., Jason Fleck, Jason Garland, David Gilboy, Jeffrey J. Hodges, Chun-Kai Jason Hsu, Lori McFadden, Peter Thomas McLean, Abhijit Moharil

Life of this patent

Estimating the term…

patentgrep

Loading patent…

Abstract

A method of database recovery includes starting a first database server, starting a second database server, starting a third database server, and starting an application server after starting the first database server, the second database server, and the third. The first, second, and third database servers are configured to store data according to first, second, and third database management systems, respectively, and the application server is configured to run application modules of a set of application modules. The method of database recovery further includes starting a search module, starting a product catalog management module, starting a web connectivity module after starting the search module, starting a graphical user interface module after starting the web connectivity module, and starting at least one business operations module.

Claims16

Dependent claims

A method of database recovery, the method comprising:

detecting a failure of at least one of a first database server, a second database server, and an application server;
in response to detecting the failure of the at least one of a first database server, a second database server, and an application server, transitioning a backup server system from an inactive state to an active state, wherein:
the backup server system comprises a backup first database server, a backup second database server, and a backup application server,
the first backup database server is configured to store data according to a first database management system,
the second backup database server is configured to store data according to a second database management system,
the backup application server is configured to run application modules of a set of application modules, and
the set of application modules comprises:
a web connectivity module configured to allow other application modules of the set of application modules to connect to the Internet;
a product catalog management module for managing a product catalog;
a search module for searching at least one of the first database server and the second database server;
a graphical user interface module configured to allow a user to interact with one or more application modules of the set of application modules;
and
at least one business operations module configured to request data from at least one of the search module, the product catalog management module, and the web connectivity module, wherein the at least one business operations module is one or more of a credit card verification module, a shipping address verification module, a reporting module, or a financial consolidation module;
after transitioning the backup server system from the inactive state to the active state:
starting the search module;
starting the product catalog management module;
starting the web connectivity module after starting the search module, wherein the web connectivity module is configured to request data from the search module;
starting the graphical user interface module, wherein the graphical user interface module is configured to request data from the web connectivity module and to request data from the search module;
starting the at least one business operations module after starting the at least one of the search module, the product catalog management module, and the web connectivity module;
validating, after starting the at least one business operations module, connections used by application modules of the set of application modules;
and
validating, after starting the at least one business operations module, functionality of application modules of the set of application modules.

19 more elements

A method of performing a database recovery test, the method comprising:

disconnecting a first backup database server from a first active database server, wherein:
the first backup database server is configured to store data according to a first database management system;
and
the first backup database server is configured to back up a first set of data from the first active database server;
disconnecting a second backup database server from a second active database server, wherein:
the second backup database server is configured to store data according to a second database management system;
and
the second backup database server is configured to back up a second set of data from the second active database server;
disconnecting a backup application server from an active application server, wherein:
the backup application server is configured to back up application modules of a set of application modules from the active application server;
and
the backup application server is configured to run the application modules of the set of application modules;
starting a name system server after disconnecting the first backup database server, the second backup database server, and the backup application server, the name server connected to the first backup database server, the second backup database server, and the backup application server;
assigning new network configurations to the first backup database server, the second backup database server, and the backup application server after disconnecting the first backup database server, the second backup database server, and the backup application server and after starting the name system server;
providing the new network configurations for the first backup database server and the second backup database server to the backup application server;
transitioning the first backup database server to an active state from an inactive state after providing the new network configurations to the backup application server, wherein the first database management system is configured to recall data when the first backup database server is active;
transitioning the second backup database server to an active state from an inactive state, wherein the second database management system is configured to recall data when the second backup database server is active;
transitioning the backup application server to an active state from an inactive state after transitioning the first backup database server to an active state and transitioning the second backup database server to an active state, wherein the backup application server is configured to recall data from at least one of the first backup database server and the second backup database server;
starting the set of application modules;
validating connections used by application modules of the set of application modules;
stopping the set of application modules after validating connections;
transitioning the backup application server to an inactive state after stopping the set of application modules;
transitioning the first backup database server and the second backup database server to inactive states after transitioning the backup application server to an inactive state;
and
reconnecting, after transitioning the first backup database server and the second backup database server to inactive states:
the first backup database server to the first active database server;
the second backup database server to the second active database server;
and
the backup application server to the active application server.

26 more elements

Dependencies are inferred from the claim text.

Facts

Application: 19/531,120Filed 5 Feb 2026
Priority: 4 Mar 2022
Published: 18 Jun 2026
Term ends: Not estimatedThe source records don’t support an estimate.

Classification13 codes

G06F 11/1469
Management of the backup or restore process: backup restoration techniques
G06F 11/2028
Failover techniques: eliminating a faulty processor or activating a spare
G06F 11/1464
Management of the backup or restore process: for networked environments
G06F 11/2035
Where processing functionality is redundant: without idle spare hardware

Family

Application17/686,886Continuation · filed 4 Mar 2022
Application18/378,538Continuation · filed 10 Oct 2023
Application18/965,531Continuation · filed 2 Dec 2024
Application19/531,120Continuation
US 11,847,031 B2Related patent
US 12,189,498 B2Related patent
US 12,554,599 B1Related patent
US 2023/0281086 A1Published application
US 2024/0036991 A1Published application
US 2026/0169869 A1This patent

From the US filing history. Foreign family members aren’t listed.