Patent application number | Description | Published |
20130191465 | FACILITATING MESSAGE SERVICES USING MULTI-ROLE SYSTEMS - Systems, methods, and software are provided for facilitating a message service. A multi-role system is identified based on where an active message database associated with a user identity resides. Service communications generated by a messaging client associated with the user identity are directed from an entry system to the multi-role system for handling in the multi-role system by a messaging server and a content server to provide the message service. | 07-25-2013 |
20130340075 | ENHANCED DATA PROTECTION FOR MESSAGE VOLUMES - In a message replication environment, instances of a message volume are hosted by message systems. Each message system exchanges condition information with the other message systems indicative of the health of the volume instance hosted by the message system. Each message system then determines independently from the other message systems whether or not the message volume is sufficiently protected. In the event that the message volume is insufficiently protected, a protection action can be initiated. | 12-19-2013 |
20130346512 | ENHANCED AVAILABILITY FOR MESSAGE SERVICES - An enhanced availability environment for facilitating a message service provided by a plurality of service elements is disclosed herein. The enhanced availability environment comprises a monitoring element and an enhanced availability element. The monitoring element monitors a first service element of the plurality of service elements for a monitored characteristic, generates monitoring information corresponding to the monitored characteristic, and communicates the monitoring information to the enhanced availability element. The enhanced availability element determines an availability of the first service element for the message service based at least in part on the monitoring information and an availability characteristic of the first service element, and communicates the availability to initiate an availability action. | 12-26-2013 |
20130346786 | DYNAMIC ESCALATION OF SERVICE CONDITIONS - Systems, methods, and software are provided for dynamically escalating service conditions associated with data center failures. In one implementation, a monitoring system detects a service condition. The service condition may be indicative of a failure of at least one service element within a data center monitored by the monitoring system. The monitoring system determines whether or not the service condition qualifies for escalation based at least in part on an access condition associated with the data center. The access condition may be identified by at least another monitoring system that is located in a geographic region distinct from that of the first monitoring system. Upon determining that the service condition qualifies for escalation, the monitoring system escalates the service condition to an escalated condition and initiates an escalated response. | 12-26-2013 |
Patent application number | Description | Published |
20090276657 | MANAGING CLUSTER SPLIT-BRAIN IN DATACENTER SERVICE SITE FAILOVER - A central controlling service for datacenter activation/deactivation control in a cluster deployment to assist in preventing a split-brain scenario. The central controlling service provides a central point of control in the datacenter for application servers to periodically query as to whether to go offline, online, or normal. Redundancy of the central service facilitates detection of datacenter failure by the redundant services interacting to resolve the state of control information. This control information is then used to answer the server queries. On startup from a datacenter failure, a single instance of the central service queries other redundant instance(s) to determine if the single instance is starting up from a datacenter-wide failure or from operations other than total datacenter failure. If the failure is datacenter-wide, a central service protocol assists in resolving to the single service keeping the associated datacenter servers offline; otherwise, the server queries are answered to go online. | 11-05-2009 |
20090319525 | LOST WRITE PROTECTION VIA STREAM-BASED REPLICATION - Architecture for detecting lost writes using timestamps. During a replication process, lost writes in data replicated from a stream can be detected by noting discrepancies between the timestamps of data in the replica and timestamps associated with the corresponding data from the source in original data store. A lost write either in the original data store or in the replica data store can be inferred by comparing these timestamps with the timestamps in a number of other replica data stores. Additionally, check entries can be added to the replicas by the original data store to allow expanded comparison between recently modified data and the source data in the original data store. The check entries can be added to the replication journal after a time delay, thereby increasing effectiveness of the check by decreasing the likelihood that caching in the hardware will defeat the test. | 12-24-2009 |
20090327519 | ADDING INDIVIDUAL DATABASE FAILOVER/SWITCHOVER TO AN EXISTING STORAGE COMPONENT WITH LIMITED IMPACT - High availability architecture that employs a mid-tier proxy server to route client communications to active data store instances in response to failover and switchover. The proxy server includes an active manager client that interfaces to an active manager in each of the backend servers. State information and configuration information are maintained separately and according to semantics consistent with needs of corresponding data, the configuration information changing less frequently and more available, the state information changing more frequently and less available. The active manager indicates to the proxy server which of the data storage instances is the currently the active instance. In the event that the currently active instance is inactive, the proxy server selects a different backend server that currently hosts the active data store instance. Client communications are then routed to the different backend server with minimal or no interruption to the client. | 12-31-2009 |
20090327805 | MINIMIZING DATA LOSS IN ASYNCHRONOUS REPLICATION SOLUTION USING DISTRIBUTED REDUNDANCY - Architecture that reduces data loss resulting from failover in an asynchronous log shipping deployment, but leveraging mid-tier and frontend servers to fill in lost data. In an asynchronous log shipping operation, a replication component asynchronously replicates messaging data to a backend server in accordance with one or more replication operations, which can be updates to databases on the backend server. These databases can include messaging data, such as email address books, mailboxes, etc. A history component maintains a history of replication operations on a frontend server. In the event of a lossy failover, a replay component is used for replaying the replication operations from the history to the backend server. | 12-31-2009 |
20120331336 | ADDING INDIVIDUAL DATABASE FAILOVER/SWITCHOVER TO AN EXISTING STORAGE COMPONENT WITH LIMITED IMPACT - High availability architecture that employs a mid-tier proxy server to route client communications to active data store instances in response to failover and switchover. The proxy server includes an active manager client that interfaces to an active manager in each of the backend servers. State information and configuration information are maintained separately and according to semantics consistent with needs of corresponding data, the configuration information changing less frequently and more available, the state information changing more frequently and less available. The active manager indicates to the proxy server which of the data storage instances is the currently the active instance. In the event that the currently active instance is inactive, the proxy server selects a different backend server that currently hosts the active data store instance. Client communications are then routed to the different backend server with minimal or no interruption to the client. | 12-27-2012 |
20130198141 | TECHNIQUES FOR LEVERAGING REPLICATION TO PROVIDE ROLLING POINT IN TIME BACKUP WITH SIMPLIFIED RESTORATION THROUGH DISTRIBUTED TRANSACTIONAL RE-CREATION - Techniques to leverage replication to provide rolling point in time backup are described. Some embodiments are directed to techniques to provide rolling point in time backup with simplified restoration through distributed transactional re-creation. In one embodiment, for example, a technique may comprise creating a plurality of availability copies of a primary set of data; designating at least one of the plurality of availability copies as a backup copy; creating a log file that indicates changes to the primary set of data; updating the plurality of availability copies from the log file in near real time, without updating the backup copy; and restoring at least one of: the primary set of data and an availability copy using the backup copy and content resubmitted from a content contributor when an error occurs in at least one of: the primary set of data and an availability copy. Other embodiments are described and claimed. | 08-01-2013 |
20130268495 | SPLIT BRAIN PROTECTION IN COMPUTER CLUSTERS - A computer cluster can be divided into a plurality of failure scopes and a voting constraint can be enforced. The voting constraint can allow a portion of the cluster to provide the service if a majority of health votes from cluster members is obtained by that portion. A loss of connectivity between a first failure scope, which has a majority of cluster members in the cluster, and one or more other failure scopes in the cluster can be detected. The loss of connectivity can be such that the first failure scope does not have connectivity to a member in any other failure scope in the cluster. In response to detecting the loss of connectivity, a split brain situation in the cluster can be automatically protected against by preventing the first failure scope from providing the service. | 10-10-2013 |
20130332770 | ACTIVE/PASSIVE DATABASE MANAGEMENT ACROSS CLUSTERS - A primary active manager can manage a first copy of a database in a first computer system cluster according to a set of management rules that provide for an active copy and one or more passive copies of the database at a given time. The primary active manager can also manage a second copy of the database in a second computer system cluster according to the rules. The rules can allow the first copy of the database or the second copy of the database to be the active copy if one or more criterion in the rules is met for that active copy. The first copy can be designated as the active copy and the second copy can be designated as a passive copy. A failure of the first copy can be detected, and in response, the second copy can be automatically designated as the active copy. | 12-12-2013 |