JPH08166854A - Managing method for saved volume - Google Patents

Abstract

PURPOSE: To make the managing operation of a system which has MVDSs efficient and simple by saving data, recorded on a volume to be saved, on a magnetic tape as a volume saved data set and performing a volume saving processing. CONSTITUTION: The data on the magnetic disk volume to be saved are copied to the magnetic tape to generate the volume saved data set. Then the volume saving information is outputted to a volume saving registry 5 through the magnetic disk volume saving information output processing 23. Then a multivolume data set information input processing 24 inputs assignation destination volume information on all MVDSs having extents on the magnetic disk volume to be saved from a multivolume data set registry 6. On the basis of this input information, all the MVDSs to be saved are copied to the magnetic tape to generate an MVDs saved data set, whose MVDS saving information is outputted to the volume saving registry 5.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a save volume management method, and more particularly to a multi-volume data set (MVD
The present invention relates to a management method of a save volume suitable for a system having S).

[0002]

2. Description of the Related Art Conventionally, in a computer system using a magnetic disk device, a failure may occur by evacuating (backing up) the data on the magnetic disk to a magnetic tape as needed or periodically as part of system operation. At times, the data on the magnetic disk is prevented from being lost. That is, when the data on the magnetic disk is lost due to the occurrence of a failure, the lost data can be recovered by copying the corresponding data from the saved magnetic tape onto the magnetic disk.

As a specific method of saving (recovering) data, a physical magnetic disk (volume) is used as a management unit, and data is saved (recovered) for each volume.
There is a method of doing so and a method of saving (recovering) data for each data set using a logical data set as a management unit. In general, since the save (recovery) processing time and the amount of saved (recovery) data are almost constant, a method that facilitates operation management is often adopted. Further, since the method (1) does not involve data retrieval, there is an advantage that the save (recovery) processing time is shorter than the method (1).

[0004]

However, in the above-mentioned conventional technique, when there is a multi-volume data set (MVDS) in which extents, which are constituent elements, are recorded over a plurality of volumes, data saving is performed separately from the data saving. There is a problem that the management of operations is complicated because it is necessary to manage the locations of all the extents that compose the MVDS. When recovering data, the MV
Since it is difficult to quickly search for all the extents that make up the DS, there is a problem in that it takes a lot of time to recover from a volume failure, which may delay the return to normal operation. For this reason, operation management has often been performed in which the failure recovery time of a volume is shortened by assigning no MVDS on the magnetic disk as much as possible.

Therefore, an object of the present invention is to solve the above-mentioned problems and combine the save and restore processing of the data recorded on the magnetic disk and the processing for the MVDS to manage the operation of the system having the MVDS. It is an object of the present invention to provide a save volume management method capable of improving the efficiency and simplification of the above.

[0006]

In order to achieve the above object, the save volume management method of the present invention is an operation method of a system for saving and recovering data on a magnetic disk in volume units, An extent that updates the allocation destination volume information of the MVDS registered in the multi-volume data set register as the extents that make up the multi-volume data set (MVDS) recorded across multiple volumes are incremented and released. When performing a backup operation during the update process, the data recorded in the specified save target volume is saved to a magnetic tape as a volume save data set, and the volume save information is output to the volume save register. Set register Volume saving processing that saves the MVDS whose extent exists on the save target volume to the magnetic tape as an MVDS save data set based on the allocation destination volume information obtained from the same and outputs the MVDS save information to the volume save register To
Upon failure recovery work, based on the volume save information and MVDS save information obtained from the volume save directory, after copying the volume save data set from the magnetic tape to the save target volume, the Volume recovery processing for copying the MVDS save data set onto the save target volume is executed.

[0007]

The operation based on the above configuration will be described.

According to the save volume management method of the present invention,
In the operation method of the system that saves and recovers the data on the magnetic disk in units of volume, during normal operation, it is necessary to increase and release the extents that make up the multi-volume data set (MVDS) recorded across multiple volumes. By executing the extent renewal process that updates the allocation destination volume information of the MVDS registered in the multi-volume data set register, the system does not search the target MVDS from the first extent, but the multi-volume data set. The allocation destination volume of the MVDS can be easily grasped by referring to the registration list.

In the backup operation, the data recorded in the designated save target volume is saved to the magnetic tape as a volume save data set, and the volume save information is output to the volume save register, and then the multi-volume An MV that has an extent on the evacuation target volume based on the allocation destination volume information obtained from the dataset registry
By saving the DS as the MVDS save data set to the magnetic tape and executing the volume save process that outputs the MVDS save information to the volume save directory, the save of the MVDS is automatically performed in addition to the save of the data in volume units. The backup procedure is MV
It is unified regardless of the presence or absence of DS, and operational management can be simplified compared to the past.

Further, at the time of failure recovery work, after copying the volume save data set from the magnetic tape to the save target volume based on the volume save information and the MVDS save information obtained from the volume save register, By executing the volume recovery process of copying the MVDS save data set from the magnetic tape onto the save target volume, the time required for failure recovery of the volume is
Since it only takes time to copy the MVDS save data set,
Even if an MVDS exists, there is no delay in returning to normal operation, and the failure recovery time can be shortened.
The procedure of the disaster recovery work is unified regardless of the presence / absence of MVDS, and the operation management can be simplified more than ever before.

As described above, the operation management of a system having an MVDS can be made more efficient and simpler than before by combining the save and restore processing of the data recorded on the magnetic disk and the processing of the MVDS. You can

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the save volume management method of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing an example of the configuration of a system to which the save volume management method of the present invention is applied. In the figure, 1 is a central processing unit (CPU) of an electronic computing system, 3 is a magnetic disk device group in which data is recorded, 4 is data on the magnetic disk device group 3 in volume units and multi-volume data sets (hereinafter, "MV
A group of magnetic tape devices that are saved in units of "DS",
Reference numeral 5 denotes a volume evacuation register (corresponding to a "volume evacuation register" in the claims) for performing registration management regarding data saved in the magnetic tape device group 4, and 6 is created on the magnetic disk device group 3. 3 is a multi-volume data set registry (corresponding to a "multi-volume data set registry" in the claims) for registering and managing the volume to which the extents constituting the MVDS are allocated.

FIG. 2 is a diagram showing the functional configuration of an embodiment of the save volume management method of the present invention. In the figure,
The volume evacuation registration list 5 includes evacuation information regarding the data evicted from the magnetic disk device group 3 in volume units (corresponding to "volume evacuation information" in the claims), as well as evacuation information regarding data evicted in MVDS units. (Corresponding to "MVDS save information" in the claims) is registered. Further, in the multi-volume data set register 6, for all MVDS on the magnetic disk device group 3 in the system, the allocation destination volume information of extents forming the MVDS is registered.

MVDS created on the magnetic disk unit group 3
Extent extension processing 2 when the extent of
By 1, the allocation volume information for specifying the newly secured extent is additionally registered in the multi-volume data set register 6. Further, when the extent is released, the extent release processing 22 deletes the allocation destination volume information that identifies the extent registered in the multi-volume data set registration list 6. The extent increment process 21 and the extent release process 22 correspond to the "extent update process" in the claims.

When saving a magnetic disk volume, first, the data on the magnetic disk volume to be saved is copied onto a magnetic tape to create a volume save data set, and the volume save information is stored in the magnetic disk volume. It is output to the volume save registration list 5 by the save information output processing 23. Next, the multi-volume data set information input processing 24 inputs the allocation-destination volume information of all MVDSs having extents on the magnetic disk volumes to be saved from the multi-volume data set register 6 and based on the allocation-destination volume information. Copy all MVDS on the target magnetic disk to the magnetic tape to create an MVDS save data set, and output the MVDS save information to the multi-volume data set save information output process 2
5 to the volume saving registration list 5. Volume save information and MVDS save information are stored in the same record. This series of processes corresponds to the "volume saving process" in the claims.

When recovering the magnetic disk volume, first, the magnetic disk volume save information input processing 26 inputs the volume save information and the MVDS save information from the volume save register 5. Next, after copying the volume evacuation data set from the magnetic tape to the magnetic disk based on the obtained volume evacuation information, the MVDS evacuation data set is further copied from the magnetic tape to the magnetic disk based on the MVDS information. . This series of processes corresponds to the "volume recovery process" in the claims.

FIG. 3 is a diagram showing an example of the format of the allocation destination volume information held in the multi-volume data set registry in FIG. In the figure, 31 indicates one of the records registered in the multi-volume data set registry. Then, in record 31, 32
Is a data set name that identifies the MVDS, 33 is a VSAM / non-VSAM distinction and data set organization (information on the VTOC) as attributes of the MVDS, and 34 is a list of all extents that make up the MVDS. A group of allocation destination volume serial numbers is held respectively.

FIG. 4 is a diagram showing an example of the format of the save information held in the volume save register in FIG. In the figure, 41 indicates one of the records registered in the volume evacuation register. In the record 41, 42 is a volume serial number that identifies the magnetic disk volume of the save source, 43 is the device type as the attribute information of the magnetic disk volume of the save source, and 44 is the magnetic disk volume of the save source. The evacuation generation information of is held respectively. The save generation information is created each time the magnetic disk volume of the save source is saved, and 45 is the generation number that identifies the save generation, and 46 is the magnetic disk volume save information (“volume save information” in the claims). Is the volume serial number of the magnetic tape device group of the save destination and the label number storing the volume save data set, and MVDS save information (corresponds to "MVDS save information" in the claims) in 47. ,
Retained respectively. The MVDS save information is created by the number of MVDS having extents on the save source magnetic disk volume, 48 is a data set name that identifies the MVDS, and 49 is the MVDS in the magnetic disk device group as the MVDS information. The volume serial numbers and device types of all the magnetic disk devices to which the constituent extents are allocated are stored in 50 as the MVDS save destination identification information, which is the volume serial numbers of the save destination magnetic tape device groups and the MVDS save data set. Label number is
Retained respectively.

FIG. 5 is a flow chart showing in detail the flow of extent increment processing in FIG. In the figure, FIG.
The same components as those in FIG. 4 are designated by the same reference numerals and the description thereof will be omitted.

In FIG. 5, when the incremental extent of the dataset is secured in a volume different from the volume currently being processed (step 501 = YES), the record 31 of the MVDS is input from the multi-volume dataset register 6 ( If the record of the MVDS exists (step 502) (step 503 = YES), the record is updated by adding the volume serial number 34 that identifies the newly allocated volume of the incremental extent to the record (step 504). If the MVDS record does not exist (step 503 = NO), the MVDS record is created (step 505), and
An MVDS name 32, a data set attribute 33, a volume serial number 34 that identifies an allocated volume and a newly allocated volume are newly registered.

FIG. 6 is a flow chart showing in detail the flow of the extent release processing in FIG. In the figure, FIG.
The same components as those in FIG. 4 are designated by the same reference numerals and the description thereof will be omitted.

In FIG. 6, first, the MVDS record 31 is input from the multi-volume data set registry 6 (step 601). And record 3 of the MVDS
If 1 exists (step 602 = YES), the volume serial number 34 that identifies the volume in which the release extent existed is deleted from the record 31 (step 603). As a result, when the number of registered volume serial numbers 34 in the record 31 becomes one (step 604 = YES), it is considered that a single volume data set has been created, and the record 31 is recorded in the multi-volume data set register 6 Remove from.

As described above, the system performs the target MV by the extent increment processing and the extent release processing (corresponding to "extent renewal processing" in claims).
Instead of retrieving the DS from the top extent, it is possible to easily grasp the allocation volume of the MVDS by referring to the multi-volume data set register.

FIG. 7 is a flow chart showing in detail the flow of the volume save processing in the save volume management method of the present invention. In the figure, the processing in steps 701 to 705 is the magnetic disk volume save information output processing 23 in FIG. 2, and the processing in step 706 is the multi-volume data set information input processing 24 in FIG.
The process in step 709 corresponds to the multi-volume data set save information output process 25 in FIG. 2, respectively. Further, the same components as those in FIGS. 1 to 4 are designated by the same reference numerals, and the description thereof will be omitted.

In FIG. 7, first, the data of the magnetic disk volume to be saved is output onto the magnetic tape of the magnetic tape device group 4 (creation of volume saved data set: step 701). Next, the volume evacuation register 5
Then, the record 41 of the volume is input (step 702), and if the record exists (step 703 =).
If YES, the save generation information 44 is added to the record 41 (step 704), and if the record does not exist (step 703 = NO), the record 41 of the volume is newly created (step 705). At this time, the magnetic disk volume serial number 42, the magnetic disk volume information 43, and the save generation information 44 corresponding to the save of the volume currently being processed are recorded in the created record 41. Next, the records 31 of all MVDSs having extents on the magnetic disk volumes to be saved are input from the multi-volume data set register 6 (step 706). For all of these MVDS (step 707), MV is placed on the magnetic tape of the magnetic tape device group 4.
A DS save data set is created (step 708), and the MVDS save information 47 is additionally registered in the volume save register 5 (step 709).

As described above, the volume saving process automatically saves the MVDS in addition to saving the data in volume units, so the backup procedure is MV.
It is unified regardless of the presence or absence of DS, and operational management can be simplified compared to the past.

FIG. 8 is a flow chart showing in detail the flow of volume recovery processing in the save volume management method of the present invention. In the figure, the process of step 801 corresponds to the magnetic disk volume save information input process 26 of FIG. Further, the same components as those in FIGS. 1 to 4 are designated by the same reference numerals, and the description thereof will be omitted.

In FIG. 8, first, the record 41 of the volume is input from the volume evacuation registration list 5 (step 801). At this time, it is in the same record
MVDS save information is also entered. Based on the information in this record, first, as recovery of the magnetic disk volume, the volume save data set is copied from the magnetic tape onto the magnetic disk (step 802). Next, for all MVDSs that are saved when the volume is saved and are indicated by the input MVDS save information (step 803),
The MVDS save data set is copied from the magnetic tape onto the magnetic disk (step 804).

As described above, since the volume recovery processing requires only the time required for the volume failure recovery to copy the volume save data set and the MVDS save data set, it is possible to return to the normal operation even if the MVDS exists. There is no delay and the failure recovery time can be shortened, and the procedure for failure recovery work is unified regardless of the presence / absence of MVDS, and the operation management can be simplified compared to the past.

As described above, the operation management of a system having an MVDS is made more efficient and simpler than in the past by combining the save and restore processing of the data recorded on the magnetic disk and the processing of the MVDS. You can

[0032]

As described in detail above, according to the save volume management method of the present invention, in the system operation method for saving and recovering the data on the magnetic disk in volume units, a plurality of Extent renewal processing that updates the allocation destination volume information of the MVDS registered in the multi-volume data set register as the extents that make up the multi-volume data set (MVDS) recorded over the volume are increased and released. By executing it, the system can refer to the multi-volume data set directory instead of searching for the target MVDS from the first extent and can easily grasp the allocation destination volume of the MVDS. .

In the backup operation, the data recorded in the designated save target volume is saved to the magnetic tape as a volume save data set and the volume save information is output to the volume save register, and then the multi-volume is restored. An MV that has an extent on the evacuation target volume based on the allocation destination volume information obtained from the dataset registry
By saving the DS as the MVDS save data set to the magnetic tape and executing the volume save process that outputs the MVDS save information to the volume save directory, the save of the MVDS is automatically performed in addition to the save of the data in volume units. The backup procedure is MV
It is unified regardless of the presence or absence of DS, and the effect that operation management can be simplified more than before is obtained.

Further, at the time of failure recovery work, after copying the volume save data set from the magnetic tape to the save target volume based on the volume save information and MVDS save information obtained from the volume save register, By executing the volume recovery process of copying the MVDS save data set from the magnetic tape onto the save target volume, the time required for failure recovery of the volume is
Since it only takes time to copy the MVDS save data set,
Even if an MVDS exists, there is no delay in returning to normal operation, and the failure recovery time can be shortened.
The procedure of the disaster recovery work is unified regardless of the presence / absence of MVDS, and the operation management can be simplified more than before.

As described above, the operation management of a system having an MVDS is made more efficient and simpler than before by combining the save and restore processing of the data recorded on the magnetic disk and the processing for the MVDS. The effect of being able to do is obtained.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration example of a system to which a save volume management method of the present invention is applied.

FIG. 2 is a diagram showing a functional configuration of an embodiment of a save volume management method of the present invention.

FIG. 3 is a diagram showing an example of a format of allocation destination volume information held in the multi-volume data set registry in FIG.

FIG. 4 is a diagram showing an example of a format of save information held in a volume save register in FIG.

FIG. 5 is a flowchart showing in detail the flow of extent increment processing in FIG.

6 is a flowchart showing in detail the flow of extent release processing in FIG.

FIG. 7 is a flowchart showing in detail the flow of volume saving processing in the save volume management method of the present invention.

FIG. 8 is a flowchart showing in detail the flow of volume recovery processing in the save volume management method of the present invention.

[Explanation of symbols]

 1 central processing unit (CPU) 2 memory 3 magnetic disk device group 4 magnetic tape device group 5 evacuation volume register 6 multi-volume data set register

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Yoshiaki Shinmura 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Hitachi Ltd. Software Development Division

Claims (1)

[Claims] 1. A method of operating a system for backing up and recovering data on a magnetic disk in units of volume. In normal operation, the extents of extents constituting a multi-volume data set (MVDS) recorded over a plurality of volumes are recorded. Extent update processing that updates the allocation destination volume information of the MVDS registered in the multi-volume data set register with the increment and release is performed. When performing backup work, the data recorded in the specified save target volume After saving to the magnetic tape as the volume save data set and outputting the volume save information to the volume save register, the volume to be saved on the save target volume based on the allocation destination volume information obtained from the multi volume data set register. MVDS the MVDS that stent exists retracts to the magnetic tape as MVDS save data sets
The volume evacuation process that outputs evacuation information to the volume evacuation registration list is performed from the magnetic tape to the evacuation target volume based on the volume evacuation information and MVDS evacuation information obtained from the volume evacuation list during failure recovery work. A method of managing an evacuation volume, characterized in that after the volume evacuation data set is copied to a disk, a volume recovery process of copying the MVDS evacuation data set from the magnetic tape onto the evacuation target volume is executed.