US20130212599A1 - Event notification management - Google Patents
Event notification management Download PDFInfo
- Publication number
- US20130212599A1 US20130212599A1 US13/724,148 US201213724148A US2013212599A1 US 20130212599 A1 US20130212599 A1 US 20130212599A1 US 201213724148 A US201213724148 A US 201213724148A US 2013212599 A1 US2013212599 A1 US 2013212599A1
- Authority
- US
- United States
- Prior art keywords
- event
- event notifications
- combined
- notifications
- queue
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1461—Backup scheduling policy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/81—Threshold
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/86—Event-based monitoring
Definitions
- the disclosed implementations relate generally to storing and restoring data.
- a hallmark of modern graphical user interfaces is that they allow a large number of graphical objects or items to be displayed on a display screen at the same time.
- Leading personal computer operating systems such as Apple Mac OS®, provide user interfaces in which a number of windows can be displayed, overlapped, resized, moved, configured, and reformatted according to the needs of the user or application.
- Taskbars, menus, virtual buttons and other user interface elements provide mechanisms for accessing and activating windows even when they are hidden behind other windows.
- the revision process is usually straightforward if the user wants to add more material to the file or make changes to what is there. But it is typically more difficult for a user who has changed his/her mind about changes that were previously made and wants the file back as it was once before.
- Application programs for word processing typically let the user “undo” previous edits of a text, at least up to a predefined number of past revisions.
- the undo feature also usually is configured so that the previously made revisions must be undone in reverse chronological order; that is, the user must first undo the most recently made edit, then the second-most recent one, and so on. If the user saves and closes the document and thereafter opens it again, it may not be possible to automatically undo any previous edits.
- Virtually all computer systems generate event information of some form during operation.
- “file system events” are used in the Apple Mac OS® X (a corresponding PC version is NT ChangeLog) to provide event notifications for all file system activity (e.g., add file, change file, delete file, etc).
- Some event information can generate a large data stream, and the capacity to store event notifications can be limited. Additionally, a particular event can require some action by the system and can therefore block the flow of events. To address this situation, event notifications are sometimes dropped to make room for incoming events.
- Events such as file changes
- the event notifications from these events can be used, for example, by a backup system to identify changed data for the next incremental backup operation.
- the number of event notifications can be limited, leading to dropped events. Dropped events prevent the system from knowing what was changed without searching everything (e.g., searching an entire file system).
- the loss can be limited by managing the event notifications to combine the event notifications as necessary to maintain space for new incoming events. For example, event notifications for changes to files in a same folder can be combined to a single event notification at a parent level (e.g., a folder that contains the files) to reduce space. Only that parent will need scanned or otherwise examined to determine the changed files instead of the entire file system.
- a method is provided. A determination is made as to whether a threshold associated with pending event notifications has been exceeded by an incoming event notification. A plurality of pending event notifications that can be combined are identified. Two or more event notifications are combined.
- Each event notification can identify a change to an entry in a data system.
- Each event notification can be associated with one or more parent levels of a hierarchical file system and identifying event notifications that can be combined comprises determining two or more event notifications having a common parent level. Combining two or more event notification can include replacing two or more event notifications with a single event notification identifying a change to the common parent level.
- the method can further include scanning the common parent level to identify the combined event notifications and performing a backup operation including backup data associated with the combined event notifications. Scanning the common parent level can include comparing the parent data with data from a previous backup to identify changed data.
- Receiving an incoming event notification can include receiving an event notification identifying a change to a file system at an event notification queue.
- the method can further include identifying one or more event notifications as protected, where protected event notifications can not be combined.
- the method can further include determining a number of event notifications to combine according to one or more criteria.
- the criteria can include minimizing a number of combined event notifications. Minimizing the number of combined event notifications can include combining a minimum number of event notifications such that the incoming event notification does not exceed the threshold.
- a system in one aspect, includes a monitoring engine for monitoring incoming event notifications.
- the system includes an event notification queue and an event combiner for combining event notifications in the event notification queue.
- the system also includes an event notification manager.
- a method is provided. A determination of whether a backup event has occurred is made. Event notifications are evaluated. A backup is generated according to the event notifications. Evaluating event notifications can include identifying an event notification that is a combination of two or more event notifications and scanning data associated with the event notification to identify the combined event notifications.
- the system can combine event notifications in order to reduce dropped event notifications. By combining events, the original event notifications can be more easily identified.
- FIG. 1 is a block diagram of an example of an architecture for tracking file system events.
- FIG. 2 is a block diagram of an example of an architecture of an event managing component.
- FIG. 3 is a flow chart of exemplary operations that can be performed to store an event notification.
- FIG. 4 is a flow chart of exemplary operations that can be performed to process event notifications.
- FIG. 5 is a block diagram of an example of an architecture for backing up and restoring application files.
- FIG. 6 is a screen shot showing a time machine interface.
- FIG. 1 is a block diagram of an architecture 100 that manages generated event notifications and handles them accordingly.
- an event notification corresponds to activity related to one or more data elements within a computer system.
- the architecture 100 includes a personal computer 102 communicatively coupled to a remote server 107 via a network interface 116 and a network 108 (e.g., local area network, wireless network, Internet, intranet, etc.).
- the computer 102 generally includes a processor 103 , memory 105 , one or more input devices 114 (e.g., keyboard, mouse, etc.) and one or more output devices 115 (e.g., a display device).
- a user interacts with the architecture 100 via the input and output devices 114 , 115 .
- Architecture 100 as disclosed includes various hardware elements. Architecture 100 can include hardware, software, and combinations of the two.
- the computer 102 also includes a local storage device 106 and a graphics module 113 (e.g., graphics card) for storing information and generating graphical objects, respectively.
- the local storage device 106 can be a computer-readable medium.
- the term “computer-readable medium” refers to any medium that includes data and/or participates in providing instructions to a processor for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media.
- Transmission media includes, without limitation, coaxial cables, copper wire, fiber optics, and computer buses. Transmission media can also take the form of acoustic, light or radio frequency waves.
- event management is described herein with respect to a personal computer 102 , it should be apparent that the disclosed implementations can be incorporated in, or integrated with, any electronic device that has a user interface, including without limitation, portable and desktop computers, servers, electronics, media players, game devices, mobile phones, email devices, personal digital assistants (PDAs), embedded devices, televisions, other consumer electronic devices, etc.
- portable and desktop computers servers, electronics, media players, game devices, mobile phones, email devices, personal digital assistants (PDAs), embedded devices, televisions, other consumer electronic devices, etc.
- PDAs personal digital assistants
- Systems and methods are provided for managing events regarding system information, application information or system, application, or user interface state.
- the systems and methods can be stand alone, or otherwise integrated into a more comprehensive application.
- an integrated system and method for event management is disclosed.
- the engines, methods, processes and the like that are described can themselves be an individual process or application, part of an operating system, a plug-in, an application, or the like.
- the system and methods can be implemented as one or more plug-ins that are installed and run on the personal computer 102 .
- the plug-ins are configured to interact with an operating system (e.g., MAC OS® X, WINDOWS XP, LINUX, etc.) and to perform the various functions, as described with respect to the Figures.
- a system and method for modifying a user interface view can also be implemented as one or more software applications running on the computer 102 .
- a view refers to an item, element, or other content, capable of being presented in a user interface, that can be subjected to a backup operation by a backup component 117 .
- a user interface view can contain any number of icons, files, folders, application state information and/or machine state information, etc.
- Such a system and method can be characterized as a framework or model that can be implemented on various platforms and/or networks (e.g., client/server networks, wireless networks, stand-alone computers, portable electronic devices, mobile phones, etc.), and/or embedded or bundled with one or more software applications (e.g., email, media player, browser, etc.).
- the computer 102 includes a backup component 117 that allows for the storage of versions of the computer's files or other items, for example within the local storage 106 or in an external storage repository.
- the backup component 117 captures versions of one or more interface views and manages an archive of such backups, for example to facilitate user-initiated restoration based on any of them.
- a view refers to an item, element or other content, capable of being presented in a user interface, that can be subjected to a backup operation by the backup component 117 .
- a user interface view can contain any number of icons, files, folders, application state information, and/or machine state information, etc.
- the backup component 117 also allows a user to select any of the stored versions and use it to initiate a restoration of that version in the computer 102 .
- An event managing component 118 monitors and manages events within the computer 102 .
- events can be generated by one or more event logging tools.
- the event logging tool is a file system event tool such as FS Events (available in products from Apple Computer in Cupertino, Calif.).
- the event managing component 118 stores and manages the event notifications as will be described below.
- the backup component 117 can use a compiled list of events to determine which changed elements should be archived.
- FIG. 2 is a block diagram of an architecture 200 with examples of features that can be included in the event managing component 118 .
- the event managing component 118 here contains a monitoring engine 202 , an event notification queue 204 , a combining engine 206 , and an event notification manager 208 .
- An exemplary operation of the event managing component 118 is as follows.
- the monitoring engine 202 captures a new event that is to be forwarded for storage in the event notification queue 204 until it can be processed. If the event notification manager 208 recognizes that the event notification queue 204 is reaching capacity, the event notification manager 208 can instruct the combining engine 206 to combine two or more of the events into a combined event to save capacity in the event notification queue 204 .
- the system can scan the identified directory or folder to identify the changes that were made.
- the monitoring engine 202 detects incoming event notifications.
- the event notifications originate from a file system activity monitor.
- An event can occur to a file, folder, data set, system setting, state information, or other individual data element within a computer system. Events include, but are not limited to, element addition, element modification, element deletion, etc.
- the monitoring engine 202 sends the incoming events for storage processing. If there is currently sufficient capacity in the event notification queue 204 , the detected events remain stored there. In contrast, if the event notification queue 204 currently has insufficient capacity, a check is made to determine whether two or more events can be combined. For example, if the event notification queue 204 is above a set threshold capacity, automatic combining of events can help clear space within the queue.
- the event notification queue 204 When the event notification queue 204 receives an incoming event, it is first determined whether the event notification queue has the capacity to add the new notification. In one implementation, the capacity determination is made by the event notification queue 204 and the results forwarded to the event notification manager 208 . In another implementation, the capacity determination is made by the event notification manager 208 acting on event volume information received from the event notification queue 204 .
- Events can be removed from the event notification queue 204 by processing the events stored within the queue. For example, after the backup component 117 uses the events stored within the event notification queue 204 to create a new archive view, the information within the event notification queue is no longer needed. Events can also be removed from the event notification queue by creating a combined event. In one implementation, all events covered by the scope of the combined event are deleted from the queue upon the addition of the combined event. Thereafter, individual events can be rediscovered by scanning the structure shared by the combined events, such as a parent folder.
- the combining engine 206 can first attempt to find one or more events within the event notification queue 204 that can be combined with a newly received event. As another example, the combining engine 206 can attempt to find two or more events within the event notification queue 204 that can be combined with each other, to free up resources for handling the newly received event. Thus, in the latter situation, the newly received event is not included in the event combination.
- the combining engine 206 can take into account one or more protection levels in attempting to combine event notifications. That is, one or more event notifications can be identified as protected, meaning that the event notification(s) can not be combined with other event notifications. For example, the protection can be set for those event notifications that can be expected to create worse problems than other event notifications if they are lost before they can be processed.
- one or more events can be dropped based on a prioritization scheme. For example, it can be considered critical not to lose a file renaming event, because it can later lead to anomalies and be very difficult to detect. Such critical events can be identified as protected event notifications, which are not combinable. In contrast, a regularly scheduled status update can sometimes be lost without causing significant problems. In one implementation, non-critical events can be dropped in these or other situations. In the later event of queue processing, the backup component 117 will need to scan globally for all element changes in addition to using the critical events contained within the event notification queue 204 .
- the combining engine 206 can be triggered by the event notification manager 208 to combine individual events within the event notification queue 204 .
- the combining engine is activated when the event notification queue 204 is at maximum capacity.
- the event notification queue 204 has a threshold level determining when to engage the combining engine 206 .
- the scope of combining activity is based upon system or user settings. For example, the combining engine 206 can begin combining events in no particular order until a queue threshold level has been met. In another implementation, the combining engine 206 can seek out the combinations that are more preferable to make. For example, it could be preferable to combine events that have a high degree of common hierarchical parentage, such as by being related to the same structure in the hierarchy. In contrast, it could be less preferable to combine events that are more unrelated to each other in the hierarchy. This is because the scope and amount of scanning needed in the former case can be less than that necessary in the latter case.
- the combining engine 206 scans the event notification queue 204 and analyzes the events to determine whether two or more events are combinable. For example, the combining engine 206 can look for elements that share a common feature, such as a parent directory. The combining engine 206 then creates a new combination event regarding the common feature. The combining engine 206 drops the individual events comprising the new combination event from the event notification queue 204 and replaces them with the combination event. In some implementations, the combining engine 206 merges the involved events to form the combined event.
- the event notification manager 208 manages the operation of the monitoring engine 202 and the combining engine 206 .
- the event notification manager 208 can monitor the status of the event notification queue 204 .
- the event notification manager 208 instructs the combining engine 206 to combine events.
- the event notification manager 208 contains a set of values relating to the trigger events for the combining engine 206 .
- the set of values can contain a queue threshold value at which combination of events should occur.
- the set of values can also include a lower threshold value at which the combining engine 206 should cease the combining operation.
- the event notification manager 208 in one implementation, triggers the removal of unnecessary event notifications, for example, after the contents of the event notification queue 204 have been processed by the backup component 117 .
- the shared feature listed within each combination event can be perused to determine which elements within that shared feature have undergone changes. For example, if the event combination involved two events relating to changes in two images located in the same photo album, the combined event can identify the photo album as a general indication that two or more system events relating to that album have been dropped. In the event processing, then, the album contents can be scanned (or otherwise analyzed) to determine what events relating to the album need to be rediscovered. Upon determining, in this example, that the dropped events related to changes in two of the images, the event managing component 118 can process these rediscovered events similarly to a scenario where they had not been dropped.
- the processing of events can include interaction with the backup component 117 .
- the event managing component 118 can trigger the backup component 117 to create new backup versions of the altered images.
- the combining engine 206 can also prune events from the event notification queue 204 .
- the combining engine 206 can scan the event notification queue 204 for multiple events that occurred to the same element, because such events can render each other superfluous or moot, at least in part. For example, adding a new element and then deleting the same element is an example of two events that effectively cancel each other out. In another example, successive additions to a text file can be pruned to a single modification event. Thus, the combining engine 206 can drop one or more events as redundant.
- FIG. 3 is a flow chart of exemplary operations 300 that can be performed in relation to event generation and management.
- the operations begin in step 302 with receiving an incoming event notification.
- the event notification can be detected by the monitoring engine 202 ( FIG. 2 ).
- the incoming event in one example, originates from a file system event logging tool.
- step 304 the operation determines whether the addition of the incoming event notification exceeds a threshold value associated with the event queue. For example, this determination can be made by the event notification queue 204 ( FIG. 2 ). In another implementation, the threshold capacity can be detected by the event notification manager 208 ( FIG. 2 ). If the answer in step 304 is yes, then combinable event notifications are identified in step 306 . For example, event notifications are combinable if they have a shared feature, e.g., a shared parent directory or other hierarchical structure, such that by scanning the shared feature, all of the combinable event elements can be located within that feature. In one implementation, the combining engine 206 ( FIG. 2 ) locates combinable events.
- a shared feature e.g., a shared parent directory or other hierarchical structure
- the operation can first attempt to identify any elements that share the same parent structure. If there are no such events, or if the combination thereof does not free up sufficient space in the notification queue, the operation can then move up a hierarchical tree, determining potential combinations among two or more events that share relatively less commonality that those considered earlier.
- the number of event notifications to combine can be determined, in step 308 .
- the operation desires to combine a sufficient number of events such that an incoming event notification will not exceed the queue threshold.
- the number of event notifications to combine can, in one implementation, be based on default or user settings.
- the event notification manager 208 can contain a lower threshold setting that is the goal for the combining engine 206 when combining events.
- the order of steps 306 and 308 can be reversed.
- event notifications are combined.
- the combining engine 206 can combine the most recently received event notification with one or more previously received ones.
- notification events can be combined with previously combined events, or previously combined events can be combined with each other, to create additional combination events at a higher hierarchical level.
- a new event notification is generated and used as the combined event, in other implementations one of the events being combined is modified to be the combined event.
- the system can scan (e.g., prior to initiating a backup operation) the particular structure (e.g., folder, directory, or other hierarchical level) that includes combined event notifications in order to determine the underlying events. For example, if two file events were combined into a single folder event notification, the folder is examined to identify which files were the source of the file events that have been lost. In one implementation, the system can compare the folder data with an archive version (e.g., from a previous backup operation) in order to determine which files have changed data, indicating they were the source of the combined file event notifications.
- an archive version e.g., from a previous backup operation
- step 312 the incoming event notification is added to the notification queue.
- the newly received notification can be added without modification.
- the notification that is added in step 312 can be a combined event resulting from the steps 306 - 310 .
- the event notification manager 208 adds the incoming event to the event notification queue 204 .
- FIG. 4 is a flow chart of exemplary operations 400 that can be performed in relation to event generation and management.
- the operations 400 can be performed in processing a queue of event notifications that could include one or more combined event notifications.
- the operations 400 can be performed in an attempt to rediscover that missing information so that the events can be processed.
- the operations begin at step 402 with the initiation of the processing of event notifications. For example, this can involve initiating the event managing component 118 ( FIG. 1 ). As has been mentioned, the event managing component 118 can process event notifications that are stored in a queue.
- step 404 it is determined, for each event notification, whether the notification is a combination of two or more event notifications. If so, the operation scans the area implicated by the combined events, in step 406 . For example, when two events relating to the same folder are combined, information about the events can be lost. Although the specifics of the events are no longer known, it is known that they related to a particular folder. The folder can then be considered a hierarchical region that is implicated by these combined events. The system can attempt to rediscover the missing information by scanning the folder. For example, the event managing component 118 can scan each element within the hierarchical region implicated by the combined event, such as by comparing each element's timestamp to the timestamp of the previously generated backup version. In another implementation, the backup component 117 compares the contents of the hierarchical region to the contents of that region within the previously generated backup version to determine the change(s). Other approaches can be used to rediscover the lost event notifications.
- the operation identifies all changed elements within the implicated area. For example, changes can include added data elements, modified data elements, and deleted data elements, etc.
- the operation then processes the identified change(s) in step 410 .
- the change(s) processed in step 410 can be from a non-combined event following the determination in step 404 , or from two or more previously combined events that were rediscovered in steps 406 - 408 .
- the backup component 117 can use the list of changed elements to generate a new backup version of each element.
- step 412 If, at step 412 , it is found that this is not the last event notification in the list, the operation returns to step 404 to process at least one more event notification. If, instead, this is the last notification to be processed, the operation ends.
- the event notification manager at the termination of the event processing operation, the event notification manager ( 208 ) can trigger the cleaning of the event notification queue 204 to clear it of all stored events.
- the operations 400 can be repeated in part or in whole as required.
- FIG. 5 is a block diagram of an exemplary architecture 201 for enabling the back up and restoration of data (e.g., application files, application data, settings, parameters or the like), such as those associated with a set of application programs 228 .
- Backup component 117 provides back up and restoration capability for the system.
- Many different items or elements can be the subject of a backup operation in the system. For example, folders, files, items, information portions, directories, images, system or application parameters, playlists, e-mail, inbox, application data, address book, preferences, and the like all can be candidates for archiving. Other types are also possible.
- the backup component 117 includes at least one storage device 232 .
- This can be an internal or external resource, or a combination of the two. Any number of local and/or external storage devices can be used by the backup component 117 for storing versions.
- the backup component 117 views any and all storage device(s) designated for version storage as a single memory bank.
- the backup component 117 runs as a background task on an operating system 230 , such that the task is not visible to the user.
- the backup component 117 can be capable of running across multiple user accounts.
- the backup component 117 includes an activity monitoring engine 212 .
- the activity monitoring engine 212 monitors for changes within an application view (e.g. files) that are targeted for a backup operation. A change can also include the addition of new files or data or the deletion of the same.
- the activity monitoring engine 212 is capable of discerning between a substantive change (e.g. the text within a document has been modified) and a non-substantive change (e.g. the play count within an iTunes playlist has been updated, or several changes cancel each other out) through its interaction with the application programs 228 .
- the activity monitoring engine 212 can, for example, create a list of modified elements to be used when a backup event is eventually triggered.
- the activity monitoring engine 212 can monitor the system for periods of inactivity. The activity monitoring engine 212 can then trigger a backup event during a period of time in which the backup operation will not cause a system slowdown for an active user.
- a preference management engine 214 specifies some operating parameters of the backup component 117 .
- preference management engine 214 contains user-specified and/or system default application parameters for the backup component 117 . These can include settings for the details of capturing and storing the earlier versions. For example, the preference management engine 214 can determine the frequency of the backup capture, the storage location for the backup versions, the types of files, data, or other items that are eligible for backup capture, and the events which trigger a backup capture (periodic or event-driven, etc.).
- the preference management engine 214 can detect that a new storage device is being added to the system and prompt the user whether it should be included as a backup repository.
- Files and other items can be scheduled for a backup operation due to location (e.g. everything on the C: drive and within D:/photos), a correlation with specific applications (e.g. all pictures, music, e-mail, address book, preferences, and system settings), or a combination of strategies. Different types of items can be scheduled to be stored on different devices or on different segments of a storage device during a backup operation.
- the backup component 117 stores the versions in a format corresponding to a file system structure.
- a backup management engine 216 coordinates the collection, storage, and retrieval of view versions performed by the backup component 117 .
- the backup management engine 216 can trigger the activity monitoring engine 212 to watch for activities that satisfy a requirement specified in the preference management engine 214 .
- a change identifying engine 218 locates specific views or other items within to determine if they have changed.
- the change identifying engine 218 can be capable of discerning a substantive change from a non-substantive change, similar to the example described above for the activity monitoring engine 212 .
- the change identifying engine 218 traverses a target set of files, data, or other items, comparing a previous version to the current version to determine whether or not a modification has occurred.
- a backup capture engine 220 locates files, data, or other items that are to be backed up.
- the backup capture engine 220 can invoke the activity monitoring engine 212 and/or the change identifying engine 218 , for example, to generate a capture list.
- the backup capture engine 220 can then store copies of these elements in one or more targeted storage repositories.
- the backup capture engine 220 can track multiple version copies of each item included in the backup repository.
- the backup component 117 includes a backup restoration engine 222 to restore previous views (e.g. versions of files, data, or other items).
- the backup restoration engine 222 provides a user interface (e.g., a graphical user interface) where a user can select the item(s) to be restored.
- a device management engine 224 handles the addition and removal of individual storage devices to be used for archiving views.
- the preference management engine 214 obtains user settings regarding the identification of individual storage devices for use in archiving. These settings could include, but are not limited to, particular segments of individual devices to use, a threshold capacity which can be filled with archive data, and individual applications to archive to each device.
- the device management engine 224 records the storage device settings obtained by the preference management engine and uses them to monitor storage device activity.
- the device management engine 224 can alert the user when a new device has been added to the system.
- the device management engine 224 can alert the user when an archive-enabled device has been removed from the system.
- the device management engine 224 can alert the user when an archive-enabled device is nearing its threshold storage capacity setting.
- An archive management engine 226 tracks where archived views are being stored.
- the archive management engine 226 obtains user options from the preference management engine.
- Such settings can include, but are not limited to, methods to be used to remove older or otherwise unnecessary archived views. These settings can establish criteria for archived view deletion, for instance in the event of storage capacity being reached or on a regular basis.
- the archive management engine 226 alerts the user when archives are missing because a device has gone offline.
- the archive management engine 226 bars a user from viewing another user's archived data due to system permissions settings.
- the first external storage device 232 is being used by the backup component 117 for archiving.
- the first device 232 contains an initial backup version 234 , which is the first archived view created within this device for a particular item.
- the first device 232 also contains an incremental update 236 .
- the incremental update 236 contains links back to data stored within initial backup 234 , such that only one copy of an unchanged piece of data is retained. In this manner, links can also exist between incremental updates.
- Each incremental update can then contain a copy of each new or changed data item plus a link back to a previously stored copy of each unchanged data item. Any number of incremental updates can exist. If the user changes the scope of data that is being backed up from one incremental update period to another so that the scope of data now includes new data areas, a portion of an incremental update can be considered similar to an initial backup version. Other archive management techniques could be used.
- the backup component 117 can use information stored by the event managing component 118 during incremental backup creation. For example, as described with reference to FIG. 4 , events stored by the event managing component 118 can provide the backup component 117 with a list of changed elements since the last incremental backup event. In some implementations, the backup component 117 includes some or all portions of the event managing component 118 . In another implementation, the event managing component 118 includes some or all portions of the backup component 117 .
- any number of storage devices can be used by the backup component.
- different storage devices contain the backup version and incremental updates of data belonging to different applications or to different users on the system.
- two or more storage devices can be responsible for backing up contents from separate applications in the system.
- the archived copies can be compressed and/or encrypted.
- An example of a compression technique is the ZIP file format for data compression and archiving.
- An example of an encryption technique is the RSA algorithm for public key encryption. Other compression techniques or encryption techniques could be used.
- each user can select to keep separate archives. Access to an individual user's archives can be password protected or otherwise held in a secure manner.
- the archive storage structure mimics a typical file system structure, such that the archived versions can be perused using a standard file system viewing utility.
- the backup component 117 can be used for selective restoration of a captured backup version, or a portion thereof.
- the interface is here referred to as a time machine interface 500 , and includes a presentation window 501 , a timeline 502 , and function buttons.
- the timeline 502 includes a number of snapshots.
- a snapshot refers to a backup element stored in a historical archive that includes a backup of selected items or content as specified by the backup component 117 ( FIG. 1 ).
- the time machine engine can be activated to backup or restore media content within the iTunesTM application (available from Apple Computer in Cupertino, Calif.) or another application.
- the time machine user interface 500 can also include function buttons.
- the interface 500 can include arrow buttons 503 a and 503 b , and an associated scroll bar 505 to allow the user to navigate to additional snapshots not shown in the current timeline window.
- the presentation window 501 is displaying the current state of the iTunesTM application because a “current” snapshot 504 has been selected (highlighted) in the timeline.
- the current snapshot can be a default selection.
- the presentation window 501 can show the contents corresponding to the currently selected snapshot, or a portion thereof.
- the window 501 shows a list of songs that are available in the iTunesTM application, a list sometimes referred to as a playlist.
- the timeline contains a date beneath each snapshot indicating when the snapshot was taken.
- the user can select items or content within the playlist of any of the snapshots.
- the selection functionality can be used in earlier snapshots, such as snapshot 514 , to restore missing data to the state associated with the current snapshot 504 .
- the timeline 502 can include a number of snapshots representing earlier versions or states of the iTunesTM library that have been backed up. Each snapshot provides a screenshot representation of the earlier version of the iTunesTM library at a particular point in time. In some implementations, the timeline 502 includes a visual representation of backup elements, such as a miniature version of the earlier state.
- the timeline can appear across the top portion of the time machine interface 502 (as shown). Alternatively, the timeline does not appear in the top portion of the time machine interface 500 until a user moves their cursor to (or otherwise activates) the timeline (e.g., by activating the top portion of the interface).
- the snapshots within the timeline 502 were created by the backup component 117 using a list of event notifications generated by the event management component 118 ( FIG. 1 ).
- changes occurring to the current playlist are captured by the monitoring engine 202 ( FIG. 2 ) of the event management component 118 .
- the event notifications generated through the modification of the contents of the iTunesTM application can be combined by the combining engine 206 .
- the event notifications generated through the modification of the contents of the iTunesTM application can be combined by the combining engine 206 .
- the combining engine 206 For example, assume that modifications are made to the songs “Rich Girl” and “Crash”, both belonging to the album Love, Angel, Music, Baby and that the event notification queue is currently above its capacity. The notifications relating to these modifications can then be combined to create a single event notification regarding the album Love, Angel, Music, Baby.
- the album Love, Angel, Music, Baby can be scanned to determine what events were dropped, and the corresponding backups can thereafter be performed.
- these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
- An apparatus for performing the operations herein can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer.
- a computer program can be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
- a component is implemented as software
- the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming.
- the present description is in no way limited to implementation in any specific operating system or environment.
- the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus.
- the instructions can be organized into modules (or engines) in different numbers and combinations from the exemplary modules described.
- the computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them.
- data processing apparatus encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers.
- the apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
- a propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
Abstract
Systems and methods are provided for event notification. In one implementation, a method is provided. A determination is made as to whether a threshold associated with pending event notifications has been exceeded by an incoming event notification. A plurality of pending event notifications that can be combined are identified. Two or more event notifications are combined.
Description
- This application is a continuation of U.S. patent application Ser. No. 11/499,866, filed on Aug. 4, 2006, the entire contents of which are hereby incorporated by reference.
- The disclosed implementations relate generally to storing and restoring data.
- A hallmark of modern graphical user interfaces is that they allow a large number of graphical objects or items to be displayed on a display screen at the same time. Leading personal computer operating systems, such as Apple Mac OS®, provide user interfaces in which a number of windows can be displayed, overlapped, resized, moved, configured, and reformatted according to the needs of the user or application. Taskbars, menus, virtual buttons and other user interface elements provide mechanisms for accessing and activating windows even when they are hidden behind other windows.
- With the sophisticated tools available, users are encouraged not only to create and save a multitude of items in their computers, but to revise or otherwise improve on them over time. For example, a user can work with a certain file and thereafter save its current version on a storage device. The next day, however, the user could have had second thoughts about the revisions, or could have come up with new ideas, and therefore opens the file again.
- The revision process is usually straightforward if the user wants to add more material to the file or make changes to what is there. But it is typically more difficult for a user who has changed his/her mind about changes that were previously made and wants the file back as it was once before. Application programs for word processing typically let the user “undo” previous edits of a text, at least up to a predefined number of past revisions. The undo feature also usually is configured so that the previously made revisions must be undone in reverse chronological order; that is, the user must first undo the most recently made edit, then the second-most recent one, and so on. If the user saves and closes the document and thereafter opens it again, it may not be possible to automatically undo any previous edits.
- Virtually all computer systems generate event information of some form during operation. For example, “file system events” are used in the Apple Mac OS® X (a corresponding PC version is NT ChangeLog) to provide event notifications for all file system activity (e.g., add file, change file, delete file, etc). Some event information can generate a large data stream, and the capacity to store event notifications can be limited. Additionally, a particular event can require some action by the system and can therefore block the flow of events. To address this situation, event notifications are sometimes dropped to make room for incoming events.
- Systems and methods are provided for event notification. Events, such as file changes, can be monitored. The event notifications from these events can be used, for example, by a backup system to identify changed data for the next incremental backup operation. The number of event notifications can be limited, leading to dropped events. Dropped events prevent the system from knowing what was changed without searching everything (e.g., searching an entire file system). The loss can be limited by managing the event notifications to combine the event notifications as necessary to maintain space for new incoming events. For example, event notifications for changes to files in a same folder can be combined to a single event notification at a parent level (e.g., a folder that contains the files) to reduce space. Only that parent will need scanned or otherwise examined to determine the changed files instead of the entire file system.
- In general, in one aspect, a method is provided. A determination is made as to whether a threshold associated with pending event notifications has been exceeded by an incoming event notification. A plurality of pending event notifications that can be combined are identified. Two or more event notifications are combined.
- Implementations of the method can include one or more of the following features. Each event notification can identify a change to an entry in a data system. Each event notification can be associated with one or more parent levels of a hierarchical file system and identifying event notifications that can be combined comprises determining two or more event notifications having a common parent level. Combining two or more event notification can include replacing two or more event notifications with a single event notification identifying a change to the common parent level.
- The method can further include scanning the common parent level to identify the combined event notifications and performing a backup operation including backup data associated with the combined event notifications. Scanning the common parent level can include comparing the parent data with data from a previous backup to identify changed data. Receiving an incoming event notification can include receiving an event notification identifying a change to a file system at an event notification queue. The method can further include identifying one or more event notifications as protected, where protected event notifications can not be combined. The method can further include determining a number of event notifications to combine according to one or more criteria. The criteria can include minimizing a number of combined event notifications. Minimizing the number of combined event notifications can include combining a minimum number of event notifications such that the incoming event notification does not exceed the threshold.
- In general, in one aspect, a system is provided. The system includes a monitoring engine for monitoring incoming event notifications. The system includes an event notification queue and an event combiner for combining event notifications in the event notification queue. The system also includes an event notification manager.
- In general, in one aspect, a method is provided. A determination of whether a backup event has occurred is made. Event notifications are evaluated. A backup is generated according to the event notifications. Evaluating event notifications can include identifying an event notification that is a combination of two or more event notifications and scanning data associated with the event notification to identify the combined event notifications.
- Particular embodiments of the subject matter described in this specification can be implemented to realize one or more of the following advantages. The system can combine event notifications in order to reduce dropped event notifications. By combining events, the original event notifications can be more easily identified.
- The details of the various aspects of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the invention will become apparent from the description, the drawings, and the claims.
-
FIG. 1 is a block diagram of an example of an architecture for tracking file system events. -
FIG. 2 is a block diagram of an example of an architecture of an event managing component. -
FIG. 3 is a flow chart of exemplary operations that can be performed to store an event notification. -
FIG. 4 is a flow chart of exemplary operations that can be performed to process event notifications. -
FIG. 5 is a block diagram of an example of an architecture for backing up and restoring application files. -
FIG. 6 is a screen shot showing a time machine interface. -
FIG. 1 is a block diagram of anarchitecture 100 that manages generated event notifications and handles them accordingly. As used herein, an event notification corresponds to activity related to one or more data elements within a computer system. Thearchitecture 100 includes apersonal computer 102 communicatively coupled to aremote server 107 via anetwork interface 116 and a network 108 (e.g., local area network, wireless network, Internet, intranet, etc.). Thecomputer 102 generally includes aprocessor 103,memory 105, one or more input devices 114 (e.g., keyboard, mouse, etc.) and one or more output devices 115 (e.g., a display device). A user interacts with thearchitecture 100 via the input andoutput devices Architecture 100 as disclosed includes various hardware elements.Architecture 100 can include hardware, software, and combinations of the two. - The
computer 102 also includes alocal storage device 106 and a graphics module 113 (e.g., graphics card) for storing information and generating graphical objects, respectively. Thelocal storage device 106 can be a computer-readable medium. The term “computer-readable medium” refers to any medium that includes data and/or participates in providing instructions to a processor for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media. Transmission media includes, without limitation, coaxial cables, copper wire, fiber optics, and computer buses. Transmission media can also take the form of acoustic, light or radio frequency waves. - While event management is described herein with respect to a
personal computer 102, it should be apparent that the disclosed implementations can be incorporated in, or integrated with, any electronic device that has a user interface, including without limitation, portable and desktop computers, servers, electronics, media players, game devices, mobile phones, email devices, personal digital assistants (PDAs), embedded devices, televisions, other consumer electronic devices, etc. - Systems and methods are provided for managing events regarding system information, application information or system, application, or user interface state. The systems and methods can be stand alone, or otherwise integrated into a more comprehensive application. In the materials presented below, an integrated system and method for event management is disclosed.
- One of ordinary skill in the art will recognize that the engines, methods, processes and the like that are described can themselves be an individual process or application, part of an operating system, a plug-in, an application, or the like. In one implementation, the system and methods can be implemented as one or more plug-ins that are installed and run on the
personal computer 102. The plug-ins are configured to interact with an operating system (e.g., MAC OS® X, WINDOWS XP, LINUX, etc.) and to perform the various functions, as described with respect to the Figures. A system and method for modifying a user interface view can also be implemented as one or more software applications running on thecomputer 102. As used herein, a view refers to an item, element, or other content, capable of being presented in a user interface, that can be subjected to a backup operation by abackup component 117. For example, a user interface view can contain any number of icons, files, folders, application state information and/or machine state information, etc. Such a system and method can be characterized as a framework or model that can be implemented on various platforms and/or networks (e.g., client/server networks, wireless networks, stand-alone computers, portable electronic devices, mobile phones, etc.), and/or embedded or bundled with one or more software applications (e.g., email, media player, browser, etc.). - The
computer 102 includes abackup component 117 that allows for the storage of versions of the computer's files or other items, for example within thelocal storage 106 or in an external storage repository. Thebackup component 117 captures versions of one or more interface views and manages an archive of such backups, for example to facilitate user-initiated restoration based on any of them. As used herein, a view refers to an item, element or other content, capable of being presented in a user interface, that can be subjected to a backup operation by thebackup component 117. For example, a user interface view can contain any number of icons, files, folders, application state information, and/or machine state information, etc. In one implementation, thebackup component 117 also allows a user to select any of the stored versions and use it to initiate a restoration of that version in thecomputer 102. - Though discussion is made with reference to a particular user interface view, those of ordinary skill will recognize that such a view can be based on various data structures, files, processes, and other aspects of information management. It follows that modification to file structures, data and the like is also contemplated in order to achieve the modification to the user interface view. In other words, while the restoration of the user interface view from one state to another is the most apparent change from the user's perspective, this is accomplished through the corresponding changes in the underlying system content.
- An
event managing component 118 monitors and manages events within thecomputer 102. For example, such events can be generated by one or more event logging tools. In one implementation, the event logging tool is a file system event tool such as FS Events (available in products from Apple Computer in Cupertino, Calif.). Theevent managing component 118 stores and manages the event notifications as will be described below. For example, thebackup component 117 can use a compiled list of events to determine which changed elements should be archived. -
FIG. 2 is a block diagram of an architecture 200 with examples of features that can be included in theevent managing component 118. Theevent managing component 118 here contains amonitoring engine 202, anevent notification queue 204, a combiningengine 206, and anevent notification manager 208. An exemplary operation of theevent managing component 118 is as follows. Themonitoring engine 202 captures a new event that is to be forwarded for storage in theevent notification queue 204 until it can be processed. If theevent notification manager 208 recognizes that theevent notification queue 204 is reaching capacity, theevent notification manager 208 can instruct the combiningengine 206 to combine two or more of the events into a combined event to save capacity in theevent notification queue 204. For example, if the newly received event relates to a change in a particular directory or folder, that event can be combined with one or more other events relating to the same directory or folder. In some implementations, this causes the information about the specific changes to be lost, but the combined event identifies the localized area (e.g., the directory or folder) that was changed. When the combined event is to be processed, the system can scan the identified directory or folder to identify the changes that were made. - The
monitoring engine 202 detects incoming event notifications. In one implementation, the event notifications originate from a file system activity monitor. An event can occur to a file, folder, data set, system setting, state information, or other individual data element within a computer system. Events include, but are not limited to, element addition, element modification, element deletion, etc. Themonitoring engine 202 sends the incoming events for storage processing. If there is currently sufficient capacity in theevent notification queue 204, the detected events remain stored there. In contrast, if theevent notification queue 204 currently has insufficient capacity, a check is made to determine whether two or more events can be combined. For example, if theevent notification queue 204 is above a set threshold capacity, automatic combining of events can help clear space within the queue. - When the
event notification queue 204 receives an incoming event, it is first determined whether the event notification queue has the capacity to add the new notification. In one implementation, the capacity determination is made by theevent notification queue 204 and the results forwarded to theevent notification manager 208. In another implementation, the capacity determination is made by theevent notification manager 208 acting on event volume information received from theevent notification queue 204. - Events can be removed from the
event notification queue 204 by processing the events stored within the queue. For example, after thebackup component 117 uses the events stored within theevent notification queue 204 to create a new archive view, the information within the event notification queue is no longer needed. Events can also be removed from the event notification queue by creating a combined event. In one implementation, all events covered by the scope of the combined event are deleted from the queue upon the addition of the combined event. Thereafter, individual events can be rediscovered by scanning the structure shared by the combined events, such as a parent folder. - When the
event notification queue 204 is at or above capacity or threshold, the combiningengine 206 can first attempt to find one or more events within theevent notification queue 204 that can be combined with a newly received event. As another example, the combiningengine 206 can attempt to find two or more events within theevent notification queue 204 that can be combined with each other, to free up resources for handling the newly received event. Thus, in the latter situation, the newly received event is not included in the event combination. - The combining
engine 206 can take into account one or more protection levels in attempting to combine event notifications. That is, one or more event notifications can be identified as protected, meaning that the event notification(s) can not be combined with other event notifications. For example, the protection can be set for those event notifications that can be expected to create worse problems than other event notifications if they are lost before they can be processed. - If the
event notification queue 204 is at or above capacity and there are no combinable events, one or more events can be dropped based on a prioritization scheme. For example, it can be considered critical not to lose a file renaming event, because it can later lead to anomalies and be very difficult to detect. Such critical events can be identified as protected event notifications, which are not combinable. In contrast, a regularly scheduled status update can sometimes be lost without causing significant problems. In one implementation, non-critical events can be dropped in these or other situations. In the later event of queue processing, thebackup component 117 will need to scan globally for all element changes in addition to using the critical events contained within theevent notification queue 204. - The combining
engine 206 can be triggered by theevent notification manager 208 to combine individual events within theevent notification queue 204. In one implementation, the combining engine is activated when theevent notification queue 204 is at maximum capacity. In another implementation, theevent notification queue 204 has a threshold level determining when to engage the combiningengine 206. - In some implementations, the scope of combining activity is based upon system or user settings. For example, the combining
engine 206 can begin combining events in no particular order until a queue threshold level has been met. In another implementation, the combiningengine 206 can seek out the combinations that are more preferable to make. For example, it could be preferable to combine events that have a high degree of common hierarchical parentage, such as by being related to the same structure in the hierarchy. In contrast, it could be less preferable to combine events that are more unrelated to each other in the hierarchy. This is because the scope and amount of scanning needed in the former case can be less than that necessary in the latter case. - To create a combination event, the combining
engine 206 scans theevent notification queue 204 and analyzes the events to determine whether two or more events are combinable. For example, the combiningengine 206 can look for elements that share a common feature, such as a parent directory. The combiningengine 206 then creates a new combination event regarding the common feature. The combiningengine 206 drops the individual events comprising the new combination event from theevent notification queue 204 and replaces them with the combination event. In some implementations, the combiningengine 206 merges the involved events to form the combined event. - The
event notification manager 208 manages the operation of themonitoring engine 202 and the combiningengine 206. In addition, theevent notification manager 208 can monitor the status of theevent notification queue 204. In one implementation, theevent notification manager 208 instructs the combiningengine 206 to combine events. In one implementation, theevent notification manager 208 contains a set of values relating to the trigger events for the combiningengine 206. For example, the set of values can contain a queue threshold value at which combination of events should occur. The set of values can also include a lower threshold value at which the combiningengine 206 should cease the combining operation. Theevent notification manager 208, in one implementation, triggers the removal of unnecessary event notifications, for example, after the contents of theevent notification queue 204 have been processed by thebackup component 117. - During the processing of events within the
event notification queue 204, the shared feature listed within each combination event can be perused to determine which elements within that shared feature have undergone changes. For example, if the event combination involved two events relating to changes in two images located in the same photo album, the combined event can identify the photo album as a general indication that two or more system events relating to that album have been dropped. In the event processing, then, the album contents can be scanned (or otherwise analyzed) to determine what events relating to the album need to be rediscovered. Upon determining, in this example, that the dropped events related to changes in two of the images, theevent managing component 118 can process these rediscovered events similarly to a scenario where they had not been dropped. - The processing of events can include interaction with the
backup component 117. In the above example, where there had been changes in two images, theevent managing component 118 can trigger thebackup component 117 to create new backup versions of the altered images. - In one implementation, the combining
engine 206 can also prune events from theevent notification queue 204. For example, the combiningengine 206 can scan theevent notification queue 204 for multiple events that occurred to the same element, because such events can render each other superfluous or moot, at least in part. For example, adding a new element and then deleting the same element is an example of two events that effectively cancel each other out. In another example, successive additions to a text file can be pruned to a single modification event. Thus, the combiningengine 206 can drop one or more events as redundant. -
FIG. 3 is a flow chart of exemplary operations 300 that can be performed in relation to event generation and management. The operations begin instep 302 with receiving an incoming event notification. In one implementation, the event notification can be detected by the monitoring engine 202 (FIG. 2 ). The incoming event, in one example, originates from a file system event logging tool. - In
step 304, the operation determines whether the addition of the incoming event notification exceeds a threshold value associated with the event queue. For example, this determination can be made by the event notification queue 204 (FIG. 2 ). In another implementation, the threshold capacity can be detected by the event notification manager 208 (FIG. 2 ). If the answer instep 304 is yes, then combinable event notifications are identified instep 306. For example, event notifications are combinable if they have a shared feature, e.g., a shared parent directory or other hierarchical structure, such that by scanning the shared feature, all of the combinable event elements can be located within that feature. In one implementation, the combining engine 206 (FIG. 2 ) locates combinable events. For example, the operation can first attempt to identify any elements that share the same parent structure. If there are no such events, or if the combination thereof does not free up sufficient space in the notification queue, the operation can then move up a hierarchical tree, determining potential combinations among two or more events that share relatively less commonality that those considered earlier. - Once combinable event notifications have been identified, the number of event notifications to combine can be determined, in
step 308. In one implementation, the operation desires to combine a sufficient number of events such that an incoming event notification will not exceed the queue threshold. The number of event notifications to combine can, in one implementation, be based on default or user settings. For example, in addition to a higher threshold setting that triggers event combination, theevent notification manager 208 can contain a lower threshold setting that is the goal for the combiningengine 206 when combining events. In one implementation, the order ofsteps - In
step 310, event notifications are combined. For example, the combiningengine 206 can combine the most recently received event notification with one or more previously received ones. In one implementation, notification events can be combined with previously combined events, or previously combined events can be combined with each other, to create additional combination events at a higher hierarchical level. In some implementations, a new event notification is generated and used as the combined event, in other implementations one of the events being combined is modified to be the combined event. - In one implementation, the system can scan (e.g., prior to initiating a backup operation) the particular structure (e.g., folder, directory, or other hierarchical level) that includes combined event notifications in order to determine the underlying events. For example, if two file events were combined into a single folder event notification, the folder is examined to identify which files were the source of the file events that have been lost. In one implementation, the system can compare the folder data with an archive version (e.g., from a previous backup operation) in order to determine which files have changed data, indicating they were the source of the combined file event notifications.
- In
step 312, the incoming event notification is added to the notification queue. When the threshold was not exceeded instep 304, the newly received notification can be added without modification. In contrast, when the threshold was exceeded instep 304, the notification that is added instep 312 can be a combined event resulting from the steps 306-310. In one implementation, theevent notification manager 208 adds the incoming event to theevent notification queue 204. -
FIG. 4 is a flow chart ofexemplary operations 400 that can be performed in relation to event generation and management. For example, theoperations 400 can be performed in processing a queue of event notifications that could include one or more combined event notifications. As has been noted above, in some implementations, when two or more event notifications are combined, the information about the events that triggered them is lost, at least in part. In such situations, for example, theoperations 400 can be performed in an attempt to rediscover that missing information so that the events can be processed. - The operations begin at
step 402 with the initiation of the processing of event notifications. For example, this can involve initiating the event managing component 118 (FIG. 1 ). As has been mentioned, theevent managing component 118 can process event notifications that are stored in a queue. - In
step 404, it is determined, for each event notification, whether the notification is a combination of two or more event notifications. If so, the operation scans the area implicated by the combined events, instep 406. For example, when two events relating to the same folder are combined, information about the events can be lost. Although the specifics of the events are no longer known, it is known that they related to a particular folder. The folder can then be considered a hierarchical region that is implicated by these combined events. The system can attempt to rediscover the missing information by scanning the folder. For example, theevent managing component 118 can scan each element within the hierarchical region implicated by the combined event, such as by comparing each element's timestamp to the timestamp of the previously generated backup version. In another implementation, thebackup component 117 compares the contents of the hierarchical region to the contents of that region within the previously generated backup version to determine the change(s). Other approaches can be used to rediscover the lost event notifications. - In
step 408, the operation identifies all changed elements within the implicated area. For example, changes can include added data elements, modified data elements, and deleted data elements, etc. The operation then processes the identified change(s) instep 410. The change(s) processed instep 410 can be from a non-combined event following the determination instep 404, or from two or more previously combined events that were rediscovered in steps 406-408. In processing the changes, in one implementation, thebackup component 117 can use the list of changed elements to generate a new backup version of each element. - If, at
step 412, it is found that this is not the last event notification in the list, the operation returns to step 404 to process at least one more event notification. If, instead, this is the last notification to be processed, the operation ends. In one implementation, at the termination of the event processing operation, the event notification manager (208) can trigger the cleaning of theevent notification queue 204 to clear it of all stored events. Theoperations 400 can be repeated in part or in whole as required. - Some operations of the
backup component 117 have been described in some of the examples above. There will now be provided an example of features that can be included in thebackup component 117.FIG. 5 is a block diagram of anexemplary architecture 201 for enabling the back up and restoration of data (e.g., application files, application data, settings, parameters or the like), such as those associated with a set ofapplication programs 228.Backup component 117 provides back up and restoration capability for the system. Many different items or elements can be the subject of a backup operation in the system. For example, folders, files, items, information portions, directories, images, system or application parameters, playlists, e-mail, inbox, application data, address book, preferences, and the like all can be candidates for archiving. Other types are also possible. In this example, thebackup component 117 includes at least onestorage device 232. This can be an internal or external resource, or a combination of the two. Any number of local and/or external storage devices can be used by thebackup component 117 for storing versions. In this implementation, thebackup component 117 views any and all storage device(s) designated for version storage as a single memory bank. - In one implementation, the
backup component 117 runs as a background task on anoperating system 230, such that the task is not visible to the user. Thebackup component 117 can be capable of running across multiple user accounts. - The
backup component 117 includes anactivity monitoring engine 212. In one implementation, theactivity monitoring engine 212 monitors for changes within an application view (e.g. files) that are targeted for a backup operation. A change can also include the addition of new files or data or the deletion of the same. In one implementation, theactivity monitoring engine 212 is capable of discerning between a substantive change (e.g. the text within a document has been modified) and a non-substantive change (e.g. the play count within an iTunes playlist has been updated, or several changes cancel each other out) through its interaction with theapplication programs 228. Theactivity monitoring engine 212 can, for example, create a list of modified elements to be used when a backup event is eventually triggered. In one implementation, theactivity monitoring engine 212 can monitor the system for periods of inactivity. Theactivity monitoring engine 212 can then trigger a backup event during a period of time in which the backup operation will not cause a system slowdown for an active user. - A
preference management engine 214 specifies some operating parameters of thebackup component 117. In one implementation,preference management engine 214 contains user-specified and/or system default application parameters for thebackup component 117. These can include settings for the details of capturing and storing the earlier versions. For example, thepreference management engine 214 can determine the frequency of the backup capture, the storage location for the backup versions, the types of files, data, or other items that are eligible for backup capture, and the events which trigger a backup capture (periodic or event-driven, etc.). - In one implementation, the
preference management engine 214 can detect that a new storage device is being added to the system and prompt the user whether it should be included as a backup repository. Files and other items can be scheduled for a backup operation due to location (e.g. everything on the C: drive and within D:/photos), a correlation with specific applications (e.g. all pictures, music, e-mail, address book, preferences, and system settings), or a combination of strategies. Different types of items can be scheduled to be stored on different devices or on different segments of a storage device during a backup operation. In one implementation, thebackup component 117 stores the versions in a format corresponding to a file system structure. - A
backup management engine 216 coordinates the collection, storage, and retrieval of view versions performed by thebackup component 117. For example, thebackup management engine 216 can trigger theactivity monitoring engine 212 to watch for activities that satisfy a requirement specified in thepreference management engine 214. - A
change identifying engine 218 locates specific views or other items within to determine if they have changed. Thechange identifying engine 218 can be capable of discerning a substantive change from a non-substantive change, similar to the example described above for theactivity monitoring engine 212. In one implementation, thechange identifying engine 218 traverses a target set of files, data, or other items, comparing a previous version to the current version to determine whether or not a modification has occurred. - A
backup capture engine 220 locates files, data, or other items that are to be backed up. Thebackup capture engine 220 can invoke theactivity monitoring engine 212 and/or thechange identifying engine 218, for example, to generate a capture list. Thebackup capture engine 220 can then store copies of these elements in one or more targeted storage repositories. Thebackup capture engine 220 can track multiple version copies of each item included in the backup repository. - The
backup component 117 includes abackup restoration engine 222 to restore previous views (e.g. versions of files, data, or other items). In one implementation, thebackup restoration engine 222 provides a user interface (e.g., a graphical user interface) where a user can select the item(s) to be restored. - A
device management engine 224 handles the addition and removal of individual storage devices to be used for archiving views. In one implementation, thepreference management engine 214 obtains user settings regarding the identification of individual storage devices for use in archiving. These settings could include, but are not limited to, particular segments of individual devices to use, a threshold capacity which can be filled with archive data, and individual applications to archive to each device. Thedevice management engine 224 records the storage device settings obtained by the preference management engine and uses them to monitor storage device activity. In one implementation, thedevice management engine 224 can alert the user when a new device has been added to the system. In one implementation, thedevice management engine 224 can alert the user when an archive-enabled device has been removed from the system. In yet another implementation, thedevice management engine 224 can alert the user when an archive-enabled device is nearing its threshold storage capacity setting. - An
archive management engine 226 tracks where archived views are being stored. In one implementation, thearchive management engine 226 obtains user options from the preference management engine. Such settings can include, but are not limited to, methods to be used to remove older or otherwise unnecessary archived views. These settings can establish criteria for archived view deletion, for instance in the event of storage capacity being reached or on a regular basis. In one implementation, thearchive management engine 226 alerts the user when archives are missing because a device has gone offline. In another implementation, thearchive management engine 226 bars a user from viewing another user's archived data due to system permissions settings. - In this example, the first
external storage device 232 is being used by thebackup component 117 for archiving. Thefirst device 232 contains an initialbackup version 234, which is the first archived view created within this device for a particular item. Thefirst device 232 also contains anincremental update 236. In one implementation, theincremental update 236 contains links back to data stored withininitial backup 234, such that only one copy of an unchanged piece of data is retained. In this manner, links can also exist between incremental updates. Each incremental update can then contain a copy of each new or changed data item plus a link back to a previously stored copy of each unchanged data item. Any number of incremental updates can exist. If the user changes the scope of data that is being backed up from one incremental update period to another so that the scope of data now includes new data areas, a portion of an incremental update can be considered similar to an initial backup version. Other archive management techniques could be used. - The
backup component 117 can use information stored by theevent managing component 118 during incremental backup creation. For example, as described with reference toFIG. 4 , events stored by theevent managing component 118 can provide thebackup component 117 with a list of changed elements since the last incremental backup event. In some implementations, thebackup component 117 includes some or all portions of theevent managing component 118. In another implementation, theevent managing component 118 includes some or all portions of thebackup component 117. - Any number of storage devices can be used by the backup component. In one implementation, different storage devices contain the backup version and incremental updates of data belonging to different applications or to different users on the system. As another example, two or more storage devices can be responsible for backing up contents from separate applications in the system.
- The archived copies can be compressed and/or encrypted. An example of a compression technique is the ZIP file format for data compression and archiving. An example of an encryption technique is the RSA algorithm for public key encryption. Other compression techniques or encryption techniques could be used.
- In one implementation, if multiple users make use of the time
machine backup component 117 on a single system, each user can select to keep separate archives. Access to an individual user's archives can be password protected or otherwise held in a secure manner. In one implementation, the archive storage structure mimics a typical file system structure, such that the archived versions can be perused using a standard file system viewing utility. - It has been mentioned that the
backup component 117 can be used for selective restoration of a captured backup version, or a portion thereof. There will now be described with reference toFIG. 6 an example of a user interface that can be generated to facilitate such restoration. The interface is here referred to as atime machine interface 500, and includes apresentation window 501, atimeline 502, and function buttons. Thetimeline 502 includes a number of snapshots. As used herein, a snapshot refers to a backup element stored in a historical archive that includes a backup of selected items or content as specified by the backup component 117 (FIG. 1 ). The time machine engine can be activated to backup or restore media content within the iTunes™ application (available from Apple Computer in Cupertino, Calif.) or another application. - The time
machine user interface 500 can also include function buttons. For example, theinterface 500 can includearrow buttons scroll bar 505 to allow the user to navigate to additional snapshots not shown in the current timeline window. Thus, there can be a large number of snapshots from which to select. As shown, thepresentation window 501 is displaying the current state of the iTunes™ application because a “current”snapshot 504 has been selected (highlighted) in the timeline. The current snapshot can be a default selection. Thepresentation window 501 can show the contents corresponding to the currently selected snapshot, or a portion thereof. Here, thewindow 501 shows a list of songs that are available in the iTunes™ application, a list sometimes referred to as a playlist. - In this particular example, the timeline contains a date beneath each snapshot indicating when the snapshot was taken. In some implementations, the user can select items or content within the playlist of any of the snapshots. The selection functionality can be used in earlier snapshots, such as
snapshot 514, to restore missing data to the state associated with thecurrent snapshot 504. - The
timeline 502 can include a number of snapshots representing earlier versions or states of the iTunes™ library that have been backed up. Each snapshot provides a screenshot representation of the earlier version of the iTunes™ library at a particular point in time. In some implementations, thetimeline 502 includes a visual representation of backup elements, such as a miniature version of the earlier state. The timeline can appear across the top portion of the time machine interface 502 (as shown). Alternatively, the timeline does not appear in the top portion of thetime machine interface 500 until a user moves their cursor to (or otherwise activates) the timeline (e.g., by activating the top portion of the interface). - The snapshots within the
timeline 502, in one implementation, were created by thebackup component 117 using a list of event notifications generated by the event management component 118 (FIG. 1 ). In another implementation, changes occurring to the current playlist are captured by the monitoring engine 202 (FIG. 2 ) of theevent management component 118. - In the case where the
event notification queue 204 is at or beyond its threshold value, for example, the event notifications generated through the modification of the contents of the iTunes™ application can be combined by the combiningengine 206. For example, assume that modifications are made to the songs “Rich Girl” and “Crash”, both belonging to the album Love, Angel, Music, Baby and that the event notification queue is currently above its capacity. The notifications relating to these modifications can then be combined to create a single event notification regarding the album Love, Angel, Music, Baby. At a later time, when the combined event notification is to be processed, the album Love, Angel, Music, Baby can be scanned to determine what events were dropped, and the corresponding backups can thereafter be performed. Assume, as another example, that modifications are instead made to “Rich Girl” of the album Love, Angel, Music, Baby and to “St. Louis Blues” of the album The Blues, and that the event notifications corresponding to these changes are subsequently combined. Later, upon event processing, the playlist covering both affected albums (and, in some situations, several other albums) can be scanned to determine what events were dropped, for performing the corresponding backup operations. Thus, the latter example can require more extensive scanning than the former. - In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. It will be apparent, however, to one skilled in the art that implementations can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the disclosure.
- In particular, one skilled in the art will recognize that other architectures and graphics environments can be used, and that the examples can be implemented using graphics tools and products other than those described above. In particular, the client/server approach is merely one example of an architecture for providing the functionality described herein; one skilled in the art will recognize that other, non-client/server approaches can also be used. Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
- It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
- An apparatus for performing the operations herein can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
- The algorithms and modules presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems can be used with programs in accordance with the teachings herein, or it could prove convenient to construct more specialized apparatuses to perform the method steps. The required structure for a variety of these systems will appear from the description. In addition, the present examples are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings as described herein. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, features, attributes, methodologies, and other aspects can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present description is in no way limited to implementation in any specific operating system or environment.
- The subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The instructions can be organized into modules (or engines) in different numbers and combinations from the exemplary modules described. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
- While this specification contains many specifics, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features specific to particular implementations of the subject matter. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
- Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
- The subject matter of this specification has been described in terms of particular embodiments, but other embodiments can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims.
Claims (19)
1. (canceled)
2. A method comprising:
determining, by a computer system, that a threshold number of pending event notifications in a queue has been exceeded by an incoming event notification;
determining that two or more event notifications in the queue are associated with a common feature of the computer system; and
combining the two or more event notifications based on the common feature such that the number of pending event notifications, including the combined two or more event notifications, in the queue no longer exceeds the threshold number of event notifications, including replacing two or more event notifications with a single event notification indicating that a change has occurred with regard to the common feature.
3. The method of claim 2 , further comprising:
scanning the computer system to identify the combined event notifications associated with the common feature; and
performing a backup operation including backup data associated with the combined event notifications.
4. The method of claim 3 , where scanning the computer system includes comparing current data related to the common feature with data from a previous backup to identify changed data.
5. The method of claim 2 , where receiving an incoming event notification includes receiving an event notification at an event notification queue that identifies a change to a feature of the computer system.
6. The method of claim 2 , further comprising:
identifying one or more event notifications as protected, where protected event notifications cannot be combined.
7. The method of claim 2 , further comprising:
determining a number of event notifications to combine according to one or more criteria.
8. A non-transitory computer-readable medium including instructions which, when executed by one or more processors causes:
determining that a threshold number of pending event notifications in a queue has been exceeded by an incoming event notification;
determining that two or more event notifications in the queue are associated with a common feature of a computer system; and
combining the two or more event notifications based on the common feature such that the number of pending event notifications, including the combined two or more event notifications, in the queue no longer exceeds the threshold number of event notifications, including replacing two or more event notifications with a single event notification indicating that a change has occurred with regard to the common feature.
9. The non-transitory computer-readable medium of claim 8 , wherein the instructions cause:
scanning the computer system to identify the combined event notifications associated with the common feature; and
performing a backup operation including backup data associated with the combined event notifications.
10. The non-transitory computer-readable medium of claim 9 , where the instructions that cause scanning the computer system include instructions that cause comparing current data related to the common feature with data from a previous backup to identify changed data.
11. The non-transitory computer-readable medium of claim 8 , where the instructions that cause receiving an incoming event notification include instructions that cause receiving an event notification at an event notification queue that identifies a change to a feature of the computer system.
12. The non-transitory computer-readable medium of claim 8 , where the instructions cause:
identifying one or more event notifications as protected, where protected event notifications cannot be combined.
13. The non-transitory computer-readable medium of claim 8 , where the instructions cause:
determining a number of event notifications to combine according to one or more criteria.
14. A system comprising:
one or more processors; and
a non-transitory computer-readable medium including instructions which, when executed by the one or more processors causes:
determining that a threshold number of pending event notifications in a queue has been exceeded by an incoming event notification;
determining that two or more event notifications in the queue are associated with a common feature of a computer system; and
combining the two or more event notifications based on the common feature such that the number of pending event notifications, including the combined two or more event notifications, in the queue no longer exceeds the threshold number of event notifications, including replacing two or more event notifications with a single event notification indicating that a change has occurred with regard to the common feature.
15. The system of claim 14 , wherein the instructions cause:
scanning the computer system to identify the combined event notifications associated with the common feature; and
performing a backup operation including backup data associated with the combined event notifications.
16. The system of claim 15 , where the instructions that cause scanning the computer system include instructions that cause comparing current data related to the common feature with data from a previous backup to identify changed data.
17. The system of claim 14 , where the instructions that cause receiving an incoming event notification include instructions that cause receiving an event notification at an event notification queue that identifies a change to a feature of the computer system.
18. The system of claim 14 , where the instructions cause:
identifying one or more event notifications as protected, where protected event notifications cannot be combined.
19. The system of claim 14 , where the instructions cause:
determining a number of event notifications to combine according to one or more criteria.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/724,148 US20130212599A1 (en) | 2006-08-04 | 2012-12-21 | Event notification management |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/499,866 US8370853B2 (en) | 2006-08-04 | 2006-08-04 | Event notification management |
US13/724,148 US20130212599A1 (en) | 2006-08-04 | 2012-12-21 | Event notification management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/499,866 Continuation US8370853B2 (en) | 2006-08-04 | 2006-08-04 | Event notification management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130212599A1 true US20130212599A1 (en) | 2013-08-15 |
Family
ID=39464997
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/499,866 Active 2029-06-04 US8370853B2 (en) | 2006-08-04 | 2006-08-04 | Event notification management |
US13/724,148 Abandoned US20130212599A1 (en) | 2006-08-04 | 2012-12-21 | Event notification management |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/499,866 Active 2029-06-04 US8370853B2 (en) | 2006-08-04 | 2006-08-04 | Event notification management |
Country Status (1)
Country | Link |
---|---|
US (2) | US8370853B2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8943026B2 (en) | 2011-01-14 | 2015-01-27 | Apple Inc. | Visual representation of a local backup |
US8984029B2 (en) | 2011-01-14 | 2015-03-17 | Apple Inc. | File system management |
US9009115B2 (en) | 2006-08-04 | 2015-04-14 | Apple Inc. | Restoring electronic information |
US20150195356A1 (en) * | 2014-01-07 | 2015-07-09 | Samsung Electronics Co., Ltd. | Method of providing information by electronic device and electronic device |
US9360995B2 (en) | 2007-06-08 | 2016-06-07 | Apple Inc. | User interface for electronic backup |
US9454587B2 (en) | 2007-06-08 | 2016-09-27 | Apple Inc. | Searching and restoring of backups |
CN106462631A (en) * | 2014-06-18 | 2017-02-22 | 微软技术许可有限责任公司 | Consistent views of partitioned data in eventually consistent systems |
US20190102258A1 (en) * | 2015-09-16 | 2019-04-04 | Richard Banister | System and Method for Procedure for Point-in-Time Recovery of Cloud or Database Data and Records in Whole or in Part |
US10657123B2 (en) | 2015-09-16 | 2020-05-19 | Sesame Software | Method and system for reducing time-out incidence by scoping date time stamp value ranges of succeeding record update requests in view of previous responses |
US10686740B2 (en) | 2016-09-09 | 2020-06-16 | Microsoft Technology Licensing, Llc | Learned user preference- and behavior-based notification filtering |
US10838827B2 (en) | 2015-09-16 | 2020-11-17 | Richard Banister | System and method for time parameter based database restoration |
US10990586B2 (en) | 2015-09-16 | 2021-04-27 | Richard Banister | System and method for revising record keys to coordinate record key changes within at least two databases |
US11194769B2 (en) | 2020-04-27 | 2021-12-07 | Richard Banister | System and method for re-synchronizing a portion of or an entire source database and a target database |
US20220329475A1 (en) * | 2016-12-02 | 2022-10-13 | Worldpay, Llc | Systems and methods for subscribing topics and registering computer server event notifications |
Families Citing this family (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6961804B2 (en) * | 2001-07-20 | 2005-11-01 | International Business Machines Corporation | Flexible techniques for associating cache memories with processors and main memory |
US7856424B2 (en) * | 2006-08-04 | 2010-12-21 | Apple Inc. | User interface for backup management |
US7853566B2 (en) | 2006-08-04 | 2010-12-14 | Apple Inc. | Navigation of electronic backups |
US7860839B2 (en) | 2006-08-04 | 2010-12-28 | Apple Inc. | Application-based backup-restore of electronic information |
US20080034004A1 (en) * | 2006-08-04 | 2008-02-07 | Pavel Cisler | System for electronic backup |
US7809688B2 (en) * | 2006-08-04 | 2010-10-05 | Apple Inc. | Managing backup of content |
US8370853B2 (en) | 2006-08-04 | 2013-02-05 | Apple Inc. | Event notification management |
US7853567B2 (en) * | 2006-08-04 | 2010-12-14 | Apple Inc. | Conflict resolution in recovery of electronic data |
US8311988B2 (en) | 2006-08-04 | 2012-11-13 | Apple Inc. | Consistent back up of electronic information |
US20080034017A1 (en) * | 2006-08-04 | 2008-02-07 | Dominic Giampaolo | Links to a common item in a data structure |
US20080034019A1 (en) * | 2006-08-04 | 2008-02-07 | Pavel Cisler | System for multi-device electronic backup |
US8166415B2 (en) * | 2006-08-04 | 2012-04-24 | Apple Inc. | User interface for backup management |
US7809687B2 (en) * | 2006-08-04 | 2010-10-05 | Apple Inc. | Searching a backup archive |
US7975109B2 (en) | 2007-05-30 | 2011-07-05 | Schooner Information Technology, Inc. | System including a fine-grained memory and a less-fine-grained memory |
US8745523B2 (en) * | 2007-06-08 | 2014-06-03 | Apple Inc. | Deletion in electronic backups |
US8307004B2 (en) * | 2007-06-08 | 2012-11-06 | Apple Inc. | Manipulating electronic backups |
US8468136B2 (en) * | 2007-06-08 | 2013-06-18 | Apple Inc. | Efficient data backup |
US8099392B2 (en) * | 2007-06-08 | 2012-01-17 | Apple Inc. | Electronic backup of applications |
US8725965B2 (en) * | 2007-06-08 | 2014-05-13 | Apple Inc. | System setup for electronic backup |
US8429425B2 (en) | 2007-06-08 | 2013-04-23 | Apple Inc. | Electronic backup and restoration of encrypted data |
US8245078B1 (en) * | 2007-12-21 | 2012-08-14 | American Megatrends, Inc. | Recovery interface |
US20090204648A1 (en) * | 2008-02-11 | 2009-08-13 | Steven Francie Best | Tracking metadata for files to automate selective backup of applications and their associated data |
US8229945B2 (en) | 2008-03-20 | 2012-07-24 | Schooner Information Technology, Inc. | Scalable database management software on a cluster of nodes using a shared-distributed flash memory |
US8732386B2 (en) | 2008-03-20 | 2014-05-20 | Sandisk Enterprise IP LLC. | Sharing data fabric for coherent-distributed caching of multi-node shared-distributed flash memory |
US8306522B1 (en) * | 2008-12-23 | 2012-11-06 | Sprint Communications Company L.P. | Dynamic interface for mobile devices |
US20100257113A1 (en) * | 2009-04-06 | 2010-10-07 | Microsoft Corporation | Metric-based events for social networks |
US20110191784A1 (en) * | 2010-02-02 | 2011-08-04 | Microsoft Corporation | Processing observable events using join patterns |
US8856593B2 (en) | 2010-04-12 | 2014-10-07 | Sandisk Enterprise Ip Llc | Failure recovery using consensus replication in a distributed flash memory system |
US8725951B2 (en) | 2010-04-12 | 2014-05-13 | Sandisk Enterprise Ip Llc | Efficient flash memory-based object store |
US9047351B2 (en) | 2010-04-12 | 2015-06-02 | Sandisk Enterprise Ip Llc | Cluster of processing nodes with distributed global flash memory using commodity server technology |
US8868487B2 (en) * | 2010-04-12 | 2014-10-21 | Sandisk Enterprise Ip Llc | Event processing in a flash memory-based object store |
US9164554B2 (en) | 2010-04-12 | 2015-10-20 | Sandisk Enterprise Ip Llc | Non-volatile solid-state storage system supporting high bandwidth and random access |
US8666939B2 (en) | 2010-06-28 | 2014-03-04 | Sandisk Enterprise Ip Llc | Approaches for the replication of write sets |
US20120159395A1 (en) | 2010-12-20 | 2012-06-21 | Microsoft Corporation | Application-launching interface for multiple modes |
US8689123B2 (en) | 2010-12-23 | 2014-04-01 | Microsoft Corporation | Application reporting in an application-selectable user interface |
US8694733B2 (en) | 2011-01-03 | 2014-04-08 | Sandisk Enterprise Ip Llc | Slave consistency in a synchronous replication environment |
US8874515B2 (en) | 2011-04-11 | 2014-10-28 | Sandisk Enterprise Ip Llc | Low level object version tracking using non-volatile memory write generations |
US9880604B2 (en) | 2011-04-20 | 2018-01-30 | Microsoft Technology Licensing, Llc | Energy efficient location detection |
US9723459B2 (en) * | 2011-05-18 | 2017-08-01 | Microsoft Technology Licensing, Llc | Delayed and time-space bound notifications |
US8893033B2 (en) * | 2011-05-27 | 2014-11-18 | Microsoft Corporation | Application notifications |
US9158445B2 (en) | 2011-05-27 | 2015-10-13 | Microsoft Technology Licensing, Llc | Managing an immersive interface in a multi-application immersive environment |
US9104307B2 (en) | 2011-05-27 | 2015-08-11 | Microsoft Technology Licensing, Llc | Multi-application environment |
US20120311492A1 (en) * | 2011-06-03 | 2012-12-06 | Memory On Demand, Llc | Automated method of capturing, preserving and organizing thoughts and ideas |
US20130057587A1 (en) | 2011-09-01 | 2013-03-07 | Microsoft Corporation | Arranging tiles |
US10353566B2 (en) | 2011-09-09 | 2019-07-16 | Microsoft Technology Licensing, Llc | Semantic zoom animations |
US8922575B2 (en) | 2011-09-09 | 2014-12-30 | Microsoft Corporation | Tile cache |
US9146670B2 (en) | 2011-09-10 | 2015-09-29 | Microsoft Technology Licensing, Llc | Progressively indicating new content in an application-selectable user interface |
US9324055B2 (en) | 2011-12-08 | 2016-04-26 | Microsoft Technology Licensing, Llc | Techniques to manage remote events |
WO2013123514A1 (en) * | 2012-02-17 | 2013-08-22 | Bsquare Corporation | Managed event queue for independent clients |
US9135064B2 (en) | 2012-03-07 | 2015-09-15 | Sandisk Enterprise Ip Llc | Fine grained adaptive throttling of background processes |
US20140058679A1 (en) * | 2012-08-23 | 2014-02-27 | Apple Inc. | Wake Status Detection for Suppression and Initiation of Notifications |
US20140258921A1 (en) * | 2013-03-11 | 2014-09-11 | Corel Corporation | System and method for ergonomic placement of an object or cursor on a computer display |
US9820231B2 (en) | 2013-06-14 | 2017-11-14 | Microsoft Technology Licensing, Llc | Coalescing geo-fence events |
US9998866B2 (en) | 2013-06-14 | 2018-06-12 | Microsoft Technology Licensing, Llc | Detecting geo-fence events using varying confidence levels |
US9584379B2 (en) * | 2013-06-20 | 2017-02-28 | Microsoft Technology Licensing, Llc | Sorted event monitoring by context partition |
GB2529436B (en) * | 2014-08-20 | 2016-05-18 | Ibm | Grouping file system events to perform continuous file system monitoring and backup |
CN106294351A (en) * | 2015-05-13 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Log event treating method and apparatus |
US11115368B2 (en) * | 2017-05-02 | 2021-09-07 | Life360, Inc. | Systems and methods for intelligent application notification management |
US10970143B1 (en) * | 2019-11-19 | 2021-04-06 | Hewlett Packard Enterprise Development Lp | Event action management mechanism |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5961605A (en) * | 1997-02-06 | 1999-10-05 | Gte Laboratories Incorporated | Method and apparatus for acknowledging TCP data packets |
US20010055317A1 (en) * | 2000-06-21 | 2001-12-27 | Noriki Kajizaki | Network relay apparatus and method of combining packets |
US6493745B1 (en) * | 1999-09-03 | 2002-12-10 | Microsoft Corporation | Message processing technique to improve client computer response to user input |
US20060026218A1 (en) * | 2004-07-23 | 2006-02-02 | Emc Corporation | Tracking objects modified between backup operations |
US20060117022A1 (en) * | 2004-11-26 | 2006-06-01 | Lucas Matthew P | Communication method and system using notification availability indicators |
US7657450B2 (en) * | 2000-12-08 | 2010-02-02 | Microsoft Corporation | Reliable, secure and scalable infrastructure for event registration and propagation in a distributed enterprise |
US20100205397A1 (en) * | 2009-02-11 | 2010-08-12 | Hewlett-Packard Development Company, L.P. | Method and apparatus for allocating resources in a computer system |
US8219995B2 (en) * | 2007-03-28 | 2012-07-10 | International Business Machins Corporation | Capturing hardware statistics for partitions to enable dispatching and scheduling efficiency |
US8352702B2 (en) * | 2009-12-17 | 2013-01-08 | International Business Machines Corporation | Data processing system memory allocation |
Family Cites Families (231)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5163148A (en) | 1989-08-11 | 1992-11-10 | Digital Equipment Corporation | File backup system for producing a backup copy of a file which may be updated during backup |
US5276867A (en) | 1989-12-19 | 1994-01-04 | Epoch Systems, Inc. | Digital data storage system with improved data migration |
US5150473A (en) | 1990-01-16 | 1992-09-22 | Dantz Development Corporation | Data storage format for addressable or sequential memory media |
US5349658A (en) | 1991-11-01 | 1994-09-20 | Rourke Thomas C O | Graphical user interface |
US5369570A (en) | 1991-11-14 | 1994-11-29 | Parad; Harvey A. | Method and system for continuous integrated resource management |
AU3969093A (en) | 1992-04-30 | 1993-11-29 | Apple Computer, Inc. | Method and apparatus for organizing information in a computer system |
JPH0827754B2 (en) | 1992-05-21 | 1996-03-21 | インターナショナル・ビジネス・マシーンズ・コーポレイション | File management method and file management system in computer system |
US5790120A (en) | 1992-08-27 | 1998-08-04 | Starfish Software, Inc. | Individually configurable panel user interface with selective launching, sticky windows, hot keys, start up options and configurable background |
US5623588A (en) | 1992-12-14 | 1997-04-22 | New York University | Computer user interface with non-salience deemphasis |
US5754178A (en) | 1993-03-03 | 1998-05-19 | Apple Computer, Inc. | Method and apparatus for improved feedback during manipulation of data on a computer controlled display system |
US5963962A (en) | 1995-05-31 | 1999-10-05 | Network Appliance, Inc. | Write anywhere file-system layout |
US7174352B2 (en) | 1993-06-03 | 2007-02-06 | Network Appliance, Inc. | File system image transfer |
US6604118B2 (en) | 1998-07-31 | 2003-08-05 | Network Appliance, Inc. | File system image transfer |
ATE409907T1 (en) | 1993-06-03 | 2008-10-15 | Network Appliance Inc | METHOD AND DEVICE FOR DESCRIBING ANY AREAS OF A FILE SYSTEM |
US5583984A (en) | 1993-06-11 | 1996-12-10 | Apple Computer, Inc. | Computer system with graphical user interface including automated enclosures |
US5572709A (en) | 1993-06-18 | 1996-11-05 | Lucent Technologies Inc. | Using dynamically-linked libraries to add side effects to operations |
US5745669A (en) | 1993-10-21 | 1998-04-28 | Ast Research, Inc. | System and method for recovering PC configurations |
US5565888A (en) | 1995-02-17 | 1996-10-15 | International Business Machines Corporation | Method and apparatus for improving visibility and selectability of icons |
US6023506A (en) | 1995-10-26 | 2000-02-08 | Hitachi, Ltd. | Data encryption control apparatus and method |
US5831617A (en) | 1995-11-27 | 1998-11-03 | Bhukhanwala; Saumil A. | Browsing and manipulating objects using movie like icons |
US5832526A (en) | 1996-01-24 | 1998-11-03 | Symantec Corporation | Method and apparatus using slack area of file storage structures for file reconstruction |
US5818936A (en) | 1996-03-15 | 1998-10-06 | Novell, Inc. | System and method for automically authenticating a user in a distributed network system |
US5819032A (en) | 1996-05-15 | 1998-10-06 | Microsoft Corporation | Electronic magazine which is distributed electronically from a publisher to multiple subscribers |
US5819310A (en) | 1996-05-24 | 1998-10-06 | Emc Corporation | Method and apparatus for reading data from mirrored logical volumes on physical disk drives |
US6768999B2 (en) | 1996-06-28 | 2004-07-27 | Mirror Worlds Technologies, Inc. | Enterprise, stream-based, information management system |
US6006227A (en) | 1996-06-28 | 1999-12-21 | Yale University | Document stream operating system |
US20040139396A1 (en) | 1996-06-28 | 2004-07-15 | Gelernter David H. | Stream-based information management system |
US5758359A (en) | 1996-10-24 | 1998-05-26 | Digital Equipment Corporation | Method and apparatus for performing retroactive backups in a computer system |
US6366988B1 (en) | 1997-07-18 | 2002-04-02 | Storactive, Inc. | Systems and methods for electronic data storage management |
US6112318A (en) | 1997-08-11 | 2000-08-29 | Digital Equipment Corporation | Performance counters controlled by programmable logic |
DE69802294T2 (en) | 1997-08-29 | 2002-05-16 | Hewlett Packard Co | SYSTEMS FOR DATA BACKUP AND RECOVERY |
JP3547300B2 (en) | 1997-12-04 | 2004-07-28 | 株式会社日立製作所 | Information exchange system |
US6167532A (en) | 1998-02-05 | 2000-12-26 | Compaq Computer Corporation | Automatic system recovery |
US6901493B1 (en) | 1998-02-24 | 2005-05-31 | Adaptec, Inc. | Method for protecting data of a computer system |
US6269381B1 (en) | 1998-06-30 | 2001-07-31 | Emc Corporation | Method and apparatus for backing up data before updating the data and for restoring from the backups |
US6188405B1 (en) | 1998-09-14 | 2001-02-13 | Microsoft Corporation | Methods, apparatus and data structures for providing a user interface, which exploits spatial memory, to objects |
JP4141556B2 (en) | 1998-12-18 | 2008-08-27 | 株式会社日立製作所 | Structured document management method, apparatus for implementing the method, and medium storing the processing program |
US6397308B1 (en) | 1998-12-31 | 2002-05-28 | Emc Corporation | Apparatus and method for differential backup and restoration of data in a computer storage system |
US6396500B1 (en) | 1999-03-18 | 2002-05-28 | Microsoft Corporation | Method and system for generating and displaying a slide show with animations and transitions in a browser |
US6486896B1 (en) | 1999-04-07 | 2002-11-26 | Apple Computer, Inc. | Scalable scroll controller |
US6714201B1 (en) | 1999-04-14 | 2004-03-30 | 3D Open Motion, Llc | Apparatuses, methods, computer programming, and propagated signals for modeling motion in computer applications |
US6629129B1 (en) | 1999-06-16 | 2003-09-30 | Microsoft Corporation | Shared virtual meeting services among computer applications |
US6959368B1 (en) | 1999-06-29 | 2005-10-25 | Emc Corporation | Method and apparatus for duplicating computer backup data |
US6993710B1 (en) | 1999-10-05 | 2006-01-31 | Borland Software Corporation | Method and system for displaying changes of source code |
WO2001027768A1 (en) | 1999-10-12 | 2001-04-19 | Cms Peripherals, Inc. | Automatic backup system |
US6424626B1 (en) * | 1999-10-29 | 2002-07-23 | Hubbell Incorporated | Method and system for discarding and regenerating acknowledgment packets in ADSL communications |
US6714952B2 (en) | 1999-11-10 | 2004-03-30 | Emc Corporation | Method for backup and restore of a multi-lingual network file server |
US6460055B1 (en) | 1999-12-16 | 2002-10-01 | Livevault Corporation | Systems and methods for backing up data files |
US7434177B1 (en) | 1999-12-20 | 2008-10-07 | Apple Inc. | User interface for providing consolidation and access |
US7505762B2 (en) | 2004-02-27 | 2009-03-17 | Fusionone, Inc. | Wireless telephone data backup system |
US6658436B2 (en) | 2000-01-31 | 2003-12-02 | Commvault Systems, Inc. | Logical view and access to data managed by a modular data and storage management system |
US6829615B2 (en) | 2000-02-25 | 2004-12-07 | International Business Machines Corporation | Object type relationship graphical user interface |
CN1209708C (en) | 2000-03-01 | 2005-07-06 | 电脑联合想象公司 | Method and system for updating an archive of a computer file |
US6918124B1 (en) * | 2000-03-03 | 2005-07-12 | Microsoft Corporation | Query trees including or nodes for event filtering |
US20060143250A1 (en) | 2000-03-09 | 2006-06-29 | Pkware, Inc. | System and method for manipulating and managing computer archive files |
JP3522181B2 (en) | 2000-03-27 | 2004-04-26 | 日本電気株式会社 | Backup data management apparatus and method |
JP3404353B2 (en) | 2000-03-31 | 2003-05-06 | 真二 青山 | Data backup method for portable telephone, portable telephone and data backup device for portable telephone |
US20020112237A1 (en) | 2000-04-10 | 2002-08-15 | Kelts Brett R. | System and method for providing an interactive display interface for information objects |
US6615225B1 (en) | 2000-04-27 | 2003-09-02 | International Business Machines Corporation | System and method for relating files in a distributed data storage environment |
US6711572B2 (en) * | 2000-06-14 | 2004-03-23 | Xosoft Inc. | File system for distributing content in a data network and related methods |
US6665815B1 (en) | 2000-06-22 | 2003-12-16 | Hewlett-Packard Development Company, L.P. | Physical incremental backup using snapshots |
JP2002024071A (en) | 2000-07-07 | 2002-01-25 | Toshiba Corp | Information processor, data backup method and storage medium in which data backup program is stored |
WO2002011396A2 (en) * | 2000-08-01 | 2002-02-07 | Hrl Laboratories, Llc | Apparatus and method for context-sensitive dynamic information service |
US7072916B1 (en) | 2000-08-18 | 2006-07-04 | Network Appliance, Inc. | Instant snapshot |
DE10040890C1 (en) | 2000-08-18 | 2002-01-31 | Trw Automotive Electron & Comp | System for safe high temperature flash memory operation in vehicle involves programming memory before high temperature operation so that each record is stored redundantly |
JP2002074322A (en) | 2000-08-31 | 2002-03-15 | Sony Corp | Information processor, method for processing information and data recording medium |
US7099900B1 (en) | 2000-09-13 | 2006-08-29 | Veritas Operating Corporation | Mapping driver for use in data backup systems |
US6785751B1 (en) * | 2000-09-19 | 2004-08-31 | Intel Corporation | Method and apparatus for minimizing bus contention for I/O controller write operations |
US7380216B2 (en) | 2000-11-30 | 2008-05-27 | International Business Machines Corporation | Zoom-capable scrollbar |
WO2002071219A2 (en) | 2001-03-07 | 2002-09-12 | Matchtip Limited | System for replicating data of a mobile station |
US6728735B1 (en) | 2001-03-12 | 2004-04-27 | Network Appliance, Inc. | Restartable dump that produces a consistent filesystem on tapes |
CA2438481A1 (en) | 2001-03-27 | 2002-10-03 | British Telecommunications Public Limited Company | File synchronisation |
US6801229B1 (en) | 2001-04-06 | 2004-10-05 | Plumbdesign | System for creation of visual representation of data |
US20020156921A1 (en) | 2001-04-19 | 2002-10-24 | International Business Machines Corporation | Automatic backup of wireless mobile device data onto gateway server while device is idle |
TW501037B (en) | 2001-05-01 | 2002-09-01 | Benq Corp | Interactive update method for parameter data |
US7711771B2 (en) | 2001-05-25 | 2010-05-04 | Oracle International Corporation | Management and synchronization application for network file system |
EP1415425B1 (en) | 2001-07-06 | 2019-06-26 | CA, Inc. | Systems and methods of information backup |
US6912645B2 (en) | 2001-07-19 | 2005-06-28 | Lucent Technologies Inc. | Method and apparatus for archival data storage |
US6948038B2 (en) | 2001-07-24 | 2005-09-20 | Microsoft Corporation | System and method for backing up and restoring data |
US20030097640A1 (en) | 2001-07-25 | 2003-05-22 | International Business Machines Corporation | System and method for creating and editing documents |
US6625704B2 (en) | 2001-08-08 | 2003-09-23 | Sangate Systems, Inc. | Data backup method and system using snapshot and virtual tape |
US7032188B2 (en) | 2001-09-28 | 2006-04-18 | Nokia Corporation | Multilevel sorting and displaying of contextual objects |
JP2003140940A (en) | 2001-10-19 | 2003-05-16 | Internatl Business Mach Corp <Ibm> | Program for managing external storage device, recording medium, managing device, and computer system |
US6810881B2 (en) | 2001-10-22 | 2004-11-02 | O.R. Solutions, Inc. | Medical solution thermal treatment system and method of controlling system operation in accordance with detection of solution and leaks in surgical drape containers |
US6948039B2 (en) | 2001-12-14 | 2005-09-20 | Voom Technologies, Inc. | Data backup and restoration using dynamic virtual storage |
JP4108973B2 (en) | 2001-12-26 | 2008-06-25 | 株式会社日立製作所 | Backup system |
US7620908B2 (en) | 2001-12-28 | 2009-11-17 | Sap Ag | Managing a user interface |
US8010903B2 (en) | 2001-12-28 | 2011-08-30 | International Business Machines Corporation | System and method for visualizing and navigating dynamic content in a graphical user interface |
US20030126247A1 (en) | 2002-01-02 | 2003-07-03 | Exanet Ltd. | Apparatus and method for file backup using multiple backup devices |
US20030220949A1 (en) | 2002-01-22 | 2003-11-27 | Columbia Data Products, Inc. | Automatic deletion in data storage management |
DE10211606B4 (en) | 2002-03-12 | 2017-06-08 | Kip Cr P1 Lp | Data processing device with a metadata backup management |
US7225204B2 (en) | 2002-03-19 | 2007-05-29 | Network Appliance, Inc. | System and method for asynchronous mirroring of snapshots at a destination using a purgatory directory and inode mapping |
US6857001B2 (en) | 2002-06-07 | 2005-02-15 | Network Appliance, Inc. | Multiple concurrent active file systems |
JP3747887B2 (en) * | 2002-06-14 | 2006-02-22 | ブラザー工業株式会社 | Setting information transmission / reception system, transmission device, and program |
CA2497625A1 (en) | 2002-09-10 | 2004-03-25 | Exagrid Systems, Inc. | Method and apparatus for managing data integrity of backup and disaster recovery data |
US20040078641A1 (en) | 2002-09-23 | 2004-04-22 | Hewlett-Packard Company | Operating system-independent file restore from disk image |
US7913183B2 (en) | 2002-10-08 | 2011-03-22 | Microsoft Corporation | System and method for managing software applications in a graphical user interface |
JP2004157637A (en) | 2002-11-05 | 2004-06-03 | Hitachi Ltd | Storage management method |
US20040117459A1 (en) | 2002-12-12 | 2004-06-17 | George Fry | System and method providing multimedia messaging in communication networks |
US7406481B2 (en) * | 2002-12-17 | 2008-07-29 | Oracle International Corporation | Using direct memory access for performing database operations between two or more machines |
US7007043B2 (en) | 2002-12-23 | 2006-02-28 | Storage Technology Corporation | Storage backup system that creates mountable representations of past contents of storage volumes |
US7278111B2 (en) | 2002-12-26 | 2007-10-02 | Yahoo! Inc. | Systems and methods for selecting a date or range of dates |
US7533158B2 (en) | 2003-01-17 | 2009-05-12 | At&T Intellectual Property I, L.P. | System and method for handling digital content delivery to portable devices |
US6895323B2 (en) * | 2003-02-20 | 2005-05-17 | Delphi Technologies, Inc. | Brake control method utilizing a controlled center differential |
US20040193953A1 (en) | 2003-02-21 | 2004-09-30 | Sun Microsystems, Inc. | Method, system, and program for maintaining application program configuration settings |
US8230359B2 (en) | 2003-02-25 | 2012-07-24 | Microsoft Corporation | System and method that facilitates computer desktop use via scaling of displayed objects with shifts to the periphery |
US7320076B2 (en) | 2003-03-05 | 2008-01-15 | Sun Microsystems, Inc. | Method and apparatus for a transaction-based secure storage file system |
US7188156B2 (en) | 2003-03-20 | 2007-03-06 | International Business Machines Corporation | System, method and computer program for providing a time map of rolled-up data |
US7155465B2 (en) | 2003-04-18 | 2006-12-26 | Lee Howard F | Method and apparatus for automatically archiving a file system |
US7415115B2 (en) | 2003-05-14 | 2008-08-19 | Broadcom Corporation | Method and system for disaster recovery of data from a storage device |
WO2004104739A2 (en) | 2003-05-14 | 2004-12-02 | Rhysome, Inc. | Method and system for reducing information latency in a business enterprise |
JP4800953B2 (en) | 2003-05-15 | 2011-10-26 | コムキャスト ケーブル ホールディングス,エルエルシー | Video playback method and system |
US7660817B2 (en) | 2003-05-22 | 2010-02-09 | Microsoft Corporation | System and method for representing content in a file system |
US7240219B2 (en) | 2003-05-25 | 2007-07-03 | Sandisk Il Ltd. | Method and system for maintaining backup of portable storage devices |
US7111136B2 (en) | 2003-06-26 | 2006-09-19 | Hitachi, Ltd. | Method and apparatus for backup and recovery system using storage based journaling |
US7162473B2 (en) | 2003-06-26 | 2007-01-09 | Microsoft Corporation | Method and system for usage analyzer that determines user accessed sources, indexes data subsets, and associated metadata, processing implicit queries based on potential interest to users |
US7225208B2 (en) | 2003-09-30 | 2007-05-29 | Iron Mountain Incorporated | Systems and methods for backing up data files |
US6990637B2 (en) | 2003-10-23 | 2006-01-24 | Microsoft Corporation | Graphical user interface for 3-dimensional view of a data collection based on an attribute of the data |
DE10350445A1 (en) * | 2003-10-29 | 2005-06-02 | Braun Gmbh | Electric drive unit for generating an oscillating movement |
US7698728B2 (en) | 2003-11-12 | 2010-04-13 | Home Box Office, Inc. | Automated playlist chaser |
CA2548542C (en) | 2003-11-13 | 2011-08-09 | Commvault Systems, Inc. | System and method for performing a snapshot and for restoring data |
US8990255B2 (en) | 2003-11-17 | 2015-03-24 | Nokia Corporation | Time bar navigation in a media diary application |
US7908208B2 (en) | 2003-12-10 | 2011-03-15 | Alphacap Ventures Llc | Private entity profile network |
JP2005190259A (en) | 2003-12-26 | 2005-07-14 | Hitachi Ltd | Management of multigenerational backup data |
US7103740B1 (en) | 2003-12-31 | 2006-09-05 | Veritas Operating Corporation | Backup mechanism for a multi-class file system |
US7240171B2 (en) | 2004-01-23 | 2007-07-03 | International Business Machines Corporation | Method and system for ensuring consistency of a group |
US20050204186A1 (en) | 2004-03-09 | 2005-09-15 | Rothman Michael A. | System and method to implement a rollback mechanism for a data storage unit |
US7318134B1 (en) | 2004-03-16 | 2008-01-08 | Emc Corporation | Continuous data backup using distributed journaling |
JP4285287B2 (en) | 2004-03-17 | 2009-06-24 | セイコーエプソン株式会社 | Image processing apparatus, image processing method and program, and recording medium |
US7353241B2 (en) | 2004-03-24 | 2008-04-01 | Microsoft Corporation | Method, medium and system for recovering data using a timeline-based computing environment |
US7536424B2 (en) | 2004-05-02 | 2009-05-19 | Yoram Barzilai | System and methods for efficiently managing incremental data backup revisions |
US7096392B2 (en) | 2004-05-07 | 2006-08-22 | Asempra Technologies, Inc. | Method and system for automated, no downtime, real-time, continuous data protection |
US8108429B2 (en) | 2004-05-07 | 2012-01-31 | Quest Software, Inc. | System for moving real-time data events across a plurality of devices in a network for simultaneous data protection, replication, and access services |
US7913043B2 (en) | 2004-05-14 | 2011-03-22 | Bakbone Software, Inc. | Method for backup storage device selection |
US7809682B2 (en) | 2004-05-24 | 2010-10-05 | Apple Inc. | Data synchronization between multiple devices |
US7624133B1 (en) | 2004-06-09 | 2009-11-24 | Symantec Operating Corporation | Automatic detection of backup recovery sets |
US7437358B2 (en) | 2004-06-25 | 2008-10-14 | Apple Inc. | Methods and systems for managing data |
EP1612636A1 (en) | 2004-07-01 | 2006-01-04 | Tecnostore AG | Method for archiving data with automatic encryption and decryption |
US7284190B2 (en) | 2004-07-15 | 2007-10-16 | Microsoft Corporation | Automatically generated compatibility reports |
US7225371B2 (en) | 2004-08-03 | 2007-05-29 | International Business Machines Corporation | Method and apparatus for storing and retrieving multiple point-in-time consistent data sets |
US7411590B1 (en) | 2004-08-09 | 2008-08-12 | Apple Inc. | Multimedia file format |
JP4576936B2 (en) | 2004-09-02 | 2010-11-10 | ソニー株式会社 | Information processing apparatus, information recording medium, content management system, data processing method, and computer program |
US7418619B1 (en) | 2004-09-07 | 2008-08-26 | Emc Corporation | Backup and restore operations of interdependent system components |
US7346799B2 (en) | 2004-09-07 | 2008-03-18 | Emc Corporation | Systems and methods for recovering and backing up data |
US20060064634A1 (en) | 2004-09-17 | 2006-03-23 | International Business Machines Corporation | Editing multiple file versions |
US7756833B2 (en) | 2004-09-22 | 2010-07-13 | Microsoft Corporation | Method and system for synthetic backup and restore |
US20060080521A1 (en) | 2004-09-23 | 2006-04-13 | Eric Barr | System and method for offline archiving of data |
US20060070066A1 (en) * | 2004-09-30 | 2006-03-30 | Grobman Steven L | Enabling platform network stack control in a virtualization platform |
US7559016B1 (en) | 2004-10-07 | 2009-07-07 | Google Inc. | System and method for indicating web page modifications |
US7840963B2 (en) | 2004-10-15 | 2010-11-23 | Microsoft Corporation | Marking and utilizing portions of memory state information during a switch between virtual machines to minimize software service interruption |
KR100667767B1 (en) | 2004-10-20 | 2007-01-11 | 삼성전자주식회사 | Multimedia device having backup function of broadcast contents on home network environment and backup method thereof |
US7490197B2 (en) | 2004-10-21 | 2009-02-10 | Microsoft Corporation | Using external memory devices to improve system performance |
US20060106893A1 (en) | 2004-11-02 | 2006-05-18 | Rodger Daniels | Incremental backup operations in storage networks |
US7904913B2 (en) | 2004-11-02 | 2011-03-08 | Bakbone Software, Inc. | Management interface for a system that provides automated, real-time, continuous data protection |
US20060117309A1 (en) | 2004-11-24 | 2006-06-01 | Upanshu Singhal | Software configuration methods and client module communication component |
US7624443B2 (en) | 2004-12-21 | 2009-11-24 | Microsoft Corporation | Method and system for a self-heating device |
US7934064B1 (en) | 2004-12-21 | 2011-04-26 | Acronis Inc. | System and method for consolidation of backups |
US7734999B2 (en) | 2005-01-03 | 2010-06-08 | Emergis Inc. | System and method for providing forms on a user interface |
US7788592B2 (en) | 2005-01-12 | 2010-08-31 | Microsoft Corporation | Architecture and engine for time line based visualization of data |
US8341541B2 (en) | 2005-01-18 | 2012-12-25 | Microsoft Corporation | System and method for visually browsing of open windows |
US20080046557A1 (en) | 2005-03-23 | 2008-02-21 | Cheng Joseph C | Method and system for designing, implementing, and managing client applications on mobile devices |
US7461221B2 (en) | 2005-03-24 | 2008-12-02 | International Business Machines Corporation | Apparatus, system, and program for automatic backup of related data |
US7669141B1 (en) | 2005-04-11 | 2010-02-23 | Adobe Systems Incorporated | Visual interface element transition effect |
US20080065663A1 (en) | 2005-04-14 | 2008-03-13 | Emc Corporation | Reestablishing process context |
US7590668B2 (en) | 2005-04-15 | 2009-09-15 | Microsoft Corporation | Pausable backups of file system items |
US8886778B2 (en) | 2005-04-29 | 2014-11-11 | Netapp, Inc. | System and method for proxying network management protocol commands to enable cluster wide management of data backups |
US7454435B2 (en) | 2005-05-03 | 2008-11-18 | Microsoft Corporation | Systems and methods for granular changes within a data storage system |
US7558930B2 (en) | 2005-07-25 | 2009-07-07 | Hitachi, Ltd. | Write protection in a storage system allowing both file-level access and volume-level access |
US20070027935A1 (en) | 2005-07-28 | 2007-02-01 | Haselton William R | Backing up source files in their native file formats to a target storage |
EP1910949A4 (en) | 2005-07-29 | 2012-05-30 | Cataphora Inc | An improved method and apparatus for sociological data analysis |
US20070038884A1 (en) | 2005-08-10 | 2007-02-15 | Spare Backup, Inc. | System and method of remote storage of data using client software |
US7716171B2 (en) | 2005-08-18 | 2010-05-11 | Emc Corporation | Snapshot indexing |
JP2009508274A (en) | 2005-09-13 | 2009-02-26 | スペースタイムスリーディー・インコーポレーテッド | System and method for providing a three-dimensional graphical user interface |
US20070078910A1 (en) | 2005-09-30 | 2007-04-05 | Rajendra Bopardikar | Back-up storage for home network |
US20070088702A1 (en) | 2005-10-03 | 2007-04-19 | Fridella Stephen A | Intelligent network client for multi-protocol namespace redirection |
US20070106978A1 (en) | 2005-10-11 | 2007-05-10 | Bea Systems, Inc. | Patch management system |
US7404150B2 (en) | 2005-11-14 | 2008-07-22 | Red Hat, Inc. | Searching desktop objects based on time comparison |
US7765187B2 (en) | 2005-11-29 | 2010-07-27 | Emc Corporation | Replication of a consistency group of data storage objects from servers in a data network |
US7904425B2 (en) | 2005-12-13 | 2011-03-08 | International Business Machines Corporation | Generating backup sets to a specific point in time |
US20070185879A1 (en) | 2005-12-23 | 2007-08-09 | Metacommunications, Inc. | Systems and methods for archiving and retrieving digital assets |
US9100197B2 (en) | 2006-01-19 | 2015-08-04 | Lenovo (Singapore) Pte. Ltd. | Apparatus and method for signaling by and to a computer system user |
US8229897B2 (en) | 2006-02-03 | 2012-07-24 | International Business Machines Corporation | Restoring a file to its proper storage tier in an information lifecycle management environment |
US7822717B2 (en) | 2006-02-07 | 2010-10-26 | Emc Corporation | Point-in-time database restore |
US7698318B2 (en) | 2006-02-10 | 2010-04-13 | Microsoft Corporation | Automatically determining file replication mechanisms |
US7853988B2 (en) | 2006-05-16 | 2010-12-14 | Waterstone Environmental Hydrology & Engineering, Inc. | State saver/restorer for a geospatial decision management system |
US20070271303A1 (en) | 2006-05-18 | 2007-11-22 | Manuel Emilio Menendez | Personal file version archival management and retrieval |
US20070271263A1 (en) | 2006-05-19 | 2007-11-22 | Matchware A/S | Displaying Data |
US8190571B2 (en) | 2006-06-07 | 2012-05-29 | Microsoft Corporation | Managing data with backup server indexing |
US7774829B2 (en) | 2006-06-20 | 2010-08-10 | Lenovo (Singapore) Pte. Ltd. | Computer access control using password reset |
US7676689B1 (en) | 2006-06-30 | 2010-03-09 | Emc Corporation | Browsing and selecting items in recovery storage groups to perform recovery onto production server |
JP4749266B2 (en) | 2006-07-27 | 2011-08-17 | 株式会社日立製作所 | Backup control apparatus and method without duplication of information resources |
US8370853B2 (en) | 2006-08-04 | 2013-02-05 | Apple Inc. | Event notification management |
US8311988B2 (en) | 2006-08-04 | 2012-11-13 | Apple Inc. | Consistent back up of electronic information |
US7853566B2 (en) | 2006-08-04 | 2010-12-14 | Apple Inc. | Navigation of electronic backups |
US7853567B2 (en) | 2006-08-04 | 2010-12-14 | Apple Inc. | Conflict resolution in recovery of electronic data |
US7860839B2 (en) | 2006-08-04 | 2010-12-28 | Apple Inc. | Application-based backup-restore of electronic information |
US7809687B2 (en) | 2006-08-04 | 2010-10-05 | Apple Inc. | Searching a backup archive |
US20080034017A1 (en) | 2006-08-04 | 2008-02-07 | Dominic Giampaolo | Links to a common item in a data structure |
US20080033969A1 (en) | 2006-08-04 | 2008-02-07 | Sing Chi Koo | Electronic document management method and system |
US7809688B2 (en) | 2006-08-04 | 2010-10-05 | Apple Inc. | Managing backup of content |
US20080034004A1 (en) | 2006-08-04 | 2008-02-07 | Pavel Cisler | System for electronic backup |
US8166415B2 (en) | 2006-08-04 | 2012-04-24 | Apple Inc. | User interface for backup management |
US9009115B2 (en) | 2006-08-04 | 2015-04-14 | Apple Inc. | Restoring electronic information |
US7856424B2 (en) | 2006-08-04 | 2010-12-21 | Apple Inc. | User interface for backup management |
US20080126442A1 (en) | 2006-08-04 | 2008-05-29 | Pavel Cisler | Architecture for back up and/or recovery of electronic data |
US20080034019A1 (en) | 2006-08-04 | 2008-02-07 | Pavel Cisler | System for multi-device electronic backup |
US20080070496A1 (en) | 2006-09-20 | 2008-03-20 | Luke Jackson | Cell phone live redundancy data back-up system |
US20080082578A1 (en) | 2006-09-29 | 2008-04-03 | Andrew Hogue | Displaying search results on a one or two dimensional graph |
US7882077B2 (en) | 2006-10-17 | 2011-02-01 | Commvault Systems, Inc. | Method and system for offline indexing of content and classifying stored data |
CA2705379C (en) | 2006-12-04 | 2016-08-30 | Commvault Systems, Inc. | Systems and methods for creating copies of data, such as archive copies |
US20080141029A1 (en) | 2006-12-11 | 2008-06-12 | Migo Software, Inc. | Digital content protection |
US10083184B2 (en) | 2007-01-07 | 2018-09-25 | Apple Inc. | Widget synchronization in accordance with synchronization preferences |
US8850140B2 (en) | 2007-01-07 | 2014-09-30 | Apple Inc. | Data backup for mobile device |
US7778971B2 (en) | 2007-01-07 | 2010-08-17 | Apple Inc. | Synchronization methods and systems |
US7900142B2 (en) | 2007-01-15 | 2011-03-01 | Microsoft Corporation | Selective undo of editing operations performed on data objects |
US20080177961A1 (en) | 2007-01-23 | 2008-07-24 | International Business Machines Corporation | Partial Backup and Restore with Backup Versioning |
WO2008094508A2 (en) | 2007-01-26 | 2008-08-07 | Fusionone, Inc. | System for and method of backing up content for use on a mobile device |
US20080208630A1 (en) | 2007-02-22 | 2008-08-28 | General Electric Company | Methods and systems for accessing a saved patient context in a clinical information system |
US20090013267A1 (en) | 2007-04-27 | 2009-01-08 | Bea Systems, Inc. | Constructor web-based change control system and method |
US8745523B2 (en) | 2007-06-08 | 2014-06-03 | Apple Inc. | Deletion in electronic backups |
US8010900B2 (en) | 2007-06-08 | 2011-08-30 | Apple Inc. | User interface for electronic backup |
EP2372553B1 (en) | 2007-06-08 | 2013-01-30 | Apple Inc. | Application-based backup-restore of electronic information |
US8468136B2 (en) | 2007-06-08 | 2013-06-18 | Apple Inc. | Efficient data backup |
US8307004B2 (en) | 2007-06-08 | 2012-11-06 | Apple Inc. | Manipulating electronic backups |
US8099392B2 (en) | 2007-06-08 | 2012-01-17 | Apple Inc. | Electronic backup of applications |
US8725965B2 (en) | 2007-06-08 | 2014-05-13 | Apple Inc. | System setup for electronic backup |
US8429425B2 (en) | 2007-06-08 | 2013-04-23 | Apple Inc. | Electronic backup and restoration of encrypted data |
US20080307017A1 (en) | 2007-06-08 | 2008-12-11 | Apple Inc. | Searching and Restoring of Backups |
US8484464B2 (en) | 2007-06-15 | 2013-07-09 | Research In Motion Limited | Method and devices for providing secure data backup from a mobile communication device to an external computing device |
US8583602B2 (en) | 2008-06-05 | 2013-11-12 | Palm, Inc. | Restoring of data to mobile computing device |
US20110016089A1 (en) | 2009-07-16 | 2011-01-20 | Apple Inc. | Restoring data to a mobile device |
-
2006
- 2006-08-04 US US11/499,866 patent/US8370853B2/en active Active
-
2012
- 2012-12-21 US US13/724,148 patent/US20130212599A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5961605A (en) * | 1997-02-06 | 1999-10-05 | Gte Laboratories Incorporated | Method and apparatus for acknowledging TCP data packets |
US6493745B1 (en) * | 1999-09-03 | 2002-12-10 | Microsoft Corporation | Message processing technique to improve client computer response to user input |
US20010055317A1 (en) * | 2000-06-21 | 2001-12-27 | Noriki Kajizaki | Network relay apparatus and method of combining packets |
US7657450B2 (en) * | 2000-12-08 | 2010-02-02 | Microsoft Corporation | Reliable, secure and scalable infrastructure for event registration and propagation in a distributed enterprise |
US20060026218A1 (en) * | 2004-07-23 | 2006-02-02 | Emc Corporation | Tracking objects modified between backup operations |
US20060117022A1 (en) * | 2004-11-26 | 2006-06-01 | Lucas Matthew P | Communication method and system using notification availability indicators |
US8219995B2 (en) * | 2007-03-28 | 2012-07-10 | International Business Machins Corporation | Capturing hardware statistics for partitions to enable dispatching and scheduling efficiency |
US20100205397A1 (en) * | 2009-02-11 | 2010-08-12 | Hewlett-Packard Development Company, L.P. | Method and apparatus for allocating resources in a computer system |
US8352702B2 (en) * | 2009-12-17 | 2013-01-08 | International Business Machines Corporation | Data processing system memory allocation |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9009115B2 (en) | 2006-08-04 | 2015-04-14 | Apple Inc. | Restoring electronic information |
US9360995B2 (en) | 2007-06-08 | 2016-06-07 | Apple Inc. | User interface for electronic backup |
US10891020B2 (en) | 2007-06-08 | 2021-01-12 | Apple Inc. | User interface for electronic backup |
US9454587B2 (en) | 2007-06-08 | 2016-09-27 | Apple Inc. | Searching and restoring of backups |
US9411812B2 (en) | 2011-01-14 | 2016-08-09 | Apple Inc. | File system management |
US10303652B2 (en) | 2011-01-14 | 2019-05-28 | Apple Inc. | File system management |
US8943026B2 (en) | 2011-01-14 | 2015-01-27 | Apple Inc. | Visual representation of a local backup |
US8984029B2 (en) | 2011-01-14 | 2015-03-17 | Apple Inc. | File system management |
US20150195356A1 (en) * | 2014-01-07 | 2015-07-09 | Samsung Electronics Co., Ltd. | Method of providing information by electronic device and electronic device |
CN106462631A (en) * | 2014-06-18 | 2017-02-22 | 微软技术许可有限责任公司 | Consistent views of partitioned data in eventually consistent systems |
US10318618B2 (en) | 2014-06-18 | 2019-06-11 | Microsoft Technology Licensing, Llc | Consistent views of partitioned data in eventually consistent systems |
US10990586B2 (en) | 2015-09-16 | 2021-04-27 | Richard Banister | System and method for revising record keys to coordinate record key changes within at least two databases |
US20190102258A1 (en) * | 2015-09-16 | 2019-04-04 | Richard Banister | System and Method for Procedure for Point-in-Time Recovery of Cloud or Database Data and Records in Whole or in Part |
US10540237B2 (en) * | 2015-09-16 | 2020-01-21 | Sesame Software, Inc. | System and method for procedure for point-in-time recovery of cloud or database data and records in whole or in part |
US10657123B2 (en) | 2015-09-16 | 2020-05-19 | Sesame Software | Method and system for reducing time-out incidence by scoping date time stamp value ranges of succeeding record update requests in view of previous responses |
US10838827B2 (en) | 2015-09-16 | 2020-11-17 | Richard Banister | System and method for time parameter based database restoration |
US10686740B2 (en) | 2016-09-09 | 2020-06-16 | Microsoft Technology Licensing, Llc | Learned user preference- and behavior-based notification filtering |
US20220329475A1 (en) * | 2016-12-02 | 2022-10-13 | Worldpay, Llc | Systems and methods for subscribing topics and registering computer server event notifications |
US11665045B2 (en) * | 2016-12-02 | 2023-05-30 | Worldpay, Llc | Systems and methods for subscribing topics and registering computer server event notifications |
US11870636B2 (en) | 2016-12-02 | 2024-01-09 | Worldpay, Llc | Systems and methods for subscribing topics and registering computer server event notifications |
US11194769B2 (en) | 2020-04-27 | 2021-12-07 | Richard Banister | System and method for re-synchronizing a portion of or an entire source database and a target database |
Also Published As
Publication number | Publication date |
---|---|
US8370853B2 (en) | 2013-02-05 |
US20080126441A1 (en) | 2008-05-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8370853B2 (en) | Event notification management | |
US8468136B2 (en) | Efficient data backup | |
US7809688B2 (en) | Managing backup of content | |
US9009115B2 (en) | Restoring electronic information | |
US8745523B2 (en) | Deletion in electronic backups | |
US8775378B2 (en) | Consistent backup of electronic information | |
US20080034004A1 (en) | System for electronic backup | |
US9354982B2 (en) | Manipulating electronic backups | |
US9454587B2 (en) | Searching and restoring of backups | |
US7809687B2 (en) | Searching a backup archive | |
US7853567B2 (en) | Conflict resolution in recovery of electronic data | |
US7853566B2 (en) | Navigation of electronic backups | |
US8504527B2 (en) | Application-based backup-restore of electronic information | |
EP2372553B1 (en) | Application-based backup-restore of electronic information | |
US20080034017A1 (en) | Links to a common item in a data structure | |
US20080126442A1 (en) | Architecture for back up and/or recovery of electronic data | |
US20080034019A1 (en) | System for multi-device electronic backup |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |