Prioritizing backup of endpoint devices in enterprise network environments

US2016335283A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016335283-A1
Application numberUS-201514709402-A
CountryUS
Kind codeA1
Filing dateMay 11, 2015
Priority dateMay 11, 2015
Publication dateNov 17, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A backup system is described for prioritizing backup data in enterprise networks. Messages containing data to be backed up are received at a backup server from endpoint devices and a priority value is determined for each message based on numerous factors, such as the organizational role of the user of the endpoint, the time since last backup, average upload speed, frequency of backups, and other properties. The system prioritizes backing up of messages based on the priority value of the messages.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method, comprising: receiving at a backup server messages containing backup data from a plurality of endpoint devices, wherein the endpoint devices send the messages to the backup server to backup data on a backup database; determining a priority value corresponding to each message based on properties related to the endpoint device from which the message is received; placing each message into a queue that temporarily stores messages before messages are written to the backup database; and processing the messages from the queue to the backup database according to the priority value corresponding to each message. 2 . The method of claim 1 , wherein processing the messages from the queue to the backup database according to the priority value corresponding to each message comprises at least one of: writing messages in the queue with a higher corresponding priority value to the database before messages with a lower corresponding priority value; or allocating more resources to writing messages with a higher corresponding priority value to the database than to messages with a lower corresponding priority value. 3 . The method of claim 1 , wherein the priority value corresponding to a message is further determined based on an organizational role corresponding to the endpoint device from which the message is received. 4 . The method of claim 1 , wherein the priority value corresponding to a message is further determined based on how close the endpoint device from which the message is received is to completing backup. 5 . The method of claim 1 , wherein the priority value corresponding to a message is further determined based on an amount of time that passed since the endpoint device from which the message is received was backed up last. 6 . The method of claim 1 , wherein the priority value corresponding to a message is further determined based on at least one of: a comparison of a current upload speed with an average upload speed of the endpoint device from which the message is received; or an average connected time to the backup server of the endpoint device from which the message is received. 7 . The method of claim 1 , wherein the priority value corresponding to a message is further determined based on a uniqueness of data that is to be backed up on the endpoint from which the message is received. 8 . A computing device, comprising: at least one processor; and memory including instructions that, when executed by the at least one processor, cause the computing device to: receive at a backup server messages containing backup data from a plurality of endpoint devices, wherein the endpoint devices send the messages to the backup server to backup data on a backup database; determine a priority value corresponding to each message based on properties related to the endpoint device from which the message is received; place each message into a queue that temporarily stores messages before messages are written to the backup database; and process the messages from the queue to the backup database according to the priority value corresponding to each message. 9 . The computing device of claim 8 , wherein processing the messages from the queue to the backup database according to the priority value corresponding to each message comprises at least one of: writing messages in the queue with a higher corresponding priority value to the database before messages with a lower corresponding priority value; or allocating more resources to writing messages with a higher corresponding priority value to the database than to messages with a lower corresponding priority value. 10 . The computing device of claim 8 , wherein the priority value corresponding to a message is further determined based on an organizational role corresponding to the endpoint device from which the message is received. 11 . The computing device of claim 8 , wherein the priority value corresponding to a message is further determined based on how close the endpoint device from which the message is received is to completing backup. 12 . The computing device of claim 8 , wherein the priority value corresponding to a message is further determined based on an amount of time that passed since the endpoint device from which the message is received was backed up last. 13 . The computing device of claim 8 , wherein the priority value corresponding to a message is further determined based on at least one of: a comparison of a current upload speed with an average upload speed of the endpoint device from which the message is received; or an average connected time to the backup server of the endpoint device from which the message is received. 14 . The computing device of claim 8 , wherein the priority value corresponding to a message is further determined based on a uniqueness of data that is to be backed up on the endpoint from which the message is received. 15 . A non-transitory computer readable storage medium comprising one or more sequences of instructions, the instructions when executed by one or more processors causing the one or more processors to execute the operations of: receiving at a backup server messages containing backup data from a plurality of endpoint devices, wherein the endpoint devices send the messages to the backup server to backup data on a backup database; determining a priority value corresponding to each message based on properties related to the endpoint device from which the message is received; placing each message into a queue that temporarily stores messages before messages are written to the backup database; and processing the messages from the queue to the backup database according to the priority value corresponding to each message. 16 . The non-transitory computer readable storage medium of claim 15 , wherein processing the messages from the queue to the backup database according to the priority value corresponding to each message comprises at least one of: writing messages in the queue with a higher corresponding priority value to the database before messages with a lower corresponding priority value; or allocating more resources to writing messages with a higher corresponding priority value to the database than to messages with a lower corresponding priority value. 17 . The non-transitory computer readable storage medium of claim 15 , wherein the priority value corresponding to a message is further determined based on an organizational role corresponding to the endpoint device from which the message is received. 18 . The non-transitory computer readable storage medium of claim 15 , wherein the priority value corresponding to a message is further determined based on how close the endpoint device from which the message is received is to completing backup. 19 . The non-transitory computer readable storage medium of claim 15 , wherein the priority value corresponding to a message is further determined based on an amount of time that passed since the endpoint device from which the message is received was backed up last. 20 . The non-transitory computer readable storage medium of claim 15 , wherein the priority value corresponding to a message is further determined based on at least one of: a comparison of a current upload speed with an average upload speed of the endpoint device from which the message is received; or an average connected time to the backup server of the endpoint device from which the message is received.

Assignees

Inventors

Classifications

  • for networked environments · CPC title

  • G06F16/17Primary

    Details of further file system functions · CPC title

  • Management of the backup or restore process · CPC title

  • Management of the data involved in backup or backup restore · CPC title

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016335283A1 cover?
A backup system is described for prioritizing backup data in enterprise networks. Messages containing data to be backed up are received at a backup server from endpoint devices and a priority value is determined for each message based on numerous factors, such as the organizational role of the user of the endpoint, the time since last backup, average upload speed, frequency of backups, and othe…
Who is the assignee on this patent?
Vmware Inc
What technology area does this patent fall under?
Primary CPC classification G06F16/17. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Nov 17 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).