WO2016085537A1

WO2016085537A1 - Backup operations

Info

Publication number: WO2016085537A1
Application number: PCT/US2015/023555
Authority: WO
Inventors: Kiran C K
Original assignee: Hewlett Packard Enterprise Development Lp
Priority date: 2014-11-26
Filing date: 2015-03-31
Publication date: 2016-06-02

Abstract

In some examples, techniques to send discovery commands to host computers to initiate execution of the discovery modules, generate a filtered list of backup object types from the list of backup object types based on backup policies, send backup modules based on the filtered list to the host computers to perform backup operations of backup objects associated with the filtered list, generate a logical grouping of the host computers to perform backup operations on the backup objects based on the backup policies, and send backup commands to the logical grouping of host computers to initiate performance of the backup modules independently from each of the host computers directed to a remote computer that is separate from each of the host computers.

Description

BACKUP OPERATIONS BACKGROUND

[0001 ] Storage systems may include backup management functionality to perform backup and restore operations. Backup operations may include generating a copy of data that is in use to allow the data to be recovered or restored in the event the data is lost or corrupted. Restore operations may include retrieving the copy of the data and replacing the lost or corrupted data with the retrieved copy of the data.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Fig. 1 is a block diagram of a computer system for backup operations according to an example implementation.

[0003] Fig. 2 is a flow diagram of a computer system for backup operations of Fig. 1 according to an example implementation.

[0004] Fig. 3 is an example block diagram showing a non-transitory, computer-readable medium that stores instructions for a computer system for backup operations in accordance with an example implementation.

DETAILED DESCRIPTION

[0005] Storage systems may include backup management functionality to perform backup and restore operations. Backup operations may include generating a copy of data that is in use to allow the data to be recovered or restored in the event the data is lost or corrupted. Restore operations may include retrieving the copy of the data and replacing the lost or corrupted data with the retrieved copy of the data.

[0006] Storage systems include applications that process data for normal operation of the applications. For example, a storage system may include a database application that may process data types such as data records as part of the normal operation. In another example, a storage system may include productivity applications such as spreadsheet programs, text processing programs, presentation programs which may process respective data types. The storage system may include backup functions to perform backup operations on backup objects such as data associated with the backup object types of applications. For example, for a database application, the system may identify backup object types as data records and perform backup operations on the actual backup objects that include the data that is associated with the data records. In some storage systems, a backup process may involve substantial configuration of backup software or application for each of the backup objects. The backup process may involve a large number of host computers with applications associated with data that may need to be part of backup operations. As the number of host computers increases, it may be become burdensome, error prone and costly to configure the backup process to process backup objects across all of the host computers.

[0007] The techniques presented here may improve backup operation performance. For example, the techniques may help improve the backup process by identifying backup objects of applications across host computers and perform backup operations on the backup objects thereby reduce the cost and errors in the backup process. In another example, the techniques involve the automatic discovery of backup object types present in host computers and abstracting the backup object types to help allow users such as system administrators to perform backup operations in an aggregated manner. For example, aggregation of backup operation may include generating logical groups of host computer for backup operations for particular backup objects across particular host computers. This may include, for example, backup of backup objects associated with all databases, backup object types related to file directories, backup objects of a particular file from each of the host computers, backup object types associated with a list of all directories set to an environment variable, and the like.

[0008] In one example, the techniques of the present application disclose a management module configured to send to host computers discovery modules to query for backup object types associated with application modules at the host computers. The management module sends discovery commands to the host computers to initiate execution of the discovery modules at the host computers. In response to receipt of lists of backup object types from the host computers responsive to the discovery commands, management module generates a filtered list of backup object types from the list of backup object types based on backup policies. The management module sends backup modules selected from a plurality of backup modules based on the filtered list to the host computers to perform backup operations of backup objects associated with the filtered list. The management module generates a logical grouping of the host computers to perform backup operations on the backup objects based on the backup policies. The management module sends backup commands to the logical grouping of host computers to initiate performance of the backup modules to perform backup operations on the backup objects and independently from each of the host computers directed to a remote computer that is separate from each of the host computers.

[0009] In one example, the backup object types are associated with backup objects used in the operation of the application modules that require backup operations. The management module may be further configured to check whether the host computers are authorized to perform backup operations. The management module may be configured to send the discovery commands to the host computers to iteratively query the host computers for different backup object types and return separate lists of each of the different backup object types. The backup polices may include selection of backup objects associated with the backup object types that are processed by application modules that require backup operations.

[0010] In this manner, the techniques presented here may improve storage processing performance. For example, the techniques may help improve the backup operation performance by identifying backup objects of applications across host computers and to perform backup operations on the backup objects thereby reduce the cost and errors in the backup process. The techniques provide backup policy based aggregation processing of backup operations to improve backup performance and user experience. The techniques may improve backup configuration and backup operations which may reduce the need to resort to unscrupulous system image backup thereby helping promote faster backup operations, faster restore operations, and reduction in backup operations.

[0011] Fig. 1 is a block diagram of a system 100 with a management computer 102 for communication with host computers 104 for backup operations according to an example implementation.

[0012] In one example, management computer 102 is configured to communicate with host computers 104 (104-1 through 104-n) over communication channel 128. The management computer 102 includes a management module 110, backup policies 112, backup modules 114 (114-1 through 114-n), and list of backup objects types 116, where n may be any number. [0013] The management module 110 may include functionality to manage the operation of management computer 102. For example, management module 110 may include functionality to communicate with host computers 104 to manage backup operations between the management computer and host computers and remote computer 106, as explained below in further detail.

[0014] The backup polices 1 12 may include may include principles, rules, and guidelines to manage backup operations for host computers 104. For example, backup polices 112 may include rules for selection of backup objects 136 associated with backup object types 124 that are processed by application module 122 that require backup operations for backup and restore purposes. For example, a host computer may include a database application module that processes database record types as well as a text processing applications that processes file record types. In one example, it may be desirable to have a backup policy 112 for backup object types 124 that require backup operations that include database record types and the database records with the actual data associated with the database application modules. In another example, it may be desirable to have a backup policy 112 for backup object types 124 that require backup operations that include file record types and the file records with the actual data associated with text processing application modules. In another example, backup policies 112 may be a combination of different backup object types. In another example, backup policies 112 may include other criteria such as backup object types related to file directories, backup objects of a particular file from each of the host computers, backup object types associated with a list of all directories set to an environment variable, and the like.

[0015] The backup modules 114 may include functionality to perform backup operations on backup objects 136. In some examples, management module 110 may be configured to send backup modules selected from a plurality of backup modules 114 which are stored as backup modules 120 on host computers. In one example, backup modules 114 or 120 may include functionality to perform backup operations independently from each of the host computers directed to remote computer 106 that is separate from each of the host computers. The backup modules 114 or 120 may respond to commands from management module 110 to initiate performance or execution of backup operations. In another example, management module 110 may be configured to perform or executed restore operations. Restore operations may include having host computers 104 retrieve copies of the data that have been stored as part of the backup operations and replace the lost or corrupted data with the retrieved copies of the data.

[0016] The backup operations may include making copies of backup objects 136 from one storage area to another storage area. The storage areas may be implemented on storage devices with any means to store data for later retrieval. The storage devices may include non-volatile memory, volatile memory or a combination thereof. Examples of non-volatile memory include, but are not limited to, electrically erasable programmable read only memory (EEPROM) and read only memory (ROM). Examples of volatile memory include, but are not limited to, static random access memory

(SRAM), and dynamic random access memory (DRAM). Examples of storage devices may include, but are not limited to, HDDs, CDs, DVDs, SSDs optical drives, flash memory devices and other like devices.

[0017] The list of backup objects types 116 includes lists of backup object types 124 received from host computers 104, as shown by dashed arrow 132. The list of backup objects types 116 includes object types associated with application modules that may require backup operations. For example, host computers 104 may include database application modules that process database record types. In this case, it may be desirable to have a backup policy 112 for backup object types 124 that require backup operations that includes database records which include the actual data of database record types associated with database application modules. [0018] The host computers 104 are configured to communicate with management computer 102 and remote computer 108 over communication channel 128. The host computers 104 include discovery module 118, backup module 120, application module 122, backup object types 124 and backup objects 136.

[0019] The host computers 104 may include functionality to manage the operation of the host computers. For example, host computers 104 may include functionality to communicate with management computer 102 to manage backup operations between the management computer, the host computers and remote computer 106, as explained below in further detail.

[0020] The discovery module 118 include functionality for checking or querying host computers 104 for backup object types 124. The discovery module 118 may be configured to receive discovery commands from management computer 102 (or management module 110) to initiate execution of the discovery module at the host computers. In response to the discovery commands being sent from management computer 102 to host computers 104, discovery module 118 generates list of backup object types and sends them to the management computer. As explained above, backup object types are associated with backup objects used in the operation of the application modules that require backup operations. In another example, management computer 102 may send to host computers 104 a discovery module 118 to query for backup object types associated with an application module 122 at the host computers. In another example, management computer 102 may be configured to send discovery commands to host computers 104 to iteratively query the host computers for different backup object types and return separate lists of each of the different backup object types. In another example, discovery module 1 18 may be configured to provide or return a user configurable environment variable having a comma separated list of directories to be backed up, which may dynamically restrict the backup operations necessary. [0021 ] The backup module 120 includes functionality to perform backup operations on backup objects 136. The management computer 102 sends a backup module 1 14 from the management computer to host computers 104 which is stored as backup module 120 on host computers. The functionality of backup module 120 is similar to the functionality of backup modules 114 which was described above and is not repeated here.

[0022] The application module 122 includes functionality to perform data processing functions with object types which are associated with objects which represent the actual data. For example, a host computer may include a database application module that may be configured to process database record types (object types) as well as text processing applications that process file record types (objects). In this case, the database record types are the object types and the database records are the objects which represent the actual data. As explained above, in one example, it may be desirable to have a backup policy 112 for backup object types 124 that require backup operations that include database record types (backup object types) and the database records (backup objects) which contains the actual data associated with database application modules. The backup operations are performed on backup objects 136 which are the actual data. In this case, backup objects 136 include database records which represent the actual data. In another example, it may be desirable to have a backup policy 112 for backup object types 124 that require backup operations that include file record types

(backup object types) and file records (backup objects) which contains the actual data associated with text processing application modules. In another example, backup policies 112 may be a combination of different backup object types. In other examples, backup policies 112 may include other criteria or rules such as backup object types related to file directories, backup objects of a particular file from each of the host computers, backup object types associated with a list of all directories set to an environment variable, and the like. [0023] In one example, management module 110 may be configured to send commands to host computers 104 to initiate execution of backup operations from the host computers to remote computer 106. In one example management module 1 10 may generate a logical grouping of host computers 104 to perform backup operations on the backup objects based on the backup policies. The management module 110 sends backup commands to the logical grouping of host computers 104 to initiate execution or performance of backup modules 120 to perform backup operations on the backup objects. In one example, management module 1 10 may include backup policies 112 that includes criteria, rules or guidelines for specifying the timing of the backup operations. In one example, backup policies 112 may specify that the backup operations are to occur at a particular date and time, frequency, locations and the like.

[0024] In another example, management module 110 may employ a separate computer, such as registry computer, that may be configured to identify backup object types being used by host computers and then provide or generate a list of backup object types. The registry computer may communicate with host computers 104 to gather objects types and

communicate the list to management computer 102. In another example, backup object types may be identified through a manual input process that may include having a user or administrator provide the list of backup types. In another example, management computer 102 may employ a combination of these techniques to practice the present application.

[0025] The remote computer 106 includes functionality to manage the operation of the remote computer. As explained above, backup operations may include configuring host computers to make copies of backup objects 136 from one storage area to another storage area. In one example, management module 110 may be configured to cause host computers 104 to perform backup operations from a storage area of the host computers to another storage area where such storage is associated with remote computer 106. In one example, remote computer 106 includes backup objects 126 which represents a storage area to maintain copies of backup objects 136 from host computers 104. In one example, remote computer 106 may include functionality to communicate with host computers 104 to manage backup operations between the host computers and the remote computer, as explained below in further detail.

[0026] In one example, to illustrate operation, management module 110 may be configured to send to host computers 104 a discovery module(s) 118 to query for backup object types 124 associated with application module(s) 122 at the host computers. The management module 1 10 may send discovery commands to host computers 104 to initiate execution of discovery modules 118 at the host computers. In response to receipt of lists of backup object types 116, shown as dashed arrow 132, from host computers 104 responsive to the discovery commands, management module 110 may generate a filtered list of backup object types from the list of backup object types based on backup policies 112. The management module 1 10 may then send backup modules 1 14 selected from a plurality of backup modules based on the filtered list to host computers 104, shown as dashed arrow 130, to perform backup operations of backup objects associated with the filtered list. The

management module 110 generates a logical grouping of host computers 104 to perform backup operations on the backup objects based on the backup policies. The management module 110 sends backup commands to the logical grouping of host computers 104 to initiate performance of backup modules 120 to perform backup operations on the backup objects and independently from each of the host computers directed to a remote computer 106, shown as dashed arrow 134. In this case, host computers 104 perform the backup operations separate from each of the host computers.

[0027] The management computer 102, host computers 104 and remote computer 106 may be any electronic device capable of data processing such as a server computer, mobile device, notebook computer and the like. The functionality of the components of management computer 102, host computers 104 and remote computer 106 may be implemented in hardware, software or a combination thereof.

[0028] The communication channel 128 may include any electronic communication means of communication including wired, wireless, network based such as storage area network (SAN), Ethernet, Fibre Channel and the like.

[0029] It should be understood that the description of system 100 above is for illustrative purposes and other implementations of the system may be employed to practice the techniques of the present application. For example, management computer 102 is shown as a single component but the management computer may be a plurality of computer systems to practice the techniques of the present application.

[0030] Fig. 2 is a flow diagram 200 of a computer system for backup operations of Fig. 1 according to an example implementation.

[0031] In one example, to illustrate operation, it may be assumed that management computer 102 is configured to communicate with host computers 104-1 , 104-2, 104-3, through 104-n, wherein n is 100. It may be further assumed that three host computers 104-1 ,104-2,104-3 have respective application modules 122-1 , 122-2, 122-3 configured as database applications with respective backup object types 124-1 , 124-2, 124-3 as database record types which are associated with respective backup objects 136-1 , 136-2, 136-3 as database records which contain the actual data. On the other hand, it may be further assumed that the other host computers 104- 4 through 104-100 have respective application modules 122-4 through 122- 100 configured as text processing applications with respective backup object types 124-4 through 124-100 as file record types which are associated with respective backup objects 136-4 through 136-100 as text or file records which contain the actual data. [0032] Processing may begin at block 202, wherein management computer 102 sends to host computers 104 discovery modules 118 to query for backup object types 124 associated with application modules 122 at the host computers. In this example, management module 110 sends to host computers 104-1 through 104-100 discovery modules 118 to query for backup object types 124-1 through 124-100 associated with application modules 122- 1 through 122-100 at the host computers. Processing then proceeds to block 204.

[0033] At block 204, management computer 102 sends discovery commands to host computers 104 to initiate execution of discovery modules 118 at the host computers. In this example, management module 110 sends discovery commands to host computers 104-1 through 104-100 to initiate execution of discovery modules 1 18-1 through 118-100 at the host computers. Processing then proceeds to block 206.

[0034] At block 206, management computer 102 receives lists of backup object types 116 from host computers 104. In this example, three host computers 104-1 ,104-2,104-3 provide, as shown by dashed arrow 132 in Fig. 1 , respective lists of backup object types 116-1 , 116-2, 116-3 associated with database record types which are associated with respective backup objects 136-1 , 136-2, 136-3 as database records which contain the actual data. On the other hand, the other computers host computers 104-4 through 104-100 provide, as shown by dashed arrow 132 in Fig. 1 , respective lists of backup object types 116-4 through 116-100 as file record types which are associated with respective backup objects 136-4 through 136-100 as file records which contain the actual data. Processing then proceeds to block 208.

[0035] At block 208, management computer 102 generates a filtered list of backup object types from list of backup object types 116 based on backup policies 112. As explained above, backup polices 112 may include selection of backup objects 136 associated with the backup object types 124 that are processed by application modules 122 that require backup operations. In this example, it may be assumed that backup object types 124 that require backup operations include database record types associated with database application modules of host computers 104-1 , 104-2 104-3. In this example, three host computers 104-1 ,104-2,104-3 provided respective lists of backup object types 116-1 , 116-2, 1 16-3 associated with database record types which are associated with respective backup objects 136-1 , 136-2, 136-3 as database records which contain the actual data. On the other hand, the other computers host computers 104-4 through 104-100 provided respective lists of backup object types 116-4 through 116-100 as file record types which are associated with respective backup objects 136-4 through 136-100 as file records which contain the actual data. Therefore, in this case, management module 110 generates a filtered list of backup object types of database record types associated with host computers 104-1 , 104-2, 104-3 based on backup policies 1 12 for database record types. Processing then proceeds to block 210.

[0036] At block 210, management computer 102 sends backup modules 114 selected from a plurality of backup modules based on the filtered list to host computers 104 to perform backup operations of backup objects 136 associated with the filtered list. Continuing with the example above, management module 110 generates a filtered list of backup object types of database record types associated with host computers 104-1 , 104-2, 104-3 based on backup policies 112 for database record types. In this case, management module 110 sends backup modules 114 to host computers 104- 1 , 104-2, 104-3 to perform backup operations of backup objects 136 associated with the filtered list where the backup objects are database records. Processing then proceeds to block 212.

[0037] At block 212, management computer 102 generates a logical grouping of host computers 104 to perform backup operations on backup objects 136 based on backup policies 1 12. Continuing with the above example, management module 110 generated a filtered list of backup object types of database record types associated with host computers 104-1 , 104-2, 104-3 based on backup policies 1 12 for database record types. In this case, management module 1 10 generates a logical grouping of host computers 104-1 , 104-2, 104-3 to perform backup operations on backup objects 136 based on backup policies 112, which are in this case, database records. Processing then proceeds to block 214.

[0038] At block 214, management computer 102 sends backup commands to logical grouping of host computers to initiate performance of the backup modules 120 to perform backup operations on backup objects 136 and independently from each of the host computers directed to remote computer 106 that is separate from each of the host computers. Continuing with the above example, management module 110 generated a logical grouping of host computers 104-1 , 104-2, 104-3 to perform backup operations on backup objects 136 based on backup policies 112, which are in this case, database records. In this case, management module 110 sends backup commands to logical grouping of host computersl 04-1 , 104-2, 104-3 to initiate performance or execution of backup modules 120 to perform backup operations on backup objects 136, which are in this case, database records. In this case, management module 110 proceeds to initiate backup operations to be performed which includes having host computers 104-1 , 104-2, 104-3 begin to make copies of the database records from the host computers to remote computer 106. In this case, host computers 104-1 , 104-2, 104-3 perform backup operations independently from each of the host computers directed to remote computer 106 that is separate from each of the host computers. In this case, making copies to remote computer 106 which is separate and remote from host computers may help improve storage availability and this performance. In addition, in this example, backup policies specified that backup operations were to be performed only on database records which provides greater control over the backup process. In one example, once the backup operations have been completed, processing may then proceed back to block 202 to process further requests for backup operations.

[0039] In this manner, the techniques presented here may improve storage processing performance. For example, the techniques may help improve backup operation performance by identifying backup objects of applications across host computers to perform backup operations on the specific backup objects thereby reduce the cost and errors in the backup process. The techniques may provide policy based aggregation processing of backup operations to improve backup performance and user experience. The techniques may improve backup configuration and backup operations which may reduce the need to resort to unscrupulous system image backup thereby helping promote faster backup operations, faster restore operations, and reduction in backup operations.

[0040] It should be understood that the above process 200 is for illustrative purposes and that other implementations may be employed to the practice the techniques of the present application. For example, management module 110 may be connected to a different number of host computers 104 and process a different number of backup object types 124.

[0041] Fig. 3 is an example block diagram showing a non-transitory, computer-readable medium that stores instructions for a computer system for backup operations in accordance with an example implementation. The non- transitory, computer-readable medium is generally referred to by the reference number 300 and may be included in components of system 100 as described herein. The non-transitory, computer-readable medium 300 may correspond to any typical storage device that stores computer-implemented instructions, such as programming code or the like. For example, the non- transitory, computer-readable medium 300 may include one or more of a nonvolatile memory, a volatile memory, and/or one or more storage devices. Examples of non-volatile memory include, but are not limited to, EEPROM and ROM. Examples of volatile memory include, but are not limited to, SRAM, and DRAM. Examples of storage devices include, but are not limited to, hard disk drives, compact disc drives, digital versatile disc drives, optical drives, and flash memory devices.

[0042] A processor 302 generally retrieves and executes the instructions stored in the non-transitory, computer-readable medium 300 to operate the components of system 100 in accordance with an example. In an example, the tangible, machine-readable medium 300 may be accessed by the processor 302 over a bus 304. A first region 306 of the non-transitory, computer-readable medium 300 may include management module 110 functionality as described herein. A second region 308 of the non-transitory, computer-readable medium 300 may include backup module 114 functionality as described herein. A third region 310 of the non-transitory, computer- readable medium 300 may include backup policies 112 functionality as described herein. A fourth region 312 of the non-transitory, computer-readable medium 300 may include lists of backup object types 116 functionality as described herein.

[0043] Although shown as contiguous blocks, the software components may be stored in any order or configuration. For example, if the non- transitory, computer-readable medium 300 is a hard drive, the software components may be stored in non-contiguous, or even overlapping, sectors.

Claims

What is claimed is:

1. A method comprising:

sending discovery commands to the host computers to initiate execution of discovery modules at the host computers;

in response to the discovery commands being sent to the host computers, receive lists of backup object types from the host computers; generating a filtered list of backup object types from the list of backup object types based on backup policies;

sending backup modules selected from a plurality of backup modules based on the filtered list to the host computers to perform backup operations of backup objects associated with the filtered list;

generating a logical grouping of the host computers to perform backup operations on the backup objects based on the backup policies; and

sending backup commands to the logical grouping of host computers to initiate performance of the backup modules to perform backup operations on the backup objects and independently from each of the host computers directed to a remote computer that is separate from each of the host computers.

2. The method of claim 1 , wherein the backup object types are associated with backup objects used in the operation of the application modules that require backup operations.

3. The method of claim 1 , further comprising sending to the host computers the discovery modules to query for backup object types associated with application modules at the host computers.

4. The method of claim 1 , further comprising sending the discovery commands to the host computers to iteratively query the host computers for different backup object types and return separate lists of each of the different backup object types.

5. The method of claim 1 , wherein the backup polices include selection of backup objects associated with the backup object types that are processed by application modules that require backup operations.

6. A computer comprising:

a management module to:

send to host computers discovery modules to query for backup object types associated with application modules at the host computers,

send discovery commands to the host computers to initiate execution of the discovery modules at the host computers,

in response to receipt of lists of backup object types from the host computers responsive to the discovery commands, generate a filtered list of backup object types from the list of backup object types based on backup policies,

send backup modules selected from a plurality of backup modules based on the filtered list to the host computers to perform backup operations of backup objects associated with the filtered list, generate a logical grouping of the host computers to perform backup operations on the backup objects based on the backup policies, and

send backup commands to the logical grouping of host computers to initiate performance of the backup modules to perform backup operations on the backup objects and independently from each of the host computers directed to a remote computer that is separate from each of the host computers.

7. The computer of claim 6, wherein the backup object types are associated with backup objects used in the operation of the application modules that require backup operations.

8. The computer of claim 6, wherein the management module is further configured to check whether the host computers are authorized to perform backup operations.

9. The computer of claim 6, wherein the management module is further configured to send the discovery commands to the host computers to iteratively query the host computers for different backup object types and return separate lists of each of the different backup object types.

10. The computer of claim 6, wherein the backup polices include selection of backup objects associated with the backup object types that are processed by application modules that require backup operations.

11. An article comprising a non-transitory computer readable storage medium to store instructions that when executed by a computer to cause the computer to:

send to host computers discovery modules to query for backup object types associated with application modules at the host computers;

send discovery commands to the host computers to initiate execution of the discovery modules at the host computers;

in response to receipt of lists of backup object types from the host computers responsive to the discovery commands, generate a filtered list of backup object types from the list of backup object types based on backup policies;

send backup modules selected from a plurality of backup modules based on the filtered list to the host computers to perform backup operations of backup objects associated with the filtered list;

generate a logical grouping of the host computers to perform backup operations on the backup objects based on the backup policies; and

send backup commands to the logical grouping of host computers to initiate performance of the backup modules to perform backup operations on the backup objects and to perform the backup operations independently from each of the host computers directed to a remote computer that is separate from each of the host computers.

12. The article of claim 11 , wherein the backup object types are associated with backup objects used in the operation of the application modules that require backup operations.

13. The article of claim 11 , further comprising instructions that if executed cause a computer to check whether the host computers are authorized to perform backup operations.

14. The article of claim 11 , further comprising instructions that if executed cause a computer to send the discovery commands to the host computers to iteratively query the host computers for different backup object types and return separate lists of each of the different backup object types.

15. The article of claim 11 , wherein the backup polices include selection of backup objects associated with the backup object types that are processed by application modules that require backup operations.