Deviceless brokerless backup

• US 9,766,985 B1
• Filed: 10/09/2014
• Issued: 09/19/2017
• Est. Priority Date: 10/09/2014
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Hemashekar, Bharath Siddapur, Bachu, Kiran
• Primary Examiner(s): Mackes, Kris
• Assistant Examiner(s): Bui, Tiffany
• Application Number:
  US14/510,750
• Time in Patent Office: 1,076 Days
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques

Abstract

In one example, a method for backing up data is performed in part by a manager server that receives a request for a deviceless backup session. The manager server authenticates the request and authorizes media database and index database operations. Next, the requested deviceless backup session is created and a backup session ID is transmitted that corresponds to the created deviceless backup session. The manager server then spawns an agent to handle communications with other devices. An update is then received concerning a backup performed with respect to a target device, and a confirmation sent that that the backup has been completed. Catalogue information concerning the completed backup is then received and stored, and the deviceless backup session and agent terminated.

Claims

1. A computer-implemented method for backing up data, comprising:

requesting, with a first client, a deviceless backup session;

receiving, with the first client, a backup session ID that confirms that the deviceless backup session has been created and that uniquely identifies the backup session, wherein the first client is a manager client configured to operate in conjunction with a manager backup application;

backing up, with a second client, a saveset that is based on data stored at a target device, wherein the target device is under control of the second client but is not under control of the first client, wherein the second client is an external backup client configured to operate in conjunction with an external backup application, wherein the first client and the second client are both hosted by the target device, and wherein the first client is installed on the target device either by, or at the request of, the second client;

reporting, with the first client, on progress of the backup performed by the second client;

transmitting, with the first client, catalogue information concerning the backup performed by the first client; and

ending, with the first client, the deviceless backup session.

2. The method as recited in claim 1, wherein reports concerning the progress of the backup are sent by the first client to a manager server.

3. The method as recited in claim 1, wherein the catalogue information is transmitted to an agent spawned by a manager server.

4. The method as recited in claim 1, wherein the catalogue information includes an update to saveset attributes associated with the backup performed by the second client.

5. The method as recited in claim 1, further comprising transmitting information confirming either that the backup session is still alive, or confirming that the backup session is no longer alive.

6. A physical device, wherein the physical device comprises:

one or more hardware processors; and

a non-transitory storage medium having stored therein computer-executable instructions which, when executed by the one or more hardware processors, perform the following operations;

requesting, with a first client, a deviceless backup session;

receiving, with the first client, a backup session ID that confirms that the deviceless backup session has been created and that uniquely identifies the backup session, wherein the first client is a manager client configured to operate in conjunction with a manager backup application;

backing up, with a second client, a saveset that is based on data stored at a target device, wherein the target device is under control of the second client but is not under control of the first client, wherein the second client is an external backup client configured to operate in conjunction with an external backup application, wherein the first client and the second client are both hosted by the target device, and wherein the first client is installed on the target device either by, or at the request of, the second client;

reporting, with the first client, on progress of the backup performed by the second client;

transmitting, with the first client, catalogue information concerning the backup performed by the first client; and

ending, with the first client, the deviceless backup session.

7. A computer-implemented method for backing up data, comprising:

receiving a request for a deviceless backup session, wherein the request for a deviceless backup session is received from a first client that is different from a second client associated with performance of a backup, and the first client is a manager client and the second client is an external backup client;

authenticating the request and authorizing media database and index database operations;

creating the requested deviceless backup session and transmitting a backup session ID that corresponds to the created deviceless backup session;

spawning, by a manager server that includes a manager application, an agent of the manager server;

receiving, by way of the agent, an update concerning a backup performed with respect to a target device;

transmitting the update, and receiving a response concerning whether or not the update was successfully made;

confirming, by way of the agent, that the backup has been completed;

receiving, by way of the agent, catalogue information concerning the completed backup;

storing, or causing the storage of, the catalogue information; and

receiving, by way of the agent, an indication that the deviceless backup session has been ended.

8. The method as recited in claim 7, further comprising displaying information concerning progress of the backup.

9. The method as recited in claim 7, wherein the catalogue information is transmitted to a media database daemon.

10. The method as recited in claim 7, wherein the update comprises one or more saveset attributes.

11. The method as recited in claim 7, further comprising using the agent to add index records for the backup.

12. The method as recited in claim 7, wherein the agent is terminated when the deviceless backup session is ended.

13. The method as recited in claim 7, wherein additional functions performed by and/or at the direction of the manager server and the agent include any one or more of:

updating the saveset;

updating backup/recover progress;

updating saveset/backup identifier attributes that are required by an external backup application to identify and recover the backup;

adding index records for backup;

aborting or closing, as applicable, the deviceless backup session;

or, cataloguing the backup at the manager server.

14. The method as recited in claim 7, further comprising creating, by the agent, a save-set for the deviceless backup session.

15. The method as recited in claim 7, wherein the manager client does not control the target device.

16. The method as recited in claim 7, wherein the manager server does not perform the backup.

17. The method as recited in claim 7, further comprising transmitting, by the agent, a save-set to a database.

18. The method as recited in claim 7, further comprising receiving, by the agent, the backup session ID from a database.

19. A physical device, wherein the physical device comprises:

one or more hardware processors; and

a non-transitory storage medium having stored therein computer-executable instructions which, when executed by the one or more hardware processors, perform the following operations;

receiving a request for a deviceless backup session, wherein the request for a deviceless backup session is received from a first client that is different from a second client associated with performance of a backup, and the first client is a manager client and the second client is an external backup client;

authenticating the request and authorizing media database and index database operations;

creating the requested deviceless backup session and transmitting a backup session ID that corresponds to the created deviceless backup session;

spawning, by a manager server that includes a manager application, an agent of the manager server;

receiving, by way of the agent, an update concerning a backup performed with respect to a target device;

transmitting the update, and receiving a response concerning whether or not the update was successfully made;

confirming, by way of the agent, that the backup has been completed;

receiving, by way of the agent, catalogue information concerning the completed backup;

storing, or causing the storage of, the catalogue information; and

receiving, by way of the agent, an indication that the deviceless backup session has been ended.