Abstract: One or more techniques and/or computing devices are provided for resynchronization. For example, a request may be received to create pseudo snapshots of a first consistency group, hosted by a first storage controller, and a second consistency group, hosted by a second storage controller, having a synchronous replication relationship with the first consistency group. Incoming client write requests are logged within an intercept tracking log at the first storage controller. After a first drain without hold of incoming write requests is performed, a first pseudo common snapshot of the second consistency group is created. After a second drain without hold of incoming write operations is performed, a second pseudo common snapshot of the first consistency group and the intercept tracking log is created. The pseudo snapshots and the intercept tracking log (e.g., indicating a delta between the pseudo snapshots) are used to resynchronize the first and second consistency groups.

Abstract: An aircraft rotor blade assembly includes a rotor blade rotatable about an axis of rotation and a weighted assembly mounted to the aircraft rotor blade. The weighted assembly includes an actuator which moves a mass to adjust a moment of the rotor blade assembly when the rotor blade is rotated about the axis of rotation.

Abstract: One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Abstract: One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Abstract: One or more techniques and/or computing devices are provided for utilizing a tracking structure for data replication synchronization. For example, a first storage controller, hosting first storage, may have a replication relationship with a second storage controller hosting second storage (e.g., write requests, modifying the first storage, may be replicated to the second storage). The first storage controller maintains a tracking structure comprising hash buckets, dynamic tree structures, and/or a tracking segment bitmap used to identify portions of the first storage as either comprising dirty data (e.g., data, modified by a write request not yet replicated to the second storage, that may be different than corresponding data within the second storage) or clean data (e.g., the same data as the second storage). The tracking structure may be used to resynchronize the second storage to the first storage, perform a quick resync, facilitate semi-synchronous replication, and/or perform snapshot-less resync.

Abstract: A method and computer program product for identifying errors in a computerized preparation of an electronic financial document to be submitted to an agency. A financial document preparation program is executed, a first connection is initiated with a computer of the agency, the schema requirements are received from the agency via the first connection, data entry fields are generated, data entered into the data entry fields is received, error rules are generated from the schema requirements, each error rule associated with a respective one of the data entry fields associated with the electronic financial document, the data entered into the data entry fields is checked against the respective error rules to identify schema errors in the data entered into the data entry fields, the electronic financial document is generated based on the data entered into the data entry fields, and the electronic financial document is electronically transmitted to the agency.

Abstract: One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Abstract: One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Abstract: One or more techniques and/or computing devices are provided for resynchronization. For example, a request may be received to create pseudo snapshots of a first consistency group, hosted by a first storage controller, and a second consistency group, hosted by a second storage controller, having a synchronous replication relationship with the first consistency group. Incoming client write requests are logged within an intercept tracking log at the first storage controller. After a first drain without hold of incoming write requests is performed, a first pseudo common snapshot of the second consistency group is created. After a second drain without hold of incoming write operations is performed, a second pseudo common snapshot of the first consistency group and the intercept tracking log is created. The pseudo snapshots and the intercept tracking log (e.g., indicating a delta between the pseudo snapshots) are used to resynchronize the first and second consistency groups.

Abstract: One or more techniques and/or computing devices are provided for utilizing a tracking structure for data replication synchronization. For example, a first storage controller, hosting first storage, may have a replication relationship with a second storage controller hosting second storage (e.g., write requests, modifying the first storage, may be replicated to the second storage). The first storage controller maintains a tracking structure comprising hash buckets, dynamic tree structures, and/or a tracking segment bitmap used to identify portions of the first storage as either comprising dirty data (e.g., data, modified by a write request not yet replicated to the second storage, that may be different than corresponding data within the second storage) or clean data (e.g., the same data as the second storage). The tracking structure may be used to resynchronize the second storage to the first storage, perform a quick resync, facilitate semi-synchronous replication, and/or perform snapshot-less resync.

Abstract: One or more techniques and/or computing devices are provided for resynchronization. For example, a request may be received to create pseudo snapshots of a first consistency group, hosted by a first storage controller, and a second consistency group, hosted by a second storage controller, having a synchronous replication relationship with the first consistency group. Incoming client write requests are logged within an intercept tracking log at the first storage controller. After a first drain without hold of incoming write requests is performed, a first pseudo common snapshot of the second consistency group is created. After a second drain without hold of incoming write operations is performed, a second pseudo common snapshot of the first consistency group and the intercept tracking log is created. The pseudo snapshots and the intercept tracking log (e.g., indicating a delta between the pseudo snapshots) are used to resynchronize the first and second consistency groups.

Abstract: One or more techniques and/or computing devices are provided for resynchronization. For example, a request may be received to create pseudo snapshots of a first consistency group, hosted by a first storage controller, and a second consistency group, hosted by a second storage controller, having a synchronous replication relationship with the first consistency group. Incoming client write requests are logged within an intercept tracking log at the first storage controller. After a first drain without hold of incoming write requests is performed, a first pseudo common snapshot of the second consistency group is created. After a second drain without hold of incoming write operations is performed, a second pseudo common snapshot of the first consistency group and the intercept tracking log is created. The pseudo snapshots and the intercept tracking log (e.g., indicating a delta between the pseudo snapshots) are used to resynchronize the first and second consistency groups.

Abstract: One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Abstract: A wireless communication system is configured for adaptive modulation of a transmitted symbol. The specific modulation and/or coding is uniquely identified and data related thereto is embedded within the transmitted symbol. A receiver extracts pilot signals form the transmitted symbol and performs a correlation analysis to identify the particular modulation/coding used for that particular transmitted symbol. This permits adaptive modulation on a symbol-by-symbol basis. A base station communicating with a plurality of peripheral subscribers may utilize different modulation/coding for each subscriber depending on channel conditions.

Abstract: A fixed wireless access system generally comprises a consumer premise equipment (CPE) unit, that is connected via an Ethernet interface to a personal computer or local area network, and a base station unit that is connected via an Ethernet interface to a network. As such, the CPE unit is preferably easily user-installed while the base station unit is preferably tower-mounted within a 1-5 mile range of the CPE unit. Both the CPE unit and base station unit preferably incorporate an integrated data transceiver/switch that enables a radio frequency air link operating in the 2.5-2.686 GHz range. Orthogonal frequency division multiplexing is used in the uplink and downlink transmissions between CPE units and base station units.

Abstract: A fixed wireless access system generally comprises a consumer premise equipment (CPE) unit, that is connected via an Ethernet interface to a personal computer or local area network, and a base station unit that is connected via an Ethernet interface to a network. As such, the CPE unit is preferably easily user-installed while the base station unit is preferably tower-mounted within a 1-5 mile range of the CPE unit. Both the CPE unit and base station unit preferably incorporate an integrated data transceiver/switch that enables a radio frequency air link operating in the 2.5-2.686 GHz range. Orthogonal frequency division multiplexing is used in the uplink and downlink transmissions between CPE units and base station units.

Abstract: The present invention augments an application update with an automatic sequence of steps for instantiating the updated application in place of the currently running application, without unintended loss of the end-user generated data that comprises all or part of the current application state. The new version may consume most or all of the previously entered data to enter a state of needing a minimal amount of new information (which may be different from being in the state of ready to submit).

Abstract: The present invention provides a method, system, and program product for indicating a state of a value of an application. Specifically, under the present invention a graphical state indicator is displayed for a property (e.g., background screen color) of an application. The graphical state indicator will indicate a “state” of a value of the property. That is, the graphical state indicator will indicate whether the value is a user-defined value, or is a default value. Under the present invention, a graphical state indicator can be provided for any property of the application. As such, multiple graphical state indicators may be simultaneously displayed. The present invention can also display a graphical value indicator for indicating the current value (e.g., blue) of the property (e.g., background screen color). This value can be changed based upon an interaction with the graphical value indicator by a user.

Abstract: The present invention provides a method, system and program product for transcoding content. Specifically, under the present invention, selected content is retrieved from a content source to a server. Once retrieved, the content is transcoded into a format used by a remote device. The transcoded data could then be tested for accuracy and stored in an external file system. Once stored, a mobile Internet agent will route the content from the file system to the remote device.

Abstract: The present invention provides visual inspection and physical access into the space of a fluid containment system consisting of an inner storage container or vessel, and an outer, reinforced precast structure, or vault, having a top cover. Visual inspection ports and physical access assemblies, with easily removable covers, are cast into the vault top corners for direct, or remote viewing, such as with a periscope or video camera device, of the exterior surfaces of the inner storage container; the interior surfaces of the outer, vaulted structure; and the space between the two structures. Sufficient physical access and physical maneuverability is provided by the visual inspection port assemblies, and corresponding visual inspection chambers directly below each port assembly, that proactive inspection to verify primary vessel integrity and removal of fluids from the interior space between the two containers can be achieved without personnel entry or removal of the vault top.