Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: In addition to caching I/O operations at a host, at least some data management can migrate to the host. With host side caching, data sharing or deduplication can be implemented with the cached writes before those writes are supplied to front end storage elements. When a host cache flush to distributed storage trigger is detected, the host deduplicates the cached writes. The host aggregates data based on the deduplication into a “change set file” (i.e., a file that includes the aggregation of unique data from the cached writes). The host supplies the change set file to the distributed storage system. The host then sends commands to the distributed storage system. Each of the commands identifies a part of the change set file to be used for a target of the cached writes.

Abstract: A storage management computing device, method and non-transitory computer readable medium that persist data on non-volatile memory includes maintaining a data storage structure comprising multiple nodes on non-volatile memory in at least one storage server. A determination is made when a received key in an update matches an existing key in one of the multiple nodes in the data storage structure. When the determination indicates the match, the update is provided for insertion in a slot in a vector extending from the existing key in the one of the multiple nodes for the data storage structure which matches the received key.

Abstract: Systems and methods efficiently distribute information, such as path name, attributes and object information, corresponding to changes in a content repository to remote nodes in a network using storage-layer/object-based protocols. A difference monitoring client monitors name space and object space changes by identifying inodes which have been modified on storage volumes between two or more snapshots. The monitoring client builds a list which may include name information, object space information and attributes such as file size and permissions for each of the changed inodes that is utilized to update the edge nodes. Systems and methods also provide for geo-scale content distribution from a central repository to edge nodes using a storage-layer/object protocol. A caching mechanism is utilized to cache requested content at an edge node. Cached content may be maintained at the edge node during use and/or for an additional predetermined period. Difference monitoring client may track such cached content.

Abstract: Systems and methods efficiently distribute information, such as path name, attributes and object information, corresponding to changes in a content repository to remote nodes in a network using storage-layer/object-based protocols. A difference monitoring client monitors name space and object space changes by identifying inodes which have been modified on storage volumes between two or more snapshots. The monitoring client builds a list which may include name information, object space information and attributes such as file size and permissions for each of the changed inodes that is utilized to update the edge nodes. Systems and methods also provide for geo-scale content distribution from a central repository to edge nodes using a storage-layer/object protocol. A caching mechanism is utilized to cache requested content at an edge node. Cached content may be maintained at the edge node during use and/or for an additional predetermined period. Difference monitoring client may track such cached content.

Abstract: Partner mirroring is provided with tray loss protection in an N node storage cluster architecture. A master proxy receives and records broadcasts of nodes in a cluster and selects mirror partners in a round robin fashion, so that even numbered nodes are mirrored with other even numbered nodes and odd numbered nodes are mirrored with other odd numbered nodes. In an N node storage cluster architecture which includes a cluster of dual controllers, tray loss protection is provided using such an odd numbered and even numbered mirror pairing process.

Abstract: Partner mirroring is provided with tray loss protection in an N node storage cluster architecture. A master proxy receives and records broadcasts of nodes in a cluster and selects mirror partners in a round robin fashion, so that even numbered nodes are mirrored with other even numbered nodes and odd numbered nodes are mirrored with other odd numbered nodes. In an N node storage cluster architecture which includes a cluster of dual controllers, tray loss protection is provided using such an odd numbered and even numbered mirror pairing process.