Abstract: Embodiments of an overlay network with innovative virtual network switches and related network interface controllers are disclosed. According to one embodiment, the overlay network may comprise at least one virtual network switch (VNS), wherein each VNS is installed within a corresponding first processing endpoint which is logically above a network of virtual machines. And, the VNS may be configured to intercept data packets transmitted on a network layer logically below the network of virtual machines. The VNS may comprise: (a) a manager element configured to connect to at least one virtual network interface controller (VNIC), each VNIC being installed within a corresponding second processing endpoint which is also logically above the network of virtual machines; (b) a replicator node configured to replicate and route the data packets; and (c) a switch controller configured to control the first replicator node.

Abstract: Embodiments of an overlay network with innovative virtual network switches and related network interface controllers are disclosed. According to one embodiment, the overlay network may comprise at least one virtual network switch (VNS), wherein each VNS is installed within a corresponding first processing endpoint which is logically above a virtualization layer of a virtual network. And, the VNS may be configured to intercept data packets transmitted on a network layer logically below the virtualization layer of the virtual network. The VNS may comprise: (a) a manager element configured to connect to at least one virtual network interface controller (VNIC), each VNIC being installed within a corresponding second processing endpoint of the virtual network, the second processing endpoint being separate from the first processing endpoint; (b) a replicator node configured to replicate and route the data packets; and (c) a switch controller configured to control the first replicator node.

Abstract: A method and system operate to secure and efficiently manage data. The method includes performing steps such as generating independent keys corresponding to multiple portions of segmented data and utilizing the independent keys to encrypt the multiple portions of segmented data. The method additionally includes generating a master key, encrypting the independent keys with the master key, and storing each portion of the segmented data adjacent to the corresponding independent key in a data and key storage device. The method additionally includes segmenting the master key, thereby creating multiple master key segments and storing the multiple master key segments in disparate locations separate from the data.

Abstract: A Data Synchronization and Failover Management (DSFM) system monitors simultaneous execution of non-identical instances of a software application and may label as a particular result of the software application the earliest output corresponding to that result produced by one of the instances. The DSFM may label one of the instances as a primary instance and the other instances as secondary instances and, if the primary instance fails, may re-label one of the secondary instances that computed all of the operations associated with the last result produced prior to the failure of the primary instance, as a new primary instance.

Abstract: A method and system operate to secure and efficiently manage data. The method includes performing steps such as generating independent keys corresponding to multiple portions of segmented data and utilizing the independent keys to encrypt the multiple portions of segmented data. The method additionally includes generating a master key, encrypting the independent keys with the master key, and storing each portion of the segmented data adjacent to the corresponding independent key in a data and key storage device. The method additionally includes segmenting the master key, thereby creating multiple master key segments and storing the multiple master key segments in disparate locations separate from the data.

Abstract: A Data Synchronization and Failover Management (DSFM) system monitors simultaneous execution of non-identical instances of a software application and may label as a particular result of the software application the earliest output corresponding to that result produced by one of the instances. The DSFM may label one of the instances as a primary instance and the other instances as secondary instances and, if the primary instance fails, may re-label one of the secondary instances that computed all of the operations associated with the last result produced prior to the failure of the primary instance, as a new primary instance.

Abstract: A Data Synchronization and Failover Management (DSFM) system monitors simultaneous execution of non-identical instances of a software application and may label as a particular result of the software application the earliest output corresponding to that result produced by one of the instances. The DSFM may label one of the instances as a primary instance and the other instances as secondary instances and, if the primary instance fails, may re-label one of the secondary instances that computed all of the operations associated with the last result produced prior to the failure of the primary instance, as a new primary instance.

Abstract: Embodiments of the Message Retransmission Mechanism Apparatuses, Methods and Systems (“MRM”) transform application requests for message journals via MRM components into expedited access to segmented message streams. In one implementation, the MRM may obtain message journal of messages written by applications during system operations and divide up the message obtained from the complete message journal into message segments. In some implementations, the MRM may provide recovering applications access to said message segments for expedited message consumption.

Abstract: A Data Synchronization and Failover Management (DSFM) system monitors simultaneous execution of non-identical instances of a software application and may label as a particular result of the software application the earliest output corresponding to that result produced by one of the instances. The DSFM may label one of the instances as a primary instance and the other instances as secondary instances and, if the primary instance fails, may re-label one of the secondary instances that computed all of the operations associated with the last result produced prior to the failure of the primary instance, as a new primary instance.

Abstract: Embodiments of the Message Retransmission Mechanism Apparatuses, Methods and Systems (“MRM”) transform application requests for message journals via MRM components into expedited access to segmented message streams. In one implementation, the MRM may obtain message journal of messages written by applications during system operations and divide up the message obtained from the complete message journal into message segments. In some implementations, the MRM may provide recovering applications access to said message segments for expedited message consumption.