Abstract: Disclosed are systems, methods and computer readable mediums for optimized throughput of an object based storage system. The systems, methods and computer readable mediums including receiving an I/O request to the storage system, determining a busy ratio based on a number of blocks available in a local cache and a queue size, determining an I/O speed to the storage system, the I/O speed based at least in part on the busy ratio and an upload speed, wherein the I/O speed does not exceed a current speed of the storage system, and executing the I/O request to the storage system at the I/O speed.

Abstract: Systems and methods for a flow-based data processing can begin with receiving a selection of a plurality of data processor blocks and a configuration mapping corresponding to the inputs and outputs of each data processor block. At a first compute node associated with a selected data source, an automated data flow can be initiated, wherein the automated data flow is generated from the configuration mapping and comprises a continuous sequence of one or more of the selected plurality of data processor blocks. Data from the selected data source is ingested into the automated data flow and is transformed by the continuous sequence of data processor blocks. The transformed ingested data is transmitted from the automated data flow to a second compute node associated with a selected data destination, via a data accelerator.

Abstract: Systems and methods for a flow-based data processing can begin with receiving a selection of a plurality of data processor blocks and a configuration mapping corresponding to the inputs and outputs of each data processor block. At a first compute node associated with a selected data source, an automated data flow can be initiated, wherein the automated data flow is generated from the configuration mapping and comprises a continuous sequence of one or more of the selected plurality of data processor blocks. Data from the selected data source is ingested into the automated data flow and is transformed by the continuous sequence of data processor blocks. The transformed ingested data is transmitted from the automated data flow to a second compute node associated with a selected data destination, via a data accelerator.

Abstract: A method for generating a synthetic backup comprises generating a full backup of a data source at an initial timestamp and generating a first incremental backup of the data source at a first timestamp subsequent to the initial timestamp. The first incremental backup comprises one or more modifications made to data stored in the data source between the initial timestamp and the first timestamp. A synthetic backup is generated from at least the full backup and the first incremental backup by altering one or more file system parameters of the data source and performing forwards reads for the first incremental backup based on the modified file system parameters. In response to determining that forward read data has not been merged into a synthetic backup, the forward read data is stored in a read cache and the full backup is merged with the forward read data in the read cache.

Abstract: Dynamic pool-based tiering is provided for a file system including a plurality of storage priority tiers each comprising one or more storage pools and associated volumes. Received data is written to a selected priority tier. Based on one or more transfer criteria, it is determined that a given data item stored in a source volume of a first priority tier should be transferred out of the first tier. The transfer criteria include a number of times the given data item has been accessed and an interaction history of the given data item. Based on an analysis of the transfer criteria, a target volume within a second priority tier of the file system where the given data item can be transferred to is identified. The given data item is transferred to the target volume of the second priority tier, and is removed from the source volume within the first priority tier.

Abstract: Disclosed are systems, methods and computer readable mediums for optimized throughput of an object based storage system. The systems, methods and computer readable mediums including receiving an I/O request to the storage system, determining a busy ratio based on a number of blocks available in a local cache and a queue size, determining an I/O speed to the storage system, the I/O speed based at least in part on the busy ratio and an upload speed, wherein the I/O speed does not exceed a current speed of the storage system, and executing the I/O request to the storage system at the I/O speed.

Abstract: Systems and methods for a flow-based data processing can begin with receiving a selection of a plurality of data processor blocks and a configuration mapping corresponding to the inputs and outputs of each data processor block. At a first compute node associated with a selected data source, an automated data flow can be initiated, wherein the automated data flow is generated from the configuration mapping and comprises a continuous sequence of one or more of the selected plurality of data processor blocks. Data from the selected data source is ingested into the automated data flow and is transformed by the continuous sequence of data processor blocks. The transformed ingested data is transmitted from the automated data flow to a second compute node associated with a selected data destination, via a data accelerator.

Abstract: Disclosed are systems and methods for an optimal transmission rate for large quantities of data over a network using gambler strategies. The gambler strategies can include initiating a gambler of a generation including a plurality of gamblers and transmitting one or more packets for the gambler over a network at a transmission rate specified by the gambler. In response to a determination the gambler is finished the network to discharge. In response to a determination the generation is finished, determining a gain-loss of the generation and the plurality of gamblers can be adjusted to be inline with an inherent network data loss rate.

Abstract: Method and apparatus for switching between a first server and a second server, each located within a virtual private cloud and the first server being located within a first zone and the second server being located within a second zone that is physically separate from the first zone. The method and apparatus further configured to determine that the first server has experienced a failure to send or receive data. The method and apparatus further configured to enable a second port on the second server. The method and apparatus further configured to create a new route table by the second server and flush the previous route table. The method and apparatus further configured to transmit, via the second port, a request to a virtual private cloud controller to update an elastic internet protocol address with the second port information and receive data from the virtual private cloud controller.

Abstract: Disclosed are systems and methods for an optimal transmission rate for large quantities of data over a network using gambler strategies. The gambler strategies can include initiating a gambler of a generation including a plurality of gamblers and transmitting one or more packets for the gambler over a network at a transmission rate specified by the gambler. In response to a determination the gambler is finished the network to discharge. In response to a determination the generation is finished, determining a gain-loss of the generation and the plurality of gamblers can be adjusted to be inline with an inherent network data loss rate.

Abstract: Method and apparatus for switching between a first server and a second server, each located within a virtual private cloud and the first server being located within a first zone and the second server being located within a second zone that is physically separate from the first zone. The method and apparatus further configured to determine that the first server has experienced a failure to send or receive data. The method and apparatus further configured to enable a second port on the second server. The method and apparatus further configured to create a new route table at the second server and flush the previous route table. The method and apparatus further configured to transmit, via the second port, a request to a virtual private cloud controller to update an elastic internet protocol address with the second port information and receive data from the virtual private cloud controller.

Abstract: Disclosed are systems and methods for an optimal transmission rate for large quantities of data over a network using gambler strategies. The gambler strategies can include initiating a gambler of a generation including a plurality of gamblers and transmitting one or more packets for the gambler over a network at a transmission rate specified by the gambler. In response to a determination the gambler is finished the network to discharge. In response to a determination the generation is finished, determining a gain-loss of the generation and the plurality of gamblers can be adjusted to be inline with an inherent network data loss rate.

Abstract: Method and apparatus for switching between a first server and a second server, each located within a virtual private cloud and the first server being located within a first zone and the second server being located within a second zone that is physically separate from the first zone. The method and apparatus further configured to determine that the first server has experienced a failure to send or receive data. The method and apparatus further configured to enable a second port on the second server. The method and apparatus further configured to create a new route table by the second server and flush the previous route table. The method and apparatus further configured to transmit, via the second port, a request to a virtual private cloud controller to update an elastic internet protocol address with the second port information and receive data from the virtual private cloud controller.

Abstract: A system of replicating data stored on a source node. Replication can be configured between two controllers, the source node on the one hand, and a target node on the other. A synchronization relationship between the source node and the target node is established and maintained. The synchronization relationship can be quickly and easily created for disaster recovery, real-time backup and failover, thereby ensuring that data on the source node is fully-protected at an off-site location or on another server or VM, for example, at another data center, a different building or elsewhere in the cloud. Processes described herein streamline the entire replication setup process, thereby significantly reducing error rates in conventional systems and making the replication process more user friendly than in conventional systems.