Emc IP Holding Company LLC

Giantec Semiconductor, Ltd. Inc.

Hongru Xu

Tianfang Xiong

Yuanyang Wu

Yifeng Lu

Fei Long

Minghui Zhang

Qiu Shang

He Wang

Yue Qian

Ruisong Wang

Dan Shao

Qingshan Hao

Techniques manage application systems in an application environment. The application environment includes a first application system, a second application system and a third application system. First snapshot information of a first group of snapshots of the first application system is obtained, the first application system being in active state. Second snapshot information of a second group of snapshots of the second application system is obtained, the second application system being in standby state. It is determined whether the second application system and the third application system have a common snapshot based on the first snapshot information and the second snapshot information. Data is synchronized to the third application system depending on whether the second application system and the third application system have a common snapshot. Overheads required during data synchronization may be reduced as far as possible, and the efficiency of data synchronization may be improved.

Method, device, and computer program product for managing application system

Techniques perform data backup. Such techniques involve: in response to a first storage node to be switched to a second storage node, determining whether there is an ongoing data backup operation between the first storage node and a third storage node; and in response to the ongoing data backup operation between the first and third storage nodes, ceasing the data backup operation. The second storage node is used for backing up data of the first storage node in real time and the third storage node is used for backing up the data of the first storage node periodically. Accordingly, colliding operations can be prevented, system resource can be saved and processing efficiency can be improved.

Method, apparatus and computer program product for data replication

Techniques perform data synchronization. The techniques involve: in response to writing of data to a source storage array, determining whether a transmission link between the source storage array and a destination storage array is disconnected, the data being to be synchronized to the destination storage array; in response to determining that the transmission link is disconnected, accumulating in the source storage array the data written to the source storage array; in response to detecting that the transmission link is recovered, creating a snapshot for a storage unit associated with the data in the destination storage array; and in response to crashing of the source storage array during resynchronization of the data accumulated in the source storage array to the storage unit, restoring the storage unit in the destination storage array using the snapshot. Therefore, the storage space for the snapshot is greatly saved while disaster recovery is ensured.

Method, device and computer readable medium for data synchronization

Embodiments are directed to techniques for enforcing prerequisite conditions on a data object for an operational feature both upon initiation of that operational feature and while that operational feature is maintained. Accordingly, improved techniques enforce conditions by setting a flag associated with a data object upon confirming that the conditions have been met and checking the flag anytime a configuration change to the data object is requested that would cause the conditions to be violated. If the flag is set, any configuration change that would cause the conditions to be violated is rejected.

Using a flag to selectively permit configuration changes to a data storage object having an activated feature

Replication techniques may include creating a first file pool on a first site where storage for the first pool is provisioned from a first storage device group configured as a first consistency group; creating a second file pool on a second site where storage for the second file pool is provisioned from a second storage device group configured as a second consistency group; creating a first file system and its first snapshot in the first file pool of the first site, where creating the first file system and its first snapshot include performing first modifications to the first file pool; applying the first modifications to the first consistency group; and replicating the first modifications on the second file pool. Replicating may include applying the first modifications to the second consistency group to replicate the first file system and its first snapshot on the second site.

File system snapshot replication techniques

Replication techniques for file-based replication. A first file pool and a second pool may be created, respectively, on a first site and a second site. Storage for the first file pool may be provisioned from a first storage device group configured as a first consistency group. Storage for the second file pool may be provisioned from a second storage device group configured as a second consistency group. Modification operations, such as writes, may be applied to the first file pool. The modifications performed on the first file pool result in corresponding modifications to the first consistency group. The modifications may be replicated on the second file pool by applying the modifications to the second consistency group. File systems created in the first and second file pools may be self-contained and modifications applied to the first and second consistency groups may be applied in a specified order to ensure write consistency.

File-based replication techniques

A technique handles a VDM failover situation. The technique involves adjusting a configuration file on a first platform to indicate whether data managed by an initial VDM on that platform is being replicated to a second platform. The technique further involves, following a VDM failover event, creating a replacement VDM on the first platform to replace the initial VDM. The technique further involves, after the replacement VDM is created, performing an operation that controls interfaces provided by the replacement VDM. The operation enables the interfaces when the operation determines that the data managed by the initial VDM on the first platform was not being replicated to the second platform at the time of the event, and disables the interfaces when the operation determines that the data managed by the initial VDM on the first platform was being replicated to the second platform at that time of the event.

Handling a virtual data mover (VDM) failover situation by performing a network interface control operation that controls availability of network interfaces provided by a VDM

A serial memory device having a non-volatile memory array including a plurality of memory blocks, one or more said plurality of blocks being capable of being placed in a locked or an unlocked state upon receiving designated lock or unlock signal sequences is provided. The unlock signal sequences comprises at least two sequential signal sequences: a first unlock sequence, which has 1 to 7 signal bits, is applied to one of address input pins or a logic low enabled write-protection input pin and a second unlock sequence follows the first unlock signal sequence and is applied to a serial data access pin. The memory device further comprising a control logic circuit block coupled to a write-protection circuit block to provide means to identify the designated lock and unlock signal sequences and to set a protection state in a security area.

Growing community of inventors

Shanghai, China

Hongru Xu