WO2005069143A1 - Maintaining consistency for remote copy using virtualization - Google Patents
Maintaining consistency for remote copy using virtualization Download PDFInfo
- Publication number
- WO2005069143A1 WO2005069143A1 PCT/EP2005/050065 EP2005050065W WO2005069143A1 WO 2005069143 A1 WO2005069143 A1 WO 2005069143A1 EP 2005050065 W EP2005050065 W EP 2005050065W WO 2005069143 A1 WO2005069143 A1 WO 2005069143A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- unit
- processing unit
- links
- data updates
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/16—Protection against loss of memory contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
- G06F11/2071—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using a plurality of controllers
- G06F11/2074—Asynchronous techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
- G06F11/2064—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring while ensuring consistency
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99954—Version management
Definitions
- the present disclosure relates to a method, system, and an article of manufacture for maintaining consistency for asynchronous remote copy using virtualization Disclosure of Invention
- Information technology systems may need protection from site disasters or outages. Furthermore, information technology systems may require features for data migration, data backup, or data duplication. Implementations for disaster or outage recovery, data migration, data backup, and data duplication may include mirroring or copying of data in storage systems.
- data is copied from a primary storage control to a secondary storage control. In response to the primary storage control being unavailable, the secondary storage control may be used to substitute the unavailable primary storage control.
- Data copying in information technology systems may be synchronous or asynchronous. Synchronous copying involves sending data from the primary storage control to the secondary storage control and confirming the reception of such data before completing write operations to the primary storage control. Synchronous copy, therefore, slows the write operation response time while waiting for the confirmation from the secondary storage control. Synchronous copy, however, provides sequentially consistent data at the secondary storage control.
- Asynchronous copy may provides better performance than synchronous copy because the write operation to the primary storage control may be completed before the reception of sent data is confirmed from the secondary storage control.
- K wever data sequence consistency may have to be ensured since data received at the secondary storage control may not be in order of the updates, i.e., write operations, to the primary storag ⁇ control.
- cross-device consistency between the primary and the secondary storage control may be achieved by storing updates temporarily in a hardened location, such as a journal dataset, until a set of consistent updates is available to apply to the secondary storage associated with the secondary storage control.
- a first unit receives data updates from a second unit.
- the data updates are stored in a plurality of physical storage locations associated with the first unit. Links are generated to at least one of the plurality of physical storage locations to achieve consistent data between the first unit and the second unit.
- the first unit is a secondary storage control coupled to a secondary storage and the second unit is a primary storage control coupled to a primary storage, wherein the plurality of physical storage locations are associated with the secondary storage, and wherein the data updates are received asynchronously at the first unit.
- the received data is stored only once in the plurality of physical storage locations associated with the first unit, and unlinked physical storage locations are released to be used for storing subsequent data updates.
- an application sends input/output requests to the ⁇ Second unit, wherein the data updates correspond to output requestS'from the application, and wherein the data updates are stored only once at the first unit, wherein the first unit can substitute the second unit in responding to the input/output requests from the application at any point in time, and wherein data in the first and second units are consistent at all points in time.
- a waiting is performed to receive a next data update in response to the stored data updates not forming a consistency group.
- a data structure that maps virtual storage locations to the at least one of the plurality of physical storage locations is maintained, wherein the generated links are associated with the data structure, and wherein a plurality of ap- plications are capable of performing input/output operations with the virtual storage locations.
- data structures representing consistency groups corresponding to the data updates are maintained, wherein the maintained data structures are capable of pointing to the plurality of physical storage locations.
- a deletion is performed on a first data structure that represents a first consistency group in response to first data updates associated with the first consistency group being committed.
- an error is received, at the first unit, in response to waiting for a data update.
- the generated links are modified to reflect consistent data between the first unit and the second unit.
- Certain embodiments achieve consistency for asynchronous remote copy using a virtual storage system.
- a replication management application writes data that has been received but that is not yet consistent with data associated with other storage controls into unused physical storage.
- virtualization tables may be updated at the true secondary locations to point to locations in the physical storage where the data has been written.
- the received data at a secondary storage control may be written only once to the physical storage associated with the secondary storage control.
- FIG. 1 illustrates a block diagram of a computing environment, in accordance with certain described aspects of the invention
- FIG. 2 illustrates a block diagram of data structures and devices related to the computing environment, in accordance with certain described implementations of the invention
- FIG. 3 illustrates a block diagram of consistency groups, in accordance with certain described implementations of the invention.
- FIG. 4 illustrates logic for maintaining consistency using virtualization, in accordance with certain described implementations of the invention
- FIG. 5 illustrates a block diagram of a first state of data structures in an exemplary
- FIG. 6 illustrates a block diagram of a second state of data structures in an exemplary embodiment, in accordance with certain described implementations of the invention
- FIG. 7 illustrates a block diagram of a third state of data structures in an exemplary embodiment, in accordance with certain described implementations of the invention.
- FIG. 8 illustrates logic for logic for maintaining consistency and disaster recovery, in accordance with certain described implementations of the invention.
- FIG. 9 illustrates a block diagram of a computer architecture in which certain described aspects of the invention are implemented. Best Mode for Carrying Out the Invention
- FIG. 1 illustrates a block diagram of a computing environment, in accordance with certain aspects of the invention.
- a primary storage control 10O is coupled to a secondary storage control 102.
- An application system 104 that includes one or more applications may perform I/O operations, including write operations, to the primary storage control 100.
- the application system 104 may reside in a host computational device that is coupled to the primary storage control 100 via a host bus adapter.
- the primary storage control 100 and the secondary storage control 102 may store and retrieve data from a primary storage 106 and a secondary storage 108 respectively, where the primary storage 106 is coupled to the primary storage control 100 and the secondary storage 108 is coupled to the secondary storage control 102. Additionally, the primary storage control 100 and the secondary storage control 102 may control the operations of the primary storage 106 and the secondary storage 108 respectively.
- the primary storage 106 and the secondary storage 108 may include non- volatile storage, such as, hard disk drives, RAIDs, direct access storage devices, or other types of physical storage.
- the primary storage control 100 may not be operational and data associated with the secondary storage control 102 may be used by a recovery system 110 for processing.
- data associated with the secondary storage control 102 is maintained consistent with data associated with the primary storage control 100. The consistency is maintained by a replication management application 112.
- the replication management application 112 is coupled to the primary storage control 100 and the secondary storage control 102 and in certain embodiments may mirror data from the primary storage control 100 to the secondary storage control 102. In some embodiments, the mirroring may be performed by copying data asynchronously from the primary storage control 100 to the secondary storage control 102.
- the replication management application 112 may be spread across the primary storage control 100 and the secondary storage control 102. In other embodiments, the replication management application 112 may reside on a separate system that is different from the primary storage control 100 and the secondary storage control 102. In yet additional embodiments, the replication management application 112 may reside in only one of the primary storage control 100 and the secondary storage control 102.
- the replication management application 112 maintains consistency of data updates received from the application system 104, where the data updates are asynchronously copied to the secondary storage control 102 from the primary storage control 100.
- the replication management application 112 may perform a virtualization of the secondary storage 108 that is coupled to the secondary storage control 102 to maintain the consistency of data across the primary storage control 100 and the secondary storage control 102.
- virtualization includes the mapping of the physical secondary storage 108 to virtual volumes.
- FIG. 1 illustrates an embodiment where the replication management application 112 virtualizes the secondary storage control 102 and maintains con- sistencyof data across the primary storage control 100 and the secondary storage control 102, where data is copied asynchronously from the primary storage control 100 to the secondary storage control 102.
- FIG. 2 illustrates a block diagram of data structures and devices related to the replication management application 112 and the secondary storage control 102, in accordance with certain described implementations of the invention.
- the secondary storage control 102 may receive data updates 200 generated as a result of write operations from one or rrrjre applications 204a...204m to the primary storage control 100, where the one or more applications 204a...204m may comprise the application system 104.
- the data updates 200 from the application system 104 arrive asynchronously at the secondary storage control 102 via the primary storage control 100 and the data updates 200 may be referred to as a data update stream.
- the replication management application 112 creates one or more virtual devices, such as, virtual volumes 206a...206n associated with the secondary storage control 102.
- the primary storage control 100 may also have virtual volumes that correspond to the virtual volumes 206a...206n.
- the data corresponding to the virtual volumes 206a...206n are stored in locations in the physical secondary storage 108.
- the mapping of the virtual volumes 206a..206n to locations in the physical secondary storage 108 may be stored in virtualization tables 208 associated vith the secondary storage control 102.
- the virtualization tables 208 may be coupled to the virtual volumes 206a..206n.
- the application system 104 performs I/O operations with respect to virtual volumes associated with the primary storage control 100 and corresponding virtual volumes 206a...206n are also associated with the secondary storage control 102.
- the replication management application 112 may include a consistency group determination application 210, and associated data structxues corresponding to consistency groups 212.
- FIG. 2 describes an embodiment where the replication management application 112 virtualizes the secondary storage control 100 and maintains data consistency across the primary storage control 100 and the secondary storage control 102.
- FIG. 3 illustrates a block diagram of exemplary consistency groups created by the replication management application 112, in accordance with certain described implementations of the invention.
- a consistency group is a set of updates in which the updates may span a. plurality of storage volumes, and where the updates must be written together in order to maintain mutual data consistency between the data contained in each storage volume of the plurality of storage volumes.
- the following set of dependent write operations by the application system 104 may occur (where the second operation occurs after the first operation):
- volume B2 contains the data update of volume A2 whereas volume Bl does not contain the data update of volume Al .
- the set of volumes B 1 , B2 are in an inconsistent state with respect to the set of volumes Al, A2.
- An application 204a...204m that uses the volumes Bl, B2 associated with the secondary storage control 102 could not recover from a back-up copy stored in the volumes Bl, B2.
- the rows of table 300 represent different devices and the columns represent different times.
- the times are relative times and not absolute times.
- t3 reference numeral 306
- t2 reference numeral 304
- t2 reference numeral 304
- tl time after tl
- Bl (reference numeral 308)
- Bl is the first data update from an application named B, where the update is for the device D3 (reference numeral 310) that arrives at relative time tl (reference numeral 302).
- the different shadings in the entries of the table 300 identify a data-consistent set of updates, and may not necessarily be just vertical slices of entries in the table.
- the table 300 has three consistency groups 312, 314, 316.
- the update data in a consistency group may need to be applied together to the secondary control 102 for data associated with the secondary control 102 to remain consistent with data associated with the primary control 100.
- the determination of consistency groups 312, 314, 316 in the table 300 may be performed in any manner known in the art.
- FIG. 3 illustrates an embodiment of exemplary consistency groups 312, 314, 316 that may be generated by the replication management application 112 by processing the data update stream 200 that arrives asynchronously at the secondary storage control 102 from the primary storage control 100.
- a consistency group is determined and committed, and then the data updates of the consistency group are reflected via pointers or links in the virtual volumes 206a...206n of the secondary storage control 108.
- FIG. 4 illustrates logic for maintaining consistency using virtualization as implemented in the secondary storage control 102 in accordance with certain described implementations of the invention.
- Control starts at block 400, where the replication management application 112 creates virtualization tables 208 corresponding to the virtual volumes 206a...206n associated with the secondary storage control 102, where the virtualization tables 208 point to locations in the physical storage 108 and may define the consistent data contents of the virtual volumes 206a...206n.
- the consistency of the data contents of the virtual volumes 206a...206n is with respect to the data contents associated with the primary storage control 100.
- the replication management application 112 receives (at block 402) a data update 200 for a vrrtual volume 206a...206n associated with the secondary storage control 102.
- the data update 200 may be the data update Bl (reference numeral 308).
- the replication management application 112 writes (at block 404) the data update 200 into unused physical storage.
- the replication management application 112 may write the data update 200 into unused locations of the secondary storage 108.
- the replication manage ent application 112 determines (at block 406) if all data updates for a consistency group 212, such as, consistency groups 312, 314, 316 have been received. If so, the replication management application 112 updates (at block 408) the virtualization tables 208 to point to the locations in the physical storage 108 that define a commitment of the data updates included in the consistency group 212. The updated virtualization tables 208 define the new data associated with the virtual volumes 206a...206n. The data associated with the virtual volumes 206a...206n of the secondary storage control 102 is therefore consistent with data associated with the primary storage control 100.
- the replication management application 112 frees (at block 410) space in the physical storage 108 as a result of the updates to the virtualization tables 208. For example, certain data updates 200 written into the unused physical storage performed in block 404 may not be needed and may be freed.
- the replication management ap- plication 112 receives (at block 402) the next data update 200.
- the replication management application 112 determines (at block 406) that all data updates for a consistency group 212, such as, consistency groups 312, 314, 316, have not been received then the replication management application 112 receives (at block 402) the next data update 200.
- FIG. 4 describes certain embodiments in which the replication management application 112 writes all data updates 200 into locations in unused physical storage 108 and after determining a consistency group 212 may harden only a certain number of the written data updates by updating virtualization tables 208 to point to the certain nurrber of the written data updates. No copying of the written data updates is necessary.
- FIG. 5 illustrates a block diagram of a first state of data structures in an exemplary embodiment, in accordance with certain described implementations of the invention, where original data is associated with the secondary storage control 102 and data updates corresponding to first and second consistency groups have arrived at the secondary storage control 102 but have not been committed.
- FIG. 5 a linear representation of an exemplary disk 500, such as the physical storage 108 is shown.
- the exemplary disk 500 has ten physical blocks with the first physical block containing a first virtual block (VB) named VB1 that is part of the original data in the disk 500.
- VB virtual block
- CG consistency groups
- a data update 200 for the fourth virtual block (VB4) which is part of the second consistency group (CG2) is written in physical block five.
- the virtual blocks correspond to the virtual volumes 206a...206n.
- FIG. 5 also illustrates cu ⁇ ent data pointers 502 that point to the physical blocks of the original data in the disk 500, a first consistency group pointers 504 that point to the physical blocks corresponding the data updates comprising the first consistency group, and a second consistency group pointers 506 that point to the physical blocks corresponding to the data updates comprising the second consistency group.
- Tables representing the virtual block to physical block mapping of the pointers 502, 504, 506 are also maintained.
- current data pointer table 508 illustrates the current mapping of the virtual blocks to the physical blocks in the disk 500.
- the mapping in the current data pointer table 508 illustrates hardened or committed data, i.e., data that is consistent across the primary storage control 100 and the secondary storage control 102.
- the applications 204a...204n that access data associated with the secondary storage control 102 work with the data pointed to by the current data pointers 502.
- the first consistency group pointer table 510 illustrates the mapping of the virtual blocks to the physical blocks in the disk 500 for data updates that fo ⁇ n part of the first consistency group.
- the data represented in the first consistency group pointer table 510 is not hardened as the first consistency group has not been committed as yet.
- a second consistency group pointer table 512 illustrates the mapping of the virtual blocks to the physical blocks in the disk 500 for data updates that form part of the second consistency group.
- the data represented in the second consistency group pointer table 512 is not hardened as the second consistency group has not been committedas yet.
- FIG. 5 illustrates a first state of data structures in an embodiment where data updates 200 for the first and second consistency groups have arrived at the secondary storage control 102 but have not been committed.
- FIG. 6 illustrates a block diagram of a second state of data structures in an exemplary embodiment, in accordance with certain described implementations of the invention, where the data updates 200 corresponding to the first consistency group pointer table 510 have been hardened, i.e., the first consistency group has been committed, and uncommitted data updates 200 corresponding to a third consistency group have arrived at the secondary storage control 102.
- FIG. 6 illustrates the updated current data pointers 502 that point to the physical blocks of the original data in the disk 500, the second consistency group pointers 506 that point to the physical blocks corresponding the data updates comprising the uncommitted second consistency group, and a new third consistency group pointers 600 that point to the physical blocks corresponding to the uncommitted data updates comprising the third consistency group.
- Tables representing the virtual block to physical block mapping of the pointers 502, 506, 510 are also maintained.
- cu ⁇ ent data pointer table 508 illustrates the current mapping of the virtual blocks to the physical blocks in the disk 500.
- the mapping in the current data pointer table 508 illustrates hardened or committed data after the date updates 200 of the first consistency group have been committed.
- the third consistency group pointer table 602 illustrates the mapping of the virtual blocks to the physical blocks in the disk 500 for data updates that form part of the third consistency group.
- the data represented in the second consistency group pointer table 512 or the third consistency group pointer table 602 is not hardened as the second and third consistency groups have not been committed as yet.
- the first consistency group pointer table 510 has been deleted as the data updates for the first consistency group have been committed.
- FIG. 6 illustrates an embodiment where data updates 200 for the first, second and third consistency groups have arrived at the secondary storage control 102 and only the data updates of the first consistency group have been committed.
- FIG. 7 illustrates a block diagram of a third state of data structures in an exemplary embodiment, in accordance with certain described implementations of the invention.
- the data updates 200 corresponding to the second and third consistency groups have been committed.
- the first consistency group pointer table 510 Since the data updates of the first, second and third consistency groups have been committed the first consistency group pointer table 510, the second consistency group pointer table 512, and the third consistency group pointer table 602 are all shown to be deleted.
- the current data pointers point to physical block 5, 6, 8, 9 of the disk 500 and correspond to virtual block VB4, VB2, VB1, and VB3 respectively.
- FIG. 7 illustrates an embodiment where data updates 200 for the first, second and third consistency groups have a ⁇ ived at the secondary storage control 102 and all the data updates have been committed.
- FIG. 8 illustrates logic for logic for maintaining consistency and disaster recovery implemented in the replication management application 112, in accordance with certain described implementations of the invention.
- Control starts at block 800, where a current consistency group is initialized to one.
- the replication management application 112 determines (at block 802) whether all storage controls, i.e., the primary storage control 100 and the secondary storage control 102, have received the data updates of the current consistency group. If so, the replication management application 112 commits the data updates of the cu ⁇ ent consistency group and for all storage controls sets (at block 804) the current pointers to the current consistency group data updates.
- the current pointers may be implemented via data structures associated with the virtualization tables 208 and/or the pointer tables 508, 510, 512, 602.
- the replication management application 112 determines (at block 806) whether all pointers have been updated. If so, the replication management application deletes (at block 808) the current consistency group pointers.
- the replication management application 112 increments (at block 810) the current consistency group. For example, if in a first iteration of blocks 802 to 808 the data updates of the first consistency group are processed, then in the second iteration of blocks 802 to 808 the data updates of the second consistency group would be processed.
- the replication management application 112 waits (at block 812) for data updates of the current consistency group to arrive. If there is no error while waiting then control proceeds to block 802 where the replication management application 112 determines if all storage controls have received the data updates for the current consistency group.
- the replication management application 112 determines (at block 802) that all storage controls have not received the data updates of the current consistency group then the replication management application 112 waits (at block 812) for all the data updates of the current consistency group to arrive. If an error or disaster strikes while waiting (at block 812) the replication management application 112 determines (at block 814) the current consistency group on all storage controls and then determines (at block 816) the last available consistency group in each storage control. The replication management application 112 determines (at block 818) the maximum consistency group available on all storage controls and then updates (at block 820) pointers on all storage controls to correspond to the last available consistency group on all storage controls.
- the replication management application 112 begins performing (at block 824) a FOR loop for all the storage controls.
- the control for the FOR loop is executed (at block 824) for one storage control in every iteration. If the FOR loop is incomplete, i.e., not all storage controls have been processed, the replication management application 112 determines (at block 826) if the pointers correspond to the cu ⁇ ent consistency group for the storage control being processed. If so, then the replication management application 112 reverts (at block 828) the pointers to correspond to the previous consistency group and control proceeds (at block 824) to the next iteration of the FOR loop with the next storage control.
- the logic of FIG. 8 maintains the data on all storage controls consistent with each other and furthern ⁇ >re in the event of an error or disaster impacting a storage control while updating pointers or receiving data updates may revert the pointers in the storage controls to reflect the data updates associated with an earlier processed consistency group, such that data in the storage controls are consistent with each other.
- a replication management application writes data that has been received but that is not yet consistent with data in other storage subsystems into unused physical storage.
- pointers and tables may be updated at the true target locations to point to locations in the physical storage where the data has been written.
- the embodiments do not require a two phase commit at the secondary storage control to ensure data consistency.
- a two phase commit the data updates may be written into a journal dataset associated with the secondary storage control in a first phase and the appropriate data updates may copied in a second phase when the consistency group is committed.
- the embodiments are implemented without using a journal dataset.
- pointers are adjusted to point to appropriate locations in physical storage, such that the adjusted pointers represent a consistent data set across all storage controls.
- the embodiments may adjust the pointers in the storage controls to reflect the data updates associated with an earlier processed consistency group, such that the data in the storage controls are consistent with each other.
- the described techniques may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, f ⁇ nware, hardware, or any combination thereof.
- article of manufacture refers to code or logic implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate A ⁇ ay (PGA), Application Specific
- Integrated Circuit etc.
- a computer readable medium e.g., magnetic storage medium, such as hard disk drives, floppy disks, tape), optical storage (e.g., CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.).
- Code in the computer readable medium is accessed and executed by a processor.
- the code in which implementations are made may further be accessible through a transmission media or from a file server over a network.
- the article of manufacture in which the co e is implemented may comprise a transmission media, such as a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc.
- a transmission media such as a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc.
- FIG. 9 illustrates a block diagram of a computer architecture in which certain aspects of the invention are implemented.
- FIG. 9 illustrates one implementation of the storage controls 100, 102, a host that includes the application system 104, and any computational device that includes the replication management application 112.
- the storage controls 100, 102, the host that includes the application system 104, and any computational device that includes the replication management application 112 may implement a computer architecture 900 having a processor 902, a memory 904 (e.g., a volatile memory device), and storage 906 (e.g., a non-volatile storage, magnetic disk drives, optical disk drives, tape drives, etc.).
- the storage 906 may comprise an internal storage device, an attached storage device or a network accessible storage device.
- Programs in the storage 906 may be loaded into the memory 904 and executed by the processor 902 in a manner known in the art.
- the architecture may further include a network card 908 to enable communication with a network.
- the architecture may also include at least one input device 910, such as a keyboard, a touchscreen, a pen, voice- activated input, etc., and at least one output device 912, such as, a display device, a speaker, a printer, etc. 30
- FIGs. 4 - 8 describe specific operations occurring in a particular order. Further, the operations may be performed in parallel as well as sequentially. In alternative implementations, certain of the logic operations may be performed in a different order, modified or removed and still implement implementations of the present invention. Moreover, steps may be added to the above described logic and still conform to the implementations. Yet further steps may be performed by a single process or distributed processes.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05701462A EP1706822B1 (en) | 2004-01-09 | 2005-01-07 | Maintaining consistency for remote copy using virtualization |
DE602005000819T DE602005000819T2 (en) | 2004-01-09 | 2005-01-07 | Maintaining the Consistency of a Remote Copy Using Virtualization |
JP2006548309A JP4644684B2 (en) | 2004-01-09 | 2005-01-07 | Maintaining consistency of remote copy using virtualization (method and system for copying storage) |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/754,231 US7478211B2 (en) | 2004-01-09 | 2004-01-09 | Maintaining consistency for remote copy using virtualization |
US10/754,231 | 2004-01-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005069143A1 true WO2005069143A1 (en) | 2005-07-28 |
Family
ID=34739337
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2005/050065 WO2005069143A1 (en) | 2004-01-09 | 2005-01-07 | Maintaining consistency for remote copy using virtualization |
Country Status (9)
Country | Link |
---|---|
US (2) | US7478211B2 (en) |
EP (1) | EP1706822B1 (en) |
JP (1) | JP4644684B2 (en) |
KR (1) | KR100961739B1 (en) |
CN (1) | CN100422949C (en) |
AT (1) | ATE358848T1 (en) |
DE (1) | DE602005000819T2 (en) |
TW (1) | TWI339793B (en) |
WO (1) | WO2005069143A1 (en) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005309550A (en) | 2004-04-19 | 2005-11-04 | Hitachi Ltd | Remote copying method and system |
US20050154786A1 (en) * | 2004-01-09 | 2005-07-14 | International Business Machines Corporation | Ordering updates in remote copying of data |
US7657717B1 (en) * | 2004-02-02 | 2010-02-02 | Symantec Operating Corporation | Coherently sharing any form of instant snapshots separately from base volumes |
JP4512386B2 (en) | 2004-03-05 | 2010-07-28 | 株式会社日立製作所 | Backup system and method |
US7765187B2 (en) * | 2005-11-29 | 2010-07-27 | Emc Corporation | Replication of a consistency group of data storage objects from servers in a data network |
GB0616257D0 (en) * | 2006-08-16 | 2006-09-27 | Ibm | Storage management system for preserving consistency of remote copy data |
JP5073348B2 (en) * | 2007-04-04 | 2012-11-14 | 株式会社日立製作所 | Application management support system, management computer, host computer, and application management support method |
US20100153612A1 (en) * | 2008-12-15 | 2010-06-17 | Lsi Corporation | Transport agnostic scsi i/o referrals |
US8893147B2 (en) | 2012-01-13 | 2014-11-18 | Ca, Inc. | Providing a virtualized replication and high availability environment including a replication and high availability engine |
US9430343B1 (en) * | 2012-05-07 | 2016-08-30 | Emc Corporation | Using affinity to mediate bias in a distributed storage system |
US9367394B2 (en) * | 2012-12-07 | 2016-06-14 | Netapp, Inc. | Decoupled reliability groups |
US20160217175A1 (en) * | 2015-01-23 | 2016-07-28 | Netapp, Inc. | Techniques for asynchronous snapshot invalidation |
US10191672B2 (en) | 2015-10-16 | 2019-01-29 | Google Llc | Asynchronous copying of data within memory |
CN109150986A (en) * | 2018-07-27 | 2019-01-04 | 郑州云海信息技术有限公司 | Store access method, device and the storage medium of data under dual-active mode |
US11836130B2 (en) * | 2019-10-10 | 2023-12-05 | Unisys Corporation | Relational database blockchain accountability |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5193184A (en) * | 1990-06-18 | 1993-03-09 | Storage Technology Corporation | Deleted data file space release system for a dynamically mapped virtual data storage subsystem |
EP0674263A1 (en) * | 1994-03-21 | 1995-09-27 | International Business Machines Corporation | Asynchronous remote data copying |
US5555371A (en) * | 1992-12-17 | 1996-09-10 | International Business Machines Corporation | Data backup copying with delayed directory updating and reduced numbers of DASD accesses at a back up site using a log structured array data storage |
EP1349088A2 (en) * | 2002-03-19 | 2003-10-01 | Network Appliance, Inc. | System and method for determining and transmitting changes in snapshots |
Family Cites Families (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US178335A (en) * | 1876-06-06 | Improvement in jack-spools | ||
US178162A (en) * | 1876-05-30 | Improvement in wrenches | ||
US519184A (en) * | 1894-05-01 | Brook | ||
US120763A (en) * | 1871-11-07 | Improvement in ferrules | ||
US87780A (en) * | 1869-03-16 | Improvement in bolt-heading dies | ||
US4853843A (en) | 1987-12-18 | 1989-08-01 | Tektronix, Inc. | System for merging virtual partitions of a distributed database |
US5893117A (en) | 1990-08-17 | 1999-04-06 | Texas Instruments Incorporated | Time-stamped database transaction and version management system |
US5544347A (en) * | 1990-09-24 | 1996-08-06 | Emc Corporation | Data storage system controlled remote data mirroring with respectively maintained data indices |
US5701480A (en) | 1991-10-17 | 1997-12-23 | Digital Equipment Corporation | Distributed multi-version commitment ordering protocols for guaranteeing serializability during transaction processing |
US5504899A (en) | 1991-10-17 | 1996-04-02 | Digital Equipment Corporation | Guaranteeing global serializability by applying commitment ordering selectively to global transactions |
CA2285096C (en) | 1991-11-12 | 2000-05-09 | Ibm Canada Limited-Ibm Canada Limitee | Logical mapping of data objects using data spaces |
US5499367A (en) | 1991-11-15 | 1996-03-12 | Oracle Corporation | System for database integrity with multiple logs assigned to client subsets |
JPH0619785A (en) | 1992-03-27 | 1994-01-28 | Matsushita Electric Ind Co Ltd | Distributed shared virtual memory and its constitution method |
US5446871A (en) | 1993-03-23 | 1995-08-29 | International Business Machines Corporation | Method and arrangement for multi-system remote data duplexing and recovery |
KR0128271B1 (en) | 1994-02-22 | 1998-04-15 | 윌리암 티. 엘리스 | Remote data duplexing |
US5592618A (en) | 1994-10-03 | 1997-01-07 | International Business Machines Corporation | Remote copy secondary data copy validation-audit function |
US5850522A (en) | 1995-02-03 | 1998-12-15 | Dex Information Systems, Inc. | System for physical storage architecture providing simultaneous access to common file by storing update data in update partitions and merging desired updates into common partition |
US5682513A (en) | 1995-03-31 | 1997-10-28 | International Business Machines Corporation | Cache queue entry linking for DASD record updates |
US5787476A (en) | 1995-05-05 | 1998-07-28 | Silicon Graphics, Inc. | System and method for maintaining coherency of virtual-to-physical memory translations in a multiprocessor computer |
US5895499A (en) | 1995-07-03 | 1999-04-20 | Sun Microsystems, Inc. | Cross-domain data transfer using deferred page remapping |
US5765171A (en) | 1995-12-29 | 1998-06-09 | Lucent Technologies Inc. | Maintaining consistency of database replicas |
US5806074A (en) | 1996-03-19 | 1998-09-08 | Oracle Corporation | Configurable conflict resolution in a computer implemented distributed database |
US5852715A (en) * | 1996-03-19 | 1998-12-22 | Emc Corporation | System for currently updating database by one host and reading the database by different host for the purpose of implementing decision support functions |
US6438586B1 (en) | 1996-09-30 | 2002-08-20 | Emc Corporation | File transfer utility which employs an intermediate data storage system |
US5896492A (en) * | 1996-10-28 | 1999-04-20 | Sun Microsystems, Inc. | Maintaining data coherency between a primary memory controller and a backup memory controller |
US6067550A (en) | 1997-03-10 | 2000-05-23 | Microsoft Corporation | Database computer system with application recovery and dependency handling write cache |
US6490594B1 (en) | 1997-04-04 | 2002-12-03 | Microsoft Corporation | Database computer system with application recovery and dependency handling write cache |
US6032216A (en) | 1997-07-11 | 2000-02-29 | International Business Machines Corporation | Parallel file system with method using tokens for locking modes |
US5924096A (en) | 1997-10-15 | 1999-07-13 | Novell, Inc. | Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand |
US5999931A (en) | 1997-10-17 | 1999-12-07 | Lucent Technologies Inc. | Concurrency control protocols for management of replicated data items in a distributed database system |
US6105078A (en) | 1997-12-18 | 2000-08-15 | International Business Machines Corporation | Extended remote copying system for reporting both active and idle conditions wherein the idle condition indicates no updates to the system for a predetermined time period |
US6085200A (en) | 1997-12-23 | 2000-07-04 | Unisys Corporation | System and method for arranging database restoration data for efficient data recovery in transaction processing systems |
US6131148A (en) | 1998-01-26 | 2000-10-10 | International Business Machines Corporation | Snapshot copy of a secondary volume of a PPRC pair |
US6324654B1 (en) | 1998-03-30 | 2001-11-27 | Legato Systems, Inc. | Computer network remote data mirroring system |
US6157991A (en) * | 1998-04-01 | 2000-12-05 | Emc Corporation | Method and apparatus for asynchronously updating a mirror of a source device |
US6161191A (en) * | 1998-05-12 | 2000-12-12 | Sun Microsystems, Inc. | Mechanism for reliable update of virtual disk device mappings without corrupting data |
US6185663B1 (en) | 1998-06-15 | 2001-02-06 | Compaq Computer Corporation | Computer method and apparatus for file system block allocation with multiple redo |
US6260120B1 (en) | 1998-06-29 | 2001-07-10 | Emc Corporation | Storage mapping and partitioning among multiple host processors in the presence of login state changes and host controller replacement |
US6148383A (en) | 1998-07-09 | 2000-11-14 | International Business Machines Corporation | Storage system employing universal timer for peer-to-peer asynchronous maintenance of consistent mirrored storage |
US6321276B1 (en) | 1998-08-04 | 2001-11-20 | Microsoft Corporation | Recoverable methods and systems for processing input/output requests including virtual memory addresses |
US6269382B1 (en) | 1998-08-31 | 2001-07-31 | Microsoft Corporation | Systems and methods for migration and recall of data from local and remote storage |
US6301643B1 (en) | 1998-09-03 | 2001-10-09 | International Business Machines Corporation | Multi-environment data consistency |
US6611901B1 (en) | 1999-07-02 | 2003-08-26 | International Business Machines Corporation | Method, system, and program for maintaining electronic data as of a point-in-time |
US6539462B1 (en) | 1999-07-12 | 2003-03-25 | Hitachi Data Systems Corporation | Remote data copy using a prospective suspend command |
US6513051B1 (en) * | 1999-07-16 | 2003-01-28 | Microsoft Corporation | Method and system for backing up and restoring files stored in a single instance store |
US6671705B1 (en) * | 1999-08-17 | 2003-12-30 | Emc Corporation | Remote mirroring system, device, and method |
US6463501B1 (en) | 1999-10-21 | 2002-10-08 | International Business Machines Corporation | Method, system and program for maintaining data consistency among updates across groups of storage areas using update times |
US6438558B1 (en) | 1999-12-23 | 2002-08-20 | Ncr Corporation | Replicating updates in original temporal order in parallel processing database systems |
US6493727B1 (en) | 2000-02-07 | 2002-12-10 | Hewlett-Packard Company | System and method for synchronizing database in a primary device and a secondary device that are derived from a common database |
US6487645B1 (en) | 2000-03-06 | 2002-11-26 | International Business Machines Corporation | Data storage subsystem with fairness-driven update blocking |
US6532527B2 (en) | 2000-06-19 | 2003-03-11 | Storage Technology Corporation | Using current recovery mechanisms to implement dynamic mapping operations |
US6804755B2 (en) | 2000-06-19 | 2004-10-12 | Storage Technology Corporation | Apparatus and method for performing an instant copy of data based on a dynamically changeable virtual mapping scheme |
US6925528B2 (en) | 2000-06-20 | 2005-08-02 | Storage Technology Corporation | Floating virtualization layers |
JP2002116939A (en) * | 2000-10-06 | 2002-04-19 | Telecommunication Advancement Organization Of Japan | Distributed database system |
US7475199B1 (en) | 2000-10-19 | 2009-01-06 | Emc Corporation | Scalable network file system |
JP2002132568A (en) * | 2000-10-30 | 2002-05-10 | Nec Corp | System and method for client control |
US7562110B2 (en) | 2001-01-11 | 2009-07-14 | F5 Networks, Inc. | File switch and switched file system |
US20020174295A1 (en) | 2001-01-29 | 2002-11-21 | Ulrich Thomas R. | Enhanced file system failure tolerance |
US7305421B2 (en) | 2001-07-16 | 2007-12-04 | Sap Ag | Parallelized redo-only logging and recovery for highly available main memory database systems |
KR100453228B1 (en) * | 2002-03-21 | 2004-10-15 | 한국전자통신연구원 | Journaling and recovery method for shared disk file system |
US6898609B2 (en) * | 2002-05-10 | 2005-05-24 | Douglas W. Kerwin | Database scattering system |
JP2003330780A (en) * | 2002-05-14 | 2003-11-21 | Ricoh Co Ltd | Document management program and recording medium |
US7266587B2 (en) * | 2002-05-15 | 2007-09-04 | Broadcom Corporation | System having interfaces, switch, and memory bridge for CC-NUMA operation |
US7739240B2 (en) | 2002-12-09 | 2010-06-15 | Hewlett-Packard Development Company, L.P. | Replication and replica management in a wide area file system |
US6899685B2 (en) * | 2003-01-24 | 2005-05-31 | Acueity, Inc. | Biopsy device |
US6898685B2 (en) | 2003-03-25 | 2005-05-24 | Emc Corporation | Ordering data writes from a local storage device to a remote storage device |
US7051176B2 (en) | 2003-03-25 | 2006-05-23 | Emc Corporation | Reading data provided to a remote storage device |
US7111136B2 (en) | 2003-06-26 | 2006-09-19 | Hitachi, Ltd. | Method and apparatus for backup and recovery system using storage based journaling |
US7278049B2 (en) * | 2003-09-29 | 2007-10-02 | International Business Machines Corporation | Method, system, and program for recovery from a failure in an asynchronous data copying system |
US7143122B2 (en) * | 2003-10-28 | 2006-11-28 | Pillar Data Systems, Inc. | Data replication in data storage systems |
US7228456B2 (en) | 2003-12-01 | 2007-06-05 | Emc Corporation | Data recovery for virtual ordered writes for multiple storage devices |
US7155586B1 (en) | 2003-12-30 | 2006-12-26 | Emc Corporation | Method of allowing point-in-time view of data on a disk using a map on cache disk |
US20050154786A1 (en) | 2004-01-09 | 2005-07-14 | International Business Machines Corporation | Ordering updates in remote copying of data |
-
2004
- 2004-01-09 US US10/754,231 patent/US7478211B2/en not_active Expired - Fee Related
- 2004-11-12 TW TW093134680A patent/TWI339793B/en not_active IP Right Cessation
-
2005
- 2005-01-07 WO PCT/EP2005/050065 patent/WO2005069143A1/en active IP Right Grant
- 2005-01-07 AT AT05701462T patent/ATE358848T1/en not_active IP Right Cessation
- 2005-01-07 JP JP2006548309A patent/JP4644684B2/en not_active Expired - Fee Related
- 2005-01-07 EP EP05701462A patent/EP1706822B1/en active Active
- 2005-01-07 CN CNB200580001870XA patent/CN100422949C/en not_active Expired - Fee Related
- 2005-01-07 KR KR1020067013767A patent/KR100961739B1/en active IP Right Grant
- 2005-01-07 DE DE602005000819T patent/DE602005000819T2/en active Active
-
2008
- 2008-11-06 US US12/266,408 patent/US7660958B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5193184A (en) * | 1990-06-18 | 1993-03-09 | Storage Technology Corporation | Deleted data file space release system for a dynamically mapped virtual data storage subsystem |
US5555371A (en) * | 1992-12-17 | 1996-09-10 | International Business Machines Corporation | Data backup copying with delayed directory updating and reduced numbers of DASD accesses at a back up site using a log structured array data storage |
EP0674263A1 (en) * | 1994-03-21 | 1995-09-27 | International Business Machines Corporation | Asynchronous remote data copying |
EP1349088A2 (en) * | 2002-03-19 | 2003-10-01 | Network Appliance, Inc. | System and method for determining and transmitting changes in snapshots |
Also Published As
Publication number | Publication date |
---|---|
JP2007518174A (en) | 2007-07-05 |
KR100961739B1 (en) | 2010-06-07 |
US20050154845A1 (en) | 2005-07-14 |
EP1706822B1 (en) | 2007-04-04 |
US7660958B2 (en) | 2010-02-09 |
DE602005000819D1 (en) | 2007-05-16 |
KR20060123460A (en) | 2006-12-01 |
US20090055610A1 (en) | 2009-02-26 |
CN1906594A (en) | 2007-01-31 |
TWI339793B (en) | 2011-04-01 |
EP1706822A1 (en) | 2006-10-04 |
CN100422949C (en) | 2008-10-01 |
US7478211B2 (en) | 2009-01-13 |
JP4644684B2 (en) | 2011-03-02 |
DE602005000819T2 (en) | 2008-01-10 |
TW200532444A (en) | 2005-10-01 |
ATE358848T1 (en) | 2007-04-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1706822B1 (en) | Maintaining consistency for remote copy using virtualization | |
US7870353B2 (en) | Copying storage units and related metadata to storage | |
US7406487B1 (en) | Method and system for performing periodic replication using a log | |
US7308545B1 (en) | Method and system of providing replication | |
US7191299B1 (en) | Method and system of providing periodic replication | |
CA2933790C (en) | Apparatus and method for creating a real time database replica | |
US7930271B2 (en) | Method and apparatus for data processing | |
US7836266B2 (en) | Managing snapshot history in a data storage system | |
US6820180B2 (en) | Apparatus and method of cascading backup logical volume mirrors | |
KR100926880B1 (en) | Data replication method and system in DVMS | |
CN101361047B (en) | Method and system for data protection in storage systems | |
US7133982B2 (en) | Method, system, and article of manufacture for consistent copying of storage volumes | |
CN106021016A (en) | Virtual point in time access between snapshots | |
EP2521037A2 (en) | Geographically distributed clusters | |
US10747465B2 (en) | Preserving replication to a storage object on a storage node | |
US11579983B2 (en) | Snapshot performance optimizations | |
US20050154786A1 (en) | Ordering updates in remote copying of data | |
WO2007099636A1 (en) | File system migration method, program and apparatus | |
US8327095B2 (en) | Maintaining information of a relationship of target volumes comprising logical copies of a source volume | |
US7318168B2 (en) | Bit map write logging with write order preservation in support asynchronous update of secondary storage | |
US20030191917A1 (en) | Apparatus and method of maintaining reliable offline mirror copies in virtual volume groups | |
US11301341B2 (en) | Replication system takeover with handshake | |
JP2006040065A (en) | Device and method for storing data | |
US10635542B1 (en) | Support for prompt creation of target-less snapshots on a target logical device that has been linked to a target-less snapshot of a source logical device | |
EP1854012B1 (en) | Checkpoint and consistency markers |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200580001870.X Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006548309 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020067013767 Country of ref document: KR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2898/CHENP/2006 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005701462 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2005701462 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1020067013767 Country of ref document: KR |
|
WWG | Wipo information: grant in national office |
Ref document number: 2005701462 Country of ref document: EP |