Google Inc.

Stefan Valentin Gheorghita

Yonatan Zunger

Frank Dachille

Rebekah C Vickrey

Magdalena Natalia Dukielska

Johan Marinius Andersen

Raymond Blum

Josephus Cornelius Willibrordus Visser

Tulika Agrawal

Marcin Michalski

Computer-implemented systems and methods are provided for indexing and serving calendar event information. In accordance with some embodiments, information common to, and unique among, instances of a recurrent event may be determined. A markup document and search document including the common information and unique information may be generated, and a search index may be updated. Also, in accordance with some embodiments, a search query may be received and parsed, and recurrent event information can be scored as a possible search result.

Serving recurrent calendar events

A method for asynchronously replicating data onto a tape medium is implemented at one or more server computers associated with a distributed storage system and connected to a tape storage system. Upon receiving a first request from a client for storing an object within the tape storage system, a server computer stores the object within a staging sub-system of the distributed storage system and provides a first response to the requesting client. If a predefined condition is met, the server computer transfers objects from the staging sub-system to the tape storage system. For each transferred object, the server computer adds a reference to the object to a tape management sub-system, identifies a corresponding parent object associated with the object and its metadata within a parent object management sub-system of the distributed storage system, and updates the parent object's metadata to include the object's location within the tape storage system.

Method and system for providing efficient access to a tape storage system

Systems and methods are disclosed herein for performing a failover operation between a first distributed database cluster and a second distributed database cluster. In one aspect, the method includes blocking a plurality of software processes from making any new access requests to the first distributed database cluster and completing a current access request to the first distributed database cluster that was initiated by one of the plurality of software processes before the failover operation was initiated, waiting for data to replicate from the first distributed database cluster to the second distributed database cluster, wherein replicating includes any changes to the data from the current access request, and allowing the plurality of software processes to make the new access requests to the second distributed database cluster once the replicating has completed.

Failover operation on a replicated distributed database system while maintaining access invariance

Growing community of inventors

Zurich, Switzerland

Stefan Valentin Gheorghita