JP5387827B2 - Network management device, network management system, network management method, and program - Google Patents

Description

  The present invention relates to a network management device that manages a plurality of terminal devices connected to a network, a terminal device to be managed, a network management system including these, a network management method, and a program that causes a computer to execute network management. .

  In recent years, due to the rapid progress and popularization of networks, network management is extremely important in organizations such as companies, government offices, and various organizations. For this reason, the burden on the network administrator is also increasing. For this reason, various techniques have been developed to reduce the burden on the network administrator (see, for example, Patent Document 1 and Patent Document 2).

  For example, Patent Document 1 proposes a technique for reducing the burden on an administrator when collecting setting information from a device such as a client computer constituting a network and creating a backup file. Specifically, in the technique disclosed in Patent Document 1, setting information of each device is automatically collected. For this reason, the burden on the administrator is greatly reduced. In addition, the operation state of each device is monitored, and a backup file is created only when the operation state is constant. As a result, the setting information is converted after the backup file is created, and the occurrence of a situation in which the administrator is forced to collect again is avoided.

  Patent Document 2 proposes a technique for reducing the burden on an administrator when a driver of a device device such as a printer existing on a network is incorporated in a client computer. Specifically, in the technique disclosed in Patent Document 2, first, a device apparatus is automatically selected and further selected from a network according to an administrator policy (for example, a device that is in the vicinity, most frequently used, etc.). The driver of the selected device is selected. Further, the selected driver is then installed on the client computer.

JP 2000-90028 (page 3-4, FIG. 1) Japanese Patent Laying-Open No. 2005-258895 (page 5-7, FIG. 1)

  However, even when network management is performed using the techniques disclosed in Patent Document 1 and Patent Document 2, there are the following problems. For this reason, it is thought that the burden on the manager is large as before.

  The first problem is that the burden on the administrator is not reduced when a new client computer is introduced or when an OS or the like is reinstalled on a client computer that has lost backup data. . In this case, the administrator has to examine the introduction method such as which software needs to be installed in the organization and which setting items are necessary, and it can be said that the burden is large.

The second problem is that, especially in the case of an organization / project composed of a small number of members, preparation of guidelines and setting procedures describing the introduction method tends to be insufficient. This is because, especially in an environment where only a few people or only one computer is used, the network may be managed by relying on memory or verbal confirmation, which may result in loss of procedures and know-how.

  The third problem is that it is very difficult to generalize and introduce guidelines for new computers due to the diversification of software, the increase in the frequency of updating security software, the increase in the number of patch applications, etc. Is a point. This is because the procedure must be updated each time patches and setting items increase, and it is difficult to cover even a minor environment as in the second problem.

  An object of the present invention is to provide a network management device, a terminal device, a network management system, a network management method, and a program that can solve the above problems, promote automation in network management, and reduce the burden on the administrator. It is to provide.

In order to achieve the above object, a network management device according to the present invention is a network management device for managing a plurality of terminal devices connected by a network,
A data acquisition unit, a backup unit, and a restore unit;
The data acquisition unit acquires backup data and attributes of the terminal device from each of the plurality of terminal devices,
For each backup data acquired from each of the plurality of terminal devices, the backup unit obtains a corresponding attribute type, sets a counter for each type of attribute obtained, and sets the value of each counter to 1,
Furthermore, when the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data The value is the number of terminal devices having the common attribute,
Then, for each attribute, find the number of terminal devices having the attribute,
The restore unit, when an attribute is designated from the outside, uses the counter value for each attribute type of each backup data and the number of the terminal devices in each attribute to store the backup data. To select data related to the specified attribute to generate data for restore,
It is characterized by that.

In order to achieve the above object, a terminal device in the present invention is a terminal device connectable to a network,
A data backup unit that outputs the attribute of the terminal device and backup data to the device on the network is provided.

In order to achieve the above object, a network management system according to the present invention is a network management system comprising a plurality of terminal devices connected by a network, and a network management device for managing these,
The terminal device includes a data backup unit that outputs the attribute of the terminal device and backup data to the network management device, and the network management device includes a data acquisition unit, a backup unit, and a restore unit. ,
The data acquisition unit acquires backup data and attributes of the terminal device from each of the plurality of terminal devices,
For each backup data acquired from each of the plurality of terminal devices, the backup unit obtains a corresponding attribute type, sets a counter for each type of attribute obtained, and sets the value of each counter to 1,
Furthermore, when the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data Set the value to the number of terminal devices having the common attribute,
Then, for each attribute, find the number of terminal devices having the attribute,
The restore unit, when an attribute is designated from the outside, uses the counter value for each attribute type of each backup data and the number of the terminal devices in each attribute to store the backup data. To select data related to the specified attribute to generate data for restore,
It is characterized by that.

In order to achieve the above object, a network management method according to the present invention is a network management method for managing a plurality of terminal devices connected by a network,
(A) obtaining backup data and attributes of the terminal device from each of the plurality of terminal devices;
(B) For each backup data acquired from each of the plurality of terminal devices, a corresponding attribute type is obtained, a counter is set for each obtained attribute type, and the value of each counter is set to 1.
(C) When the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data The value of the number of terminal devices having the common attribute, and
(D) For each attribute, obtaining the number of terminal devices having the attribute;
(E) When an attribute is designated from the outside, the counter value for each attribute type of each backup data obtained in the step (b) or (c) and the step (d) Selecting the data related to the specified attribute from the backup data using the obtained number of the terminal devices in each attribute, and generating data for restoration; and It is characterized by having.

In order to achieve the above object, a program in the present invention is a program for causing a computer to manage a plurality of terminal devices connected by a network,
In the computer,
(A) obtaining backup data and attributes of the terminal device from each of the plurality of terminal devices;
(B) For each backup data acquired from each of the plurality of terminal devices, a corresponding attribute type is obtained, a counter is set for each obtained attribute type, and the value of each counter is set to 1.
(C) When the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data The value of the number of terminal devices having the common attribute, and
(D) For each attribute, obtaining the number of terminal devices having the attribute;
(E) When an attribute is designated from the outside, the counter value for each attribute type of each backup data obtained in the step (b) or (c) and the step (d) And using the obtained number of the terminal devices in each attribute to select data related to the specified attribute from the backup data and generate data for restoration. It is characterized by making it.

  With the above features, according to the network management device, terminal device, network management system, network management method, and program of the present invention, it is possible to promote automation in network management and reduce the burden on the administrator. Become.

FIG. 1 is an explanatory diagram for explaining the basic operation of the network management apparatus according to the present invention. FIG. 2 is a block diagram showing a schematic configuration of the network management device, the terminal device, and the network management system in the embodiment of the present invention. FIG. 3 is a diagram showing an example of attribute information used in the embodiment of the present invention. FIG. 4 is a diagram showing an example of backup data and catalog information used in the embodiment of the present invention. FIG. 5A shows backup data stored in the storage unit of the network management apparatus, and FIG. 5B shows catalog information stored in the storage unit of the network management apparatus. . FIG. 6 is a diagram illustrating an example of related information stored in the storage unit of the network management apparatus. FIG. 7 is a diagram illustrating an example of relationship information for specifying a relationship between a client attribute and the number of clients. FIG. 8 is a flowchart showing attribute setting processing by the client in this embodiment. FIG. 9 is a flowchart showing backup instruction processing by the backup instruction device. FIG. 10 is a flowchart showing data acquisition processing in the network management apparatus according to the present embodiment. FIG. 11 is a flowchart showing data transmission processing by the client in this embodiment. FIG. 12 is a flowchart showing the entire backup processing by the network management apparatus according to this embodiment. FIG. 13 is a flowchart showing processing for acquiring and storing bank update data and catalog information shown in FIG. FIG. 14 is a flowchart showing the attribute information acquisition / storage process and the client number counter setting process shown in FIG. FIG. 15 is a flowchart showing the relation information acquisition / storage process and the relation counter setting process shown in FIG. FIG. 16 is a flowchart showing a restore process by the network management apparatus in the present embodiment. FIG. 17 is a flowchart showing restore processing by the client in this embodiment.

(Description of basic operation)
First, a basic operation of network management performed in the present invention will be described with reference to FIG. FIG. 1 is an explanatory diagram for explaining the basic operation of the network management apparatus according to the present invention. The network management device according to the present invention manages a plurality of terminal devices (hereinafter referred to as “clients”) connected by a network. FIG. 1 shows an example in which the number of clients is three. The clients are referred to as “client 1”, “client 2”, and “client 3”, respectively.

As shown in FIG. 1, the clients 1 to 3 each have one of attribute A, attribute B, and attribute C. The attribute here is information that identifies the client characteristics such as the organization or department to which the client belongs, the installation location, the user, the purpose of use, the installed software, the usable device device, and the like. In the example of FIG. 1, only the client 1 has the attribute A, the attribute B has the client 1 and the client 2, and the attribute C has the client 2 and the client 3.

  As shown in FIG. 1, the clients 1 to 3 are backed up by a network management device that functions as a backup device. Specifically, file X, file Y, and setting Z in each client are backed up. Here, the file X is backed up from the client 1. The file Y is backed up from the client 1 and the client 2. Further, the setting Z is backed up from the client 2 and the client 3.

  In the present invention, the network management apparatus automatically extracts a policy in the network environment from the backed up backup data (files X, Y, setting Z) and the attributes of each client. Then, when a new client is introduced or the OS is reinstalled on the client, the network management device automatically restores data to be restored from the attributes of the target client and the extracted policy. select.

  Specifically, as shown in FIG. 1, first, the network management apparatus receives the attributes (attribute A, attribute B, attribute C) and backup data (file X, file Y, setting Z) from each client. And get. At this time, the network management apparatus also acquires catalog information for specifying the contents of the backup data. The catalog information will be described later.

  Next, the network management apparatus enumerates the attributes of the backup source client of the backup data and obtains the number of each attribute type for each backup data. Specifically, the network management device obtains a corresponding attribute type for each backup data acquired from each terminal device. Then, the network management apparatus sets a counter (hereinafter referred to as “related counter”) for each attribute type in each backup data, and sets the value of each counter to 1. For example, the file X is backed up from the client 1, and when the corresponding attributes are enumerated, the attribute A is one and the attribute B is one. Therefore, the value of the relation counter of the attribute A of the file X and the value of the relation counter of the attribute B of the file X are each “1”.

  At this time, the network management apparatus determines whether or not the same backup data is acquired from two or more clients, and further determines whether or not a common attribute exists in the two or more terminal apparatuses. Whether or not the backup data is the same is determined using catalog information as will be described later.

  For example, in the example of FIG. 1, the file Y is acquired from the clients 1 and 2, and a common attribute B exists for them. The setting Z is acquired from the clients 2 and 3, and a common attribute C exists for them. Therefore, the network management apparatus sets the counter value of the common attribute in each backup data as the number of terminal apparatuses having the common attribute. That is, the value of the relation counter of the attribute B of the file Y is “2”, and similarly, the value of the relation counter of the attribute C of the setting Z is also “2”.

  Further, the network management device also obtains the number of clients having the attribute for each attribute. In the example of FIG. 1, the number of clients having attribute A is one, the number of clients having attribute B is two, and the number of clients having attribute C is two.

Here, the strength of the relationship between each backup data and the attribute is considered. For example, assume that the value of the relation counter of any attribute of each backup data is N2, and the number of clients having any attribute is N1. Then, the strength of the relationship between each backup data and attribute is N
2 can be expressed by a value obtained by dividing N by N1 (the value of the relation counter N2 of an arbitrary attribute of backup data / the number N1 of clients having an arbitrary attribute). This value is hereinafter referred to as “relevance”. In the example of FIG. 1, when the backup data is a file X, the relevance level of the attribute A to the file X is 1, and the relevance level of the attribute B to the file X is 0.5. This indicates that in the file X, the association with the attribute A is higher than the association with the attribute B.

  For this reason, the network-related device uses the number of attributes for each type of backup data and the number of clients for each attribute when restoration is required for new installation or reinstallation. You can select highly relevant data. Then, the network-related device executes restoration using the restore data obtained in this way. As a result, the burden on the administrator in the restore operation is greatly reduced. Further, the administrator can know what kind of organization or business is used for the restored client by the attribute associated with the software or setting.

(Embodiment)
Hereinafter, a network management device, a terminal device, a network management system, a network management method, and a program according to an embodiment of the present invention will be described with reference to FIGS. First, the configuration of a network management device, a terminal device, and a network management system using these will be described with reference to FIG. FIG. 2 is a block diagram showing a schematic configuration of the network management device, the terminal device, and the network management system in the embodiment of the present invention. In the following description, FIG. 1 is referred to as appropriate.

  As shown in FIG. 2, the network management system 10 includes a plurality of clients 20-1 to 20-n (n is an arbitrary natural number) connected to the network 11, and a network management apparatus 101 that manages these clients. Yes. In the present embodiment, the clients (terminal devices) 20-1 to 20-n are computers to be backed up or restored (restored).

  Each of the clients 20-1 to 20-n includes a data backup unit 21. The data backup unit 21 of each client outputs the attribute of each client, the backup data of each client, and catalog information for specifying the contents of this backup data to the network management apparatus 101.

  The network management apparatus 101 also includes a data acquisition unit 114, a storage unit 115 that stores various types of information, and a restoration unit 116. The data acquisition unit 114 acquires the attributes of each client and the backup data of each client from each of the clients 20-1 to 20-n.

  First, the backup unit 114 obtains the corresponding attribute type for each backup data acquired from each of the clients 20-1 to 20-n, sets a counter for each obtained attribute type, and sets the value of each counter. Set to 1. Further, the backup unit 114 determines whether or not the same backup data is acquired from two or more terminal devices.

  If acquired, the backup unit 114 also determines whether there are attributes common to two or more terminal devices. Further, when there is a common attribute, the backup unit 114 sets the value of the relation counter of the common attribute of the backup data determined to be the same as the number of terminal devices having the common attribute.

For each attribute acquired from the clients 20-1 to 20-n, the backup unit 114 also obtains the number of clients having the attribute, that is, the number of clients for each attribute. Note that the value of the relation counter set by the backup unit 114 and the number of clients obtained by the backup unit are stored in the storage unit 115.

  The restoration unit 116 first receives an external attribute designation. Then, the restoration unit 116 selects data related to the specified attribute from the backup data using the value of the relation counter for each attribute type of each backup data and the number of clients for each attribute. Generate data for restore.

  As described above, the network management apparatus 101 can automatically generate data for restoration, and promotes automation in network management. As a result, the burden on the administrator of the network 11 can be reduced.

  Here, the network management system in the present embodiment will be described more specifically with reference to FIGS. 3 to 7 in addition to FIG. FIG. 3 is a diagram showing an example of attribute information used in the embodiment of the present invention. FIG. 4 is a diagram showing an example of backup data and catalog information used in the embodiment of the present invention. FIG. 5A shows backup data stored in the storage unit of the network management apparatus, and FIG. 5B shows catalog information stored in the storage unit of the network management apparatus. . FIG. 6 is a diagram illustrating an example of related information stored in the storage unit of the network management apparatus. FIG. 7 is a diagram illustrating an example of relationship information for specifying a relationship between a client attribute and the number of clients.

  As shown in FIG. 2, in this embodiment, the clients 20-1 to 20-n include a data restore unit 22, an attribute transmission unit 23, an attribute setting unit 24, and a storage unit in addition to the data backup unit 21. 25.

  In each of the clients 20-1 to 20-n to be backed up, first, attribute information is acquired prior to backup by the network management apparatus 101. Specifically, the attribute setting unit 24 acquires attribute information from information manually input by the user when the client is introduced, hardware information registered in each client, and installed applications. .

As the attribute information, as shown in the example of FIG. 3, the organization to which the client belongs, the department, the installation location, the user, the work in charge, the hardware information of the client, the name of the installed application software, and the usable device Etc. Further, the attribute setting unit 24 stores the acquired attribute information in the storage area of the storage unit 25 and sets the attribute for the client. In FIG. 2 , reference numeral 27 denotes attribute information (client attribute information) stored in the storage unit 25.

  In each client, the data backup unit 21 transmits data based on a request from the backup data acquisition unit 108 of the network management apparatus 101. In the present embodiment, the data transmitted by the data backup unit 21 is backup data and catalog information for specifying (identifying) the contents. An example of catalog information will be described later.

  Further, in each client, the attribute transmission unit 23 reads the attribute information of each client from the storage unit 25 based on a request from the backup data acquisition unit 108 of the network management apparatus, and transmits this to the backup data acquisition unit 108. To do.

When data for restoration is transmitted from the network management apparatus 101, the data restoration unit 22 receives the data and stores it in the storage unit 25. Data for restoration is stored in the storage unit 2
When the data is stored in the client 5, restoration at the client is executed.

  As shown in FIG. 2, in the present embodiment, a backup instruction device 100 is connected to the network management device 101. The backup instruction apparatus 100 issues a backup instruction to the network management apparatus 101 in accordance with a set schedule or based on a backup instruction instructed by a user.

  In the present embodiment, upon receiving an instruction from the backup instruction apparatus 100, the network management apparatus 101 performs management of backup processing, storage of backup data, and restoration processing. Specific examples of the backup instruction device 100 include an administrator's terminal device and a server device that manages the entire network.

  As shown in FIG. 2, in the present embodiment, in the network management apparatus 101, the backup unit 114 includes a backup data storage unit 109, a relationship information addition unit 110, and an attribute collection unit 111. In addition, the storage unit 115 stores backup data 102, catalog information 103, attribute information 104, and relationship information 105 in the storage area. Further, the restore unit 116 includes a restore command reception unit 106, a restore attribute reception unit 107, a restore target selection unit 112, and a restore data transmission unit 113. The operation of each part of these network management apparatuses 101 will be described below.

  First, the operation of each unit of the network management apparatus 101 at the time of backup will be described. When an instruction is issued from the backup instruction device 100, the backup data acquisition unit 108 performs backup of each of the clients 20-1 to 20-n. In the present embodiment, the backup data acquisition unit 108 receives backup data and catalog information for identifying the backup data via the data backup unit 21 of each client. Further, the backup data acquisition unit 108 also acquires attribute information of each of the clients 20-1 to 20-n via the attribute transmission unit 24 of each client 20-1.

  An example of the acquired backup data and catalog information is shown in FIG. As shown in FIG. 4, in the present embodiment, the backup data includes a file in which data contents are described and setting information. The setting information is client information stored in a registry or the like. The catalog information includes information specifying the location of backup information and backup data. The backup information includes the type of backup data, path name or setting file / setting item (= setting value), creation (or update) date, size of backup data, and the like. Information identifying the location of the backup data includes client names “40-1 to 40-n”.

  Further, the backup data acquisition unit 108 sends the acquired (received) backup data and catalog information to the backup data storage unit 109, and sends the acquired (received) attribute information to the relationship information adding unit 110. The backup data acquisition unit 108 executes such processing for backup data and catalog information for the clients 20-1 to 20-n to be backed up. The backup data acquisition unit 108 also acquires all the attributes of each client transmitted from the attribute transmission units 24 of the clients 20-1 to 20-n. The acquired attribute is sent to the attribute collection unit 111 as attribute information.

  As shown in FIGS. 5A and 5B, the backup data storage unit 109 stores the backup data and catalog information sent from the backup data acquisition unit 108 in the storage unit 115. Reference numeral 102 denotes backup data stored in the storage unit 115, and reference numeral 103 denotes catalog information stored in the storage unit 115.

  The backup data storage unit 109 assigns a unique data ID to the stored catalog information. Furthermore, at this time, the backup data storage unit 109 compares the newly stored backup data with the already stored backup data in terms of file contents, setting information, and backup information using the respective catalog information. And determine whether they are the same. That is, the backup data storage unit 109 determines whether a newly stored backup data file has already been stored.

  When the same file is stored, the backup data storage unit 109 assigns the same data ID as the already stored backup data to the newly stored backup data. The catalog information is stored in the storage unit 115 after the data ID is determined. The determined data ID is sent to the relationship information adding unit 110.

  The relationship information adding unit 110 uses the attribute information received from the backup data acquisition unit 108 to obtain a corresponding attribute type for each backup data, and sets a counter (relation counter) for each obtained attribute type. The value of each counter is set to 1. Further, the relationship information adding unit 110 creates the relationship information shown in FIG. 6 by combining the attribute information, the data ID received from the backup data storage unit 109, and the relationship counter, and stores the relationship information in the storage unit 115. . Reference numeral 105 denotes relationship information stored in the storage unit 115.

  Further, the relationship information adding unit 110 compares the newly stored related information with the already stored related information, and determines whether the attribute information and the data ID of both are common. If the result of determination is common, instead of newly storing related information, the value of the relation counter of the related information already stored is incremented by one. By performing such processing, the value of the relation counter of the common attribute of the backup data determined to be the same is equal to the number of clients having the common attribute.

  The attribute collection unit 111 stores the client attribute information received from the backup data acquisition unit 108 in the storage unit 115. Reference numeral 104 denotes attribute information stored in the storage unit 115.

  Then, the attribute collection unit 111 determines whether the attribute specified by the attribute information is already stored in the storage unit 115. As a result of the determination, if the target attribute is not yet stored, a counter is set and its value is set to 1. On the other hand, if the target attribute is already stored as a result of the determination, the value of the counter already set for the attribute is incremented by one. As a result, the counter is set for each attribute, and the value indicates the number of clients for each attribute in all backup data. This counter is hereinafter referred to as “client number counter”.

  Here, a value (relation counter / client number counter) obtained by dividing the value of the relation counter by the value of the client number counter will be considered. Thus, the value obtained by the division can be considered to indicate the degree of association (relevance) between each backup data and the attribute for each backup data. Therefore, when the degree of association between backup data and an attribute is 1.0, the backup data always exists on a client having the attribute.

Next, the operation of each unit of the network management apparatus 101 at the time of restoration will be described. When restoring a client or introducing a new client, the user instructs the restore unit to restore using an input device or another computer. In this case, the restore command receiving unit 106 receives the restore command and issues a restore command for the computer to be restored.

  In this case, the user can specify, as a computer to be restored, a client that has already been backed up, a client that has lost backup data, or a new computer that has not been backed up.

  In addition, the restore attribute receiving unit 107 receives an input of an attribute designated by the user, and transmits the received attribute to the restore target selecting unit 112. At this time, the restore target selection unit 112 can acquire a list of attributes from the attribute information 104 stored in the storage unit 115 and display the list of attributes on a display screen of a display device (not shown). In this case, the user can select an attribute to be given to the computer to be restored from the list of attributes displayed on the display screen. In the following description, the computer to be restored is referred to as “client X”.

  When receiving the restore command received by the restore command receiving unit 106 and the attribute received by the restore attribute receiving unit 107, the restore target selection unit 112 executes selection of backup data to be restored.

  In the present embodiment, first, the restore target selection unit 112 accesses the attribute information 104 stored in the storage unit 115 and searches for the number of clients having the attributes received by the restore attribute reception unit 107. Further, the restore target selection unit 112 also accesses the relationship information 105 stored in the storage unit 115 and acquires a list of relationship information corresponding to the specified attribute.

  Then, the restoration target selection unit 112 specifies the number of clients (client number counter) N1 having the designated attribute and the value N2 of the relationship counter having the same attribute as the designated attribute in each backup data. Then, the restore target selection unit 112 calculates the degree of association between each backup data and the specified attribute by dividing N2 by N1.

  Subsequently, the restoration target selection unit 112 determines whether or not the division value (N2 / N1) is equal to or greater than the set threshold value, and selects backup data corresponding to N2 when the threshold value is equal to or greater than the threshold value. Then, it is extracted and used as data to be restored. Then, the restore target selection unit 112 identifies the data IDs included in the related information of the extracted backup data, creates a list thereof, and inputs it to the restore data transmission unit 113.

  The restore data transmission unit 113 searches the backup data 102 and catalog information 103 stored in the storage unit 115 based on the input data ID list, and extracts data to be transmitted to the client X. Thereafter, the data restore unit 22 of the client X receives the data transmitted from the restore data transmission unit 113 and stores it in the storage unit 25. Thereby, the restoration at the client X is completed.

  Next, operations of the network management device, the client, and the network management system according to the embodiment of the present invention will be described with reference to FIGS. In the present embodiment, the network management method can be executed by operating the network management apparatus 101. For this reason, the description of the network management method is replaced with the description of the operation of the network management apparatus 101 below. Moreover, in the following description, FIGS. 1-7 is referred suitably.

First, prior to backup, installation setting processing (attribute setting processing) is performed in each client. FIG. 8 is a flowchart showing attribute setting processing by the client in this embodiment. In the attribute setting process, attributes are set by the attribute setting unit 24 for the clients 20-1 to 2-0-n (see FIG. 2) to be backed up. That is, what attributes each client has is set.

  As shown in FIG. 8, the attribute setting unit 24 accesses the storage unit 25, and first acquires the software name, patch name, and device name installed in the system (step S801). Next, the attribute setting unit 24 sets the acquired names as attribute names, and stores these names as client attribute information in the storage unit 25 (step S802).

  Next, the attribute setting unit 24 determines whether all software names, patch names, and device names have been acquired (step S803). If all the software names, patch names, and device names on the client are acquired as a result of the determination in step S803, steps S801 and S802 are executed again.

  On the other hand, if all the attributes are acquired as a result of the determination in step S803, the attribute setting unit 24 determines whether an attribute is input from the user (step S804). If there is no input as a result of the determination in step S804, the attribute setting unit 24 ends the process.

  On the other hand, if an input is made as a result of step S804, the attribute setting unit 24 accepts the input (step S805), and further stores the input attribute in the storage unit 25 as attribute information (step S806). ). Steps S805 and S806 are executed until all the inputs from the user are completed (804). The attribute information shown in FIG. 3 is stored in the storage unit 25 through steps S801 to S806.

  Next, processing by the backup instruction apparatus 100 will be described with reference to FIG. FIG. 9 is a flowchart showing backup instruction processing by the backup instruction device. As shown in FIG. 9, first, the backup instruction apparatus 100 selects a client that has not been backed up, and issues a backup instruction to the backup data acquisition unit 108 (step S901). In the present embodiment, step S901 is performed according to a set schedule or based on an instruction from the user.

  Next, the backup instruction apparatus 100 determines whether a backup instruction has been issued to all clients (step S902). If the result of determination in step S <b> 902 is that a backup instruction has been issued for all clients, the backup instruction apparatus 100 ends the process.

  On the other hand, if the result of determination in step S902 is that backup instructions have not been issued for all clients, the backup instruction apparatus 100 executes step S901 again and issues backup instructions for clients that have not yet been backed up. To do. By executing Steps S901 and S902, the network management apparatus 101 executes backup for the client.

  Here, assuming that the client instructed to backup is “client X”, processing in the network management apparatus will be described below. FIG. 10 is a flowchart showing data acquisition processing in the network management apparatus according to the present embodiment.

  As shown in FIG. 10, the backup data acquisition unit 108 that has received the backup instruction first makes a data transmission request to the data backup unit 21 of the client X to be backed up (step S903).

  Next, when the data backup unit 21 transmits backup data and catalog information, the backup data acquisition unit 108 receives the backup data and catalog information (step S904). Next, the backup data acquisition unit 108 sends the received backup data and catalog information to the backup data storage unit 109 (step S905).

  Next, the backup data acquisition unit 108 makes a transmission request for attribute information to the attribute transmission unit 24 of the client X (step S906). Next, when the attribute transmission unit 24 transmits the attribute information of the client X, the attribute information is received (step S907). Next, the backup data acquisition unit 108 sends the received attribute information to the relationship information addition unit 110 and the attribute collection unit 111 (step S908), and ends the process. In the present embodiment, steps S903 to S905 and steps S906 to S908 may be performed simultaneously, or the execution order may be switched.

  Further, as shown in FIG. 10, when the network management apparatus performs the data acquisition process, the target client X executes the process shown in FIG. FIG. 11 is a flowchart showing data transmission processing by the client in this embodiment.

  As shown in FIG. 11, first, the data backup unit 21 of the client X takes out the client backup data 26 from the storage unit 25 based on a request from the backup data acquisition unit 108 (see FIG. 10: step S903), and Catalog information is created (step S920).

  Next, the data backup unit 21 transmits the backup data and catalog information obtained in step S921 to the backup data acquisition unit 108 (step S921). Examples of backup data and catalog information are shown in FIG.

  Subsequently, the attribute transmission unit 24 of the client X extracts the client attribute information 27 from the storage unit 25 based on a request from the backup data acquisition unit 108 (see FIG. 10: step S906) (step S930). Then, the attribute transmission unit 24 transmits the attribute information extracted in step S930 to the backup data acquisition unit 108 (step S931).

  When the backup data, catalog information, and attribute information are acquired, the network management device executes backup processing. FIG. 12 is a flowchart showing the entire backup processing by the network management apparatus according to this embodiment.

  As shown in FIG. 12, first, the backup unit 114 acquires backup data and catalog information from the backup data acquisition unit 108, and stores them in the storage unit 115 (step S201). Step S201 is processing corresponding to step S921 shown in FIG. In step S201, the catalog information is given a data ID.

  Next, the backup unit 114 acquires attribute information from the backup data acquisition unit 108 and stores it in the storage unit 115 (step S202). Step S203 is processing corresponding to step S931 shown in FIG. Subsequently, the backup unit 114 sets a client number counter, and inputs a value to the client number counter based on the attribute information (step S203).

Next, the backup unit 114 checks the identity of the backup data stored in the storage unit 115 and the attribute of each backup data, and inputs a value to the relationship counter (step S204). After execution of step S204, the processing by the backup unit 114 ends, and the client can be restored.

  Here, each step shown in FIG. 12 will be specifically described with reference to FIGS. FIG. 13 is a flowchart showing processing for acquiring and storing bank update data and catalog information shown in FIG. Steps S1001 to S1006 shown in FIG. 13 correspond to steps S201 to S204 shown in FIG.

  As shown in FIG. 13, first, the backup data storage unit 109 acquires backup data and catalog information from the backup data acquisition unit 108 (step S1001). Next, the backup data storage unit 109 stores the backup data in the storage unit 115 (step S1002). An example of the stored backup data is shown in FIG.

  Next, the backup data storage unit 109 determines whether the same backup data as the backup data stored in step S1002 has already been stored (step S1003). Note that the determination in step S1003 is performed using the catalog information as described above.

  As a result of the determination in step S1003, if the same backup data is not stored, the backup data storage unit 109 assigns a unique data ID to the catalog information acquired in step S1001 (step S1007).

  On the other hand, as a result of the determination in step S1003, if the same backup data is stored, the backup data storage unit 109 assigns the same data ID as the data ID of the already stored backup data (step S1004).

  Next, when the data ID is determined in steps S1004 and S1007, the backup data storage unit 109 stores the data ID and catalog information together in the storage unit 115 (step S1005). The backup data storage unit 1009 also sends the data ID to the related information adding unit 110 (step S1006).

  FIG. 14 is a flowchart showing the attribute information acquisition / storage process and the client number counter setting process shown in FIG. Steps S1011 to S1013 illustrated in FIG. 14 correspond to steps S202 and S203 illustrated in FIG.

  As shown in FIG. 14, first, the attribute collection unit 111 determines whether or not the client attribute received from the backup data acquisition unit 108 is stored in the storage unit 115 (step S1011). An example of attribute information stored in the storage unit 115 is shown in FIG.

If the attribute is not stored as a result of the determination in step S1011, the attribute collection unit 111 newly sets a client number counter and sets the value to 1 (step S1012). On the other hand, if it is already stored as a result of the determination in step S1011, the attribute collection unit 111 increments the value of the client number counter of the attribute by 1 (step S1013). As a result, the value of the client number counter becomes equal to the number of clients having the attribute.

  FIG. 15 is a flowchart showing the relation information acquisition / storage process and the relation counter setting process shown in FIG. Steps S1021 to S1024 illustrated in FIG. 15 correspond to step S204 illustrated in FIG.

  As illustrated in FIG. 15, first, the relationship information adding unit 110 converts the attribute information received from the backup data acquisition unit 108, the data ID received from the backup data storage unit 103, and the combination data of the relationship counter into the relationship information. Is stored in the storage unit 115 (step S1021). In step S1021, upon receiving the attribute information from the backup data acquisition unit 108, the relationship information adding unit 110 first obtains the corresponding attribute type for each backup data, and for each obtained attribute type. Set the relationship counter.

  Next, the relationship information adding unit 110 uses the catalog information to determine whether the backup data has already stored the same related information as the related information stored in step S1021 (step S1022). Specifically, the relationship information adding unit 110 determines whether or not the attribute information and the data ID match.

  If the same related information is stored as a result of the determination in step S1022, the related information adding unit 110 increments the value of the related counter by 1 (step S1023). On the other hand, if it is determined in step S1022 that the same related information is not stored, the relationship information adding unit 110 initializes the value of the relationship counter to 1 (step S1024).

  When the backup process shown in FIGS. 12 to 15 is completed, the client can be restored. Here, processing when the user restores the client or when a new client is introduced (when a computer is constructed) will be described. FIG. 16 is a flowchart showing a restore process by the network management apparatus in the present embodiment.

  The process shown in FIG. 16 is started when the user issues a restore command to the target computer from the outside to the restore unit 116. In the following description, it is assumed that the attribute of the restore destination computer is “restore attribute” and the restore destination computer is “client X”.

  As shown in FIG. 16, first, the restore command receiving unit 106 receives an input of a restore command, and the restore attribute receiving unit 107 receives an input of a restore attribute (step S1101). The accepted restore command and restore attribute are sent to the restore target selection unit 112.

  Next, the restore target selection unit 112 receives the restore command and the restore attribute, acquires the attribute information 104 stored in the storage unit 115, and acquires the number of clients N1 having the received restore attribute (step S1102).

  Next, the restore target selection unit 112 acquires a list of relationship information corresponding to the restore attribute from the relationship information 105 stored in the storage unit 115, and further includes a relationship counter N2 and the number of clients N1 included therein. From this, the degree of association (N2 / N1) is obtained (step S1103). Subsequently, the restoration target selection unit 112 extracts related information whose relevance is equal to or higher than a preset threshold, creates a list of data IDs included in the extracted related information, and inputs the list to the data ID transmission unit (step S1). S1105).

Next, the list data transmission unit 113 accesses the backup data 102 and the catalog information 103 based on the data ID included in the list, and searches the restore data from these (step S1105). Thereafter, the restore data transmission unit 113 transmits the restore data acquired in step S1105 to the client X that is the restore destination (step S1106).

  When the steps shown in FIG. 16 are executed, the restore processing shown in FIG. 17 is executed on the client X to be restored. FIG. 17 is a flowchart showing restore processing by the client in this embodiment.

  As shown in FIG. 17, first, the data restore unit 22 of the client that is the restore target receives the data transmitted by the restore data transmission unit 113 (step S1111). Next, the data restoration unit 22 stores the received data in the storage unit 25 and constructs a machine (step S1112). As a result, the restore process in the client X ends.

  As described above, in this embodiment, the relationship between software installed in an existing system and attributes such as client affiliation and user is extracted from the existing backup tendency. Then, the software related to this client can be installed simply by specifying the attribute of the client to be introduced. Therefore, the user who constructs the client can execute the restoration or new installation of the client without being aware of which software needs to be installed.

  In addition, it is possible to configure the software and setting items to be installed automatically as long as the attributes indicating the affiliation and user characteristics are specified, and the administrator can specify the software and settings to be installed to the user. It is no longer necessary to create the described guide and make the guide thoroughly known. As a result, the burden on the administrator is greatly reduced.

  Further, by regularly performing backup, it is possible to automatically update the relationship between software installed in the current system and attributes such as computer affiliation and user. In this case, the administrator does not need to be aware of whether or not a patch is applied, addition of a setting method, software used only by a small number of users, and the like. This result also greatly reduces the burden on the administrator.

  Moreover, the program in this Embodiment should just be a program which makes a computer perform the step shown in FIG. 10, FIG. If such a program is installed in a computer and executed, the network management apparatus 101 in this embodiment can be constructed. In this case, a central processing unit (CPU) of the computer functions as the data acquisition unit 108, the backup unit 114, and the restoration unit 116 to perform processing. Further, the storage unit 115 can be realized by storing data files constituting these in a storage device such as a hard disk provided in the computer.

  As described above, the present invention is useful in a computer network used in an organization such as a company, and has industrial applicability.

DESCRIPTION OF SYMBOLS 10 Network management system 11 Network 20-1-20-n Client 21 Data backup part 22 Data restore part 23 Attribute transmission part 24 Attribute setting part 25 Storage part 26 Client data 27 Client attribute information 100 Backup instruction | indication apparatus 101 Network management apparatus 102 Backup Data 103 Catalog information 104 Attribute information 105 Relationship information 106 Restore command reception unit 107 Restore attribute reception unit 108 Data acquisition unit 109 Backup data storage unit 110 Relationship information addition unit 111 Attribute collection unit 112 Restore target selection unit 113 Restore data transmission unit

Claims (16)

A network management device for managing a plurality of terminal devices connected by a network,
A data acquisition unit, a backup unit, and a restore unit;
The data acquisition unit acquires backup data and attributes of the terminal device from each of the plurality of terminal devices,
For each backup data acquired from each of the plurality of terminal devices, the backup unit obtains a corresponding attribute type, sets a counter for each type of attribute obtained, and sets the value of each counter to 1,
Furthermore, when the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data The value is the number of terminal devices having the common attribute,
Then, for each attribute, find the number of terminal devices having the attribute,
The restore unit, when an attribute is designated from the outside, uses the counter value for each attribute type of each backup data and the number of the terminal devices in each attribute to store the backup data. To select data related to the specified attribute to generate data for restore,
A network management device. The data acquisition unit further acquires catalog information specifying the content of the backup data from each of the plurality of terminal devices,
The network management device according to claim 1, wherein the backup unit determines whether the backup data is the same using the catalog information. The restore unit identifies the number N1 of terminal devices having a specified attribute and the counter value N2 of the same attribute as the specified attribute in each backup data,
When the value obtained by dividing N2 by N1 (N2 / N1) exceeds or exceeds a set threshold value, backup data corresponding to N2 in that case is selected, and the restoration The network management device according to claim 1 or 2, wherein the data is generated. The backup data includes setting information for each of the plurality of terminal devices,
The network management device according to claim 2, wherein the catalog information includes at least a setting item of the setting information included in the backup data, a date and time of creation or update of the backup data, and a size of the backup data. A network management system comprising a plurality of terminal devices connected by a network, and a network management device for managing these,
The terminal device includes a data backup unit that outputs the attribute of the terminal device and backup data to the network management device,
The network management device includes a data acquisition unit, a backup unit, and a restore unit,
The data acquisition unit acquires backup data and attributes of the terminal device from each of the plurality of terminal devices,
For each backup data acquired from each of the plurality of terminal devices, the backup unit obtains a corresponding attribute type, sets a counter for each type of attribute obtained, and sets the value of each counter to 1,
Furthermore, when the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data Set the value to the number of terminal devices having the common attribute,
Then, for each attribute, find the number of terminal devices having the attribute,
The restore unit, when an attribute is designated from the outside, uses the counter value for each attribute type of each backup data and the number of the terminal devices in each attribute to store the backup data. To select data related to the specified attribute to generate data for restore,
A network management system characterized by that. The data acquisition unit further acquires catalog information specifying the content of the backup data from each of the plurality of terminal devices,
The network management system according to claim 5 , wherein the backup unit determines whether the backup data is the same using the catalog information. The restore unit identifies the number N1 of terminal devices having a specified attribute and the counter value N2 of the same attribute as the specified attribute in each backup data,
When the value obtained by dividing N2 by N1 (N2 / N1) exceeds or exceeds a set threshold value, backup data corresponding to N2 in that case is selected, and the restoration The network management system according to claim 5 or 6 , wherein the data is generated. The backup data includes setting information for each of the plurality of terminal devices,
The network management system according to claim 6 , wherein the catalog information includes at least a setting item of the setting information included in the backup data, a date or time of creation or update of the backup data, and a size of the backup data. A network management method for managing a plurality of terminal devices connected by a network,
(A) obtaining backup data and attributes of the terminal device from each of the plurality of terminal devices;
(B) For each backup data acquired from each of the plurality of terminal devices, a corresponding attribute type is obtained, a counter is set for each obtained attribute type, and the value of each counter is set to 1.
(C) When the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data The value of the number of terminal devices having the common attribute, and
(D) For each attribute, obtaining the number of terminal devices having the attribute;
(E) When an attribute is designated from the outside, the counter value for each attribute type of each backup data obtained in the step (b) or (c) and the step (d) Selecting the data related to the specified attribute from the backup data using the obtained number of the terminal devices in each attribute, and generating data for restoration; and A network management method characterized by comprising: In the step (a), catalog information for specifying the contents of the backup data is acquired from each of the plurality of terminal devices.
The network management method according to claim 9 , wherein in the step (c), it is determined whether the backup data is the same using the catalog information. In the step (e), the number N1 of terminal devices having a specified attribute and the value N2 of the counter having the same attribute as the specified attribute in each backup data are specified,
When the value obtained by dividing N2 by N1 (N2 / N1) exceeds or exceeds a set threshold value, backup data corresponding to N2 in that case is selected, and the restoration generating a data network management method according to claim 9 or 1 0. The backup data includes setting information for each of the plurality of terminal devices,
The catalog information, the setting item of the setting information included in the backup data, date and time of creation or update the backup data, including at least the size of the backup data, the network management method of claim 1 0. A program for causing a computer to manage a plurality of terminal devices connected via a network,
In the computer,
(A) obtaining backup data and attributes of the terminal device from each of the plurality of terminal devices;
(B) For each backup data acquired from each of the plurality of terminal devices, a corresponding attribute type is obtained, a counter is set for each obtained attribute type, and the value of each counter is set to 1.
(C) When the same backup data is acquired from two or more terminal devices and the two or more terminal devices have a common attribute, the counter of the common attribute set in the same backup data The value of the number of terminal devices having the common attribute, and
(D) For each attribute, obtaining the number of terminal devices having the attribute;
(E) When an attribute is designated from the outside, the counter value for each attribute type of each backup data obtained in the step (b) or (c) and the step (d) And using the obtained number of the terminal devices in each attribute to select data related to the specified attribute from the backup data and generate data for restoration. A program characterized by letting In the step (a), catalog information for specifying the contents of the backup data is acquired from each of the plurality of terminal devices.
In said step of (c), using the catalog information, determines whether the same backup data, the program according to claim 1 3. In the step (e), the number N1 of terminal devices having a specified attribute and the value N2 of the counter having the same attribute as the specified attribute in each backup data are specified,
When the value obtained by dividing N2 by N1 (N2 / N1) exceeds or exceeds a set threshold value, backup data corresponding to N2 in that case is selected, and the restoration generating a data program according to claim 1 3 or 1 4. The backup data includes setting information for each of the plurality of terminal devices,
The catalog information, the setting item of the setting information included in the backup data, date and time of creation or update the backup data, including at least the size of the backup data, the program according to claim 1 4.

Images