STORAGE SYSTEM AND STORAGE SYSTEM DATA PROCESSING METHOD - Patent application

Abstract

To realize replication with high versatility which can suppress a communication traffic volume.SOLUTION: A first storage system compresses data concerning reading and writing by an original site to store the data in a first physical volume, and a second storage system compresses data concerning reading and writing by a copy site to store the data in a second physical volume. The first storage system and the second storage system determine a compression system to be applied to transfer object data on the basis of a compression system which can be executed by the first storage system and a compression system which can be executed by the second storage system and transfer the transfer object data compressed by the determined compression system in the case of performing replication for transferring the data stored in the first physical volume of the first storage system to the second storage system to store the data in the second physical volume.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a storage system and a data processing method for a storage system. [Background technology]

[0002] Conventionally, there is a technology described in JP2014-524601A (Patent Document 1) regarding data processing of a storage system. This publication states that "a first storage system has a first RAID group composed of a plurality of first storage devices that are the basis of a first logical volume. A second storage system has a second RAID group composed of a plurality of second storage devices that are the basis of a second logical volume. The RAID configuration of the first RAID group is the same as that of the second RAID group, and the type of compression / decompression function possessed by each first storage device is the same as that of each second storage device. For data in the first logical volume, compressed data is read from the first storage device without being decompressed, and the read compressed data is written to a second storage device that is located in the same position in the second RAID group as the first storage device." [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2014-524601 Summary of the Invention [Problem to be solved by the invention]

[0004] According to Patent Document 1, the amount of data transmitted between storage systems can be reduced. However, this technology cannot be applied when the compression methods used by the first storage system and the second storage system are different. In addition, it is desirable to configure the second storage system with reduced processing performance compared to the first storage system. For these reasons, the realization of replication that has high versatility and can be applied even when there are differences in compression methods or performance between storage systems, and can reduce the amount of communication, has been an issue.

[0005] Therefore, an object of the present invention is to realize replication that is highly versatile and capable of reducing communication traffic. [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, one representative data replication system of the present invention comprises a first storage system having a processor and providing a primary site, and a second storage system having a processor and providing a secondary site, wherein the first storage system compresses data related to reading and writing by the primary site and stores it in a first physical volume, and the second storage system compresses data related to reading and writing by the secondary site and stores it in a second physical volume, and the first storage system and the second storage system determine a compression method to be applied to the data to be transferred based on a compression method executable by the first storage system and a compression method executable by the second storage system when performing replication in which data stored in the first physical volume of the first storage system is transferred to the second storage system and stored in the second physical volume, and transfer the data to be transferred compressed with the determined compression method.

[0007] Furthermore, one representative data replication method of the present invention is a data replication method performed by a data replication system including a first storage system having a processor and compressing data related to reading and writing by a primary site and storing it in a first physical volume, and a second storage system having a processor and compressing data related to reading and writing by a secondary site and storing it in a second physical volume, the data replication method including a step of the first storage system compressing data related to reading and writing by the primary site using the first compression method and storing it in the first physical volume, a step of determining a compression method to be applied to data to be transferred based on a compression method executable by the first storage system and a compression method executable by the second storage system when the first storage system and the second storage system perform replication in which data stored in the first physical volume of the first storage system is transferred to the second storage system and stored in the second physical volume, and a step of transferring the data to be transferred compressed using the determined compression method. Effect of the Invention

[0008] According to the present invention, it is possible to realize replication that is highly versatile and can reduce the amount of communication. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a configuration diagram of a data replication system according to a first embodiment. [Diagram 2] FIG. 4 is an explanatory diagram of a primary storage in the first embodiment. [Diagram 3] FIG. 2 is an explanatory diagram of a secondary storage according to the first embodiment. [Figure 4] FIG. 13 is an explanatory diagram of compression and data storage in the primary storage. [Diagram 5] FIG. 13 is an explanatory diagram of decompression and recompression in the primary storage. [Figure 6]FIG. 2 is an explanatory diagram of compression and data storage in a secondary storage. [Figure 7] FIG. 4 is a sequence diagram illustrating a replication processing operation according to the first embodiment. [Figure 8] FIG. 11 is an explanatory diagram of a primary storage in the second embodiment. [Figure 9] FIG. 11 is an explanatory diagram of a secondary storage according to the second embodiment. [Figure 10] FIG. 11 is a sequence diagram for explaining a replication processing operation in the second embodiment. [Figure 11] FIG. 11 is an explanatory diagram of the operation of a logical / physical address management unit in the second embodiment. [Figure 12] 1 shows a first modified example of a system configuration. [Figure 13] 2 shows a second modified example of the system configuration. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. EXAMPLES

[0011] Fig. 1 is a configuration diagram of a data replication system according to Example 1. The data replication system shown in Fig. 1 includes a first storage system providing a primary site, and a second storage system providing a secondary site.

[0012] Specifically, the data replication system has a configuration in which a primary server 100 and a primary storage 200 are connected to a network 510, a secondary server 300 and a secondary storage 400 are connected to a network 520, and the networks 510 and 520 are further connected to each other.

[0013] The primary server 100 and the network 510 are connected by a communication line 500. The primary storage 200 and the network 510 are connected by a communication line 501. The secondary server 300 and the network 520 are connected by a communication line 502. The secondary storage 400 and the network 520 are connected by a communication line 503.

[0014] The primary server 100 is a server that issues I / O on the primary site side. The primary storage 200 is a storage for storing data on the primary site side, and includes a primary volume 10. The primary storage 200 operates as a storage for holding master data in the data replication system.

[0015] The secondary server 300 is a server that issues I / O on the secondary site side. The secondary storage 400 is a storage for storing data on the secondary site side, and has a secondary volume 11. The secondary storage 400 operates as a storage for holding replicated data in a data replication system.

[0016] Fig. 2 is an explanatory diagram of the primary storage 200 in Example 1. As shown in Fig. 2, the primary storage 200 has a network interface 201, a logical volume 210, a physical volume 211, a first compression unit 220, a decompression unit 230, a second compression unit 231, a logical / physical address management unit 240, and a compression method management unit 250.

[0017] When processing a write from the primary site, the network interface 201 accepts a write request via the communication line 501 and writes data to the logical volume 210. The data written to the logical volume 210 is compressed by the first compression unit 220 and written to the physical volume 211 as compressed data.

[0018] When processing a read from the primary site, the network interface 201 accepts a read request via the communication line 501, and the compressed data 212 is read from the physical volume 211. The read compressed data is decompressed by the decompression unit 230 to become decompressed data 235, and is written to the logical volume 210, thereby enabling a read response.

[0019] When data of the physical volume 211 is sent to the secondary storage 400 for replication, the target compressed data is read from the physical volume 211, decompressed by the decompression unit 230 to become decompressed data 235, and then compressed by the second compression unit 231 and sent to the secondary storage 400 as compressed data 232.

[0020] The logical physical address management unit 240 has a management table that maps the logical addresses of the logical volume 210 to physical addresses stored in the physical volume 211. Each time data is written to the physical volume 211, a physical address 241 is generated and passed to the physical volume 211.

[0021] The compression method management unit 250 manages the compression and decompression processing in the primary storage 200. The compression algorithm used by the first compression unit 220, that is, the main algorithm used when generating compressed data to be stored in the physical volume 211, is referred to as the first compression algorithm for convenience. On the other hand, the main algorithm used by the secondary storage 400, which is the replication destination, when storing data related to reading and writing by the secondary site in the physical volume is referred to as the second compression algorithm for convenience. Note that the first and second compression algorithms are not defined by the storage that uses them, and for example, the second compression algorithm may be used in the primary storage 200 as described later. Also, there may be multiple compression algorithms in the first compression algorithm, or the first compression algorithm and the second compression algorithm may include the same compression algorithm.

[0022] The compression method management unit 250 controls the compression algorithm to be used by outputting a compression method designation signal 251 that designates a first compression algorithm and a compression method designation signal 252 that designates a second compression algorithm. Specifically, the compression method designation signal 251 is provided to the first compression unit 220, and the compression method designation signal 252 is provided to the second compression unit 231. Here, there may be multiple algorithms that can be used by the second compression unit 231. In this case, the second compression algorithm is selected according to the replication destination.

[0023] Fig. 3 is an explanatory diagram of the secondary storage 400 in the embodiment 1. As shown in Fig. 3, the secondary storage 400 has a network interface 401, a logical volume 410, a physical volume 411, a compression unit 420, a decompression unit 430, a selection unit 453, a logical / physical address management unit 440, and a compression method management unit 450.

[0024] When the network interface 401 receives the compressed data 232 from the primary storage 200, the compressed data 232 is stored as is in the physical volume 411 via the selection unit 453. This is because the compressed data 232 has been compressed using the second compression algorithm used by the secondary storage 400, and therefore does not need to be decompressed and recompressed.

[0025] Furthermore, for example, when an abnormality occurs in the primary storage 200 and the secondary storage 400 processes writing by the secondary site, the network interface 401 accepts a write request via the communication line 503 and writes data to the logical volume 410. The data written to the logical volume 410 is compressed by the compression unit 420. At this time, the compression unit 420 uses a second compression algorithm. The compressed data is written to the physical volume 411 via the selection unit 453.

[0026] When processing a read from the secondary site, the network interface 401 accepts a read request via the communication line 503, and reads the compressed data 232 from the physical volume 411. The read compressed data is expanded by the expansion unit 430 to become expanded data, and is written to the logical volume 410, thereby enabling a read response.

[0027] The logical physical address management unit 440 has a management table in which the logical addresses of the logical volume 410 are mapped to physical addresses stored in the physical volume 411. Each time data is written to the physical volume 411, a physical address 441 is generated and passed to the physical volume 411.

[0028] The compression method management unit 450 manages the compression and decompression processing in the secondary storage 400. In the secondary storage 400, compression processing is not required during replication, but compression processing is performed when writing by I / O at the secondary site during failover. The compression method management unit 450 switches between processing during replication and processing during writing by I / O by sending a control signal 452 to a selection unit 453.

[0029] Fig. 4 is an explanatory diagram of compression and data storage in the primary storage 200. In Fig. 4, first, data at logical address A and data at logical address B are stored in the logical volume 210. In the logical volume 210, the data at logical address A and data at logical address B are both 16 KB in length.

[0030] The first compression unit 220 compresses the data at the logical address A using the first compression algorithm L1 to generate compressed data A. As a result of the compression, the size of the compressed data A is 4 KB long.

[0031] Similarly, the first compression unit 220 compresses the data at logical address B using the first compression algorithm L1 to generate compressed data B. As a result of the compression, the size of compressed data B is 8 KB long.

[0032] The compressed data A and the compressed data B are written to consecutive addresses in the physical volume 211. In this way, by compressing the data on the logical volume 210 and writing it to consecutive addresses, the data capacity of the physical volume 211 can be used efficiently.

[0033] 5 is an explanatory diagram of decompression and recompression in the primary storage 200. During replication, first, compressed data A and compressed data B are read from the physical volume 211. Here, the compressed data A and compressed data B read from the physical volume 211 are in a state compressed by the first compression algorithm L1, and are therefore referred to as the first compressed data A and the first compressed data B. The first compressed data A and the first compressed data B are specific examples of the compressed data 212 shown in FIG. 2.

[0034] The decompression unit 230 decompresses the first compressed data A based on the first compression algorithm L1. The decompressed data obtained by this decompression is the data at the logical address A. Similarly, the decompression unit 230 decompresses the first compressed data B based on the first compression algorithm L1. The decompressed data obtained by this decompression is the data at the logical address B.

[0035] The second compression unit 231 recompresses the decompressed data. The second compression unit 231 supports a plurality of second compression algorithms. In FIG. 5, the second compression algorithms L2a and L2b are illustrated. The second compression unit 231 selects a second compression algorithm in accordance with the secondary storage of the replication destination. Here, the description will be given on the assumption that the secondary storage 400 of the replication destination uses the second compression algorithm L2a.

[0036] The second compression unit 231 re-compresses the data at the logical address A using the second compression algorithm L2a to generate compressed data. Similarly, the second compression unit 231 re-compresses the data at logical address B using the second compression algorithm L2a to generate compressed data. The second compressed data A and the second compressed data B are combined to form a specific example of the compressed data 232 shown in FIG.

[0037] Figure 6 is an explanatory diagram of compression and data storage in the secondary storage 400. In Figure 6, first, data at logical address A and data at logical address B are stored in a logical volume 410. In the logical volume 410, the data at logical address A and data at logical address B are both 16 KB in length.

[0038] The second compression unit 420 compresses the data at the logical address A using the second compression algorithm L2a to generate second compressed data A. As a result of the compression, the size of the second compressed data A is 8 KB in length.

[0039] Similarly, the second compression unit 420 compresses the data at logical address B using the second compression algorithm L2a to generate second compressed data B. As a result of the compression, the size of the second compressed data B is 8 KB long.

[0040] The second compressed data A and the second compressed data B are combined and written to the physical volume 411 via the selection unit 453 .

[0041] On the other hand, the compressed data 232 received from the primary storage 200 during replication has already been compressed using the second compression algorithm L2a, so it is written directly to the physical volume 411 via the selection unit 453 without being decompressed or recompressed.

[0042] FIG. 7 is a sequence diagram for explaining the processing operation of replication in the first embodiment. First, the primary storage 200 transmits a secondary storage storage method acquisition command to the secondary storage 400 (1000). The secondary storage 400 notifies the primary storage 200 of the secondary storage storage method, i.e., the compression algorithm used by the secondary storage 400 (1001). Then, the primary storage 200 determines a compression algorithm that can be used in common by the primary storage 200 and the secondary storage 400 as the compression algorithm for the data to be transferred. If the compression algorithm is the one used when the data to be transferred was stored in the primary storage, the decompression and recompression (steps S103 and S104) described below can be omitted, but if not, the decompression and recompression described below are performed so that the secondary storage 400 can compress and decompress. If there is no commonly usable compression algorithm, the primary storage 200 performs only decompression (step S103), and the secondary storage 400 performs recompression (step S104) using a compression algorithm that the secondary storage 400 can use. These processes are performed, for example, when the system is constructed or when replication is set up, and the notified compression algorithm of the secondary storage 400 is managed by the primary storage 200. After that, subsequent replication processes are executed periodically.

[0043] In the replication process, first, the primary storage 200 selects data to be replicated (step S101). For example, the difference from the previous replication may be selected as the target.

[0044] After step S101, the primary storage 200 reads the data selected as the target from the physical volume 211 (step S102), decompresses it based on a first compression algorithm (step S103), and recompresses it based on a second compression algorithm (step S104). Then, the compressed data generated by the recompression is transferred to the secondary storage 400 (1002).

[0045] The secondary storage 400 assigns a physical address to the compressed data received from the primary storage 200 (step S201), stores the data in the physical volume 411 (step S202), and notifies the primary storage 200 of the completion of copying (1004). Note that, although an example of a process for notifying completion of copying after storing in the physical volume 411 has been given here, it is also possible to configure the compressed data received from the primary storage 200 to be stored in a cache, the primary storage 200 to be notified of completion of copying, and then storage in the physical volume 411 to be performed. EXAMPLES

[0046] Fig. 8 is an explanatory diagram of the primary storage 200 in Example 2. As shown in Fig. 2, the primary storage 200 has a network interface 201, a logical volume 210, a physical volume 211, a first compression unit 220, a decompression unit 230, a logical / physical address management unit 240, and a compression method management unit 250, but does not have a second compression unit 231.

[0047] When the primary storage 200 of the second embodiment transmits data of the physical volume 211 to the secondary storage 400 to perform replication, the primary storage 200 reads the target compressed data 212 from the physical volume 211 and transmits it as is to the secondary storage 400. That is, in the second embodiment, the data for replication is transmitted in a state compressed by the first compression algorithm. The other operations are the same as those in the first embodiment, so the explanation will be omitted.

[0048] Fig. 9 is an explanatory diagram of the secondary storage 400 in the embodiment 2. As shown in Fig. 9, the secondary storage 400 has a network interface 401, a logical volume 410, a physical volume 411, a compression unit 420, a decompression unit 482, a selection unit 473, a logical / physical address management unit 480, and a compression method management unit 470.

[0049] When the network interface 401 receives the compressed data 212 from the primary storage 200, the compressed data 212 is stored as is in the physical volume 411 via the selection unit 473. The compressed data 212 is compressed by a first compression algorithm used by the primary storage 200.

[0050] For example, when an abnormality occurs in the primary storage 200 and the secondary storage 400 processes writing by the secondary site, the network interface 401 accepts a write request via the communication line 503 and writes the data to the logical volume 410. The data written to the logical volume 410 is compressed by the compression unit 420. At this time, the compression unit 420 uses a second compression algorithm. The compressed data is written to the physical volume 411 via the selection unit 473.

[0051] When processing a read request from the secondary site, the network interface 401 accepts a read request via the communication line 503 , and the compressed data is read from the physical volume 411 .

[0052] The read compressed data is decompressed by the decompression unit 482 to become decompressed data, and is written to the logical volume 410, thereby enabling a read response. The algorithm used for decompression differs depending on the compressed data read, but which algorithm is used can be determined by following a control signal 481 from the logical physical address management unit 480.

[0053] The logical physical address management unit 480 has a management table in which the logical addresses of the logical volume 410 are mapped to physical addresses stored in the physical volume 411. Each time data is written to the physical volume 411, a physical address 441 is generated and passed to the physical volume 411.

[0054] Furthermore, the logical physical address management unit 480 manages a flag that specifies a compression algorithm in association with the physical address. When reading from the physical volume 411, the logical physical address management unit 480 refers to the flag and notifies the decompression unit 482 of a control signal 481 that specifies the compression algorithm corresponding to the physical address.

[0055] The compression method management unit 470 manages the compression and decompression processing in the secondary storage 400. In the secondary storage 400, compression processing is not required during replication, and compression processing is performed when writing by I / O at the secondary site during failover. The compression method management unit 450 switches between processing during replication and processing during writing by I / O by sending a control signal 472 to a selection unit 473. In addition, the compression method of data written to the physical volume 411 is notified to the logical physical address management unit 480, and registered in the management table. It is also possible to simply perform compression processing during replication.

[0056] FIG. 10 is a sequence diagram explaining the replication processing operation in the second embodiment. First, the secondary storage 400 sends a primary storage storage method acquisition command to the primary storage 200 (1100). The primary storage 200 determines the compression algorithm of the data to be transferred in the same manner as in the first embodiment, and notifies the secondary storage 400 of the primary storage storage method, i.e., the compression algorithm used by the primary storage 200 (1101). In this embodiment, communication may be added to determine the compression algorithm of the data to be transferred by the secondary storage 400. These processes are performed, for example, when the system is constructed or when replication is set, and the notified compression algorithm of the primary storage 200 is managed by the secondary storage 400. Thereafter, the subsequent replication processes are performed periodically.

[0057] In the replication process, first, the primary storage 200 selects data to be replicated (step S301). For example, the difference from the previous replication may be selected as the target.

[0058] After step S301, the primary storage 200 reads the data selected as the target from the physical volume 211 (step S302), and transfers it to the secondary storage 400 (1102). If necessary, decompression and recompression (steps S103, S104) occur as in the first embodiment.

[0059] The secondary storage 400 assigns a physical address to the compressed data received from the primary storage 200 (step S401). Since this is a write by replication, the logical physical address management unit 480 associates a flag indicating that this is the compression method used by the primary storage (step S402). After that, the data is stored in the physical volume 411 (step S403), and the primary storage 200 is notified of the completion of copying (1104). Note that, although an example of a process for notifying completion of copying after storing in the physical volume 411 has been given here, it is also possible to configure the compressed data received from the primary storage 200 to be stored in a cache, the primary storage 200 to be notified of completion of copying, and then storage in the physical volume 411 to be performed.

[0060] 11 is an explanatory diagram of the operation of the logical physical address management unit 480 in the embodiment 2. When a write occurs to the physical volume 411, the logical physical address management unit 480 judges whether or not it is due to replication (step S501).

[0061] If it is a write by replication (step S501; Yes), the logical / physical address management unit 480 selects the primary storage storage method, that is, the compression algorithm used by the primary storage 200 (step S502). If the write is not due to replication (step S501; No), the logical / physical address management unit 480 selects the secondary storage storage method, that is, the compression algorithm used by the secondary storage 400 (step S503).

[0062] The logical / physical address management unit 480 associates a flag that specifies the selected storage method with the physical address, and manages the correspondence between the logical address and the physical address (step S504).

[0063] (Modification) Next, variations in the system configuration will be described. 12 shows a first modified example of the system configuration. In the configuration shown in FIG. On the other hand, in the configuration shown in FIG. 12, the secondary storage 700 has a processor 701, a memory 702, and a storage medium 703, but does not have a compression / decompression accelerator, and the processor 701 performs compression and decompression by software processing.

[0064] In this way, the primary storage 600 is equipped with a processor 601 that handles reading and writing by the primary site, and a compression / decompression accelerator 602 that handles compression and decompression, thereby achieving high performance, whereas the secondary storage 700 is configured to process compression and decompression using software, thereby reducing costs. Therefore, there are differences in configuration and performance between the primary storage 600 and the secondary storage 700, but the present invention can be applied even in such a configuration. For example, when the primary storage 600 performs a lot of compression and decompression processing as in the first embodiment, the high performance can be utilized to perform decompression and recompression of data for replication. Also, when the secondary storage 700 performs a lot of compression and decompression processing as in the second embodiment, the system can be configured so that the secondary storage has high performance.

[0065] Fig. 13 shows a second modified example of the system configuration. In the configuration shown in Fig. 13, the configuration of the primary storage 600 is the same as that in Fig. 12, but the secondary site side is realized by software-defined storage using the cloud 530. In such a configuration, it is easy to add functions to the secondary storage side, and it is possible to use a compression algorithm that is not supported by the primary storage 600, but replication using compressed data can be realized by decompressing data compressed in the primary storage side as necessary on the secondary storage side.

[0066] As described above, the data replication system disclosed in the embodiments comprises a first storage system having a processor and providing a primary site, and a second storage system having a processor and providing a secondary site, wherein the first storage system compresses data related to reading and writing by the primary site and stores it in a first physical volume, and the second storage system compresses data related to reading and writing by the secondary site and stores it in a second physical volume, and when performing replication in which data stored in the first physical volume of the first storage system is transferred to the second storage system and stored in the second physical volume, the first storage system and the second storage system determine a compression method to be applied to the data to be transferred based on a compression method executable by the first storage system and a compression method executable by the second storage system, and transfer the data to be transferred compressed using the determined compression method. This configuration and operation makes it possible to reduce the amount of communication between storage systems that use different compression methods. In addition, the second storage system does not need to expand and recompress the data received during replication, which reduces the demands on processing performance.

[0067] Furthermore, according to the configuration of the first embodiment, the first storage system determines a compression method for the data to be transferred, reads the compressed data to be transferred from the first physical volume and performs decompression processing, compresses the decompressed data using the determined compression method for the data to be transferred and transfers it to the second storage system, and the second storage system receives the data compressed using the second compression method and stores it in the second physical volume. Therefore, the processing load on the second storage system can be kept low, and there is no need for the second storage system to be compatible with the compression method used in the first storage system. Furthermore, in the case where the compression method of the data stored in the first storage system cannot be implemented in the second storage system, the decompression and compression may be performed.

[0068] Furthermore, according to the configuration of the second embodiment, when the first storage system decides to transfer the data to be transferred using the compression method in which the data is stored, the first storage system reads the data to be transferred from the first physical volume and transmits it to the second storage system in the compressed state, and the second storage system receives the compressed data and stores it in the second physical volume, and when it becomes necessary to read or write the data, performs decompression processing corresponding to the first compression method. Therefore, the processing load on the first storage system can be kept low, and there is no need for the first storage system to be compatible with the compression method used in the second storage system. Furthermore, the expansion of data related to replication is limited to cases where reading becomes necessary due to the occurrence of an abnormality or the like. The second storage system can also decompress the received compressed data, compress it using a different compression method, and store it in the second physical volume. Furthermore, the second storage system may be configured to receive the compressed data and store it in the second physical volume, and when a write to the data occurs, to decompress the compressed data, compress it using a different compression method, and store it in the second physical volume.

[0069] In addition, in the configuration of Example 1, the first storage system can support a plurality of compression methods, and can be configured to select the compression method used in the second storage system as the replication destination, and transmit data compressed using that compression method. This allows for flexible processing suited to the configuration of the second storage system. Furthermore, when the second storage system that is the replication destination is compatible with a plurality of compression methods, the compression method to be applied when transmitting the data to be transferred to the second storage system may be determined based on the compression method applied when the data to be transferred is stored in the first physical volume. For example, if the compression method applied when storing the data in the first physical volume is also usable in the second storage system, the data to be transferred can be transmitted while being compressed using the first compression method.

[0070] Furthermore, the first storage system may separately comprise a processor that processes reading and writing by the primary site, and a processing unit that processes compression and decompression. With this configuration, it is possible to achieve both high processing performance at the main site and overall cost reduction.

[0071] Furthermore, the second storage system may be a software-based storage system made up of a plurality of servers. In this configuration, the second storage system can be operated flexibly and at low cost.

[0072] The present invention is not limited to the above-mentioned embodiment, and includes various modified examples. For example, the above-mentioned embodiment has been described in detail to explain the present invention in an easy-to-understand manner, and is not necessarily limited to those having all of the described configurations. Furthermore, it is possible to replace or add configurations, not to limit the deletion of such configurations. [Explanation of symbols]

[0073] 10: primary volume, 11: secondary volume, 100: primary server, 200: primary storage, 201: network interface, 210: logical volume, 211: physical volume, 212: compressed data, 220: first compression unit, 230: decompression unit, 231: second compression unit, 232: compressed data, 235: decompressed data, 240: logical physical address management unit, 241: physical address, 250: compression method management unit, 251: compression method designation signal, 252: compression method designation signal, 300: secondary server, 400: secondary storage, 401: network interface, 410: logical volume, 411: physical volume, 420: second compression unit, 420: compression unit , 430: decompression unit, 440: logical / physical address management unit, 441: physical address, 450: compression method management unit, 452: control signal, 453: selection unit, 470: compression method management unit, 472: control signal, 473: selection unit, 480: logical / physical address management unit, 481: control signal, 482: decompression unit, 500: communication line, 501: communication line, 502: communication line, 503: communication line, 510: network, 520: network, 530: cloud, 600: primary storage, 601: processor, 602: compression / decompression accelerator, 603: memory, 604: storage medium, 700: secondary storage, 701: processor, 702: memory, 703: storage medium

Claims

1. A storage system having a processor and communicably connected to other storage systems via a network, the storage system compresses data using a first compression method and stores the data in a first physical volume; the storage system and the other storage system configure a replication in which data stored in the first physical volume of the storage system is compressed and transferred to the other storage system via the network, and the compressed data is stored in a second physical volume of the other storage system; When setting the replication, the storage system determines, based on a compression method executable by the storage system and a compression method executable by the other storage system, whether the compression method for the data to be transferred is the first compression method that compresses the data in the first physical volume or a second compression method different from the first compression method; When data stored in the first physical volume of the storage system is transferred to the other storage system by the replication, When the storage system determines the compression method to be the first compression method in the replication, it transfers the data without decompressing or compressing it, and when the storage system determines the compression method to be the second compression method, it reads the compressed data to be transferred from the first physical volume, performs decompression processing, compresses the decompressed data using the second compression method, and transfers the data to be transferred. A storage system comprising:

2. The other storage system receives the compressed data and stores it in a second physical volume of the other storage system, and when it becomes necessary to read or write the data, reads it from the second physical volume and performs decompression processing.

2. The storage system according to claim 1.

3. The storage system includes a processor for reading and writing data, and a processing unit for compressing and decompressing data.

2. The storage system according to claim 1, wherein the other storage system is a software-based storage system made up of a plurality of servers.

4. A data processing method for a storage system having a processor and communicably connected to another storage system via a network, comprising: the storage system compresses data using a first compression method and stores the data in a first physical volume; the storage system and the other storage system configure a replication in which data stored in the first physical volume of the storage system is compressed and transferred to the other storage system via the network, and the compressed data is stored in a second physical volume of the other storage system; When setting the replication, the storage system determines, based on a compression method executable by the storage system and a compression method executable by the other storage system, whether the compression method for the data to be transferred is the first compression method that compresses the data in the first physical volume or a second compression method different from the first compression method; When data stored in the first physical volume of the storage system is transferred to the other storage system by the replication, if the storage system determines the compression method to be the first compression method in the replication, the data is transferred without being decompressed or compressed, and if the storage system determines the compression method to be the second compression method, the compressed data to be transferred is read from the first physical volume and decompressed, and the decompressed data is compressed by the second compression method, and the data to be transferred is transferred.

23. A data processing method for a storage system comprising:

Images