JP6828253B2 - Backup control device, backup control method and program - Google Patents

Description

The present invention relates to a backup control device, a backup control method and a program.

When backing up data, a large amount of data is transferred to the backup storage and written. In addition, with the spread of technologies such as server virtualization and cloud computing, the demand for backup of the same data is increasing. Therefore, various technologies related to backup are being studied.

Patent Document 1 describes an automatic backup schedule device that can effectively utilize the storage device. In the automatic backup schedule device described in Patent Document 1, the retention period calculation means calculates the retention period of the differential backup data, and the backup data deletion schedule registration means creates the deletion schedule. Further, in the automatic backup schedule device, the backup data deletion execution means refers to the deletion schedule and deletes the differential backup data whose retention period has expired.

Japanese Unexamined Patent Publication No. 2001-195286

As described above, with the spread of technologies such as virtual servers and cloud computing, efficient backup means that eliminates duplication are required. That is, further efficiency of backup is required for the technology and the like described in Patent Document 1.

The present invention has been made to solve the above problems, and a main object of the present invention is to provide a backup control device or the like that enables efficient backup.

The backup control device according to one aspect of the present invention is determined by a copy omission determination means for determining whether or not the copy process of the data to be backed up can be omitted and a copy omission determination means based on a predetermined condition for backup. A backup creation means that creates backup data of data based on the result, a restore method determination means that determines the backup data corresponding to the data when the data is restored, and a backup data specified by the restore method determination means. It is provided with a restoration means for performing restoration using.

Further, the backup control method in one aspect of the present invention determines whether or not the copy processing of the data to be backed up can be omitted based on a predetermined condition related to the backup, and backs up the data based on the result of the determination. When data is created and data is restored, the backup data corresponding to the data is determined, and the backup data specified by the determination is used for restoration.

Further, the program according to one aspect of the present invention is based on a process of determining whether or not the copy process of the data to be backed up can be omitted from the computer based on a predetermined condition regarding backup, and a process of determining whether or not the copy process of the data to be backed up can be omitted. The process of creating backup data of data, the process of determining the backup data corresponding to the data when the data is restored, and the process of performing the restore using the backup data specified by the determination are executed.

According to the present invention, it is possible to provide a backup control device or the like that enables efficient backup.

It is a figure which shows the structure of the backup control apparatus in 1st Embodiment of this invention. It is a figure which shows an example of the screen in the case where the schedule management unit accepts the schedule requirement of an administrator in the 1st Embodiment of this invention. It is a figure which shows an example of the table of the backup database which recorded the backup requirement by an administrator in 1st Embodiment of this invention. It is a figure which shows an example of the screen when the schedule management part accepts a schedule requirement of a user in 1st Embodiment of this invention. It is a figure which shows an example of the table of the backup database which recorded the backup requirement by the user in 1st Embodiment of this invention. It is a figure which shows an example of the table which records the information of the virtual server which the backup requirement by a user is determined in 1st Embodiment of this invention. It is a figure which shows an example of the table which manages the user information in the 1st Embodiment of this invention. It is a figure which shows an example of the backup table used in the backup control apparatus in 1st Embodiment of this invention. It is a flowchart which shows the operation example of the backup making process of the backup control apparatus in 1st Embodiment of this invention. This is an example of a screen when the restore unit receives a restore instruction in the first embodiment of the present invention. It is a figure which shows an example of the backup operation of the backup control device 10 in the 1st Embodiment of this invention. It is a figure which shows the structure of the backup control apparatus in 1st Embodiment of this invention. It is a figure which shows an example of the information processing apparatus which realizes the backup control apparatus and the like in embodiment of this invention.

Each embodiment of the present invention will be described with reference to the accompanying drawings. In each embodiment of the present invention, each component of each device or the like represents a block of functional units. A part or all of each component of each device or the like is realized by an arbitrary combination of the information processing device 1000 and the program as shown in FIG. 13, for example. The information processing device 1000 includes the following configuration as an example.

-CPU (Central Processing Unit) 1001
-ROM (Read Only Memory) 1002
・ RAM (Random Access Memory) 1003
-Program 1004 loaded into RAM 1003
A storage device 1005 for storing the program 1004.
Drive device 1007 for reading and writing the recording medium 1006.
-Communication interface 1008 for connecting to the communication network 1009
・ Input / output interface 1010 for inputting / outputting data
-Bus 1011 connecting each component
Each component of each device in each embodiment is realized by the CPU 1001 acquiring and executing the program 1004 that realizes these functions. The program 1004 that realizes the functions of each component of each device is stored in, for example, a storage device 1005 or a RAM 1003 in advance, and is read by the CPU 1001 as needed. The program 1004 may be supplied to the CPU 1001 via the communication network 1009, or may be stored in the recording medium 1006 in advance, and the drive device 1007 may read the program and supply the program to the CPU 1001.

There are various modifications in the method of realizing each device. For example, each device may be realized by any combination of the information processing device 1000 and the program, which are separate for each component. Further, a plurality of components included in each device may be realized by any combination of one information processing device 1000 and a program.

Further, a part or all of each component of each device is realized by a general-purpose or dedicated circuit including a processor or the like, or a combination thereof. These may be composed of a single chip or may be composed of a plurality of chips connected via a bus. A part or all of each component of each device may be realized by a combination of the above-mentioned circuit or the like and a program.

When a part or all of each component of each device is realized by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged or distributed. May be good. For example, the information processing device, the circuit, and the like may be realized as a form in which each of the client and server system, the cloud computing system, and the like is connected via a communication network.

First, the first embodiment of the present invention will be described. As shown in FIG. 1, the backup control device 100 according to the first embodiment of the present invention includes at least a backup creation unit 110, a copy omission determination unit 111, a restore unit 120, and a restore method determination unit 121. These are the components enclosed by the dotted line in FIG.

The copy omission determination unit 111 determines whether or not the copy processing of the data to be backed up can be omitted based on the backup conditions. The copy elision determination unit 111 determines that the backup data to be backed up will be used when the backup data satisfying the backup conditions has already been created. That is, in this case, the copy omission determination unit 111 determines that the data copy process associated with the backup can be omitted. If the backup data satisfying the conditions for backup has not been created, the copy omission determination unit 111 determines that the backup data needs to be created, that is, the data copy process associated with the backup cannot be omitted.

The backup creation unit 110 creates backup data of data to be backed up based on the determination result by the copy omission determination unit 111. That is, when the copy omission determination unit 111 determines that the backup data needs to be created, the backup creation unit 110 creates the backup data.

The restore method determination unit 121 determines the restore method of the backed up data when the data backed up by the restore unit 120 is restored. That is, the restore method determination unit 121 determines which backup data is used for restoration. When the restore method determination unit 121 backs up the data to be restored, if the copy omission determination unit 111 determines that the copy process can be omitted, the restore method determination unit 121 restores using the backup data that satisfies the conditions for backup. Is determined to be performed. If the copy omission determination unit 111 determines that the copy process cannot be omitted, the restore method determination unit 121 restores using the backup data created by the backup creation unit 110 at that time. Is determined.

The restore unit 120 restores using the backup data specified by the restore method determination unit 121.

In addition to this, the backup control device 100 includes a backup deletion unit 130, a schedule management unit 140, and a backup database 150.

The backup deletion unit 130 deletes the specified record from the backup table of the backup database 150 based on the instructions of the schedule management unit 140 and the like described later. Further, the backup deletion unit 130 deletes the backup data as needed, for example, when there is no record related to the backup data.

The schedule management unit 140 manages the backup schedule based on the request from the user or the administrator. The schedule management unit 140 is realized by, for example, a program including a Web interface, a database input / output interface, and the like.

Backup requirements are recorded in the backup database 150. The backup requirement indicates the conditions for performing backup, such as the backup interval, the time when the backup is performed, and the generation of backup data stored in the backup storage 60, which will be described later. The backup database 150 is realized by an RDBMS (Relational Database Management System) or the like.

In the present embodiment, it is assumed that the user is a person who uses each device shown in FIG. 1 such as the virtual machine 401 of the physical server 40 via the user terminal 20 or the like described later. It is assumed that the administrator is a person who manages each device shown in FIG. 1 including the backup control device 100.

The backup control device 100 can be used in, for example, IaaS (Infrastructure as a Service). In IaaS, the user may rent a virtual server and manage it. Therefore, backup may be performed by both the user (tenant administrator) who rents the virtual server and the administrator (infrastructure administrator) who rents the virtual server.

The backup control device 100 is used in combination with the other components shown in FIG. 1 as an example of the above case. That is, the backup control device 10 is used in combination with the user terminal 20, the administrator terminal 30, the physical server 40, the master storage 50, and the backup storage 60.

The user terminal 30 is a terminal used by a user who uses or manages a virtual server 401 or the like described later. The user terminal 20 is realized by, for example, a Web browser operating on a PC (Personal Computer), FTP (File Transfer Protocol) client software, terminal software, or the like. The user terminal 20 may be realized by operating the above-mentioned software on a smartphone, tablet, or the like.

The administrator terminal 20 is a terminal used by an administrator or the like who manages each component shown in FIG. Like the user terminal 20, the administrator terminal 30 is realized by a Web browser, FTP client software, terminal software, or the like running on a PC.

The physical server 40 hosts one or more virtual servers 401. The physical server 40 is realized by a general server. The physical server 40 includes a virtual machine monitor so that the virtual server 401 operates. Examples of virtual machine monitors include VMware vsSphere®, Microsoft Hyper-V, and the like. The virtual server 401 is a virtual server hosted by the physical server 40. The virtual server 401 is managed by, for example, the above-mentioned user.

The master storage 50 stores data used by the physical server 40, the virtual server 401, and the like. The master storage 50 is accessed from the physical server 40, the backup control device 10, and the like. The master storage 50 and the backup control device 10 or the master storage 50 and the physical server 40 are connected via a communication network 70 or 71 or the like. Communication is performed between these devices using a protocol such as iSCSI (Internet Small Computer System Interface).

The master storage 50 has one or more volumes 501. Each of the volumes 501 stores data used by, for example, a virtual server 401. Each of the volumes 501 is recognized by the backup control device 10 or the physical server 40 or the like as, for example, a LU (Logical Unit) of the SCSI interface. The data held by the volume 501 includes, for example, the OS (Operating System) of the virtual server 401, the application program, or the data used by the application program. However, volume 501 may hold other types of data.

The backup storage 60 is a storage device that backs up the data held by the volume 501 of the master storage 50. The type of storage device used as the backup storage 60 is not particularly limited. As an example, the backup storage 60 holds backup data for the volume 501 of the master storage 50 for two generations. In the example shown in FIG. 1, the backup data is stored as backups 601 and 602. Backups 601 and 602 are, for example, compressed image files. However, the backups 601 and 602 may have different formats from the image files, respectively. The backup storage 60 is accessed from the backup control device 10 as needed for control. The backup control device 10 and the backup storage 60 are connected via a communication network. Communication is performed between the backup control device 10 and the backup storage 60 by using a protocol such as NFS (Network File System).

The backup control device 10 controls the backup of data from the master storage 50 to the backup storage 60 and the restoration from the backup storage 60 to the master storage 50.

In the example shown in FIG. 1, each of the administrator terminal 30, the master storage 50, and the backup storage 60 is described one by one. However, the number of each component including the user terminal 20 and the physical server 40 is not limited to one, and may be any number. Further, the configurations of the user terminal 20, the administrator terminal 30, the physical server 40, the master storage 50, and the backup storage 60 may be different from those in FIG. These configurations may be appropriately changed depending on, for example, the type of service provided.

Subsequently, the details of the configuration and operation of the backup control device 10 according to the first embodiment of the present invention will be described with reference to an operation example of backup.

In the following operation example, the administrator of each device shown in FIG. 1 determines in advance a backup requirement, which is one of the backup-related conditions, based on the service level of the service provided to the user such as the virtual server 401. I assume that. As described above, the backup requirement is a condition for performing backup, such as a backup interval and a generation of backup data stored in the backup storage 60. As an example, the backup requirement is defined as "acquire a new backup within one day from the previous backup and store the backup data of 7 generations (past 7 times) in the backup storage 60".

The processing performed by the virtual server 401 depends on how the user uses the virtual server 401. Therefore, it may be difficult for the administrator to know the appropriate time to execute the backup. Therefore, in the following operation example, it is assumed that the administrator does not specify the backup time as the backup requirement of the administrator.

When the backup requirement by the administrator is determined, the backup requirement is input to the schedule management unit 140 of the backup control device 10 from, for example, the administrator terminal 30 via the communication network 70. The schedule management unit 140 registers the received backup requirements in the backup database 150.

As described above, the schedule management unit 140 is realized by, for example, a Web interface, a program having a database input / output interface for the backup database 150, and the like. FIG. 2 is an example of a screen when the schedule management unit 140 accepts the schedule requirements of the administrator. The screen shown in FIG. 2 is displayed on, for example, the display of the administrator terminal 30. In the example shown in FIG. 2, the administrator inputs the backup deadline and the backup generation requirements. The backup deadline indicates the interval between backups in units of days. The backup generation indicates the number of generations of backup data stored in the backup storage 60. When the schedule management unit 140 accepts these requirements as the backup requirements of the administrator, the schedule management unit 140 records the numerical value input to the backup database 150.

FIG. 3 shows an example of a table in backup database 150 that records backup requirements by administrators. The table shown in FIG. 3 is an example in which the above-mentioned backup deadline and backup generation requirements are accepted as backup requirements by the administrator.

Further, in this operation example, it is assumed that the user sets the backup requirement for each virtual server 401. Similar to the backup requirement by the user, the backup requirement by the user is defined as, for example, "a backup is acquired at 2:00 every day, and the acquired backup is stored for three generations".

The backup requirement by the user is determined based on the operation characteristics of the application software running on the virtual server 401 as an example. For example, in the virtual server 401 running application software with a high data update frequency, a short backup cycle is set as one of the backup requirements. If the load of the application software differs depending on the time zone, the time for backing up is set in the time zone when the load of the application software is often reduced. For the virtual server 401 running application software that handles important data, the backup generation is stored so that the number of backup generations stored (that is, the number of past backup data stored) is larger than in other cases. Is determined.

Note that the backup requirements by the user may be determined based on conditions different from the operating characteristics of the application software running on the virtual server 401. Backup requirements may be set for each user, for example.

When the backup requirement by the user is determined, the backup requirement is input from the user terminal 20 or the like to the schedule management unit 140 of the backup control device 10 via the communication network 70, similarly to the backup requirement by the administrator. The schedule management unit 140 registers the backup requirements by the received user in the backup database 150.

FIG. 4 is an example of a screen when the schedule management unit 140 accepts the user's schedule requirements. The screen shown in FIG. 4 is displayed on, for example, the display of the user terminal 20. In the example shown in FIG. 4, the administrator inputs requirements regarding the backup cycle, backup time, and backup generation. The backup cycle indicates the interval at which backup is performed in units of days. The backup time indicates the time when the backup is performed. It is assumed that the user can easily assume the time zone when the load of the application software is low as compared with the administrator. Therefore, in this operation example, the schedule management unit 140 accepts the backup time as a schedule requirement of the user. Further, the backup generation indicates the number of generations of backup data stored in the backup storage 60. When the schedule management unit 140 accepts these requirements as the backup requirements of the user, the schedule management unit 140 records the numerical value input to the backup database 150.

FIG. 5 shows an example of a table in the backup database 150 that records the backup requirements by the user. The table shown in FIG. 5 is an example in which the above-mentioned backup cycle, backup time, and backup generation requirements are accepted as backup requirements by the user.

Note that the backup requirements by the user may be set for a plurality of virtual servers 401. In addition, backup requirements by users may be set by multiple users. The schedule management unit 140 manages backup requirements by a plurality of users. FIG. 6 shows an example of a table that records information on the virtual server 401 for which backup requirements are set by the user.

The table shown in FIG. 6 shows the relationship between the virtual server 401, the user who uses the virtual server 401, and the volume 501 of the master storage 50 used by the virtual server 401 for each virtual server 401 indicated by the virtual server ID. To store. In the example of the table shown in FIG. 6, the virtual server 401 whose virtual server ID is "0401" is used by the user whose user ID is "0001", and the volume 501 whose volume ID is "0501" is used. It has been shown to be.

Further, the user information included in the table shown in FIG. 6 is managed in the table shown in FIG. 7, for example. In the example of the table shown in FIG. 7, the relationship between the user ID of the user and the user name is managed. Further, in the example of the table shown in FIG. 7, a user ID is also assigned to the administrator.

The schedule management unit 140 instructs the backup creation unit 110 to perform backup based on the backup requirements of the administrator and the user. The backup creation unit 110 performs backup based on the instruction of the schedule management unit 140. That is, the backup requirements of the administrator and the user are satisfied by instructing the backup creation unit 110 to perform backup according to each backup requirement by the schedule management unit 140. Further, the backup creation unit 110 backs up according to the backup requirements of the administrator and the user based on the instruction of the schedule management unit 140.

The schedule management unit 140 determines by various methods whether or not to give an instruction to the backup creation unit 110. As an example, the schedule management unit 140 accesses the backup database 150 at predetermined intervals and refers to the backup requirements of the user and the administrator. Then, the schedule management unit 140 gives a backup instruction to the backup creation unit 110 when there is a backup requirement that requires backup at that time. The above-mentioned interval is, for example, every minute. That is, the schedule management unit 140 accesses the backup database 150 every minute, and instructs the backup creation unit 110 to back up according to the existence of the backup requirement.

As an example, when the backup time of the backup requirement referred to by the schedule management unit 140 is 2:00 every day and the current time is 2:00, the schedule management unit 140 instructs the backup creation unit 110 to back up. .. In addition, if there is a backup requirement that the backup be performed within one day from the previous backup, and the latest backup is performed 24 hours and 0 minutes before, the schedule management unit 140 gives a backup instruction. Do.

The schedule management unit 140 may access the backup database 150 at an interval different from the above-mentioned interval and refer to the backup requirements of the user and the administrator. Alternatively, the schedule management unit 140 may be realized by an event-driven implementation in order to reduce the load.

When a backup is performed, the backup creation unit 110 or the like records information about the backup in the backup table provided in the backup database 150. FIG. 8 shows an example of a backup table. In the backup table of FIG. 8, the user ID of the user who defines the backup requirement, the volume ID of the volume 501 in which the data to be backed up is stored, the execution date and time of the backup, and the file name of the backup data are recorded.

Further, when instructing the backup creation unit 110 to back up, the schedule management unit 140 notifies the above-mentioned user ID and volume ID, and information on the backup target period. The backup target period is the period during which backup should be performed for each backup requirement.
For example, if the previous backup was performed at 2:00 on the previous day, the backup requirement is "within one day from the previous backup", and the current time is 2:00, the backup target period is 2:00 on the previous day. It will be from 01 to 2:00 of the day. If the backup requirement is "2:00 every day" and the current time is 2:00, the backup target period is from 2:00 on that day to 2:00 on that day.

When the backup creation unit 110 receives a backup instruction, the backup creation unit 110 backs up the volume 501 based on the determination result of the copy omission determination unit 111. That is, the backup creation unit 110 creates backup data when it is determined by the copy omission determination unit 111 that backup is necessary. Further, when the backup creation unit 110 performs a backup, the backup creation unit 110 records the information related to the backup in the backup database 150. FIG. 9 is a flowchart showing an example of a backup creation process by the backup creation unit 110. An example of a backup creation procedure by the backup creation unit 110 will be described with reference to the flowchart shown in FIG.

Upon receiving a backup instruction from the schedule management unit 140, the backup creation unit 110 first acquires information regarding the backup target (step S101). The information regarding the backup target includes, for example, a user ID related to the backup requirement, a volume ID, a backup target period, and the like.

Subsequently, the backup creation unit 110 searches the backup table of the backup database 150 and extracts records that match the conditions (step S102). The conditions are, for example, that the volume ID recorded in the record and the volume ID acquired in step S101 match, and that the backup date and time of the record is included in the backup target period acquired in step S101. The backup creation unit 101 extracts records from the backup table when the conditions are satisfied.

Subsequently, the copy omission determination unit 111 determines whether or not to omit the copy process regarding the creation of backup data (step S103). The copy omission determination unit 111 determines whether or not to omit the copy process based on whether or not there is a record satisfying the condition shown in step S102.

In step S103, the copy omission determination unit 111 determines that the copy process is omitted when there is a record satisfying the condition shown in step S102. In this case, backup data has already been created for the target volume during the period specified as the backup target period based on other backup requirements. That is, the copy omission determination unit 111 determines that the copy process is omitted when the backup for the volume 501 to be backed up is performed during the period designated as the backup target period.

When the copy omission determination unit 111 determines that the copy process is omitted (step S103: Yes), the backup creation unit 110 makes necessary settings so as to use the backup data already created.

That is, the backup creation unit 110 selects the record with the latest backup date and time from the records extracted in step S102 (step S104). Then, the backup creation unit 110 creates a new record corresponding to the backup instruction from the schedule management unit 140 and adds it to the backup table of the backup database 150 (step S105). In this case, a record is created so that the existing file is used as backup data.

In step S105, the user ID and volume ID recorded in the new record are the user ID and volume ID acquired in step S101. Further, the backup date and time and the file name of the backup data recorded in the new record are the backup date and time and the file name included in the record selected in step S104. That is, instead of creating the backup data, the created backup data satisfying the conditions is used, so that the copy process related to the creation of the backup data is omitted.

When the copy omission determination unit 111 determines that the copy process is not omitted (step S103: No), new backup data is created. In this case, the backup creation unit 110 performs necessary processing when creating new backup data.

The backup creation unit 110 creates a new record corresponding to the backup instruction from the schedule management unit 140 and adds it to the backup table of the backup database 150 (step S106).

In step S106, the user ID and volume ID recorded in the new record are the user ID and volume ID acquired in step S101. In addition, the backup date and time recorded in the new record is the time at that time, and the file name of the backup data is set by generating the only file name that does not overlap with the file life of other backup data. That is, in step S106, a record is created on the premise of creating new backup data.

Subsequently, the backup creation unit 110 creates backup data in the backup storage 60 (step S107). As the file name of the backup data, the file name generated in step S106 is used. The backup data is performed by copying the backup data from the volume 501 to be backed up in the master storage 50. It is assumed that the backup data generated in step S107 is, for example, a compressed image file.

In step S107, the method of creating backup data by the backup creation unit 110 is not particularly limited. For example, the backup creation unit 110 may create a snapshot of the volume 501 to be backed up so that a quiesce point of the file can be secured even while the virtual server 401 is operating. In this case, the backup creation unit 110 reads necessary data from the created snapshot and writes it to the backup data. In addition, the snapshot may be deleted after the writing of the backup data is completed.

When the process of step S105 or S107 is completed, the backup creation unit 110 notifies the schedule management unit 140 and the like of the completion of the backup process as necessary (step S108).

Upon receiving the notification of the completion of the backup process, the schedule management unit 140 may delete old backups exceeding the number of backup generations specified by the user or the administrator.

In this case, the backup to be deleted is determined based on the backup table recorded in the backup database 150 and the backup requirements of the user or administrator. Then, the schedule management unit 140 instructs the backup deletion unit 130 to delete the backup. The schedule management unit 140 notifies the backup deletion unit 130 of, for example, the backup user ID, volume ID, and backup date and time to be deleted.

The backup deletion unit 130 deletes the record corresponding to the notified information from the backup table of the backup database 150 based on the instruction from the schedule management unit 140. Then, the backup deletion unit 130 confirms the existence of another record that specifies the file name of the backup data included in the deleted record as the file name. This is because the backup data may be used in other backup records, such as when the backup data copy process is not performed. If there is no other record that specifies the file name of the backup data included in the deleted record as the file name, the backup deletion unit 130 deletes the backup data of the file name.

Further, when it becomes necessary to restore from the backups 601 and 602, such as when a problem occurs in the volume 501 of the master storage 50, the user or the administrator gives an instruction to restore. A restore instruction is given from the user terminal 20 or the administrator terminal 30 to the restore unit 120 of the backup control device 10 via the communication network 70 or 71.

As described above, the restore unit 120 restores using the backup data corresponding to the data to be backed up. The restore unit 120 is realized by, for example, a program having a Web interface, a database input / output interface, and the like, like the schedule management unit 140 and the like. The restore unit 120 copies the backup data such as the backup 601 or 602 to the volume 501 to be restored, and returns the contents of the volume 501 to the state at the time of creating the backup data.

FIG. 10 is an example of a screen when the restore unit 120 receives a restore instruction. The screen shown in FIG. 10 is displayed on, for example, the user terminal 20 or the administrator terminal 30. In the screen example shown in FIG. 10, a plurality of generations of backups 601 and the like stored in the backup storage are displayed. The user or administrator appropriately specifies the desired backup date and time. The restore unit 120 restores using the backup 601 or the like backed up at the designated backup date and time.

In this operation example, it is assumed that the backup data is, for example, a compressed image file. However, when the backup creation unit 110 creates backup data, a plurality of backup methods may be used. In this case, the restore method determination unit 121 determines the restore method. In this case, the restore method determination unit 121 determines the restore method of the backed up data. The restore unit 120 restores by an appropriate method based on the result of the determination by the restore method determination unit 121.

Subsequently, an example of a more specific operation of the backup control device 10 based on the above-described operation example will be described. FIG. 11 is a diagram showing an example of a more specific operation of the backup control device 10. In FIG. 11, the leftmost column shows the time when the event occurred. The middle column shows the events that occurred at each of the times shown in the left column. The rightmost column shows the state of storage stored in the backup storage 60 after an event occurs at each of the times shown in the two columns on the left. Each row in FIG. 11 shows each event that has occurred. Further, in the example shown in FIG. 11, the backup based on the backup requirement of the user is referred to as "user backup", and the backup based on the backup requirement of the administrator is referred to as "administrator backup".

In the example shown in FIG. 11, the backup requirements have been set by 15:45 on November 15. The backup process started at 2:00 on November 16th. Initially, backup is performed based on the user's backup requirements. That is, the backup creation unit 110 creates backup data with the file name "A" at 2:00 on November 16th, and backup data with the file name "B" at 2:00 on November 17th. Is created.

Following the backup of the user, a backup will be performed at 15:38 on November 17, based on the backup requirements of the administrator. In this case, the backup requirement of the administrator is "the backup deadline is 2 days". That is, if the backup is created within 2 days, the backup requirement of the administrator is satisfied. In the example of FIG. 11, the backup data of "A" and "B" both satisfy the backup requirements of the administrator. Therefore, the copy elision determination unit 111 determines that the creation of backup data and the copy processing associated with the creation of backup data are unnecessary. As a result, the backup data with the file name "B" whose backup date is newer is used as the backup data of the administrator backup.

After that, the backup is continuously performed in the same manner as in the above-mentioned example. That is, backup is performed every day at 2:00 based on the user's backup requirements. Further, old backup data that does not meet the backup requirements, such as the backup at 2:00 on November 18, is appropriately deleted by the backup deletion unit 130. In addition, at 2:00 on November 19, backup will be performed based on the backup requirements of the administrator. Even in this case, the backup data created at the time of user backup is used as backup data for administrator backup.

As described above, in the backup control device 10 according to the first embodiment of the present invention, the copy omission determination unit 111 determines whether the data copy process associated with the backup can be omitted based on the backup conditions such as backup requirements. To do. Then, the backup creation unit 110 uses the created backup data when the created backup data is available. The backup creation unit 110 newly creates backup data only when necessary. In addition, the restore unit 120 refers to the necessary backup data for restoration.

Therefore, the control by the backup control device 10 in the present embodiment suppresses the creation of unnecessary backup data. Therefore, the capacity of the backup storage 60 required for storing the backup data is reduced. For example, in the example shown in FIG. 11 described above, in the administrator backup at 15:38 on November 17, no new backup data is generated based on the determination of the copy omission determination unit 111. In this case, the created backup data is used. That is, the capacity of the backup storage 60 required for storing the backup data is reduced while satisfying the backup requirements of the administrator.

Further, the control by the backup control device 10 in the present embodiment reduces the load on each device, communication network, etc. required for the backup process. As described above, in the example shown in FIG. 11, the copy process associated with the creation of backup data is omitted in the administrator backup at 15:38 on November 17. Therefore, the load on the CPU, memory, and input / output interface of the server that realizes the backup control device 10 is reduced, and the load required for reading from the master storage 50 and the load required for writing to the backup storage 60 are reduced. To. Further, the load on the communication network 70 or 71 used for transferring data from the master storage 50 to the backup storage 60 is reduced.

Therefore, the backup control device 10 in the present embodiment enables efficient backup.

(Modification example)
A modification of the backup control device 10 according to the first embodiment of the present invention can be considered. In the backup control device 10 according to the first embodiment described above,
Copying the data to be backed up was omitted, mainly based on time-of-day backup requirements. On the other hand, for example, the copy process of the data to be backed up may be omitted based on the backup requirement regarding the range of the data to be backed up.

FIG. 12 is a diagram showing an example of a case where the copy omission determination unit 111 determines whether or not the copy processing of the data to be backed up can be omitted based on the backup requirement regarding the range of the data to be backed up. Is. In the example shown in FIG. 12, the data of the virtual server 401 is stored as the virtual disk file image 510 in the volume 501 formatted by the file system that can be recognized by the virtual machine monitor. The file system that can be recognized by the virtual machine monitor corresponds to, for example, VMFS (Virtual Machine File System) when the virtual machine monitor is VMware vSphere. The virtual disk file image 510 corresponds to VMDK (Virtual Machine Disk), for example, when the virtual machine monitor is VMware vSphere.

Further, in the example shown in FIG. 12, the backup 601 is stored in the backup server 60 as a backup for the volume 501. The backup 602 is stored in the backup server 60 as a backup for the virtual disk image file 510.

In this modification, the administrator's backup requirement is defined as, for example, "the entire volume 501 is backed up at 2:00 every day and stored for 7 generations." Further, the backup requirement of the user is defined as, for example, "a virtual disk image file 510 is backed up every other day at 2:00 and stored for three generations".

When such backup requirements are set, when backup is performed based on the backup requirements of the user, backup is performed at the same time based on the backup requirements of the administrator. That is, when the restoration is performed based on the request from the user, it is possible to perform the restoration using the backup data backed up based on the backup requirements of the administrator. Therefore, in this case, the copy omission determination unit 111 can determine that the copy processing of the data related to the backup based on the backup requirement of the user can be omitted.

In this modification, the copy elision determination unit 111 makes a determination in the same manner as the copy elision determination unit 111 of the backup control device 10 in the first embodiment. That is, when backup data satisfying the backup requirement already exists, it is determined that a new backup is unnecessary, and the copy process associated with the backup is omitted. In this modification, the copy elision determination unit 111 also considers the case where the backup target is the virtual image file 510 when determining whether or not the backup requirement is satisfied. That is, the copy omission determination unit 111 determines whether or not the backup data including the virtual image file 510 exists when determining the omission of the copy process.

When the restoration is performed by the user, for example, the restoration method determination unit 121 determines whether the restoration is executed using the backup 601 or 602. When restoring from the backup 601 which is the backup data of the image file 510, the restore unit 120 recognizes the file system of the backup 601 and takes out the data.

In this modification, when omitting the copy for backup, it is premised that the backup times specified as the backup requirements of the user and the administrator match. In this case, the backup time may not be specified for the user's backup requirements. For example, on the screen as shown in FIG. 4 in which the schedule management unit 140 accepts the user's schedule requirements, the backup time input field may be omitted. Alternatively, the backup time in the administrator's backup requirement may be used as the default value of the backup time in the user's backup requirement. In addition, when the user is set to perform backup at a time different from the backup time by the administrator, the schedule management unit 140 issues a warning or charges the user an additional fee. There may be.

In this modification, if the inventor's backup requirement is to retain older generation data compared to the administrator's backup requirement, unnecessary data is stored in the backup storage 60 as backup data. There is. In this case, the utilization efficiency of the backup storage 60 may decrease.

For example, assume that the administrator's backup requirement is set to "back up the entire volume 501 at 2:00 every day and store it for three generations." Further, it is assumed that the backup requirement of a certain user is defined as "backup of virtual disk image file 5011 at 2:00 every day and store it for 4 generations". It is assumed that the copy omission determination unit 111 determines that the data copy process can be omitted when backing up based on the backup requirements of the user.

In this example, it is necessary to store the backup data of the 4th generation in order to enable the restoration from the backup data of the 4th generation before based on the backup requirement of the user described above. When the backup requirements of other users specify the storage of backup data of less than 4 generations, if only the backup data of the virtual disk image file 5011 is stored as the backup data of 4 generations ago. Good. Volume 501 does not have to be stored in the backup storage 60 as backup data four generations ago. However, since the volume 501 is stored in the backup storage 60 as backup data four generations ago, the utilization efficiency of the backup storage 60 is lowered.

The backup creation unit 110 may create a new backup by extracting only the data necessary for satisfying the backup requirement of the user from the backup 601 that does not meet the backup requirement of the administrator. In the above example, the backup creation unit 110 extracts the virtual disk image file 510 related to the user from the backup 601 four generations ago, creates a new backup, and deletes the backup 601 four generations ago.

By operating the backup creation unit 110 or the copy omission determination unit 111 in this way, it is possible to improve the utilization efficiency of the backup storage 60.

Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the structure and details of the present invention within the scope of the present invention. In addition, the configurations in each embodiment can be combined with each other as long as they do not deviate from the scope of the present invention.

10 Backup control device 110 Backup creation unit 111 Copy omission judgment unit 120 Restore unit 121 Restore method judgment unit 130 Backup deletion unit 140 Schedule management unit 150 Database 20 User terminal 30 Administrator terminal 40 Physical server 401 Virtual server 50 Master storage 501 Volume 60 backup storage 601 and 602 backup

Claims (10)

A schedule management unit that instructs the execution of the backup at the interval based on the backup requirement including information indicating the interval for performing the backup.
When the execution of the backup is instructed, the copy omission determination means for determining whether or not the copy processing of the data to be backed up can be omitted based on the predetermined conditions related to the backup, and the copy omission determination means.
A backup creation means that creates backup data of the data based on the determination result by the copy omission determination means, and
When the data is restored, the restoration method determining means for determining the backup data corresponding to the data, and
A restore means for performing a restore using the backup data specified by the restore method determining means is provided.
The predetermined condition is that, when the backup data has already been created, the date and time when the already created backup data is created is after the previous backup execution regarding the backup requirement, and this time. A backup control device that is included in the period for which the backup should be performed, which is the period until the backup is executed . The backup control device according to claim 1, wherein the copy omission determination means determines that the copy process is omitted when backup data satisfying the predetermined condition exists. The backup control device according to claim 1 or 2, wherein the copy omission determination means determines that the copy process cannot be omitted when backup data satisfying the predetermined condition does not exist. The copy elision determination means according to any one of claims 1 to 3, wherein the copy omission determination means determines that the copy process is omitted when the backup data generated at the time specified in the predetermined condition exists. Backup controller. The copy elision determination means according to any one of claims 1 to 4, wherein the copy omission determination means determines that the copy process is omitted when the backup data including the data in the range specified in the predetermined condition exists. Backup controller. The backup control device according to any one of claims 1 to 5, wherein the backup creating means creates the backup data when it is determined that the copy process cannot be omitted. The backup control device according to any one of claims 1 to 6, wherein the restore method determining means determines to use the backup data satisfying a predetermined condition regarding the backup when the copy process is omitted. .. The restore method determining means determines that the generated backup data will be used when the copy process is indispensable when backing up the data and the backup data is generated by the backup creating means. The backup control device according to any one of Items 1 to 7. The backup controller
Instruct the execution of the backup at the interval based on the backup requirement including information indicating the interval at which the backup is performed.
When the execution of the backup is instructed, it is determined whether or not the copy processing of the data to be backed up can be omitted based on the predetermined conditions related to the backup.
Create backup data of the data based on the result of the determination,
When the data is restored, the backup data corresponding to the data is determined, and the data is restored.
Restoration is performed using the backup data specified by the determination.
The predetermined condition is that, when the backup data has already been created, the date and time when the already created backup data is created is after the previous backup execution regarding the backup requirement, and this time. A backup control method that is included in the period for which the backup should be performed, which is the period until the backup is executed . On the computer
A process of instructing the execution of the backup at the interval based on the backup requirement including information indicating the interval for performing the backup, and
When instructed to execute the backup, a process of determining whether or not the copy process of the data to be backed up can be omitted based on a predetermined condition related to the backup, and a process of determining whether or not the copy process of the data to be backed up can be omitted.
The process of creating backup data of the data based on the result of the determination, and
When the data is restored, the process of determining the backup data corresponding to the data and
The process of performing restoration using the backup data specified by the determination is executed.
The predetermined condition is that, when the backup data has already been created, the date and time when the already created backup data is created is after the previous backup execution regarding the backup requirement, and this time. A program that is included in the period for which the backup should be performed, which is the period until the backup is executed .

Images