Dynamically switching between object storage transfer protocols

In a data storage network, a data storage transfer is initiated over a communications link between a source endpoint and a storage endpoint. The data storage transfer is configured to transmit at least one data object from the source endpoint to the storage endpoint using a first transfer technology protocol of a plurality of transfer technology protocols supported by the storage endpoint. The source endpoint monitors at least one network performance parameter associated with the communication link between the source endpoint and the storage endpoint. During transfer of the at least one data object, the source endpoint automatically switches from the first transfer technology protocol to a second transfer technology protocol based, at least in part, on a result of the monitoring.

BACKGROUND

This invention relates generally to transferring data for storage, and more particularly to dynamically switching storage protocols during transfer of objects for storage.

In an object storage system in the public cloud used for “cloud storage,” transfer services, such as Aspera® and FASP® are sometimes used. Services service can be used by a client application using a software development kit (SDK) offered by the object storage vendor. However, the user has to manually decide whether to use the transfer service, or to use some other transfer service. This decision must often made blindly in advance, or after experiencing poor performance during upload or download without knowing the cause of the poor performance.

SUMMARY

According to various embodiments of the present disclosure, a method for use in a data storage network includes using a source endpoint to initiate a data storage transfer over a communications link between a source endpoint and a storage endpoint. The data storage transfer transmits, from the source endpoint to the storage endpoint, a data object, or set of data objects, for storage in the storage endpoint. The initial transfer of data objects can be performed using an initial transfer technology protocol, sometimes referred to herein as a transfer service, or a storage transfer protocol. The storage endpoint supports more than one transfer technology protocol. The source endpoint monitors network performance parameters associated with the communication link between the source endpoint and the storage endpoint, either directly or indirectly with the assistance of another device included in the data storage network. During transfer of at least one data object, the source endpoint automatically switches, based at least in part on a result of the monitoring, from the initial technology protocol to one of the other transfer technology protocols supported by the storage endpoint.

In some embodiments, the switching can be performed between individual objects in a set of objects, so that a first object is transferred using one transfer service, or storage transfer protocol, and a second object in the set of objects is transferred using a different transfer service. In other embodiments, switching to a different protocol can be performed during transfer of a single object, so that a portion of the object is transferred using a first storage transfer protocol, and a second portion of that same object is transferred using a second storage transfer protocol.

Various embodiments enable an end-user to configure various transfer parameters using a software data kit (SDK), including setting thresholds for various performance parameters, such as packet loss or round trip time. Additionally, some embodiments can be implemented as a source endpoint device, or as a non-transitory computer readable medium.

DETAILED DESCRIPTION

Various embodiments of the present disclosure provide for dynamic switching between transfer services based on real time conditions and performance with an object storage system. As used herein, the term transfer services is used interchangeably with, and should be interpreted to include the terms “transfer technology protocol,” “storage transfer protocol,” derivatives thereof, unless the context requires otherwise.

Providing an object storage system with the ability to suggest or dynamically switch between transfer technologies based on real conditions and performance of transfers can improve the performance, speed, reliability, and usability of conventional object storage systems. In some embodiments, switching can be implicit or explicit based on configuration of a software development kit (SDK) by the client application and/or a user of the client device.

An SDK or an application using an object storage system having the ability to support multiple transfer services, as described herein, can enable users to configure dynamic switching between transfer services based on one or more conditions, such as real-time network conditions, network limitations, outages, etc. Furthermore, individual functions within the transfer service can be triggered based on any or all of the following conditions monitored by the source endpoint: round trip times for requests and responses; pre-configured IP addresses of end-points for object storage for requests; pre-configured bucket names for read or write requests; pre-configured object names for read or write requests; pre-configured accounts or users for requests; pre-configured file types; and pre-configured file sizes.

Additionally, functions within the transfer service can be triggered based on any or all of the following conditions reported to the source endpoint in, for example, a response from the storage endpoint to the source endpoint: information identifying a transfer type/protocol to use for future storage transfers based on availability of a transfer service or expected outages/disruptions in network or storage service; pre-configured bucket names; pre-configured IP addresses of end points for client applications; pre-configured object names; pre-configured users; pre-configured file types; pre-configured file sizes.

For example, an SDK based application pre-configured with transfer file size of 1 GB or greater, could use an Aspera® FASP® based service for uploads, using multiple sessions for parallel uploads in Aspera®, otherwise regular hypertext transfer protocol (HTTP) based S3 transfer with single part or multi-part upload could be used.

In response to one or more conditions being met, the source endpoint can trigger a switch in the transfer service, or transfer technology protocol, being used by the SDK or application with the object storage, without explicit interaction from the user. In some embodiments, this could facilitate allowing the user or application get optimal performance and help with positive user experience based on real time conditions of the network or storage service.

Referring toFIG. 1, a schematic block diagram of an embodiment of a data storage system9will be discussed. Data storage system9includes source endpoint13and storage endpoint43, both of which can be implemented using various computing devices discussed herein, coupled together either directly (not illustrated) or via network24. Source endpoint13includes network interface15, protocol A encoder21, protocol B encoder19, protocol selector17, data object storage23, performance monitor25, and configuration variable storage27. Storage endpoint43includes network interface35, protocol A decoder37, protocol B decoder39, and storage41. Network24may include one or more wireless and/or wire lined communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

Source endpoint13can initiate a data storage transfer over communications link29, The data storage transfer transmits data objects obtained, for example, from data object storage23, from source endpoint13to storage endpoint43using a transfer technology protocol supported by storage endpoint43. Protocol selector17chooses one of the available storage protocols based, at least in part on an output of performance monitor25, and in some embodiments based on configuration variables or parameters obtained from configuration variable storage27.

In an example of operation, protocol selector17can select an initial transfer technology protocol for source endpoint to use in initiating a data storage transfer to storage endpoint43. This initial transfer technology protocol can be selected based on reply from storage endpoint43received in response to a storage request generated by source endpoint13. The initial transfer technology protocol can also be selected based on a default value stored in configuration variable storage27, a previously used transfer technology protocol, current performance parameters associated with communications link29, historical performance parameter associated with communications link29, a user preference, or the like. Some or all performance parameters, whether historical or current, can be transmitted to performance monitor25from an external computing device, and provided to protocol selector17by performance monitor25.

In at least one embodiment, the transfer of data objects from source endpoint13to storage endpoint43continues using the initial transfer technology protocol until performance monitor25notifies protocol selector17that current performance parameters exceed thresholds established by configuration variables obtained from configuration variable storage27. For example, if a performance parameter associated with communications link29indicates a packet loss, or round trip time that exceeds a threshold for that particular parameter or combination of parameters, performance monitor25can provide a notification of that condition to protocol selector17.

Protocol selector17can respond to the notification by choosing a different transfer technology protocol supported by storage endpoint43, and switching from one protocol encoder to another. For example, if the initial transfer technology protocol is Protocol A, Protocol selector17can switch from Protocol A encoder21to Protocol B encoder19. Switching from Protocol A encoder21to Protocol B encoder19can be performed during transmission of a single object, or during transmission of a set of objects, but between objects within the set of objects. Protocol selector17can determine whether a transfer technology protocol is supported by storage endpoint43based on information obtained from configuration variable storage27, based on information obtained in a message from storage endpoint43, based on preconfigured setting in an SDK or application provided to source endpoint13by storage endpoint43, based on a combination of such information, or the like.

In at least one embodiment, one of the transfer technology protocols supported by storage endpoint43is a protocol that provides guaranteed delivery time regardless of file size, transfer distance or network conditions, such as an FASP® protocol. FASP® is a large data transport protocol that achieves reliability in the application layer in an attempt to eliminate or reduce inefficient loss and error handling, along with the resulting erratic transfer rate swings that occur when using a conventional transmission control protocol (TCP). In various embodiments, at least one of the transfer technology protocols is a conventional hypertext transfer protocol (HTTP) based S3 transfer of data. It should be appreciated that in at least one embodiment, other transfer technology protocols can be used in addition to, or in place of, the specifically disclosed protocols. However, in each case both the source endpoint13and the storage endpoint43support at least two such protocols, which generally include at least one protocol that is more efficient under network conditions involving large packet losses and/or long round trip times, and another protocol that can generally be used under more favorable network conditions.

In at least one embodiment, objects being transmitted for storage include one or more dispersal error encoded data packets to be delivered to storage endpoint43for storage in storage41, but other data objects are also contemplated.

Storage endpoint43is, in at least one embodiment, an object-based storage endpoint. Object-based storage refers to a data storage architecture that manages data as objects, as opposed managing data in a file hierarchy, or block storage which manages data as blocks within sectors and tracks. Various embodiments of storage systems and devices described herein are object-based.

Storage endpoint43receives objects to be stored from source endpoint13using network interface35coupled to communications link29. Protocol Selector45determines whether to process the object using Protocol A decoder37or Protocol B decoder39based on information included in the data itself, based on information included in an storage initiation message received from source endpoint, based on information included in a change message received from source endpoint, or the like. The decoded object is sent to storage41for object storage. It should be noted that reference to a “decoded object” in this case does not mean the object is in plaintext, or that all levels of encoding and encryption have been removed. Instead, this particular reference to a “decoded object” refers to recovering the object using one of the transfer technology protocols supported by storage endpoint43. Thus, in various embodiments, a change, or switch, from one transfer technology protocol to another can occur during transfer of a single object, or between objects included in a set of objects, but the object can still be stored in storage41in the same form in which the object existed prior to being encoded by Protocol A encoder21or Protocol B encoder19.

FIG. 2is a schematic block diagram of an embodiment of a dispersed, or distributed, storage network (DSN)10that includes a plurality of computing devices12-16, a managing unit18, an integrity processing unit20, and a DSN memory22. The components of the DSN10are coupled to a network24, which may include one or more wireless and/or wire lined communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

In at least one embodiment, source endpoint13can be implemented in one or more of the computing devices12-16. Each of the computing devices12-16, the managing unit18, and the integrity processing unit20include a computing core26, which includes network interfaces30-33. Computing devices12-16may each be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment. Note that each of the managing unit18and the integrity processing unit20may be separate computing devices, may be a common computing device, and/or may be integrated into one or more of the computing devices12-16and/or into one or more of the storage units36.

Each interface30,32, and33includes software and hardware to support one or more communication links via the network24indirectly and/or directly. For example, interface30supports a communication link (e.g., wired, wireless, direct, via a LAN, via the network24, etc.) between computing devices14and16. As another example, interface32supports communication links (e.g., a wired connection, a wireless connection, a LAN connection, and/or any other type of connection to/from the network24) between computing devices12and16and the DSN memory22. As yet another example, interface33supports a communication link for each of the managing unit18and the integrity processing unit20to the network24.

As another example, the managing unit18performs network operations, network administration, and/or network maintenance, such as providing information regarding network and/or link performance to source endpoint13(FIG. 1). Network operations includes authenticating user data allocation requests (e.g., read and/or write requests), managing creation of vaults, establishing authentication credentials for user devices, adding/deleting components (e.g., user devices, storage units, and/or computing devices with a DS client module34) to/from the DSN10, and/or establishing authentication credentials for the storage units36. Network administration includes monitoring devices and/or units for failures, maintaining vault information, determining device and/or unit activation status, determining device and/or unit loading, and/or determining any other system level operation that affects the performance level of the DSN10. Network maintenance includes facilitating replacing, upgrading, repairing, and/or expanding a device and/or unit of the DSN10.

The integrity processing unit20performs rebuilding of ‘bad’ or missing encoded data slices. At a high level, the integrity processing unit20performs rebuilding by periodically attempting to retrieve/list encoded data slices, and/or slice names of the encoded data slices, from the DSN memory22. For retrieved encoded slices, they are checked for errors due to data corruption, outdated version, etc. If a slice includes an error, it is flagged as a ‘bad’ slice. For encoded data slices that were not received and/or not listed, they are flagged as missing slices. Bad and/or missing slices are subsequently rebuilt using other retrieved encoded data slices that are deemed to be good slices to produce rebuilt slices. The rebuilt slices are stored in the DSN memory22.

In the present example, Cauchy Reed-Solomon has been selected as the encoding function (a generic example is shown inFIG. 5and a specific example is shown inFIG. 7); the data segmenting protocol is to divide the data object into fixed sized data segments; and the per data segment encoding values include: a pillar width of 5, a decode threshold of 3, a read threshold of 4, and a write threshold of 4. In accordance with the data segmenting protocol, the computing device12or16divides the data (e.g., a file (e.g., text, video, audio, etc.), a data object, or other data arrangement) into a plurality of fixed sized data segments (e.g., 1 through Y of a fixed size in range of Kilo-bytes to Tera-bytes or more). The number of data segments created is dependent of the size of the data and the data segmenting protocol.

FIG. 6illustrates a specific example of Cauchy Reed-Solomon encoding with a pillar number (T) of five and decode threshold number of three. In this example, a first data segment is divided into twelve data blocks (D1-D12). The coded matrix includes five rows of coded data blocks, where the first row of X11-X14corresponds to a first encoded data slice (EDS1_1), the second row of X21-X24corresponds to a second encoded data slice (EDS2_1), the third row of X31-X34corresponds to a third encoded data slice (EDS3_1), the fourth row of X41-X44corresponds to a fourth encoded data slice (EDS4_1), and the fifth row of X51-X54corresponds to a fifth encoded data slice (EDS5_1). Note that the second number of the EDS designation corresponds to the data segment number.

As a result of encoding, the computing device12or16produces a plurality of sets of encoded data slices, which are provided with their respective slice names to the storage units for storage. As shown, the first set of encoded data slices includes EDS1_1through EDS5_1and the first set of slice names includes SN1_1through SN5_1and the last set of encoded data slices includes EDS1_Y through EDS5_Y and the last set of slice names includes SN1_Y through SN5_Y.

To recover a data segment from a decode threshold number of encoded data slices, the computing device uses a decoding function as shown inFIG. 9. As shown, the decoding function is essentially an inverse of the encoding function ofFIG. 5. The coded matrix includes a decode threshold number of rows (e.g., three in this example) and the decoding matrix in an inversion of the encoding matrix that includes the corresponding rows of the coded matrix. For example, if the coded matrix includes rows 1, 2, and 4, the encoding matrix is reduced to rows 1, 2, and 4, and then inverted to produce the decoding matrix.

Referring next toFIG. 10, a logic diagram of an example of a method of transferring objects from a source endpoint to a storage endpoint will be discussed in accordance with various embodiments of the present invention. As illustrated by block1012, a determination is made regarding which transfer service, or transfer technology protocol, to use at the beginning of a data object transfer between a source endpoint device and a storage endpoint device. The determination can be made based on current network/link conditions, such as current round trip times for requests and responses, historical network/link conditions, predefined parameter thresholds, pre-configured IP addresses of endpoints for object storage for requests, pre-configured bucket names for read or write requests, pre-configured object names for read or write requests, pre-configured accounts or users for requests, pre-configured file types, pre-configured file sizes, and information included in responses received from a storage endpoint, or on information about network conditions from other network devices capable of communicating with the source endpoint device, such as a managing unit.

In some embodiments, the storage endpoint can set its own transfer technology protocol based on information included in a message from the source endpoint, based on an evaluation of data received from the storage endpoint to identify the transfer technology protocol being used, or based on information about network conditions from other network devices capable of communicating with the source endpoint device, such as a managing unit.

In some embodiments, the storage endpoint device provides sufficient information to the source endpoint device to allow the source endpoint device to select an appropriate transfer technology protocol/transfer service the storage endpoint device can determine which information to provide to the source endpoint based on availability of a particular transfer service, or expected outages/disruptions in network or storage service, pre-configured bucket names, pre-configured IP addresses of end points for client applications, pre-configured object names, pre-configured users, pre-configured file types, pre-configured file sizes, information obtained from a management unit, or the like.

As illustrated by block1014, a communications link is established between the source endpoint and the storage endpoint. The communications link can be established using various network messaging protocols, or as specified by one or more transfer technology protocols.

As illustrated by block1016, transfer of an object from the source endpoint to the storage endpoint, for storage by the storage endpoint, is initiated. In at least one embodiment, the source endpoint initiates the object storage over the communications link using a transfer technology protocol selected according to one or more current link performance parameters, or as otherwise selected as discussed with reference to block1012.

The current link performance parameters are monitored at block1018. In at least one embodiment, monitoring of the link performance parameters is performed by the source endpoint. Monitoring the link performance parameters can include directly measuring link parameters such packet loss and round trip times of data packets including the object being transferred, but can also include indirect measurement of those same or other parameters. Indirect measurement can include receiving messages from external devices indicating packet loss statistics, round trip times of data or control messages, general network notifications and information indicating potential network device outages, or the like.

As illustrated by block1019, a determination is made regarding whether the initial transfer technology protocol should be switched in favor of a different transfer technology protocol. The determination can be made based on, for example, measured packet loss or round trip time exceeding a preset threshold, based on historical network performance, or the like. For example, if network performance historically drops after 30 seconds of data transfer, or at particular times of day, the transfer service can be preemptively switched to avoid potential delays in transferring data objects. Similarly, transfer services can be switched in anticipation of a planned outage of particular portions of a communications network. Accordingly, in embodiments, the decision to switch from the initial (first) transfer technology protocol to the different (second) transfer technology protocol is performed in a manner transparent to a user of the source endpoint.

As illustrated by block1020, if the determination at block1019indicates that the transfer technology protocol is to be switched, the protocol being used can be switched—even during transfer of an object, or in the midst of transferring a set of objects. If, however, the determination at block1019indicates that the protocol is not to be switched, transfer of the data object can be continued at block1022.