System and method for collecting data from low-availability devices

• US 10,291,490 B1
• Filed: 02/11/2014
• Issued: 05/14/2019
• Est. Priority Date: 02/11/2014
• Status: Active Grant

• Current Assignee: Quest Software, Inc.
• Original Assignee: Quest Software, Inc.
• Inventors: McAleer, David, Dyer, Kelly Noel
• Primary Examiner(s): Cheema, Umar
• Assistant Examiner(s): Tolchinsky, Gregory P
• Application Number:
  US14/178,165
• Time in Patent Office: 1,918 Days
• Field of Search: None
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

In one embodiment, a method includes registering as a listener for availability notifications from at least one low-availability device. The method further includes determining a data-collection schedule of the at least one low-availability device. In addition, the method includes maintaining a prioritized queue comprising required data items needed from the at least one low-availability device. Also, the method includes preparing, in advance of the at least one low-availability device becoming available, a request for at least one required data item. The at least one required data item includes a highest-priority data item in the prioritized queue. The method additionally includes, responsive to a notification that the at least one low-availability device is available, transmitting the request to the at least one low-availability device.

Claims

1. A method comprising, on a computer system comprising at least one server computer:

registering as a listener for availability notifications from at least one low-availability device;

determining a data-collection schedule of the at least one low-availability device based at least in part on the availability notifications, the determining comprising tracking a frequency of availability and a duration of availability of the at least one low-availability device over time, the data-collection schedule comprising a determined frequency and a determined duration;

maintaining a prioritized queue comprising required data items needed from the at least one low-availability device, wherein the required data items are prioritized in the prioritized queue based at least in part on the data-collection schedule and a time when one or more of the required data items are needed;

preparing, in advance of the at least one low-availability device becoming available, a request for at least one required data item, the at least one required data item comprising a highest-priority data item in the prioritized queue; and

responsive to a notification that the at least one low-availability device is available, transmitting the request to the at least one low-availability device.

2. The method of claim 1, wherein the maintaining comprises creating the prioritized queue.

3. The method of claim 1, wherein the maintaining comprises updating the prioritized queue responsive to data-item updates.

4. The method of claim 1, comprising, responsive to successful receipt of the at least one required data item, removing the at least one required data item from the prioritized queue.

5. The method of claim 1, comprising, responsive to no successful receipt of the at least one required data item:

determining whether at least one failure criterion has been met; and

responsive to a determination that the at least one failure criterion has been met, performing at least one of the following;

removing the at least one required data item from the prioritized queue; and

de-prioritizing the at least one required data item.

6. The method of claim 1, comprising interacting with the at least one low-availability device until at least one of the following is true:

the prioritized queue contains no required data items that are needed from the at least one low-availability device; and

the at least one low-availability device is no longer available.

7. The method of claim 1, wherein the required data items comprise at least one selected from the group consisting of:

a firmware version, a received signal strength indication (RSSI), and a signal-to-noise ratio (SNR).

8. The method of claim 1, wherein:

each required data item in the prioritized queue is associated with a priority value;

the prioritized queue comprises a list of the required data items sorted by the priority value; and

the maintaining comprises ascertaining each priority value.

9. The method of claim 8, wherein the ascertaining is based, at least in part, on a request category of each of the required data items.

10. The method of claim 9, wherein, for at least one required data item in the prioritized queue, the ascertaining is based, at least in part, on a number of collection periods remaining before a scheduled report is due.

11. The method of claim 9, wherein, for at least one required data item in the prioritized queue, the ascertaining comprises adjusting an initial priority value based, at least in part, on the request category of the at least one required data item.

12. The method of claim 9, wherein, for at least one required data item in the prioritized queue, the ascertaining comprises setting the priority value based, at least in part, on the request category of the at least one required data item.

13. The method of claim 9, wherein the request category is selected from the group consisting of:

scheduled reports, on-demand requests from users, and user dashboards.

14. The method of claim 1, wherein the maintaining comprises merging identical entries in the prioritized queue.

15. The method of claim 1, wherein the determining comprises:

detecting that the at least one low-availability device is not in a low-availability state; and

taking corrective action based thereon.

16. The method of claim 1, wherein:

the at least one low-availability device comprises a plurality of low-availability devices; and

the method is performed for each low-availability device of the plurality of low-availability devices.

17. The method of claim 1, comprising receiving a response to the request, the response comprising the at least one required data item.

18. An information handling system comprising:

a computer processor, wherein the computer processor is operable to implement a method comprising;

registering as a listener for availability notifications from at least one low-availability device;

determining a data-collection schedule of the at least one low-availability device based at least in part on the availability notifications, the determining comprising tracking a frequency of availability and a duration of availability of the at least one low-availability device over time, the data-collection schedule comprising a determined frequency and a determined duration;

maintaining a prioritized queue comprising required data items needed from the at least one low-availability device, wherein the required data items are prioritized in the prioritized queue based at least in part on the data-collection schedule and a time when one or more of the required data items are needed;

preparing, in advance of the at least one low-availability device becoming available, a request for at least one required data item, the at least one required data item comprising a highest-priority data item in the prioritized queue; and

responsive to a notification that the at least one low-availability device is available, transmitting the request to the at least one low-availability device.

19. A computer-program product comprising a non-transitory computer-usable medium having computer-readable program code embodied therein, the computer-readable program code adapted to be executed to implement a method comprising:

registering as a listener for availability notifications from at least one low-availability device;

determining a data-collection schedule of the at least one low-availability device based at least in part on the availability notifications, the determining comprising tracking a frequency of availability and a duration of availability of the at least one low-availability device over time, the data-collection schedule comprising a determined frequency and a determined duration;

maintaining a prioritized queue comprising required data items needed from the at least one low-availability device, wherein the required data items are prioritized in the prioritized queue based at least in part on the data-collection schedule and a time when one or more of the required data items are needed;

preparing, in advance of the at least one low-availability device becoming available, a request for at least one required data item, the at least one required data item comprising a highest-priority data item in the prioritized queue; and

responsive to a notification that the at least one low-availability device is available, transmitting the request to the at least one low-availability device.