Inmage Systems, Inc.

Sun Microsystems, Inc.

Avago Technologies International Sales Pte. Limited

Sun Mirosystems, Inc.

Anup S Tirumala

Rajeev Atluri

Marc R Tremblay

Sam Inala

Andre Kowalczyk

Haitao Xia

Mohammad Shafiul Mobin

Srinivasarao Neelamraju

Srihari Kumar

Yuefei Ge

David M Pini

Embodiments are related to systems and methods for data transfer, and more particularly to systems and methods for providing non-standard bus information.

Systems and methods for channel information exchange in a PCIe environment

Methods and systems of causation of a data read operation against a first storage system by a server associated with a second storage system according to a host generated instruction are disclosed. In an embodiment, a method of causing a data read operation against a first storage system, the data read operation performed by a server associated with a second storage system according to a machine-readable instruction generated by a host directly associated with the first storage system. The method further includes saving data from the host to the first storage system, creating a record of at least one data write comprising the data saved to the first storage system, and using a variable contained in the record to process a mapping scheme resulting in knowledge of at least one physical offset in the first storage system to receive the at least one data write.

Causation of a data read operation against a first storage system by a server associated with a second storage system according to a host generated instruction

Systems and methods of event driven recovery management are disclosed. In one embodiment, a method of providing event driven recovery management includes continually copying one or more data blocks that are generated from a computing device, associating at least one event marker with the copies of the one or more data blocks, and allowing access to the copies of the one or more data blocks according to the at least one event marker in order to provide event driven recovery. For purposes of this disclosure, an event marker, a book mark, an application consistency point, and/or a business event are interchangeably used, depending on the context.

Systems and methods of event driven recovery management

Machine readable instructions, methods, and systems of causation of a data read against a first storage system to optionally store a data write to preserve the version to allow viewing and recovery are disclosed. In an embodiment, a system for providing secondary data storage and recovery services for one or more networked host nodes includes a server application for facilitating data backup and recovery services; a first data storage medium accessible to the server application; a second data storage medium accessible to the server application; and at least one client application for mapping write locations allocated by the first data storage medium to write locations represented in a logical view of the first data storage medium.

Causation of a data read against a first storage system to optionally store a data write to preserve the version to allow viewing and recovery

A method and systems of a time ordered view of backup data on behalf of a host are disclosed. In an embodiment, a method to provide a time-ordered snapshot view on behalf of a host of a specified portion of a backup of a first storage system data container stored at a second storage system includes initiating an order at the host to obtain a view of a data container. The order specifies a date and time of the ordered view. The method further includes receiving the order at a server adapted to assemble and enable access to the ordered view, and at the server, accessing the second storage system according to the date and time of the ordered view and accessing an applicable data write representing a data change to the data container.

Time ordered view of backup data on behalf of a host

Methods and a system to acquire and perform write validation of data generated by one or more networked host nodes to perform secondary storage are disclosed. According to one embodiment, a method to passively acquire and perform write validation of data generated by one or more networked host nodes to perform secondary storage in a SAN-based data storage and recovery network includes generating data to store in primary storage. The method further includes generating metadata describing the data generated to store in primary storage, sending the data and metadata to a primary SAN storage device, acquiring passive access to data traveling a data path between a generating node and the primary SAN storage device, the data mirrored over an access line to a secondary storage server. The method further includes receiving, at the secondary storage server, an exact copy of a data stream that passes a splitter.

Acquisition and write validation of data of a networked host node to perform secondary storage

A software suite, a method and a system of configuring hosts of a secondary data storage and recovery system are disclosed. In an embodiment, a system includes hosts saving data in primary storage devices, a software suite to provide secondary storage and a recovery service to one or more networked node includes a portion to configure at least one network node to perform a service, a portion to order a service and to generate metadata about data generated to store in secondary storage using a processor and a non-volatile memory, and a portion to perform data write validation and a portion to receive and prepare data to store in secondary storage. The portion to perform service configuration, the portion to perform ordering, and the portion to perform metadata generation are part of a client instance may be provided one instance per to the one or more networked node.

Configuring hosts of a secondary data storage and recovery system

A system for providing secondary data storage and recovery services for one or more networked host nodes has a server application for facilitating data backup and recovery services; at least one client application for facilitating host node configuration to receive services; a secondary data storage medium; and at least one mechanism for passive acquisition of data from the one or more host nodes for storage into the secondary data storage medium by the server application. In a preferred embodiment secondary storage is streamlined through continuous data backup and enhanced by elimination of redundant write data.

Secondary data storage and recovery system

A method for reducing signed load latency in a microprocessor has been developed. The method includes transferring a part of data to an aligner via a bypass, and generating a sign bit from the part of the data. The sign bit is transferred to the aligner along the bypass, and the data is separately transferred to the aligner along a data path.

Sign generation bypass path to aligner for reducing signed data load latency

A shared write back buffer for storing data from a data cache to be written back to memory. The shared write back buffer includes a plurality of ports, each port being associated with one of a plurality of processing units. All processing units in the plurality share the write back buffer. The shared write back buffer further includes a data register for storing data provided through the input ports, an address register for storing addresses associated with the data provided through the input ports, and a single output port for providing the data to the associated addresses in memory.

Shared write buffer for use by multiple processor units

A method for selecting a candidate to mark as overwritable in the event of a cache miss while attempting to avoid a write back operation. The method includes associating a set of data with the cache access request, each datum of the set is associated with a way, then choosing an invalid way among the set. Where no invalid ways exist among the set, the next step is determining a way that is not most recently used among the set. Next, the method determines whether a shared resource is crowded. When the shared resource is not crowded, the not most recently used way is chosen as the candidate. Where the shared resource is crowded, the next step is to determine whether the not most recently used way differs from an associated source in the memory and where the not most recently used way is the same as an associated source in the memory, the not most recently used way is chosen as the candidate. Where the not most recently used way differs from an associated source in the memory, the candidate is chosen as the way among the set that does not differ from an associated source in the memory. Where all ways among the set differ from respective sources in the memory, the not most recently used way is chosen as the candidate and the not most recently used way is stored in the shared resource.

Growing community of inventors

San Jose, CA, United States of America

Anup S Tirumala