Patent application number | Description | Published |
20130204843 | ADAPTIVE QUIESCE FOR EFFICIENT CROSS-HOST CONSISTENT CDP CHECKPONTS - A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative. | 08-08-2013 |
20140298092 | ADAPTIVE QUIESCE FOR EFFICIENT CROSS-HOST CONSISTENT CDP CHECKPOINTS - A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative. | 10-02-2014 |
20150019911 | ADAPTIVE QUIESCE FOR EFFICIENT CROSS-HOST CONSISTENT CDP CHECKPOINTS - A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative. | 01-15-2015 |
Patent application number | Description | Published |
20080205388 | Discovery of network devices logically located between a client and a service - Otherwise network-transparent devices that are logically located between a client device and a service device are discovered by sending a probe packet that has a destination address of one of the client or service but that specifies a discovery network port such as a port of the transport layer. The otherwise network-transparent device receives the packet as it is traversing the hops between the client and service. The network-transparent device analyzes the network traffic passing through it to determine whether the destination port is the discovery network port and thereby recognizes the probe packet. The network-transparent device provides a return packet to the device that sent the probe packet, whereby the return packet provides the source address as the network address of the otherwise network-transparent device. A communication session may then be established between the network-transparent device and the device that sent the probe packet such as to provide a service to the data transfer occurring between the client and service. | 08-28-2008 |
20080267217 | Compression of data packets while maintaining endpoint-to-endpoint authentication - Contiguous data packets of a single communication session between endpoints are gathered for compression, and at least the payloads are compressed collectively via a single compressible buffer. The original headers, which may or may not be compressed, and the compressed payloads are transmitted from a sending packet compression device to a receiving packet compression device that performs decompression to the compressed payload and may also decompress headers if they have been compressed at the sending end. The original contiguous data packets including headers and payload may be reconstructed at the receiving packet compression device by matching the headers to the corresponding payloads. The reconstructed data packets are injected back into the single communication session, and the presence of the original headers in the reconstructed data packets may thereby maintain the endpoint-to-endpoint authentication protocols. | 10-30-2008 |
20090024763 | Optimizing encrypted wide area network traffic - Optimization of encrypted traffic flowing over a WAN is provided by an arrangement in which WAN compression is distributed between endpoints (i.e., client machines or servers) in a subnet of a hub and branch network and a WAN compression server in the subnet. A client portion of the WAN compression running on each of one or more endpoints interfaces with a disposable local cache of data seen by endpoints in the subnet that is used for compressing and decompressing traffic using dictionary-based compression techniques. The local WAN compression server in a subnet stores a shared central database of all the WAN traffic in the subnet which is used to populate local disposable caches in the endpoints. | 01-22-2009 |
20110010536 | OPTIMIZING ENCRYPTED WIDE AREA NETWORK TRAFFIC - Optimization of encrypted traffic flowing over a WAN is provided by an arrangement in which WAN compression is distributed between endpoints (i.e., client machines or servers) in a subnet of a hub and branch network and a WAN compression server in the subnet. A client portion of the WAN compression running on each of one or more endpoints interfaces with a disposable local cache of data seen by endpoints in the subnet that is used for compressing and decompressing traffic using dictionary-based compression techniques. The local WAN compression server in a subnet stores a shared central database of all the WAN traffic in the subnet which is used to populate local disposable caches in the endpoints. | 01-13-2011 |
20120117498 | SECONDARY OUTPUT GENERATION FROM A PRESENTATION FRAMEWORK - A secondary output of a user interface created using a presentation framework may be created by making a clone of the user interface, then modifying the cloned user interface by expanding various components. The cloned user interface may also be configured to the output characteristics of the secondary output, which may be a printer or other hardcopy device. The user interface may be created with callbacks or other actions that may be executed when the cloned user interface is configured. The callbacks may cause certain user interface components to be changed on the cloned version of the user interface. | 05-10-2012 |
20140040795 | SECONDARY OUTPUT GENERATION FROM A PRESENTATION FRAMEWORK - A secondary output of a user interface created using a presentation framework may be created by making a clone of the user interface, then modifying the cloned user interface by expanding various components. The cloned user interface may also be configured to the output characteristics of the secondary output, which may be a printer or other hardcopy device. The user interface may be created with callbacks or other actions that may be executed when the cloned user interface is configured. The callbacks may cause certain user interface components to be changed on the cloned version of the user interface. | 02-06-2014 |