Remote copy with worm guarantee
First Claim
1. A remote copy system comprising:
- a first storage system including at least one first disk drive and a first control apparatus for controlling to store data in the first disk drive, the data being sent from at least one of a plurality of client systems, the first disk drive being related to a primary volume in the first storage system; and
a second storage system including at least one second disk drive and a second control apparatus for controlling to store data in the second disk drive, the data being sent from at least one of a plurality of client systems, the second disk drive being related to a secondary volume in the second storage system,wherein, if the primary volume and the secondary volume are set into remote copy pair to execute a remote copy between the primary volume and the secondary volume, attribute information of the primary volume indicating that data stored in the primary volume cannot be updated and can be referred to is set and stored to the second storage system to be applied as attribute information of the secondary volume, indicating that data stored in the secondary volume cannot be updated and can be referred to,wherein the second control apparatus has a command queue configured to queue a remote copy command received from the first storage system and write command received from one of the plurality of client systems to the secondary volume,wherein the second control apparatus determines whether a command extracted from the command queue is the remote copy command from the first control apparatus, by specifying an identifier of a source apparatus sending the command, the second control apparatus controls to store data in the secondary volume according to the remote copy command, and if the command extracted from the queue is the write command from at least one of the plurality of client systems, by specifying an identifier of the source apparatus sending the command, the second control apparatus controls so as to not store data in the secondary volume according to the write command, in order to guarantee that the data has not been falsified by at least one of the plurality of client systems,wherein the first control apparatus stores an event log of setting the attribute information to the second storage system, indicating that data stored in the secondary volume cannot be updated and can be referred to, after the setting of the attribute information to the second storage system, andwherein the first control apparatus sends the event log of setting the attribute information to the second storage system, to the second storage system, and instructs to store the event log in the second storage system, in order to keep consistency of the event log stored in the first storage system and the second storage system.
0 Assignments
0 Petitions
Accused Products
Abstract
In the case in which data in a storage system A is remotely copied to a storage system B, it is not taken into account whether the data of the remote copy is WORM data. In the case in which a setting is made such that data stored in a volume in the storage system A is copied to a volume in the storage system B, storage system A judges whether an attribute to the effect that data can be referred to and can be updated or to the effect that data can be referred to but cannot be updated is added to the volume in the storage system A. Then, if the volume is a volume to which the attribute to the effect that data can be referred to but cannot be updated is added, such attribute is added to the volume in the storage system B.
33 Citations
16 Claims
-
1. A remote copy system comprising:
-
a first storage system including at least one first disk drive and a first control apparatus for controlling to store data in the first disk drive, the data being sent from at least one of a plurality of client systems, the first disk drive being related to a primary volume in the first storage system; and a second storage system including at least one second disk drive and a second control apparatus for controlling to store data in the second disk drive, the data being sent from at least one of a plurality of client systems, the second disk drive being related to a secondary volume in the second storage system, wherein, if the primary volume and the secondary volume are set into remote copy pair to execute a remote copy between the primary volume and the secondary volume, attribute information of the primary volume indicating that data stored in the primary volume cannot be updated and can be referred to is set and stored to the second storage system to be applied as attribute information of the secondary volume, indicating that data stored in the secondary volume cannot be updated and can be referred to, wherein the second control apparatus has a command queue configured to queue a remote copy command received from the first storage system and write command received from one of the plurality of client systems to the secondary volume, wherein the second control apparatus determines whether a command extracted from the command queue is the remote copy command from the first control apparatus, by specifying an identifier of a source apparatus sending the command, the second control apparatus controls to store data in the secondary volume according to the remote copy command, and if the command extracted from the queue is the write command from at least one of the plurality of client systems, by specifying an identifier of the source apparatus sending the command, the second control apparatus controls so as to not store data in the secondary volume according to the write command, in order to guarantee that the data has not been falsified by at least one of the plurality of client systems, wherein the first control apparatus stores an event log of setting the attribute information to the second storage system, indicating that data stored in the secondary volume cannot be updated and can be referred to, after the setting of the attribute information to the second storage system, and wherein the first control apparatus sends the event log of setting the attribute information to the second storage system, to the second storage system, and instructs to store the event log in the second storage system, in order to keep consistency of the event log stored in the first storage system and the second storage system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A remote copy method in a first storage system including at least one first disk drive and a first control apparatus for controlling to store data in the first disk drive, the data being sent from at least one of a plurality of client systems, the first disk drive being related to a primary volume in the first storage system;
- and a second storage system including at least one second disk drive and a second control apparatus for controlling to store data in the second disk drive, the data being sent from at least one of a plurality of client systems, the second disk drive being related to a secondary volume in the second storage system, the method comprising;
executing a remote copy between the primary volume and the secondary volume, setting and storing attribute information of the primary volume, the attribute information indicating that data stored in the primary volume cannot be updated and can be referred to, to said second storage system to be applied as attribute information of the secondary volume indicating that data stored in the secondary volume cannot be updated and can be referred to, queuing a remote copy command received from the first storage system and write command received from one of the plurality of client systems, and extracting a command from the command queue and determining whether the extracted command is the remote copy command from the first control apparatus, by specifying an identifier of a source apparatus sending the command, storing the data in the secondary volume according to the remote copy command, and if the extracted command is the write command from at least one of the plurality of client systems, by specifying an identifier of the source apparatus sending the command, not storing data in the secondary volume according to the write command, in order to guarantee that the data has not been falsified by at least one of the plurality of client systems, wherein the first control apparatus stores an event log of setting the attribute information to the second storage system, indicating that data stored in the secondary volume cannot be updated and can be referred to, after the setting of the attribute information to the second storage system, and wherein the first control apparatus sends the event log of setting the attribute information to the second storage system, to the second storage system, and instructs to store the event log in the second storage system, in order to keep consistency of the event log stored in the first storage system and the second storage system. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
- and a second storage system including at least one second disk drive and a second control apparatus for controlling to store data in the second disk drive, the data being sent from at least one of a plurality of client systems, the second disk drive being related to a secondary volume in the second storage system, the method comprising;
Specification