Abstract: One or more techniques and/or computing devices are provided for cross-platform replication. For example, a replication relationship may be established between a first storage endpoint and a second storage endpoint, where at least one of the storage endpoints, such as the first storage endpoint, lacks or has incompatible functionality to perform and manage replication because the storage endpoints have different storage platforms that store data differently, use different control operations and interfaces, etc. Accordingly, replication destination workflow, replication source workflow, and/or a proxy representing the first storage endpoint may be implemented at the second storage endpoint comprising the replication functionality.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. In an embodiment, a rule is enforced for the object that in-use slots of the object are non-modifiable and unused slots of the object are modifiable. Metadata of additional information for a slot within the object is attached to the object header. A first application allowed to access user data within the slot is provided access to the user data without being provided access to the metadata. A second application allowed access to the user data and the additional information is provided with access to the user data and the metadata for identifying a location of additional information within the object.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object comprises a plurality of slots. Each slot is used to store a unit of data accessible to applications hosted by remote computing devices. The object comprises an object header used to store metadata for each slot. A determination is made that the object is a fragmented object comprising an in-use slot of in-use data and a freed slot from which data was freed. The object is compacted to retain in-use data and exclude freed data as a rewritten object.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object is used to store data of a snapshot of a file system hosted by a remote computing device. A determination is made that the snapshot was deleted by the remote computing device. Bitmaps describing objects within the object store that are related to snapshots of the file system are evaluated to determine that the object is unique to the deleted snapshot. The object is freed from storage within the object store.

Abstract: One or more techniques and/or computing devices are provided for cross-platform replication. For example, a replication relationship may be established between a first storage endpoint and a second storage endpoint, where at least one of the storage endpoints, such as the first storage endpoint, lacks or has incompatible functionality to perform and manage replication because the storage endpoints have different storage platforms that store data differently, use different control operations and interfaces, etc. Accordingly, replication destination workflow, replication source workflow, and/or a proxy representing the first storage endpoint may be implemented at the second storage endpoint comprising the replication functionality.

Abstract: To replicate a source LUN to a different storage system platform, a first storage system transmits a request to replicate a LUN along with attributes for the LUN to a second storage system. The second storage system maps the attributes to attributes used and understood by the platform of the second storage system. The second storage system then creates a destination LUN based on the mapped attributes. Since the destination LUN is created with similar attributes as the source LUN, the destination LUN can store the replicated data of the source LUN while still being accessed and recognized as a LUN by the second storage system. The second storage system also stores any proprietary attributes received from the first storage system so that the proprietary attributes can be supplied to the first storage system to recover the source LUN after a data loss event.

Abstract: One or more techniques and/or computing devices are provided for cross-platform replication. For example, a replication relationship may be established between a first storage endpoint and a second storage endpoint, where at least one of the storage endpoints, such as the first storage endpoint, lacks or has incompatible functionality to perform and manage replication because the storage endpoints have different storage platforms that store data differently, use different control operations and interfaces, etc. Accordingly, replication destination workflow, replication source workflow, and/or a proxy representing the first storage endpoint may be implemented at the second storage endpoint comprising the replication functionality.

Abstract: Techniques are provided for implementing management requests associated with objects of an object store. A data connector component may be instantiated as a container for processing management requests associated with backup data stored within an object store as an object according to an object format. A management request associated with the backup data may be received by the data connector component. A structure associated with the object having the object format may be traversed by the data connector component to identify the backup data. The data connector component may be implemented upon the backup data stored within the object.

Abstract: To replicate a source LUN to a different storage system platform, a first storage system transmits a request to replicate a LUN along with attributes for the LUN to a second storage system. The second storage system maps the attributes to attributes used and understood by the platform of the second storage system. The second storage system then creates a destination LUN based on the mapped attributes. Since the destination LUN is created with similar attributes as the source LUN, the destination LUN can store the replicated data of the source LUN while still being accessed and recognized as a LUN by the second storage system. The second storage system also stores any proprietary attributes received from the first storage system so that the proprietary attributes can be supplied to the first storage system to recover the source LUN after a data loss event.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object comprises a plurality of slots. Each slot is used to store a unit of data accessible to applications hosted by remote computing devices. The object comprises an object header used to store metadata for each slot. A determination is made that the object is a fragmented object comprising an in-use slot of in-use data and a freed slot from which data was freed. The object is compacted to retain in-use data and exclude freed data as a rewritten object.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object comprises a plurality of slots. Each slot is used to store a unit of data accessible to applications hosted by remote computing devices. The object comprises an object header used to store metadata for each slot. A determination is made that the object is a fragmented object comprising an in-use slot of in-use data and a freed slot from which data was freed. The object is compacted to retain in-use data and exclude freed data as a rewritten object.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object is used to store data of a snapshot of a file system hosted by a remote computing device. A determination is made that the snapshot was deleted by the remote computing device. Bitmaps describing objects within the object store that are related to snapshots of the file system are evaluated to determine that the object is unique to the deleted snapshot. The object is freed from storage within the object store.

Abstract: To replicate a source LUN to a different storage system platform, a first storage system transmits a request to replicate a LUN along with attributes for the LUN to a second storage system. The second storage system maps the attributes to attributes used and understood by the platform of the second storage system. The second storage system then creates a destination LUN based on the mapped attributes. Since the destination LUN is created with similar attributes as the source LUN, the destination LUN can store the replicated data of the source LUN while still being accessed and recognized as a LUN by the second storage system. The second storage system also stores any proprietary attributes received from the first storage system so that the proprietary attributes can be supplied to the first storage system to recover the source LUN after a data loss event.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object is used to store data of a snapshot of a file system hosted by a remote computing device. A determination is made that the snapshot was deleted by the remote computing device. Bitmaps describing objects within the object store that are related to snapshots of the file system are evaluated to determine that the object is unique to the deleted snapshot. The object is freed from storage within the object store.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object comprises a plurality of slots. Each slot is used to store a unit of data accessible to applications hosted by remote computing devices. The object comprises an object header used to store metadata for each slot. A determination is made that the object is a fragmented object comprising an in-use slot of in-use data and a freed slot from which data was freed. The object is compacted to retain in-use data and exclude freed data as a rewritten object.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. In an embodiment, a rule is enforced for the object that in-use slots of the object are non-modifiable and unused slots of the object are modifiable. Metadata of additional information for a slot within the object is attached to the object header. A first application allowed to access user data within the slot is provided access to the user data without being provided access to the metadata. A second application allowed access to the user data and the additional information is provided with access to the user data and the metadata for identifying a location of additional information within the object.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object is used to store data of a snapshot of a file system hosted by a remote computing device. A determination is made that the snapshot was deleted by the remote computing device. Bitmaps describing objects within the object store that are related to snapshots of the file system are evaluated to determine that the object is unique to the deleted snapshot. The object is freed from storage within the object store.

Abstract: One or more techniques and/or computing devices are provided for cross-platform replication. For example, a replication relationship may be established between a first storage endpoint and a second storage endpoint, where at least one of the storage endpoints, such as the first storage endpoint, lacks or has incompatible functionality to perform and manage replication because the storage endpoints have different storage platforms that store data differently, use different control operations and interfaces, etc. Accordingly, replication destination workflow, replication source workflow, and/or a proxy representing the first storage endpoint may be implemented at the second storage endpoint comprising the replication functionality.

Abstract: To replicate a source LUN to a different storage system platform, a first storage system transmits a request to replicate a LUN along with attributes for the LUN to a second storage system. The second storage system maps the attributes to attributes used and understood by the platform of the second storage system. The second storage system then creates a destination LUN based on the mapped attributes. Since the destination LUN is created with similar attributes as the source LUN, the destination LUN can store the replicated data of the source LUN while still being accessed and recognized as a LUN by the second storage system. The second storage system also stores any proprietary attributes received from the first storage system so that the proprietary attributes can be supplied to the first storage system to recover the source LUN after a data loss event.

Abstract: One or more techniques and/or computing devices are provided for cross-platform replication. For example, a replication relationship may be established between a first storage endpoint and a second storage endpoint, where at least one of the storage endpoints, such as the first storage endpoint, lacks or has incompatible functionality to perform and manage replication because the storage endpoints have different storage platforms that store data differently, use different control operations and interfaces, etc. Accordingly, replication destination workflow, replication source workflow, and/or a proxy representing the first storage endpoint may be implemented at the second storage endpoint comprising the replication functionality.