468 results about "Rollback" patented technology

A system is provided for continuous protection of data and storage configuration metadata. Content protected by snapshots, for example, in connection with continuous snapshotting and / or continuous data protection, may be extended to include not only user data but further include configuration metadata of the storage management system. In particular, a user may want to rollback a storage management system to a past point due to performance or stability issues attributed to configuration changes. The system described herein enables rollback to prior states based on storage configuration metadata in addition to rollback of user data and provides for synchronization of the data and configuration metadata in connection with a rollback. The system also enables roll forward processing.

A method and controller device for upgrading the firmware in a virtualized storage environment having a first storage controller and a second storage controller, wherein each storage controller includes a first virtual machine, at least one second virtual machine and a storage device. The method includes upgrading the current firmware of the first virtual machine in the first storage controller to a new firmware version, upgrading the current firmware of the second virtual machine in the first storage controller to a new firmware version, upgrading the current firmware of the first virtual machine in the second storage controller, upgrading the current firmware of the second virtual machine in the second storage controller, and rolling back the firmware version of all virtual machines in the first and second storage controllers if the firmware upgrade of any of the virtual machines in the first and second storage controllers is not successful.

Installing software using the configuration manager so that the rollback and security features of the configuration manager may be used during the installation process. A mobile computing device accesses files that are to be installed on the mobile computing device, and well as computer-executable instructions that define how the files are to be installed on the mobile computing device. The configuration manager then causes the computer-executable instructions to be executed (e.g., using configuration service providers), and causes a mirroring rollback document to be constructed. If the installation fails, the installation process is reversed by executing the rollback document. The configuration manager may also be used to implement security when executing the installation instructions by checking to determine whether or not execution of each installation instruction is authorized.

A code signature methodology that allows recovery from incorrectly signed software while preventing rollbacks is described herein. When software is signed, the code signature is based not only on the current version of executable code and information corresponding to the current version of executable code, but also includes a history value based on a previous version of the executable code. Each history value is unknown until each version of the software is validly signed. Thus, the code signature technique allows a signing entity to continue using the same signing key even after recovering from an attack, can be used with and without pre-configured trust roots, and allows a device to upgrade from one version of software to another version of the software while skipping intermediate versions.

A method, apparatus and program storage device for performing a return / rollback process for RCU-protected data structures is provided that includes checking a user-level state of a preempted thread having a RCU read-side critical section, and executing the critical section of the thread after preemption when the user-level state of the thread indicates execution, otherwise returning to a point of preemption, resuming execution of the thread and disabling checking the user-level state when the user-level state of the thread indicates return.

The invention discloses version management and file pulling control methods for static files, version management and file pulling control devices, and a version control system. The version management method for the static files includes: a version number is marked at each static file in the at least one static file, the static files marked with the version numbers are regarded as to-be-released files; a version configuration file corresponding to at least one to-be-released file is generated; the version configuration file comprises a file name and the information of the version number of the at least one to-be-released file; and the at least one to-be-released file is released in a content distribution network server, and the version configuration file is released in an operation server in a gated launch manner. According to the technical scheme, clear management and control of static file versions can be realized, the chaos of the static file versions is avoided, and rollback, gated launch, and incremental release of the static files can be supported.

Multiple revisions of an encoded data slice can be stored in a distributed storage unit. Before writing a new revision of an encoded data slice to storage, the distributed storage unit can invoke a write lock for all encoded data slices having the same slice name as the slice being currently written. The slice being currently written can be stored in temporary storage, and a rollback timer started. If a commit command is received before expiration of the rollback timer, the currently written slice can be permanently stored and made accessible for read requests. If the rollback timer expires prior to the storage unit receiving a commit command, however, a previously stored revision will be used.

The invention belongs to the technical field of distributed computation and discloses a distributed transaction processing method and a device thereof. The distributed transaction processing method includes the steps of application development, transaction management attribute definition, event definition, streaming calculation and transaction management. To be specific, the method includes the steps of acquiring and identifying event information in real time through the streaming calculation, acquiring transaction management attributes in real time, periodically verifying transaction status based on the event information and the transaction management attributes, initiating a verification request and / or a reversal request based on the transaction status, and sending transaction status verification instructions and / or reversal instructions through a transaction manager. With the above-mentioned scheme, the distributed transaction processing method and the device thereof have the advantages of allowing transaction control and the application development to be completely decoupled, not requiring development transaction control logic for the application development, greatly simplifying development difficulty, realizing fast rollback of transactions under abnormal scenarios, tolerating failure of any node and having no brain splitting problem.

This invention includes a circuit for tracking memory operations with trace-based execution. Each trace includes a sequence of operations that includes zero or more of the memory operations. Traces execute atomically and become eligible for commitment after all the operations in the trace have executed. The memory operations being executed form a set of active memory operations that have a predefined program order among them and corresponding ordering constraints. At least some of the active memory operations access the memory in an execution order that is different from the program order. Checkpoint entries are associated with each trace. Each entry refers to a checkpoint location. Memory operation ordering entries correspond to each one of the active memory operations. Rollback requests result in overwriting the checkpoint locations associated with the selected trace as well as the checkpoint locations associated with traces that are younger than the selected trace.

The utility model discloses an implementation method for the repeated read of database which is used for a multi-user and multiple transaction concurrency database management system which maintains a transaction list, a rollback segment and an index tree. The method comprises the following steps: firstly, the page satisfying conditions is quickly positioned utilizing the index when traversing the transaction list maintained by the system, wherein the transaction list is used for storing the transaction which is concurrently executed and uncommitted; secondly, the current transaction is checked when traversing the page record to found whether the current record is visible, the current record is added to the result set if the current record is visible; otherwise, the original version is constructed and added to the result set by utilizing the revocation log of the rollback segment maintained by the system, wherein the rollback segment is used for recording the modification of the transactions. The utility model also discloses an implementation apparatus utilizing the method and a database management system utilizing the method and the apparatus.

The invention discloses a method, device and associated equipment for rolling back an application program. The method for rolling back the application program comprises the steps of obtaining current version information of the application program and rollback target version information, further obtaining a patch file corresponding to upgrading from a target version to a current version of the application program, generating an installation file of the target version according to the patch file and a current installation file of the application program, and operating the installation file of the current version. The invention further provides the device, terminal device and server for rolling back the application program. According to the method, device and associated equipment for rolling back the application program, the installation file of the current version of the application program and the patch file corresponding to the upgrading from the target version to the current version of the application program are utilized for obtaining the installation file of the target version, the installation file of the target version is operated to roll back the application program from the current version to the target version.

The deployment of application revisions and performing of application rollbacks across multiple application servers is streamlined by reducing the number of files that are communicated to the application servers to perform updates and rollbacks. An application service is provided by multiple application servers each executing a plurality of compiled code files associated with the application service. Each application server receives a compiled code file corresponding to an update for one of the plurality of compiled code files associated with the application service. The one compiled code file is replaced with the received compiled code file corresponding to the update. The application servers then provide an updated version of the application service by executing the plurality of compiled code files including the replacement compiled code file corresponding to the update. Application rollback is performed using compiled code files stored in a local repository of each application server.

Disclosed is a rollback-free method for performing multi-step procedures in the presence of possible failure. As the procedure proceeds from its initial state through transitions to its final state, its constituent transitions are monitored for failure. If a failure is detected, then the procedure is “sidetracked” into a recovery coordination state. From the recovery coordination state, the procedure is logically taken back to its initial state and retried. In this manner, the procedure is shepherded, without rollbacks, through its transitions until it successfully reaches its final state. In a particular embodiment, a multi-step procedure is developed for moving a resource from one resource server to another. The steps of the procedure are designed so that all throughout the procedure, both of the resource servers and a directory server are kept synchronized. This allows client requests to proceed without interruption even during the resource movement.

The invention discloses a method and device for uninstalling an application program. The method comprises the steps of obtaining path information of a file released in the installation process of the application program and modification information executed by a registry key, storing the path information of the obtained file and the modification information as a journal file, when the application program needs to be uninstalled, deleting the file released in the installation process of the application program according to the journal file,, and restoring the related registry key into the status before modification. According to the method and device for uninstalling the application program, the complete rollback of the file released in the installation process of the application program and the modified registry information can be achieved, and waste of system resources is avoided.

A method and system that provides for near-zero downtime when updating enterprise system software in a client / server environment and elimination of the need to re-compile the client code with a new server component name as the new name can be addressed in a naming service. Client components will automatically connect to new-version enterprise server components that are backward compatible. Old-version client components will still work as new enterprise server components are deployed even if they are not backward compatible. Using a design with a step algorithm, the incompatibilities of client and enterprise server components are resolved. Client components automatically check a configuration file at initialization time or in parallel for the correct compatible version to use. Client rollback to the previous version is easily accomplished if bugs are found in the new deployment.

The invention discloses an analytic method of control information. The analytic method includes that the serial number of the resource where a Physical Downlink Control Channel (PDCCH) used for loading a DCI is located is obtained, and the obtained serial number of the resource is used for delivery calculation for delivery parameters; and the format of the DCI loaded on the resource corresponding to the resource serial number is judged according to the remainder of delivery calculation, wherein the format of the DCI includes a normal format and a saving bit format, the length of the DCI in the saving bit format is smaller than that of the DCI in the normal format, and the PDCCH is subjected to blind detection by using the judged length of the DCI in the normal format or the saving bit format to obtain all fields of the DCI. The length of the DCI in the saving bit format is smaller than that of the DCI in the normal format, a base station only issues the DCI in one format except for the rollback format for all the resources, so that the variety of the DCI length is not added, and the PDCCH is enhanced without increasing the blind detection times.

An approach is provided for managing a reorganization of a database object. Because a reorganization utility cannot acquire exclusive access to the object to complete the reorganization, determinations are made: an amount of transaction log records corresponding to active units of work using the database object is determined to be less than a first threshold; a sum of costs of SQL statements executed in the units of work is determined to be less than a second threshold; and a priority of the reorganization is determined to indicate a greatest priority among multiple priorities. Based on the determinations, (1) a reorganization lock providing exclusive access to the database object is acquired, (2) process(es) holding lock(s) on the database object experience a lockout error, a rollback of the process(es) is issued, and the lock(s) are released, and (3) the utility completes the reorganization based on the lock(s) being released.

A router rolls back a current running configuration to a selected prior running configuration without requiring interruption or reinitialization of the router or of its network connections. The router retrieves command line interface control settings associated with the selected prior running configuration and those associated with the current running configuration. The router then generates and executes a rollback script based on the difference between the prior control settings and the current control settings.

A patch tool receives multiple patches, with each patch designed to fix a corresponding subset of a set of errors in a system. Some of the patches may require that the files from older patches be removed from the system. In an embodiment of the present invention, a developer of a patch is provided the flexibility to specify that a desired file from an older patch fixing a specific error, not be removed during deployment of a new patch designed to fix the same specific error. Rolling back later to the older version of the patch may be simplified by not removing the desired file.

An internal and external network parallel running system for database merging comprises an internal network database management system, an external network database management system, and an all-weather physical isolation system, wherein the internal network database management system and the external network database management system are isolated from each other by the all-weather physical isolation system, and exchange data by ferrying equipment; an external network database temporary mirroring unit imports external network data in an external network data table of the external network database temporary mirroring unit into an intermediate data table; the intermediate data table merges the imported data in an internal network data table; and transaction-based double rollback error treatment is performed on the intermediate data table and the internal network data table after merging. With the adoption of the method, not only can the correct merging of the data in the data tables be realized, but also the out-of-control data during the date merging can be avoided effectively, and the parallel running of an internal network system and an external network system of the all-weather physical isolation system is ensured.

The invention discloses a service state consistency maintenance method based on transactions. The service state consistency maintenance method supports restoration attribute variety by introducing and distinguishing four restoration attributes, dynamically confirming the attribute situations of service examples in the dispatched composite service example set and any other relevant service examples in two sets according to restoration attributes, timestamp size and dynamically-detected conflict relation by establishing a rollback composite service example set and a non-rollback composite service example set with a waiting queue, so that service concurrence, destruction, recovery and submitting in a composite service engine are finished. The service state consistency maintenance method supports the service restoration attribute variety and various control modes, can ensure the serializability and restorability of concurrence dispatch, avoid a starvation phenomenon, permit concurrence dispatch and execution of multiple composite service examples executing irrecoverable transactions and support dynamic conflict detection of the service examples and can effectively reduce linkage destruction of long-term running transactions.

Implementations are provided herein for non-disruptive upgrade including rollback capabilities for a distributed file system within a cluster of nodes. To continue availability of the file system to external clients during the upgrade process, nodes can be upgraded piecemeal, for example, in one implementation, one node at a time. When a node is undergoing certain stages of the upgrade process, external clients can be directed toward the remaining nodes of the file system that are not currently being upgraded, including already upgraded nodes, to perform client activity. During the upgrade process, a first subset of nodes can be running in an upgraded state while a second subset of nodes can be in a non-upgraded state, both providing access to external clients in a seamless manner. During the upgrade process, an administrator can decide to rollback any upgrades and return the distributed file system to its previous version (e.g., the version of the file system prior to starting the non-disruptive upgrade process). Hooks can be provided prior to, during, and after various stages of the upgrade or rollback process that can allow services of the distributed file system to be notified of certain events of the upgrade process, or execute service specific processes at distinct times during the upgrade process. At the conclusion of an upgrade or rollback process, the distributed file system can enter a committed state that finalizes the process and cements an upgrade or a rollback to a more permanent state.

The invention discloses a continuous integration method and system based on k8s and docker containers. The system comprises a git server, a nereus platform, a mirror image warehouse and a k8s cluster,wherein the git server, the nereus platform, the mirror image warehouse and the k8s cluster are connected in sequence; the git server is used for providing project codes of developers for the netherus platform; wherein the newus platform is used for compiling and packaging project codes of a developer to generate a corresponding package; then, a corresponding docker file is generated through a shell script; a docker build command is used for creating a container; pushing the container to a mirror image warehouse by using a docker push command; pulling down the docker mirror image from the mirror image warehouse through the mirror image address; configurations in a yaml file are utilized to create a container, the container is started and deployed into a k8s cluster to be managed so as tobe conveniently used by developers, and the newus platform constructs packaging and online, supports release, online and rollback of java, python, vue and other codes and can be completed through a page in a one-key mode.

The invention discloses a method for quickly reclaiming rollback space in MySQL. The method includes: closing a MySQL database by means of clearing inactive rollback data during closing; based on an original system table space file of rollback space to be reclaimed, generating a new system table space file not including the rollback space; replacing the original system table space file with the new system table space file. The invention further discloses a device for quickly reclaiming the rollback space in MySQL. The rollback space in MySQL can be quickly reclaimed by the method; availability of the whole database system is improved.

Disclosed are a method and an apparatus for transmitting ACK / NACK feedback information. By applying the technical solution of the present invention, when ACK / NACK feedback information is transmitted based on an ACK / NACK mapping table with a PUCCH format 1b with channel selection scheme, the problem of inconsistent detection results due to inconformity of the transmission scheme by a base station and a user equipment (UE) in the process of feeding back the ACK / NACK feedback information can be avoided, so as to implement a rollback of LTE Rel-8 PUCCH format 1a / 1b.

The invention provides a data security access method based on a block chain in a federated learning environment, and mainly solves the problem that a user does not have a complete control right to owndata in existing federated learning. The method comprises the implementation steps of 1) performing initialization operation on a blockchain, a smart contract and a KGA; 2) the user performs local training on the data, stores the trained data by using IPFS, encrypts the data through CP-ABE, and uploads the encrypted data to a deployed blockchain; 3) the server interacts with the KGA to obtain theuser uploaded data of the required version for centralized training, and updates the final data after training to the blockchain; and 4) the user acquires final data uploaded by the server and updates the local training model according to the data information.The learning process of the method is open and transparent, the control right of the user on the own data is ensured, data backtracking andmodel rollback can be conveniently performed, and version management is facilitated.

The invention provides a project version release management method. The method comprises the steps of packaging a target code of a to-be-released project update version to obtain a target resource packet; uploading the target resource packet to a test server for testing; uploading the target resource packet to a version release server for verification after the test is passed, and releasing a project update version after the verification is passed; and monitoring the published project update version, generating a rollback strategy according to the received feedback data and a preset priority label, and determining and re-publishing a target rollback version according to the rollback strategy. The invention provides a management system for project version release. According to the method, the target resource packet is directly uploaded to the version release server from the test server, so that the consistency of the target resource packet from test to production verification is ensured; the error rate is reduced and the efficiency is improved; and a customized rollback strategy is generated according to the real-time feedback data, so that quick release of a project rollback version is facilitated, continuous operation of the project is facilitated, and the user experience is improved.

The invention relates to a method and a device for supporting multi-tenancy data and service customized running, which aim to improve the customizability of the whole software and makes transactional consistency higher. The device comprises a transaction processing unit, a basic service calling unit, an extended service calling unit and a calling result integration unit, wherein the transaction processing unit is used for the coordination of all transactions in a software-as-a-service (SaaS) engine, can ensure the integrity of a database and realize the rollback of changes in all failing transactions when failures or abnormity occurs in the whole transaction processing process, and simultaneously is required to record whether the calling of the basic service calling unit and the extended service calling unit succeeds or not; the basic service calling unit is used for organizing input parameters of basic services, and calling the basic services according to the parameters; the extendedservice calling unit is used for calling extended services; and the calling result integration unit is used for integrating calling results of the basic service calling unit and the extended service calling unit.

The embodiment of the invention provides a transaction processing method, a device and equipment. The method comprises the steps: a transaction request transmitted by terminal equipment of a first user is received; wherein the transaction request comprises transaction information of transaction between a first user and a second user, and related record information of the transaction is stored in blockchain; transaction elements associated with the transaction is determined according to the transaction information; locking processing on the determined transaction elements is carried out; and ifthe locking processing fails, transaction rollback processing is carried out and transaction failure information is sent to the terminal device of the first user.

A technique for transaction recovery by one transaction manager of another transaction manager's transactions in which each transaction manager is adapted to manage two phase commit transactional operations on transactional resources and to record commit or rollback decisions in a transaction recovery log. The recovery transaction manager detects apparent unavailability of the another transaction manager for transaction processing and initiates a transaction recovery process for the another transaction manager's transactions. This process also determines whether any of the transactions of the another transaction manager have all respective resources prepared to commit without there yet being a pending commit decision record in the another transaction manager's recovery log. If so, the recovery transaction manager writes a rollback record indicating an intention to roll back the identified transaction, in the another transaction manager's recovery log provided no commit decision record has been recorded.