Backup device, backup method and program
The backup device efficiently backs up multiple target devices by utilizing unique and common information acquisition units, addressing the inefficiency of single-device backup systems and enabling effective restoration processes.
Patent Information
- Application Number
- JP2023084618
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-23
- Publication Date
- 2024-12-05
AI Technical Summary
Conventional backup systems only consider backing up a single computer, making it inefficient for multiple target devices.
A backup device that includes unique and common information acquisition units to efficiently backup multiple target devices by accumulating unique and common information specific to each device, and a restoration unit to restore data using this information.
Enables efficient backup and restoration of multiple target devices by leveraging unique and common information, enhancing the backup efficiency and effectiveness for multiple devices.
Smart Images

Figure 2024168172000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a backup device or the like that backs up two or more target devices. [Background technology]
[0002] Conventionally, there has been a backup system that is claimed to be extremely practical, enabling data recovery using a method that places a smaller burden on the backup computer (see Patent Document 1).
[0003] This backup system is characterized by comprising: an automatic storage mechanism that automatically stores an operating system and software running on the operating system stored in a storage device of an in-office computer installed within a business premises in one logically divided area on the storage device of a data management computer installed outside the business premises and connected to the in-office computer so as to be able to communicate with each other; an imaging mechanism that converts the operating system and software stored in the storage device of the data management computer by this automatic storage mechanism into an image file and stores it in an image storage device connected to the data management computer so as to be able to communicate with each other and installed outside the business premises; and a reconversion mechanism that, when the operating system and software stored in the storage device of the in-office computer become inoperable, reconverts the image file into the operating system and software before conversion in the logically divided area on the storage device of the data management computer. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2011-60023 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, in the conventional technology, only the backup of one computer is considered, and it is not possible to efficiently back up multiple target devices that are the backup targets. [Means for solving the problem]
[0006] The backup device of the first invention is a backup device comprising: a unique information acquisition unit that acquires, from each of two or more target devices, unique information specific to each target device in association with each target device; a business information acquisition unit that acquires, from each of the two or more target devices, business information stored in the target devices in association with each target device; and a storage unit that stores two or more pieces of unique information for each target device and the business information for each target device in association with common information common to each of the two or more target devices.
[0007] With this configuration, multiple target devices can be efficiently backed up.
[0008] In addition, compared to the first invention, the backup device of the second invention further includes a common information acquisition unit that acquires common information common to two or more target devices, and the common information is common information acquired by the common information acquisition unit of the backup device.
[0009] With this configuration, multiple target devices can be efficiently backed up.
[0010] In addition, the backup device of the third invention is a backup device in which, compared to the first invention, each of the two or more target devices corresponds to an attribute value, and the common information acquisition unit acquires common information from the target devices for each different attribute value.
[0011] With this configuration, multiple target devices can be backed up more efficiently.
[0012] In addition, the backup device of the fourth invention is a backup device having, with respect to any one of the first to third inventions, a restoration receiving unit that receives a restoration instruction including a target device identifier, an information acquisition unit that acquires common information, unique information, and business information corresponding to the target device identifier, and a restoration unit that performs restoration using the common information, unique information, and business information acquired by the information acquisition unit.
[0013] With this configuration, the target device can be restored using the backed up information.
[0014] In addition, the backup device of the fifth invention, compared to the second or third invention, further includes a common definition management unit in which common definition information identifying the common information is stored, and the common information acquisition unit is a backup device that acquires common information based on information identified by the common definition information from at least one target device among two or more target devices or another target device.
[0015] With this configuration, multiple target devices can be efficiently backed up.
[0016] In addition, the backup device of the sixth invention, compared to any one of the first to fifth inventions, further includes a unique definition management unit in which unique definition information, which is information corresponding to each of two or more target devices and is information that identifies the unique information, is stored, and the unique information acquisition unit acquires, from each of the two or more target devices, unique information based on information identified by the unique definition information corresponding to each target device, in association with each target device.
[0017] With this configuration, multiple target devices can be efficiently backed up.
[0018] In addition, the backup device of the seventh invention, compared to any one of the first to sixth inventions, further comprises a business definition management unit in which business definition information, which is information corresponding to each of two or more target devices and is information identifying business information, is stored, and the business information acquisition unit acquires, from each of the two or more target devices, business information based on information identified by the business definition information corresponding to each target device, in association with each target device.
[0019] With this configuration, multiple target devices can be efficiently backed up. Effect of the Invention
[0020] According to the backup device of the present invention, a plurality of target devices can be efficiently backed up. [Brief description of the drawings]
[0021] [Figure 1] Conceptual diagram of information system A in embodiment 1. [Diagram 2] Block diagram of the backup device 1 constituting the information system A. [Diagram 3] A flowchart illustrating an example of the operation of the backup device 1. [Figure 4] A diagram showing the common definition management table [Diagram 5] A diagram showing the unique definition management table [Figure 6] The diagram shows the business definition management table. [Figure 7] Overview of the computer system [Figure 8] Block diagram of the computer system DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0022] Hereinafter, an embodiment of a backup device and the like will be described with reference to the drawings. Note that in the embodiments, components with the same reference numerals perform similar operations, so repeated description may be omitted.
[0023] (Embodiment 1) In this embodiment, a backup device that efficiently backs up two or more target devices by accumulating three types of information: one common information (e.g., an image file), specific information corresponding to each of two or more target devices (e.g., IaC (Infrastructure as Code) data), and business information for each target device (e.g., a file created by a user) is described.
[0024] In this embodiment, a backup device that accumulates the above three types of information for each type of target device having different common information will be described.
[0025] Furthermore, in this embodiment, a backup device that restores a target device using the three types of stored information will be described.
[0026] In this specification, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.
[0027] 1 is a conceptual diagram of an information system A according to this embodiment. The information system A includes a backup device 1 and two or more target devices 2.
[0028] The backup device 1 is a device for backing up a target device 2. The backup device 1 may be one of two or more target devices 2. The backup device 1 is usually a server. The backup device 1 is, for example, a cloud server or an ASP server, but the type is not important.
[0029] The target device 2 is a device that is the target of backup. The target device 2 may be, for example, a server, a personal computer, a tablet terminal, or a smartphone, but the type does not matter. The server may be, for example, a cloud server or an ASP server, but the type does not matter.
[0030] The backup device 1 and each of the two or more target devices 2 are usually capable of communicating with each other via a network such as the Internet or a LAN.
[0031] FIG. 2 is a block diagram of the backup device 1 constituting the information system A in this embodiment.
[0032] The backup device 1 includes a storage unit 11, a reception unit 12, a processing unit 13, and an output unit 14. The storage unit 11 includes a common definition management unit 111, a unique definition management unit 112, and a business definition management unit 113. The reception unit 12 includes a restoration reception unit 121. The processing unit 13 includes a common information acquisition unit 131, a unique information acquisition unit 132, a business information acquisition unit 133, an accumulation unit 134, an information acquisition unit 135, and a restoration unit 136.
[0033] Various types of information are stored in the storage unit 11 constituting the backup device 1. The various types of information are, for example, common definition information (to be described later), unique definition information (to be described later), and task definition information (to be described later).
[0034] The common definition management unit 111 stores one or more pieces of common definition information. The common definition information may correspond to an attribute value. The attribute value is an attribute value of the target device 2. The attribute value is, for example, a type identifier that identifies the type of the target device 2. The type of the target device 2 is, for example, an OS or the type of the device itself. The type identifier is, for example, an OS identifier that identifies the OS of the target device 2. The OS identifier is, for example, an OS name or an OS ID.
[0035] The common definition information is information that identifies the common information, and is, for example, one or more folder names, one or more directory names, one or more disk IDs, or a combination of these.
[0036] It goes without saying that the common definition information in the common definition management unit 111 may be embedded in the program.
[0037] Common information is information common to two or more target devices 2. Common information is, for example, information based on a collection of files for constructing an OS. Common information is, for example, information based on a collection of system files. Common information is, for example, a so-called image file. Common information may be, for example, an encrypted file or a compressed file. The data structure of the common information is not important.
[0038] The unique definition management unit 112 stores unique definition information corresponding to each of two or more target devices 2. Unique definition information is information that identifies unique information. The unique definition information is, for example, a folder name, a directory name, a disk identifier, an application name, an application identifier, or a combination of these. Note that the unique definition information may be common to two or more target devices 2.
[0039] The unique information is information unique to each of two or more target devices 2. The unique information is, for example, information based on a collection of files for constructing one or more applications installed in the target device 2. The unique information is, for example, IaC data. Note that IaC data may simply be referred to as IaC.
[0040] The task definition management unit 113 stores task definition information corresponding to each of two or more target devices. Task definition information is information that identifies task information. Task definition information is, for example, a folder name, a directory name, a disk identifier, a disk ID, or a combination of these. Note that the task definition information may be common to two or more target devices 2.
[0041] The business information is information accumulated in each of the two or more target devices 2. The business information is, for example, a folder name, a directory name, or a disk identifier. The business information is, for example, an image file, but it may also be an encrypted file, a compressed file, etc. The content of the business information is, for example, information accumulated and updated in a business system, such as incoming and outgoing inventory information in a store, product information in a factory, transaction information in a financial institution, or customer information, but the content is not important.
[0042] It goes without saying that the common definition information in the common definition management section 111, the unique definition information in the unique definition management section 112, and the task definition information in the task definition management section 113 may be embedded in a program.
[0043] The reception unit 12 receives various instructions and information, such as a backup instruction and a restoration instruction.
[0044] The means for inputting various instructions and information may be any means, such as a touch panel, a keyboard, a mouse, or a menu screen.
[0045] The restoration reception unit 121 receives a restoration instruction. The restoration instruction is an instruction to restore the target device 2 using the backed up information. The restoration instruction includes, for example, a target device identifier.
[0046] Here, reception is a concept that includes reception of information input from input devices such as a keyboard, mouse, or touch panel, reception of information transmitted via a wired or wireless communication line, and reception of information read from recording media such as an optical disk, magnetic disk, or semiconductor memory.
[0047] The processing unit 13 performs various types of processing. The various types of processing are processing performed by a common information acquisition unit 131, a specific information acquisition unit 132, a business information acquisition unit 133, a storage unit 134, an information acquisition unit 135, or a restoration unit 136.
[0048] The common information acquisition unit 131 acquires common information common to two, three, four or more target devices 2. The common information acquisition unit 131 may read out the common information from the storage unit 11.
[0049] The common information acquisition unit 131 acquires common information from the target device 2, for example, for each different attribute value. For example, for each different attribute value, it is each different type identifier.
[0050] The common information acquisition unit 131 acquires common information based on information identified by the common definition information of the common definition management unit 111, for example, from at least one target device 2 among two or more target devices 2, or from another target device 2 that does not constitute information system A.
[0051] The unique information acquisition unit 132 acquires unique information unique to each of the target devices 2 from two, three, four or more target devices 2 in association with each target device 2 .
[0052] The unique information acquisition unit 132, for example, acquires unique definition information corresponding to each of two or more target devices 2 from the unique definition management unit 112, and acquires unique information based on information identified by the unique definition information in association with each target device 2.
[0053] The transaction information acquisition unit 133 acquires transaction information stored in each of the two or more target devices 2 from each of the target devices 2 in association with the target device 2 .
[0054] The business information acquisition unit 133, for example, acquires business definition information corresponding to each target device 2 from the business definition management unit 113 for each of two or more target devices 2, acquires information identified by the business definition information from each target device 2, and acquires business information based on the information in association with each target device 2.
[0055] The accumulation unit 134 accumulates the common information, the unique information for each target device 2, and the business information for each target device. The accumulation unit 134 preferably accumulates the information in the storage unit 11, but may accumulate the information in another device or another recording medium.
[0056] The information acquisition unit 135 acquires information for restoring the target device 2. The information for restoring the target device 2 includes common information, unique information, and business information.
[0057] The information acquiring unit 135 acquires, for example, the common information stored by the storage unit 134. In addition, the information acquiring unit 135 acquires, for example, unique information and business information corresponding to the target device identifier included in the restoration instruction accepted by the restoration accepting unit 121.
[0058] The restoration unit 136 performs restoration using the common information, the unique information, and the business information acquired by the information acquisition unit 135 .
[0059] The restoration unit 136 uses, for example, the common information to restore the OS or system files of the target device 2. The restoration unit 136 uses, for example, the unique information to restore one or more applications of the target device 2. The restoration unit 136 uses, for example, the business information to restore one or more files created by the user in the target device 2.
[0060] The output unit 14 outputs various types of information, such as information indicating that backup has been completed and information indicating that restoration has been completed.
[0061] Here, output is a concept that includes display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over the processing results to other processing devices or other programs, etc.
[0062] Each of the two or more target devices 2 is associated with an attribute value.
[0063] The storage unit 11, the common definition management unit 111, the specific definition management unit 112, and the task definition management unit 113 are preferably non-volatile recording media, but may also be realized as volatile recording media.
[0064] There is no restriction on the process by which information is stored in the storage unit 11, etc. For example, information may be stored in the storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 11, etc., or information inputted via an input device may be stored in the storage unit 11, etc.
[0065] The reception unit 12 and the restoration reception unit 121 can be realized by a device driver for an input means such as a touch panel or a keyboard, control software for a menu screen, etc. The reception unit 12 may be realized by a wireless or wired communication means.
[0066] The processing unit 13, the common information acquisition unit 131, the unique information acquisition unit 132, the business information acquisition unit 133, the storage unit 134, the information acquisition unit 135, and the restoration unit 136 can usually be realized by a processor, a memory, or the like. The processing procedure of the processing unit 13, etc. is usually realized by software, and the software is recorded in a recording medium such as a ROM. However, it may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, or the like, and the type is not important.
[0067] The output unit 14 may or may not include an output device such as a display, a speaker, etc. The output unit 14 may be realized by driver software for an output device, or a combination of driver software for an output device and an output device, etc.
[0068] Next, an example of the operation of the backup device 1 will be described with reference to the flowchart of FIG.
[0069] (Step S301) The processing unit 13 judges whether it is time for a backup. If it is time for a backup, the process proceeds to step S302, and if it is not time for a backup, the process proceeds to step S314. Note that the timing for a backup may be, for example, a predetermined time, or an instruction from a user being accepted. There is no limitation on the trigger for starting a backup.
[0070] (Step S302) The processing unit 13 assigns 1 to a counter i.
[0071] (Step S303) The processing unit 13 judges whether or not there exists an i-th type of the target device 2. If the i-th type exists, the process proceeds to step S304, and if the i-th type does not exist, the process returns to step S301.
[0072] The processing unit 13 determines whether the i-th type exists by determining whether the i-th type identifier exists in the common definition management unit 111, for example.
[0073] (Step S304) The common information acquisition unit 131 acquires common definition information corresponding to the i-th type from the common definition management unit 111.
[0074] (Step S305) The common information acquisition unit 131 acquires information (e.g., a file, a folder) of a storage area specified by the common definition information from any of the target devices 2 corresponding to the i-th type identifier. The common information acquisition unit 131 acquires common information using the acquired information. The storage unit 134 stores the common information. The common information is, for example, an image file.
[0075] (Step S306) The processing unit 13 assigns 1 to the counter j.
[0076] (Step S307) The specific information acquisition unit 132 judges whether or not the j-th target device 2 of the i-th type exists. If the j-th target device 2 exists, the process proceeds to step S308, and if not, the process proceeds to step S313.
[0077] (Step S308) The unique information acquiring unit 132 acquires, from the unique definition managing unit 112, unique definition information paired with the object device identifier of the j-th object device 2 of the i-th type.
[0078] (Step S309) The unique information acquisition unit 132 acquires information (e.g., a file, a folder) of the storage area specified by the unique definition information from the j-th target device 2. The unique information acquisition unit 132 acquires unique information using the acquired information. The storage unit 134 stores the unique information in a pair with the target device identifier of the j-th target device 2. The unique information is, for example, Iac data.
[0079] (Step S310) The task information acquiring unit 133 acquires task definition information paired with the object device identifier of the j-th object device 2 of the i-th type from the task definition managing unit 113.
[0080] (Step S311) The business information acquisition unit 133 acquires information (e.g., a file, a folder) of a storage area specified by the business definition information from the j-th target device 2. The business information acquisition unit 133 acquires business information using the acquired information. The storage unit 134 stores the business information in a pair with the target device identifier of the j-th target device 2.
[0081] (Step S312) The processing unit 13 increments the counter j by 1. The process returns to step S307.
[0082] (Step S313) The processing unit 13 increments the counter i by 1. The process returns to step S303.
[0083] (Step S314) The restoration receiving unit 121 judges whether or not a restoration instruction has been received. If a restoration instruction has been received, the process proceeds to step S315, and if a restoration instruction has not been received, the process returns to step S301.
[0084] (Step S315) The information acquisition unit 135 acquires a target device identifier corresponding to the restoration instruction. Note that the target device identifier corresponding to the restoration instruction is, for example, the target device identifier included in the restoration instruction.
[0085] (Step S316) The information acquisition unit 135 acquires common information paired with the type identifier paired with the target device identifier. The information acquisition unit 135 acquires the common information from the storage unit 11, for example.
[0086] (Step S317) The restoration unit 136 performs a restoration process using the common information acquired in step S316 on the target device 2 identified by the target device identifier.
[0087] (Step S318) The information acquisition unit 135 acquires unique information that is paired with the target device identifier. The information acquisition unit 135 acquires the unique information from the storage unit 11, for example.
[0088] (Step S319) The restoration unit 136 performs a restoration process on the target device 2 identified by the target device identifier, using the unique information acquired in step S318.
[0089] (Step S320) The information acquisition unit 135 acquires business information paired with the target device identifier. The information acquisition unit 135 acquires the business information from the storage unit 11, for example.
[0090] (Step S321) The restoration unit 136 performs a restoration process using the business information acquired in step S320 on the object device 2 identified by the object device identifier. Return to step S301.
[0091] In the flowchart of Fig. 3, backups are performed at once for all of the target devices 2 constituting the information system A. However, in the flowchart of Fig. 3, backups may be performed only for some of the target devices 2 constituting the information system A.
[0092] In the flowchart of FIG. 3, the process ends when the power is turned off or an interrupt occurs to end the process.
[0093] A specific example of the operation of the backup device 1 constituting the information system A in this embodiment will be described below.
[0094] The common definition management unit 111 of the backup device 1 stores a common definition management table shown in FIG. 4. The common definition management table is a table that manages common definition information for each type identifier. The common definition management table manages records that have an "ID," "type identifier," and "common definition information." The "ID" is information that identifies the record. The "type identifier" is information that identifies the OS of the target device 2 in this case. The "common definition information" is a collection of folder names that make up the common information.
[0095] The unique definition management unit 112 stores a unique definition management table shown in Fig. 5. The unique definition management table is a table that manages unique definition information for each target device 2. The unique definition management table manages records that have an "ID," "type identifier," "target device identifier," and "unique definition information." The "target device identifier" is an IP address here. The "unique definition information" is a collection of folder names that make up the unique information here.
[0096] The task definition management unit 113 stores a task definition management table shown in Fig. 6. The task definition management table is a table that manages task definition information for each target device 2. The task definition management table manages records that have an "ID," "type identifier," "target device identifier," and "task definition information." In this case, these are IP addresses. "Task definition information" is a collection of folder names that make up the task information.
[0097] In this situation, it is assumed that the processing unit 13 judges that it is time to perform a backup.
[0098] Next, the common information acquisition unit 131 acquires common definition information for each type identifier, and based on the common definition information, acquires information that is the source of the common information from any of the target devices 2 corresponding to the type identifier (information of two or more folders indicated by the common definition information), and acquires common information that is an image file of the information. Note that the common information acquisition unit 131 acquires a target device identifier (IP address) that pairs with the type identifier from the unique definition management table, and uses the target device identifier to access the target device 2 and acquire the information that is the source of the common information from the target device 2.
[0099] Next, the accumulation unit 134 accumulates the acquired common information in the storage unit 11 for each of the two or more type identifiers in association with the type identifier.
[0100] Furthermore, the unique information acquisition unit 132 acquires unique definition information paired with the target device identifier from the unique definition management table for each of the two or more type identifiers and for each target device identifier. Next, the unique information acquisition unit 132 accesses each target device 2 using the target device identifier (IP address) and acquires information (here, a folder) of a storage area specified by the unique definition information paired with each target device identifier from each target device 2. The unique information acquisition unit 132 acquires unique information, which is IaC data, using the acquired information. The accumulation unit 134 accumulates the unique information in the storage unit 11, paired with the target device identifier for each target device identifier.
[0101] Next, the business information acquisition unit 133 acquires business definition information paired with the target device identifier from the business definition management table for each of the two or more type identifiers and for each target device identifier. Next, the business information acquisition unit 133 accesses each target device 2 using the target device identifier (IP address) and acquires information (here, folders) of the storage area specified by the business definition information paired with each target device identifier from each target device 2. The business information acquisition unit 133 uses the acquired information to acquire business information (for example, a compressed file with a password assigned to each folder). The accumulation unit 134 accumulates the business information in the storage unit 11 paired with the target device identifier for each target device identifier.
[0102] Through the above processing, backup of each of the two or more target devices 2 is completed.
[0103] Next, suppose that the target device 2 identified by the target device identifier "IP address 11" crashes due to a disaster or the like. Then, suppose that the user inputs a restore instruction including "IP address 11" to the backup device 1.
[0104] Next, the restoration reception unit 121 receives the restoration instruction. Next, the information acquisition unit 135 acquires the target device identifier "IP address 11" corresponding to the restoration instruction. Next, the information acquisition unit 135 acquires the type identifier "OS1" that is paired with the target device identifier "IP address 11" from the unique definition management table, and acquires the common information that is paired with the type identifier "OS1" from the storage unit 11.
[0105] Next, the restoration unit 136 accesses the target device 2 identified by the target device identifier "IP address 11" and performs restoration processing using the acquired common information. Through the above processing, the OS of the target device 2 identified by the target device identifier "IP address 11" is reinstalled.
[0106] Next, the information acquisition unit 135 acquires unique information paired with the target device identifier "IP address 11" from the storage unit 11. Next, the restoration unit 136 accesses the target device 2 using the target device identifier "IP address 11" and performs restoration processing on the target device 2 using the acquired unique information. Through the above processing, the target device 2 identified by the target device identifier "IP address 11" is placed in a state where applications that were previously installed are reinstalled.
[0107] Next, the information acquisition unit 135 acquires the business information paired with the target device identifier "IP address 11" from the storage unit 11. Next, the restoration unit 136 accesses the target device 2 using the target device identifier "IP address 11" and performs restoration processing using the acquired business information. Through the above processing, previously existing user-created folders and files are stored in the target device 2 identified by the target device identifier "IP address 11".
[0108] By the above-described processing of this specific example, the target device 2 corresponding to the restoration instruction has been restored.
[0109] As described above, according to this embodiment, a plurality of target devices 2 can be efficiently backed up.
[0110] Furthermore, according to this embodiment, the target device 2 can be restored using the backed up information.
[0111] The process in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software for realizing the backup device 1 in this embodiment is a program as follows. That is, this program is a program for making a computer function as an inherent information acquisition unit that acquires inherent information inherent to each of two or more target devices in association with each target device, a business information acquisition unit that acquires business information stored in the target devices in association with each target device from each of the two or more target devices, and a storage unit that stores two or more inherent information for each of the target devices and business information for each of the target devices in association with common information common to each of the two or more target devices.
[0112] 7 shows the appearance of a computer that executes the programs described in this specification to realize the backup device 1 and the like of the various embodiments described above. The above-mentioned embodiments can be realized by computer hardware and a computer program executed thereon. FIG. 7 is an overview of this computer system 300, and FIG. 8 is a block diagram of the system 300.
[0113] In FIG. 7, computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.
[0114] 8, computer 301 includes, in addition to CD-ROM drive 3012, MPU 3013, bus 3014 connected to CD-ROM drive 3012 etc., ROM 3015 for storing programs such as a boot-up program, RAM 3016 connected to MPU 3013 for temporarily storing instructions of application programs and providing temporary storage space, and hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.
[0115] A program for causing computer system 300 to execute functions such as those of backup device 1 of the above-mentioned embodiment may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and then transferred to hard disk 3017. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 when executed. The program may also be loaded directly from CD-ROM 3101 or the network.
[0116] The program does not necessarily include an operating system (OS) or a third party program that causes the computer 301 to execute the functions of the backup device 1 of the above-mentioned embodiment. The program only needs to include an instruction portion that calls appropriate functions (modules) in a controlled manner to obtain a desired result. How the computer system 300 operates is well known, and a detailed description will be omitted.
[0117] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmitting step (processing that is performed only by hardware).
[0118] The program may be executed by a single computer or a plurality of computers, that is, centralized processing or distributed processing may be performed.
[0119] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.
[0120] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.
[0121] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]
[0122] As described above, the backup device 1 according to the present invention has the effect of being able to efficiently back up a plurality of target devices, and is useful as a backup server or the like. [Explanation of symbols]
[0123] 1 Backup device 2. Target device 11 Storage area 12 Reception 13 Processing section 14 Output section 111 Common definition management department 112 Unique definition management section 113 Business definition management department 121 Restoration Reception Department 131 Common information acquisition unit 132 Unique information acquisition unit 133 Business Information Acquisition Department 134 Storage Unit 135 Information Acquisition Department 136 Restoration Department
Claims
1. a common information acquisition unit that acquires common information common to each of two or more target devices; a unique information acquisition unit that acquires unique information unique to each of the two or more target devices from each of the two or more target devices in association with each of the target devices; each of the two or more target devices is associated with an attribute value; The common information acquisition unit A backup device that acquires common information from the target devices for each different attribute value.
2. a business information acquisition unit that acquires, from each of the two or more target devices, business information stored in the target device in association with each target device; 2. The backup device according to claim 1, further comprising a storage unit that stores two or more pieces of unique information for each of the two or more target devices and business information for each of the two or more target devices in association with common information common to each of the two or more target devices.
3. a restoration receiving unit that receives a restoration instruction including a target device identifier; an information acquisition unit that acquires the common information, the unique information, and the business information corresponding to the target device identifier; 4. The backup device according to claim 1, further comprising a restoration unit that performs restoration using the common information, the specific information, and the business information acquired by the information acquisition unit.
4. a common definition management unit in which common definition information for identifying the common information is stored; The common information acquisition unit 4. The backup device according to claim 2, wherein the common information based on information specified by the common definition information is acquired from at least one of the two or more target devices or from another target device.
5. a unique definition management unit for storing unique definition information, which is information corresponding to each of the two or more target devices and is information for identifying unique information; The unique information acquisition unit 2. The backup device according to claim 1, further comprising: acquiring, from each of said two or more target devices, unique information based on information specified by said unique definition information corresponding to each target device, in association with each target device.
6. a task definition management unit for storing task definition information, which is information corresponding to each of the two or more target devices and is information for identifying task information; The business information acquisition unit, 2. The backup device according to claim 1, further comprising: acquiring, from each of said two or more target devices, task information based on information specified by said task definition information associated with each target device, in association with each target device.
7. A backup method using a backup device, the backup method being realized by a common information acquisition unit and a unique information acquisition unit, a common information acquisition step in which the common information acquisition unit acquires common information common to two or more target devices; the unique information acquisition unit acquires unique information unique to each of the two or more target devices from each of the two or more target devices in association with each target device; each of the two or more target devices is associated with an attribute value; In the common information acquisition step, A backup method for acquiring common information from target devices for each different attribute value.
8. Computer, a common information acquisition unit that acquires common information common to each of two or more target devices; a program for causing the program to function as a unique information acquisition unit that acquires unique information unique to each of the two or more target devices in association with each of the two or more target devices, each of the two or more target devices is associated with an attribute value; The common information acquisition unit A program for causing the computer to function as acquiring common information from the target device for each different attribute value.
Citation Information
Patent Citations
Backup system
JP2011060023A
