An aspect of the invention relates to a method and apparatus for managing, on a computer, a plurality of backup sets of data maintained in a computer system, the data including a hierarchy of objects. In some embodiments, a graphical user interface (GUI) is displayed on a display coupled to the computer, the GUI having views configured show a first group of backup sets from the plurality of backup sets. Individual objects of a selected backup set in the first group of backup sets are pinned in a pinned view of the views in response to a first command. A second group of backup sets from the plurality of backup sets is shown in the views in response to a second command by sliding individual objects of at least one backup set in the plurality of backup sets across at least one unpinned view of the views with respect to the individual objects of the selected backup set in the pinned view.
In some embodiments, each of the views is configured to show a GUI control representing the hierarchy of objects for a respective one of the plurality of backup sets. In some embodiments, the data comprises a database of network elements in the computer system, where the hierarchy of objects including information related to at least one of: network resources, network services, or network users. In some embodiments, an additional view is displayed adjacent to the views in the GUI, where the additional view configured to show individual objects of a live copy of the data in the computer system. The individual objects of the live copy of the data in the additional view are pinned with respect to the individual objects of the at least one backup set being slid across the at least one unpinned view. In some embodiments, the individual objects of the selected backup set in the pinned view are unpinned in response to a third command subsequent to the second command. Individual objects of another selected backup set in the second group of backup sets are pinned in another pinned view of the views in response to a fourth command. In some embodiments, the individual objects of the selected backup set in the pinned view are unpinned in response to a third command subsequent to the second command. A third group of backup sets from the plurality of backup sets is shown in the views in response to a fourth command by sliding individual objects of backup sets in the plurality of backup sets across the views. Individual objects of another selected backup set in the third group of backup sets are pinned in a respective one of the views in response to a fifth command.
Another aspect of the invention relates to a method for managing, on a computer, a plurality of backup sets of data maintained in a computer system, the data including a hierarchy of objects. In some embodiments, a GUI is displayed on a display coupled to the computer, the GUI having a merged view and views configured show a first group of backup sets from the plurality of backup sets, the merged view being adjacent to the views. In response to a first command, a first object of a first backup set in the first group of backup sets as shown in a respective one of the views is selected, and a second object of a second backup set in the first group of backup sets as shown in a respective one of the views is selected. A second group of backup sets from the plurality of backup sets in the views is shown in response to a second command by sliding individual objects of backup sets in the plurality of backup sets across the views with respect to the merged view, where the first object and the second object are slid into the merged view where the first object and the second object are pinned.
In some embodiments, each of the views is configured to show a GUI control representing the hierarchy of objects for a respective one of the plurality of backup sets. In some embodiments, the data comprises a database of network resources in the computer system, and the hierarchy of objects includes information related to at least one of: network resources, network services, or network users. In some embodiments, an additional view is displayed adjacent to the merged view in the GUI, the additional view configured to show individual objects of a live copy of the data in the computer system.
So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
The client computer 102 illustratively includes a processor 118, a memory 120, various support circuits 122, an I/O interface 125. The processor 118 may include one or more microprocessors known in the art. The support circuits 122 for the processor 118 include conventional cache, power supplies, clock circuits, data registers, I/O interfaces, and the like. The I/O interface 125 may be configured for communication with the network 104. The memory 120 may include one or more of the following random access memory, read only memory, magneto-resistive read/write memory, optical read/write memory, cache memory, magnetic read/write memory, and the like.
The client computer 102 is configured with a service 116 and a backup agent 114. Each of the service 116 and the backup agent 114 may include software (e.g., program code) stored in the memory 120 and configured for execution by the processor 118. In some embodiments, the service 116 can provide any type of network service to other computers 150 on the network. The service 116 is configured to maintain a database 112 stored in the memory 120. The database 112 includes various objects. For example, the service 116 can be a domain controller, and the database 112 can include a hierarchy of objects representative of network elements on the network 104. The network elements may include network resources, network services, and/or network users. An exemplary domain controller service is MICROSOFT ACTIVE DIRECTORY. In general, the service 116 can be any type of service that maintains a database of objects, such as an e-mail service having a database of e-mail related objects, a file service having a database of files (e.g., a file system, network share, etc.), and the like. In some embodiments, the service 116 may be an operating system (OS) or the like, and the database may be a file system having files.
The backup agent 114 is configured to interact with the backup appliance 106 over the network 104 to back up the database 112 thereto. The backup agent 114 may perform such a backup operation periodically in accordance with a schedule so that several different backups of the database 112 are made.
The backup appliance 106 illustratively includes a processor 130, a memory 132, various support circuits 134, and an I/O interface 136. The backup appliance 106 may be coupled to a display 126 and various input/output devices 110. The processor 130 may include one or more microprocessors known in the art. The support circuits 134 for the processor 130 include conventional cache, power supplies, clock circuits, data registers, I/O interfaces, and the like. The I/O interface 136 may be configured for communication with the network 104, the display 126, and the input/output devices 110. The memory 132 may include one or more of the following random access memory, read only memory, magneto-resistive read/write memory, optical read/write memory, cache memory, magnetic read/write memory, and the like.
The backup appliance 106 is configured with a backup service 138. The backup service 138 may include software (e.g., program code), stored in the memory 132, configured for execution by the processor 130. The backup service 138 is configured to cooperate with backup agents to backup target data in computers. For example, the backup service 138 can cooperate with the backup agent 114 to backup the database 112. The backup service 138 may perform such backup operations in accordance with a schedule such that multiple backup sets are maintained in the memory 132 for each target data. For example, the backup service 138 may maintain backup sets 128 of the database 112.
In some embodiments, the backup service 138 includes a restore manager 140. The restore manager 140 can include software (e.g., program code), stored in the memory 132, configured for execution by the processor 130. The restore manager 140 is configured to display a graphical user interface (GUI) 108 on the display 126. An administrator may interact with the restore manager 140 through the GUI 108 and the input/output devices 110. The restore manager 140 enables comparison of individual objects of all or a portion of the backup sets 128 for the purpose of readily identifying particular objects for granular restore. In particular, the restore manager 140 enables various ones of the backup sets 128 to be pinned or repositioned and slide across the GUI 108 in order to facilitate visual comparison of individual objects across different backup sets. Exemplary embodiments of the GUI 108 and processes performed by the restore manager 140 are described below.
Although the restore manager 140 is shown as being executed by the backup appliance 106, it is to be understood that the restore manager 140 can be executed by other computers on the network 104 that have access to the backup sets 128 or data representative of the contents of the backup sets 128 stored by the backup appliance 106. For example, the restore manager 140 can be executed by the computer 102, which can be coupled to a display and input/output devices (not shown) in similar fashion to the backup appliance 106.
The method 200 begins at step 202, where the restore manager 140 displays the GUI 108 on the display 126. The GUI 108 generally includes views configured to show a group of the backup sets 128 (e.g., two of more of the backup sets 128). In some cases, there are not enough views to show all of the backup sets 128 (e.g., the group of backup sets is less than all of the backup sets 128). The restore manager 140 may initially show a first group of the backup sets 128 in the views of the GUI 108.
In the initial view, a first group of the backup sets 128 are shown in the views 306, designated as backup sets 128-1 through 128-4. Four objects of the backup set 128-1 are shown in the view 306-1, designated objects 1-4. In particular, object 1 is shown un-expanded, object 2 is shown expanded to include object 3, and object 3 is shown expanded to include object 4. Three objects of the backup set 128-2 are shown in the view 306-2, designated objects 1-3. In particular, object 1 is shown un-expanded, object 2 is shown expanded to include object 3, and object 3 is shown unexpanded. Five objects of the backup set 128-3 are shown in the view 306-3, designated objects 1-5. In particular, object 1 is shown un-expanded, object 2 is shown expanded to include object 3, and object 3 is shown expanded to include object 4, and object 5 is shown unexpanded. Four objects of the backup set 128-4 are shown in the view 306-4, designated objects 1-3 and 5. In particular, object 1 is shown un-expanded, object 2 is shown expanded to include object 3, and object 5 is shown unexpanded. The configuration of objects in the backup sets 128-1 through 128-4 is merely illustrative. Further, a backup set may include more or less than the numbers of objects shown.
The GUI 108 also includes a scroll control 307. The scroll control 307 is shown positioned under the views 306, but may be positioned anywhere within the GUI 108. The scroll control 307 is configured to receive input and, responsive to the input, forward a scroll command to the restore manager 140. The scroll command can indicate a leftward or rightward scroll. The scroll control 307 can be used to slide backup sets across the views 306 horizontally left or right. For example, the scroll control 307 may be used to slide the backup sets 128-2, 128-3, and 128-4 from the views 306-2, 306-3, and 306-4 to the views 306-1, 306-2, and 306-3 in response to a left scroll request. The backup set 128-1 in the view 306-1 is hidden from view, and the view 306-4 would show a previously hidden backup set (if any). In this manner, all of the backup sets 128 may be viewed within the four views 306-1 through 306-4. Those backup sets 128 hidden from view may be displayed by using the scroll control 307. Those of the backup sets 128 shown in the views 306 are referred to as a group of backup sets. As shown in
In some embodiments, the GUI 108 may be configured with a live view 310. The live view 310 can include a header 312, with a label therein (e.g., “live view” is shown). The live view 310 can show the current state of the database 112 that is the target of the backup sets 128 (e.g., a live copy of the database 112). In particular, the live view 310 can include a GUI control 314, similar to the GUI controls 308. In the present example, the live view 310 shows three objects 1, 2, and 5 of the database 112. The individual objects of the database 112 can be pinned in the live view 312. In this manner, an administrator can pin and slide different backup sets and compare such backup sets to a live copy of the database 112. Such a comparison can facilitate restore of particular objects to the database 112.
In some embodiments, each of the views 306 can show all objects of a respective one of the backup sets 128. In other embodiments, each of the views 306 can show less than all of the objects of a respective one of the backup sets 128. For example, in some embodiments, the views 306 may be configured to show only those objects of the respective backup sets that are different from objects currently stored in the database 112. Thus, objects in the backup sets that are the same as the objects currently in the database 112 may be hidden from view. The views 306 may be configured to only show the different objects either with the GUI 108 having the live view 310 or with the GUI 108 not having the live view 310. Such filtering of objects can result in the views 306 having less objects being shown.
In some embodiments, differences between objects in different backup sets across the views 306 can be emphasized. For example, in a scenario described above, the views 306 can be configured to show only those objects in the respective backup sets that are different from the current database 112. In a further refinement, objects between multiple backup sets in the views 306 that are the same (but also different from the live database 112) can be de-emphasized (e.g., grayed out or the like), and/or objects between multiple backup sets in the views 306 that are different can be emphasized (e.g., highlighted, bolded, and the like). The above emphasis/de-emphasis scenario may also be employed if the views 306 are configured to show all of the objects, rather than just the different objects from the live database 112.
Returning to
Referring again to
For example,
By pinning one or more backup sets, and sliding one or more backup sets leftward or rightward, an administrator can efficiently compare the individual objects of different backup sets with one another. For example, an administrator may want to compare the objects in one backup set with objects of other backup sets, including those hidden from display at any one time. Since the selected backup set can be pinned, other backup sets can be slid across the unpinned views to display hidden backup sets without hiding the selected backup set.
Returning to
In the embodiments described above, the GUI 108 has been shown as having columnar views across which the backup sets can be pinned and slid horizontally. It is to be understood that the views of the GUI 108 can be configured in different arrangements. For example, the views can be rows and backup sets can be pinned and slid vertically across rows. In another example, the views can be multidimensional. For example, views can be arranged in a rectangular grid of columns and rows and can be pinned and scrolled in both horizontal and vertical directions. In other embodiments, rather than having the backup set adjacent to a pinned backup set disappear from view after a scroll command, the adjacent backup set can be shown with the pinned backup set using data overlay and transparency GUI features. For example, the pinned backup set can overlay another backup set that has been slid into the respective pinned view.
The method 400 begins at step 402, where the restore manager 140 displays the GUI 108 on the display 126. The GUI 108 generally includes views configured to show a group of the backup sets 128 (e.g., two of more of the backup sets 128). In some cases, there are not enough views to show all of the backup sets 128 (e.g., the group of backup sets is less than all of the backup sets 128). The restore manager 140 may initially show a first group of the backup sets 128 in the views of the GUI 108. The GUI 108 further includes a merged view. The merged view can be initially empty. As discussed below, after a scroll operation, the merged view can include objects from different backup sets. The GUI 108 may also show a live view, as described above.
Returning to
The method 400 proceeds from step 404 to step 406. At step 406, the restore manager 140 shows a second group of backup sets in response to a scroll command. The restore manager 140, in response to the scroll command, slides individual objects of backup sets across the views with respect to the merged view. As the backup sets are slid, any selected objects are slid into the merged view and are thereafter pinned in the merged view.
In this manner, an administrator can select different objects from different backup sets and relate them into a merged backup set by selecting and sliding, as described above. The administrator can pick and choose different objects from different backup sets, have them all stored in the merged view, and then restore from the merged view.
Aspects of the methods described above may be implemented as a program product for use with a computer system. Program(s) of the program product defines functions of embodiments and can be contained on a variety of computer readable media, which include, but are not limited to: (i) information permanently stored on non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM or DVD-ROM disks readable by a CD-ROM drive or a DVD drive); and (ii) alterable information stored on writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive or read/writable CD or read/writable DVD). Such computer readable media, when carrying computer-readable instructions that direct functions of the invention, represent embodiments of the invention.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
1. Field of the Invention This application is a continuation of U.S. patent application Ser. No. 12/415,900, entitled “Method and Apparatus for Simultaneous Comparison of Multiple Backup Sets Maintained in a Computer System” filed Mar. 31, 2009 now U.S. Pat. No. 8,219,528 and naming Christopher Greene, Kirk Freiheit as the inventors. This application is assigned to Symantec Corporation, the assignee of the present invention, and is hereby incorporated by reference in its entirety and for all purposes as if completely and fully set forth herein. The present invention relates generally to computer systems. More particularly, the present invention relates to method and apparatus for simultaneous comparison of multiple backup sets maintained in a computer system. 2. Description of the Related Art Computer systems typically include many computers coupled to a network. For data protection, such computer systems can include one or more backup appliances for backing up data stored on the computers. For example, a computer network may include a server configured to manage a domain in the computer system (referred to as a “domain controller”). The domain controller is configured to store information about network resources of the domain in a database. The database can include a hierarchical structure of objects that represent these network resources. A backup appliance can be configured to backup the database of the domain controller. Typically, the backup appliance would perform such a backup task periodically according to a schedule. As such, the backup appliance can maintain several different copies of the backed up data (referred to as “backup sets”). A database of a domain controller is just one example of a type of data that can be backed-up in a computer system. For example, other types of databases can be backed-up, such as e-mail databases and the like. In another example, other types of data can be backed-up, such as file systems, disk images, and the like for various workstation computers in the computer system. A backup appliance can restore backed-up data to a target computer in the computer system. In cases where multiple backup sets are maintained, an administrator must select an appropriate backup set to restore. In some cases, the entire backup set is restored (“complete restore”). In other cases, only some objects in a backup set need to be restored (“granular restore”). A backup set may include a large number of objects. Thus, for a granular restore, an administrator might have to search through and compare a large number of objects across many backup sets to search for particular versions of the objects to be restored. This searching and comparison can be time consuming and error prone.
Number | Name | Date | Kind |
---|---|---|---|
4533296 | Duchesneau et al. | Aug 1985 | A |
4891625 | VanRiper et al. | Jan 1990 | A |
5155824 | Edenfield et al. | Oct 1992 | A |
5208781 | Matsushima | May 1993 | A |
5469565 | Hibi | Nov 1995 | A |
5497483 | Beardsley et al. | Mar 1996 | A |
5506580 | Whiting | Apr 1996 | A |
5532694 | Mayers et al. | Jul 1996 | A |
5574874 | Jones et al. | Nov 1996 | A |
5611042 | Lordi | Mar 1997 | A |
5644766 | Coy et al. | Jul 1997 | A |
5649152 | Ohran et al. | Jul 1997 | A |
5778395 | Whiting | Jul 1998 | A |
5835953 | Ohran | Nov 1998 | A |
5907672 | Matze et al. | May 1999 | A |
5943335 | Dilley et al. | Aug 1999 | A |
5948055 | Pulsipher et al. | Sep 1999 | A |
5991240 | Van Ryzin | Nov 1999 | A |
6061770 | Franklin | May 2000 | A |
6073222 | Ohran | Jun 2000 | A |
6085298 | Ohran | Jul 2000 | A |
6141734 | Razdan et al. | Oct 2000 | A |
6154694 | Aoki et al. | Nov 2000 | A |
6189079 | Micka et al. | Feb 2001 | B1 |
6212531 | Blea et al. | Apr 2001 | B1 |
6253193 | Ginter et al. | Jun 2001 | B1 |
6282610 | Bergsten | Aug 2001 | B1 |
6341341 | Grummon et al. | Jan 2002 | B1 |
6353878 | Dunham | Mar 2002 | B1 |
6363488 | Ginter et al. | Mar 2002 | B1 |
6389402 | Ginter et al. | May 2002 | B1 |
6401098 | Moulin | Jun 2002 | B1 |
6427140 | Ginter et al. | Jul 2002 | B1 |
6434681 | Armangau | Aug 2002 | B1 |
6460054 | Grummon | Oct 2002 | B1 |
6550057 | Bowman-Amuah | Apr 2003 | B1 |
6564301 | Middleton | May 2003 | B1 |
6591351 | Urabe et al. | Jul 2003 | B1 |
6643667 | Arai et al. | Nov 2003 | B1 |
6721766 | Gill et al. | Apr 2004 | B1 |
6760746 | Schneider | Jul 2004 | B1 |
6771843 | Huber et al. | Aug 2004 | B1 |
6785789 | Kekre et al. | Aug 2004 | B1 |
6792518 | Armangau et al. | Sep 2004 | B2 |
6961838 | Reuter et al. | Nov 2005 | B2 |
6996687 | Kekre et al. | Feb 2006 | B1 |
7350042 | Kekre et al. | Mar 2008 | B1 |
7412433 | Anglin et al. | Aug 2008 | B2 |
7447729 | Thakur et al. | Nov 2008 | B1 |
7603618 | Mori et al. | Oct 2009 | B2 |
7657582 | Cram et al. | Feb 2010 | B1 |
7693878 | Anglin et al. | Apr 2010 | B2 |
7856424 | Cisler et al. | Dec 2010 | B2 |
7886048 | Holland et al. | Feb 2011 | B1 |
7904425 | Cannon et al. | Mar 2011 | B2 |
7966293 | Owara et al. | Jun 2011 | B1 |
8108494 | Holland et al. | Jan 2012 | B1 |
8219528 | Greene et al. | Jul 2012 | B1 |
8463798 | Claudatos et al. | Jun 2013 | B1 |
8489817 | Flynn et al. | Jul 2013 | B2 |
8548940 | Rajaram et al. | Oct 2013 | B1 |
8676809 | Naftel | Mar 2014 | B1 |
8706833 | Bergant et al. | Apr 2014 | B1 |
8738669 | Hsu et al. | May 2014 | B1 |
8762429 | Reeves et al. | Jun 2014 | B1 |
20020120685 | Srivastava et al. | Aug 2002 | A1 |
20030041220 | Peleska | Feb 2003 | A1 |
20050228961 | Reuter et al. | Oct 2005 | A1 |
20050237572 | Mori et al. | Oct 2005 | A1 |
20050246631 | Mori et al. | Nov 2005 | A1 |
20070136381 | Cannon et al. | Jun 2007 | A1 |
20080034307 | Cisler et al. | Feb 2008 | A1 |
20080177994 | Mayer | Jul 2008 | A1 |
20080243958 | Prahlad et al. | Oct 2008 | A1 |
20080307019 | Weiss et al. | Dec 2008 | A1 |
20090089341 | Skaria et al. | Apr 2009 | A1 |
20090164527 | Spektor et al. | Jun 2009 | A1 |
20090199133 | Deutsch et al. | Aug 2009 | A1 |
20090248737 | Shukla et al. | Oct 2009 | A1 |
20100070491 | Cragun et al. | Mar 2010 | A1 |
20110219035 | Korsunsky et al. | Sep 2011 | A1 |
20130036088 | Orenstein et al. | Feb 2013 | A1 |
Entry |
---|
Chen, Gwo-Dong, and Tai-Ming Parng. “A database management system for a VLSI design system.” In Proceedings of the 25th ACM/IEEE Design Automation Conference, pp. 257-262. IEEE Computer Society Press, 1988. |
Number | Date | Country | |
---|---|---|---|
Parent | 12415900 | Mar 2009 | US |
Child | 13544602 | US |