JPH10269123A - Data backup method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform data backup of disk data of an I/O subsystem connected to a mainframe, to a magnetic tape library of the I/O subsystem connected to the mainframe without through the mainframe. SOLUTION: This method backs up without through a mainframe 101 by making a disk controller 104 and an MT controller 105 of I/O subsystems have information that manages the connection relation and data between the I/O subsystems, accessing from the controller 104 to the controller 106 and outputting an instruction to back up data of a disk drive group 105 to an MT library from a service processor 109 to the controller 104 of the I/O subsystem.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a disk control device which can back up data between different I / O subsystems of a storage control device, and more particularly to storing data of a disk device in an MT library.

[0002]

2. Description of the Related Art In a mainframe, an optimal data arrangement, a large storage hierarchy (storage hierarchy) combining external storage devices having different processing speeds and storage capacities, and the like.
The data management function and the integrated storage management function for the purpose of efficient operation support and IBM's D
FSMS (Data Facility Storage Management Su
bsystem) is equivalent to "IBM SYSTEMS JO
URNAL, Vol. 28, No. 1, 1989 ". Through this management function, data of the I / O subsystem of the mainframe can be stored at a low bit cost.
Alternatively, the data can be backed up to a medium such as a magnetic tape, a magnetic tape library, or an optical disk capable of storing a large amount of data. However, with the increase in network size and data capacity, data management via a mainframe will require a supercomputer-level capability in the future. For this reason, US Pat. No. 5,155,845 discloses a conventional technique for realizing data backup between I / O subsystems connected to a mainframe.

[0003]

In the prior art, backup of disk data is realized between I / O subsystems connected to a mainframe. In order to send and receive data via a network that connects the disk controller,
Backup processing can be efficiently realized without being concentrated on the mainframe. Generally, data backup between disk I / O subsystems of a mainframe has a high bit cost. For this reason, the mainframe disk data is stored in an MT library with low bit cost,
It is desirable to be able to backup efficiently without modifying the mainframe. Further, when the I / O subsystem having the disk device goes down, it is desirable to restore the disk data from the I / O subsystem having the MT library without going through the mainframe. However, the conventional example does not consider these points.

A first object of the present invention is to transfer disk data of an I / O subsystem connected to a mainframe to a magnetic tape library of the I / O subsystem connected to the mainframe without passing through the mainframe. To provide a method for backing up data without changing the processing of the mainframe.

A second object of the present invention is to provide an I / O subsystem having an MT library without an intervening mainframe when an I / O subsystem having a disk device goes down.
An object of the present invention is to provide a data backup method capable of restoring disk data from an O subsystem.

[0006]

The first object can be realized by instructing a disk controller of the I / O subsystem connected to the mainframe from an instruction device different from the mainframe.

A second object of the present invention is to provide the disk controller and the MT controller of the I / O subsystem with information for managing the connection relation between the I / O subsystems and data, and to control the MT control from the disk controller. This can be realized by accessing the device.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing an example of a computer system to which the present invention is applied. The processing system A 100 is connected to a magnetic tape (MT) I / O subsystem 131 via a mainframe 101 and a channel interface 102, and is connected to a disk I / O subsystem 132 via a channel interface 103. Connected. Magnetic tape (MT) I / O subsystem 131
Are a magnetic tape (MT) controller 106, a magnetic tape library controller 107, a magnetic tape drive 110,
It comprises a magnetic tape library 108. The disk I / O subsystem 132 includes the disk control device 104, the disk device group 105, and the service processor 1.
09. The MT controller 106 and the disk controller 104 are connected via a connection cable 130.

FIG. 2 is a diagram showing another example of a computer system to which the present invention is applied. I / O of processing system A100
It comprises a subsystem and an I / O subsystem of the processing system B200. The processing system B200 includes the mainframe 20
1. It is connected to the disk I / O subsystem 232 via the channel interface 203. The disk I / O subsystem 232 includes the disk controller 2
04, disk device group 205, service processor 20
9 is comprised. Processing system B disk controller 204
And the MT controller 106 of the processing system A
0 is connected.

Hereinafter, the connection cables 130 and 230 will be described as channel cables.

The basic operation of the mainframes 101 and 121 accesses the magnetic tape library 108 or the disk device group 105 as an external storage device via a channel interface. The mainframe process may be any operating system that supports the channel interface, such as Hitachi's VOS3 (Virtual-storage Operating System).
Under the control of 3) and the like, a path to externally stored data is established via the interface.

FIG. 3 shows the disk controller 1 in FIG.
FIG. 4 is a diagram illustrating a configuration of a fourth embodiment. Disk control device 104
Is the control system process 307 of the disk controller 104
302, memory device 301, host interface 303, and disk cache device 30 for executing
4. It is composed of an I / O subsystem interface 305, a disk interface 306, and a bus 308 connecting these devices. The control system process 307 operates in a multitask or multiprocessor environment. Various microprograms 3 are stored in the memory device 301.
12, various data 313, and connection relation information 314 including connection relations of control devices and the like and data management information are stored. The memory device 311 is a duplicate of the memory device 301 in order to prevent loss of important information in the event of a failure.

In the disk controller 104 in FIG. 16, the connection destination of the I / O subsystem interface 305 is the MT library controller 107.

The disk control device 204 in FIGS. 2 and 17 has the same configuration and will not be described.

FIG. 18 is a diagram showing a configuration of the MT control device 106 in FIGS. 1 and 2. MT controller 106
Are the MPU 1802 that executes the control system process 1807 of the MT controller 106, the memory device 1801, the host interface 1803, the MT library controller interface 1804, the I / O subsystem interface 1805, the MT driver interface 18
06, and a bus 1808 connecting these devices. The control system process 1807 operates in a multitask or multiprocessor environment. Memory device 18
01 stores connection relation information 1814 including connection relations of various microprograms 1812, various data 1813, control devices and the like, and data management information. The memory device 1811 is a duplicate of the memory device 1801 in order to prevent loss of important information at the time of failure. In the MT control device 106 shown in FIGS.
The configuration is such that there is no O subsystem interface 1805.

FIG. 19 is a diagram showing the configuration of the MT library control device 107 in FIGS. 16 and 17. The MT library control device 107 stores the M
Operate the T cartridge. MT library controller 1
07, an MPU 1902 for executing the control system process 1907 of the MT library control device 107, the memory device 1
901, MT controller interface 1903, MT
It comprises a library interface 1904, an I / O subsystem interface 1905, and a bus 1908 connecting these devices. Control system process 19
07 operates in a multitasking or multiprocessor environment. The memory device 1901 has connection relation information 191 including connection relations of various microprograms 1912, various data 1913, control devices and the like, and data management information.
4 is stored. The memory device 1911 is used to prevent loss of important information in the event of a failure.
01 is duplicated. Further, an interface 1906 with an external storage device can be provided, a disk 1912 can be connected, and memory contents can be stored. In the MT library control device 107 shown in FIGS.
The configuration is such that there is no subsystem interface 1705.

In FIGS. 18 and 19, the MT controller 106
The configuration management information 1814 and 1914 are installed in both the MT library control device 107 and the MT library control device 107, and may be managed by either of them. Hereinafter, the MT control device 106
Has the configuration management information 1814. Therefore, the connection relation information is transmitted between the disk control device 104 and the MT.
It is stored in the control device 106 and is updated when the configuration is changed.

The service processor 109 is connected to the disk controller 104 and
4 can acquire information on the memory device 301 and issue an instruction to the disk control device 104. Similarly, the service processor 209 is connected to the disk control device 204, can acquire information on the memory device of the disk control device 204, and can issue an instruction to the disk control device 204.

First, the memory device 30 of the disk control device
The connection relation information 314 stored in No. 1 will be described. It is stored in the form of a device configuration information list 900 shown in FIG. 9, and has connection relations of control devices and the like and data management information. The entry 900 of the component device information list includes a device identifier 901 and a device identifier 9 that can uniquely identify each component device.
01, which is identification information for internally managing 01 in the device, and attribute list 1 of device identifier 901
It comprises a pointer 903 to 100 or 1110, a pointer 904 to a lower configuration information list indicating a device connected below the device identifier 901, and a next entry pointer 905 indicating the storage location of the next device configuration information entry.

Entry 1000 of lower-level configuration information list
Is a device identifier 100 that can uniquely identify each component device.
1. An internal address 1002 which is identification information for internally managing the device identifier 1001 in the device, an attribute list 1100 of the device identifier 1101, or a pointer 1003 to 1110, and a storage location of the next lower device configuration information entry. The next entry pointer 1004 is shown.

Pointers 903 and 1003 to attribute list
Is an entry pointer indicating the storage location of the entry in the attribute list 1100 in FIG. 11A if the device identifier indicates a disk control device, and FIG. 11B if the device identifier indicates an MT library. ) Is an entry pointer that indicates the storage location of the entry in the attribute list. In other cases, a NULL character is set.

The entry 1100 of the attribute list shown in FIG. 11A is a disk identifier 110 for identifying a disk.
1. a backup destination MT cartridge identifier 1102 for identifying the backup destination of the disk identifier 1101;
A backup status 1103 indicates the backup execution status of the disk identifier 1101 and a next entry pointer 1104 indicates the storage location of the next attribute entry. The backup status 1103 indicates that the device identifier 1001 is in backup, backup completed, differential backup in progress, differential backup completed, or any other status.

An entry 1100 of the attribute list shown in FIG. 11B includes an MT cartridge identifier 1111 for identifying the MT cartridge, a mode 1112 for indicating the category of the MT cartridge, and a backup source for identifying the disk stored in the MT cartridge identifier 1111. Disk identifier 1113, backup status 1114 indicating the backup execution status of disk identifier 1111, next entry pointer 11 indicating the storage location of the next attribute entry
It consists of fifteen. The mode 1112 indicates a category assigned to the MT cartridge, such as private or scratch. Backup status 1113
Indicates whether the device identifier 1111 is in backup, backup completed, differential backup in progress, differential backup completed, or any other state.

Hereinafter, an embodiment of the first invention will be described with reference to flowcharts shown in FIGS. Specifically, the disk data stored in the disk device group 105 in FIG. 1 is backed up to the MT library 108 connected to the MT I / O subsystem 131.
The backup process is instructed by the service processor 109, and the mainframe issues a normal I / O instruction without regard to the backup process.

FIG. 4 shows the processing of the control system process 307 in the disk control device 104. The service processor 109 is connected to the memory device 30 of the disk controller 104.
After confirming the configuration relationship information 314 on the first disk, the backup control and the disk to be backed up are specified to the disk controller 104. The block 401 receives a backup request from the service processor 109.

[0027] The disk controller 104
2, a request to mount the MT cartridge on the MT library 108 with the data of the disk device group 105 is created by a request record 1200 shown in FIG. The request can be generated by the service processor 109, but is generated here by the disk controller 104.

The request record 1200 is assigned on the transmitting apparatus side of this record, and includes, as information capable of uniquely identifying this record, a session identifier 120 including a serial number, transmission source, and transmission destination information for the record data.
1, a request content identifier 1202 indicating an instruction such as mount, data read, data write, etc., and a pointer 1203 to a parameter record shown in FIG.

The parameter record 1300 includes an MT controller identifier 1301 for identifying the MT controller, an MT driver identifier 1302 for identifying the MT driver, an MT cartridge identifier 1303 for identifying the MT cartridge,
The category of the MT cartridge identifier 1303 includes a designation mode 1304.

The parameter record 1310 includes an MT driving device identifier 1311 and a pointer 1302 to a transfer data record 1500.

The parameter record 1320 includes an MT driving device identifier 1321.

The disk controller 104 sets the mount request identifier in the request content identifier 1202 of the request record 1200, and sets a pointer indicating the storage location of the entry 1300 in FIG. In the parameter record 1300, the MT controller 106 is designated as the MT controller identifier 1301, the MT driver identifier 1302 is designated as the MT driver 110, and the mode 1304 is designated as the scratch mode described above. The MT cartridge identifier 1303 is not set. This indicates that the MT library control device 107 selects the MT cartridge having the scratch mode as the storage destination of the backup data. A mount request is transmitted to the MT control device 106.

In block 403, the MT controller 1
06, a response is received. The response is received in the response record 1400.

The response record 1400 is assigned on the transmitting device side of the record, and includes, as information that can uniquely identify the record, a session identifier 14 including a serial number for the record data, transmission source information, transmission destination information, and the like.
01, a return target session identifier 1403 for identifying the return target session, a return content identifier 1403 indicating the return content, and an MT cartridge identifier 1404 indicating the backup data storage destination. In block 404, the response record is analyzed and the MT cartridge identifier 1 of the backup data storage destination is analyzed.
From 404, enter the MT cartridge number (Volume Serial
Numer) is acquired, the MT cartridge number is set in the backup destination MT cartridge identifier 1103 of the attribute information of the disk to be backed up in the configuration relationship information 314, and the backup state 1103 is set to backup. Thereafter, the disk control device 104 does not accept data update from the mainframe to the corresponding disk until the backup processing is completed.

In block 405, a data write request for writing management information of the backup data is generated in the request record 1200 and transmitted to the MT controller 106. A data write request identifier is set in the request content identifier 1202 of the request record 1200,
FIG. 13 shows the pointer 1203 to the parameter record.
A pointer indicating the storage location of the entry 1310 in (b) is set, the MT drive 110 is set in the MT drive identifier 1311 of the parameter record 1310, and the transfer data record 1500 is set in the pointer 1312 to the transfer data record. Set a pointer to the storage location of the entry.

The transfer data record 1500 includes, as information capable of uniquely identifying this record, control data 1505 such as a record serial number, transfer data length, and transfer data 1502.

In the transfer data 1502, a disk number for identifying a disk of the disk group 105 to be backed up specified by the service processor is set as management information for a write request. Generated write request to M
Transmit to the T control device 106.

In block 406, a request to read data to be backed up from the disk device group 105 and write the read data to the MT library 108 is generated in the same manner as in block 405, and transmitted to the control device 106. As write data, VTOC (Volume
Data set management information (fixed-length non-block format, record length, number of heads) of the VOS3 operating system called "Table of Content" is also included. In block 407, it is checked whether the transfer of the data to be backed up has been completed.
Returning to step 408, if completed, proceed to block 408. At block 408, a completion notification from the MT controller 106 is received in the transfer record 1500. In block 409, backup completion is set in the backup status 1103 of the attribute information of the disk to be backed up in the configuration relationship information 314. The backup destination M
A disk device identifier corresponding to the backup source device identifier 1113 of the attribute information of the T cartridge is set, and backup completion is set in the backup status 1114. A processing completion report may be sent to the service processor 109.

FIG. 7 shows the processing of the MT controller 106 and the MT library controller 107. Processing system E700 is M
The processing is performed by a control system process 1807 of the T control device 106, and the processing system F 710 is performed by a control system process 1907 of the MT library control device 107. MT controller 1
06, in block 701, the disk controller 1
An MT cartridge mount request from the server 04 is received in a request record. At block 702, the received MT cartridge mount request is transmitted to the MT library control device 107. MT library control device 107
Receives the MT cartridge mount request in block 711, analyzes the request record in block 712, confirms that the mode 1303 of the MT cartridge storing the backup data is the scratch mode, A possible MT cartridge is selected from the MT library 108 and set in the MT driving device 110. Block 7
At 13, the number (Volume Serial Number) of the MT cartridge set in the MT driving device 110 is transmitted to the MT control device 106. The MT controller 106 receives the MT cartridge number at block 703. At block 704, the response record 14
00 is generated and transmitted to the disk control device 104. The block 70 is added to the MT cartridge identifier 1404 of the backup data storage destination of the response record 1400.
The MT cartridge number received in step 3 is set. In block 705, according to the number of the received MT cartridge, the backup state 1104 of the attribute information of the relevant MT cartridge in the configuration relation information 1814 is set to “in backup”. If a data write request from the disk control device 104 is received in block 706, the process proceeds to block 707, and if data reception is completed, the process proceeds to block 708. At block 707,
The data is transmitted to the MT driver 110 so that the received data is stored in the MT cartridge, and the process returns to block 706. At block 708, a completion report is sent to the disk controller 104 in the transfer data record. In block 709, the corresponding M in the configuration relation information 1814
The disk identifier received in the transfer data 1502 of the transfer data 1500 first received as write data is set as the backup source device identifier 1103 of the attribute information of the T cartridge, and the backup state 1104 which is the attribute information of the corresponding MT cartridge is backed up. Set to complete.

With the above processing, the data of the disk device group A 105 in FIG. 1 can be backed up to the MT library 108.

Next, the difference data backup processing executed by the control system process 307 of the disk control device 104 is shown in the processing flow of FIG. According to FIG. 4, after the disk data is backed up to the MT cartridge, only the updated data of the disk to be backed up is backed up to an MT cartridge different from the previously backed up MT cartridge. Service processor 109, M
The processing of the T control device 106 is the same as the previous backup processing. The service processor 109 checks the configuration relationship information 314 of the disk control device 104, and stores the data of the target disk of the disk device
Disk control unit 1
04, the disk controller 104 receives a differential data backup request in block 500. In block 501, an MT cartridge mount request is generated and transmitted to the MT controller 106. At block 502, a response record is received from the MT controller 106. In block 503, the response record is analyzed, the backup mode is set to the differential data backup processing mode, and the backup status 100 of the disk identifier designated by the configuration relation information in the disk control device 104.
3 is during differential backup. In block 504, a request record of a request to perform differential backup of the data of the corresponding disk of the disk device group 105 to the MT library 108 is created and transmitted to the disk control device 104. In block 505, as in block 405, a management data write request is transmitted. Block 5
At 06, if there is no instruction from the service processor 109 to release the differential data backup processing mode, the flow proceeds to block 506, and if there is a release request, the flow proceeds to block 521. In block 506, if the update data is sufficiently accumulated in the disk cache 304, the process proceeds to block 509, and if there is enough room, the process proceeds to block 507. In block 507, write data from the mainframe 101 (data requested to be updated)
Received at block 508, the disk cache 30
4 and return to block 506. In block 509, a request to write the write data stored in the disk cache 304 to the MT library 108 is generated and transmitted to the MT controller 106. Block 510
, The data of the disk device group 105 is updated with the write data stored in the disk cache 304. At block 511, a completion notification from the MT controller 106 is received in the transfer record 1500. In block 512, the backup status 110 of the attribute information of the disk to be backed up in the configuration relationship information 314
Set backup completion to 3. Also, the corresponding disk device identifier is set as the device identifier 1113 of the backup source in the attribute information of the MT cartridge as the backup destination, and the differential backup complete is set as the backup status 1114.

Here, it is assumed that the write data in the MT controller 106 in block 508 corresponds to one MT cartridge. Blocks 521, 522, 523, 5
14 are blocks 509, 510, 511 and 51, respectively.
Same as 2. When the completion report of the blocks 511 and 523 is received, a process completion report may be sent to the service processor 109.

Next, FIG. 6 shows a processing flow for listing backup data and differential backup data. This is a process in which the disk controller 104 receives a request to read backed-up data from the service processor 109 and lists the backup data stored in the MT library 108. FIG. 6 shows a control system process 30 that has received a backup / restore request from the service processor in the disk controller 104.
7 shows the operation. The service processor 109 checks the configuration relationship information 314 of the disk control device 104 and instructs the disk control device 104 to restore the backed up data from the MT library 108 to the disks of the disk device group 105. At block 601, a backup / restore request from a service processor is received. At block 602, a request to mount the MT cartridge generated in FIG.
The MT cartridge mount request transmitted to the T control device 106 sets the mount request identifier in the request content identifier 1202 of the request record 1200, and indicates the storage location of the entry 1300 in FIG. 13A in the pointer 1203 to the parameter record. Set the pointer,
After confirming the configuration relationship information 314, the parameter record 1
The MT controller 1 is assigned to the MT controller identifier 1301 of 300.
06, the MT driving device identifier 1302 indicates the MT driving device 11
0, the MT cartridge identifier 1303 is set to the cartridge number of the MT cartridge in which the data of the target disk is backed up. The mode 1304 is not set. At block 603, a response from the MT controller 106 is received. At block 604,
The MT controller 106 sends a backup data read request
Transfer to Request record 1200 of read request
, A data read request identifier is set in the request content identifier 1202, and the pointer 1 to the parameter record is set.
A pointer indicating the storage location of the entry 1320 in FIG.
0 MT drive device identifier 1321 includes the MT drive device 1
Set 10 Although the processing of the MT control device 106 is omitted, the M in which the specified backup data is stored is stored.
Select a T cartridge from the MT library 108 and
It is set in the T drive 110, reads data, and transmits it to the disk controller 104. At block 605, backup data is received. In block 606, it is determined from the configuration relationship information 314 whether there is still an MT cartridge from which data has not been read among the MT cartridges storing difference data, and if so, returns to block 602 to store the difference. The mounted MT cartridges are sequentially mounted, and the differential backup data generated in FIG. 5 is received. At block 607,
Merge the received data and bring it up to date. In block 608, the merged data is stored in the disk device 1
05, and a completion notification is received at block 609.

With the above processing, the backup data can be restored.

As a catalog of the MT cartridge described above, in addition to the existing catalog (private, scratch) mode, a new backup-only mode is defined. As a mode for designating the MT cartridge to which the request record of the backup request is stored, You can also specify a backup-only mode. The processing of the MT library control device in this case is the same as that of FIG.
At 12, the MT library control device selects an MT cartridge in the backup-only mode from the MT library and sets it in the MT drive device 110.

FIG. 16 is a diagram showing another example of the computer system to which the present invention is applied, and is the same as FIG. However, the disk controller 104 is connected to the MT library controller 107 by a connection cable 1061.

FIG. 17 is a diagram showing another example of the computer system to which the present invention is applied, which is the same as FIG. However, the MT library control device 107 of the processing system A is connected to the processing system B disk control device 204 via the connection cable 230.

As shown in FIGS. 16 and 17, when the disk control device 104 and the MT library device 107 are connected via a channel cable, the MT control device 10
8 shows the processing of the MT library apparatus 107 and FIG. The connection cables 1601 and 1701 are described as channel cables. Here, it is assumed that the configuration relation information is managed by the MT library control device 107 in the configuration management information 1914. The processing system G800 is the MT controller 10
6 is executed by the control system process 1807, and the processing system H82 is executed.
0 is the control system process 1 of the MT library control device 107
907 is executed. MT library control device 107
Receives an MT library mount request in a request record at block 810. Block 811
In the case where the request record is analyzed and the designation of the MT cartridge for storing the backup data is, for example, the backup-only mode, the MT cartridge having the corresponding catalog is selected from the MT library 108 and set in the MT drive 110, Prepare for data storage. In block 812, a response record 1400 is created, and the MT controller 106 of the controller identifier 1301 of the device identifier 1404 of the storage destination and the number of the MT cartridge previously set in the MT drive (Volume Serial Number) are set as the device identifier 1302 of the device identifier 1302. Is set, and a response is transmitted to the disk control device 104 using a response record. In block 813, according to the received MT cartridge number, the configuration relation information 181 is displayed.
4, the backup source device identifier 1103, which is the attribute information of the relevant MT cartridge received, is set to the disk device identifier 1302 of the request record designated by the backup data, and the backup status 1104, which is the attribute information of the relevant MT cartridge, is being backed up. Set to. If the backup data write request is received in block 814, the process proceeds to block 815, where the backup data write request is
6 and return to block 814. At block 814, when the data has been received, the process proceeds to block 816. The MT controller 106 receives the data write request at block 801 and at block 812 sends the received data to the MT cartridge to store the data in the MT cartridge.
Transmit the data to the T drive. In block 816, the MT library control device 107 sets the disk device identifier corresponding to the device identifier 1103 of the backup source in the attribute information of the MT cartridge as the backup destination, and sets the differential backup completion to the backup status 1104. At block 817, a completion notification is transmitted to the disk control device 104 with the transfer data record.

The second embodiment is basically the same as the first embodiment. This can be realized by grasping different processing systems A and B as connection relation information stored in the disk control device 204 and the MT control device 106.

As described above, the disk controller 1
By issuing an instruction such as data backup from the service processor 109 connected to the server 04, data backup can be realized without changing the processing of the mainframe 101, and the first object of the present invention is achieved. Also, the configuration relation information 18 is provided on the MT control device 106 side.
14, the data stored in the MT library 108 can be stored in the disk device group 10 because a correspondence with the disk backed up in the MT library 108 is established.
5 and the I / O subsystem 132 having the disk goes down even if the mainframe 101
The disk data can be restored from the I / O subsystem 131 having the MT library without using the media library, and the second object of the present invention is achieved.

[0051]

According to the present invention, without changing the main frame,
Disk data of the I / O subsystem connected to the mainframe can be backed up to the magnetic tape library of the I / O subsystem connected to the mainframe without passing through the mainframe. Also,
Even when the I / O subsystem of the disk data goes down, the disk data can be restored without going through the mainframe, and flexible operability between the I / O subsystems becomes possible.

[Brief description of the drawings]

FIG. 1 is a diagram showing an example of an outline of a computer system to which the present invention is applied.

FIG. 2 is a diagram showing another example of the outline of a computer system to which the present invention is applied.

FIG. 3 is a diagram illustrating a configuration of a disk control device;

FIG. 4 is a diagram illustrating an example of a data backup processing flow in the disk control device.

FIG. 5 is a diagram illustrating an example of a differential data backup processing flow in the disk control device.

FIG. 6 is a diagram illustrating an example of a backup data restore processing flow in the disk control device.

FIG. 7 is a diagram illustrating an example of a data backup processing flow in the MT control device and the MT library control device.

FIG. 8 is a diagram showing another example of the data backup processing flow in the MT control device and the MT library control device.

FIG. 9 is a diagram illustrating an example of a constituent device information list;

FIG. 10 is a diagram illustrating an example of a lower-level device information list;

FIG. 11 is a diagram illustrating an example of an attribute list.

FIG. 12 is a diagram illustrating an example of a request record.

FIG. 13 is a diagram illustrating an example of a parameter record.

FIG. 14 is a diagram illustrating an example of a response record.

FIG. 15 is a diagram illustrating an example of a transfer data record.

FIG. 16 is a diagram showing another example of the outline of a computer system to which the present invention is applied.

FIG. 17 is a diagram showing another example of the outline of a computer system to which the present invention is applied;

FIG. 18 is a diagram illustrating a configuration of an MT control device.

FIG. 19 is a diagram illustrating a configuration of an MT library control device.

[Explanation of symbols]

101, 102: Main frame, 102, 103, 2
03: channel interface, 104, 204: disk control device, 105, 205: disk device group,
106: magnetic tape control device, 107: magnetic tape library control device, 108: magnetic tape library,
109, 209 ... service processor, 110 ...
MT drive device, 301: memory device, 302: MP
U, 303: host interface, 304: disk cache device, 305: I / O subsystem interface, 306: disk interface.

Claims (2)

[Claims] 1. A computer having a first computer
I / O subsystem and a second I / O subsystem are connected, and a first I / O subsystem and a second I / O subsystem are connected.
The first subsystem is connected by a network between the subsystems.
Copy the contents of the disk connected to the / O subsystem to the second
A method of backing up to an MT library connected to an I / O subsystem of the present invention, wherein a pointing device different from the computer connected to the first I / O subsystem is connected to the first I / O subsystem. The contents of the disc
Request to back up to the MT library connected to the I / O subsystem of the first I / O subsystem, and in the controller of the storage device of the first I / O subsystem, the contents of the disk connected to the first I / O subsystem Is read as backup data, a request to store the backup data in the second I / O subsystem via the network is transmitted, and the control device of the storage device of the second I / O subsystem receives the request. I / O for storing backup data, and holding, in the control devices of the storage devices of the first and second I / O subsystems, information on the connection relationship between the control devices and the storage relationship of the backup data.
Data backup method between subsystems. 2. A first computer connected to a first I / O subsystem of the computer, a second computer connected to a second I / O subsystem, and a first I / O subsystem connected to the first computer. An O subsystem and a second I / O subsystem are connected by a network, and the contents of a disk connected to the first I / O subsystem are transferred to an MT connected to the second I / O subsystem. In a method of backing up to a library, the contents of a disk connected to the first I / O subsystem are transferred from a pointing device separate from the first computer connected to the first I / O subsystem to a second computer. I / O
A request for backup to the MT library connected to the subsystem is issued, and the controller of the storage device of the first I / O subsystem uses the contents of the disk connected to the first I / O subsystem as backup data. Reads, transmits a request to store the backup data to the second I / O subsystem via the network, and stores the received backup data in the control device of the storage device of the second I / O subsystem. And a control device for a storage device of the first and second I / O subsystems, wherein information on a connection relationship between the control devices and a storage relationship of backup data is held. Method.