JP2015203908A - Storage management apparatus and storage management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently execute restoration processing to a capacity virtual disk.SOLUTION: A storage management apparatus includes: a restoration processing section 14 which reads backup data recorded in a recording medium by data string of a predetermined size, to be stored in a restoration destination volume; a confirmation section 16 which confirms whether all the data string read by the restoration processing section 14 from the recording medium is zero data indicating zero; and a release processing section 17 which issues a physical area release instruction, to a storage apparatus 4, on a write area of zero-data string in the restoration destination volume, when the data string read from the recording medium is zero data.

Description

  The present invention relates to a storage management device and a storage management program.

In recent years, storage devices using capacity virtualization (Thin Provisioning) technology have been adopted to reduce introduction costs and operation costs.
The capacity virtualization technique is a technique for virtualizing a volume capacity that can be seen from a host device such as a server, and is a technique that allows a host to show a capacity that is greater than the physical volume capacity in a storage system.

In capacity virtualization technology, while providing a volume with virtual capacity to the host, the storage side efficiently uses the volume capacity by allocating a physical area only to the data that was actually written. .
A virtual storage area provided by the capacity virtualization technology may be referred to as a capacity virtual disk.

6 is a diagram schematically showing a data image of a capacity virtual disk, and FIG. 7 is a diagram showing a state in which the capacity virtual disk shown in FIG. 6 is backed up to a tape medium.
In the capacity virtualization technology, a physical storage area is allocated to the area of the virtual volume only when data is actually stored. Therefore, in a capacity virtual disk, as shown in FIG. 6, a virtual allocation part (physical unallocation) to which a physical storage area (hereinafter referred to as a physical area) is not allocated and a physical allocation part to which a physical area is allocated And exist. In FIG. 6, “real” is shown in the physical allocation part and “temporary” is shown in the virtual allocation part.

  Now, in tape backup that copies volume data to a tape medium, the virtual allocation portion of the capacity virtual disk is read as zero data when the capacity virtual disk as described above is stored in the tape medium. Therefore, when the data of the capacity virtual disk is backed up to the tape medium, as shown in FIG. 7, 0 is stored as data in the virtual allocation portion (0 data) on the tape medium.

FIGS. 8A and 8B are diagrams showing the data size at the time of backup processing from a capacity virtual disk to a tape medium in a conventional capacity virtualization system, and FIG. 8A schematically shows the state of the capacity virtual disk. FIG. 8B is a diagram schematically showing a state after backup to the tape medium.
As shown in FIG. 8A, in the capacity virtual disk, a part of the physical allocation is occupied by the physical allocation part, and the other virtual allocation part is not actually written. Therefore, the disk capacity actually required in the capacity virtual disk is a physical allocation part.

  On the other hand, in a state where such a capacity virtual disk is backed up to a tape medium, as shown in FIG. 8B, 0 is stored in the tape medium as data corresponding to the virtual allocation portion. Since 0 is stored as data corresponding to such a virtual allocation portion, an actual physical area is required in this area. Therefore, the data size to be backed up on the tape medium is a value obtained by adding the data size of the virtual allocation part to the data size of the physical allocation part, and the data size of the physical allocation part to which the data is actually allocated in the capacity virtual disk. Compared to increase.

FIG. 9 is a diagram schematically showing the data size at the time of restoration processing from a tape medium to a capacity virtual disk in a conventional capacity virtualization system, and shows a disk after restoration processing.
In the restore process for restoring backup data to a capacity virtual disk from a tape medium on which data of a capacity virtual disk has been backed up, as shown in FIG. 9, all data (data image) stored on the tape medium is restored. The

Japanese Patent No. 4927408 JP 2006-31446 A JP 2010-152781 A

In the conventional capacity virtualization system as described above, zero data stored in the tape medium is written back to the capacity virtual disk of the restore destination, and a physical area is allocated. As a result, the capacity virtual disk requires a physical capacity equivalent to the virtual capacity including the data size of the physical allocation part and the data size of the virtual allocation part.
Therefore, in the conventional capacity virtualization system, in order to restore all data stored in the tape medium in the backup process, it is necessary to secure a physical capacity corresponding to the virtual capacity as a restore destination.

The physical capacity for the virtual capacity that needs to be secured as the restore destination (see FIG. 9) is larger than the physical allocation portion (see FIG. 8A) that is secured at least before restoration.
This is contrary to the introduction purpose of the capacity virtual disk, in which the capacity of the volume is efficiently utilized by assigning the capacity only to the data actually written.
Further, as described above, in the capacity virtual disk in which 0 data is stored in the virtual allocation part by the restoration process and the physical area is allocated, the area in which these unnecessary physical areas are allocated is released and the physical unallocated area is released. A zero reclamation function is known.

However, in a conventional capacity virtualization system, performing a release process after allocating a physical area to a capacity virtual disk has a problem of increasing the load on the storage apparatus.
It is also conceivable to perform release processing without allocating a physical area to a capacity virtual disk by executing zero reclamation in parallel with restoration from a tape medium. However, the data writing process to the disk performed by the restoration from the tape medium is not different from a normal I / O (Input / Output) process command, and therefore it is not possible to distinguish whether the area is the tape data written area. As a result, the zero reclamation process may precede the tape data written process, in which case the physical area cannot be released.

  In one aspect, an object of the present invention is to enable efficient restoration processing to a capacity virtual disk.

  For this reason, this storage management device is a storage management device connected to a recording medium processing device that reads and writes data from and to a recording medium and a storage device that provides a volume using a storage device. A restore processing unit that reads recorded backup data in units of a data string of a predetermined size and stores it in a restore destination volume, and whether or not the data sequence read from the recording medium by the restore processing unit is zero data that is all zero When the data sequence read from the recording medium is zero data, a physical area release instruction is issued to the storage device for the write area of the zero data sequence in the restore destination volume. A release processing unit.

  According to one embodiment, restoration processing to a capacity virtual disk can be executed efficiently.

1 is a diagram schematically illustrating a configuration of a virtual storage system as an example of an embodiment. 6 is a flowchart illustrating processing of the operation management server at the time of backup in the virtual storage system as an example of the embodiment. 10 is a flowchart for explaining processing of the operation management server at the time of restoration in the virtual storage system as an example of the embodiment. 10 is a flowchart for explaining processing of the operation management server at the time of restoration in the virtual storage system as an example of the embodiment. 5 is a flowchart for describing physical block release processing in a storage apparatus of a virtual storage system as an example of an embodiment; It is a figure which shows typically the data image of a capacity | capacitance virtual disk. It is a figure which shows the state which backed up the capacity | capacitance virtual disk shown in FIG. 6 to the tape medium. (A), (b) is a figure which shows the data size at the time of the backup process from a capacity | capacitance virtual disk to a tape medium in the conventional capacity | capacitance virtualization system. It is a figure which shows typically the data size at the time of the restoration process from a tape medium to a capacity | capacitance virtual disk in the conventional capacity | capacitance virtualization system.

  Hereinafter, embodiments according to the present storage management apparatus and storage management program will be described with reference to the drawings. However, the embodiment described below is merely an example, and there is no intention to exclude application of various modifications and techniques not explicitly described in the embodiment. That is, the present embodiment can be implemented with various modifications without departing from the spirit of the present embodiment. Each figure is not intended to include only the components shown in the figure, and may include other functions.

FIG. 1 is a diagram schematically illustrating a configuration of a virtual storage system as an example of an embodiment.
The virtual storage system 1 includes a storage device 4 and virtualizes a storage area of a storage device (real storage environment) 21 provided in the storage device 4 to form a virtual storage environment. Then, the storage device 4 provides the virtual volume to a host device (not shown) that is a higher-level device.

The storage device 4 is communicably connected to the host device via a communication network such as Ethernet (registered trademark).
The host device is an information processing device having a server function, for example, and transmits various data such as SCSI (Small Computer System Interface) commands and responses to the storage device 4 via TCP (Transmission Control Protocol) / IP (Internet). Protocol). The host device writes and reads data to and from the virtual volume provided by the storage device 4 by transmitting a disk access command such as read / write to the storage device 4.

The storage device 4 includes one or more (one in the example shown in FIG. 1) CM (Control Module) 20 and one or more (two in the example shown in FIG. 1) storage devices 21.
The storage device 21 is a storage device such as a hard disk drive (HDD) or an SSD (Solid State Drive), and stores various data.
In the storage device 4, the actual volume capacity can be changed at any time by adding the storage device 21. Further, in the storage device 4, a plurality of storage devices 21 may be arranged in an array to configure RAID (Redundant Arrays of Inexpensive Disks).

Each storage device 21 is connected to the CM 20, and writes and reads data according to the control from the CM 20.
The CM 20 is a controller (control device) that controls the operation in the storage device 4 and performs various controls such as access control to the storage device 21 in accordance with an I / O command transmitted from the host device.

The CM 20 is communicably connected to the host device via a network (not shown), receives a command such as read / write transmitted from the host device, and controls the storage device 21.
In addition to the virtual volume provided within the capacity range of the storage device 21 actually provided as the virtual volume provided to the host device, the CM 20 also provides a thin provisioning (capacity virtual) type virtual volume. Provide the functions to provide.

Hereinafter, for convenience, a virtual volume provided within the capacity range of the storage device 21 actually provided is referred to as a normal disk, and a capacity virtual type virtual volume is referred to as a capacity virtual disk. Further, hereinafter, the virtual volume including the normal disk and the capacity virtual disk may be simply referred to as a disk.
Note that the method of providing the normal disk and the capacity virtual disk to the host device by the storage device 4 can be realized by various known methods, and the description thereof is omitted.

  In addition, the storage apparatus 4 (CM 20) is connected to an operation management server 3 to be described later via a communication line 51. Data of a virtual volume (backup source disk, backup source volume) managed in the storage apparatus 4 is transmitted to a tape drive 5 (to be described later) via the operation management server 3, and the tape drive 5 uses a tape medium (backup) (not shown). (Destination) is saved (backed up).

Further, the data of the virtual volume backed up on the tape medium (restore source) is transmitted from the tape drive 5 to the storage device 4 via the operation management server 3, and restored to the virtual volume (restore destination disk) in the storage device 4. The For this restoration, the storage device 21 provided in the storage device 4 is used.
Backup and restoration of data on these disks is performed under the control of the operation management server 3.

In the CM 20, storage management information 201, which is information related to a virtual volume (disk), is managed.
In the storage management information 201, for example, (a1) disk type, (a2) total physical disk capacity, (a3) physically allocated capacity, and (a4) for information specifying a disk (for example, disk number) The release block size is associated.

(a1) The disk type is information indicating whether the disk is a normal disk or a capacity virtual disk.
(a2) The total physical disk capacity is the total capacity of the physical disk capacity corresponding to the virtual volume.
(a3) Physically allocated capacity indicates the size of the physical area of the storage device 21 allocated to the virtual volume when the virtual volume is a capacity virtual disk. That is, the physically allocated capacity is the capacity of the physical area used by the virtual volume (capacity virtual disk).

(a4) The released block size is information indicating the size (block size) that can release the physical area allocated to the virtual volume at one time, and is the size of the physical area (block) that is released at one time. The release block size is determined as a specification of the storage apparatus 4 and is, for example, 21 Mbytes or 32 Mbytes.
Note that (a1) disk type, (a2) total physical disk capacity, (a3) physically allocated capacity, and (a4) released block size in these storage management information 201 are respectively known methods in the storage apparatus 4. Can be acquired.

Further, when the storage apparatus 4 receives an acquisition request for these information from the storage information acquisition unit 12 or the restore information acquisition unit 141 of the operation management server 3 to be described later, the storage device 4 reads the corresponding information from the storage management information 201 and performs operation management. Send (response) to the server 3.
The tape drive 5 is a recording medium processing device that reads / writes data from / to a tape medium (not shown) that is a recording medium, and is connected to the operation management server 3 via a communication line 53.

The tape drive 5 stores the data transmitted from the operation management server 3 in the tape medium and transmits the data read from the tape medium to the operation management server 3 in accordance with the control from the operation management server 3.
The functions as the tape drive 5 and the tape medium can be realized by using various known methods, and detailed description thereof will be omitted.

  The operation terminal 2 is a terminal device on which an operator performs an input operation, and is an information processing device including an input device such as a keyboard and a mouse (not shown), a display, a memory, a CPU (Central Processing Unit), and the like. The operation terminal 2 is connected to the operation management server 3 via the communication line 52, and various instructions input from the operation terminal 2 are transmitted to the operation management server 3, and various information and notifications are received from the operation management server 3. It is transmitted to the operation terminal 2.

For example, the operator performs various input operations such as backup and restoration start instructions using the input device of the operation terminal 2, and these input instructions are transmitted from the operation terminal 2 to the operation management server 3. . Further, the operation management server 3 transmits various processing results and error notifications to the operation terminal 2.
The operation management server 3 is a storage management device that controls management and operation in the virtual storage system 1 and controls, for example, backup and restoration of virtual volumes in the storage device 4.

That is, the operation management server 3 performs control to back up the disk data of the storage device 4 to the tape medium using the tape drive 5 and restore the data backed up to the tape medium to the disk of the storage device 4.
As shown in FIG. 1, the operation management server 3 is configured as an information processing apparatus (computer) including a CPU 10, a memory 18, and a storage device 19.

The storage device 19 is a storage device such as an HDD or an SSD, and stores various data.
The memory 18 is a storage device including a ROM (Read Only Memory) and a RAM (Random Access Memory). In the ROM of the memory 18, a software program related to storage control and data for this program are written. The software program on the memory 18 is appropriately read by the CPU 10 and executed. The RAM of the memory 18 is used as a primary storage memory or a working memory.

Further, backup management information 181 is stored in the storage area of the memory 18. The backup management information 181 is information related to a virtual volume (disk) whose data has been backed up to a tape medium.
In the backup management information 181, for example, (b1) disk type and (b2) physical allocation capacity are associated with information for specifying a disk (for example, disk number).

(b1) The disk type is information indicating whether the disk is a normal disk or a capacity virtual disk.
(b2) The physical allocation capacity indicates the size of the physical area of the storage device 21 allocated to the capacity virtual disk before backup when the disk is a capacity virtual disk. That is, the physical allocation capacity is the capacity of the physical area used by the virtual volume (capacity virtual disk) before backup.

Note that (b1) disk type and (b2) physically allocated capacity in the backup management information 181 can also be obtained from the storage apparatus 4 by a known method.
The CPU 10 is a processing device that performs various controls and operations, and implements various functions by executing O (Operating System) S and programs (storage management programs) stored in the memory 18. That is, the CPU 10 implements functions as a backup processing unit 11 and a restoration processing unit 14 as shown in FIG.

  Note that programs (storage management programs) for realizing the functions as the backup processing unit 11 and the restore processing unit 14 are, for example, a flexible disk, a CD (CD-ROM, CD-R, CD-RW, etc.), DVD, and the like. (DVD-ROM, DVD-RAM, DVD-R, DVD + R, DVD-RW, DVD + RW, HD DVD, etc.), recorded on a computer-readable recording medium such as a Blu-ray disc, magnetic disc, optical disc, magneto-optical disc Provided in form. Then, the computer reads the program from the recording medium, transfers it to the internal storage device or the external storage device, and uses it. The program may be recorded in a storage device (recording medium) such as a magnetic disk, an optical disk, or a magneto-optical disk, and provided from the storage device to the computer via a communication path.

When realizing the functions as the backup processing unit 11 and the restoration processing unit 14, the program stored in the internal storage device (memory 18 in this embodiment) is executed by the microprocessor of the computer (CPU 10 in this embodiment). The At this time, the computer may read and execute the program recorded on the recording medium.
The backup processing unit 11 performs control for backing up virtual volume data to a tape medium. That is, the backup processing unit 11 reads data from the storage device 4 from the virtual volume (backup source disk) to be backed up in a predetermined size (X bytes: for example, X = 256K), and stores the read backup data of the predetermined size on the tape. The data is transmitted to the drive 5 and recorded on a tape medium. The predetermined size of data read from the backup source disk is called a disk read block size.

Further, as shown in FIG. 1, the backup processing unit 11 has functions as a storage information acquisition unit 12 and a storage information recording control unit 13.
The storage information acquisition unit 12 acquires information about the backup source disk, and acquires the disk number, disk type, and physically allocated capacity of the backup source disk.

Specifically, the storage information acquisition unit 12 requests these disk numbers, disk types, and physically allocated capacities from the storage apparatus 4, and receives these responses from the storage apparatus 4. Get information.
The storage information recording control unit 13 records information about the backup source disk in a storage device (for example, the memory 18). The storage information recording control unit 13 stores the disk number, disk type, and physically allocated capacity of the backup source disk acquired by the storage information acquisition unit 12 in the backup management information 181.

Here, the disk type corresponds to disk information indicating whether or not the backup source volume is a capacity virtual disk. The physical allocated capacity corresponds to physical allocated capacity information indicating the physical disk capacity allocated to the backup source volume.
In other words, the storage information recording control unit 13 performs physical allocation indicating the disk information indicating whether or not the backup source disk is a capacity virtual disk and the physical disk capacity allocated to the backup source disk at the time of backup processing. It functions as a recording control unit that stores the capacity information in the memory 18 (backup management information 181).

The restore processing unit 14 performs a restore process for restoring the backup data recorded on the tape medium to the restore destination virtual volume (restore destination disk).
The restore processing unit 14 uses the tape drive 5 to store data in units of a predetermined size (X bytes: for example, X = 256K) from a tape medium (restoration source tape medium, backup destination tape medium) in which backup data to be restored is stored. Is read out. Then, the restore processing unit 14 transmits backup data of a predetermined size read from the tape medium to the storage device 4 and stores it in the restore destination disk. The predetermined size of data read from the restoration source tape medium is referred to as a tape read block size.

This tape reading block size is smaller than the above-described release block size and is a value that is a divisor of the release block size. That is, the release block size is a multiple of the tape read size. The tape reading block size is preferably the same as the disk reading block size described above.
Further, as shown in FIG. 1, the restore processing unit 14 has functions as a restore information acquisition unit 141, a free space confirmation unit 15, a zero data confirmation unit 16, and a release processing unit 17.

The restore information acquisition unit 141 acquires information related to the backup source disk for the backup data to be restored, and acquires the disk number, disk type, and physically allocated capacity of the backup source disk.
Specifically, the restore information acquisition unit 141 acquires the disk number, disk type, and physically allocated capacity from the backup management information 181 by reading them.

  Further, the restore information acquisition unit 141 acquires the disk type, the total physical disk capacity, and the physically allocated capacity for the restore destination disk from the storage apparatus 4. Specifically, the restore information acquisition unit 141 transmits an acquisition request for these information to the storage apparatus 4 and receives each response from the storage apparatus 4 to acquire the information.

The free capacity confirmation unit 15 confirms whether there is enough free capacity to be restored on the restore destination disk.
When the backup source disk is a capacity virtual disk and the restore destination disk is a virtual volume, the free capacity confirmation unit 15 calculates the allocatable capacity of the restore destination.

The free space confirmation unit 15 calculates an allocatable capacity by the following equation (1).
Allocatable capacity = Total physical disk capacity-Physical allocated capacity (1)
Here, “total physical disk capacity” and “physically allocated capacity” are (a2) total physical disk capacity and (a3) physically allocated capacity) managed by the storage management information 201 of the storage apparatus 4. The free capacity confirmation unit 15 requests the storage device 4 for these (a2) total physical disk capacity and (a3) physically allocated capacity, and applies them to the above equation (1), thereby assignable capacity. Is calculated.

Then, the free capacity confirmation unit 15 compares the calculated allocatable capacity with the (b2) physical allocation capacity for the backup source disk to be restored, read from the backup management information 181 by the restore information acquisition unit 141. . As a result, it is confirmed whether or not the restoreable capacity remains in the restore destination disk.
As a result of this comparison, when the calculated allocatable capacity is larger than the (b2) physical allocation capacity of the backup source disk, the data of the backup source disk can be restored to the restore destination disk.

As a result of this comparison, the restore processing unit 14 executes the restore process when the calculated allocatable capacity is larger than the (b2) physical allocation capacity of the backup source disk.
The zero data confirmation unit (confirmation unit) 16 determines whether or not the backup data (data string) of a predetermined size (release block size) read from the tape medium by the restore processing unit 14 has a zero data pattern that is all zero. Check. Hereinafter, a data string having a zero data pattern is referred to as zero data.

For example, the zero data confirmation unit 16 includes all the data constituting the data sequence of each tape read block size for the backup data that the restore processing unit 14 sequentially reads from the backup destination tape medium in units of the tape read block size (X bytes). Check if it is zero.
The release processing unit 17 transmits a physical area release instruction to the storage apparatus 4 to release a physical block (physical area) corresponding to an area where zero data is stored in the restore destination disk.

The physical area release instruction includes position information and block size of the physical area to be released, and the storage apparatus 4 that has received this physical area release instruction performs physical block release processing of the target area.
Note that the physical block release processing of the target area in the storage apparatus 4 can be realized by a well-known technique. For example, the storage apparatus 4 releases the physical block by setting a value indicating “unallocated” to the target physical block in the physical block management information.

Further, the release processing unit 17 determines that the backup data (data string) of the tape read block size read from the tape medium by the restore processing unit 14 is zero data, and the storage device 4 A physical area release instruction is transmitted to
In other words, when the data sequence of the backup data read from the tape medium is zero data, the release processing unit 17 issues a physical area release instruction for the zero data write area to the storage apparatus 4.

  The release processing unit 17 uses the restore processing unit 14 to sequentially read each backup data of the tape reading block size in units of tape reading block size (X bytes) from the backup destination tape medium. When the total tape read block size, which is data, reaches the release block size (X × Nbyte), a physical area release instruction is transmitted to the storage apparatus 4. N is the number of readings in units of tape reading block size (Xbyte) from the backup destination tape medium. That is, N indicates the number of times of reading of the tape reading block size for achieving the released block size. N can also be said to indicate the number of times of writing to the storage apparatus 4 in units of the tape read block size.

In this way, the release processing unit 17 sends a physical area release instruction to the storage apparatus 4 when a plurality of physical block release requests are continuously made and exceeds a fixed size, thereby allowing storage storage A physical area release instruction to the device 4 is performed with the release block size.
Processing of the operation management server 3 at the time of backup in the virtual storage system 1 as an example of the embodiment configured as described above will be described according to the flowchart (steps A1 to A12) shown in FIG.

  When a backup disclosure instruction is transmitted from the operation terminal 2 to the operation management server 3 in accordance with an input instruction from the operator, the storage information acquisition unit 12 of the backup processing unit 11 in the operation management server 3 Request the disk number of the backup source disk. The storage apparatus 4 reads the disk number of the backup source disk from the storage management information 201 in response to the request from the storage information acquisition unit 12 and responds to the operation management server 3. As a result, the storage information acquisition unit 12 acquires the disk number of the backup source disk (step A1).

The backup processing unit 11 determines a reading position (reading start position) on the backup source disk (step A2), and reads data of the disk reading block size (Xbyte) from this reading position (step A3).
The backup processing unit 11 transmits the disk read block size data read from the backup source disk to the tape drive 5 and records it on the tape medium (step A4). In the tape drive 5, data is written to the tape medium in units of disk read block size.

The backup processing unit 11 records the end position where reading from the backup source disk is completed and writing to the tape medium, that is, the read position, as a backup completion history in the memory 18 or the like. If a backup completion history has already been recorded in the memory 18 or the like, the value is updated (step A5).
In step A6, the backup processing unit 11 checks whether data remains on the backup source disk. If data that has not been backed up still remains (see YES route in step A6), the backup processing unit 11 proceeds to step A2. Return. When the process of step A2 is performed after the second time, a position subsequent to the read position updated (recorded) in step A5 is set as a new read start position.

If there is no data that has not been backed up on the backup source disk (see NO route in step A6), the storage information recording control unit 13 records the disk number of the backup source disk in the backup management information 181. (Step A7).
Further, the storage information acquisition unit 12 requests the storage device 4 for the disk type of the backup source disk. In response to the request from the storage information acquisition unit 12, the operation management server 3 reads the disk type of the backup source disk from the storage management information 201 and responds to the operation management server 3. As a result, the storage information acquisition unit 12 acquires the disk type of the backup source disk (step A8).

The storage information recording control unit 13 records the acquired disk type of the backup source disk in the backup management information 181 in association with the disk number of the backup source disk (step A9).
In addition, the storage information acquisition unit 12 requests the storage apparatus 4 for the physically allocated capacity of the backup source disk. In response to the request from the storage information acquisition unit 12, the operation management server 3 reads the physically allocated capacity of the backup source disk from the storage management information 201 and responds to the operation management server 3. Thereby, the storage information acquisition unit 12 acquires the physically allocated capacity of the backup source disk (step A10).

The storage information recording control unit 13 records the acquired physical allocation capacity of the backup source disk in the backup management information 181 in association with the disk number of the backup source disk (step A11).
Note that the order of the processes of steps A8 to A11 described above is not limited to this, and can be implemented with appropriate changes. For example, the acquisition and recording of the disk type of the backup source disk may be performed before or simultaneously with the acquisition and recording of the physically allocated capacity of the backup source disk.

Thereafter, the backup processing unit 11 returns a backup processing result to the operation terminal 2 (step A12), and ends the process.
Next, processing of the operation management server 3 at the time of restoration in the virtual storage system 1 as an example of the embodiment will be described with reference to flowcharts (steps B1 to B22) illustrated in FIGS. 3 shows steps B1 to B12, and FIG. 4 shows steps B13 to B22.

  When a restore disclosure instruction is transmitted from the operation terminal 2 to the operation management server 3 in accordance with an input instruction from the operator, in the operation management server 3, the restore information acquisition unit 141 of the restore processing unit 14 is transferred from the backup management information 181 to the backup source. It is obtained by reading the disk number of the disk (step B1 in FIG. 3). Thereby, the backup source disk can be specified.

Further, the restore information acquisition unit 141 acquires the backup source disk by reading the disk type of the backup source disk from the backup management information 181 (step B2 in FIG. 3).
The restore processing unit 14 confirms whether the backup data to be restored is data of a capacity virtual disk (step B3 in FIG. 3). That is, the restore processing unit 14 checks whether or not the restore destination disk type acquired in step B2 is a capacity virtual disk.

As a result of the confirmation, if the backup data is not data of the capacity virtual disk (see NO route in step B3), the process proceeds to step B13 in FIG. If the data is not the capacity virtual disk data, the capacity confirmation process performed in the following steps B4 to B12 is unnecessary and is not performed.
As a result of the confirmation, if the backup data is data of a capacity virtual disk (see YES route in step B3), the restore information acquisition unit 141 acquires the physical allocation capacity of the backup source disk (step in FIG. 3). B4). The physical allocation capacity of this backup source disk corresponds to the planned physical allocation capacity when restoring backup data.

  The restore processing unit 14 acquires the disk type of the restore destination disk (step B5 in FIG. 3). Specifically, the restore processing unit 14 requests the storage device 4 for the disk type of the restore destination disk. In response to the request from the restore information acquisition unit 141, the storage apparatus 4 reads the backup source disk, that is, the disk number of the restore destination disk from the storage management information 201, and responds to the operation management server 3. Thereby, the restore information acquisition unit 141 acquires the disk type of the restore destination disk. This is because the restoration process does not necessarily restore to the same backup source disk.

The restore processing unit 14 checks whether or not the restore destination disk is a capacity virtual disk based on the obtained disk type of the restore destination disk (step B6 in FIG. 3).
As a result of the confirmation, if the restore destination disk is not a capacity virtual disk (see NO route in step B6), the process proceeds to step B13 in FIG.
As a result of the confirmation, if the restore destination disk is a capacity virtual disk (see YES route in step B6), the restore information acquisition unit 141 acquires the total physical disk capacity of the restore destination disk from the storage apparatus 4 (FIG. 3 step B7).

Further, the restore information acquisition unit 141 acquires the physically allocated capacity of the restore destination disk from the storage device 4 (step B8 in FIG. 3).
The acquired physical allocation capacity and total physical disk capacity of the restore destination disk are recorded in a storage device such as the memory 18.
Note that the order of the processing of these steps B7 and B8 is not limited to this, and can be changed as appropriate. For example, the physically allocated capacity of the restore destination disk may be acquired before or simultaneously with the total physical disk capacity of the restore destination disk.

Next, the free space confirmation unit 15 calculates the allocatable capacity of the restore destination using the above formula (1) (step B9 in FIG. 3).
The free space confirmation unit 15 compares the calculated allocatable capacity with the (b2) physical allocation capacity for the backup source disk to be restored, read from the backup management information 181 by the restore information acquisition unit 141. As a result, it is confirmed whether or not the restoreable capacity remains in the restore destination disk. That is, it is confirmed whether or not there is enough free capacity to be restored on the restore destination disk (step B10 in FIG. 3).

  If the calculated allocatable capacity is equal to or less than (b2) the physical allocation capacity of the backup source disk, that is, if there is not enough free capacity to be restored on the restore destination disk (see NO route in step B10), step B11 Migrate to That is, the free space confirmation unit 15 responds to the operation terminal 2 with an error notification indicating that restoration is impossible (step B11 in FIG. 3), and ends the process.

  On the other hand, when the calculated allocatable capacity is larger than (b2) the physical allocation capacity of the backup source disk (see YES route in step B10), the restore information acquisition unit 141 acquires the release block size of the restore destination (see FIG. Step B12 in FIG. Specifically, the restore information acquisition unit 141 requests the free block size from the storage apparatus 4. The storage apparatus 4 reads the released block size from the storage management information 201 in response to the request from the restore information acquisition unit 141 and responds to the operation management server 3. Thereby, the restore information acquisition unit 141 acquires the release block size. Thereafter, the process proceeds to step B13 in FIG.

In step B13 of FIG. 4, the restore processing unit 14 determines the start position (write start position) of data to be written to the restore destination disk in the restore source tape medium.
The restore processing unit 14 causes the tape drive 5 to read data of the tape read block size (X bytes: for example, X = 256K) from the write start position in the restore source tape medium (step B14 in FIG. 4). Data read from the tape medium is transmitted from the tape drive 5 to the operation management server 3 via the communication line 51 and stored in the memory 18 of the operation management server 3 or a cache memory (not shown).

The zero data confirmation unit 16 confirms whether all data included in the tape read block size read from the backup destination tape medium by the restore processing unit 14 is zero data (step B15 in FIG. 4).
If all the data included in the tape reading block size read from the tape medium is zero data (see YES route in step B15), then the zero data confirmation unit 16 reads the tape that is the read zero data. It is confirmed whether the total block size has reached the released block size (step B16 in FIG. 4). That is, the zero data confirmation unit 16 confirms whether or not the condition “X × N ≧ open block size” is satisfied.

Note that N is the number of times of reading from the tape medium, and the value of X × N represents the total tape read block size that is zero data that has been read.
If the total tape read block size that is the read zero data does not reach the released block size (see NO route in step B16), the process returns to step B14.

Further, when the total of the tape read block size which is the read zero data reaches the release block size (see YES route of step B16), the process proceeds to step B17. That is, the zero data confirmation unit 16 confirms whether or not zero data corresponding to the released block size is continuous in the backup data sequentially read from the tape medium.
In step B17 of FIG. 4, the release processing unit 17 transmits a physical area release instruction to the storage apparatus 4 to thereby release a physical block having a release block size (X × Nbyte) corresponding to the restore destination virtual volume. Let go. That is, the release processing unit 17 causes the storage apparatus 4 to place the zero data area having the release block size starting from the write start position determined in step B13 into a physically unallocated state.

The physical block release processing in the storage apparatus 4 that has received the physical area release instruction will be described later with reference to FIG.
The release processing unit 17 records the end position on the tape medium where writing to the restoration destination disk is completed, that is, the written position, as a restoration completion history in the memory 18 or the like. If a restoration completion history has already been recorded in the memory 18 or the like, the value is updated (step B18 in FIG. 4).

As described above, during the restore process, if the backup data read from the tape medium is zero data, a physical area release instruction is transmitted to the storage apparatus 4 without writing to the restore destination disk. Thus, the zero data area is set to a state not physically allocated.
In step B19 in FIG. 4, the restore processing unit 14 confirms whether unrestored backup data remains on the tape medium. If unrestored backup data still remains (see YES route in step B19). Return to Step B13. When the process of step B13 is performed after the second time, a position subsequent to the written position updated (recorded) in step B18 is set as a new writing start position.

When unrestored backup data does not remain on the tape medium (see NO route in step B19), the restore processing unit 14 notifies the operation terminal 2 of the completion of the restore process (step B20 in FIG. 4). ), The process is terminated.
If at least a part of the data included in the tape read block size read from the tape medium is not 0 in step B15, that is, if it is not zero data (see NO route in step B15), the step of FIG. The process proceeds to B21. In this step B21, the restore processing unit 14 transmits the backup data of the tape read block size (Xbyte) read from the tape medium to the storage device 4 and records it in the write area of the restore destination disk. That is, the restore processing unit 14 reads the backup data from the tape medium in units of tape read block size (Xbyte) and records it in the write area of the restore destination disk.

The restore processing unit 14 confirms whether the number of times of writing in the unit of tape read block size to the storage device 4 performed in step B21 has reached the number of times N of read of the tape read block size for achieving the released block size described above. (Step B22 in FIG. 4).
If the number of writes to the storage device 4 in units of the tape read block size has not reached the number of reads N of the tape read block size for achieving the above-mentioned release block size (see NO route in step B22), step Repeat B21.

Then, when the number of times of writing to the storage device 4 in units of tape read block size has reached the number of times N of read of the tape read block size for achieving the above-mentioned release block size (see YES route of step B22), step The process proceeds to B18.
Next, physical block release processing in the storage apparatus 4 of the virtual storage system 1 as an example of the embodiment will be described with reference to the flowchart shown in FIG. 5 (steps C1 to C3).

In the storage apparatus 4, when a physical area release instruction is received from the release processing unit 17 of the operation management server 3 (step C1), the area specified by the physical area release instruction (release target area) has been physically allocated. (Step C2).
As a result of the confirmation, if the area to be released is not physically allocated (see NO route in step C2), the process is terminated. When the area to be released has been physically allocated (see YES route in step C2), the allocated physical allocation portion in the area to be released is released (step C3), and the process is terminated.

  As described above, according to the virtual storage system 1 as an example of the embodiment, when the data sequence of the backup data read from the tape medium is zero data during the restore process, the zero data to the restore destination disk is stored. By sending a physical area release instruction to the storage apparatus 4 without writing, the zero data area is brought into a physical unallocated state.

As a result, unnecessary zero data can be prevented from being stored in the restore destination disk, and the storage device 21 can be used efficiently. In addition, it is not necessary to allocate an unnecessary physical area to the capacity virtual disk, and capacity estimation becomes easy.
Further, since there is no need to execute zero reclamation, it is possible to efficiently execute the restore process without imposing unnecessary load on the storage apparatus 4.

Furthermore, before executing the restore process, the free capacity confirmation unit 15 confirms whether there is enough free capacity to be restored, thereby preventing a failure of the restore process due to a lack of capacity.
The disclosed technology is not limited to the above-described embodiment, and various modifications can be made without departing from the spirit of the present embodiment.

  For example, in the above-described embodiment, a tape medium is used as a backup destination. However, the present invention is not limited to this, and various recording media other than the tape medium may be used. Further, a disk device such as an HDD may be used as a backup destination recording medium. In this case, it can be used as means for transferring data from the disk device to the capacity virtual disk, and is highly convenient.

Further, according to the above-described disclosure, this embodiment can be implemented and manufactured by those skilled in the art.
Regarding the above embodiment, the following additional notes are disclosed.
(Appendix 1)
A storage management device connected to a recording medium processing device that reads and writes data from and to a recording medium, and a storage device that provides a volume using a storage device,
A restore processing unit that reads backup data recorded in the recording medium in units of a data string of a predetermined size and stores it in a restore destination volume;
A confirmation unit for confirming whether the data string read from the recording medium by the restore processing unit is zero data that is all zero;
A release processing unit that issues a physical area release instruction to the storage device for a write area of the zero data string in the restore destination volume when the data string read from the recording medium is zero data; A storage management device.

(Appendix 2)
When the backup source volume is a capacity virtual disk,
Calculate the restore destination physical disk free capacity, compare the calculated restore destination physical disk free capacity with the backup source physical allocated capacity indicating the physical disk capacity allocated to the backup source volume, and A determination unit for determining whether the backup data of the recording medium can be restored to the restore destination volume;
The storage management apparatus according to appendix 1, wherein the restore processing unit stores backup data of the recording medium in the restore destination volume when it is determined that restoration is possible.

(Appendix 3)
During backup processing for storing the data of the backup source volume in the recording medium,
Disk information indicating whether or not the backup source volume is the capacity virtual disk and physical allocated capacity information indicating the physical disk capacity allocated to the backup source volume are stored in the storage device. The storage management device according to appendix 1 or 2, further comprising a recording control unit.

(Appendix 4)
To a computer connected to a recording medium processing apparatus that reads and writes data from and to a recording medium, and a storage apparatus that provides a volume using a storage device,
Processing for reading backup data recorded in the recording medium in units of a data string of a predetermined size and storing it in a restore destination volume;
A process of confirming whether the data string read from the recording medium is zero data that is all zero;
When the data string read from the recording medium is zero data, the storage apparatus is caused to execute a process of issuing a physical area release instruction for the write area of the zero data string in the restore destination volume. A storage management program.

(Appendix 5)
When the backup source volume is a capacity virtual disk,
Calculate the restore destination physical disk free capacity, compare the calculated restore destination physical disk free capacity with the backup source physical allocated capacity indicating the physical disk capacity allocated to the backup source volume, and A process for determining whether the backup data of the recording medium can be restored to the restore destination volume;
The storage management program according to appendix 4, wherein the computer executes a process of storing backup data of the recording medium in the restore destination volume when it is determined that restoration is possible.

(Appendix 6)
During backup processing for storing the data of the backup source volume in the recording medium,
Disk information indicating whether or not the backup source volume is the capacity virtual disk and physical allocated capacity information indicating the physical disk capacity allocated to the backup source volume are stored in the storage device. 6. The storage management program according to appendix 4 or 5, which causes the computer to execute processing.

(Appendix 7)
To a computer connected to a recording medium processing apparatus that reads and writes data from and to a recording medium, and a storage apparatus that provides a volume using a storage device,
Processing for reading backup data recorded in the recording medium in units of a data string of a predetermined size and storing it in a restore destination volume;
A process of confirming whether the data string read from the recording medium is zero data that is all zero;
When the data string read from the recording medium is zero data, the storage apparatus is caused to execute a process of issuing a physical area release instruction for the write area of the zero data string in the restore destination volume. A computer-readable recording medium on which a storage management program is recorded.

(Appendix 8)
When the backup source volume is a capacity virtual disk,
Calculate the restore destination physical disk free capacity, compare the calculated restore destination physical disk free capacity with the backup source physical allocated capacity indicating the physical disk capacity allocated to the backup source volume, and A process for determining whether the backup data of the recording medium can be restored to the restore destination volume;
The computer recorded with the storage management program according to appendix 7, wherein the computer is caused to execute a process of storing backup data of the recording medium in the restore destination volume when it is determined that restoration is possible A readable recording medium.

(Appendix 9)
During backup processing for storing the data of the backup source volume in the recording medium,
Disk information indicating whether or not the backup source volume is the capacity virtual disk and physical allocated capacity information indicating the physical disk capacity allocated to the backup source volume are stored in the storage device. 9. A computer-readable recording medium on which the storage management program according to appendix 7 or 8 is recorded, wherein the computer executes processing.

1 Virtual Storage System 2 Operation Terminal 3 Operation Management Server (Storage Management Device)
4 Storage device 5 Tape drive (recording medium processing device)
10 CPU
DESCRIPTION OF SYMBOLS 11 Backup processing part 12 Storage information acquisition part 13 Storage information recording control part (recording control part)
14 Restore processing section 15 Free space confirmation section (determination section)
16 Zero data confirmation part (confirmation part)
17 Release processing unit 18 Memory 19, 21 Storage device 20 CM
51, 52, 53 Communication line

Claims (4)

A storage management device connected to a recording medium processing device that reads and writes data from and to a recording medium, and a storage device that provides a volume using a storage device,
A restore processing unit that reads backup data recorded in the recording medium in units of a data string of a predetermined size and stores it in a restore destination volume;
A confirmation unit for confirming whether the data string read from the recording medium by the restore processing unit is zero data that is all zero;
A release processing unit that issues a physical area release instruction to the storage device for a write area of the zero data string in the restore destination volume when the data string read from the recording medium is zero data; A storage management device. When the backup source volume is a capacity virtual disk,
Calculate the restore destination physical disk free capacity, compare the calculated restore destination physical disk free capacity with the backup source physical allocated capacity indicating the physical disk capacity allocated to the backup source volume, and A determination unit for determining whether the backup data of the recording medium can be restored to the restore destination volume;
The storage management apparatus according to claim 1, wherein when it is determined that restoration is possible, the restore processing unit stores backup data of the recording medium in the restore destination volume. During backup processing for storing the data of the backup source volume in the recording medium,
Disk information indicating whether or not the backup source volume is the capacity virtual disk and physical allocated capacity information indicating the physical disk capacity allocated to the backup source volume are stored in the storage device. The storage management apparatus according to claim 1, further comprising a recording control unit. To a computer connected to a recording medium processing apparatus that reads and writes data from and to a recording medium, and a storage apparatus that provides a volume using a storage device,
Processing for reading backup data recorded in the recording medium in units of a data string of a predetermined size and storing it in a restore destination volume;
A process of confirming whether the data string read from the recording medium is zero data that is all zero;
When the data string read from the recording medium is zero data, the storage apparatus is caused to execute a process of issuing a physical area release instruction for the write area of the zero data string in the restore destination volume. A storage management program.

Images