1. Field of the Invention
The present invention generally relates to a device information management apparatus for collecting device information regarding operational status of devices including image processing devices such as multifunction printers (MFPs) via a network and managing the collected device information.
2. Description of the Related Art
Patent document 1 discloses a remote management system for collecting information (e.g., counter information such as the number of printed pages, failure information, and remaining-amount information of consumables such as toner) on image processing devices such as MFPs via a network, for example, the Internet.
In such a system, information including counter information and failure information of an image processing device is reported to a center by a communication device attached to the image processing device or by a communication function of the image processing device. Then, an appropriate action, e.g., dispatching a service engineer, is taken according to the importance level of the reported information.
Remote management systems as described above have become essential to properly manage devices in customer offices. Therefore, failure of a device (server) in a remote management system may have a significant impact on the business and it is important to take appropriate measures against system failures.
Generally, measures as described below are taken to cope with failures in a remote management system.
(1) To provide multiple servers with the same function/performance so that even if a server fails, the operation can be continued with another server (cluster configuration).
(2) To provide a secondary server in a remote place so that even if a primary server fails, the operation can be continued by the secondary server (cold site or hot site).
In either case, a service being provided by a server is taken over by a backup server to continue the operation.
With the above measures, it is necessary to provide a backup server having substantially the same performance as that of the primary server. Accordingly, if a large-scale server is used as the primary server to manage a large number of devices, it is necessary to provide a backup server of equal size.
Embodiments of the present invention provide a device information management apparatus, a device information management method, and a non-transitory storage medium containing a device information management program that solve or reduce one or more problems caused by the limitations and disadvantages of the related art.
An embodiment of the present invention provides a device information management apparatus for processing a report from a device management client during a failure of a transaction system. The device information management apparatus includes a reception unit configured to receive the report from the device management client; a determining unit configured to determine whether to process the report based on an importance level of the report and a load (workload) level of the device information management apparatus; a processing unit configured to process the report if the determining unit determines to process the report; and a discarding unit configured to discard the report if the determining unit determines not to process the report.
Another embodiment of the present invention provides a method of processing a report from a device management client by a device information management apparatus during a failure of a transaction system. The method includes the steps of receiving the report from the device management client during the failure of the transaction system; determining whether to process the report based on an importance level of the report and a load level of the device information management apparatus; processing the report if it is determined to process the report; and discarding the report if it is determined not to process the report.
Still another embodiment of the present invention provides a storage medium storing program code for causing a computer to perform a method of processing a report from a device management client during a failure of a transaction system. The method includes the steps of receiving the report from the device management client during the failure of the transaction system; determining whether to process the report based on an importance level of the report and a load level of the computer; processing the report if it is determined to process the report; and discarding the report if it is determined not to process the report.
Preferred embodiments of the present invention are described below with reference to the accompanying drawings.
<System Configuration>
In
A load balancer 4 receives the device information collected by the device management client 2 via the network 3 and sends the device information to a transaction system 5. In the transaction system 5, application servers 51 manage the device information. Also, the device information collected by the transaction system 5 is utilized by an information utilization system 8 connected via a network to the transaction system 5. When the transaction system 5 fails, the load balancer 4 sends the device information to a device information management apparatus 6. A user terminal 9 used by a user at a service center is connected via a network to the information utilization system 8.
The transaction system 5 includes application servers 51A, 51B, . . . , database (DB) servers 52A, 52B, . . . , and a storage device (disk array) 53. The device information management apparatus 6 includes a reception unit 61, a load measuring unit 62, a determining unit 63, a processing unit 64, a discarding unit 65, and a storage unit 66. Also, a recovery processing unit 7 is connected to the device information management apparatus 6. The recovery processing unit 7 restores the transaction system 5 using data in the storage unit 66 during a recovery process (or after recovery).
The load balancer 4 equally distributes reports received via the network 3 from the device management client 2 to the application servers 51 for load (workload) balancing while the transaction system 5 is operating properly. During a failure of the transaction system 5, the load balancer 4 redirects the reports to the device information management apparatus 6. As a distribution algorithm during normal operations of the transaction system 5, the round robin algorithm or the fastest algorithm is preferably used. With the round robin algorithm, assuming that the transaction system 5 includes application servers 51A through 51D, reports are distributed, for example, in order of “A>B>C>D>A>B>C>D . . . ”. With the fastest algorithm, each report is directed to one of the application servers 51 with the fastest response time.
When the transaction system 5 fails, the load balancer 4 redirects reports to the device information management apparatus 6. This redirection may be accomplished by either one of the following methods:
(1) The load balancer 4 is preconfigured to redirect all reports to the device information management apparatus 6 if all the application servers 51 do not respond.
(2) The load balancer 4 is manually reconfigured by an operator to redirect all reports to the device information management apparatus 6 when the transaction system 5 fails.
One problem with the method (1) is that reports may be mistakenly redirected to the device information management apparatus 6 even when responses of the application servers 51 become slow because of, for example, temporary heavy load. With the method (2), the above redirection error may not occur, but it takes time to manually reconfigure the load balancer 4.
The application servers 51 are functional units for executing business logic to provide services. The application servers 51 store regular reports received from the device management client 2 via the load balancer 4 in the storage device 53 by using the DB servers 52, and transfer irregular reports immediately to the information utilization system 8. A regular report is used to report information such as counter information on a regular basis, and an irregular report is used to report information such as failure information or remaining-amount information of consumables each time when an event occurs. Each of the application servers 51 is connected to multiple DB servers 52. The DB servers 52 connected to each application server 51 are prioritized. For example, the application server 51 first tries to access a primary DB server, and if the primary DB server does not respond, tries to access a secondary DB server.
Each of the DB servers 52 runs a database management system (DBMS) and manipulates database entities stored in the storage device 53 according to requests from the application servers 51. To prevent database access contention between the DB servers 52, a mechanism to lock, for example, a database, a table, or a record is provided. Also, synchronizing signals may be exchanged between the DB servers 52.
The device information management apparatus 6 is a functional unit to perform processing during a failure of the transaction system 5. The reception unit 61 receives reports sent from the device management client 2 via the load balancer 4. The load measuring unit 62 measures the load of the device information management apparatus 6. The determining unit 63 determines whether to process or discard a report based on the importance level of the report and the current load of the device information management apparatus 6 measured by the load measuring unit 62. Importance levels of reports are predetermined according to service types of the reports such as a critical failure report, a scheduled report, and a toner near-end report. Reports include a regular report used to report information such as counter information and an irregular report used to report information such as failure information or remaining-amount information of consumables. The processing unit 64 temporarily stores regular reports with high importance levels and transfers irregular reports with high importance levels immediately to the information utilization system 8. Reports having low importance levels and received when the load of the device information management apparatus 6 is high are discarded by the discarding unit 65 without being processed.
The recovery processing unit 7 restores regular reports temporarily stored in the storage unit 66 of the device information management apparatus 6 into the DB servers 52 during a recovery process of the transaction system 5. The function of the recovery processing unit 7 may instead be provided in the device information management apparatus 6, the load balancer 4, or the application servers 51.
The information utilization system 8 includes an application server 81, a DB server 82, and a storage device 83.
The application server 81 is a functional unit for executing business logic to provide services. The application server 81 sends irregular reports transferred from the transaction system 5 to the user terminal 9. Also, the application server 81 obtains information stored in the database of the transaction system 5 at appropriate timings and stores the obtained information in the storage device 83 under the control of the DB server 82 to be able to respond to information requests from the user terminal 9.
In
The processing unit 64 may include a regular report processing unit 641 for processing regular reports and an irregular report processing unit 645 for processing irregular reports. The regular report processing unit 631 includes a regular report analysis unit 642 for determining types of regular reports, a scheduled report processing unit 643 for processing scheduled reports, and a billing counter report processing unit 644 for processing billing counter reports. The scheduled report processing unit 643 and the billing counter report processing unit 644 temporarily store reports in the storage unit 66. The temporarily stored reports are restored by the recovery processing unit 7 to the DB servers 52 of the transaction system 5. The reports may be stored in the storage unit 66 in a text format without using a database (without converting the reports into a database format). This makes it possible to reduce the load of the device information management apparatus 6 during a system failure and thereby to increase the number of reports that can be handled by the device information management apparatus 6.
The irregular report processing unit 645 includes an irregular report transmission unit 646 for sending irregular reports to the information utilization system 8.
<Operations>
In
When a retrieval request for stored information is sent from the information utilization system 8 to the transaction system 5 (step S13), the transaction system 5 retrieves the requested information from the database (step S14) and sends the retrieved information to the information utilization system 8 (step S15).
Meanwhile, when an irregular report is sent from the device management client 2 and is directed to one of the application servers 51 of the transaction system 5 by the load balancer 4 (step S16), the application server 51 transfers the irregular report to the information utilization system 8 (step S17).
In
Discarding reports with low importance levels during a system failure as described above makes it possible to reduce the size of a storage device necessary to store reports. Reports may be stored in a format other than a database format. For example, storing reports in a text format makes it possible to simplify the system configuration and to save storage space of a storage device (e.g., HDD).
Meanwhile, when recovering from a failure, the transaction system 5, under the control of the recovery processing unit 7, restores regular reports temporarily stored in the storage unit 66 of the device information management apparatus 6 into the DB servers 52 (step S27).
Steps S22 and S25 in
In the above embodiment, whether to process a report is determined based on both the importance level of a report and the load level of the device information management apparatus 6. Alternatively, whether to process a report may be determined based only on the importance level of a report or the load level of the device information management apparatus 6.
Also, whether to process a report may be determined based primarily on the importance level as shown in
If the importance level is not 4 (NO in step S103), it is then determined whether the importance level is 3 (step S104). If the importance level is 3 (YES in step S104), it is then determined whether the load of the device information management apparatus 6 (hereafter called the server load) is less than 80% (step S105). If the server load is less than 80% (YES in step S105), the report is processed (step S110) and the determining process is terminated (step S111). If the server load is not less than 80% (NO in step S105), the determining process is terminated without processing the report (step S111).
If the importance level is not 3 (NO in step S104), it is then determined whether the importance level is 2 (step S106). If the importance level is 2 (YES in step S106), it is then determined whether the server load is less than 60% (step S107). If the server load is less than 60% (YES in step S107), the report is processed (step S110) and the determining process is terminated (step S111). If the server load is not less than 60% (NO in step S107), the determining process is terminated without processing the report (step S111).
If the importance level is not 2 (NO in step S106), it is then determined whether the importance level is 1 (step S108). If the importance level is 1 (YES in step S108), it is then determined whether the server load is less than 40% (step S109). If the server load is less than 40% (YES in step S109), the report is processed (step S110) and the determining process is terminated (step S111). If the server load is not less than 40% (NO in step S109), the determining process is terminated without processing the report (step S111).
If the importance level is not 1 (NO in step S108), the determining process is terminated without processing the report (step S111).
<Summary>
As described above, embodiments of the present invention provide at least the following features:
(1) A device information management apparatus of the above embodiments makes it possible to discard reports that are not important and/or urgent and thereby to continue only important operations performed by application servers and DB servers of a transaction system.
(2) The device information management apparatus makes it possible to store reports in a storage unit in a format other than a database format and thereby to save storage space.
(3) The device information management apparatus makes it possible to restore reports temporarily stored in a storage unit to DB servers of the transaction system during a recovery process (or after recovery) from a system failure.
The above features in turn make it possible to use a low-performance apparatus as the device information management apparatus.
Embodiments of the present invention provide a device information management apparatus that makes it possible to use a small-scale backup device for data recovery.
An embodiment of the present invention provides a device information management apparatus for processing reports during a system failure. The device information management apparatus processes only reports of high importance when its load is high and processes even reports of low importance when its load is low. This configuration makes it possible to continue operations normally performed by a primary server when it fails by using a backup server smaller than the primary server.
The present invention is not limited to the specifically disclosed embodiments, and variations and modifications may be made without departing from the scope of the present invention.
The present application is based on Japanese Priority Application No. 2007-238269 filed on Sep. 13, 2007, and Japanese Priority Application No. 2008-173661 filed on Jul. 2, 2008, the entire contents of which are hereby incorporated herein by reference.
Number | Date | Country | Kind |
---|---|---|---|
2007-238269 | Sep 2007 | JP | national |
2008-173661 | Jul 2008 | JP | national |
Number | Name | Date | Kind |
---|---|---|---|
5146344 | Bennett et al. | Sep 1992 | A |
5155842 | Rubin | Oct 1992 | A |
5748470 | Hager et al. | May 1998 | A |
5814799 | Swartz et al. | Sep 1998 | A |
5881238 | Aman et al. | Mar 1999 | A |
6247142 | Wong et al. | Jun 2001 | B1 |
6327591 | Osborn et al. | Dec 2001 | B1 |
6404513 | Denker | Jun 2002 | B1 |
6434165 | Sherer et al. | Aug 2002 | B1 |
6499117 | Tanaka | Dec 2002 | B1 |
6874103 | Cepulis | Mar 2005 | B2 |
7194433 | Hyakutake et al. | Mar 2007 | B1 |
7315893 | Vinberg | Jan 2008 | B2 |
7457879 | Horvitz et al. | Nov 2008 | B2 |
7624308 | Critchley et al. | Nov 2009 | B2 |
7668879 | Vivian et al. | Feb 2010 | B2 |
7921224 | Jajoo et al. | Apr 2011 | B2 |
20020194324 | Guha | Dec 2002 | A1 |
20020196452 | Komiya | Dec 2002 | A1 |
20030033554 | Bomfim et al. | Feb 2003 | A1 |
20030076532 | Seto | Apr 2003 | A1 |
20030081248 | Simpson | May 2003 | A1 |
20030105863 | Hegli et al. | Jun 2003 | A1 |
20030123393 | Feuerstraeter et al. | Jul 2003 | A1 |
20030142955 | Hashizume et al. | Jul 2003 | A1 |
20030145109 | Nakashima | Jul 2003 | A1 |
20030195917 | Horiyama et al. | Oct 2003 | A1 |
20030225903 | Lodha | Dec 2003 | A1 |
20040034807 | Rostowfske | Feb 2004 | A1 |
20040145973 | Nagashima | Jul 2004 | A1 |
20040199655 | Davies et al. | Oct 2004 | A1 |
20040233474 | Watanabe | Nov 2004 | A1 |
20050013288 | Hong et al. | Jan 2005 | A1 |
20050018242 | Azami | Jan 2005 | A1 |
20050050544 | Saito et al. | Mar 2005 | A1 |
20050097405 | Sesek et al. | May 2005 | A1 |
20050111857 | Negishi | May 2005 | A1 |
20050193110 | Dantzig et al. | Sep 2005 | A1 |
20050241026 | Esler et al. | Oct 2005 | A1 |
20050286483 | Lee et al. | Dec 2005 | A1 |
20060047712 | Shitomi et al. | Mar 2006 | A1 |
20060077436 | Zhang et al. | Apr 2006 | A1 |
20060129563 | Phillips et al. | Jun 2006 | A1 |
20060290995 | Tanabe et al. | Dec 2006 | A1 |
20070038518 | Yokoyama | Feb 2007 | A1 |
20070043784 | Parkinson | Feb 2007 | A1 |
20070091370 | Saito | Apr 2007 | A1 |
20070169125 | Qin | Jul 2007 | A1 |
20070208799 | Hughes | Sep 2007 | A1 |
20070220353 | Iura et al. | Sep 2007 | A1 |
20070266148 | Ruiz et al. | Nov 2007 | A1 |
20080004067 | Piipponen et al. | Jan 2008 | A1 |
20080030750 | Kato | Feb 2008 | A1 |
20080114866 | Round | May 2008 | A1 |
20080201470 | Sayama | Aug 2008 | A1 |
20090009340 | Weaver et al. | Jan 2009 | A1 |
20100238839 | Batteram et al. | Sep 2010 | A1 |
Number | Date | Country |
---|---|---|
63-250746 | Oct 1988 | JP |
6-324916 | Nov 1994 | JP |
9-6652 | Jan 1997 | JP |
11-143829 | May 1999 | JP |
2001-250008 | Sep 2001 | JP |
2003-140986 | May 2003 | JP |
2005-18372 | Jan 2005 | JP |
3814071 | Jun 2006 | JP |
WO 2007088575 | Aug 2007 | WO |
Entry |
---|
Japanese Office Action issued Sep. 25, 2012, in Japan Patent Application No. 2008-173661. |
Number | Date | Country | |
---|---|---|---|
20090077231 A1 | Mar 2009 | US |