Systems and methods for online brand continuity

• US 9,990,259 B1
• Filed: 09/01/2014
• Issued: 06/05/2018
• Est. Priority Date: 03/11/2008
• Status: Active Grant

• Current Assignee: United Services Automobile Association
• Original Assignee: United Services Automobile Association
• Inventors: Niedzielski, David M., Trost, Christopher S., Pena, Roger, Lavelle, Tommy, Clemons, Donald E.
• Primary Examiner(s): Daftuar, Saket K
• Application Number:
  US14/474,273
• Time in Patent Office: 1,373 Days
• 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, data traffic transmitted to a destination address advertised as 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 data traffic;

replicating, by the first server, the new or modified data to a second server of a second data center over an autonomous network upon storing the new or modified data,

wherein the first server is configured to synchronously replicate the new or modified data to the second server;

asynchronously replicating, by the first server, the new or modified application data to a third server of a failover data center over a second autonomous network;

responsive to the first network address and a second network IP address of the second data center ceasing to be advertised;

receiving, by the third server of the failover data center, from the client computer the data traffic transmitted to the destination address advertised as the first network IP address or the second network IP address,

wherein a third network IP address corresponding to the failover data center comprises an IP address that is advertised to have a network prefix that is equal to at least a portion of at least one of the first and second network IP address; and

providing, by the third server, static data associated with the application to the client computer responsive to the operation required by the data traffic.

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

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

4. The method according to claim 1, further comprising advertising, by a third access point of the failover data center, a multi-host network address as the destination address and routing data the traffic to the third server.

5. The method according to claim 1, further comprising processing, by the first server, operations required by the data traffic received from the client computer.

6. 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.

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

8. The method according to claim 1, wherein application data comprises dynamic data and static data.

9. The method according to claim 8, further comprising transmitting, by the first server, application data to the client computer responsive to completing the operations required by the data traffic.

10. 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 data traffic.

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

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

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

12. The method according to claim 11, responsive to first network IP address ceasing to be advertised by the load balancer, further comprising:

logically routing, by the load balancer, the data traffic from the client computer transmitted to the first network IP address; and

physically routing, by the load balancer, the data traffic from the client computer to the second access point of the second data center.

13. An online brand continuity system comprising:

a two or more active data centers, each data center comprising an access point advertising a network IP address of the data center and receiving data traffic transmitted by a client computer based on a routing policy, and an application server providing at least a portion of the application data to the client computer in response to receiving data traffic from the access point;

a standby data center comprising a third access point advertising a multi-host network IP address and receiving data traffic transmitted by the client computer when at least one access point of the active data centers fails to satisfy criteria, and a third application server providing to the client computer at least static data of the application data, wherein the multi-host network IP address corresponding to the standby data center comprises an IP address that is advertised to have a network prefix that is equal to at least a portion of at least one of the network IP addresses corresponding to the two or more active data centers;

an autonomous network communicating data between a first data center and a second data center, wherein the first data center replicates new or modified application data over the autonomous network to the second data center and wherein the application server of the first data center and the application server of the second data center split processing over the autonomous network based on processing operations requested by the data traffic, wherein the first data center is configured to synchronously replicate the new or modified application data over the autonomous network to the second data center; and

a second autonomous network communicating data between the two or more active centers and the standby data center, wherein each of the active data centers asynchronously replicate new or modified application data over the second autonomous network to the standby data center.

14. The system according to claim 13, further comprising a load balancer balancing data traffic directed to the first data center and the second data center.

15. The system according to claim 13, further comprising a load balancer associated with the first data center performing a health check on one or more application servers in the first data center, wherein the load balancer causes the network IP address of the access point to cease to be advertised upon determining information received from a health check fails to meet the criteria.

16. The system according to claim 13, further comprising a second autonomous network communicating data between the two or more active centers and the standby data center,

wherein each of the active data centers asynchronously replicate new or modified application data over the second autonomous network to the standby data center based on a preset time period.

17. The system according to claim 13, wherein the application server of the first data center provides an indication to the client computer that the replicated application data is stored in the second data center.

18. The system according to claim 13, wherein the application data comprises dynamic data and static data, and wherein the application server of the standby data center further provides dynamic data.

19. The system according to claim 13, further comprising a router receiving data traffic from the client computer transmitted to a destination address advertised as the network IP address of at least one active data center and routing the data traffic to the access point of the least one of the active data advertising the network IP address in accordance with the routing policy.

20. The system according to claim 13, wherein the network IP address of the second data center is a multi-host address, and wherein a router logically routes the traffic to the network IP address of the first data center and physically routes the traffic to the multi-host address of the second data center.