WO2011158386A1 - 計算機システム、及びシステム制御方法 - Google Patents

計算機システム、及びシステム制御方法 Download PDF

Info

Publication number
WO2011158386A1
WO2011158386A1 PCT/JP2010/063405 JP2010063405W WO2011158386A1 WO 2011158386 A1 WO2011158386 A1 WO 2011158386A1 JP 2010063405 W JP2010063405 W JP 2010063405W WO 2011158386 A1 WO2011158386 A1 WO 2011158386A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
storage area
replication
computer
backup
Prior art date
Application number
PCT/JP2010/063405
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
美沙子 河野
晋広 牧
裕教 江丸
正靖 淺野
原　純一
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to US12/988,546 priority Critical patent/US8683154B2/en
Publication of WO2011158386A1 publication Critical patent/WO2011158386A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring

Definitions

  • the present invention relates to a computer system and a system control method, for example, control of replication processing in a storage system and a computer.
  • DR Disaster Recovery
  • a storage area in which application data is stored is called a data volume.
  • Backup is a process of storing data at a certain point in time and storing it for a long time.
  • DR is a process in which duplicated data can be used in another system by always replicating data in the data volume.
  • replication includes host-based replication performed on the host computer and array-based replication performed on the storage system.
  • write data written from the application to the data volume is captured to create a replica volume that stores the same data as the data volume. Since the write data from the application is transferred and written to the medium, it is possible to deal with a heterogeneous environment without depending on the storage device. In addition, a replica volume can be created at a low cost.
  • a replica volume is created using the storage replication function. This makes it possible to create a replica volume in which the consistency of a plurality of hosts is maintained without imposing a load on the host.
  • the present invention has been made in view of such a situation, and in order to make the data content of the replica volume used in host-based replication coincide with the data content of the main volume when the restoration process of the main volume is performed.
  • the present invention proposes a replication management method for realizing an environment in which array-based replication and host-based replication are used together.
  • the data in the first storage area (storage system primary volume) is copied to the second storage area (storage system secondary volume) using the array-based replication engine (backup is created and stored) To do).
  • the execution result of replication is managed by adding a flag indicating the time when the backup was created.
  • the first host computer uses the host-based replication engine to copy the data written to the first storage area to the third storage area of the second host computer to create a replica volume.
  • the data in the third storage area (replica volume) is copied to the fourth storage area to create a secondary replica volume.
  • the third storage area (replica volume) is the same as the data in the second storage area used in the restore process.
  • the data in the fourth storage area (secondary replica volume) is returned to the third storage area.
  • the present invention it is possible to realize an environment using both host-based replication and array-based replication. If a combined environment can be realized, it is possible to handle heterogeneous environments without depending on the type and nature of the storage device, replication operation that is inexpensive, does not put a load on the host computer, and maintains the consistency of multiple hosts Is possible.
  • FIG. 1 is a block diagram showing a schematic configuration of a computer system 1.
  • FIG. 2 is a block diagram showing an example of the internal configuration of a storage system 10.
  • FIG. 3 is a block diagram showing an example of the internal configuration of a host computer (business server) 30.
  • FIG. 3 is a block diagram showing an example of the internal configuration of a host computer (standby server) 40.
  • FIG. 3 is a block diagram showing an example of the internal configuration of a management computer 50.
  • FIG. It is a figure which shows the structural example of a structure information table.
  • It is a figure which shows the structural example of a replication information table.
  • It which shows the structural example of an array base replication management table.
  • It is a figure which shows the structural example of a host base replication management table.
  • aaa table the information does not necessarily have to be expressed by a data structure of a table, and data structures such as lists, DBs, queues, etc. It may be expressed in other ways. Therefore, “aaa table”, “aaa list”, “aaaDB”, “aaa queue”, etc. may be referred to as “aaa information” to indicate that they are not dependent on the data structure.
  • program will be the subject, but the program is executed by the processor, and processing determined by using the memory and communication port (communication control device) will be performed. It is good. Further, the processing disclosed with the program as the subject may be processing performed by a computer such as a management server or an information processing apparatus. Part or all of the program may be realized by dedicated hardware, or may be modularized. Various programs may be installed in each computer by a program distribution server or a storage medium.
  • FIG. 1 is a block diagram showing a schematic configuration of a computer system 1 according to the first embodiment of the present invention.
  • the computer system 1 of this embodiment includes a storage system 10, a switch device 20, a host computer (business server) 30, a host computer (standby server) 40, and a management computer 50.
  • the storage system 10 and the host computer (business server) 30 are connected from each data interface to the data network 21A via the switch device 20A.
  • the data network 21A is a storage network (SAN).
  • the data network 21A may be an IP (Internet Protocol) network or any other type of data communication network.
  • the host computer (business server) 30 and the host computer (standby server) 40 are connected to each other via the data network 21B from each data interface.
  • the data network 21B is an IP network. However, it may be a storage network or any other type of data communication network.
  • the host computer 40 is operated as a standby server for storing and managing replica volumes as described above.
  • the host computer 40 is a separate business server having the same performance and configuration as the host computer 30. There may be. In this case, a replica volume of a main volume used by an application of another host computer is stored and managed among a plurality of host computers (business servers).
  • the storage system 10, the host computer (business server) 30, the host computer (standby server) 40, and the management computer 50 are connected to the management network 22 from each management interface via the switch device 20B.
  • the management network 22 is an IP network.
  • the management network 22 may be a SAN or any other type of data communication network.
  • the data network 21 and the management network 22 may be the same network.
  • the switch device 20A and the switch device 20B may be the same device.
  • the host computer (business server) 30, the host computer (standby server) 40, and the management computer 50 may be configured to use the same computer.
  • the computer system 1 includes one storage system 10, two host computers, and one management computer 50, but the number is not limited.
  • FIG. 2 is a diagram showing an internal configuration of the storage system 10 according to the embodiment of the present invention.
  • the storage system 10 includes a storage controller 11 that controls the entire storage system 10 and a storage device 12 that stores data.
  • the storage controller 11 and the storage apparatus 12 are connected via the storage I / F 112.
  • the storage controller 11 includes a data I / F 110, a CPU (Central Processing Unit) 111, a storage I / F 112, a management I / F 113, and a memory 114.
  • the data I / F 110 is an interface to the data network 21A and has one or more communication ports.
  • the storage controller 11 exchanges data with the host computer (business server) 30 via this port.
  • the CPU 111 is a processor that executes a program stored in the memory 114.
  • the storage I / F 112 is an interface to the storage apparatus 12. Data and control commands are transmitted / received via the storage I / F 112.
  • the management I / F 113 is an interface with the management network 22 and has one or more communication ports.
  • the storage controller 11 can exchange data and control commands with the host computer (business server) 30, the host computer (standby server) 40, the management computer 50, and other storage systems via this port.
  • the storage microprogram 115 is a program for managing the storage apparatus 12 and is executed by the CPU 111 to realize a function of causing the host computer (business server) 30 to recognize the volume.
  • the function of causing the host computer (business server) 30 to recognize the volume is to collect the physical resources 120 (configuration information) of the storage apparatus 12 and to create one or more logical volumes via the I / F. This is a function provided (notified) to the server 30.
  • the configuration information includes information about the primary volume, secondary volume, RAID configuration, and volume usage status (from which application is accessed), and these are periodically requested by the administrator. Or when the configuration changes.
  • the array-based replication engine 116 is a program that realizes the replication function of the storage system 10.
  • the replication function of the storage system is a function for copying data in a logical volume to another logical volume. For example, assuming that the physical resource 120 in the storage apparatus 12 is one logical volume, data is copied from the physical resource 120A to the physical resource 120B.
  • the storage device 12 includes a physical resource 120 and a pool 121.
  • the physical resource 120 is a storage area for storing data operated by a computer (for example, a host computer (business server) 30).
  • the physical resource 120A corresponds to a primary volume
  • the physical resource 120B corresponds to a secondary volume (array-based replica volume).
  • the physical resource 120 represents a storage area resource provided by a physical device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive).
  • the type of physical device that provides the physical resource 120 is not particularly limited.
  • the pool 121 is a group of physical resources 121. Generally, the pool 121 is configured by making the physical resources 120 redundant by using a technique called RAID (Redundant Array of Independent Disks). However, the present invention is not limited to this, and any physical resource 120 may be used. In the figure, there is one pool 121 and four physical resources 120, but this is not restrictive, and it is sufficient that one or more pools exist.
  • FIG. 3 is a diagram showing an internal configuration of the host computer (business server) 30 according to the embodiment of the present invention.
  • the host computer (business server) 30 includes an input device 300 such as a keyboard and a mouse, a display device 301 such as a CRT (Cathode Ray Tube) and an LCD (Liquid Crystal Display), a CPU 302, and a data I / F (A) 303.
  • the CPU 302 is a processor that executes a program stored in the memory 304.
  • the data I / F (A) 303 is an interface to the data network 21A and has one or more communication ports.
  • the host computer (business server) 30 transmits / receives data to / from the storage system 10 via this port.
  • the memory 304 stores an agent 310, an application 305, and a host-based replication engine 306. These are executed by the CPU 302.
  • the application 305 is a program that executes processing by reading / writing data from / to the physical resource 120 on the storage apparatus 12.
  • the application 305 is a DBMS (Data Base Management System) or a file system, for example. In the figure, there is one application 305, but this number is not limited in the present invention.
  • the host-based replication engine 306 realizes a function of capturing data that the application 305 writes to the storage system 10 and transferring the data to the host computer (standby server) 40 via the data I / F (B) 308. However, this may be a function of the application.
  • the agent 310 has a function of collecting the configuration information of the host computer 30 and grasping the relationship between the application 305 and the storage system 10 such as which volume the application is accessing.
  • the storage area 307 is an area for storing data on the host computer 30. Data used by the application 305 or the host-based replication engine 306 may be stored.
  • the data I / F (B) 308 is an interface with the data network 21B, and exchanges data and control commands with the host computer (standby server) 40.
  • the management I / F 309 is an interface with the management network 22 and transmits / receives data and control commands to / from the storage system 10, the host computer (standby server) 40, and the management computer 50 for system management.
  • FIG. 4 is a diagram showing an internal configuration of the host computer (standby server) 40 according to the embodiment of the present invention.
  • the host computer (standby server) 40 has the same configuration as that of the host computer (business server) 30, but the host-based replication engine 306 is not limited to the host base, and replication is performed in the standby server 40. It is different from the business server 30 in that it has a replication engine 406 (which can create a secondary replica volume described later).
  • the replication engine 406 may have a replication function 5081 as shown in FIG.
  • the replication engine 406 manages the differential bitmap of the data volume, specifies the differential data information to be transferred to the replica volume from the differential bitmap information, and at the stage when the restoration for the data volume by array-based replication is completed.
  • data may be transferred from the data volume to the replica volume.
  • FIG. 5 is a diagram showing an internal configuration of the management computer 50 according to the embodiment of the present invention.
  • the management computer 50 includes an input device 500 such as a keyboard and a mouse, a display device 501 such as a CRT, a CPU 502, a management I / F 503, and a memory 504.
  • the CPU 502 is a processor that executes a program stored in the memory 504.
  • the management I / F 503 is an interface with the management network 22, and transmits and receives data and control commands to and from the host computer (business server) 30, the host computer (standby server) 40, and the storage system 10 for system management.
  • the memory 504 includes a replication management program 506, a configuration information table 507, a replication information table 508, an array-based replication management table 509, a host-based replication management table 510, an array-based replication catalog table 511, and a secondary replica catalog. Table 512 is stored.
  • the replication management program 506 is realized by being executed by the CPU 502, and realizes the processing of the embodiment of the present invention.
  • the replication management program 506 is a program for providing a setting screen to the administrator, obtaining information from the host computers 30 and 40 and the storage system 10, controlling the replication engine, and managing each table.
  • the configuration information table 507, replication information table 508, array-based replication management table 509, host-based replication management table 510, array-based replication catalog table 511, and host-based replication catalog data table 512 will be described later.
  • a keyboard and a pointer device can be considered as examples of the input device 400 included in the management computer 50, but other devices may be used. Further, instead of or in addition to the display device 401, another output device (for example, a printer) may be provided.
  • a serial interface or an Ethernet interface is used as an input / output device
  • a display computer having a display, a keyboard, or a pointer device is connected to the interface, and display information is used as a display computer.
  • the input and display on the input / output device may be substituted by transmitting or receiving input information from the display computer to display on the display computer or accepting input.
  • a set of one or more computers that manage the computer system 1 and display the display information of the present invention may be referred to as a management system.
  • the management computer 50 displays the display information
  • the management computer 50 is a management system
  • the combination of the management computer 50 and the display computer is also a management system.
  • a plurality of computers may realize processing equivalent to that of the management computer.
  • the plurality of computers if the display computer performs the display, display (Including computers) is the management system.
  • FIG. 6 is a diagram showing an example of the configuration information table 507 according to the embodiment of the present invention.
  • the configuration information table 507 is a table for storing configuration information of the host computers 30 and 40 and the storage system 10.
  • the configuration information table 507 is referred to by the replication management program 506 executed by the management computer 50.
  • the configuration information table 507 includes a host ID 5070 for identifying the host computers 30 and 40, an application ID 5071 for identifying applications on the host computers 30 and 40, a storage ID 5072 for identifying the storage system 10, and storage
  • the configuration item includes a volume ID 5073 for identifying the physical resource 120 in the storage apparatus 12 on the system 10 and a usage status 5074 indicating the usage status of the physical resource.
  • the replication management program 506 acquires host ID 5070, application ID 5071, and volume ID 5073 information from the host computer 30, acquires storage ID 5072, volume ID 5073, and usage status 5074 information from the storage system 10, and combines these information.
  • the configuration information table 507 is created. These pieces of information may be acquired in advance by an administrator.
  • “used” and “ ⁇ ” are described in the column of the usage status 5074 for convenience, but the expression is not particularly limited as long as it can be specified whether it is in use or unused.
  • FIG. 7 is a diagram showing an example of the replication information table 508 according to the embodiment of the present invention.
  • the replication information table 508 is a table for storing information on the replication function on the devices of the computer system 1.
  • the replication information table 508 is referred to by the replication management program 506 executed by the management computer 50.
  • the replication information table 508 has, as its configuration items, a system device ID 5080 for recognizing each system device and a replication function 5081 existing in the device.
  • the function name is described in the column of the replication function 5081 and expressed as “asynchronous remote replication” or “host-based CDP (Continuous Data Protection)”.
  • the array-based replication engine 116 is described as a function of “full backup” and “differential backup” for convenience.
  • the host-based replication engine 306 is described as “asynchronous remote replication”
  • the replication engine 406 is described as “host-based CDP”.
  • each replication engine is not limited to these replication functions.
  • FIG. 8 is a diagram showing an example of the array-based replication management table 509 according to the embodiment of the present invention.
  • the array-based replication management table 509 is a table for managing backups using the array-based replication engine, and manages the schedule of array-based backup (replication) operations.
  • the array-based replication management table 509 is referred to by a replication management program 506 executed by the management computer 50.
  • the array-based replication management table 509 includes a replication ID 5090 for managing replication, an application ID 5091 for identifying an application to be backed up, a type 5092 for identifying a backup type, a backup schedule 5093, and a backup target application.
  • the data VOLID 5094 in which the data is stored and the backup VOLID 5095 for identifying the backup destination volume are included as configuration items.
  • the application ID 5091, type 5092, schedule 5093, and backup VOLID 5095 information are set using the replication management program 506. Further, the replication ID 5090 is given at the time of setting by the administrator, but may be given by manual input by the administrator.
  • the data VOLID 5094 is specified from the information of the application 305 set by the administrator, and the volume ID 5073 is specified from the application ID 5071 of the configuration information table 507. Note that the administrator may directly set the volume VOLID 5073, which is the data VOL, or specify the volume ID by setting information that can specify the data VOL.
  • the backup VOLID 5095 may be set by the administrator, or the replication management program 506 may determine an unused volume from the usage status 5074 of the configuration information table 507.
  • the backup of VOL001 which is the volume used by the application AP001, is executed alternately for the backup volumes VOL003 and VOL004 every other day.
  • the schedule 5093 is entered with a time designation of “every day 23:00” and a time interval of “every hour”.
  • a description method may be used.
  • FIG. 9 is a diagram showing an example of the host-based replication management table 510 according to the embodiment of the present invention.
  • the host-based replication management table 510 is a table for managing replication using the host-based replication engine.
  • the host-based replication management table 510 is referred to by the replication management program 506 executed by the management computer 50.
  • the host-based replication management table 510 includes a replication ID 5100 for managing replication, an application ID 5101 for identifying an application to be replicated, a replication type 5102, and a data VOLID 5103 in which data of the replication target application is stored.
  • the configuration item includes a target host ID 5104 for identifying a replication destination host and a replica VOLID 5105 for identifying a replication destination volume.
  • the replication ID 5100 is given by the replication management program 506 when set by the administrator, but may be given manually by the administrator.
  • the data VOLID 5103 is specified from the information of the application 305 set by the administrator, and the volume ID 5073 is specified from the application ID 5071 of the configuration information table 507.
  • the administrator may directly set the volume VOLID that is the data VOL, or may specify the volume ID by setting information that can specify the data VOL.
  • the target host ID 5104 and the replica VOLID may be set by the administrator, or the replication management program 506 may determine an unused volume from the usage status 5074 of the configuration information table 507.
  • FIG. 10 is a diagram showing an example of the array-based replication catalog table 511 according to the embodiment of the present invention.
  • the array-based replication catalog table 511 is a table for managing the results of array-based replication processing executed according to the array-based replication management table 509 (see FIG. 8).
  • the array-based replication catalog table 511 is referred to by a replication management program 506 executed by the management computer 50.
  • the array-based replication catalog table 511 stores a replication catalog ID 5110 for uniquely specifying a replication execution task, a backup start time 5111, a replication ID 5112 for managing replication, and data of a backup target application.
  • the configuration item includes a data VOLID 5113 and a backup VOLID 5114 in which backup data is stored.
  • the array base replication catalog table 511 stores the execution result of the array base replication management table 509. Information of the replication ID 5112, the data VOLID 5113, and the backup VOLID 5114 of the array-based replication catalog table 511 is acquired from the array-based replication management table 509. The backup VOLID 5114 is selected from the backup VOLID 5095 in the array-based replication management table 509.
  • the replication management program 506 selects them in order. However, the administrator may select the backup VOLID, and the selection method does not matter. Further, at the start of backup, the replication management program 506 assigns the replication catalog ID 5110 and the time 5111 and stores the information in the table. However, it may be given manually by the administrator.
  • FIG. 11 is a diagram illustrating an example of the secondary replica catalog table 512.
  • the secondary replica catalog table 512 is referred to by the replication management program 506 executed by the management computer 50.
  • the secondary replica catalog table 512 creates a replication catalog ID 5120 for uniquely specifying a replication execution task, a replication ID 5121 for managing replication, a secondary replica data creation time 5122, and secondary replica data.
  • the replica VOLID 5123 indicating the replica volume in which the original data is stored, the secondary replica data storage area 5124 for specifying the storage area in which the secondary replica data is stored, and the backup executed by array-based replication And a backup flag 5125 for providing the performance as a configuration item.
  • the secondary replica data means a replica volume (replica replica) created by replicating a replica volume created by host-based replication.
  • the secondary replica catalog table 512 the results executed by the replication engine 406 on the host computer (standby server) 40 are stored. This is for replicating the replica VOL data storing the replication data executed by the host-based replication management table 510 (see FIG. 9) to the secondary replica data storage area 5124.
  • the secondary replica data storage area 5124 may be selected by the administrator, or the replication management program 506 may select a free volume from the usage status 5070 of the configuration information table 507. Further, when the replication management program 506 stores data in the secondary replica data storage area 5124, the creation time 5122 and the replication catalog ID (for example, the time when array-based replication (backup) is executed in the storage device is used as the ID. ) Information. Furthermore, the replication management program 506 gives a backup flag 5125 when a backup using the array-based replication engine 116 is executed.
  • the replica volume of the standby server is 23 of 2010/4/21. It can be seen that the content is the same as the replica volume data of the storage device at 0:00.
  • FIG. 12 is a diagram for explaining the flow of data processing in an environment shared by host-based replication and array-based replication according to this embodiment.
  • backup is performed using an array-based replication engine on the storage system 10 and replication is performed for disaster recovery using host-based replication.
  • the application 305 on the host computer (business server) 30 stores data in a data volume on the storage system 10.
  • the replication management program 506 uses the array-based replication engine 116 to copy the data volume (main volume) data to the target volume (replica volume). As for the copy timing, the data at the time when the replication management program 506 wants to save it as backup data is copied according to the array base replication table 509 (FIG. 8).
  • the replication management program 506 uses the host-based replication engine 306 to capture the write data of the application 305 and transfer it to the replica volume on the host computer (standby server) 40.
  • the replication engine 406 stores the data written in the replica volume in a secondary replica volume such as a snapshot volume so that the replica volume can be returned to a past state using the secondary replica volume. .
  • FIG. 19 is a diagram showing a configuration example of the Write command data 1900.
  • Write command data 1900 is data for managing a Write command.
  • Write command data 1900 is created when data used by application 305 changes.
  • Write command data 1900 includes, for example, an instruction code, data, generation time, data VOLID, storage destination address, sequence number, and backup flag as configuration items.
  • the instruction code and data are information that is added when the application 305 issues write data (write data).
  • the data VOIID is a field in which the identifier of the data VOL that is the storage destination of the write data is stored.
  • the storage destination address is a field in which the storage destination address in the data volume indicated by the data VOLID is stored.
  • the generation time is the time when the host-based replication engine 306 captures the Write command from the application 305.
  • These values are values that are set when the host-based replication engine 306 captures a write command from the application 305. Note that when only the backup flag is transferred, NULL is set in the data.
  • FIG. 13 is a flowchart for explaining the environment setting process according to the present embodiment.
  • the volume shared by array-based replication and host-based replication is specified, and the environment is set so that business can be taken over even if the volume used in host-based replication is broken.
  • the processing from S1001 to S1004 is realized by the replication management program 506 on the management computer 50 according to the present embodiment. This is realized by the CPU 502 reading the program from the memory 504 and executing this processing step.
  • the program may be described as the subject, but in reality, the CPU that is the processing unit that executes the program is processing.
  • the replication management program 506 acquires configuration information (see FIG. 6) and information on the replication function (see FIG. 7) existing in each device from the host computer 30 and the storage system 10.
  • the configuration information acquired from the storage system 10 includes a storage ID for identifying the storage system 10 and volume ID information for identifying a volume stored in the storage.
  • the configuration information acquired from the host computer 30 identifies the host ID for identifying the host computer, the application ID for identifying the application 305 running on the host computer, and the volume in which the data of the application 305 is stored. Volume ID, storage ID information for identifying the storage system 10 to which the volume belongs, and usage status information. These pieces of information are stored in the host ID, application ID, storage ID, and volume ID in the configuration information table 507 (FIG. 6).
  • the replication management program 506 acquires information about the replication function existing in each device from each device belonging to the computer system 1. Specifically, in the present embodiment, the replication management program 506 acquires information on the array-based replication function existing on the storage and information on the host-based replication function existing on the host. These pieces of information are stored in the system device ID of the replication information table 508 and the replication function.
  • the replication management program 506 acquires replication setting information.
  • the replication management program 506 displays a replication setting screen and starts processing according to an instruction from the administrator.
  • the screen may be a graphic screen operation such as GUI (Graphical User Interface), or may be input by a command such as CLI (Command Line Interface).
  • CLI Common Line Interface
  • a property file created by the administrator may be referred to, or the replication management program 506 may automatically generate it.
  • the setting method is not limited. This information is information that the host-based replication engine 306 and the array-based replication engine 116 hold in advance, and the replication management program 506 may acquire the information from each engine.
  • the administrator registers the ID of the application 305 to be replicated using the replication setting screen. Further, the administrator uses the setting screen to select the host-based replication or the array-based replication for the type of replication set in the application 305. Then, the replication management program 506 refers to the replication function 5081 of the replication information table 508 based on the selected replication type, and presents a replication function that can be selected by the administrator. From this information, the administrator selects and sets the replication function. Also, the administrator selects a replication destination volume using the replication setting screen.
  • the administrator sets information related to the replication schedule using the replication setting screen. Then, the replication management program 506 acquires the set information and adds it to the array-based replication management table 509 or the host-based replication management table 510 depending on the type of replication. The replication management program 506 searches and acquires the configuration information table 507 based on the application ID designated by the administrator for the host ID and data VOLID, and obtains the information from the array-based replication management table 509 or the host base. Stored in the replication management table 510.
  • the replication management program 506 identifies a volume shared by array-based replication and host-based replication. Specifically, the replication management program 506 collates the data VOLID 5094 registered in the array-based replication management table 509 with the data VOLID 5103 registered in the host-based replication management table 510 to determine whether the same volume exists. By searching, the volume on which both replication processes are executed is specified. For example, in this embodiment, the data VOLID 5094 in FIG. 8 and the data VOLID 5103 in FIG. 9 are searched. Then, it can be seen that the volume shared by the array-based replication and the host-based replication is a volume whose data VOLID is VOL001.
  • the replication management program 506 determines the secondary replica data storage method in the standby server that is the replication destination of host-based replication. For example, referring to FIG. 7, the replication function existing in HOST002, which is the replication destination of host-based replication, is host-based CDP. Therefore, host-based CDP is used.
  • the replication management program 506 may acquire a related copy function from the host computer (standby server) 40, present an environment that can be constructed to the administrator, and the administrator may determine the standby server-side data storage method. .
  • FIG. 14 is a flowchart for explaining the operation of array-based replication and host-based replication in this embodiment.
  • FIG. 14 the processing from S2001 to S2006 is realized by the replication management program 506 on the memory of the management computer 50 according to the present embodiment.
  • Step S2001 The replication management program 506 uses the host-based replication engine 306 to capture the write data from the application 305 and transfer it to the host computer (standby server) 40 side. Specifically, referring to the host-based replication management table 510, the host-based replication engine 306 captures the write data from the application 305, and stores it in the replica VOLID destination volume of the host computer (standby server: target host) 40. Store the data.
  • the replication management program 506 uses the replication engine 406 to replicate data as secondary replica data in the host computer (standby server) 40 (or in a storage area provided outside the standby server 40).
  • the replication management program 506 adds necessary information to the secondary replica catalog table 512 every time replica data is replicated to create secondary replica data.
  • the replication management program 506 confirms the backup start time in the storage system 10, and repeats the processing of S2001 and step S2002 until the backup start time comes. When the backup start time comes, the process proceeds to step S2004.
  • the replication management program 506 quiesces the application (freeze: stops the I / O processing while the application is operating) when the backup schedule time comes. Specifically, the replication management program 506 refers to the backup schedule in the array-based replication management table 509, and freezes the application when the time comes.
  • the replication management program 506 starts backup using array-based replication.
  • the replication management program 506 acquires a backup by the backup acquisition method set by the administrator in S1002.
  • the backup method is not limited to this.
  • necessary information is added to the array-based replication catalog table 511 (FIG. 10). That is, since the replication ID is ARP001, ARPC001 is added to the column 5112.
  • the replication management program 506 uses the host-based replication engine 306 to transfer the backup flag to the host computer (standby server) 40 side. This makes it possible to maintain consistency between the data up to the transfer of this flag and the data that is being backed up.
  • the replication management program 506 also assigns the time of this backup (backup in the storage system) to the column of the backup flag 5125 of the secondary replica catalog table 512 (see FIG. 11).
  • the replication catalog IDs HRPC001 and HRP002 before the backup flag is transferred are the same as the backup data of “2010/04/20 23: 00: 00: 00”. After the flag is transferred, the written data HRPC003 becomes the time used for the next backup.
  • Restore processing means that when there is a primary volume (data volume) and a secondary volume (replica volume), when the data in the primary volume is corrupted, the secondary volume is used to move the primary volume to a certain point This is processing to restore data at the time of generation), and business takeover processing (described later) that resumes application operation using a different volume (for example, a replica volume of the standby server 40) when the primary volume is broken Is different.
  • FIG. 15 is a flowchart for explaining the restoration processing of data backed up by array-based replication in this embodiment.
  • the processing from step S3001 to step S3007 is realized by the replication management program 506 on the memory 504 of the management computer 50 according to this embodiment.
  • the replication management program 506 transfers untransferred data to the host computer (standby server) 40 using the host-based replication engine 306. This process is a process for discharging the data stored in the host computer (business server) 30 without being transferred by the host base replication engine 306. By performing this processing, the data VOL at the time when the application 305 is stopped and the data in the replica VOL can be matched. More specifically, the replication management program 506 searches the application specified by the administrator from the application ID of the host-based replication management table 510, specifies the target host ID and replica VOLID, and stores data for the specified volume. Forward.
  • the replication management program 506 executes restore processing using the array-based replication engine 116. Specifically, the volume specified in S3002 (for example, VOL003) is copied to the data volume.
  • the replication management program 506 applies the data of the secondary replica volume to the replica volume so that the content of the replica volume is the same data as the data volume restored in S3005. More specifically, the replication management program 506 sets the secondary replica volume data so that the replica volume on the host computer (standby server) 40 has the same content as the backup data (secondary volume) created at the specified time. Is applied to the replica volume.
  • the replication management program 506 refers to the backup flag of the secondary replica catalog table 512 and identifies the secondary replica data storage area 5124 to be applied.
  • the secondary replica data storage areas “SSVOL001” and “SSVOLC002” corresponding to the backup flag “2010/04/20 23: 00: 00: 00” can be specified. Then, by applying a method of returning data from the information on the secondary replica data storage method, the data is returned to the volume whose replica VOLID is VOL011.
  • FIG. 16 is a flowchart for explaining the business handover process according to this embodiment.
  • the processing from step S4001 to step S4004 is processing realized by the replication management program 506 on the memory 504 of the management computer 50 according to this embodiment.
  • the replication management program 506 receives a business takeover instruction in the host computer (standby server) 40. Specifically, the administrator selects a host computer that takes over the business and its application to the replication management program 506, and issues a business takeover instruction to the host computer (standby server) 40. In other words, for example, when the host computer (business server) 30 is broken, the administrator selects a host computer that takes over the business, displays the applications belonging to the host, Select and identify applications that will continue to take over operations.
  • the replication management program 506 identifies a volume that takes over the business. Specifically, the volume that takes over the work is specified from the host and application that take over the work received in S4001. The administrator can specify the target host ID 5104 and the replica VOLID 5105 from the application ID 5101 of the host-based replication management table 510. For example, it can be seen that the data of AP0011 on HOST001 that wants to take over the work is stored in VOL011 on HOST002.
  • the replication management program 506 mounts the identified volume.
  • the replication management program 506 resumes the application of the host computer (standby server) 40 using the volume mounted in S4003. Therefore, even when the host computer (business server) 30 and the storage system 10 storing the data are broken, the business can be resumed using the host computer (standby server) 30. In addition, even if the system goes down during the transfer of host-based replication, it is possible to apply data that can be taken over by using secondary replica volume data on the host computer (standby server) 40. It becomes.
  • the data of the application 305 is captured on the host computer 30 in the computer system 1 in the first embodiment, whereas the application is performed by the switch device 20.
  • the difference is that 305 data is captured.
  • the present embodiment a case where the present invention is applied in this environment will be described focusing on the difference from the configuration of FIG.
  • FIG. 17 is a diagram showing a schematic configuration of a computer system 1B according to the present embodiment.
  • the computer system 1B of this embodiment is similar to FIG. 1 in that the storage system 10, the switch device 20, the host computer (business server) 30, the host computer (standby server) 40, and the management And a computer 50.
  • the storage system 10, the host computers 30 and 40, and the management computer 50 have the same configuration as in the first embodiment.
  • the host-based replication engine 306 may not be on the memory 304 of the host computer (business server) 30.
  • the switch device 20 includes a data I / F 200, a CPU 201, a memory 202, and a management I / F.
  • the data I / F 200 is an interface to the data network 21 and has one or more communication ports. Via this port, the host computer (business server) 30, the host computer (standby server) 40, and the storage system 10 transmit and receive data. Although there are three data I / Fs in the figure, the number is not limited.
  • the management I / F 204 is an interface to the management network 22, has one or more communication ports, and can communicate with the switch device 20B.
  • the CPU 201 is a processor that executes a program stored in the memory 202.
  • the memory 202 stores a replication engine 203. These are executed by the CPU 201.
  • the replication engine 203 captures data that the application 305 on the host computer (business server) 30 writes to the storage system 10 and transfers the data to the host computer (standby server) 40 via the data I / F 200B.
  • the various information used in the present embodiment is the same as the information recorded in the tables shown in FIGS. 6 to 11 described in the first embodiment.
  • the replication information table 508 in this embodiment for example, “asynchronous remote replication” is entered in the replication function 5081 of the system device ID 5080 “switch” in FIG.
  • step S2001 the replication management program 506 on the memory 504 of the management computer 50 uses the replication engine 203 on the memory 202 on the switch device 20A instead of the host computer (business server) 30, and the application 305 Write data is captured and transferred to the standby server.
  • the processing performed by the host-based replication engine 306 is executed by the replication engine 203 on the switch device 20.
  • the replication management program 506 issues an instruction to the replication engine on the switch device 20 instead of the host computer (business server) 30.
  • the third embodiment is different in that a NAS (Network Attached Storage) device 60 is installed instead of the host computers 30 and 40 included in the computer system 1 in the first embodiment.
  • the NAS device 60 stores a file system program 604 on the memory 603 and functions as a file server.
  • a case where the present invention is applied in an NAS environment will be described focusing on the difference from the configuration of FIG.
  • FIG. 18 is a diagram showing a schematic system configuration of a computer system 1C including the NAS device 60 according to the present embodiment.
  • the computer system 1 ⁇ / b> C of this embodiment includes a storage system 10, a switch device 20, a NAS device 60, and a management computer 50.
  • the storage system 10, the switch device 20, and the management computer 50 have the same internal configuration as that of the first embodiment.
  • the difference from the system configuration of FIG. 1 is that the host computers 30 and 40 are replaced with a NAS device 60.
  • the NAS device 60 includes a management I / F 600, a CPU 601, a data I / F 602, and a memory 603.
  • the management I / F 600 is an interface to the management network 22 and has one or more communication ports. Data and control commands are exchanged with the management computer 50 via this port.
  • the CPU 601 is a processor that executes a program stored in the memory 202.
  • the data I / F 602 is an interface to the data network 21 and has one or more communication ports.
  • the data I / F 602A transmits and receives data to and from the storage system 10.
  • the data I / F 602B transmits / receives data to / from the NAS device 60B.
  • a file system program 604 and a NAS replication engine 605 are stored in the memory 603. These are executed by the CPU 601.
  • the file system program 604 is a program for managing the file system.
  • the NAS replication engine 605 captures data that the file system program 604 writes to the storage system 10 and transfers the data to the NAS device 60B via the data I / F 602B.
  • the NAS replication engine 605 transfers data in units of files.
  • FIGS. 13, 14, 15 and 16 The processing shown in FIGS. 13, 14, 15 and 16 can be applied to the processing operation of the computer system 1C according to this embodiment, as in the first embodiment.
  • the application 405 is replaced with the file system program 604, and the host-based replication engine 306 is replaced with the NAS replication engine 605.
  • the NAS replication engine 605 of the NAS device 60B captures the write data to the storage system 10 by the file system program 604, transfers it to the NAS device 60B via the data I / F 602B, and the first embodiment As in the case, a replica volume is created in the NAS device 60B. Then, the replication engine of the NAS device 60B creates a secondary replica volume that is a replica of the replica volume.
  • the computer system includes the first computer (host computer 30, switch device 20A, NAS device 60A) and the second computer (host computer 40, NAS device). 60B), a storage system, and a management computer.
  • backup data (replica) of the first storage area (primary volume) is generated by array-based replication at a predetermined timing (for example, a replication schedule is specified from the management computer), and the second storage area ( Secondary volume).
  • host-based replication is executed in the first computer, and replica data of the first storage area is stored in the third storage area (replica volume) in the second host computer.
  • replication (not necessarily host-based) is executed, and a replica of the replica volume is stored as secondary replica data in the fourth storage area (secondary replica volume).
  • secondary replica data is applied to the replica volume so that By doing this, even if the primary volume is restored, the replica volume is not destroyed by host-based replication, and the consistency between host-based replication and array-based replication can be ensured, and both can be used in combination. Can be provided.
  • the secondary replica update time indicating the time at which the replica of the data was added to the fourth storage area as the secondary replica data, and the write data added to the fourth storage area at the secondary replica update time is It can be seen at which backup time the data was backed up in the second storage area (see FIG. 11).
  • the management computer transfers the data in the fourth storage area (secondary replica volume) corresponding to the backup time of the data in the second storage area (secondary volume) used for the restore process to the third storage area (replica volume). ) Apply to data.
  • the restore process will be performed if the restore process is performed. It is possible to make the contents of the secondary volume used in the above match the contents of the replica volume.
  • the present invention can also be realized by a program code of software that realizes the functions of the embodiment.
  • a storage medium in which the program code is recorded is provided to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus reads the program code stored in the storage medium.
  • the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention.
  • a storage medium for supplying such program code for example, a flexible disk, CD-ROM, DVD-ROM, hard disk, optical disk, magneto-optical disk, CD-R, magnetic tape, nonvolatile memory card, ROM Etc. are used.
  • an OS operating system
  • the computer CPU or the like performs part or all of the actual processing based on the instruction of the program code.
  • the program code is stored in a storage means such as a hard disk or memory of a system or apparatus, or a storage medium such as a CD-RW or CD-R
  • the computer (or CPU or MPU) of the system or apparatus may read and execute the program code stored in the storage means or the storage medium when used.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
PCT/JP2010/063405 2010-06-17 2010-08-06 計算機システム、及びシステム制御方法 WO2011158386A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/988,546 US8683154B2 (en) 2010-06-17 2010-08-06 Computer system and system control method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2010-138464 2010-06-17
JP2010138464A JP5424992B2 (ja) 2010-06-17 2010-06-17 計算機システム、及びシステム制御方法

Publications (1)

Publication Number Publication Date
WO2011158386A1 true WO2011158386A1 (ja) 2011-12-22

Family

ID=45347806

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/063405 WO2011158386A1 (ja) 2010-06-17 2010-08-06 計算機システム、及びシステム制御方法

Country Status (2)

Country Link
JP (1) JP5424992B2 (enrdf_load_stackoverflow)
WO (1) WO2011158386A1 (enrdf_load_stackoverflow)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013140443A (ja) * 2011-12-28 2013-07-18 Fujitsu Ltd バックアップ制御プログラム、バックアップ制御方法およびバックアップ制御装置
JPWO2016162916A1 (ja) * 2015-04-06 2017-12-07 株式会社日立製作所 管理計算機およびリソース管理方法
CN116301654A (zh) * 2023-03-29 2023-06-23 深圳市正浩创新科技股份有限公司 数据迁移方法、装置、电子设备及存储介质
JP2024017058A (ja) * 2022-07-27 2024-02-08 株式会社日立製作所 ストレージシステム及び管理方法

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005062928A (ja) * 2003-08-11 2005-03-10 Hitachi Ltd 複数のサイトにリモートコピーを行うシステム
JP2007047892A (ja) * 2005-08-08 2007-02-22 Hitachi Ltd 計算機システム及び計算機システムの状態管理方法
JP2007066192A (ja) * 2005-09-01 2007-03-15 Hitachi Ltd ストレージシステム及びその制御方法並びにコンピュータプログラム
JP2007310448A (ja) * 2006-05-16 2007-11-29 Hitachi Ltd 計算機システム、管理計算機、および、ストレージシステム管理方法
JP2008123529A (ja) * 2007-11-19 2008-05-29 Hitachi Ltd 記憶システム
JP2010503089A (ja) * 2006-09-07 2010-01-28 インターナショナル・ビジネス・マシーンズ・コーポレーション 改良された同期データ・ミラー・スワップのための装置、システム、および方法
JP2010039986A (ja) * 2008-08-08 2010-02-18 Hitachi Ltd データのバックアップを管理する計算機システム及び方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6948089B2 (en) * 2002-01-10 2005-09-20 Hitachi, Ltd. Apparatus and method for multiple generation remote backup and fast restore
JP4402992B2 (ja) * 2004-03-18 2010-01-20 株式会社日立製作所 バックアップシステム及び方法並びにプログラム
JP4843976B2 (ja) * 2005-03-25 2011-12-21 日本電気株式会社 レプリケーションシステムと方法
JP4902403B2 (ja) * 2006-10-30 2012-03-21 株式会社日立製作所 情報システム及びデータ転送方法
JP2009070143A (ja) * 2007-09-13 2009-04-02 Hitachi Ltd Ｎａｓ装置の差分リモートバックアップにおけるデータ復旧方法及び計算機システム
JP5026309B2 (ja) * 2008-03-06 2012-09-12 株式会社日立製作所 バックアップデータ管理システム及びバックアップデータ管理方法
JP5224240B2 (ja) * 2008-03-25 2013-07-03 株式会社日立製作所 計算機システム及び管理計算機
JP2009245004A (ja) * 2008-03-28 2009-10-22 Nippon Telegraph & Telephone West Corp 双方向データ配置システム、アクセス解析サーバ、データ移動サーバ、双方向データ配置方法、及び、プログラム

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005062928A (ja) * 2003-08-11 2005-03-10 Hitachi Ltd 複数のサイトにリモートコピーを行うシステム
JP2007047892A (ja) * 2005-08-08 2007-02-22 Hitachi Ltd 計算機システム及び計算機システムの状態管理方法
JP2007066192A (ja) * 2005-09-01 2007-03-15 Hitachi Ltd ストレージシステム及びその制御方法並びにコンピュータプログラム
JP2007310448A (ja) * 2006-05-16 2007-11-29 Hitachi Ltd 計算機システム、管理計算機、および、ストレージシステム管理方法
JP2010503089A (ja) * 2006-09-07 2010-01-28 インターナショナル・ビジネス・マシーンズ・コーポレーション 改良された同期データ・ミラー・スワップのための装置、システム、および方法
JP2008123529A (ja) * 2007-11-19 2008-05-29 Hitachi Ltd 記憶システム
JP2010039986A (ja) * 2008-08-08 2010-02-18 Hitachi Ltd データのバックアップを管理する計算機システム及び方法

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013140443A (ja) * 2011-12-28 2013-07-18 Fujitsu Ltd バックアップ制御プログラム、バックアップ制御方法およびバックアップ制御装置
JPWO2016162916A1 (ja) * 2015-04-06 2017-12-07 株式会社日立製作所 管理計算機およびリソース管理方法
JP2024017058A (ja) * 2022-07-27 2024-02-08 株式会社日立製作所 ストレージシステム及び管理方法
JP7665565B2 (ja) 2022-07-27 2025-04-21 日立ヴァンタラ株式会社 ストレージシステム及び管理方法
CN116301654A (zh) * 2023-03-29 2023-06-23 深圳市正浩创新科技股份有限公司 数据迁移方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
JP2012003544A (ja) 2012-01-05
JP5424992B2 (ja) 2014-02-26

Similar Documents

Publication Publication Date Title
US12375560B2 (en) Enhanced network attached storage (NAS) services interfacing to cloud storage
US12235744B2 (en) Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations
US10715614B2 (en) Assigning data agent proxies for executing virtual-machine secondary copy operations including streaming backup jobs
US20200334112A1 (en) Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount
JP5227887B2 (ja) バックアップ管理方法
JP5227125B2 (ja) ストレージシステム
US7188187B2 (en) File transfer method and system
JP5172574B2 (ja) アプリケーションデータのバックアップ構成構築に用いる管理計算機
JP5137476B2 (ja) 連携して動作する複数のアプリケーションが使用するデータのバックアップ環境の設定を行う計算機及び方法
US7979649B1 (en) Method and apparatus for implementing a storage lifecycle policy of a snapshot image
US20090089340A1 (en) Backup catalog recovery from replicated data
US20100306174A1 (en) Method and apparatus for block based volume backup
US7584339B1 (en) Remote backup and restore operations for ISB protocol systems
US7725669B1 (en) Backup and restore operations using coherency groups for ISB protocol systems
US7987206B2 (en) File-sharing system and method of using file-sharing system to generate single logical directory structure
US7487310B1 (en) Rotation policy for SAN copy sessions of ISB protocol systems
JP2015527620A (ja) 計算機システム、サーバ、及び、データ管理方法
US8683154B2 (en) Computer system and system control method
JP5424992B2 (ja) 計算機システム、及びシステム制御方法
US7587565B1 (en) Generating automated and scheduled SAN copy sessions for ISB protocol systems
US9582384B2 (en) Method and system for data replication
JP5640480B2 (ja) データ管理プログラム、ストレージシステム、およびデータ管理方法
Dell
JP2013161383A (ja) 情報処理装置、情報処理方法、プログラム及び情報処理システム
Pandey et al. A survey of storage remote replication software

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 12988546

Country of ref document: US

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10853265

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10853265

Country of ref document: EP

Kind code of ref document: A1