[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

EP2254036B1 - Appareil de stockage et procédé de copie de données - Google Patents

Appareil de stockage et procédé de copie de données Download PDF

Info

Publication number
EP2254036B1
EP2254036B1 EP10162571.3A EP10162571A EP2254036B1 EP 2254036 B1 EP2254036 B1 EP 2254036B1 EP 10162571 A EP10162571 A EP 10162571A EP 2254036 B1 EP2254036 B1 EP 2254036B1
Authority
EP
European Patent Office
Prior art keywords
copy
volume
area
data
copy destination
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP10162571.3A
Other languages
German (de)
English (en)
Other versions
EP2254036A3 (fr
EP2254036A2 (fr
Inventor
Akihiro Ueda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to EP12191700.9A priority Critical patent/EP2557494B1/fr
Publication of EP2254036A2 publication Critical patent/EP2254036A2/fr
Publication of EP2254036A3 publication Critical patent/EP2254036A3/fr
Application granted granted Critical
Publication of EP2254036B1 publication Critical patent/EP2254036B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662—Virtualisation aspects
    • G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • 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/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup 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/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1456—Hardware arrangements for backup
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • G06F3/0613—Improving I/O performance in relation to throughput
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/065—Replication mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Definitions

  • the embodiments discussed herein are related to a storage apparatus and a data copy method.
  • a technique for virtually allocating a physical resource such as a disk has received attention in recent years.
  • the demanded amount of storage use is provided as a virtual volume by preparing only a physical disk capacity corresponding to the actual amount of storage use without preparing a physical disk capacity corresponding to the demanded amount of storage use.
  • a Thin Provisioning volume is a variable allocation virtual volume to which a physical area (storage area) is variably allocated in accordance with a usage pattern. With such a Thin Provisioning volume, it is possible to establish a virtual volume having a capacity larger than the prepared physical disk capacity.
  • Japanese Laid-open Patent Publications No. 2008-130080 , No. 2008-181271 , No. 2003-256148 , and No. 02-093721 are examples of related art.
  • Examples of the above-described advanced copy function include a remote advanced copy function of typically backing up the volume of a copy source storage unit to the volume of a copy destination storage unit disposed far from the copy source storage unit.
  • the remote advanced copy function when copying processing for copying data from a copy source to a copy destination starts, initial copying processing for sequentially transferring pieces of data in the copy range of the copy source to the copy destination in predetermined units is performed.
  • variable allocation virtual volume such as a Thin Provisioning volume
  • zero data is allocated to an area having no real data as dummy information. This means that zero is read from the area when data is read from the area by a server. Accordingly, when the area having no real data is subjected to copying in the above-described remote advanced copy function, as illustrated in FIG. 1 , the zero data that is dummy information is remotely transferred from the area. As a result, a large amount of data is transferred.
  • FIG. 1 a variable allocation virtual volume
  • allocated represents a state in which a physical area (storage area) has already been allocated to a target virtual area (virtual block) in a virtual volume
  • unallocated represents a state in which a physical area (storage area) is not allocated to a target virtual area (virtual block) in a virtual volume.
  • Embodiments of aspects of the invention provide storage apparatuses and methods for copying data, as defined in the claims.
  • the claims define the scope of the
  • FIG. 2 illustrates the configuration of a storage system according to an embodiment.
  • like reference numerals designate identical or corresponding components.
  • a storage system 10 includes a business server 11, a maintenance server 12, a Fibre Channel-Storage Area Network (FC-SAN) 13, a copy source unit 20, a copy destination unit 30, and a line 40.
  • the copy source unit 20 provides a business volume 50 that is a copy source virtual volume.
  • the copy destination unit 30 provides a backup volume 60 that is a copy destination virtual volume.
  • FC-SAN Fibre Channel-Storage Area Network
  • the business server 11 accesses the business volume 50 of the copy source unit 20 via the FC-SAN 13 and performs various processing operations upon pieces of data stored in the business volume 50.
  • the maintenance server 12 copies the pieces of data stored in the business volume 50 to the backup volume 60 of the copy destination unit 30 using dedicated software.
  • the copying processing can be performed with the above-described remote advanced copy function, etc.
  • the remote advanced copy function will be described.
  • the maintenance server 12 may use ETERNUS SF AdvancedCopy Manager or ETERNUS VSS Hardware Provider sold by FUJITSU LIMITED as the dedicated software.
  • the maintenance server 12 is disposed independently of the business server 11, but the business server 11 and the maintenance server 12 may be integrated.
  • the FC-SAN 13 is a storage area network achieved by Fibre Channel that is a high-speed serial interface, and connects the business server 11, the maintenance server 12, and the copy source unit 20 to one another.
  • the business server 11, the maintenance server 12, and the copy source unit 20 may be connected to one another by another appropriate network or bus instead of the FC-SAN 13.
  • the copy source unit 20 stores pieces of data including business data upon which the business server 11 performs various processing operations, and provides the business volume 50.
  • the copy source unit 20 includes a controller module 21, a cache memory 22, FC ports 14, 23, and 25, and disks 241 to 244.
  • the controller module 21 is typically achieved by a processor, and controls various components included in the copy source unit 20 by executing programs stored in the cache memory 22. In another embodiment, the controller module 21 may be achieved by another piece of hardware such as a logic circuit for controlling various components included in the copy source unit 20.
  • the cache memory 22 is connected to the controller module 21, and stores a program for controlling the operation of the controller module 21. Furthermore, the cache memory 22 may be used as a work memory for temporarily storing data used for various processing operations performed by the controller module 21.
  • FC ports 14, 23, and 25 function as interfaces for the FC-SAN 13, the disks 241 to 244, and the line 40, respectively. Instead of the FC ports 14, 23, and 25, other appropriate interfaces used for connections to the FC-SAN 13, the disks (storage units) 241 to 244, and the line 40 may be used.
  • the disks 241 to 244 are the same type of disks or different types of disks capable of storing data, and function as a storage apparatus for the copy source unit 20 with Redundant Arrays of Inexpensive Disks (RAID).
  • RAID Redundant Arrays of Inexpensive Disks
  • FIG. 2 four disks, the disks 241 to 244, are illustrated. However, any number of disks may be used.
  • the copy destination unit 30 is typically disposed far from the copy source unit 20, and is connected to the copy source unit 20 via the line 40.
  • the copy destination unit 30 receives data stored in the business volume 50 from the copy source unit 20 via the line 40 and an FC port 31 and stores the received data.
  • the copy destination unit 30 provides the backup volume 60 that is made equivalent to the business volume 50 by the remote advanced copy function.
  • the copy destination unit 30 includes the controller module 21, the cache memory 22, the FC ports 14, 23, and 25, and the disks 241 to 244. The description and illustration thereof will be omitted for simplification of explanation.
  • the line 40 may be any appropriate communication line capable of connecting the copy source unit 20 and the copy destination unit 30 to each other. It is desirable that the line 40 be a line with a high bandwidth. In this case, however, the cost of installation and maintenance of the line 40 is high.
  • the business volume 50 provided by the copy source unit 20 may be a variable allocation virtual volume such as a Thin Provisioning volume to which a physical area (storage area) is variably allocated in accordance with a usage pattern or may be a current (or normal) volume that is not a variable allocation virtual volume.
  • the business volume 50 is a logic volume defined by RAID which is composed of the disks 241 to 244.
  • the current volume has a storage capacity independent of actual amount of data stored in the current volume.
  • the backup volume 60 provided by the copy destination unit 30 may be a variable allocation virtual volume such as a Thin Provisioning volume or may be a current or normal volume that is not a variable allocation virtual volume.
  • the business volume 60 is a logic volume composed of the disks 241 to 244.
  • a remote advanced copy function that can be applied to a variable allocation virtual volume according to an embodiment includes remote advanced copy start processing to be described later and data transmission/receiving processing to be described later.
  • FIG. 3 illustrates remote advanced copy start processing according to an embodiment.
  • a server In Thin Provisioning, it is impossible for a server to determine whether a copy source volume and a copy destination volume are Thin Provisioning virtual volumes or normal or current volumes that are not Thin Provisioning virtual volumes, that is, determine the volume types of a copy source and a copy destination. Accordingly, the copy source unit 20 that has received a remote advanced copy function start instruction from the maintenance server 12 cannot determine the volume type of the backup volume 60 of the copy destination unit 30 on the basis of information received from the maintenance server 12.
  • the controller module 21 included in the copy source unit 20 upon receiving a remote advanced copy function start instruction from the maintenance server 12, the controller module 21 included in the copy source unit 20 communicates with the controller module 21 included in the copy destination unit 30 before performing data transfer processing so as to transmit and receive a volume type to and from the copy destination unit 30.
  • the controller module 21 included in the copy source unit 20 can specify and store the volume type of the copy destination unit 30, and the controller module 21 included in the copy destination unit 30 can specify and store the volume type of the copy source unit 20.
  • FIG. 4 illustrates data transfer patterns used in data transmission/receiving processing according to an embodiment.
  • the controller module 21 included in the copy source unit 20 specifies and stores the volume type of the copy destination unit 30 before performing data transfer processing.
  • the controller module 21 included in the copy source unit 20 compresses zero data by specifying the initial address and block length of an allocation area and transfers the compressed zero data to the copy destination unit 30.
  • the controller module 21 included in the copy source unit 20 transfers real data stored in the business volume 50 of the copy source unit 20 to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 analyzes the data received from the copy source unit 20 so as to determine whether the received data is real data or compressed data.
  • the controller module 21 included in the copy destination unit 30 copies the received real data to the copy destination area.
  • the controller module 21 included in the copy destination unit 30 allocates a physical area to the copy destination area and then copies the received real data to the copy destination area.
  • the controller module 21 included in the copy destination unit 30 deallocates the physical area allocated to the copy destination area or copies zero data to the copy destination area.
  • the controller module 21 included in the copy destination unit 30 ends the data copying processing without processing the copy destination area.
  • Each of the illustrated data transfer patterns is formed on the basis of the combination of some conditions.
  • One of these conditions is the types (a Thin Provisioning volume or a current volume that is not a Thin Provisioning volume) of the business volume 50 of the copy source unit 20 and the backup volume 60 of the copy destination unit 30.
  • the other one of these conditions is the physical area allocation state of a copy target area of each of the volumes 50 and 60 when the business volume 50 of the copy source unit 20 and the backup volume 60 of the copy destination unit 30 are Thin Provisioning volumes.
  • copying processing is performed on the basis of these conditions.
  • a case (i) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area is not allocated to the business volume 50, a case (ii) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area has already been allocated to the business volume 50, and a case (iii) in which the business volume 50 of the copy source unit 20 is a current volume are illustrated.
  • one of these cases (i) to (iii) regarding the business volume 50 of the copy source unit 20 is associated with one of a case (a) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area is not allocated to the backup volume 60, a case (b) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area has already been allocated to the backup volume 60, and a case (c) in which the backup volume 60 of the copy destination unit 30 is a current volume.
  • the case (i) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area is not allocated to the business volume 50 is associated with the case (a) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area is not allocated to the backup volume 60.
  • the controller module 21 included in the copy source unit 20 compresses zero data that is dummy information. That is, the controller module 21 generates data representing that the physical area is not allocated to the business volume 50. Then the controller module 21 transfers the compressed zero data representing that the physical area is not allocated to the business volume 50 to the copy destination unit 30. Upon receiving the compressed zero data, as described previously, the controller module 21 included in the copy destination unit 30 ends the data copying processing without processing a copy destination area in the backup volume 60 of the copy destination unit 30.
  • the case (i) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area is not allocated to the business volume 50 is associated with the case (b) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area has already been allocated to the backup volume 60.
  • the controller module 21 included in the copy source unit 20 compresses zero data that is dummy information. That is, the controller module 21 generates data representing that the physical area is not allocated to the business volume 50. Then the controller module 21 transfers the compressed zero data representing that the physical area is not allocated to the business volume 50 to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 Upon receiving the compressed zero data, as described previously, the controller module 21 included in the copy destination unit 30 deallocates the physical area allocated to the copy destination area in the backup volume 60 of the copy destination unit 30. Alternatively, in this case, as described previously, the controller module 21 included in the copy destination unit 30 may copy zero data to the copy destination area in the backup volume 60 of the copy destination unit 30.
  • the case (i) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area is not allocated to the business volume 50 is associated with the case (c) in which the backup volume 60 of the copy destination unit 30 is a current volume.
  • the controller module 21 included in the copy source unit 20 compresses zero data that is dummy information. That is, the controller module 21 generates data representing that the physical area is not allocated to the business volume 50. Then the controller module 21 transfers the compressed zero data representing that the physical area is not allocated to the business volume 50 to the copy destination unit 30. Upon receiving the zero data, the controller module 21 included in the copy destination unit 30 writes zero data to a copy destination area in the backup volume 60 of the copy destination unit 30.
  • the controller module 21 included in the copy source unit 20 may transfer zero data that is dummy information to the copy destination unit 30. Upon receiving the zero data, the controller module 21 included in the copy destination unit 30 copies the zero data to a copy destination area in the backup volume 60 of the copy destination unit 30.
  • the case (ii) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area has already been allocated to the business volume 50 is associated with the case (a) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area is not allocated to the backup volume 60.
  • the controller module 21 included in the copy source unit 20 transfers real data to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 allocates a physical area to the copy destination area in the backup volume 60 of the copy destination unit 30 and copies the real data to the copy destination area.
  • the case (ii) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area has already been allocated to the business volume 50 is associated with the case (b) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area has already been allocated to the backup volume 60.
  • the controller module 21 included in the copy source unit 20 transfers real data to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 copies the real data to the copy destination area in the backup volume 60.
  • the case (ii) in which the business volume 50 of the copy source unit 20 is a Thin Provisioning volume and a physical area has already been allocated to the business volume 50 is associated with the case (c) in which the backup volume 60 of the copy destination unit 30 is a current volume.
  • the controller module 21 included in the copy source unit 20 transfers real data to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 copies the real data to the copy destination area in the backup volume 60.
  • the case (iii) in which the business volume 50 of the copy source unit 20 is a current volume is associated with the case (a) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area is not allocated to the backup volume 60.
  • the controller module 21 included in the copy source unit 20 transfers real data to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 allocates a physical area to a copy destination area in the backup volume 60 of the copy destination unit 30 and copies the real data to the copy destination area in the backup volume 60.
  • the case (iii) in which the business volume 50 of the copy source unit 20 is a current volume is associated with the case (b) in which the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume and a physical area has already been allocated to the backup volume 60.
  • the controller module 21 included in the copy source unit 20 transfers real data to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 copies the real data to the copy destination area in the backup volume 60.
  • the case (iii) in which the business volume 50 of the copy source unit 20 is a current volume is associated with the case (c) in which the backup volume 60 of the copy destination unit 30 is a current volume.
  • the controller module 21 included in the copy source unit 20 transfers real data to the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 copies the real data to the copy destination area in the backup volume 60.
  • FIGs. 5 to 7 an initial copying operation performed immediately after a remote advanced copy function, which can be applied to a variable allocation virtual volume according to an embodiment, has started and an in-service copying operation performed when the business volume 50 is updated will be described with reference to FIGs. 5 to 7 .
  • the backup of the business volume 50 that is a Thin Provisioning volume of the copy source unit 20 is generated in the backup volume 60 that is a Thin Provisioning volume of the copy destination unit 30.
  • FIG. 5 is a schematic diagram illustrating an initial copying operation performed in remote advanced copy start processing according to an embodiment.
  • the controller module 21 included in the copy source unit 20 sequentially copies pieces of data stored in the business volume 50 of the copy source unit 20 starting from the head to the backup volume 60 of the copy destination unit 30.
  • the states of areas in the business volume 50 of the copy source unit 20 are "allocated”, “allocated”, “unallocated” and “unallocated” from the head and the states of areas in the backup volume 60 of the copy destination unit 30 are “allocated”, “unallocated”, “allocated”, and “unallocated” from the head.
  • the controller module 21 included in the copy source unit 20 communicates with the controller module 21 included in the copy destination unit 30 and determines that both of the volumes of the copy source unit 20 and the copy destination unit 30 are Thin Provisioning volumes. Subsequently, the controller module 21 included in the copy source unit 20 starts to sequentially copy pieces of data stored in the business volume 50 from the head so as to make the business volume 50 and the backup volume 60 equivalent to each other.
  • the controller module 21 included in the copy source unit 20 transfers these pieces of data in accordance with the above-described data transfer patterns. That is, in the case of data stored in an allocated area in the business volume 50, the controller module 21 included in the copy source unit 20 transfers real data stored in the allocated area to the copy destination unit 30 on the basis of the case (ii). In the case of data stored in an unallocated area in the business volume 50, the controller module 21 included in the copy source unit 20 compresses zero data and transfers the compressed zero data to the copy destination unit 30 on the basis of the case (i).
  • the compression of zero data may be typically performed by specifying a start Logical Block Addressing (LBA) representing the initial address of a transfer area and a Block Count (BC) representing a block length measured from the initial address.
  • LBA Logical Block Addressing
  • BC Block Count
  • an LBA is an address representing each area in a volume.
  • the controller module 21 included in the copy destination unit 30 sequentially receives "data”, “data”, “compressed data”, and “compressed data” that have been transferred thereto from the allocated area, the allocated area, the unallocated area, and the unallocated area, respectively, analyzes the received pieces of data, and copies the analyzed pieces of data to the backup volume 60 of the copy destination unit 30.
  • the controller module 21 included in the copy destination unit 30 copies the received data to a copy destination area for the received data in the backup volume 60 on the basis of the data transfer pattern in the fifth row when the state of the copy destination area is "allocated” (see, a first row in a volume having a title of "after copying" in the copy destination unit 30 illustrated in FIG. 5 ).
  • the controller module 21 included in the copy destination unit 30 allocates a physical area to a copy destination area for the received data in the backup volume 60 and copies the received data to the copy destination area on the basis of the data transfer pattern in the fourth row when the state of the copy destination area is "unallocated" (see, a second row in the volume having the title of "after copying" in the copy destination unit 30 illustrated in FIG. 5 ).
  • the controller module 21 included in the copy destination unit 30 Upon receiving the "compressed data" from the copy source unit 20, the controller module 21 included in the copy destination unit 30 deallocates a physical area allocated to a copy destination area for the received compressed data in the backup volume 60 (see, a third row in the volume having the title of "after copying" in the copy destination unit 30 illustrated in FIG. 5 ) or copies zero data to the copy destination area on the basis of the data transfer pattern in the second row when the state of the copy destination area is "allocated".
  • the controller module 21 included in the copy destination unit 30 does not perform copying processing on the basis of the data transfer pattern in the first row when the state of a copy destination area for the received compressed data in the backup volume 60 is "unallocated” (see, a fourth row in the volume having the title of "after copying" in the copy destination unit 30 illustrated in FIG. 5 ).
  • FIG. 6 is a schematic diagram illustrating an in-service copying operation performed in remote advanced copy start processing according to an embodiment.
  • the business volume 50 of the copy source unit 20 is equivalent to the backup volume 60 of the copy destination unit 30 (see, a volume having a title of "before updating” in the copy source unit 20 and a volume having a title of "before copying" in the copy destination unit 30 illustrated in FIG. 6 ).
  • the updated data is copied to the backup volume 60 of the copy destination unit 30.
  • the updating in the business volume 50 is reflected in the backup volume 60.
  • update data is written into a copy source area in a first row in the business volume 50.
  • the controller module 21 included in the copy source unit 20 transfers to the copy destination unit 30 updated data stored in the copy source area into which the update data has been written.
  • the controller module 21 included in the copy destination unit 30 copies the received data to the copy destination area.
  • FIG. 7 is a schematic diagram illustrating an in-service copying operation performed in remote advanced copy start processing according to another embodiment.
  • update data is written into a copy source area in a third row in the business volume 50. Since the state of this copy source area is "unallocated", the controller module 21 included in the copy source unit 20 allocates a physical area to the copy source area and writes the update data into the copy source area. In addition, the controller module 21 included in the copy source unit 20 transfers to the copy destination unit 30 updated data stored in the copy source area into which the update data has been written.
  • the controller module 21 included in the copy destination unit 30 Upon receiving the updated data, since the state of a copy destination area for the updated data is "unallocated", the controller module 21 included in the copy destination unit 30 allocates a physical area to the copy destination area and copies the received data to the copy destination area. Thus, it is possible to maintain the equivalence between the business volume 50 and the backup volume 60 during operation.
  • FIG. 8 is a flowchart illustrating the flow of remote advanced copy start processing according to an embodiment.
  • step S100 upon receiving an instruction for starting a remote advanced copy function from the maintenance server 12, the copy source unit 20 starts remote advanced copy start processing.
  • step S102 the controller module 21 included in the copy source unit 20 creates a copy management table in the cache memory 22 so as to record volume type information representing the volume type of the business volume 50 of the copy source unit 20 and the volume type of the backup volume 60 of the copy destination unit 30.
  • step S104 the controller module 21 included in the copy source unit 20 sets the volume type of the business volume 50 of the copy source unit 20 in the created copy management table.
  • step S106 the controller module 21 included in the copy source unit 20 notifies the copy destination unit 30 of the volume type of the business volume 50.
  • step S108 when the controller module 21 included in the copy destination unit 30 is notified of the volume type of the business volume 50 by the copy source unit 20, it creates a copy management table in the cache memory 22 so as to record volume type information representing the volume type of the business volume 50 of the copy source unit 20 and the volume type of the backup volume 60 of the copy destination unit 30.
  • step S110 the controller module 21 included in the copy destination unit 30 sets in the created copy management table the volume type of the backup volume 60 of the copy destination unit 30 and the volume type of the business volume 50 that has been notified by the copy source unit 20.
  • step S112 the controller module 21 included in the copy destination unit 30 notifies the copy source unit 20 of the volume type of the backup volume 60.
  • step S114 when the controller module 21 included in the copy source unit 20 is notified of the volume type of the backup volume 60 by the copy destination unit 30, it sets the volume type of the backup volume 60 in the copy management table updated in step S104 and the remote advanced copy start processing ends.
  • the copy management table may be updated as appropriate in the following processing.
  • FIG. 9 illustrates a copy management table according to an embodiment.
  • a single copy management table is created and managed for a single copy session in each unit.
  • a copy management table used in the remote advanced copy start processing includes at least volume type information representing the volume type of the business volume 50 of the copy source unit 20 and the volume type of the backup volume 60 of the copy destination unit 30.
  • a copy management table may include other items regarding copying processing in addition to the volume type of the business volume 50 of the copy source unit 20 and the volume type of the backup volume 60 of the copy destination unit 30.
  • FIG. 10 is a flowchart illustrating the flow of data transmission processing performed by a copy source unit according to an embodiment.
  • FIG. 11 is a flowchart illustrating the flow of data receiving processing performed by a copy destination unit according to an embodiment.
  • step S200 when the controller module 21 included in the copy source unit 20 acquires the volume type of the business volume 50 of the copy source unit 20 and the volume type of the backup volume 60 of the copy destination unit 30 in the above-described remote advanced copy start processing, the data transmission processing starts.
  • the controller module 21 refers to the copy management table stored in the cache memory 22 and determines whether the business volume 50 of the copy source unit 20 and the backup volume 60 of the copy destination unit 30 are Thin Provisioning volumes. More specifically, the controller module 21 specifies the volume types of the business volume 50 and the backup volume 60 set in the copy management table and determines whether both of the business volume 50 and the backup volume 60 are Thin Provisioning volumes.
  • step S202 When it is determined that at least one of the business volume 50 and the backup volume 60 is not a Thin Provisioning volume and is a current or normal volume (No in step S202), the process proceeds to step S204. On the other hand, when it is determined that both of the business volume 50 and the backup volume 60 are Thin Provisioning volumes (Yes in step S202), the process proceeds to step S206.
  • step S204 the controller module 21 reads real data from a copy target area in the business volume 50.
  • step S206 the controller module 21 determines whether a physical area is not allocated to the copy target area in the business volume 50.
  • the controller module 21 performs the above-described determination processing by referring to a physical area conversion table recording information about the relationship between each virtual area in the business volume 50 that is a virtual volume and a physical area in a physical volume which is allocated to the virtual area.
  • a physical area conversion table may include data items illustrated in FIG. 12 .
  • LUN_V represents a virtual area (virtual block) in a virtual volume or a physical area (storage area) in a physical volume
  • LBA Logical Block Addressing
  • a physical volume is divided into blocks having a predetermined size.
  • a physical area is allocated to the virtual volume in units of the blocks of the physical volume in accordance with the size of the data.
  • FIG. 12 it is assumed that each of the blocks of the physical volume has a size of 32 MB (0x10000 block count).
  • the controller module 21 retrieves a physical area associated with a copy target area using the physical area conversion table. When a physical area associated with the copy target area is detected, the controller module 21 determines that a physical area has already been allocated to the copy target area. On the other hand, when a physical area associated with the copy target area is not detected using the physical area conversion table, the controller module 21 determines that a physical area is not allocated to the copy target area.
  • step S206 When it is determined that a physical area has already been allocated to the copy target area (No in step S206), the process proceeds to step S204 in which the controller module 21 reads real data from the copy target area. On the other hand, when it is determined that a physical area is not allocated to the copy target area (Yes in step S206), the process proceeds to step S208.
  • the controller module 21 generates compressed data for the copy target area.
  • the compressed data is data transferred from the copy source unit 20 to the copy destination unit 30 when both of the business volume 50 of the copy source unit 20 and the backup volume 60 of the copy destination unit 30 are Thin Provisioning volumes and a physical area is not allocated to the copy target area in the business volume 50.
  • the compressed data may be compressed zero data generated by specifying a start LBA representing an initial address of a transfer area and a Block Count (BC) representing a block length measured from the initial address.
  • BC Block Count
  • the compressed data may be number or value representing the each copy target area unallocated to any of the physical areas.
  • the size of the each copy target area is the same as the each of the blocks of the physical volume having the size of 32 MB.
  • the compressed data may be number or value representing the business volume 50.
  • the compressed data regarding the whole virtual areas is transferred to the backup volume 60 at one time.
  • compressed zero data generated by specifying a start LBA and a transfer length may be transferred to each copy destination area (LUN_V) in the backup volume 60 of the copy destination unit 30.
  • LUN_V copy destination area
  • a data transfer length is set to a length corresponding to the block of the physical area.
  • step S210 the controller module 21 remotely transfers the real data read in step S204 or the compressed data generated in step S208 to the copy destination unit 30.
  • step S212 After the controller module 21 has transmitted all of pieces of transmission target data, the data transmission processing ends in step S212.
  • step S300 upon receiving data from the copy source unit 20, the controller module 21 included in the copy destination unit 30 starts the data receiving processing.
  • step S302 the controller module 21 refers to the copy management table stored in the cache memory 22 and determines whether the backup volume 60 of the copy destination unit 30 is a Thin Provisioning volume. More specifically, as described previously, the controller module 21 performs the above-described determination processing by detecting the volume type of the backup volume 60 set in the copy management table.
  • step S302 When it is determined that the backup volume 60 is not a Thin Provisioning volume and is a normal or current volume (No in step S302), the process proceeds to step S316. On the other hand, when it is determined that the backup volume 60 is a Thin Provisioning volume (Yes in step S302), the process proceeds to step S304.
  • step S304 the controller module 21 determines whether the received data is compressed data. When it is determined that the received data is not compressed data and is real data (No in step S304), the process proceeds to step S306. On the other hand, when it is determined that the received data is compressed data (Yes in step S304), the process proceeds to step S310.
  • step S306 the controller module 21 refers to a physical area conversion table and determines whether a physical area has already been allocated to a copy destination area in the backup volume 60. When it is determined that a physical area is not allocated to the copy destination area (No in step S306), the process proceeds to step S308 in which the controller module 21 allocates a physical area to the copy destination area. On the other hand, when it is determined that a physical area has already been allocated to the copy destination area (Yes in step S306), the process proceeds to step S316.
  • step S316 the controller module 21 writes the received data into the copy destination area.
  • step S318 After the controller module 21 has performed the above-described processing upon all of pieces of received data, the data receiving processing ends in step S318.
  • step S304 when it is determined in step S304 that the received data is compressed data, the controller module 21 refers to the physical area conversion table and determines whether a physical area has already been allocated to the copy destination area in the backup volume 60 in step S310. When it is determined that a physical area is not allocated to the copy destination area (No in step S310), the process proceeds to step S312 in which the controller module 21 does not copy the received data and the data receiving processing ends. On the other hand, when it is determined that a physical area has already been allocated to the copy destination area (Yes in step S310), the process proceeds to step S314.
  • step S314 the controller module 21 deallocates the physical area allocated to the copy destination area or copies zero data to the copy destination area. In an embodiment, when the entire area of one of blocks of the physical area is a copy target area, the controller module 21 may deallocate the physical area. When the entire area of one of blocks of the physical area is not a copy target area, the controller module 21 may copy zero data.
  • the invention also provides a computer program or a computer program product for carrying out any of the methods described herein, and a computer readable medium having stored thereon a program for carrying out any of the methods described herein.
  • a computer program embodying the invention may be stored on a computer-readable medium, or it could, for example, be in the form of a signal such as a downloadable data signal provided from an Internet website, or it could be in any other form.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)

Claims (2)

  1. Appareil de stockage (30) pouvant être connecté à un autre appareil de stockage (20) de manière à recevoir des données depuis celui-ci, l'appareil de stockage (30) comprenant :
    des unités de stockage (241 à 244) configurées pour stocker des données ; et
    un dispositif de commande (21) configuré pour commander un volume virtuel (60) utilisant les unités de stockage (241 à 244), dans lequel le volume virtuel (60) est une allocation variable d'unités de stockage (241 à 244) conformément à un modèle d'utilisation du volume virtuel (60),
    dans lequel le dispositif de commande (21) est configuré pour allouer une zone de stockage physique dans l'allocation variable d'unités de stockage (241 à 244) au volume virtuel (60) en unités de blocs ;
    le dispositif de commande (21) étant opérationnel pour :
    déterminer si des données reçues depuis l'autre appareil de stockage (20) sont des données réelles ou des données nulles comprimées, les données nulles comprimées concernant une adresse initiale et une longueur de bloc d'une zone cible de copie d'une source de copie d'un volume virtuel (50) de l'autre appareil de stockage (20) ;
    déterminer si une zone de destination de copie du volume virtuel (60) est allouée à au moins une des unités de stockage (241 à 244) ;
    allouer sélectivement ou ne pas allouer la zone de destination de copie à l'unité de stockage (241 à 244) conformément à une combinaison de la détermination, et
    copier les données réelles dans la zone de destination de copie lorsque la zone de destination de la copie est allouée,
    dans lequel, s'il est déterminé que les données reçues sont des données nulles comprimées et que la zone de destination de copie occuperait un bloc entier de la zone de stockage physique, le dispositif de commande (21) est configuré de telle sorte que la zone de stockage physique n'est pas allouée au volume virtuel, et
    dans lequel, s'il est déterminé que les données reçues sont des données nulles comprimées et que la zone de destination de copie occuperait une partie d'un bloc de la zone de stockage physique, le dispositif de commande (21) est configuré pour allouer la zone de stockage physique au volume virtuel et pour copier les données nulles dans la partie du bloc de la zone de stockage physique destinée à être occupée par la zone de destination de copie.
  2. Procédé de copie de données stockées dans un premier volume virtuel (50) d'un premier appareil de stockage (20) dans un second volume virtuel (60) d'un second appareil de stockage (30), dans lequel une zone de stockage physique dans une allocation variable d'unités de stockage (241 à 244) est allouée au volume virtuel (60) en unités de blocs ; le procédé comprenant les étapes consistant à :
    recevoir une instruction pour copier des données stockées dans le premier volume virtuel (50) dans le second volume virtuel (60) ;
    déterminer si chacun des premier volume virtuel (50) et du second volume virtuel (60) est une allocation variable d'unités de stockage (241 à 244) conformément à un modèle d'utilisation du volume virtuel (50, 60) ;
    déterminer si une zone cible de copie d'une source de copie du premier volume virtuel (50) est allouée dans une unité de stockage (241 à 244), chacun des premier et second volumes virtuels (50, 60) étant une allocation variable d'unités de stockage (241 à 244) ;
    transmettre des données nulles comprimées, incluant une adresse initiale et une longueur de bloc de la zone cible de copie de la source de copie, au second appareil de stockage (30) lorsque la zone cible de copie n'est pas allouée à l'unité de stockage (241 à 244) ; et
    transmettre des données stockées dans la zone cible de copie au second appareil de stockage (30),
    dans lequel, s'il est déterminé que les données reçues sont des données nulles comprimées et que la zone de destination de copie occuperait un bloc entier de la zone de stockage physique, la zone de stockage physique dans l'unité de stockage (241 à 244) n'est pas allouée au volume virtuel, et
    dans lequel, s'il est déterminé que les données reçues sont des données nulles comprimées et que la zone de destination de copie occuperait une partie d'un bloc de la zone de stockage physique, la zone de stockage physique dans l'unité de stockage (241 à 244) est allouée au volume virtuel et des données nulles sont copiées dans la partie du bloc de la zone de stockage physique destinée à être occupée par la zone de destination de copie.
EP10162571.3A 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données Active EP2254036B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12191700.9A EP2557494B1 (fr) 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2009121602A JP4818395B2 (ja) 2009-05-20 2009-05-20 ストレージ装置及びデータコピー方法

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP12191700.9A Division EP2557494B1 (fr) 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données
EP12191700.9A Division-Into EP2557494B1 (fr) 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données

Publications (3)

Publication Number Publication Date
EP2254036A2 EP2254036A2 (fr) 2010-11-24
EP2254036A3 EP2254036A3 (fr) 2011-08-24
EP2254036B1 true EP2254036B1 (fr) 2018-04-04

Family

ID=42633126

Family Applications (2)

Application Number Title Priority Date Filing Date
EP12191700.9A Active EP2557494B1 (fr) 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données
EP10162571.3A Active EP2254036B1 (fr) 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP12191700.9A Active EP2557494B1 (fr) 2009-05-20 2010-05-11 Appareil de stockage et procédé de copie de données

Country Status (3)

Country Link
US (1) US8639898B2 (fr)
EP (2) EP2557494B1 (fr)
JP (1) JP4818395B2 (fr)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8892676B2 (en) * 2008-11-07 2014-11-18 Compellent Technologies Thin import for a data storage system
US9934108B2 (en) * 2010-10-27 2018-04-03 Veritas Technologies Llc System and method for optimizing mirror creation
US9552160B2 (en) 2011-06-27 2017-01-24 International Business Machines Corporation Preserving data availability and I/O performance when creating virtual raid volumes
JP5780067B2 (ja) * 2011-09-01 2015-09-16 富士通株式会社 ストレージシステム、ストレージ制御装置およびストレージ制御方法
US9063883B2 (en) * 2011-09-26 2015-06-23 International Business Machines Corporation Management of point-in-time copy relationship for extent space efficient volumes
US9927979B1 (en) * 2012-02-01 2018-03-27 EMC IP Holding Company LLC Data compression using constant number-of-track-groups and thin provisioning clone target
US9177177B1 (en) * 2012-10-04 2015-11-03 Symantec Corporation Systems and methods for securing storage space
WO2014101086A1 (fr) * 2012-12-28 2014-07-03 华为技术有限公司 Procédé et dispositif permettant de traiter un espace de stockage et support de stockage lisible par ordinateur non volatile
US9779003B2 (en) 2013-06-12 2017-10-03 International Business Machines Corporation Safely mapping and unmapping host SCSI volumes
US9940019B2 (en) * 2013-06-12 2018-04-10 International Business Machines Corporation Online migration of a logical volume between storage systems
US8819317B1 (en) 2013-06-12 2014-08-26 International Business Machines Corporation Processing input/output requests using proxy and owner storage systems
US9769062B2 (en) 2013-06-12 2017-09-19 International Business Machines Corporation Load balancing input/output operations between two computers
JP6160296B2 (ja) 2013-06-25 2017-07-12 富士通株式会社 ストレージ制御装置，ストレージシステム，および制御プログラム
US9946604B1 (en) * 2015-02-04 2018-04-17 Tintri Inc. Optimized remote cloning
JP2016212548A (ja) 2015-05-01 2016-12-15 富士通株式会社 ストレージ制御装置、ストレージ制御方法、及びストレージ制御プログラム
US10853257B1 (en) * 2016-06-24 2020-12-01 EMC IP Holding Company LLC Zero detection within sub-track compression domains
WO2018131067A1 (fr) * 2017-01-10 2018-07-19 株式会社日立製作所 Dispositif de restauration de données perdues en raison d'une défaillance d'un lecteur de mémoire
US10628200B2 (en) * 2017-11-02 2020-04-21 Red Hat Israel, Ltd. Base state for thin-provisioned volumes

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0293721A (ja) 1988-09-29 1990-04-04 Nec Corp 磁気ディスク装置の複写転送方式
JP2003202964A (ja) * 2002-01-09 2003-07-18 Hitachi Ltd 計算機システムの制御方法、計算機システム、記憶装置の制御方法及び記憶装置
JP4288037B2 (ja) 2002-02-25 2009-07-01 インターナショナル・ビジネス・マシーンズ・コーポレーション 記録ディスクを用いた記録装置、記録システムおよびそのバックアップ方法
US7024586B2 (en) * 2002-06-24 2006-04-04 Network Appliance, Inc. Using file system information in raid data reconstruction and migration
US7024526B2 (en) * 2002-10-31 2006-04-04 Hitachi, Ltd. Apparatus and method of null data skip remote copy
JP4634136B2 (ja) * 2004-12-24 2011-02-16 株式会社日立製作所 記憶制御システム
US20070214194A1 (en) * 2006-03-07 2007-09-13 James Reuter Consistency methods and systems
JP2007316995A (ja) * 2006-05-26 2007-12-06 Hitachi Ltd 記憶システム及びデータ管理方法
JP4877962B2 (ja) * 2006-10-25 2012-02-15 株式会社日立製作所 暗号化機能を備えたストレージサブシステム
US8117409B2 (en) * 2006-11-22 2012-02-14 Hitachi, Ltd. Method and apparatus for backup and restore in a dynamic chunk allocation storage system
JP2008181271A (ja) * 2007-01-24 2008-08-07 Hitachi Ltd 仮想ボリュームに記憶されたデータをバックアップする記憶制御装置
JP4990066B2 (ja) * 2007-08-21 2012-08-01 株式会社日立製作所 論理ボリュームのペアを利用したデータ保存の方式を変更する機能を備えたストレージシステム
JP5142629B2 (ja) * 2007-08-22 2013-02-13 株式会社日立製作所 仮想ボリュームのバックアップを行うストレージシステム及び方法
JP4762323B2 (ja) * 2009-03-03 2011-08-31 富士通株式会社 アクセス制御装置、情報処理装置、アクセス制御プログラム及びアクセス制御方法

Also Published As

Publication number Publication date
EP2557494A1 (fr) 2013-02-13
EP2557494B1 (fr) 2018-03-21
US20100299491A1 (en) 2010-11-25
EP2254036A3 (fr) 2011-08-24
JP2010271808A (ja) 2010-12-02
JP4818395B2 (ja) 2011-11-16
EP2254036A2 (fr) 2010-11-24
US8639898B2 (en) 2014-01-28

Similar Documents

Publication Publication Date Title
EP2254036B1 (fr) Appareil de stockage et procédé de copie de données
JP6791834B2 (ja) 記憶システム及び制御ソフトウェア配置方法
US7127557B2 (en) RAID apparatus and logical device expansion method thereof
US9501231B2 (en) Storage system and storage control method
US8667241B2 (en) System for data migration from a storage tier allocated to a virtual logical volume
US8037267B2 (en) Remote copy system and remote site power saving method
US8984221B2 (en) Method for assigning storage area and computer system using the same
US7461201B2 (en) Storage control method and system for performing backup and/or restoration
US8209505B2 (en) Storage system and method of taking over logical unit in storage system
US20070271429A1 (en) Storage System and method of producing recovery volume
US8010753B2 (en) Systems and methods for temporarily transferring use of portions of partitioned memory between host computers
US7984260B2 (en) Storage system provided with a plurality of controller modules
JP2015515033A (ja) ストレージシステム
US20130036279A1 (en) Storage system using real data storage area dynamic allocation method
JPWO2015052798A1 (ja) ストレージシステム及び記憶制御方法
US7451285B2 (en) Computer systems, management computers and storage system management method
JP2015162091A (ja) 記憶制御装置、ストレージシステム、記憶制御方法、および記憶制御プログラム
CN110300960B (zh) 信息系统、管理程序和信息系统的程序更换方法
US10664193B2 (en) Storage system for improved efficiency of parity generation and minimized processor load
US8935488B2 (en) Storage system and storage control method
WO2018055686A1 (fr) Système de traitement d'informations
US20050223180A1 (en) Accelerating the execution of I/O operations in a storage system
JP7057408B2 (ja) 記憶システム及びその制御方法
US20160357479A1 (en) Storage control apparatus
JP2020027433A (ja) 情報システム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME RS

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME RS

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 3/06 20060101AFI20110715BHEP

17P Request for examination filed

Effective date: 20120220

17Q First examination report despatched

Effective date: 20150217

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20171012

INTG Intention to grant announced

Effective date: 20171027

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 986271

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180415

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010049597

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180404

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180704

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180704

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180705

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 986271

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180806

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010049597

Country of ref document: DE

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180531

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180531

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

26N No opposition filed

Effective date: 20190107

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180511

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180511

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180511

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20100511

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180404

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180804

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602010049597

Country of ref document: DE

Representative=s name: HL KEMPNER PATENTANWAELTE, SOLICITORS (ENGLAND, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602010049597

Country of ref document: DE

Representative=s name: HL KEMPNER PATENTANWALT, RECHTSANWALT, SOLICIT, DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240419

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240418

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240418

Year of fee payment: 15