• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    A data storage facility for transferring data from a data altering apparatus, such as a production data processing site to a remote data receiving site. The data storage facility includes a first data store for recording each change in the data generated by the data altering apparatus. A register set records each change on a track-by-track basis. A second data store has first and second operating modes. During a first operating mode the second data store becomes a mirror of the first data store. During a second operating mode the second data store ceases to act as a mirror and becomes a source for a transfer of data to the data receiving site. Only information that has been altered, i.e., specific tracks that have been altered, are transferred during successive operations in the second operating mode. Commands from the local production site initiate the transfers between the first and second operating modes.
    公开号:US20010007102A1
    申请号:US09/740,281
    申请日:2000-12-19
    公开日:2001-07-05
    发明作者:Mathieu Gagne；Yuval Ofek
    申请人:EMC Corp；
    IPC主号:G06F11-2082
    专利说明:
    [0001] U.S. Letters Patent Ser. No. 08/656,035 filed May 31, 1996 for a Method and Apparatus for Independent Operation of a Remote Data Facility which application is assigned to the Same Assignee as this application. [0001]
    [0002] U.S. Letters Patent Ser. No. 08/842,953 filed Apr. 25, 1997 by Yuval Ofek for a Method and Apparatus for Independent and Simultaneous Access to a Common Data Set, which application is assigned to the same Assignee as this application. [0002] BACKGROUND OF THE INVENTION
    [0003] 1. Field of the Invention [0003]
    [0004] This invention generally relates to redundant data storage devices in a data processing network and more particularly to a method and apparatus that enables data to cascade through multiple redundant data storage units. [0004]
    [0005] 2. Description of Related Art [0005]
    [0006] The maintenance of data integrity by data redundancy has become a very important issue. Data redundancy has several forms or variations. At a single site, mirroring or RAID redundancy protects against disk or other storage failure. In another form described in U.S. Letters Patent Ser. No. 08/656,035 filed May 31, 1996 and others, redundancy is achieved by duplicating a local system at a remote location. The use of a remote location prevents data loss due to natural disasters and the like at one site. [0006]
    [0007] In accordance with the foregoing U.S. Letters Patent Ser. No. 08/656,035, all data processing activity occurs at a “local” or “production” site that contains a host system for processing data stored in a data storage facility. A geographically remote or backup site includes a data storage facility as a “redundant” facility for maintaining a restoration or recovery data set. In this system each time the host at the production site writes data to the production site data storage facility, the production data storage facility automatically writes data to the remote storage facility. In many, if not most, of these applications, writing data to the remote site data storage facility requires a transfer across a high bandwidth communications link so the backup procedure does not affect operations at the production facility. T3 and ESCON lines are typically preferred as the communications links despite their expense. [0007]
    [0008] U.S. Letters Patent Ser. No. 08/842,953 discloses another concept involving a BCV device typically used at the production site. In this approach a data set, for example a “logical volume”, on a production site data storage facility, i.e., a “production volume”, operates in a normal fashion. Another logical volume at this same site is designated as a “BCV volume”. An ESTABLISH command connects the BCV volume to the production volume so that the BCV volume synchronizes with the production volume. A SPLIT command thereafter can separate the BCV volume from the production volume making the data stored on the BCV volume available for another application. [0008]
    [0009] This other application may alter the data stored on the BCV volume. Consequently whenever the BCV volume is reconnected with the production volume, it is necessary to transfer data to the BCV volume that represent changes in both the BCV volume and the production volume. An alternative is to reconnect the BCV volume to the production volume by issuing another ESTABLISH command. However, this command will replace all the data on the BCV volume so all the data from the production volume must be transferred to the BCV volume whether or not changes have occurred. [0009]
    [0010] In the past locating data storage facilities at a production site and a single remote site has been acceptable. In certain critical applications it is now also desirable, and in some situations mandatory, to store still another restoration copy at a third site that is remote from the first two sites. This requires some approach for copying the data from the production site to both remote sites, all transparently to the operations at the production site. Merely repeating the foregoing approach for copying data from a production site to a single remote site involves excessive communications costs. A second high-speed communications link will be required between either the production site and the second remote site or between the first and second remote sites. What is needed is a way to establish a redundant data copy over a less costly communications link without any significant disparity in the data that exists at various remotely located sites such that all the data storage facilities are in synchronism or nearly in synchronism. [0010] SUMMARY
    [0011] Therefore it is an object of this invention to provide a method and apparatus for establishing redundant data storage facilities that can communicate over less costly communications links. [0011]
    [0012] Another object of this invention is to provide a method and apparatus for achieving redundant disk storage at geographically remote sites on an economical basis. [0012]
    [0013] Still another object of this invention is to provide a method and apparatus for providing redundant data storage at two or more geographically remote sites using an economical communications link. [0013]
    [0014] Yet another object of this invention is to provide a method and apparatus for providing redundant data storage at two or more geographically remote sites using an economical low-bandwidth communications link. [0014]
    [0015] Yet still another object of this invention is to provide a data processing network in which data processed at a production site is stored at two or more redundant storage sites with redundancy being achieved transparently to operations at the production site. [0015]
    [0016] In accordance with this invention, a data storage site remote from a data processing facility that alters data, such as a production facility, transfers data to another site remote from the data storage facility. The data storage facility at the remote site includes first and second data stores. The first data store receives data from the production site. A data change recorder identifies changes that the data processing facility makes in the first data store. A first operating control establishes a first operating mode during which the second data store receives data from the first data store according to the changes recorded in said change recording means. After this operation is complete, a second operating control can establish a second operating mode for copying data from the second data store to the other remote site according to the changes recorded in said data change recorder. [0016]
    [0017] In accordance with another aspect of this invention, data is transferred between a production site and a remote site. The production site includes a host and production storage facility; the remote site, a remote storage facility including a first data store and a second data store wherein the first data store receives data from the production facility on a track-by-track basis. The host can issue a plurality of cascade commands to enable the definition of a plurality of track status tables for identifying each track in the first data store that the production facility changes. In addition, the host can establish first and second operating modes. In the first operating mode the second data store receives data from the first data store according to the changes recorded in the track status tables. During the second operating mode data from the second data store is copied to the remote storage facility according to the changes recorded in the track status tables at the time the second mode is established. [0017] BRIEF DESCRIPTION OF THE DRAWINGS
    [0018] The appended claims particularly point out and distinctly claim the subject matter of this invention. The various objects, advantages and novel features of this invention will be more fully apparent from a reading of the following detailed description in conjunction with the accompanying drawings in which like reference numerals refer to like parts, and in which: [0018]
    [0019] FIG. 1 is a block diagram of a data processing network including a production facility and two geographically remote facilities; [0019]
    [0020] FIG. 2 is a flow diagram that illustrates the transfer of commands from a production facility to a remote storage facility; [0020]
    [0021] FIG. 3 depicts the operation of the network in FIG. 1 in response to a DIFFERENTIAL SPLIT command; [0021]
    [0022] FIG. 4 depicts details of a procedure used in the operation depicted in FIG. 3; [0022]
    [0023] FIG. 5 depicts the operation of the network in FIG. 1 in response to a RE-ESTABLISH command; and [0023]
    [0024] FIG. 6 depicts another operation that occurs after processing a DIFFERENTIAL SPLIT command. [0024] DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS General Operation
    [0025] FIG. 1 depicts a data processing network [0025] 20 with equipment located at a local or production site 21, a first remote site 22 and a second remote site 23. The first and second remote sites 22 and 23 typically will be geographically remote from the local production site 21 and from each other. However, as will become apparent, the equipment at the local production site 21 and first remote site 22 could be collocated.
    [0026] A first level of redundancy is achieved in the data processing network [0026] 20 through interactions between the local production site 21 and the first remote site 22. As known, a host 24, that includes one or more central processors and a main memory, operates on various programs. Periodically the host 24 will effect a transfer through a host adapter 25 to a disk storage device. This disk storage device may have many physical disk drives organized into discrete sections for storing related information. These include files or other data blocks. In the context of the equipment manufactured by the assignee of this invention, a typical storage section is a logical volume comprising a number of contiguous disk tracks and transfers are made on a track-by-track basis. In FIG. 1 an R1 logical volume 26 is representative of the many logical volumes that normally are included in such a disk storage facility. As will also be apparent the host 24 retrieves any information it needs from such a production storage facility through the host adapter 25. Such systems are well known in the art. U.S. Letters Patent Ser. No. 08/656,035 describes one such system.
    [0027] Although not shown, the local production site [0027] 21 may provide redundancy for the R1 logical volume 26. For example, the R1 volume may actually be mirrored or constituted by an array of logical volumes in any one of various RAID configurations thereby to prevent failure of a particular physical disk drive from interrupting operations by the host 24. As will become apparent, this invention can be applied notwithstanding any redundancy scheme implemented at the local production site 21.
    [0028] As is also known in the prior art and described in U.S. Pat. No. 5,544,347 to Yanai et al. and assigned to the same assignee of this invention, discloses another redundancy scheme that can be implemented by mirroring the data in the R1 logical volume [0028] 26 at the first remote site 22. More specifically in this configuration the local production site 21 includes a remote adapter (RA) 27 that connects through a high speed communications link, such as an ESCON or T3 communications line, to a corresponding remote adapter 31 in the first remote site 22. In this configuration each time the host 24 writes data to the R1 logical volume 26, the remote adapter 27 responds by transferring that data through the high speed communications link to the remote adapter 31 in the first remote storage site 22 for transfer to an R2 logical volume 32. Thus each WRITE operation is reflected or conveyed to the R2 logical volume 32 that acts as a remote mirror with respect to the R1 logical volume 26. If a natural disaster strikes the local production site 21, the data is readily available in the R2 logical volume at the remote site. Moreover if a host 33 is located in the first remote site 22, it is possible for all operations to shift to the first remote site for continued operation without any undetected data losses.
    [0029] As previously stated, U.S. patent application Ser. No. 842,953 discloses a data processing network that includes a BCV logical volume associated with a data storage facility. In accordance with this invention, a BCV/R1 logical volume [0029] 34 is included in the first remote site 22. It can comprise any dedicated logical volume within the first remote site 22 preferably on a physical disk drive that is different from the physical disk drive that contains the R2 logical volume 32.
    [0030] In accordance with this invention and as described in more detail later, the BCV/R1 logical volume [0030] 34 can be connected either to the R2 logical volume 32 or to a remote adapter 35. In a first operating mode, the BCV logical volume 34 synchronizes with the R2 logical volume 32. In a second operating mode with the BCV/R1 logical volume 34 attached to the remote adapter 35, data will transfer over another communications link 36 to a remote adapter 37 in the second remote site 23 for transfer to an R2 logical volume 40 or other data receiver. In one embodiment of this invention, the second remote site 23 contains a host 41 and eliminates the need for the existence of the host 33 at the first remote site 22. Thus the second remote site 23 becomes the restoration site or secondary site for operating on the data if a natural disaster occurs at the local production site 21.
    [0031] The second remote site is shown as containing an optional BCV/R1 logical volume [0031] 42. As described more fully later, including this logical volume at the second remote site 23 could allow a replication of the function performed in accordance with this invention to a third remote site.
    [0032] In general terms, a remote site constructed in accordance with this invention will have the basic structure of the first remote site [0032] 22 that constitutes a data storage facility. It includes a first data store in the form of the R2 logical volume 32 for connection to the local production site 21 that can alter data. The BCV/R1 logical volume 34 constitutes a second data store. In response to a first command, the data store facility in the first remote site 22 operates in a first operating mode during which the R2 logical volume 32 receives data from the remote adapter 31 and thereby is responsive to changes made to the data in the R1 logical volume 26. Typically this is accomplished synchronously so a high-speed communications link 30 is necessary. In this operating mode the BCV/R1 logical volume 34 is considered to be operating in its BCV or first operating mode.
    [0033] In accordance with this invention, the BCV/R1 logical volume [0033] 34 can shift to a second, or R1, operating mode once synchronism is achieved in the first operating mode. In the second operating mode the first remote site transfers data from the BCV/R1 logical volume 34 through the remote adapter 35, communications link 36 and remote adapter 37 to the R2 logical volume 40. The timing of shifts from the first to the second operating modes will be determined by a system operator. However, shifts from the second operating mode to the first operating mode will generally be made after the data transfer to the R2 logical volume 40 is complete. Typically the interval between shifts to the second operating mode will be in terms of minutes, hours or even days depending upon the activity in the R2 logical volume 32.
    [0034] Still in accordance with this invention, each time the BCV/R1 logical volume [0034] 34 shifts to its second operating mode, only the data tracks that have been altered during the first operating mode are transferred to the R2 logical volume 40. If the local production site 21 makes repeated changes to a single track of the R2 logical volume 32 between successive shifts to the second operating mode, only one transfer will occur from the BCV/R1 logical volume 34 to the R2 logical volume 40. Such a reduction can lead to a reduction in the bandwidth requirements on the communications link 36. For example, it may be possible to reduce the communications link 36 to a level that will allow transfers over low bandwidth telephone lines or the Internet.
    [0035] Thus in accordance with this invention data changes made to the R1 logical volume [0035] 26 are replicated in the R2 logical volume 32 and then through the BCV/R1 logical volume 34 to the R2 logical volume 40. This process of sequentially transferring the data is characterized as cascading and is controlled by a cascade command set processed by the host 24 at the local or production site 21. Cascade Command Processing
    [0036] More specifically, the system operator or an application program being processed at the local production site [0036] 21 can effect the cascading operation being performed at the first remote site 22. As known, the host 24 in FIG. 1 will produce various commands including commands in the cascade command set. These commands can be directed to any number of device or addresses including the host adapter 25.
    [0037] Now referring to FIGS. 1 and 2, when the host adapter [0037] 25 receives a command, step 44 uses a conventional process to test and decode the command. The test analyzes syntax, context and other related parameters to determine whether a correct command has been received. Step 45 determines whether the command is one of commands in the cascade command set, that is, a cascade command. If it is not, the host adapter 25 uses a procedure 46 to implement a corresponding function. When a valid cascading command is received, the host adapter 25 uses step 47 to transfer the command to the remote adapter 27.
    [0038] When the remote adapter [0038] 27 receives a command at step 50, step 51 merely transfers the command over the communications link 30 to the remote adapter 31 without any further analysis. The remote adapter 31 performs a similar process. That is, the remote adapter 31 receives the command in step 52 and uses step 53 to transfer the command to the device controller 43.
    [0039] After the device controller [0039] 34 receives the command from the remote adapter 31 in step 54, the device controller 34 decodes the command in step 55 and processes that command in step 56.
    [0040] When the operation defined by the cascade command or other command has been completed, the device controller [0040] 43 generates an acknowledgement in step 60 for transfer to the remote adapter 31; steps 61, 62 and 63 represent the process for transferring that acknowledgement back across the communications link to the remote adapter 27 and the host adapter 25 for transfer to the host 24.
    [0041] Thus, this process allows a program running in the host [0041] 24 to issue commands to the device controller 43 in the first remote site that in turn controls the operation of the BCV/R1 logical volume 34. Steps 60 through 63 then provide the necessary feedback so that the host is aware of the completion of any such operation. As a result, there is no requirement for a host such as host 33 in FIG. 1, at the first remote site to implement this invention. First Remote Site 22
    [0042] Referring again to FIG. 1, the first remote site [0042] 22 includes a number of status registers and tables and program modules for implementing this invention. A control module 70 includes modules for processing various commands including commands in the cascade command set including an EST module 71 for processing an ESTABLISH command, a DS module 72 for processing a DIFFERENTIAL SPLIT command and an REEST module 73 for processing a REESTABLISH command. The ESTABLISH and REESTABLISH commands also perform functions independently of a cascading operation.
    [0043] Each of the logical volumes includes a dedicated portion for maintaining information about the status of individual physical cylinders and tracks within those cylinders for a device. One such portion of the R2 logical volume [0043] 32 is constituted by a dedicated portion 74 that contains a status word for each track. Each status word contains information about the track and dedicates a number of bit positions that are available for various status functions. One of those bit positions will be assigned for use in the cascading process and that bit position will be replicated as a Protection Bits Table 75 that is a 1×n table where n equals the number of tracks in the R2 logical volume 32.
    [0044] The first remote site [0044] 22 also includes an R2 track status table 76 and a BCV/R1 track status table 77. Each of the track status tables 76 and 77 includes a plurality of rows, specifically four rows assigned to four mirror devices or volumes. In normal operations when the BCV/R1 logical volume 34 attaches to the R2 logical volume 32, the bit positions in the M1 row of the R2 track status table 76 correspond to tracks in the R2 logical volume 32; the bit positions in the M2 row, to tracks in the R1 logical volume 26; and bit positions in the M3 row, to tracks in the BCV/R1 logical volume 34 acting in its BCV operating mode. Similarly the BCV/R1 track status table 77 includes a plurality of mirror rows including bit positions in an M1 row for identifying track status for the BCV/R1 logical volume 34 and bit positions in the M2 row for the R2 logical volume 40.
    [0045] A PB bit register [0045] 80 identifies a selected bit position in the Protection Bit table 75 that will be used during a cascading operation. A session flag 81 indicates whether the system is operating in response to cascade commands. A copy program 82 copies data to and from different logical volumes in the first remote site 22 facility as described more fully later. Operation—First Operating Mode
    [0046] The first remote site [0046] 22 initially will be configured to operate in a first operating mode during which the copy program 82 copies data from the first data store in the form of the R2 logical volume 32 to the second data store in the form of the BCV/R1 logical volume 34 according to changes received at the remote adapter 31. This configuration remains in place until such time as the data on BCV/R1 logical volume 34 is identical to the data stored on the R2 logical volume 32; that is until the two logical volumes are synchronized. Thereafter the first operating mode maintains that synchronism. Operation—Second Operating Mode
    [0047] At any time after such synchronism has been achieved, a second operating mode can be established when the host [0047] 24 issues a DIFFERENTIAL SPLIT cascade command. Alternatively an optional host 33 at the first remote site could also generate such a command. Issuing the command begins a cascade session.
    [0048] In response, the device controller [0048] 43 will isolate the BCV/R1 logical volume 34 from the R2 logical volume 32 and enable the copy program 82 in FIG. 1 to transfer data from the BCV/R1 logical volume 34 through the remote adapter 35 to a data receiving device as represented by the second remote site 23 in FIG. 1 including the R2 logical volume 40. At any time after those two volumes are synchronized, a REESTABLISH command will revert the system to the first operating mode by detaching the BCV/R1 logical volume 34 from the remote adapter 35 and reattaching it to the R2 logical volume 32 after which the copy program 82 will resynchronize the BCV/R1 logical volume 34 to the R2 logical volume 32. The session continues by issuing subsequent DIFFERENTIAL SPLIT and REESTABLISH commands until a CLOSE SESSION command is generated.
    [0049] FIG. 3 depicts operation in response to the receipt of a DIFFERENTIAL SPLIT command in more detail. When the host adapter [0049] 25 recognizes that a differential command has been received in step 90, it tests the command for various possible error conditions as known and as described with respect to step 44 in FIG. 2. If any errors exist, the procedure aborts using a reporting procedure as known in the art. If no errors exist, control passes to step 92 that transfers the DIFFERENTIAL SPLIT command for transfer through the remote adapter 27, communications link 30 and the remote adapter 31 to enable the control 70 to respond.
    [0050] When the DIFFERENTIAL SPLIT (DS) module [0050] 72 responds in step 93, it performs a conventional locking operation to preclude any other applications from effecting the selected logical volume while the lock exists. Step 94 monitors the session flag 81 to determine if a cascading session is in progress. If this is the first differential split operation of a cascading operation, the session flag 81 indicates that the session is not in progress. Control passes to step 95 that establishes the protection bits table 75 based upon data stored at a predetermined location. For example, step 95 may retrieve a protection bits data file from a dedicated portion 74 in the R2 logical volume 32. Alternatively, step 95 may retrieve corresponding information from a copy of such a file that is maintained in memory. In whatever form, each entry corresponds to a track, and each entry contains a plurality of bit positions that can be assigned for arbitrary purposes. Step 95 selects an unused bit position from a table (not shown) identifying any valid uses of different bit positions to establish one bit position for the session that is beginning. Processes for selecting such a bit position are well known in the art. Then the DS module 72 records the selected bit position in PB BIT register 80.
    [0051] Step [0051] 96 represents a procedure for performing a conventional split operation using basic steps from a conventional module. Details of this operation are depicted in FIG. 4. Specifically, step 101 terminates the mirroring operation of the BCV/R1 logical volume 34 as a mirror for the R2 logical volume 32. This action prevents the copy program 82 from transferring data from the R2 logical volume 32 to the BCV/R1 logical volume 34. However, each transfer to the R2 logical volume 32 will be recorded in the M3 row of the R2 track status table 76 thereby to indicate a change in the R2 logical volume 26 that is not reflected in the BCV/R1 logical volume 34.
    [0052] Step [0052] 102 manages WRITE PENDING operations as described in the foregoing U.S. patent application Ser. No. 08/842,953. Next step 103 copies any identification tables from the R2 logical volume 32 to the BCV/R1 logical volume 34 so that the transfer of data from the first remote site 22 to the second remote site will include all the identification information. Step 104 then assigns the BCV/R1 logical volume 34 to copy data to the R2 logical volume 40 at the second remote site 23. This enables the copy program 82 to transfer data to the appropriate destination namely the R2 logical volume 40.
    [0053] When the operation of FIG. 4 completes, step [0053] 105 in FIG. 3 sets all the bits in the M2 bit position of the BCV/R1 track status table 77. Setting all the bits establishes an operating environment in which the data in all the tracks will be transferred to the R2 logical volume 40 in FIG. 1. Step 105 also sets the session flag 81 so it will be clear that during any subsequent DIFFERENTIAL SPLIT the alternate path described later is followed.
    [0054] Step [0054] 106 releases the lock. Step 107 initiates the copy program 82 that begins the transfer of data from the BCV/R1 logical volume 34 to the R2 logical volume 40 according to the data in the BCV/R1 track status table 77, particularly the information in the M3 row. As each copy operation occurs, the corresponding M2 bit in the BCV/R1 track status table 77 is cleared. When all the bits have been cleared, step 110 posts a complete status and a corresponding message is transferred back to the host adapter 25 thereby to indicate to the corresponding application program running in the host 24 that the transfer has been completed. Operation—Return to First Operating Mode
    [0055] At any time after all the data has been transferred to the R2 logical volume [0055] 40, the system operator can issue a REESTABLISH command that constitutes another cascade command. Step 112 in FIG. 5 represents receipt of that command in the host adapter 25. Step 113 represents the context and syntax testing of that command with the possibility of aborting the process if an error is detected. Otherwise the host adapter 25 uses step 114 to pass to the device controller 43 command for control transfer through the remote adapter 27 and communications link 30 to the remote adapter 31.
    [0056] The device controller [0056] 43 uses step 115 to indicate the receipt of such a command. Step 116 adds the BCV/R1 logical volume 34 as a local BCV mirror with the next available device mirror designation in the R2 track status table 76. In step 117 the device controller 43 sets the BCV/R1 logical volume 34 acting as a storage facility for the DIFFERENTIAL SPLIT operation to NOT READY (NR). This prevents the COPY program from copying any further data to the second remote site 23. Any WRITE PENDING operations are set to an INVALID state in step 118. As described in the foregoing application, setting any WRITE PENDING operations does not affect the data being stored. Step 120 then merges any bits in the R2 track status table 76 that have been in the mirrored position allocated to the BCV/R1 logical volume 34 (i.e., the M3 bits) with the bits in the M4 bit position for the BCV/R1 track status table 77. During other applications the M4 bit position normally records any changes that are made to the data of the BCV/R1 device. However, no such changes are made during a differential split command when the system operates in the second mode. Consequently step 120 merely obtains the bits in the M3 row of the R2 track status table 76 representing any changes made to the R2 logical volume 32 while the first remote site was operating in the DIFFERENTIAL SPLIT operating mode. Next step 121 releases the lock and step 122 posts a complete status that transfers back to the host adapter 25 to the host 24 in step 123. Now the copy program 82 becomes available for transferring data from the R2 logical volume 32 to the BCV/R1 logical volume 34 according to the contents of the M3 bit positions in the R2 track status register table 76. During each transfer the copy program 82 clears the corresponding bit in the M3 bit positions of the R2 track status register table 76. However, the corresponding bit position in the protection bits table 75 remains unchanged. Operation—Write to R2 Logical Volume 40
    [0057] During the interval in which the data storage facility at the first remote site [0057] 22 operates in the second operating mode copying data from the BCV/R1 logical volume 34 to the R2 logical volume 40, the host 24 can continue to issue writing operations to the R1 logical volume 26 and the R2 logical volume 32. The remote adapter 31 receives the WRITE data at step 130 at FIG. 6. The information is written immediately to the R2 logical volume 32 in step 131 and the corresponding entries in the R2 track status table 76 are updated in step 132. In this case, the corresponding track bit position in the M3 row would be updated to indicate that WRITE operation had caused a transfer to the R2 logical volume 32, but had not caused a corresponding change in the BCV/R1 logical volume 34. Next the system would look to the session flag 81 to determine if a cascade operation were underway. If it were, step 133 would transfer control to step 134 thereby to write the corresponding status to the Protection Bits Table 75, so that the Projection Bits Table 75 and the M3 row in the track status table 76 would have identical information. Step 134 is bypassed if a cascading operation is not underway. Step 135 then represents the process by which the control 70 completes the write operation. In the case of a normal operation the WRITE operation would complete by transferring the changed data to the BCV/R1 logical volume 34. If the BCV/R1 logical volume 34 were no longer attached, the WRITE request would be made a WRITE PENDING request. Operation—Successive Differential Split Operations
    [0058] After some additional time interval, that again may be defined by a system operator and measured in minutes, hours or days, host [0058] 21 issues another DIFFERENTIAL SPLIT command. When the device controller 43 receives that command, its control again transfers to the procedure set forth in FIG. 3. In this case, however, the session flag 81 is set so step 94 diverts to step 141 in a manner analogous to that described with respect to step 101 in FIG. 4, terminates the operation of the BCV/R1 logical volume 34 as a mirror to the R2 logical volume 32. This disables any further action of the copy program 82 for the purpose of transferring data from the R2 logical volume 32 to the BCV logical volume 34. Step 142, like step 102, manages all WRITE PENDING operations.
    [0059] Next, the DS module [0059] 72 uses step 143 to copy the Protection Bits Table 75 to the M2 row in the BCV/R1 track status table 77. Then the DS module 72 clears the Protection Bits Table 75. After these operations, the M2 bit positions in the BCV/R1 track status table 77 indicate those tracks in the R2 logical volume 32 that were altered subsequent to a last DIFFERENTIAL SPLIT request being processed. Clearing the protection bits in the protection bits table 75 assures that upon unlocking the logical volumes 32 and 34 any WRITE PENDING operations are properly recorded by setting an appropriate bit in the Protection Bits Table 75.
    [0060] Next control in the DS module [0060] 72 then shifts from step 143 to step 106 to release the lock applied in step 93 and to step 107 whereupon the copy program 82 is enabled to transfer data from the BCV/R1 logical volume 34 to the R2 logical volume 40. However, only data in changed tracks will be transmitted. That is, it is the nature of this command that all DIFFERENTIAL SPLIT operations after a first operation in a session transmit only incremental amounts of information corresponding to data in tracks that have been altered. Moreover the number of tracks of data actually transferred over the communications link 36 normally will be significantly less than the number of writing operations that occurs between successive DIFFERENTIAL SPLIT operations. For example, if during such an interval there have been ten writing operations to different areas on the same track of the R2 logical volume 32, the BCV/R1 device 34 will only contain the latest information and so only one track writing operation will be required to update the R2 logical volume 40 in the second remote site 23. When such repetitive writing operations occur to a single track, the bandwidth requirements for the communications link 36 can be dramatically reduced. It is generally found the requirements can be reduced sufficiently so at least the next lower level of communications bandwidth, such as a T1 line can be used. In many applications it may be possible to reduce the bandwidth requirement even further to a level at which the Internet can be used as a communications link 36.
    [0061] The sequence of DIFFERENTIAL SPLIT and REESTABLISH commands can continue on an iterative basis so long as it is desired to use the second remote site [0061] 23 as a repository for a redundant copy. Once there is no longer any need to maintain the redundant copy, the host can generate a predetermined CLOSE SESSION command. This cascade command releases the assignment of the PB bit position in register 80 and clears the session flag 81 to complete the cascading operation.
    [0062] This invention has been described in terms of a preferred embodiment in which a local production site [0062] 21 is representative of apparatus for periodically altering data in a production data storage facility. In accordance with this invention a first remote site includes a first data store for mirroring the data at the production site. A second data store in the form of the BCV/R1 logical volume 34 has two operating modes. In one, the BCV/R1 logical volume 34 acts as a mirror for the R2 logical volume 32. In the other mode instituted by issuing a DIFFERENTIAL SPLIT or equivalent command, the BCV/R1 logical volume 34 detaches from the R2 logical volume 32 and conveys data identified in the BCV/R1 track status table 77 to the R2 logical volume 40 or other means in the second remote site 23 that acts as a receiver for data from the BCV/R1 logical volume 34.
    [0063] A data change recording apparatus represented by the Protection Bits Table [0063] 75 records any changes to the R2 logical volume 32 while the contents of the BCV/R1 logical volume 34 are being transferred to the R2 logical volume 40 during the second operating mode. When control shifts the BCV/R1 logical volume 34 back to the first operating mode, the data change recording identifies those tracks or other data blocks that must be transferred from the R2 logical volume 32 to the BCV/R1 logical volume 34. This changed data recording further controls those tracks that are transferred from the BCV/R1 logical volume 34 to the data receiving site such as the second remote site 23 when the system again shifts the operation of the BCV/R1 logical volume 34 to the second operating mode.
    [0064] There are many variations that can be made to the specifically disclosed embodiment shown in FIGS. 1 through 6. FIG. 1 for example, depicts a specific organization of tables and modules. It will be apparent that different configurations of the information could be substituted without detracting from the overall operation of the first remote site [0064] 22. FIGS. 1 through 6 further depict the operation in conjunction with a single logical volume. Generally a network will include multiple logical volumes, each of which could be handled in this same way by replicating the operation and apparatus shown in FIGS. 1 through 6. Moreover, the description of the various modules establishes specific sequences of events for purposes of explanation; other sequences might also be included with the elimination of some or addition of other operations such as are necessary for other ancillary operations. Such sequences can be under manual control so that each transfer between operating modes will be initiated by a system operator. Alternatively, all or portions of a cascading session might be under automatic control. Thus while this invention has been disclosed in terms of certain embodiments, it is the intent of the appended claims to cover all such variations and modifications as come within the true spirit and scope of this invention.
    权利要求:
    Claims (36)
    [1" id="US-20010007102-A1-CLM-00001] 1. A data network with means for altering data and means for receiving data in a data processing system, said data network comprising:
    A) a first data store for connection to the data altering means for receiving data therefrom,
    B) a second data store,
    C) first and second change recording means for identifying the location of any change that the data altering means makes in said first data store,
    D) first operating means for establishing a first operating mode during which said second data store receives data from said first data store according to the changes recorded in said first change recording means,
    E) second operating means for establishing a second operating mode for copying data from said second data store to the receiving means according to the changes recorded in said second change recording means that reflect the recorded changes in said first data store at the time the second mode is established.
    [2" id="US-20010007102-A1-CLM-00002] 2. A data network as recited in
    claim 1 wherein said first and second change recording means include first and second tables, respectively and transfers within said data network occur as data blocks and wherein said first data store includes storage for diverse information about each data block and said second table in said second change recording means receives the diverse information, said second operating means transferring the contents of said second table to a third table that controls the transfer of data from said second data store the receiving data means.
    [3" id="US-20010007102-A1-CLM-00003] 3. A data network as recited in
    claim 1 wherein transfers within said data network occur as data blocks and wherein a portion of said first data store contains information about changes to each data block and wherein said network additionally includes a third change recording means and said second operating means transfers the contents of said first data store portion to said third change recording means at the time that the second mode is established.
    [4" id="US-20010007102-A1-CLM-00004] 4. A data network as recited in
    claim 3 additionally including control means responsive to predetermined data received from the altering means for enabling said first and second operating means on a mutually exclusive basis.
    [5" id="US-20010007102-A1-CLM-00005] 5. A data network as recited in
    claim 3 additionally including control means responsive to iteratively generated first and second commands from the altering means for effecting a cascading session during which said control means alternately and iteratively enables said first and second operating means on a mutually exclusive basis.
    [6" id="US-20010007102-A1-CLM-00006] 6. A data network as recited in
    claim 5 wherein said first, second and third change recording means comprise first, second and third tables, respectively and wherein said second table receives change information from the stored diverse information, said network additionally including copy means for transferring data, said second operating means initializing said second table and setting all data in said third table to a first state during a first iteration in a cascading session for enabling said copy means to transfer all the data in the second data store to said receiving means.
    [7" id="US-20010007102-A1-CLM-00007] 7. A data network as recited in
    claim 6 wherein said first operating means on succeeding operations responds to a data block change by altering the corresponding data in said first and second tables and second operating means, on successive operations, transferring corresponding data from said second table to said third table.
    [8" id="US-20010007102-A1-CLM-00008] 8. A data network comprising:
    A) a production site with a host and an associated production site storage facility,
    B) a remote site with an associated remote site storage facility,
    C) a storage facility for interconnecting the production site and the remote site wherein the host can issue a plurality of cascade commands,
    D) a first data store for connection to the production facility for receiving data therefrom on a track-by-track basis,
    E) a second data store,
    F) first and second track status tables for identifying each track in said first data store that the production site changes,
    G) first operating means for establishing a first operating mode in response to a first cascade command during which said second data store receives data from said first data store according to the changes recorded in said first track status table,
    H) second operating means for establishing a second operating mode in response to a second cascade command for copying data from said second data store to the remote storage facility according to the changes transferred from said second track status table to a third track status table at the time the second mode is established.
    [9" id="US-20010007102-A1-CLM-00009] 9. A data network as recited in
    claim 8 wherein said first data store includes storage for diverse information about each track and said second track status table receives the diverse information.
    [10" id="US-20010007102-A1-CLM-00010] 11. A data network as recited in
    claim 8 additionally including control means responsive to predetermined data received from the production facility for enabling said first and second operating means on a mutually exclusive basis.
    [11" id="US-20010007102-A1-CLM-00011] 12. A data network as recited in
    claim 8 additionally including control means responsive to iteratively generated first and second commands from the production facility for effecting a cascading session during which said control means alternatingly and iteratively enables said first and second operating means on a mutually exclusive basis.
    [12" id="US-20010007102-A1-CLM-00012] 13. A data network as recited in
    claim 12 additionally including copy means for transferring data, said second operating means initializing said second table and setting all data in said third table to a first state during a first iteration in a cascading session whereby said copy means transfers all the data in the second data store to said receiving means.
    [13" id="US-20010007102-A1-CLM-00013] 14. A data network as recited in
    claim 13 wherein said first operating means on succeeding iterations alters corresponding data in said first and second tables and second operating means, on successive iterations, transfers corresponding data from said second table to said third table.
    [14" id="US-20010007102-A1-CLM-00014] 15. A data network as recited in
    claim 10 additionally comprising means for establishing a communications link between said first and second data stores and the remote site.
    [15" id="US-20010007102-A1-CLM-00015] 16. A data network as recited in
    claim 10 additionally comprising means for establishing a communications link between the production site and said first and second data stores.
    [16" id="US-20010007102-A1-CLM-00016] 17. A data network as recited in
    claim 16 additionally comprising means for establishing a communications link between said first and second data stores and the remote site.
    [17" id="US-20010007102-A1-CLM-00017] 18. A data network as recited in
    claim 16 additionally comprising means for establishing a communications link between said first and second data stores and the remote site and wherein each of said communications links has a different characteristic bandwidth.
    [18" id="US-20010007102-A1-CLM-00018] 19. A data network as recited in
    claim 16 additionally comprising means for establishing a communications link between said first and second data stores and the remote site and wherein said communications link to the production facility has a greater characteristic bandwidth than said communications link to the remote site.
    [19" id="US-20010007102-A1-CLM-00019] 20. A method for transferring data between a facility for altering data and a facility for receiving data including the steps of:
    A) establishing a first data store for receiving the altered data,
    B) establishing a second data store,
    C) recording the identification of changes in the first data store produced by the facility for altering data in first and second locations,
    D) establishing a first operating mode during which the second data store receives data from the first data store according to the identified changes in the first locations,
    E) establishing a second operating mode for copying data from the second data store to the receiving facility according to the changes in the second locations identified at the time the second operating mode is established.
    [20" id="US-20010007102-A1-CLM-00020] 21. A method as recited in
    claim 20 wherein data transfers occur as data blocks and wherein the first data store includes storage for diverse information about each data block and said step of identifying changes includes establishing third locations for recording an identification of changes and said second operating mode establishment transferring the contents of the second locations to the third locations for enabling the copying to the receiving facility.
    [21" id="US-20010007102-A1-CLM-00021] 22. A method as recited in
    claim 20 wherein data transfers occur as data blocks and wherein a portion of the first data store contains information about changes to each data block, the contents of the first data store portion being transferred to the second locations to provide initial identification information at the time that the second operation mode is established.
    [22" id="US-20010007102-A1-CLM-00022] 23. A method as recited in
    claim 22 wherein the first and second operating modes operate on a mutually exclusive basis in response to predetermined data from the altering facility.
    [23" id="US-20010007102-A1-CLM-00023] 24. A method as recited in
    claim 22 wherein an iterative generation of first and second commands from the altering facility effects a cascading session during which the first and second operating modes are enabled on a mutually exclusive basis, iteratively.
    [24" id="US-20010007102-A1-CLM-00024] 25. A method as recited in
    claim 24 additionally wherein data is transferred by copying, the initial operation of the second operating mode initializing the second locations and setting all data in third locations to a first state during a first iteration in a cascading session whereby said copying transfers all the data in the second data store to the receiving facility.
    [25" id="US-20010007102-A1-CLM-00025] 26. A method as recited in
    claim 25 wherein the first operating mode on succeeding operations responds to a data block change by altering the corresponding data in the first and second as locations and the second operating mode, on successive operations, transferring corresponding data from the second locations to the third locations.
    [26" id="US-20010007102-A1-CLM-00026] 27. A method for transferring data between a production site with a host and an associated production site storage facility and a remote site with an associated remote site storage facility, wherein the host can issue a plurality of cascade commands, said method comprising the steps of:
    A) establishing a first data store for receiving data from the production facility on a track-by-track basis,
    B) establishing a second data store,
    C) defining a first and second track status tables for identifying each track in the first data store that the production site changes and a third track status table that identifies changes in the second data store,
    D) establishing a first operating mode in response to a first cascade command during which the second data store receives data from the first data store according to the changes recorded in the first track status tables,
    E) establishing a second operating mode in response to a second cascade command for copying data from the second data store to the remote storage facility according to the changes transferred to the third track status from the second track status table at the time the second mode is established.
    [27" id="US-20010007102-A1-CLM-00027] 28. A method as recited in
    claim 27 wherein the first data store includes storage for diverse information about each track and the second table receives the diverse information.
    [28" id="US-20010007102-A1-CLM-00028] 30. A method as recited in
    claim 28 wherein additionally including the step of enabling the first and second operating means on a mutually exclusive basis to predetermined data received from the production facility.
    [29" id="US-20010007102-A1-CLM-00029] 31. A method as recited in
    claim 28 additionally including the step of effecting a cascading session during which the control means alternatingly and iteratively enables the first and second operating means on a mutually exclusive basis in response to iteratively generated first and second commands from the production facility.
    [30" id="US-20010007102-A1-CLM-00030] 32. A method as recited in
    claim 31 additionally including the step of copying data to effect a data transfer, said method including initializing the second track status table and setting all data in the third table to a first state during a first iterative in the second operating mode in a cascading session whereby the copy means transfers all the data in the second data store to the receiving means.
    [31" id="US-20010007102-A1-CLM-00031] 33. A method as recited in
    claim 32 wherein during the first operating mode alters corresponding data in the first and second tables and during second operating mode, on successive iterations, corresponding data from the second table transfers to the third table.
    [32" id="US-20010007102-A1-CLM-00032] 34. A method as recited in
    claim 29 wherein said first and second data stores are geographically remote from the remote site, said method additionally comprising the step of establishing a communications link between said first and second data stores and the remote site.
    [33" id="US-20010007102-A1-CLM-00033] 35. A method as recited in
    claim 29 wherein said first and second data stores are geographically remote from the production facility, said method additionally comprising the step of establishing a communications link between the production site and said first and second data stores.
    [34" id="US-20010007102-A1-CLM-00034] 36. A method as recited in
    claim 35 wherein said first and second data stores are geographically remote from the remote site, said method additionally comprising step of establishing a communications link between said first and second data stores and the remote site.
    [35" id="US-20010007102-A1-CLM-00035] 37. A method as recited in
    claim 35 wherein the steps of establishing the communications links establishes communications links with different characteristic bandwidths.
    [36" id="US-20010007102-A1-CLM-00036] 38. A method as recited in
    claim 35 wherein the step of establishing the communications links establishes a communications link to the production facility with a greater characteristic bandwidth than the communications link to the remote site.
    类似技术:
    公开号 | 公开日 | 专利标题
    US6687718B2|2004-02-03|Method and apparatus for cascading data through redundant data storage units
    US7287181B2|2007-10-23|Mirrored volume replication method, apparatus, and system
    US6868506B2|2005-03-15|Data recovery method and apparatus
    US6401178B1|2002-06-04|Data processing method and apparatus for enabling independent access to replicated data
    US5720029A|1998-02-17|Asynchronously shadowing record updates in a remote copy session using track arrays
    US5682513A|1997-10-28|Cache queue entry linking for DASD record updates
    US5870537A|1999-02-09|Concurrent switch to shadowed device for storage controller and device errors
    US7310743B1|2007-12-18|Data recovery method and apparatus
    US7225307B2|2007-05-29|Apparatus, system, and method for synchronizing an asynchronous mirror volume using a synchronous mirror volume
    JP3149325B2|2001-03-26|Method and associated system for forming a consistency group to provide disaster recovery functionality
    JP2576847B2|1997-01-29|Storage control device and related method
    US6052758A|2000-04-18|Interface error detection and isolation in a direct access storage device DASD system
    US5615329A|1997-03-25|Remote data duplexing
    US8060779B2|2011-11-15|Using virtual copies in a failover and failback environment
    US6035412A|2000-03-07|RDF-based and MMF-based backups
    EP1000397B1|2004-08-25|Producing a mirrored data copy | using reference labels
    US7882316B2|2011-02-01|Shared data mirroring apparatus, method, and system
    JP2002149499A|2002-05-24|Remote copy system with integrity of data
    US7240080B2|2007-07-03|Method and apparatus for determining using least recently used protocol if one or more computer files should be written to one or more information storage media and synchronously providing one or more computer files between first and storage devices
    US20020120605A1|2002-08-29|Data recovery method and apparatus
    同族专利:
    公开号 | 公开日
    WO2000049500A1|2000-08-24|
    DE69927258T2|2006-06-14|
    US6687718B2|2004-02-03|
    KR20010042781A|2001-05-25|
    IL183096A|2008-04-13|
    KR100562820B1|2006-03-23|
    EP1605357A2|2005-12-14|
    EP1071993A1|2001-01-31|
    US20040193660A1|2004-09-30|
    JP3769190B2|2006-04-19|
    EP1071993B1|2005-09-14|
    US7313578B2|2007-12-25|
    US6209002B1|2001-03-27|
    IL139069D0|2001-11-25|
    EP1605357A3|2008-01-23|
    IL139069A|2008-04-13|
    DE69927258D1|2005-10-20|
    JP2002542526A|2002-12-10|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US6092066A|1996-05-31|2000-07-18|Emc Corporation|Method and apparatus for independent operation of a remote data facility|
    US6101497A|1996-05-31|2000-08-08|Emc Corporation|Method and apparatus for independent and simultaneous access to a common data set|
    US6442551B1|1996-05-31|2002-08-27|Emc Corporation|Method and apparatus for independent and simultaneous access to a common data set|EP1517242A2|2003-09-01|2005-03-23|Hitachi, Ltd.|Method of mirroring and backing up a storage system|
    US20050073887A1|2003-06-27|2005-04-07|Hitachi, Ltd.|Storage system|
    EP1536338A1|2003-11-27|2005-06-01|Hitachi, Ltd.|Computer system and method for failure recovery using remote copy|
    US6957301B2|2002-09-18|2005-10-18|International Business Machines Corporation|System and method for detecting data integrity problems on a data storage device|
    US20050262312A1|2002-07-30|2005-11-24|Noboru Morishita|Storage system for multi-site remote copy|
    US20060048014A1|2004-09-01|2006-03-02|Masamitsu Takahashi|Data processing system and copy processing method thereof|
    US20060047660A1|2004-06-09|2006-03-02|Naoko Ikegaya|Computer system|
    US20060069890A1|2004-09-30|2006-03-30|Emc Corporation|Triangular asynchronous replication with minimal synchronous storage|
    US20060069893A1|2004-09-30|2006-03-30|Emc Corporation|Host implementation of triangular asynchronous replication|
    US7152078B2|2001-12-27|2006-12-19|Hitachi, Ltd.|Systems, methods and computer program products for backup and restoring storage volumes in a storage area network|
    GB2434894A|2004-09-30|2007-08-08|Emc Corp|Restoring backed up data to a host system from local and remote data storage units|
    US20070234106A1|2006-03-31|2007-10-04|Lecrone Douglas E|Resumption of operations following failover in connection with triangular asynchronous replication|
    US20100199038A1|2003-06-27|2010-08-05|Hitachi, Ltd.|Remote copy method and remote copy system|US4686620A|1984-07-26|1987-08-11|American Telephone And Telegraph Company, At&T Bell Laboratories|Database backup method|
    US5093787A|1986-06-12|1992-03-03|Simmons John C|Electronic checkbook with automatic reconciliation|
    US4866611A|1987-01-29|1989-09-12|International Business Machines Corporation|Method for automatically reconciling entries on two copies of independently maintained electronic calendars|
    US4975690A|1988-11-07|1990-12-04|Ibm Corporation|Method for concurrent data entry and manipulation in multiple applications|
    US5307481A|1990-02-28|1994-04-26|Hitachi, Ltd.|Highly reliable online system|
    US5544347A|1990-09-24|1996-08-06|Emc Corporation|Data storage system controlled remote data mirroring with respectively maintained data indices|
    JP3126225B2|1991-07-12|2001-01-22|富士通株式会社|Database system|
    JP2550239B2|1991-09-12|1996-11-06|株式会社日立製作所|External storage system|
    JP2793399B2|1991-12-09|1998-09-03|日本電気株式会社|Buffer device|
    US5392390A|1992-04-10|1995-02-21|Intellilink Corp.|Method for mapping, translating, and dynamically reconciling data between disparate computer platforms|
    EP0593062A3|1992-10-16|1995-08-30|Siemens Ind Automation Inc|Redundant networked database system|
    JP3612339B2|1992-10-23|2005-01-19|株式会社日立製作所|Data processing method and apparatus|
    US5469503A|1993-07-27|1995-11-21|Aspect Telecommunications Corporation|Method for resynchronizing secondary database and primary database with preservation of functionality of an automatic call distribution system|
    US5432922A|1993-08-23|1995-07-11|International Business Machines Corporation|Digital storage system and method having alternating deferred updating of mirrored storage disks|
    US5553279A|1993-10-08|1996-09-03|International Business Machines Corporation|Lossless distribution of time series data in a relational data base network|
    US5495606A|1993-11-04|1996-02-27|International Business Machines Corporation|System for parallel processing of complex read-only database queries using master and slave central processor complexes|
    US5596745A|1994-05-16|1997-01-21|International Business Machines Corporation|System and procedure for concurrent database access by multiple user applications through shared connection processes|
    US5434994A|1994-05-23|1995-07-18|International Business Machines Corporation|System and method for maintaining replicated data coherency in a data processing system|
    US5579318A|1994-06-30|1996-11-26|Bellsouth Corporation|Processes and apparatus for maintaining data concurrence between databases in telecommunications networks|
    US5625818A|1994-09-30|1997-04-29|Apple Computer, Inc.|System for managing local database updates published to different online information services in different formats from a central platform|
    US5835953A|1994-10-13|1998-11-10|Vinca Corporation|Backup system that takes a snapshot of the locations in a mass storage device that has been identified for updating prior to updating|
    US5799147A|1994-10-19|1998-08-25|Shannon; John P.|Computer recovery backup method|
    US5634052A|1994-10-24|1997-05-27|International Business Machines Corporation|System for reducing storage requirements and transmission loads in a backup subsystem in client-server environment by transmitting only delta files from client to server|
    US5649089A|1994-11-30|1997-07-15|Motorola, Inc.|Method and apparatus for maintaining a redundant database system|
    US6063983A|1995-09-05|2000-05-16|The General Hospital Corporation|Monoclonal lymphocytes and methods of use|
    US5857208A|1996-05-31|1999-01-05|Emc Corporation|Method and apparatus for performing point in time backup operation in a computer system|
    US5937414A|1997-02-28|1999-08-10|Oracle Corporation|Method and apparatus for providing database system replication in a mixed propagation environment|
    US6529944B1|1999-01-06|2003-03-04|Emc Corporation|Host system for remote control of mass storage volumes using cascading commands|
    US6950871B1|2000-06-29|2005-09-27|Hitachi, Ltd.|Computer system having a storage area network and method of handling data in the computer system|US7756986B2|1998-06-30|2010-07-13|Emc Corporation|Method and apparatus for providing data management for a storage system coupled to a network|
    US6662197B1|1999-06-25|2003-12-09|Emc Corporation|Method and apparatus for monitoring update activity in a data storage facility|
    TW454120B|1999-11-11|2001-09-11|Miralink Corp|Flexible remote data mirroring|
    US6401178B1|1999-12-23|2002-06-04|Emc Corporatiion|Data processing method and apparatus for enabling independent access to replicated data|
    US20020046251A1|2001-03-09|2002-04-18|Datacube, Inc.|Streaming memory controller|
    JP3951547B2|2000-03-24|2007-08-01|株式会社日立製作所|Data sharing method between hosts by replication|
    US6505307B1|2000-09-06|2003-01-07|Unisys Corporation|Method and apparatus for ensuring data integrity|
    JP2002189570A|2000-12-20|2002-07-05|Hitachi Ltd|Duplex method for storage system, and storage system|
    US7260636B2|2000-12-22|2007-08-21|Emc Corporation|Method and apparatus for preventing unauthorized access by a network device|
    US6516394B1|2001-03-02|2003-02-04|Emc Corporation|System and method for management of storage devices using labels|
    US6728736B2|2001-03-14|2004-04-27|Storage Technology Corporation|System and method for synchronizing a data copy using an accumulation remote copy trio|
    US7827142B2|2001-05-11|2010-11-02|Nokia Corporation|Data element information management in a network environment|
    JP4175789B2|2001-07-05|2008-11-05|株式会社日立製作所|File level remote copy method for storage device|
    US20030014523A1|2001-07-13|2003-01-16|John Teloh|Storage network data replicator|
    US7827136B1|2001-09-20|2010-11-02|Emc Corporation|Management for replication of data stored in a data storage environment including a system and method for failover protection of software agents operating in the environment|
    US7155463B1|2001-09-20|2006-12-26|Emc Corporation|System and method for replication of one or more databases|
    US6701392B1|2001-11-14|2004-03-02|Emc Corporation|Hierarchical approach to indentifying changing device characteristics|
    US6862632B1|2001-11-14|2005-03-01|Emc Corporation|Dynamic RDF system for transferring initial data between source and destination volume wherein data maybe restored to either volume at same time other data is written|
    US6976139B2|2001-11-14|2005-12-13|Emc Corporation|Reversing a communication path between storage devices|
    US7539745B1|2001-12-11|2009-05-26|Emc Corporation|Network management for replication of data stored in a data storage environment|
    US7139932B2|2002-01-03|2006-11-21|Hitachi, Ltd.|Data synchronization of multiple remote storage after remote copy suspension|
    US6745303B2|2002-01-03|2004-06-01|Hitachi, Ltd.|Data synchronization of multiple remote storage|
    US6948089B2|2002-01-10|2005-09-20|Hitachi, Ltd.|Apparatus and method for multiple generation remote backup and fast restore|
    US7007142B2|2002-02-19|2006-02-28|Intel Corporation|Network data storage-related operations|
    US20030204539A1|2002-04-30|2003-10-30|Bergsten James R.|Facility protection utilizing fault tolerant storage controllers|
    US7080378B1|2002-05-17|2006-07-18|Storage Technology Corporation|Workload balancing using dynamically allocated virtual servers|
    US20030217131A1|2002-05-17|2003-11-20|Storage Technology Corporation|Processing distribution using instant copy|
    US6928476B2|2002-08-23|2005-08-09|Mirra, Inc.|Peer to peer remote data storage and collaboration|
    JP2004110367A|2002-09-18|2004-04-08|Hitachi Ltd|Storage system control method, storage control device, and storage system|
    US7263593B2|2002-11-25|2007-08-28|Hitachi, Ltd.|Virtualization controller and data transfer control method|
    US7107272B1|2002-12-02|2006-09-12|Storage Technology Corporation|Independent distributed metadata system and method|
    US7080225B1|2002-12-10|2006-07-18|Emc Corporation|Method and apparatus for managing migration of data in a computer system|
    US6996682B1|2002-12-27|2006-02-07|Storage Technology Corporation|System and method for cascading data updates through a virtual copy hierarchy|
    JP2004220450A|2003-01-16|2004-08-05|Hitachi Ltd|Storage device, its introduction method and its introduction program|
    JP4429634B2|2003-06-02|2010-03-10|株式会社日立製作所|Storage system and storage system control method|
    US7065589B2|2003-06-23|2006-06-20|Hitachi, Ltd.|Three data center remote copy system with journaling|
    US7130975B2|2003-06-27|2006-10-31|Hitachi, Ltd.|Data processing system|
    US7793060B2|2003-07-15|2010-09-07|International Business Machines Corporation|System method and circuit for differential mirroring of data|
    JP4419460B2|2003-08-04|2010-02-24|株式会社日立製作所|Remote copy system|
    JP2005056200A|2003-08-05|2005-03-03|Hitachi Ltd|Data management method, disk storage device and disk storage system|
    JP2005062928A|2003-08-11|2005-03-10|Hitachi Ltd|Remote copy system using two or more sites|
    JP4374953B2|2003-09-09|2009-12-02|株式会社日立製作所|Data processing system|
    JP4386694B2|2003-09-16|2009-12-16|株式会社日立製作所|Storage system and storage control device|
    US7219201B2|2003-09-17|2007-05-15|Hitachi, Ltd.|Remote storage disk control device and method for controlling the same|
    JP4598387B2|2003-09-17|2010-12-15|株式会社日立製作所|Storage system|
    JP2005157521A|2003-11-21|2005-06-16|Hitachi Ltd|Method for monitoring state information of remote storage device and storage sub-system|
    JP2005157712A|2003-11-26|2005-06-16|Hitachi Ltd|Remote copy network|
    JP2005157867A|2003-11-27|2005-06-16|Hitachi Ltd|Storage system, storage controller, and method for relaying data using storage controller|
    US7228456B2|2003-12-01|2007-06-05|Emc Corporation|Data recovery for virtual ordered writes for multiple storage devices|
    DE112004002315B4|2003-12-01|2016-11-10|Emc Corp.|Virtual ordered write entries for multiple storage devices|
    GB2436746B|2003-12-01|2008-02-27|Emc Corp|Virtual ordered writes for multiple storage devices|
    US7054883B2|2003-12-01|2006-05-30|Emc Corporation|Virtual ordered writes for multiple storage devices|
    US7330861B2|2004-09-10|2008-02-12|Hitachi, Ltd.|Remote copying system and method of controlling remote copying|
    US7437389B2|2004-03-10|2008-10-14|Hitachi, Ltd.|Remote copy system|
    US7085788B2|2003-12-03|2006-08-01|Hitachi, Ltd.|Remote copy system configured to receive both a write request including a write time and a write request not including a write time.|
    US7724599B2|2003-12-03|2010-05-25|Hitachi, Ltd.|Remote copy system|
    JP4412989B2|2003-12-15|2010-02-10|株式会社日立製作所|Data processing system having a plurality of storage systems|
    JP4426275B2|2003-12-16|2010-03-03|株式会社日立製作所|Remote copy control method|
    JP4282464B2|2003-12-17|2009-06-24|株式会社日立製作所|Remote copy system|
    JP2005202893A|2004-01-19|2005-07-28|Hitachi Ltd|Storage device controller, storage system, recording medium recording program, information processor, and method for controlling storage system|
    US20050172072A1|2004-01-30|2005-08-04|Cochran Robert A.|Multiple site data replication|
    JP4477370B2|2004-01-30|2010-06-09|株式会社日立製作所|Data processing system|
    US7039785B2|2004-02-24|2006-05-02|Hitachi, Ltd.|Method and apparatus for increasing an amount of memory on demand when monitoring remote mirroring performance|
    US8140475B1|2004-02-26|2012-03-20|Netapp, Inc.|Dynamic configuration archival and retrieval|
    JP4476683B2|2004-04-28|2010-06-09|株式会社日立製作所|Data processing system|
    US7366857B2|2004-04-30|2008-04-29|Hewlett-Packard Development Company, L.P.|Internal disk array mirror architecture|
    JP4715286B2|2004-05-11|2011-07-06|株式会社日立製作所|Computer system and computer system control method|
    JP2006011581A|2004-06-23|2006-01-12|Hitachi Ltd|Storage system and its control method|
    JP4477950B2|2004-07-07|2010-06-09|株式会社日立製作所|Remote copy system and storage device system|
    US20060031418A1|2004-07-30|2006-02-09|Mirra, Inc.|Authenticating client-to-client communication|
    JP2006048300A|2004-08-03|2006-02-16|Hitachi Ltd|Disk array device group and its copy processing method|
    JP4519563B2|2004-08-04|2010-08-04|株式会社日立製作所|Storage system and data processing system|
    JP4401895B2|2004-08-09|2010-01-20|株式会社日立製作所|Computer system, computer and its program.|
    US7516354B2|2004-08-25|2009-04-07|International Business Machines Corporation|Storing parity information for data recovery|
    US7395265B2|2004-08-27|2008-07-01|Hitachi, Ltd.|Data processing system and storage subsystem provided in data processing system|
    JP4519573B2|2004-08-27|2010-08-04|株式会社日立製作所|Data processing system and method|
    JP4646574B2|2004-08-30|2011-03-09|株式会社日立製作所|Data processing system|
    JP2006099440A|2004-09-29|2006-04-13|Hitachi Ltd|Remote copying system|
    US20060080362A1|2004-10-12|2006-04-13|Lefthand Networks, Inc.|Data Synchronization Over a Computer Network|
    JP2006127028A|2004-10-27|2006-05-18|Hitachi Ltd|Memory system and storage controller|
    JP2006127217A|2004-10-29|2006-05-18|Hitachi Ltd|Computer system and method for controlling the same|
    US7657578B1|2004-12-20|2010-02-02|Symantec Operating Corporation|System and method for volume replication in a storage environment employing distributed block virtualization|
    GB0504390D0|2005-03-02|2005-04-06|Ibm|Storage system with cascaded copy targeting and enhanced integrity|
    US20060218060A1|2005-03-09|2006-09-28|Lawlor Erin P|Accounting method and system|
    JP4639112B2|2005-04-28|2011-02-23|株式会社日立製作所|Remote copy topology check method|
    US7549029B2|2005-05-06|2009-06-16|International Business Machines Corporation|Methods for creating hierarchical copies|
    US7552309B2|2005-05-06|2009-06-23|International Business Machines Corporation|Data storage methods for hierarchical copies|
    US7490213B2|2005-05-06|2009-02-10|Xiv Ltd.|Dynamic allocation of storage for hierarchical copies|
    US7613747B1|2005-06-08|2009-11-03|Sprint Communications Company L.P.|Tiered database storage and replication|
    US7890508B2|2005-08-19|2011-02-15|Microsoft Corporation|Database fragment cloning and management|
    US7836266B2|2005-09-19|2010-11-16|International Business Machines Corporation|Managing snapshot history in a data storage system|
    US7620938B2|2005-10-31|2009-11-17|Microsoft Corporation|Compressed program recording|
    JP4577242B2|2006-03-10|2010-11-10|日本電気株式会社|Data backup system, data backup method, and operation control program thereof|
    JP4915775B2|2006-03-28|2012-04-11|株式会社日立製作所|Storage system and storage system remote copy control method|
    US8548948B2|2006-04-11|2013-10-01|Oracle International Corporation|Methods and apparatus for a fine grained file data storage system|
    JP4887893B2|2006-04-26|2012-02-29|株式会社日立製作所|Computer system and computer system control method|
    JP2007310448A|2006-05-16|2007-11-29|Hitachi Ltd|Computer system, management computer, and storage system management method|
    JP2007323218A|2006-05-31|2007-12-13|Hitachi Ltd|Backup system|
    JP4842720B2|2006-06-29|2011-12-21|株式会社日立製作所|Storage system and data replication method|
    US7539827B2|2006-07-19|2009-05-26|Microsoft Corporation|Synchronization of change-tracked data store with data store having limited or no change tracking|
    US8117409B2|2006-11-22|2012-02-14|Hitachi, Ltd.|Method and apparatus for backup and restore in a dynamic chunk allocation storage system|
    US7856419B2|2008-04-04|2010-12-21|Vmware, Inc|Method and system for storage replication|
    JP5147570B2|2008-07-02|2013-02-20|株式会社日立製作所|Storage system and remote copy recovery method|
    JP5422147B2|2008-07-08|2014-02-19|株式会社日立製作所|Remote copy system and remote copy method|
    US8495043B2|2008-09-17|2013-07-23|International Business Machines Corporation|System and method for allowing updates to database objects|
    US9325790B1|2009-02-17|2016-04-26|Netapp, Inc.|Servicing of network software components of nodes of a cluster storage system|
    US9215279B1|2009-02-17|2015-12-15|Netapp, Inc.|Servicing of storage device software components of nodes of a cluster storage system|
    IT1399922B1|2010-05-06|2013-05-09|Tenova Spa|INTEGRATED PROCEDURE FOR CONTROL, CENTERING AND ADJUSTMENT OF THE SCABBULATIONOF THE METAL TAPE IN PROCESS LINES|
    JP5675234B2|2010-09-10|2015-02-25|任天堂株式会社|Information processing system, information processing program, and information processing method|
    WO2012127537A1|2011-03-24|2012-09-27|Hitachi, Ltd.|Computer system and data backup method|
    JP5776267B2|2011-03-29|2015-09-09|日本電気株式会社|Distributed file system|
    US9372910B2|2012-01-04|2016-06-21|International Business Machines Corporation|Managing remote data replication|
    JP5867902B2|2012-03-06|2016-02-24|日本電気株式会社|Asynchronous database replication method|
    US9081754B1|2012-03-30|2015-07-14|Emc Corporation|Method and apparatus for cascaded replication using a multi splitter|
    US9798636B2|2014-06-23|2017-10-24|Liqid Inc.|Front end traffic handling in modular switched fabric based data storage systems|
    US10303782B1|2014-12-29|2019-05-28|Veritas Technologies Llc|Method to allow multi-read access for exclusive access of virtual disks by using a virtualized copy of the disk|
    US10198183B2|2015-02-06|2019-02-05|Liqid Inc.|Tunneling of storage operations between storage nodes|
    US11169727B1|2017-03-10|2021-11-09|Pure Storage, Inc.|Synchronous replication between storage systems with virtualized storage|
    法律状态:
    2004-01-15| STCF| Information on status: patent grant|Free format text: PATENTED CASE |
    2007-08-03| FPAY| Fee payment|Year of fee payment: 4 |
    2007-08-23| AS| Assignment|Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GAGNE, MATHIEU;OFEK, YUVAL;REEL/FRAME:019733/0446;SIGNING DATES FROM 19990329 TO 19990330 |
    2011-08-03| FPAY| Fee payment|Year of fee payment: 8 |
    2015-08-03| FPAY| Fee payment|Year of fee payment: 12 |
    2016-09-21| AS| Assignment|Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 |
    2016-09-29| AS| Assignment|Owner name: EMC IP HOLDING COMPANY LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EMC CORPORATION;REEL/FRAME:040203/0001 Effective date: 20160906 |
    2019-03-21| AS| Assignment|Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., T Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 |
    2021-11-03| AS| Assignment|Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MOZY, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MAGINATICS LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL INTERNATIONAL, L.L.C., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: AVENTAIL LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 |
    优先权:
    申请号 | 申请日 | 专利标题
    US09/251,812|US6209002B1|1999-02-17|1999-02-17|Method and apparatus for cascading data through redundant data storage units|
    US09/740,281|US6687718B2|1999-02-17|2000-12-19|Method and apparatus for cascading data through redundant data storage units|US09/740,281| US6687718B2|1999-02-17|2000-12-19|Method and apparatus for cascading data through redundant data storage units|
    US10/752,256| US7313578B2|1999-02-17|2004-01-06|Method and apparatus for cascading data through redundant data storage units|
    [返回顶部]