Browse Prior Art Database

FAILOVER-AWARE SYSTEM, METHOD AND APPARATUS FOR FAILOVER OF ELECTRONIC MESSAGES DELIVERY ON PER-DATABASE BASIS AND USER ACCESS TO THOSE MESSAGES.

IP.com Disclosure Number: IPCOM000239385D
Publication Date: 2014-Nov-04
Document File: 2 page(s) / 105K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and apparatus for failover of electronic message delivery on per-database basis and user access to those messages is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

FAILOVER- -AWARE SYSTEM

AWARE SYSTEM , METHOD AND APPARATUS FOR FAILOVER OF ELECTRONIC MESSAGES DELIVERY ON PER - -DATABASE

DATABASE

BASIS AND USER ACCESS TO THOSE MESSAGES .

Disclosed is a method to solve the problem of failover of email delivery per-database basis in a cluster environment and enables user to access and read the email on the secondary system. Even though messaging servers could be clustered at server and user database level, user database still is a single point of failure and messages will be in failed state if there is corruption at the database level on the primary server until the corruption is removed. The disclosed method implements an approach to deliver message to user's database on the secondary server without any down time for the user.

Some definitions:
System
: The sum of all nodes that comprises the server product, i.e.: Server product cluster, DNS server(s), Network File System (NFS) server(s), authentication server(s), edge server(s), Hypertext Transfer Protocol (HTTP) server(s), etc.

Node: An individual computing object that sends and/or receives some sort of message(s) to and from other nodes in a system and performing a unit of work. This includes a running server application of any type. The servers include authorization and authentication (ie: Lightweight Directory Access Protocol (LDAP)) and network (ie: Domain Name Server (DNS)), database storage & Load Balancer.

In an example embodiment, depicted in Figure 1 describes the disclosed idea for the failover of email delivery on per-database basis in a cluster environment and Figure 2 describes how user is enabled to access the email on the secondary mail system.

Current methodology:

User B's mail database (as depicted in Figure 1) is on Mail Server A & Mail Server B where Mail Server A & Mail Server B are clustered at the


1.

application level.

User B's mail database on Mail Server A goes bad (corrupted/non-readable). Mail Server A is active and receiving messages for all other users


2.

on Mail Server A.

User B's won't be able to receive messages until corruption is fixed for that user on Mail Server A. Even though Mail Server B is healthy and


3.

user data store is in functional state mail won't be delivered to Mail Server B's data store until Mail Server A is not available for all users.

Until database corruption is fixed, "user B" won't be able to receive/send mail on Mail Server A. This leaves "user B" totally in an non-functional


4.

state until corruption is fixed.

Implementation of the disclosed idea in the server product code to solve the failover of email delivery per database basis as follows:

Router program knows about user B's database on Mail Server A & Mail Server B. Database Cache has user details from Mail Server A & Mail Server B.

Once router program finds out that user database is no longer usable (or n...