Systems and methods for online brand continuity

• US 10,606,717 B1
• Filed: 04/16/2018
• Issued: 03/31/2020
• Est. Priority Date: 03/11/2008
• Status: Active Grant

• Current Assignee: United Services Automobile Association
• Original Assignee: United Services Automobile Association
• Inventors: Niedzielski, David, Trost, Christopher S., Pena, Roger, Lavelle, Tommy, Clemons, Donald E.
• Primary Examiner(s): Chou, Alan S
• Application Number:
  US15/954,394
• Time in Patent Office: 715 Days
• Field of Search: 709217
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 16/58 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04W 88/12 Access point controller devices

Abstract

The present disclosure provides a system and method for online brand continuity. Online brand continuity can include a number of Internet or intranet access points via which one or more network addresses can be advertised. A client can be provided with availability of a business image application via at least one of the Internet or intranet access points.

Claims

1. A method comprising:

receiving, by a first server of a first data center from a client computer, a first request to be the first server having a first network IP address of the first data center;

storing, by the first server, new or modified data resulting from processing operations required by the first request;

synchronously replicating, by the first server, the new or modified data to a second server of the first data center having a second network IP address;

asynchronously replicating, by the first server, the new or modified application data to a third server of a failover data center having a failover network IP address, the third server having a network prefix that is equal to at least a portion of at least one of the first and second network IP address; and

responsive to the first network IP address and the second network IP address ceasing to be advertised as a destination address for one or more requests, receiving, by the third server of the failover data center from the client computer, a second request transmitted to the first network IP address or the second network IP address.

2. The method according to claim 1, wherein synchronously replicating and asynchronously replicating the new or modified data is performed, by the first server, over a first and a second autonomous network respectively.

3. The method according to claim 1, wherein synchronously replicating and asynchronously replicating the new or modified data is performed, by the first server, over a single autonomous network.

4. The method according to claim 1, further comprising advertising, by a first access point of the first data center, the first or the second network IP address as the destination address and routing the second request to the first server.

5. The method according to claim 1, further comprising advertising, by a second access point of the failover data center, the failover network IP address as the destination address and routing the second request to the second server.

6. The method according to claim 1, further comprising processing, by the third server, operations required by request.

7. The method according to claim 1, further comprising asynchronously replicating, by the first server, the new or modified application data to the failover data center over a second autonomous network at a periodic interval.

8. The method according to claim 1, further comprising transmitting, by the first server, to the client computer an indication the operation required by the second request is completed responsive to the second server storing the new or modified application data.

9. The method according to claim 1, further comprising storing, by the third server, the new or modified application data resulting from processing operations required by the second request.

10. The method according to claim 1, further comprising:

checking, by a load balancer of the first data center, an operational health status of the first server; and

ceasing, by the load balancer, advertisement of the first network IP address based on criteria determining the operational health of the first server.

11. The method according to claim 1, wherein the load balancer transfers the second request form the client computer to the third server of the failover data center.

12. A computer system comprising:

a first server within a first center, the first server having a first network IP address of the first data center;

a second server within the first data center, the second server having a second network IP address;

a third server within a failover data center, wherein the first server is configured to;

receive, of a first data center from a client computer, a first request to be the first server;

store new or modified data resulting from processing operations required by the first request;

synchronously replicate the new or modified data to a second server of the first data center;

asynchronously replicate the new or modified application data to a third server of a failover data center having a failover network IP address, the third server having a network prefix that is equal to at least a portion of at least one of the first and second network IP address; and

wherein the third server is configured to;

responsive to the first network IP address and the second network IP address ceasing to be advertised as a destination address for one or more requests, receive, from the client computer, a second request transmitted to the first network IP address or the second network IP address.

13. The computer system according to claim 12, wherein synchronously replicating and asynchronously replicating the new or modified data is performed, by the first server, over a first and a second autonomous network respectively.

14. The computer system according to claim 12, wherein synchronously replicating and asynchronously replicating the new or modified data is performed, by the first server, over a single autonomous network.

15. The computer system according to claim 12, further comprising advertising, by a first access point of the first data center, the first or the second network IP address as the destination address and routing the second request to the first server.

16. The computer system according to claim 12, wherein the first server is further configured to advertise the failover network IP address as the destination address and routing the second request to the second server.

17. The computer system according to claim 12, wherein the third server is further configured to process operations required by request.

18. The computer system according to claim 12, wherein the first server is further configured to asynchronously replicate the new or modified application data to the failover data center over a second autonomous network at a periodic interval.

19. The computer system according to claim 12, wherein the first server is further configured to transmit to the client computer an indication the operation required by the second request is completed responsive to the second server storing the new or modified application data.

20. The computer system according to claim 12, wherein the third server is further configured to store the new or modified application data resulting from processing operations required by the second request.