JP2013258481A - Network device management system and network device management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem in which when setting values of network devices are frequently changed from their initial values by a user to efficiently utilize the devices, differences from the initial values may be stored for the backup, but the amount of the stored data may become large under an environment where setting of the network devices are standardized, resulting in inefficiency of the backup.SOLUTION: Setting data of a backup management device and backed-up device are compared each other, and among setting data of the backed-up device, both of setting items and setting values different form the setting data of the backup management device are extracted as the difference data. The backup management device stores the extracted difference data in itself as backup data for the backed-up device. When reconstruction of the setting data for the backed-up device is required, the backup management device reconstructs the setting data for the backed-up device based on the setting data of itself and the backup data.

Description

  The present invention relates to a network device management system that backs up setting data in a network device.

In the case of a personal computer, it is common to back up data to another storage medium in case the data on the hard disk is lost or damaged. In addition, network devices such as printers and multi-function peripherals are storing various setting data and document data in storage devices as their functionality and functionality increase, and there is an increasing need for backups of setting data. ing.
However, there is also a demand that it is not necessary to prepare a dedicated server for network devices, and a method for backing up setting data to another network device as in Patent Document 1 has been proposed.
Patent Document 1 aims to apply the setting data of the first printer that can no longer be used due to a failure or the like to the newly introduced second printer. In this case, the setting data is backed up to another printer, and all the setting data of the first printer or the difference data between the setting data of the first printer and the initial setting value (default) is the backup target. .
In recent years, with respect to devices connected to a network, an increasing number of companies manage the selection of devices to be introduced and the settings of those devices by the IT department. In these companies, it is common to unify network device settings as much as possible in accordance with the operation policy of the network device. In particular, security-related settings (off / on of a specific port, SNMP community name, e-mail / fax transmission address book, etc.) are often unified.

JP2009-175983A

In an environment where network device settings are unified, as in Patent Document 1, when backing up all setting data and differential data from the default, a large storage capacity is required to save the setting data. There is a possibility of becoming. For example, when all setting data is backed up, it is necessary to have a capacity for storing setting data for one network device to be backed up. Further, when the difference data from the default is backed up, the storage capacity increases as the difference from the default (the setting item to be changed according to the company policy) increases. A more specific example is a destination table. In the destination table, since the initial setting value of the network device is zero, the storage capacity increases as the number of registered destination tables increases. For this reason, the storage area of the storage unit is compressed as much as the storage capacity is used for backup of the set value.
SUMMARY An advantage of some aspects of the invention is to provide a mechanism for efficiently backing up setting data of network devices.

  The network device management system according to the present invention is a network device management system including a management device and a managed device to which the management device backs up setting data, and the management device specifies the managed device. Means for acquiring setting data of the managed device from the managed device, means for extracting a difference item between the acquired setting data and setting data in the managed device, and the extracted difference It has a means for storing a set of items and set difference values as difference data as difference data.

  The network device management system of the present invention is a network device management system including a first management device and a second management device that performs backup with the first management device, wherein the first management device includes: Means for designating the second management device; means for obtaining setting data of the second management device from the second management device; and setting in the first management device among the obtained setting data First difference extraction means for extracting a difference item with data, means for storing a set of difference items extracted by the first difference extraction means and a difference setting value which is a setting value thereof as first difference data; Of the setting data of the first management device, extracted by the second difference extraction means for extracting a difference item from the setting data in the second management device, and the second difference extraction means And a means for transmitting a set of differential setting values, which are set items, to the second management device as difference data, wherein the second management device is transmitted from the first management device. It has a means to preserve | save said 2nd difference data, It is characterized by the above-mentioned.

  Network device setting data can be backed up efficiently.

Figure of system configuration example A diagram of a hardware configuration example of the management device 101 and the managed device 102 Software configuration example of the managed device 101 and the managed device 102 Example of setting data managed by the management device 101 The figure which shows the backup processing flow of the setting data in 1st embodiment The figure which shows the restoration process flow of the setting data in 1st embodiment The figure which shows the whole flow of the mutual backup in 2nd embodiment. The figure which shows the backup processing flow of the setting data in 2nd, 3rd embodiment The figure which shows the restoration process flow of the setting data in 2nd, 3rd embodiment The figure which shows the whole flow of the mutual backup in 3rd embodiment. The figure which shows the update process flow of the setting data in 3rd embodiment

  The best mode for carrying out the present invention will be described below with reference to the drawings.

<First embodiment>
FIG. 1 is an overall configuration diagram of a network device management system according to the present embodiment. FIG. 1 includes a network device management apparatus 101 (hereinafter referred to as a management device) that manages backup of network devices connected to each other via a network 100 and a network device 102 (hereinafter referred to as a managed device) to be backed up by the management device 101. Is done.
The managed device 101 and the managed device 102 indicate devices including office devices such as MFP (Multifunction Peripheral), printer, FAX, and general-purpose computers, for example. 1 may be connected to the network 100 by an arbitrary number.

  The hardware configuration and software configuration of each device constituting the device management system according to the present invention will be described below.

  FIG. 2 shows a hardware configuration diagram of the management device 101 and the managed device 102. The management device 101 and the managed device 102 include a control unit 200, an operation unit 201, a printer 202, and a scanner 203. The operation unit-related configuration of the control unit 200 includes a CPU (computer) 210, a RAM 211, an operation unit I / F 212, a network I / F 213, a ROM 214, an image bus I / F 215, a DKC 216, an HD 217, and a system bus 218. The configuration relating to printing and scanning of the control unit 200 includes an image bus 219, a scanner image processing unit 220, a printer image processing unit 221, a RIP 222, and a device I / F 223. In the above configuration, the scanner 203 and the scanner image processing unit 220 are provided as necessary.

  The CPU 210 is a controller for controlling the entire control unit 200. The RAM 211 is an image memory for temporarily storing image data. The operation unit I / F 212 is an interface with the operation unit 201, and outputs image data to be displayed on the operation unit 201 to the operation unit 201. Further, it has a role of transmitting information input by the user through the operation unit 201 to the CPU 210. The network I / F 213 is an interface that is connected to the network 100 and exchanges information with an external device via the network 100. In addition, a management information base (MIB) that stores various information of the management device 101 and the managed device 102 is provided. The MIB is stored in the HD 217 and can be accessed from an external device via the network I / F 213. The various information that the MIB has indicates information such as the IP address, the name of the managed device, and the status. The ROM 214 is a boot ROM, and is a storage medium that stores a system boot program (computer program). The Image Bus I / F 215 is a bus bridge that connects the system bus 218 and the image bus 219 and performs data conversion. A DKC (Disk Controller) 216 controls an HD (Hard Disk) 217. The HD 217 is an external storage device that stores system software, image data, setting data, and the like. The system bus 218 is a common data exchange path between components constituting the control unit 200. The image bus 219 is configured by a PCI bus or IEEE1394, and is a path for transferring image data at high speed. The scanner image processing unit 220 corrects, processes, and edits an input image. The printer image processing unit 221 performs correction, resolution conversion, and the like on the print output image data according to the performance of the printer. A RIP (Raster Image Processor) 222 expands a PDL command sent from the network 100 into a bitmap image. The device I / F 223 connects the printer 202 and the scanner 203, which are image input / output devices, and the control unit 200, and performs synchronous / asynchronous conversion of image data.

  When the managed device and the managed device are shipped, default values are stored in the devices as setting data. After these devices are installed in the user environment, the setting data is customized from the default value according to the operation instruction of the user or the administrator of the user environment via the operation unit 213 or a remote setting unit (not shown), and the customized setting data Is stored in the HD 217. The device operates based on the customized setting data. In the following description, it is assumed that the setting data stored in the HD 217 is a value customized from the default value at the time of shipment. Although there are a plurality of items in the setting data, it is not necessary to customize the setting data from the default values for all items. The customization also includes giving an arbitrary setting value to an item whose default is null.

  FIG. 3 shows software configurations of the management device 101 and the managed device 102. The software configuration of the management device 101 and the managed device 102 includes a network module 300, a setting data management module 301, a task management module 302, and a database (hereinafter referred to as DB) 303. The network module 300 serves as an interface with an external device (such as the management device 101 for the managed device 102) connected to the network 100. For example, when the managed device 102 receives a setting data acquisition request from the management device 101, the managed device 102 transmits the request to the setting management module 301. The network module 300 of the managed device 102 receives various data from the setting data management module 301 and responds to the management device 101 via the network 100. The setting management module 301 is a module for operating and managing setting data held by the management device 101 and the managed device 102, and includes a backup module 304 and a restoration module 305. The setting management module 301 can acquire, store, and apply settings to the DB 303. The task management module 302 is a module for scheduling periodic processing (such as periodic notification to an external device) assigned to the management device 101 and the managed device 102. The DB 303 stores data of the management device 101 and the managed device 102. In this embodiment, the DB 303 stores setting data in each device as shown in FIG. The backup module 304 has a function for backing up the device setting data, and executes the processing of FIG. For example, the setting data to be backed up is generated and the setting data is transmitted to the external device via the network module 300. The restoration module 305 is a module for applying the setting data received from the external device to itself, and executes the processing of FIG. Note that the communication method with the external devices of the management device 101 and the managed device 102 may use communication by MIB, communication by SOAP message, or the like. There may be modules other than the modules shown in FIG.

  FIG. 4A and FIG. 4B show an example of the configuration of setting data managed by the management device 101 and a specific example. The setting data managed in this embodiment is characterized in that it is shown as a difference between the management device 101 and the managed device 102. The setting data shown in FIG. 4 is stored and managed in the DB 303.

  Reference numeral 400 denotes a list of managed devices 102 managed by the management device 101, which is managed using a management ID for uniquely identifying the managed device 102. Reference numerals 401 and 402 indicate the difference between the setting items of the management device 101 and the managed device 102, respectively, and are composed of a difference item 403 and a difference setting value 404 corresponding to the difference item 403. Reference numeral 401 denotes a list indicating a difference from the managed device 102 whose management ID is X in 400 (hereinafter, simply referred to as a difference list or X-Diff). Specifically, it is a set of set values for which the exclusive OR is obtained for the set values of the management device 101 and the managed device 102 and the result is true. The difference list 401 in this example indicates that there are n differences. On the other hand, 402 is a list indicating differences from the managed device 102 whose management ID is Y in 400, and indicates that m differences exist. Reference numeral 405 denotes a setting item of the management apparatus 101 itself, which indicates that it is composed of t setting items in total. From the above information, for example, if the setting item of the management ID (X) is Xi and the setting item of the management device 101 itself is Oi, the difference list (X-Diff) can be expressed by the following equation.

  The above expression is an expression for extracting the difference item D to be stored, and the case where Di = 0 is excluded from the storage target. Also, the number of items 403 indicated by 401, 402, and 405 does not always match, and the contents of specific items do not always match. In the above equation, the items Oi and Xi to be compared are items indicating the same setting contents, and if the item corresponding to Oi does not exist in the managed device 102, the difference list indicates that the setting value is unnecessary. Saved. Further, even when an item corresponding to Xi does not exist in the management apparatus 101, the setting value is stored in the difference list.

  FIG. 4B shows an example in which specific values are applied to the configuration example of FIG. Reference numeral 405 denotes all setting items of the management apparatus 101, and 401 and 402 denote difference lists between the management apparatus 102 corresponding to the management ID (X) and the management ID (Y). Reference numerals 406 and 407 indicate setting items 403 as to whether or not “double-sided printing” is used as a comparison target item by default. 406 is an example of an item that is not necessary for the difference list 401. If the setting for double-sided printing in the setting data 405 of the management device 101 is On and the setting for double-sided printing of the managed device 102 corresponding to the management ID (X) of 400 is also On, the setting values of both are equal. It becomes an unnecessary item in the difference list. For this reason, FIG. 4B shows that the data is not stored by a double line. On the other hand, 407 is the target of the difference list because the setting of duplex printing of the managed device 102 is Off and there is a difference from the setting data 405 of the managed device 101.

  Setting data backup processing (difference data creation processing) and restoration processing according to the present embodiment will be described with reference to FIGS. In this embodiment, the management device 101 is described as a processing flow in which the managed device 102 actively backs up the managed device 102. However, the present invention is not limited to this, and the backup / restore is passively performed in response to a request from the managed device 102. May be processed automatically.

  FIG. 5 shows a processing flow for the management device 101 to create a backup of the managed device 102 (create differential data). It should be noted that the backup module 304 is the subject of execution of this processing unless otherwise specified. This backup creation process flow is performed based on a backup creation process instruction from the operation unit of the management apparatus 101. Alternatively, after the first backup is created, the re-creation process may be performed as a periodic task process. The re-creation process may be performed when the setting data of the management device 101 is changed and when the setting data of the managed device 102 is changed. S500 is a process for the user to designate a managed device 102 (hereinafter, a backup target device) to be backed up by the management device 101. When a backup target device is designated by this processing, the existence confirmation is performed on the backup target device in S501. This survival confirmation may be simply a continuity test using PING, or another method may be used. S502 is processing for determining whether or not the backup target device is alive in the existence confirmation in S501. If the backup target device is alive, the process proceeds to S503. If not, the process proceeds to S508. In step S503, the backup module 304 acquires all setting data from the backup target device. In step S504, the setting data acquired in step S503 is compared with the setting data of the management device 101 to extract a difference. In S503 and S504, all settings are acquired at once and the difference is extracted. However, the items to be compared may be partially acquired and the difference may be extracted repeatedly. In step S505, the difference extracted in step S504 is stored in the DB 303 as backup data (difference data) of the backup target device. A difference list such as 401 in FIG. 4 is created by S504 and S505. S506 is a process for determining whether or not the difference list has been correctly created. If the difference list has been created correctly, the process proceeds to S507. If not, the process proceeds to S508. S507 is a process for storing backed-up device information. A device list to be managed as shown in 400 of FIG. 4 is created and linked to the difference list stored in S505. As a result, the setting data to be managed shown in FIG. 4 is stored. S508 is a process of displaying the execution result of the backup process, and can notify the user of the normal end or the error end.

  FIG. 6 shows a processing flow for the management device 101 to restore setting data for the managed device 102. If there is no particular description, the subject of execution of this processing is the restoration module 305. S600 is processing for determining whether a restoration request has been issued from the user or the managed device 102 in the management device 101. For example, as a method for requesting restoration by the user, a method of displaying a device list 400 currently managing backup on the operation unit 201 of the management device 101, selecting a backup target device from the list, and clicking a restoration request button. There is. In step S601, it is determined whether there is backup data corresponding to the backup target device, that is, 401 and 402 in FIG. If the backup data exists, the process proceeds to S602. If the backup data does not exist, the process proceeds to S609. S602 is processing for confirming whether or not the restoration destination device, that is, the backup target device is alive. This survival confirmation may be simply a continuity test using PING, or another method may be used. S603 is processing for determining whether or not the restoration destination device is alive in the existence confirmation in S602. If the restoration destination device is alive, the process proceeds to S604, and if not, the process proceeds to S609. S604 is processing for temporarily storing the setting data 405 of itself, and S605 is processing for temporarily storing the restoration destination data 401 in the RAM 211 or the like. Thereafter, based on the data stored in S604 and S605, restoration data is created in S606. For example, when creating the restoration data of 400 management ID (X), it is possible to create by applying the information of the difference list of the managed device 102 to each setting value of the setting data 405 of the management device 101. it can. When the setting value is stored in the difference list, the setting value is overwritten on the setting data 405 of the management apparatus 101. When it is stored in the difference list that the setting item of the management device 101 does not exist in the managed device, the setting item is excluded from the restoration data. In step S607, the restoration data created in step S606 is transmitted to the restoration destination device. The restoration destination device that has received the restoration data restores the setting by overwriting each setting data on its own setting by the restoration module (not shown). Thereafter, the restoration destination device transmits a success / failure restoration result to the management device 101 (not shown). In step S608, the restoration result transmitted from the restoration destination device is received. In step S609, the execution result of the restoration process is displayed, and the user can be notified that the process has ended normally or ended in error.

  In addition, it does not depend on the configuration of the management device 101 and the managed device 102 described in the present embodiment, and for example, there may be a plurality of managed devices 102 for one management device 101. A plurality of management devices 101 may manage the managed device 102.

  According to the above method, backup and restoration can be efficiently performed without a server in an environment where setting data of a plurality of network devices are almost unified.

<Second Embodiment>
In the first embodiment, the process in which the management device 101 backs up the setting data of the managed device 102 and the processing to restore the setting data to the managed device 102 have been described. However, in the case of the first embodiment, even if the managed device 102 can be backed up, the managed device 101 cannot be backed up. Therefore, in the present embodiment, a method for mutual backup between the management devices 101 will be described. The system configuration diagram (FIG. 1), the hardware configuration (FIG. 2), the software configuration (FIG. 3), and the saved data (FIG. 4) of the management device 101 are the same as those in the first embodiment. Description of is omitted. Further, in this embodiment, for the purpose of backup between the management devices 101, the management device 101 will be described by distinguishing between the device A (first management device) and the device B (second management device).

  FIG. 7 shows an overall flow of mutual backup (including restoration) between managed devices. In FIG. 7, processing focusing on the device A is shown, but the same processing is also performed on the device B. S700 is a process of confirming whether or not there are devices that are mutually backed up after the device A is activated. If it exists, the process proceeds to S702. If it does not exist, the process proceeds to S701 as the first activation. S701 is a process of performing mutual backup at the first activation. This process will be described later with reference to FIG. In step S702, it is determined whether or not setting data restoration processing is necessary. If it is determined that it is necessary, the process proceeds to S703. If it is determined that it is not necessary, the process proceeds to S704. S703 is a setting data restoration process, which will be described in detail later with reference to FIG. S704 is a process for determining whether to perform regular backup. If regular backup is to be performed, the process proceeds to S705. If not, the process proceeds to S706. S705 is processing for periodically updating the backup data stored in each of the devices A and B, and S701, that is, the same processing as that shown in FIG. The timing for regular backup is managed and executed by the task management module 302. In step S706, it is determined whether the device has received a shutdown request from the user or the system. If a shutdown request is received, the backup process is terminated, and if no request is received, the process proceeds to S702.

  FIG. 8 shows a backup processing flow in mutual backup. This process corresponds to S701 and S705 in FIG. S801, S803, S804, S806 to S809 are the same as S501 to S507 in FIG. Note that S806 corresponds to a first difference extraction process and a process of generating first difference data. S800 is the same process as S500, and detailed description thereof is omitted. However, in the case of the periodic backup in S705, it is assumed that the device is selected from the mutual backup target devices stored in the DB 303. S802 is a process of transmitting a response when the device B, which is a mutual backup target device, receives a survival confirmation from the device A. In step S805, when the device B receives a setting data acquisition request from the device A, the setting data management module 301 of the device B collects the setting data of the device B and transmits the setting data to the requesting device A. S810 is processing for creating backup data (difference list, A-Diff) of device A to be stored in device B. In this process, the difference list of device A with respect to the setting data of device B is created in the same manner as the difference list created in step S806. Specifically, the difference item with the setting data in the device B is extracted from the setting data of the device A (second difference extraction process), and the set of the difference item and the difference setting value that is the setting value is extracted as the second difference. Generate as data. S811 is a process of transmitting the difference list (A-Diff) created in S812 to the device B. Upon receipt of A-Diff in S812, device B stores A-Diff in device B's DB 303 as backup data of device A. In S812, the backup target device (device A in this example) in device B is saved at the same time to create a difference list as shown in FIG. In step S813, the mutual backup process is completed by sending a storage completion notification to the device A.

  FIG. 9 shows a data restoration processing flow in mutual backup. This process corresponds to S703 in FIG. Since S900 to S902, S904 to S907, S913, and S914 have the same contents as S600 to S609 in FIG. 9 will be described assuming that the device A restores the setting data of the device B. S903 is processing for transmitting a response when device B, which is a device to be restored and receives mutual confirmation from device A, is a device to be restored. S908 is processing for creating backup data (difference, A-Diff) of device A to be stored in device B. In this process, a difference list (A-Diff) for backing up the setting data of the device A to the device B again is created as in S810 of FIG. S909 is processing for transmitting the restoration data B ′ created in S907 and the difference list (A-Diff) created in S810 to the device B. S910 is a process in which the device B that has received the restored data B ′ applies B ′ to its own settings. After applying the restoration data B ′, the device B stores the A-Diff received together with the restoration data B ′ as backup data of the device A in the DB 303 (S911). After that, in step S912, the device B transmits to the device A that the restoration has been normally performed or that the error has ended. Although the device A creates backup data (A-Diff) for backup to the device B together with the restored data as described in FIG. 9, the device B may create A-Diff.

  In the mutual backup described in this embodiment, one mutual backup target device is targeted for one management device, but mutual backup may be performed with a plurality of devices for one device. In addition to mutual backup, the managed device 102 may be backed up as in the first embodiment.

  By using the above mutual backup method, server-less and efficient backup / restoration including the management device 101 can be performed in an environment where the setting data of a plurality of network devices are almost unified. Is possible.

<Third embodiment>
In the second embodiment, the mutual backup method for backing up the management device 101 has been described. However, according to the method shown in the second embodiment, the data update timing is only the regular backup process. In such a case, since the latest setting data cannot be backed up, the old setting data may be restored. Therefore, in this embodiment, an efficient data update method in mutual backup when the setting of the management device is changed will be described.

  The system configuration diagram (FIG. 1), the hardware configuration (FIG. 2), software configuration (FIG. 3), and saved data (FIG. 4) of the management device 101 are the same as those in the first and second embodiments. Explanation here is omitted. Further, the backup process (FIG. 8) and the restoration process (FIG. 9) are the same as those in the second embodiment, and thus description thereof is omitted. Further, in this embodiment, as in the second embodiment, the management device 101 is described as being distinguished from the device A and the device B for backup of the management devices 101, respectively.

  FIG. 10 shows an overall flow of mutual backup between managed devices including data update processing. S1000 to S1003 and S1006 to S1009 correspond to S700 to S707 in FIG. S1004 is a process of determining whether the setting data has been changed in the device A. If there is a change, the process proceeds to the update process of S1005 (described later in FIG. 11), and if there is no change, the process proceeds to S1006.

  FIG. 11 shows a data update processing flow in mutual backup. This process is a process when the setting data is changed in the device A, and is executed by the setting data management module 301. S1100 is processing for determining whether or not there is a mutual backup target device (also referred to as a data update target device in FIG. 11) that holds its own backup data. In the determination in S1100, it is confirmed whether or not the device is stored in the managed device list 400 stored in the DB 303 of the device A. If there is a mutual backup destination, the process proceeds to S1101. If there is no mutual backup destination, the process ends because there is no data update destination. S1101 is a process of confirming whether or not the data update target device is alive. This survival confirmation may be simply a continuity test using PING, or another method may be used. S1102 is a response process for notifying that the device B is alive in response to the confirmation from the device A in S1101. Device A determines in S1103 that there was a response (S1102) from device B. If the device B, which is the data update target device, is alive, the process proceeds to S1104. If the device B is not alive, the backup data cannot be updated, and the process ends. S1104 is a process of extracting a changed point in its own setting data. S1105 is a process of determining whether or not the changed portion of S1104 is included in the difference list (B-Diff) of device B stored in device A. Specifically, it is determined whether or not the setting items included in 401 and 402 in FIG. 4 have been changed. If the changed part is included in B-Diff, the process proceeds to S1106. If not included, the process proceeds to S1107. In step S1106, the setting content of the B-Diff is updated. Specifically, the value of the setting content 404 is updated. Note that, in the update processing in S1106, when the setting contents of the device A and the device B match, the item with the matching setting content is deleted from the B-Diff. S1107 is a process of determining whether the changed portion of S1104 corresponds to a portion not included in the difference data (B-Diff) of device B stored in device A. Specifically, it is determined whether a setting item not included in 401 or 402 in FIG. 4 has been changed. If it is determined in S1108 that a part other than B-Diff has been changed, a new setting item is found to be different, so a new setting item is added to B-Diff to update B-Diff (S1108). If it is determined in S1107 that the portion not included in the difference data (B-Diff) has not been changed, the process proceeds to S1109. In step S1109, the difference data (B-Diff) updated in steps S1104 to S1108 is stored in the DB 303 of the device A as new backup data of the device B. S1110 is processing for creating backup data (difference list, A-Diff) of device A to be stored in device B. The difference list of the device A can be created, for example, by the same processing as S905 to S908 in FIG. S1111 is a process of transmitting the difference data extracted in S1110 to the device B. Upon receipt of the difference data (A-Diff) transmitted in S1111, device B stores A-Diff as backup data for device A in DB 303 of device B (S1112). Thereafter, the device A is notified of the completion of the data update in S1113. S1114 is a process for displaying to the user that the data update process has been completed normally. By using the above method, the data update process is completed.

  In the mutual backup described in this embodiment, the backup data of one mutual backup target device is updated for one management device, but a plurality of backup data may be updated.

  By using the above data update method, efficient data update in mutual backup can be realized.

<Other examples>
The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (11)

A network device management system including a management device and a managed device to which the management device performs a backup of setting data,
The management device is:
Means for designating the managed device;
Means for obtaining setting data of the managed device from the managed device;
Of the acquired setting data, means for extracting a difference item with the setting data in the management device;
A network device management system comprising means for storing a set of extracted difference items and a set difference value as difference data as difference data. The network device management system according to claim 1,
The management device is:
Means for restoring the setting data of the managed device based on the setting data of the management device and the difference data stored in the management device;
A network device management system comprising means for transmitting the restored setting data to the managed device.   The network device management system according to claim 1, wherein the difference data is generated when setting data is changed in the management device and when setting data is changed in the managed device. A network device management system including a first management device and a second management device that backs up with the first management device,
The first management device is:
Means for designating the second management device;
Means for obtaining setting data of the second management device from the second management device;
Of the acquired setting data, a first difference extraction means for extracting a difference item with the setting data in the first management device;
Means for storing, as first difference data, a set of difference items extracted by the first difference extraction means and a difference setting value that is a setting value thereof;
Of the setting data of the first management device, second difference extraction means for extracting a difference item from the setting data in the second management device;
A difference item extracted by the second difference extraction means and a set of difference setting values that are set values thereof are transmitted as difference data to the second management device;
The second management device is:
A network device management system comprising means for storing the second difference data transmitted from the first management device. The network device management system according to claim 4,
The first management device is:
Means for restoring the setting data of the second management device based on the setting data of the first management device and the first difference data stored in the first management device;
Means for creating difference data to be stored in the second management device from the setting data of the first management device and the restored setting data of the second management device;
Means for transmitting difference data to be stored in the second management device and the restored setting data to the second management device;
The second management device is:
Means for applying the setting data transmitted from the first management device;
A network device management system comprising means for storing the difference data transmitted from the first management device. In the network equipment management system according to claim 4 or 5,
The first management device is:
Means for extracting a changed portion of the setting data when the setting data is changed in the first management device;
When the change location of the setting data is included in the difference data extracted by the first difference extraction unit, the setting value of the change location in the difference data is updated, and the change location of the setting data is the first If it is not included in the difference data extracted by the difference extraction means, an update means for adding the changed location and its set value to the difference data;
A network device management system comprising means for storing difference data updated by the updating means. The network device management system according to claim 6,
The means for updating the value of the changed location of the setting data is such that if the set value of the changed location matches the set value of the difference data extracted by the first difference extracting means, the item of the changed location is a difference A network device management system, characterized in that it is deleted from the difference data as if there is no data. A network device management method in a network device management system including a management device and a managed device on which the management device performs backup of setting data,
The management device is
Designating the managed device;
Obtaining setting data of the managed device from the managed device;
Of the acquired setting data, a step of extracting a difference item with setting data in the management device;
A network device management method comprising: executing a step of storing a set of extracted difference items and a set difference value as difference data as difference data. A network device management method in a network device management system including a first management device and a second management device that performs backup with the first management device,
The first management device is
Designating the second management device;
Obtaining setting data of the second management device from the second management device;
Of the acquired setting data, a first difference extraction step of extracting a difference item with the setting data in the first management device;
Storing a set of difference items extracted by the first difference extraction step and difference setting values that are set values as first difference data;
Of the setting data of the first management device, a second difference extraction step of extracting a difference item with the setting data in the second management device;
A set of difference items extracted by the second difference extraction step and a difference setting value that is a setting value thereof is transmitted as difference data to the second management device, and the second difference data is transmitted to the second management device. A network device management method characterized by executing a step of storing data.   A computer program for causing a computer to execute the network device management method according to claim 8 or 9.   A storage medium storing the computer program according to claim 10.

Images