JP2000227868A - Backup acquiring method and computer system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To backup data, which are to be used by a computer to use the CKD format of a main frame or the like, with a miniaturized computer to use the fixed length block format of a personal computer or work station. SOLUTION: A storage device 300 provided with mutually different first and second interfaces 320 and 330 is connected to a host 100 having a first interface 110 and a host 200 having a second interface 210. The host 100 stores data through the first interface 110 into the storage device 300. The host 200 transforms the storage format of the data on the first interface to the storage format of the data on the second interface, acquires the storage position information of the data to be backed up, reads the data out of the storage device 300 on the basis of that storage position information and preserves them in a backup device 290.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a backup acquisition method in a computer system and a computer system using the backup acquisition method.

[0002]

2. Description of the Related Art In recent years, mainframes, personal computers, and workstations have become increasingly popular due to the "downsizing" of performing tasks conventionally performed on mainframes on small computers such as personal computers and workstations.
Computer systems in which different types of computers and operating systems are mixed have been constructed. As a technology for exchanging data between different types of computers or different types of operating systems, FTP (File Tra
Technologies such as nsfer protocol) and distributed databases are known. For such a technique, see, for example, Nikkei Open System February 1998 (no. 59) p. 2
30-p. 241 is disclosed.

Japanese Patent Application Laid-Open No. 9-258908 discloses a count key data format (CKD format) which is an I / O interface format of a mainframe, and a fixed length which is an I / O interface format of a small computer such as a personal computer or a workstation. Using a disk subsystem with both types of interfaces in block format,
A method for sharing data between different computers and different operating systems is shown.

[0004]

According to the above prior art, mainframe data is transferred to a small computer such as a personal computer or a workstation by data transfer via a network, and the data is stored in a tape device or the like connected to the small computer. Then you can get a backup. However, in this case, since the data transfer speed via the network is lower than the transfer speed of the I / O device, there is a problem that the backup processing time becomes longer.

[0005] In the method of acquiring a backup via a network, a processing load is applied to both the mainframe and the small computer. In particular, there is a problem that a processing load is generated not only in the small computer that stores data but also in the mainframe. Generally, the mainframe is high-speed processing such as transaction processing,
Since processing requiring high-speed response is performed, it is not preferable that a processing load is generated on the mainframe due to the backup processing. In addition, this method also has a problem that a transfer bandwidth load occurs on the network.

[0006] JP-A-9-258908 discloses that
For disk subsystems that have both CKD format and fixed-length block format interfaces, CKD
A small computer such as a personal computer or a workstation connected to the fixed-length block type interface reads out data stored in the mainframe connected to the interface of the fixed format, and shows a method of using the data in an application program on the small computer. ing. However, in this method, when data stored in the disk subsystem by the mainframe is stored in a tape device or the like connected to a small computer for backup, only the stored data is obtained in the application program on the small computer. Therefore, various management information related to the backup cannot be obtained. here,
The management information is information that is useful for backup acquisition processing and management, and data recovery processing (restore processing) using backup data, and includes, for example, position information for returning data at the time of restoration. Without the management information, when restoring backed up data, it cannot be returned to the original position. Therefore, Japanese Patent Application Laid-Open
It is impossible to obtain a backup of data created by a mainframe by a small computer using the technique disclosed in Japanese Patent Application Publication No. -258908.

[0007] A first object of the present invention is to store and obtain a backup of data used by a computer using a CKD format such as a mainframe in a tape device or the like connected to a computer using a fixed-length block format. An object of the present invention is to provide a backup acquisition method capable of realizing high-speed backup processing and reducing backup processing time. At this time, a second object of the present invention is to store and acquire a backup of data used by a computer using a CKD format such as a mainframe in a tape device or the like connected to a computer using a fixed-length block format. It is an object of the present invention to provide a backup acquisition method capable of reducing a processing load generated on a mainframe side or a network connecting two computers.

[0008]

SUMMARY OF THE INVENTION In order to solve the above problems, the present invention provides a storage device having a first interface and a second interface different from each other, and a first device connected to the storage device by the first interface. A computer and a backup acquisition method in a computer system including a second computer connected to the storage device by a second interface, wherein the first computer stores data stored in the storage device by the first interface in the second interface. Is read from the storage device by the second interface and stored.

From another viewpoint, a computer system according to the present invention comprises a storage device having a first interface and a second interface different from each other, and a first computer and a second computer connected to the storage device by the first interface. A computer system comprising a second computer connected to the storage device by a second interface, wherein the second computer converts data stored in the storage device in a storage format according to the first interface by the first computer. Means for detecting and reading by the second interface, means for converting the data storage format to the storage format according to the first interface for reading by the second interface, and storing the read data. Get a backup of the data used by the first computer Characterized in that a that means.

According to a preferred aspect of the present invention, an interface according to a count key data format is used as the first interface, and an interface according to a fixed length block format is used as the second interface. The management information created in the storage device by the first computer with respect to the data stored in the storage device by the first computer may be detected by the second computer, read out from the storage device, and stored. Also, the second calculator is
With respect to the data stored in the storage device by the first computer, the management information created in the storage device by the first computer may be detected and read from the storage device and used for controlling the backup acquisition process.

Further, according to another aspect of the present invention, a storage device having a first interface and a second interface different from each other, a first computer connected to the storage device by the first interface, and a storage device And a switching device connected by the second interface, a second computer connected to the switching device, and a backup device connected to the switching device.

When the first computer receives the backup request from the second computer, the first computer transmits the storage location information including the volume ID of the volume storing the data to be backed up and the physical address on the volume to the second computer. Notice. The second computer receives the storage location information and creates a command for instructing the switch device to copy the backup target data from the volume identified by the volume ID to the backup device based on the storage location information. And issue. The switch device copies the backup target data from the volume to the backup device according to the contents of the command.

[0013]

FIG. 1 is a block diagram of a computer system according to a first embodiment of the present invention.

The computer system according to the present embodiment has two
Host computers (hereinafter simply referred to as hosts) 1
00, 200, the disk subsystem 300 connected to both the host 100 and the host 200, and the host 200
Has a tape device 290 connected thereto. The host 100 and the host 200 are mutually connected via a network 400.

The host 100 has a disk subsystem 3
00 has a CKD interface 110 to connect to and a network interface 120 to connect to the network 400. The CKD interface 110 is
The interface conforms to the count key data format (CKD format).

The host 100 has an operating system 130, an application program 140 operating under the control of the operating system 130, and a backup agent program 150 as programs operating thereon. These programs are stored in a memory (not shown) of the host 100. Various processes by the host 100 are realized by executing these programs by a CPU (not shown).

The host 200 has a disk subsystem 3
00, a fixed length interface 210 to which the tape device 211 is connected,
And a network interface 220 connected to the network 400. Fixed length interface 21
0 and 211 are interfaces according to a fixed-length block format.

The host 200 includes, as programs, an operating system 230, a file access program 240 operating under the control of the operating system 230, and a format conversion program 25.
0, and a backup program 260. These programs achieve predetermined functions by being stored in a memory (not shown) and executed by a CPU (not shown).

The disk subsystem 300 has a disk 310, a CKD interface 320 connected to the host 100, a fixed length interface 330 connected to the host 200, and a CKD interface conversion means 340.

In the fixed-length block format, data is handled in a form called a block, for example, stored in a fixed-length storage area of 512 bytes. The specification of each book
Block number (LB) assigned to each block
This is performed using A).

In the CKD format, data is handled by storing it in a record that is a variable-length storage area. In CKD format, cylinder number (CC), head number (HH),
And the record number (R) is specified, and the record is specified. Hereinafter, an address for designating a record represented by a cylinder number, a head number, and a record number is referred to as CCHHR. A set of records represented only by a cylinder number and a head number is a track, and an address for specifying the track is called CCHH. A record in the CKD format includes three parts: a count part (C part), a key part (K part), and a data part (D part).
The C section has a fixed length, and stores the CCHHR and the lengths of the K section and the D section. The K and D sections are of variable length.

FIG. 2 is an explanatory diagram showing the relationship between the data structure in the CKD format and the disc on the disc.
In the figure, A is a data arrangement on a track in CKD format, and B is a disk 310 of CKD data shown in A.
This shows the data arrangement in the state stored in. In the present embodiment, the disk 310 physically follows a fixed-length block format. The CKD format data used by the host 100 is stored in the disk 310 after being converted into a fixed-length block format by the CKD interface conversion unit 340.

In the CKD format shown in FIG.
Reference numeral 10 denotes a home address, which indicates a track state and the like. R0C520 stores the record “(R
0 ”, and R0D 530 has the record“ R
R0D530 is used for storing management information and cannot store user data.
R1C540, R1K550, and R1D560 are the C part, the D part, and the K part of the record “R1” of record number 1, respectively.
, R2C570, R2K580, and R2D590 are C and D of the record “R2” of record number 2, respectively.
Part, part K. The user data is usually stored in the D section of the record after “R1”.

The disk subsystem 300 of the present embodiment
Then, HA510, R0C520, R0D of all the tracks
Reference numeral 530 is collectively stored in an area different from the record after R1. The records after “R1” are stored in blocks after LBA0 in the disk 310, for example, as shown in B in the figure. When the host 200 specifies the block 610 of LBA0 via the fixed length interface 330, the head of R1 of CCHHR = (0, 0, 1) is specified.

When the size of one record in the CKD format exceeds the size of one block in the disk 310, the record is divided into a plurality of continuous blocks and stored. For example, in the figure, the record "R1"
Are two blocks LBA1 and LBA2 (block 61
0, 620) and the following record “R2”
Is the following block, LBA2 (block 630)
Is stored in The length of the record does not always match the length of the fixed block. For this reason, the area from the end of the record to the end of the block is blank and filled with the value 0.

In the present embodiment, the size of the track is an integral multiple of the block. If the end of the record in the track does not coincide with the end of the track, zero is filled from the end of the record to the end of the track, and all tracks have the same number of blocks. At this time, CCHHR = (c, h,
The LBA indicating the head of the record specified by 1) can be calculated by LBA = (c × nh + h) × (nb) (Equation 1). Here, nh is the number of heads in one cylinder, and nb is the number of blocks in one track.

FIG. 3 shows that the host 100 sends the CKD interface 110 and the CK
The file (data set) and the data set management information in the CKD format created via the D interface 320 are shown.

A volume label 710 is stored at a specific position on the disk subsystem 300. The volume label 710 includes a VTOC (Volume Table Of Content).
ts) The position of 720 is held. The VTOC 720 records management information of a data set stored on the disk 310. VTOC 720 is, for example,
The record is composed of 44 bytes of K section and 96 bytes of D section. The K section stores a data set name, and the D section stores data set position information. The data set is stored in a continuous area, called an extent, composed of a plurality of tracks. One data set may be stored in a plurality of discontinuous extents.

The application program 140 on the host 100 communicates with the disk subsystem 30 via the CKD interface 110 and the CKD interface 320.
When reading / writing the data set on 0, processing is performed in the following procedure.

The application program 140 specifies the target data set and requests the operating system 130 to open the data set. The operating system 130 searches the record in the VTOC 720 to obtain the storage location of the data set. From the storage location of the acquired data set, the operation system 130 obtains the relative track and record number of the target record, and performs seek processing for the target record. The relative track is a relative track number with the beginning of the extent of the data set being 0.

Next, when performing a read, the application program 140 is executed by the operating system 130.
Is called. In the read processing, the operating system 130 transfers the D part of the record to the host 1
Read on 00. When writing, the application program 140 calls a write process of the operating system 130. In the write processing, the operating system 130 writes out the data prepared by the application program 140 as the D part of the record.

The procedure when the backup program 260 on the host 200 reads / writes a data set on the disk subsystem 300 via the fixed length interface 210 and the fixed length interface 330 is as follows.

The backup program 260 requests the open, read, write, close, VTOC read, and VTOC write processing of a data set to the file access program 240. The file access program 240 includes a backup program 260
Are processed in accordance with a unit such as a record and a set of records such as a track and a data set. The operating system 230 on the host 200
It does not have a function to read / write KD format data sets. For this reason, in the present embodiment, the format conversion program 250 intervenes between the file access program 240 and the operating system 230 to perform conversion between the CKD format and the fixed-length block format. It provides seek (positioning), read, write, close, VTOC read, and VTOC write processing. The file access program 240 executes a format conversion program 250 according to a request from the backup program 260.
, Open, read, write, close, VTOC read, and VTOC write. The seek process by the format conversion program 250 is performed as needed in conjunction with the read and write processes.

First, the open processing will be described. FIG. 4 is a flowchart of a process performed by the format conversion program 250 in response to a request to open a data set on the disk subsystem 300 by the file access program 240.

The format conversion program 250 has an internal buffer for one track. Format conversion program 250
Reads the volume label 710 stored in the disk subsystem 300 into the internal buffer for each track as described below, and obtains the volume label 710. Here, the storage location (CCHHR) of the volume label 710 on the disk subsystem 300 is given to the format conversion program 250 in advance.

For example, when the storage position of the volume label 710 is CCHHR = (0, 0, 3), the format conversion program 250 specifically performs the following processing to find the position. First, the format conversion program 250
The LBA corresponding to HH = (0, 0), that is, LBA0 is calculated from Equation 1 (step 1010), and 1 is calculated from LBA0.
The blocks for the track are read into the internal buffer (step 1020). As described with reference to FIG. 2, the format conversion program 250 refers to the C portion of “Record 1” at the beginning of the read block to determine the sizes of the K portion and D portion of “Record 1”, and The LBA storing 2 "is obtained (step 1030). Further, the LBA storing “Record 3” is obtained by referring to the C part of “Record 2”, and the D part of Record 3 where the volume label 710 exists is obtained (Step 1040).

The format conversion program 250 converts the volume label 710 stored in the D section of "record 3"
The storage position of the TOC 720 is obtained (step 105).
0), the LBA corresponding to the storage location is calculated from Equation 1 (Step 1060). Format conversion program 250
Reads a block for one track from the obtained LBA and obtains VTOC 720 (step 107).
0).

Next, the format conversion program 250 prepares a counter r and searches for a data set name in the VTOC 720. Specifically, the format conversion program 250
Sets the initial value of the counter r to 1 (step 108
0), the K portion of the record r in the read track is checked, and it is determined whether or not it matches the name of the data set to be processed (step 1090). If a record having a K part holding the name of the data set to be processed is found, the format conversion program 250 obtains the storage position of the data set from the D part of this record and stores it in an internal variable ( Step 1140). The format conversion program 250 has an internal pointer for storing a relative track to be read / written next and a record number. The format conversion program 250 sets this internal pointer to a value indicating “record 1” of relative track 0, and ends the open processing (step 1150).

If the corresponding record is not found in the judgment at step 1090, the format conversion program 25
0 determines whether or not the end of the read track has been checked (step 1100). If the end has not been checked, the counter r is incremented by 1 (step 1130), and the process returns to step 1090 to return to the next VTO in the next record.
C is searched. If a corresponding record is not found even after checking to the end of the read track, the format conversion program 250 reads the subsequent track from the disk 310 (step 1110), initializes the counter r to 1, returns to step 1090, and returns to step 1090. Search is continued from "record 1" in the track (step 112).
0).

Next, the seek processing by the format conversion program 250 will be described. Format conversion program 250
Indicates the “record 1” of the relative track 0 immediately after the data set is opened as described above. The file access program 240 requests the format conversion program 250 for processing by designating the target relative track. The format conversion program 250 calculates CCHH from the relative track, further obtains the LBA, and moves the internal pointer to the record position in the data set. The relative track indicates a relative position from the head track in the data set. If the extents related to the data set are all continuous areas, if CCHH of the first track is (c1, h1), CCHH = (c,
The relative track TT of h) is as follows: TT = (c−c1) × (nt) + h−h1 (2) Here, nt indicates the number of tracks in one cylinder. Conversely, CCHH can be obtained from TT.
In the present embodiment, for the sake of simplicity, it is assumed that all extents are continuous areas. However, even if all extents are not continuous areas, it is possible to obtain the correspondence between TT and CCHH and calculate them mutually.

FIG. 5 is a flowchart of the read process. The internal pointer (buffer pointer) of the format conversion program 250 holds the relative track, record number, and read / write position in the internal buffer of the data set to be processed by the above-described seek processing. The format conversion program 250 that has received the read processing request from the file access program 240 checks whether the track specified by the internal pointer has already been read into the internal buffer (step 2010). If the designated track has not been read, CCHH is calculated from the relative track indicated by the internal pointer, and LBA is calculated from this value (step 202).
0). The format conversion program 250 reads a block for one track from the calculated LBA into the internal buffer (step 2030). If the track has already been read in step 2010, step 2020,
The processing of 2030 is not performed.

Next, the format conversion program 250 passes only the D portion from the record read into the internal buffer to the file access program 240 (step 2040).
It is determined whether the read processing has been performed up to the last record in the track (step 2050). If the last record in the track has not been read, the internal pointer is moved to the next record, and the process ends (step 2070).
The head of the next record is obtained by referring to the C section of the current record. If the read processing has been performed up to the last record in the track, the internal pointer is moved to the record of record number 1 of the next track, and the processing ends (step 2060).

FIG. 6 is a flowchart of the write process. In the write process, the format conversion program 250
Creates CKD format contents for one track in the internal buffer, and writes the contents to the disk subsystem 300 on a track-by-track basis.

In response to the write processing request, the file access program 240 passes the write data and the write data length to the format conversion program 250. The format conversion program 250 can create the C part of the record from the write data and the write data length, the relative track and record number to be processed held by the above-described seek processing, and the record length obtained from the VTOC.

Format conversion program 2 in write processing
50 calculates CCHHR as information of the C section (step 3010). A part C is created from the CCHHR and the record length and written into the internal buffer (step 302).
0), and then write the write data as the D portion of the record (step 3030). Since the next record starts from the beginning of the next block, if the written data does not reach the end of the block, 0 is written up to the beginning of the next block (step 3040).

In step 3050, it is determined whether the next record can be written on the current track.

In this embodiment, since the data set to be used is a fixed-length record, the determination in step 3050 can be made from information such as the record length. Step 305
If it is determined at 0 that the next record can be written, the internal pointer is moved to the start position of the next record, and the write processing ends (step 3060). If not, 0 is written from the current write position of the internal buffer to the end of the current track (step 3070), and the contents of the internal buffer are written to the disk subsystem 300 as the contents of one track (step 3080). . And
The internal pointer is moved to the record of record number 1 of the next track, and the write processing ends (step 309).
0).

Next, the VTOC read and VTOC write processing performed by the format conversion program 250 will be described.

FIG. 7 shows a flowchart of the VTOC read and VTOC write processing.

From the file access program 240 to V
The format conversion program 250 that has received the request for the TOC read or the VTOC write performs the same processing as Steps 1010 to 1130 in the data set open processing, and performs the processing for the VTOC data set from the given processing target data set name. The position of the record in the internal buffer and the storage position (LBA) in the disk subsystem 300 are obtained and searched, and the record is obtained in the internal buffer (steps 4010 to 4130). Here, similarly to the open processing, the storage position is CCHHR =
It is assumed that it is given by (0, 0, 3).

After the above processing, it is determined whether the processing to be performed is a VTOC read or a VTOC write (step 414).
0). VTO from file access program 240
Format conversion program 250 for C read request
Transfers the contents of the record in the internal buffer to the file access program 240 and ends the VTOC read processing (step 4150).

In response to a VTOC write request from the file access program 240, the format conversion program 2
50 receives the record contents of the format indicating the VTOC from the file access program 240, and creates the contents of the track including the record on the internal buffer (step 4160). Then, the contents of the internal buffer are written back to the disk subsystem 300 as the contents of one track, and the VTOC write processing ends (step 417).
0). It is assumed that there is no change in the configuration of the VTOC before and after writing back, and that the size of the VTOC does not change.

By the VTOC read and VTOC write processing of the format conversion program 250 and the file access program 240 described above, the backup program 260 can request the VTOC read from the file access program 240 and obtain the VTOC contents. Further, the record content in the format storing the VTOC is passed to the file access program 240 to
By requesting the OC write, the VTOC can be rewritten.

In the close processing, the format conversion program 250 releases internal variables and the like for the processing target data set set in the seek processing in response to a close processing request from the file access program 240.

FIG. 8 is a flowchart of a backup process performed by the backup program 260 on the host 200. The target of the backup processing is a data set on the disk subsystem 300 used by the host 100 via the CKD interface 320.

The backup program 260 first stores information that can specify a target data set, such as a data set name set by the user, into the backup agent program 1 on the host 100 via the network 400.
50 (step 5010). The backup agent program 150 checks the status of the data set with the operating system 130 on the host 100 based on this information (Step 5020). For example, it is possible to acquire a state such as the data set being used (opened) by confirmation. The backup agent program 150 passes the acquired state to the backup program 260 via the network 400 (Step 5030). Backup program 2
The control unit 60 can perform control, determination, and scheduling such as performing / not performing / deferring backup of the data set based on the received status. Here, however, in the present embodiment, the backup program 2
Reference numeral 60 indicates that the backup process is to be continued.

The backup program 260 requests the file access program 240 to open a data set (step 5040). File access program 240 and format conversion program 250
Performs an open process in response to this request (step 5050). The backup program 260 requests the file access program 240 for a VTOC read for the data set (step 5060), and as a result of the VTOC read processing by the file access program 240 and the format conversion program 250, the VTOC read is performed.
The record of C is obtained (step 5070). The backup program 260 stores this VTOC record in the tape device 290 connected to the host 200 (Step 5080). At the time of saving, the backup program 260 may add information such as a backup acquisition date and time.

Further, the backup program 260
A request to read the data set is issued to the file access program 240 (step 5090), and the file access program 240 and the format conversion program 250 are read.
The contents of the data set are obtained as a result of the seek processing and the read processing according to (step 5100). The backup program 260 stores the contents of the data set in the tape device 290 (Step 5110). At the time of saving, the backup program 260 may add information such as a backup acquisition date and time.

If the purpose of the process is merely to acquire and save the contents of the data set without using the VTOC as management information as described later, steps 5060, 5070, and 5080 need not be performed. Good.

Next, a description will be given of a restore process (data recovery process using backup data) performed by the backup program 260 on the host 200.

The target of the restoration process is that the host 100
This is a data set on the disk subsystem 300 that is used via the KD interface 320, and has already been backed up to the tape device 290 by backup processing. As one example of the recovery destination by the restore processing, it is conceivable to directly recover the data set that has been backed up in the disk subsystem 300.

FIG. 9 shows a flowchart of a restore process when the data set of the disk subsystem 300 is directly restored.

The backup program 260 transmits information that can specify a target data set such as a data set name set by the user to the backup agent program 15 on the host 100 via the network 400.
0 (step 6010). The backup agent program 150 locks using the operating system 130 based on the received information so that other processes on the host 100 do not access the data set (step 6020). The backup agent program 150 notifies the backup program 260 of the completion of the lock via the network 400 (Step 6030).

Next, the backup program 260
It requests the file access program 240 to open the data set (step 6040). File access program 240 and format conversion program 2
Receiving this request, 50 performs open processing (step 6050). The backup program 260 reads the VTOC record of the backed up data set from the tape device 290 (Step 606).
0). The backup program 260 requests the file access program 240 to write the read VTOC, that is, the VTOC for the data set (step 6070), and the VTOC by the file access program 240 and the format conversion program 250.
As a result of the write process, the VTOC on the disk subsystem 300 relating to the data set is changed with the VTOC record read from the tape device (step 6).
080).

Further, the backup program 260
The contents of the backed up data set are read from the tape device 290 (step 6090). The backup program 260 requests the file access program 240 to write the read contents to the data set (step 6100). As a result of the seek processing and the write processing by the file access program 240 and the format conversion program 250, the backup program 260 The content is written back to the storage location of the data set (step 6110).

Thereafter, the backup program 260
Allows the backup agent program 150 to release the lock via the network 400 (step 6120). The backup agent program 150 receives this and releases the lock (step 6130). With the above processing, the data set can be restored.

As another example of the recovery destination by the restore processing, when the arrangement or configuration of the data set in the disk subsystem 300 has changed between the time of the backup and the time of the restore, the data set that has been backed up Another data set may be prepared, and the content may be restored to that data set. FIG. 10 shows a flowchart of the restore processing in this case.

First, the backup program 260 reads the VTOC record of the backed up data set from the tape device 290 for the target data set set by the user, and acquires the data set configuration information such as the record length. (Step 701
0). The backup program 260 passes the configuration information obtained via the network 400 to the backup agent program 150 on the host 100 (Step 7020). The backup agent program 150 prepares another appropriate data set on the disk subsystem 300 using the operating system 130 on the host 100 based on the configuration information (Step 7030). The backup agent program 150 passes information that can specify another data set, such as a data set name, to the backup program 260 via the network 400 (Step 7040).

Next, the backup program 260
It requests the file access program 240 to open another data set (step 7050). The file access program 240 and the format conversion program 250 perform open processing in response to this request (step 7060). The backup program 260
The contents of the backed up data set are read from the tape device 290 (step 7070). The backup program 260 requests the file access program 240 to write the read contents to another data set (step 7080), and the file access program 240 and the format conversion program 2
The contents are written back to the storage position of another data set as a result of the seek processing and write processing by 50 (step 7090).

With the above processing, the restoration processing to another data set can be performed. The user can use the backup program 260 or the backup agent program 15
From 0, the data set names of other data sets can be known.

In the embodiment described above, the backup program 260 and the file access program 240 are described as separate programs, but the processing of both the backup program 260 and the file access program 240 is performed using the format conversion program 250. It may be realized as one program to be executed.

By performing the above processing, when the host 200 uses the tape device 290 to perform the backup processing and the restore processing of the data set on the disk subsystem 300 used by the host 100 via the CKD interface 320. In addition, the processing can be performed at high speed, and the time required for the backup processing and the restore processing can be reduced. Further, since the host 100 does not need to perform the data transfer process in the backup process or the list process, the processing load on the host 100 can be reduced. Further, the host 100
Since data transfer between the host and the host 200 via the network does not occur, an increase in the transfer bandwidth load of the network can be suppressed. Furthermore, the host 100
By using the management information created on the disk subsystem 300 as the management information in the backup process, the backup process and the restore process can be easily and efficiently performed.

FIG. 11 is a configuration diagram of a computer system according to the second embodiment of the present invention. The difference between this embodiment and the first embodiment is that the disk subsystem 3
00 is that there is no CKD interface conversion means 340 and there is a fixed length interface conversion means 350. In this embodiment, the disk 310 is physically
When the host 200 reads and writes data on the disk 310 via the fixed-length interface 210 and the fixed-length interface 330 according to the KD format, the fixed-length interface conversion unit 350 converts the data between the CKD format and the fixed-length block format. Perform the conversion.

The correspondence between the CKD format converted by the fixed-length interface converting means 350 and the fixed-length block format is the same as that described in FIG. 2 in the first embodiment. In the present embodiment, A shown in FIG. 2 is the actual data arrangement in the CKD format on the disk 310, and B in FIG.
Is converted by the fixed-length interface conversion means 350, and becomes a data arrangement in a fixed-length block format used for transfer between the fixed-length interface 210 and the fixed-length interface 330. Fixed length interface conversion means 3
50 is C as in the case of the first embodiment.
The conversion between the KD format and the fixed-length block format is performed.

In this embodiment, the host 100 and the host 200 can perform the same processing as the processing described in the first embodiment on the data set stored in the disk subsystem 300. Host 10
0, the operating system 130 and the backup agent program 150 on the host 200, and the operating system 230, the file access program 240, the format conversion program 250, and the backup program 260 on the host 200 are the same as the respective processes described in the first embodiment. Performs processing and implements backup processing and restore processing for the data set. For the specific processing contents of these programs, see
There is no difference from the first embodiment, and the description is omitted.

According to the second embodiment described above, the same effects as in the first embodiment can be obtained.

Next, a third embodiment of the present invention will be described. The configuration of the computer system in the present embodiment is as follows:
The configuration is the same as that of the first embodiment shown in FIG. In the present embodiment, the backup processing described with reference to FIG. 8 in the first embodiment is different from the first embodiment.

FIG. 12 shows the host 20 in this embodiment.
11 is a flowchart of a backup process performed by a backup program 260 on the backup program 0. The target of the backup processing is a data set on the disk subsystem 300 used by the host 100 via the CKD interface 320.

The backup program 260 on the host 200 stores information that can specify a target data set such as a data set name set by the user on the network 4.
00 to the backup agent program 150 on the host 100 (step 8010). The backup agent program 150 checks the status of the data set with the operating system 130 on the host 100 based on this information (Step 80).
20). With this confirmation, it is possible to acquire a state such as whether the data set is in use (opened).

Backup Agent Program 15
0 indicates that the acquired state is the network interface 12
0 to the backup program 260 (step 8030). The backup program 260 controls / determines, based on the received status, such as performing / not performing / deferring backup of the data set,
Alternatively, scheduling can be performed. Here, it is assumed that the backup processing is continued.

The backup program 260 requests the file access program 240 to open a data set (step 8040). File access program 240 and format conversion program 250
Performs an open process in response to this request (step 8050). The backup program 260 requests the file access program 240 to perform a VTOC read on the data set (step 8060), and as a result of the VTOC read processing by the file access program 240 and the format conversion program 250, the VTOC read is performed.
The record of C is obtained (step 8070).

The backup program 260 has a VTO
The last reference date of the data set recorded in the record of C is compared with a date set in advance by the user (step 8080), and the context is determined (step 8090). If the last reference date is a date before the set date, the backup program 260 stops backup processing for the data set (Step 8).
100). If the last reference date is later than or equal to the set date in step 8090, the backup program 260 continues the backup process for the data set.

When continuing the backup process, the backup program 260 stores the VTOC record in the tape device 290 connected to the host 200 (Step 8110). At the time of storage, information such as a backup acquisition date and time may be added. Further, the backup program 260 stores the file access program 24
0 is requested to read the data set (step 81
20), the contents of the data set are obtained as a result of seek processing and read processing by the file access program 240 and the format conversion program 250 (step 8)
130). The backup program 260 saves the contents of the data set in the tape device 290 (Step 8140). At the time of storage, information such as a backup acquisition date and time may be added.

Processes other than the backup process in this embodiment are performed in the same manner as in the first embodiment.

In the backup process described in this embodiment, in addition to the last reference date, the VTOC such as the creation date
May be used to control the backup process. Instead of the setting date specified by the user, the date of the last backup processing recorded by the backup program 260 at the time of the last backup processing may be used. The backup processing described here can be similarly applied to the configuration of the above-described second embodiment.

In the present embodiment, the same effects as in the first and second embodiments can be obtained.

FIG. 13 is a schematic diagram showing a configuration and a schematic operation of a computer system according to the fourth embodiment of the present invention. In the figure, reference numeral 1 denotes an open server constituted by an open computer such as a workstation or a personal computer.

The open server 1 corresponds to the host 200 in the above-described first to third embodiments, and accesses the disk device according to the interface of the FBA format. The open server 1 is connected to the switch 3 via a fiber channel 7. The switch 3 is a device that routes a transmission packet. Access from the open server 1 to the disk system 4 is performed by the switch 3
Is done via There is also a connection method that does not pass through the switch 3. The switch 3 is a fiber channel 7
Is connected to the disk system 4. The open server 1 accesses the disk system 4 by a protocol called FCP in which a conventional protocol on SCSI is implemented on Fiber Channel.

Reference numeral 2 denotes a so-called mainframe computer (hereinafter abbreviated as mainframe). The mainframe 2 corresponds to the host 100 in the above-described first to third embodiments, and accesses a disk device according to a CKD format interface. The mainframe 2 is connected to a disk system 4 by a channel interface 6. For example, a routing device called a director may be interposed between the mainframe 2 and the disk system 4.

The disk device 4 has a volume 8 in which user data is stored. The disk device 4 has a CK
D interface 9 and FBA interface 10, and the same volume 8
It is possible to access

The open server 1 instructs the mainframe 1 to back up a target data set via the network 14 according to a backup instruction from a user or when a predetermined time has arrived. At this time, the open server 1 notifies the name of the data set to be backed up to the mainframe 1 ().

The data set position detection program 12
It detects at which address of which volume 8 the target data set exists, and notifies this information to the open system 1 as data set position information (). In this embodiment and the embodiments described below, it is assumed that the data set position information is acquired by the mainframe 2 and transmitted to the open server 1, but the open server 1 refers to the catalog information and the VTOC information from the volume 8. By doing so, the data set position may be grasped. In this case, the volume 8 storing the data set and the related catalog may be given by the user in advance, or may be instructed from the mainframe 2. Alternatively, as in the first to third embodiments, the VTs of all the shared volumes are
It is also possible to read the OC information and acquire the data set position information.

The open system 1 creates a command (referred to as a CCOPY command) based on the data set position information given from the main frame 2 by the copy command creation / issuing program 11, and issues the command to the switch 3 ( ,). The CCOPY command includes
A copy source volume number and copy address, a copy destination tape number, and the like are stored. The switch 3 reads data from the volume 8 based on the information, and backs up the data to the tape device 5 (). Hereinafter, such backup processing will be described in detail.

FIG. 14 is an explanatory diagram showing details of the data set position information.

The number of subsystems 16 indicates the number of logical disk systems that store the data set. In recent disk systems 4, a single physical disk system may appear to the mainframe 2 or the open server 1 as a logically multiple disk system. This logical disk system is called a subsystem here. The disk system serial number 17 is
This is a number for uniquely identifying the disk system 4. The subsystem ID 18 is the disk system 4
Is the ID assigned to the. The volume ID 19 is an ID of the volume 8 storing the data set to be backed up, and is a unique number for each subsystem.

The number of extents 20 indicates the number of continuous areas storing the data set. Extent start CCHH21 by the number indicated by the number of extents 20
And an entry of the extent end CCHH 22 appear. In the figure, three extent start and end CCHs
H is shown. When the data set is stored across a plurality of volumes 8, subsystems, and disk systems, the number of subsystems 16 stores a value of 2 or more, and entries from the disk system serial number 17 to the end of extent CCHH22 are stored. Repeated. The mainframe 2 transmits the data set position information to the open server 1 in this format.

The open server 1 needs to check as to which device file the volume 8 indicated by the volume ID 19 of the data set position information is registered. In the open server 1, the program accesses the volume 8 via the device file. For this reason, the open server 1
Issue the Inquiry command.

FIG. 15 shows the return values of the Inquiry command. A part of the return value of the Inquiry command can be independently defined by the vendor, and FIG. 15 shows only a part defined for realizing the present embodiment. Disk system serial number 25 and subsystem ID 26 are In
Shows the serial number and subsystem ID of the disk system 4 that has processed the inquiry command. Volume ID 2
Reference numeral 7 denotes a volume ID corresponding to the device file name that has issued the Inquiry command. The emulation type 28 is set to three types: dedicated to mainframe, shared, and open, and in the case of dedicated to mainframe and shared, a specific disk system type is set. Each type has a different track format and capacity. The volume capacity 29 indicates the capacity of the volume 8 in MB units.

The Inquiry command takes time because it is issued to all device files of the open server 1. For this reason, it is better to issue the Inquiry command only once when the system is booted, and to hold the return value. Some recent OSes can incorporate a volume without booting the system. In such an OS, when the volume 8 is installed, it is preferable to execute the Inquiry command only for the volume 8 and obtain its return value. By comparing the return value of the Inquiry command with the data set position information, the volume ID corresponding to the device file name can be found. That is, the respective disk system serial numbers, subsystem IDs, and volume IDs are compared. Inquiry if these match
It can be seen that the device file that issued the command has the volume ID given by the data set position information.

When the device file is determined in this manner, the open server 1 determines that the next data set position is
Find the address on the device file.

The address on the device file is CKD
The logical configuration of the volume 8 in the format,
It can be obtained by (Equation 1) based on the track length of the volume 8 in the CKD format, the number of tracks per cylinder, and the block size in the FBA format.
The logical configuration of the volume in the CKD format differs depending on the emulation type, and is recognized based on the emulation type 28 acquired by the Inquiry command.

Based on these information, open system 1
Creates a copy command. FIG. 16 shows an example of the format of the copy command. The copy command shown in the figure is 0x10 blocks from address 0 of volume 8,
And 0x10 block from address 100 to one C
It is assumed that copying is performed to the tape device 5 by a COPY command.

The open server 1 has a CDB (Command Descri
After ptor Block), switch the parameter list to switch 3.
Send to The parameter list is variable, and its length is stored in Parameter List Length 32 of the CDB.

The parameter list is a Target Descriptor List in which the source and destination device addresses are stored.
Segment Descri in which information about the address on the device where the data to be copied is stored is stored.
It is composed of a ptor list 36. The length of these lists is variable, and their lengths are
r Length 33 and Segment Descriptor Length 34 are stored.

The Target Descriptor List 35 includes a plurality of Tas.
Consists of rget Descriptor. In the figure, the copy source disk device and the copy destination tape device Targ
et Descriptor is shown. Meanwhile, Segment Descrip
The tor List has two Segment Descriptors: a parameter that copies 0x10 blocks from address 0 and a parameter that copies 0x10 blocks from address 100.
Having.

The open server 1 transmits the CC
When the OPY command is issued to the switch 3, the switch 3 copies data from the volume 8 to the tape 5 according to the command.

When the backup is completed, the data set information recording program 23 registers the data set information shown in FIG. 17 in the backup directory, that is, the backup management file (). The registered contents include the host name 40 of the mainframe 2 owning the data set, the disk system serial number 41 storing the data set, the subsystem ID 42, and the volume I
D43, which are included in the data set position information. Further, the backup date and time 44, data set name 4
5, the data set size 46, the extent range of the data set (extent start CCHH55 and extent end CCHH56) and the like are registered. If there are a plurality of extents constituting the data set as shown in the figure, a plurality of extent ranges are recorded.

[0108] These pieces of information may be registered as one table, but as shown in FIG.
If the directory is configured by using 0 and the data set name 45 as keys, management becomes easier. In this example, the host name that owns the backup file is traced from the backup directory “backDir”. In the figure, “MFDB2MAI
"N" owns the desired dataset "DB2SYS"
It is registered as a child directory. In addition, “DB2SY
The time when the data set was backed up from “S” is registered as its child directory “1999.8, 7.00: 12.” For example, if the same data set is backed up periodically, there must be multiple child directories Then, a file that stores detailed backup information is stored in the child directory.

Normally, the user often performs recovery based on the name of the mainframe 2 and the file name. In addition, consider when you backed up and when it can be recovered to. In such a case, the directory structure shown in FIG. 18 is effective. Furthermore, since the backup information of the open system is also managed by the same mechanism,
It is convenient because management can be integrated.

FIG. 19 is a schematic diagram showing a configuration and a schematic operation of a computer system according to the fifth embodiment of the present invention. In the present embodiment, backup is performed using a known volume duplication function of the disk system 4.

When a backup request is issued from the open server 1, the mainframe 2 obtains the physical position of the data set requested to be backed up, that is, the data set storage volume 8 and the extent. Next, the volume duplication control program 49 causes the volume 8
Check whether is in a duplex state. If the volume is in a duplex state, the volume redundancy control program 49
A pair split request is issued to the disk system 4 (').

When the pair division is successful, the main frame 1
Reports the data set position information so that the open server 2 performs backup from the secondary volume 8b. Therefore, of the data set position information shown in FIG. 14, the subsystem ID 18 and the volume ID 19 of the secondary volume 8b are stored. Subsequent processing is the same as in the fourth embodiment, and a description thereof will be omitted.

According to the present embodiment, the database (DB)
After the application such as the application is quiesced, the secondary volume 8b is frozen to obtain a backup that is consistent with the application. In addition, since the stationary state may be maintained until the command for dividing the pair is completed, the stationary state is very short. Further, the volume 8b for performing the backup and the volume 8a for accessing the mainframe 2
Therefore, the influence of the performance on the mainframe 2 in the normal business can be reduced.

FIG. 20 is a schematic diagram showing a configuration and a schematic operation of a computer system according to the sixth embodiment of the present invention. In this embodiment, the volume duplication function is realized between the different disk systems 4a and 4b, and backup is performed from the disk system 4b.

The disk systems 4a and 4b are connected by the fiber channel 7. Data is transferred from the volume 8a of the disk system 4a to the volume 8b of the disk system 4b via the fiber channel 7,
Duplex state is maintained.

The basic processing in this embodiment is the fifth
This is the same as the embodiment. When performing backup, the volume duplication control 49 of the mainframe host 2
A pair split instruction is issued to the disk system 4a, whereby the duplex state is suspended. Thereafter, the data set position information is transmitted to the open server 1. In the data set position information shown in FIG. 14, the disk system serial number 17 stores the disk system 4b, and includes the subsystem ID 18 and the volume ID.
19 stores the data of the secondary volume 8b. Subsequent processing is the same as in the fourth or fifth embodiment, and a description thereof will be omitted.

According to the present embodiment, the disk system 4
A backup system with higher data protection can be provided by arranging “a” and the backup 4b at remote locations. For example, in a wide-area disaster such as an earthquake, if the distance between the disk system 4 and the backup 5 is short, both may be damaged and data may be lost. However, such a danger can be avoided by installing the backup device 5 in a remote place as in the present embodiment.

FIG. 21 is a schematic diagram showing a process of restoring backed-up data according to the seventh embodiment of the present invention. In the restore processing, the data set is not always restored to the original storage position. Since a record constituting the data set has a count section which is a field storing the physical position of the record, if the restore position is different from the position at the time of the backup, it needs to be rewritten. In the present embodiment, this processing is executed by the open server 1.

The open system 1 includes a mainframe 2
Issue a restore request via the network 14. The parameters attached to the restore request include data set name, data set size, serial number of the disk system to be restored, subsystem ID, and volume I
D, etc. are included. The data set name, the restoration destination disk system serial number, the subsystem ID, and the volume ID are specified by the user. The data set size is obtained from the file in the backup directory created at the time of backup.

In some cases, the mainframe 2 to be restored may be different from the one at the time of backup. For example, there is a case where the mainframe 2 that owns the data set is down and cannot be recovered. Therefore, the restore request is sent to the mainframe 2 that owned the file.
Is not necessarily issued to

Subsequently, the main frame 2 secures a data set area on the volume 8 specified by the specified disk system 2, subsystem ID, and volume ID by the data set area securing processing 50. Then, the physical position information, that is, the extent position is obtained. The mainframe 2 reports this physical location information to the open server 1. As described with reference to FIG. 14, the extent position is the extent start CCHH and the end CCH.
It is composed of a set of CHHs.

The open server 1 reads data to be restored from the backup medium specified by the backup device serial number 47 and the backup medium name 48. Then, the counting unit is updated based on the extent information reported from the main frame 2 by the counting unit change processing 51. Thereafter, a block address is calculated from the extent information, and the restore data is written to the corresponding block.

FIG. 22 is a schematic diagram of another restore processing according to the eighth embodiment of the present invention. In the present embodiment, as shown in the figure, the open server 1 reads the restore data from the backup device 5, performs necessary data shaping processing, and then transfers the restore data to the mainframe 2 via the network 14. In the main frame 2, after securing a data set area of a designated size, data is stored in the data set area.

In the embodiments described so far, the data set is backed up including gaps and padding data which are originally unnecessary. In the restore processing, the restore data may be sent to the mainframe 2 while including these data, but the network load increases and the restore time also increases.

The data shaping process 53 executes a process for removing these unnecessary data. Open server 1
Since the user knows the track format, it is possible to know where the gap is and how many bytes are present, and detect the end of the record to know how many bytes are left in the track and perform data shaping processing.

This embodiment is different from the seventh embodiment in that
Since the data is transferred to the mainframe 2 via the network, there is a disadvantage that the network load increases and the restoration time becomes longer.

FIG. 23 is a schematic diagram of still another restore processing according to the ninth embodiment of the present invention. In the seventh or eighth embodiment, when the restore target volume is different from the backup volume, the open server 1 reads the restore data from the tape device 5, updates the count unit, and restores. If the restore volume is the same as the backup volume, there is no need to update the count section. In this embodiment, when this condition is satisfied, backup is performed without passing through the open server 1.

In this embodiment, the open server 1
Has a direct restore availability determination process 54. In this process, when the data set position of the restore destination is received from the mainframe 1, whether the volume and the data set position of the restore destination match the volume and the data set position of the backup based on the contents of the backup directory Determine whether If they match, it is determined that it is not necessary to change the count unit, control is passed to the copy process 11, and the copy destination volume 8 is restored from the tape device 5 by the CCOPY command.
Restore directly to.

If the emulation type of the restore volume is different from that at the time of backup, restoration cannot be performed. Therefore, in the restore processing in the seventh to ninth embodiments, when the open server 1 receives the data set position information from the mainframe 2, it checks whether the emulation type of the restore volume matches the one at the time of backup. . For this purpose, the open server 1 reads out the emulation type of the volume stored in the data set position information using the Inquiry command. Then, it is compared with the emulation type 57 of the backup volume stored in the backup directory, and it is checked whether they match. If they do not match, the open server 1 reports an error to the user and stops the restoration processing.

FIG. 24 is a schematic diagram of a database recovery process according to the tenth embodiment of the present invention. When recovering a database in a database system, the database itself and its log are restored as needed. The user can select the backup data to be restored, and the data at the selected time is restored. From here, logs can be applied to the restored data to recover the database to a more recent state.

In this embodiment, first, the database body and the log are recovered by the restore processing in any of the seventh to ninth embodiments. Thereafter, the log is applied to the database recovered by the mainframe 2. In the following description, the description will be made from the state where the restoration processing to the volume 8 is completed.

The open server 1 has a DB recovery manager 61. The DB recovery manager 61 mainly manages a user interface. That is, display of a data set of a recovery candidate, display of a recovery result, input of a recovery target file and a recovery time, and the like are executed.

The database management system provides a DB recovery program 63 for recovering a data set. The DB recovery program 63 searches the log volume 8e for a transaction that has updated the data set to be recovered, and uses this log to reflect the update to the data set (roll forward) or restore it to its original state (roll back). Perform processing. The DB recovery program 63 generally receives the name of the data set to be recovered and the time, and executes an AP for executing the recovery.
I. The DB recovery agent 60 performs a recovery process using this API.

When a recovery request is issued from the user together with the data set name and time using these mechanisms, the recovery processing is executed in cooperation with these three processing programs.

With the above processing, the recovery of the database owned by the mainframe 2 can be executed from the open server 1 side.

According to the embodiment described above, the management of backup files can be centralized without distinction between a mainframe and an open system, and the cost of the user for backup and restoration can be reduced.

Further, the data of the mainframe can be copied to the tape device without going through the open server, so that the CPU load of the mainframe and the open server can be reduced, and the time required for backup and restoration can be reduced.

[0138]

According to the present invention, for example, when a backup of data used by a computer such as a main frame using the CKD format is stored and acquired on a tape device or the like connected to the computer using the fixed-length block format, In addition, high-speed backup processing can be realized, and backup processing time can be reduced.

When a backup of data used by a computer such as a mainframe using the CKD format is stored and acquired on a tape device or the like connected to the computer using the fixed-length block format, the data is transferred to the computer such as the mainframe. The generated processing load can be reduced.

Further, when a backup of data used by a computer such as a mainframe using the CKD format is stored and obtained on a tape device or the like connected to a computer using the fixed-length block format, the computer such as the mainframe uses a backup. It is possible to realize backup processing and restore processing in which management information created for data is acquired and used by a computer using a fixed-length block format.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a computer system according to a first embodiment of the present invention.

FIG. 2 is an explanatory diagram showing a relationship between a data structure in a CKD format and a disc on a disc.

FIG. 3 is an explanatory diagram showing a data set in CKD format and data set management information created by a host.

FIG. 4 is a flowchart of a process performed by a format conversion program 250 in response to a data set open request.

FIG. 5 is a flowchart of a data set read process by a format conversion program 250;

FIG. 6 is a flowchart of a data set write process by the format conversion program 250.

FIG. 7 is a flowchart of VTOC read processing and VTOC write processing by the format conversion program 250;

FIG. 8 is a flowchart of a backup process.

FIG. 9 is a flowchart illustrating an example of a restore process according to the first embodiment of the present invention.

FIG. 10 is a flowchart of another example of the restore processing according to the first embodiment of the present invention.

FIG. 11 is a configuration diagram of a computer system according to a second embodiment of the present invention.

FIG. 12 is a flowchart of a backup process according to a third embodiment of the present invention.

FIG. 13 is a schematic diagram showing a configuration and a schematic operation of a computer system according to a fourth embodiment of the present invention.

FIG. 14 is an explanatory diagram showing details of data set position information.

FIG. 15 is a format diagram showing a return value of an Inquiry command.

FIG. 16 is an explanatory diagram showing an example of a format of a copy command.

FIG. 17 is a data format diagram showing a configuration of data set information.

FIG. 18 is an explanatory diagram of a directory structure when storing data set information.

FIG. 19 is a schematic diagram showing a configuration and a schematic operation of a computer system according to a fifth embodiment.

FIG. 20 is a schematic diagram showing a configuration and a schematic operation of a computer system according to a sixth embodiment.

FIG. 21 is a schematic diagram of a restore process of backed-up data according to the seventh embodiment.

FIG. 22 is a schematic diagram of a restore process according to the eighth embodiment.

FIG. 23 is a schematic diagram of a restore process according to the ninth embodiment.

FIG. 24 is a schematic diagram of a database recovery process according to the tenth embodiment.

[Explanation of symbols]

100: Host, 110: CKD interface, 12
0, 220 ... network interface, 130, 2
30 operating system, 140 application program, 150 backup agent program, 200 host, 210, 211 fixed length interface, 240 file access program, 250 format conversion program, 260 backup program, 290 tape device, 300: Disk subsystem, 310: Disk, 320: CKD
Interface, 330 ... fixed length interface, 34
0: CKD interface conversion means, 350: fixed length interface conversion means, 400: network, 710
... volume label, 720 ... VTOC.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Shigeo Honma 2880 Kozu, Odawara-shi, Kanagawa Prefecture Storage Systems Division, Hitachi, Ltd. Inside the Manufacturing Systems Development Laboratory

Claims (15)

[Claims] A storage device having a first interface and a second interface different from each other, a first computer connected to the storage device by the first interface, and a storage device connected to the storage device by the second interface. A backup acquisition method in a computer system including a second computer, wherein the first computer stores data stored in the storage device by the first interface, and the second computer stores the data in the second interface. A backup of data used by the first computer by detecting the data from the storage device, reading the data, and storing the data. 2. The backup acquisition method according to claim 1, wherein said first interface is an interface according to a count key data format, and said second interface is an interface according to a fixed length block format. 3. The second computer detects and reads, from the storage device, management information created in the storage device by the first computer with respect to the data stored in the storage device by the first computer. The backup acquisition method according to claim 1, wherein the backup acquisition method is performed. 4. The second computer detects, from the storage device, management information created in the storage device by the first computer with respect to the data stored in the storage device by the first computer. 4. The backup acquisition method according to claim 1, wherein the backup acquisition method is used for controlling reading and the backup acquisition processing. 5. The second computer detects, from the storage device, management information created in the storage device by the first computer for the data stored in the storage device by the first computer. 5. The backup acquisition method according to claim 4, wherein whether or not backup of the data can be acquired is determined based on the read out date information on the data recorded in the management information. 6. A storage device having a first interface and a second interface different from each other, a first computer connected to the storage device by the first interface, and connected to the storage device by the second interface. At least two of the second calculators
A computer system comprising two computers, wherein the second computer stores data stored in the storage device by the first computer in a storage format according to the first interface, by the second interface. Means for detecting and reading, means for converting the storage format of the data to a storage format according to the first interface for performing reading by the second interface, and storing the read data, Means for obtaining a backup of data used by the first computer. 7. The computer system according to claim 6, wherein said first interface is an interface according to a count key data format, and said second interface is an interface according to a fixed length block format. 8. The second computer detects, from the storage device, management information created in the storage device by the first computer with respect to the data stored in the storage device by the first computer. 8. The computer system according to claim 6, further comprising: means for reading and reading; and means for storing the read management information. 9. The second computer detects, from the storage device, management information created in the storage device by the first computer with respect to the data stored in the storage device by the first computer. 7. The apparatus according to claim 6, further comprising: means for reading and storing the data; and means for determining whether the data can be read and stored based on the read management information.
9. The computer system according to any one of claims 1 to 8. 10. The computer system according to claim 6, wherein said storage device is a disk subsystem. 11. A storage device having a first interface and a second interface different from each other, a first computer connected to the storage device by the first interface, and connected to the storage device by the second interface. A second computer and a backup acquisition method in a computer system having a backup device connected to the second computer, wherein when the first computer receives a backup request from the second computer, Computer notifies the second computer of the volume ID storing the data to be backed up, and the physical address on the volume identified by the volume ID, and the second computer Access by the second access interface Calculating a scan possible addresses, reads data from the volume based on the calculated address, backup acquisition method characterized by storing the read data to the backup device. 12. The backup acquisition method according to claim 11, wherein said first interface is an interface according to a count key data format, and said second interface is an interface according to a fixed length block format. 13. The backup acquisition method according to claim 12, wherein data is read from said backup device by said second computer, and a count section in the read data is changed and then written to said storage device. How to get a backup. 14. A storage device having a first interface and a second interface different from each other, a first computer connected to the storage device by the first interface, and a storage device and the second interface. In a computer system having a connected switch device, a second computer connected to the switch device, and a backup device connected to the switch device, the first computer receives a backup request from the second computer Then, the first computer notifies the second computer of storage location information including the volume ID of the volume storing the data to be backed up and the physical address on the volume, and the second computer Receiving location information, and based on the storage location information, A command for instructing the device to copy the data to be backed up from the volume identified by the volume ID to the backup device is generated and issued to the switch device. Therefore, a backup acquisition method characterized by copying data from the volume to the backup device. 15. The backup acquisition method according to claim 14, wherein the second computer checks whether or not the storage device at the restoration destination is the same as the storage device at the time of backup acquisition, and confirms that it is the same. Generating a command for copying data from the backup device to the storage device and issuing the command to the switch device, wherein the switch device restores data from the backup device to the storage device according to the command. And how to get backup.