Abstract: Example distributed storage systems, replication managers, and methods provide versioning validation for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A versioned write request message is sent to a second object data store and a response is received. The versioning-enabled status of the second object data store is determined from the response message and, if the versioning enabled status is invalid, any residual object versions in the second object data store are deleted based on a delete request.

Abstract: Example distributed storage systems, version control managers, and methods provide persistent version control for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A version control manager is configured to determine a creation timestamp for each of the plurality of sequential versions and store a persistent version field for each. The persistent version field remains associated with each of the plurality of sequential versions when transferred from the first object data store to a second object data store.

Abstract: Example distributed storage systems, replication managers, and methods provide versioning validation for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A versioned write request message is sent to a second object data store and a response is received. The versioning-enabled status of the second object data store is determined from the response message and, if the versioning enabled status is invalid, any residual object versions in the second object data store are deleted based on a delete request.

Abstract: Example distributed storage systems, version control managers, and methods provide persistent version control for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A version control manager is configured to determine a creation timestamp for each of the plurality of sequential versions and store a persistent version field for each. The persistent version field remains associated with each of the plurality of sequential versions when transferred from the first object data store to a second object data store.

Abstract: A method of direct access by a virtual machine (VM) running on a host machine to physical storage via a virtual function (VF) running on an input/output (IO) adapter comprising: providing by a virtualization intermediary running on the host machine an indication of an active path associated with a virtual storage device; obtaining by a guest driver running within a guest operating system of the VM the stored indication of the active path from the shared memory region; dispatching an IO request by the guest driver to the VF that includes an indication of the active path; and sending by the VF an IO request that includes the indicated active path.

Abstract: A method of direct access by a virtual machine (VM) running on a host machine to physical storage via a virtual function (VF) running on an input/output (IO) adapter comprising: providing by a virtualization intermediary running on the host machine an indication of an active path associated with a virtual storage device; obtaining by a guest driver running within a guest operating system of the VM the stored indication of the active path from the shared memory region; dispatching an IO request by the guest driver to the VF that includes an indication of the active path; and sending by the VF an IO request that includes the indicated active path.