Sign up to receive free email alerts when patent applications with chosen keywords are publishedSIGN UP

Abstract:

Systems and methods are provided for performing backup operations while a
user is using a device. In one implementation, a method is provided. A
backup operation of data including a plurality of related items is
initiated. Modifications to one or more items of the plurality of related
items are monitored for during the backup operation. The backup operation
is completed. If a modification occurred to one or more items, a second
backup operation is performed for the modified items.

Claims:

1-20. (canceled)

21. A computer-implemented method performed by one or more processors for
backing up files, the method comprising the following operations:
initiating a backup operation of a plurality of related files;
determining a first file in the plurality of related files was modified
prior to executing the back operation on the first file; executing the
backup operation on the modified first file to generate a backed-up file
of the modified first file; determining the backed-up file of the
modified first file includes data inconsistent with data in a backed-up
file of a second file in the plurality of related files; and replacing
the backed-up file of the modified first file with a version of the first
file that existed prior to the modified first file.

22. The method of claim 21, wherein the plurality of items are
interdependent.

23. The method of claim 21, wherein determining the first file in the
plurality of related files was modified includes identifying an event
notification associated with the first file in the plurality of related
files.

24. The method of claim 21, further comprising monitoring for
modifications to one or more items of the plurality of related items
while replacing the backed-up file.

25. The method of claim 21, further comprising determining a maximum
number of backup operations to perform to complete a backup operation
without modifications occurring during the backup operations.

26. The method of claim 25, further comprising generating an alert in
response to reaching the maximum number of backup operations.

27. The method of claim 26, wherein generating an alert includes
notifying a user.

28. The method of claim 25, further comprising suspending the backup
operation for a predefined period of time in response to reaching the
maximum number of backup operations.

29. A computer program product encoded on a tangible, non-transitory
storage medium, the product comprising computer readable instructions for
causing one or more processors to perform operations comprising:
initiating a backup operation of a plurality of related files;
determining a first file in the plurality of related files was modified
prior to executing the back operation on the first file; executing the
backup operation on the modified first file to generate a backed-up file
of the modified first file; determining the backed-up file of the
modified first file includes data inconsistent with data in a backed-up
file of a second file in the plurality of related files; and replacing
the backed-up file of the modified first file with a version of the first
file that existed prior to the modified first file.

30. The computer program product of claim 29, wherein the plurality of
items are interdependent.

31. The computer program product of claim 29, wherein determining the
first file in the plurality of related files was modified includes
identifying an event notification associated with the first file in the
plurality of related files.

32. The computer program product of claim 29, the instructions further
comprising monitoring for modifications to one or more items of the
plurality of related items while replacing the backed-up file.

33. The computer program product of claim 29, the instructions further
comprising determining a maximum number of backup operations to perform
to complete a backup operation without modifications occurring during the
backup operations.

34. The computer program product of claim 33, the instructions further
comprising generating an alert in response to reaching the maximum number
of backup operations.

35. The computer program product of claim 34, wherein generating an alert
includes notifying a user.

36. The computer program product of claim 33, the instructions further
comprising suspending the backup operation for a predefined period of
time in response to reaching the maximum number of backup operations.

37. A device, comprising: memory for storing back up data; and one or
more processors configured to: initiate a backup operation of a plurality
of related files; determine a first file in the plurality of related
files was modified prior to executing the back operation on the first
file; execute the backup operation on the modified first file to generate
a backed-up file of the modified first file; determine the backed-up file
of the modified first file includes data inconsistent with data in a
backed-up file of a second file in the plurality of related files; and
replace the backed-up file of the modified first file with a version of
the first file that existed prior to the modified first file.

38. The device of claim 37, wherein the processors configured to
determine the first file in the plurality of related files was modified
includes the processors configured to identify an event notification
associated with the first file in the plurality of related files.

39. The device of claim 37, the processors further configured to monitor
for modifications to one or more items of the plurality of related items
while replacing the backed-up file.

40. The device of claim 37, the processors further configured to
determine a maximum number of backup operations to perform to complete a
backup operation without modifications occurring during the backup
operations.

Description:

RELATED APPLICATIONS

[0001] This application is generally related to the following jointly
owned and co-pending patent applications, each incorporated herein by
reference in its entirety:

[0015] A hallmark of modem 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.

[0016] 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.

[0017] 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 can not be possible to
automatically undo any previous edits.

SUMMARY

[0018] Systems and methods are provided for performing backup operations
(e.g., using a backup daemon) while a user is using a device. An
algorithm or other monitoring can be used to detect changes that occur
during the backup operation in order to maintain consistency between
related data in the backup. The back up can be performed again for
related data that was modified during prior backup operation.

[0019] In general, in one aspect, a method is provided. A backup operation
of data including a plurality of related items is initiated.
Modifications to one or more items of the plurality of related items are
monitored for during the backup operation. The backup operation is
completed. If a modification occurred to one or more items, a second
backup operation is performed for the modified items.

[0020] Implementations of the method can include one or more of the
following features. The method can further include determining which
items of data are related. The monitoring for modifications can include
identifying event notifications associated with an item of the plurality
of related items. Performing a second backup operation can include
replacing the backup data for an item with backup data from the second
backup. The method can further include monitoring for modifications to
one or more items of the plurality of related items during the second
backup operation. The method can further include determining a maximum
number of backup operations to perform to complete a backup operation
without modifications occurring during the backup operations. If the
maximum number of backup operations is reached, an alert can be generated
including notifying a user. If the maximum number of backup operations is
reached, the backup operation can be suspended for a predefined period of
time.

[0021] In general, in one aspect, a method is provided. A criterion for
capturing a state of a view of a user interface is defined. The state of
the view is captured in accordance with the criterion. Capturing the
state includes monitoring for modification of the state of the view
during the capture and performing a second capture for the modification
of the state of the view. A prompt is received to suspend presentation of
a current view and present a captured view. The captured view is
reinstated into the current view of the user interface.

[0022] Particular embodiments of the subject matter described in this
specification can be implemented to realize one or more of the following
advantages. Changes to data being included in a backup operation can be
detected. If changes are detected, additional backup operations can be
performed in order to prevent inconsistent data in a backup, particularly
related data.

[0023] 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.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG. 1 is a block diagram of an example of an architecture for
modifying a user interface view in a display environment.

[0025] FIG. 2 is a block diagram of an example of an architecture for
backing up and restoring.

[0028]FIG. 5 is a flow chart of exemplary operations that can be
performed in a backup procedure.

[0029] FIG. 6 shows a screen shot depicting an example of a time machine
settings dialog within a desktop user interface.

[0030] FIG. 7 shows a screen shot depicting an example of a time machine
settings dialog in which a backup options tab is selected.

[0031] FIG. 8 is a screen shot depicting an example of a time machine user
interface after the time machine engine has been activated.

[0032] FIG. 9 is a screen shot depicting another example of a time machine
user interface after the time machine engine has been activated.

DETAILED DESCRIPTION

[0033] FIG. 1 is a block diagram of an architecture 100 (e.g., a hardware
architecture) for capturing at least one earlier version of a user
interface view and allowing a user to initiate a restoration based on it.
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 the backup 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. 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.

[0034] 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.

[0035] While modifications of a user interface view are 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.

[0036] Systems and methods are provided for modifying an interface view
(e.g., a user interface view). Systems and method are also provided for
performing consistent backup operations while data on a device is being
modified. 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 modifying a user
interface view is disclosed. 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 the backup component 117.

[0037] Though discussion is made with reference to modifying a 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 can be
the most apparent change from the user's perspective, this is
accomplished through the corresponding changes in the underlying system
content.

[0038] 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 the computer 102. 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.).

[0039] The computer 102 includes the 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. In one implementation, 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.

[0040] FIG. 2 is a block diagram of an exemplary architecture (e.g.,
software architecture) 200 for enabling the back up and restoration of
elements of items such as, application files, for example, those
associated with a set of application programs 228.

[0041] Each application program 228 can include an application programming
interface (API) 229. The architecture 200 can utilize API 229 techniques
to access application programs and enhance them with further
functionality. For example, the API 229 can link several applications
together for providing a single service on all linked applications.
Particularly, the time machine architecture can utilize API techniques to
enhance application programs with the time machine functionality. The API
tools can link several applications to the time machine engine by using
an API for providing a similar menu or icon for each application. For
example, the API can be used by the time machine when generating a backup
version of a current state of the application. As another example, the
API can be used when the application is restored, through the time
machine, to a state that corresponds to a backup version. Although the
API 229 is shown in FIG. 2 as part of application programs 228, the API
can be separate from the application programs 228. For example, the API
229 can be separately located and made available by the system for use by
one or more of the application programs 228.

[0042] In one implementation, the backup component 117 provides back up
and restoration capability for the system. Many different items or
elements can be the subject of a back up in the system. For example,
folders, files, items, information portions, directories, images, system
parameters, playlists, address books, e-mails, e-mail folders,
application states and the like all can be candidates for archiving.
Other types are also possible. In this example, the backup component 117
includes a local storage device 204 and an external storage device 232.
Versions can be stored on either of them. Any number of local and/or
external storage devices can be used by the backup component 117 for
storing versions. In one implementation, no local storage is provided.

[0043] In one implementation, one copy of original data (e.g., folders,
files, items, information portions, directories, images, system
parameters, playlists, address books, e-mails, e-mail folders,
application states, preferences, and the like) is stored in the system in
addition to the original. When one or more subsequent copies are made,
each one can contain only the differences between the current data
version and the original data version, thereby saving storage space. In
some implementations, the storage devices 204 and 232 can be used to
store the original versions of the data as well as links pointing to the
original versions. The links can be hard links which reference, or point
to, physical data, or as another example can be symbolic links that
reference another file on the storage device (e.g., by name or location).

[0044] The backup component 117 can interact with one or more of the
applications using the corresponding API. In one implementation, this can
provide backing up of that application's files, state or other items, and
can provide for user restoration of a selected backed up version, to name
two examples. In one implementation, the backup component 117 runs as a
background task on an operating system 230, where the task is not visible
to the user. The backup component 117 can be capable of running across
multiple user accounts.

[0045] The backup component 117 includes an activity monitoring engine
212. In one implementation, the activity monitoring engine 212 monitors
for changes within applications (e.g., application files or state) that
are targeted for backup operations. A change can also include the
addition of new files or other data structures, or deletion of existing
ones. For example, the activity management engine 212 can be responsible
for verifying the integrity of a playlist in a music file management
program, or for verifying that a corresponding song file exists for a
listed song.

[0046] In one implementation, 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. In one implementation, 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.

[0047] A preference management engine 214 specifies some operating
parameters of the backup component 117. In one implementation, 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 views. For example,
the preference management engine 214 can determine the frequency of a
backup capture, the storage location for the backup versions, the types
of elements (e.g., files or other items) that are eligible for backup
capture, and the events which trigger a backup capture (periodic or
event-driven, etc.).

[0048] 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 in an inbox, an
address book, 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, the backup component 117 stores the
versions in a format corresponding to a file system structure.

[0049] A backup management engine 216 coordinates the collection, storage,
and retrieval of views performed by the backup component 117. For
example, 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.

[0050] A change identifying engine 218 locates specific files 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. For example, the change identifying engine 218
can identify a loss of data associated with a user's current view. In one
implementation, the change identifying engine 218 traverses a target set
of files or other items, comparing a previous version to the current
version to determine whether or not a modification has occurred. In
addition, the change identifying engine 218 can generate an alert
identifying the loss of data, and prompt the user to initiate a previous
version of the current view to restore the lost data. For example, the
change identifying engine 218 can be responsible for verifying whether a
data loss has occurred in a music file management program, or for
verifying that a corresponding song file is unchanged for a listed song.

[0051] A backup capture engine 220 locates views (e.g., elements, files 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.

[0052] The backup component 117 includes a backup restoration engine 222
to restore previous versions of views (e.g., files or other items). In
one implementation, 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.

[0053] The backup restoration engine 222 can initiate data backup
operations on one or more data elements or items as directed by a user,
the system, or according to a predetermined or otherwise defined
schedule. For example, the user can set up a scheduled backup operation
to occur for any number of data files. The data files can be related to
one another, such as when the files share similar attributes or a schema.
For example, several files included on one particular webpage can have a
similar schema and can require versions of each related file to remain
consistent to display a successful webpage image. Unless the backup
operation is completed in a very short amount of time, there is a chance
that one or more of the files to be included in the backup can be
modified before the backup operation is complete. For example, the backup
operation can be performed while a computer system is in use (e.g.,
executing operation received from a user). The use of the computer system
during a backup operation can introduce inconsistencies between backed up
data files and data files currently awaiting the backup operation. In
this example, such changes are monitored and the backup operation can be
tailored to take them into account. If inconsistencies are found between
files, the backup restoration engine 222 can attempt to resolve any
discrepancies between data files.

[0054] FIG. 3 is a block diagram 300 schematically depicting a data backup
operation. The block diagram 300 schematically shows a folder 302 and a
backup 304. The folder 302 can include several files or other items. For
example, when the backup operation is initiated, a folder 306 includes
file A, file B, and file C. The system monitors any changes in the
files/items while a backup operation is being performed.

[0055] The backup 304 can over time include copies of files, such as file
A, file B, or file C, as they are backed up. Files stored in the backup
folder 304 can be exact copies of the original folder 102 contents, or a
modified portion thereof. As shown in FIG. 3, the backup component 117
has been instructed to back up the files A, B and C included in the
folder 306. At time TA, a backup operation has been initiated and
begins to backup files. For example, the backup operation has
successfully backed up file A in a backup folder 310. At time TB
thereafter, the user makes a modification to file A in folder 306, thus
changing the file A to file A'. In this description, when a user modifies
a file during the backup operation, the file name is modified to include
an inversion mark, or a prime mark (e.g., modifications to file A are
notated as file A'). Similarly, the user at time TB changes the file
C to C'. File A has been successfully backed up at time TA, and the
new modification can create an inconsistency in the data.

[0056] At time TB, file B is successfully backed up to backup folder
310. The time machine engine can continue to backup data at time Tc
adding file C' from folder 306 to folder 310. Upon nearing the end of the
group of files to back up, the time machine engine can now resolve the
inconsistency at time TD. At TD, the backup folder 310 is
modified based on a change that was detected during the back up.
Particularly, the backed up file A is replaced with the file A'. This
backup modification operation was triggered by detecting the change
between the original file A and the new file A'. Thus, if the folder 310
is used in a restoration operation in the future, it will restore the
files A', B and C' to the system, rather than the files A, B, and C'
which was the state of the backup folder at Tc. Thus, the change in
the backup folder at TD seeks to give that folder the state that the
folder 306 had when the backup was completed at Tc.

[0057] In some implementations, the time machine engine can determine that
particular files are related to one another. In the example in FIG. 3,
the user can have set the time machine engine to resolve changes in
related files before completion of the first backup. In such
implementations, the subsequent modification of the backup folder is done
only if there is a change in a related file. Here, changing file A to
file A' can alter a link or shared relationship to file B. For example,
when file A changes to file A', the time machine engine can modify an
associated link or relationship within file A to allow the correlation
between file A (now modified to file A') and file B to remain intact. In
some implementations, a user can define files as being related through a
predefined relationship between the original files or file structures. In
some implementations, the user can receive an alert or message stating
that the inconsistency has been found, and further, can be prompted to
make a decision about performing another backup operation. In other
implementations, the backup process can not attempt to determine a
relationship between files.

[0058] In some implementations, a backup operation can begin automatically
when the backup management engine 216 is invoked to compare data captured
by the backup capture engine 220 with data identified in the change
identifying engine 218. For example, when the user modifies a previously
backed up file, the backup management engine 216 can be invoked to begin
the comparison of data. If changed data has been identified, the change
identifying engine 218 informs the backup management engine 216 that a
change has occurred. Next, the backup management engine 216 can query the
preference management engine 214 to determine whether or not to attempt
an additional backup operation for the modified files. The preference
management engine 214 can inform the backup management engine 216 of any
predetermined preferences and an additional backup operation can ensue.

[0059] Upon initiating each backup operation, the time machine engine can
begin monitoring for additional modifications (e.g., using an event
monitor or detector such as FS Events which monitors file system
changes). If additional modifications to the data identified as part of
the backup operation (e.g., an incremental backup of particular changed
files) occur during the time of the backup operation are detected, the
time machine engine can attempt to resolve each conflict. In one
implementation, any changes to data other than the data being included in
the backup will not impact the backup data and will be captured during
the next backup operation. Moreover, while the post-backup modification
of the backup folder is being done, the system can monitor for additional
changes in any of the files involved. If such additional changes are
found, the system can perform an additional modification of the backup
folder. In some implementations, the user can predetermine a maximum
number of such iterations to perform. Upon completing the maximum number
of backup operations, the time machine engine can inform the user that a
maximum number of backup operations has completed, and further backups
can not be performed on the current data. In other implementations, the
iterative updates of the backup folder can continue until no further
changes of the files at issue are detected.

[0060] In an alternative implementation, a notification system provides
notifications to the time machine engine when a change is detected. For
example, an event notification system can provide a notification when a
change to one of the files in the backup operation is detected (e.g.,
using event detector such as FS Events). For example, if a file in the
backup is written to during the backup operation, the change can be
logged by an event detector. The event detector can then notify the time
machine engine that the file has been written to.

[0061] In some implementations, the time machine engine can detect
modifications occurring to previously backed up data and ignore the
conflict the modified data can create. For example, the user can set the
time machine engine to never resolve backup conflicts and therefore the
time machine engine stores elements in the version that is available to
the system. Specifically, modified files are stored in their modified
state if the backup operation occurred after the modification.

[0062] In some implementations, a modification can be ignored because the
change is insignificant. For example, a file attribute modification, such
as which particular user opened the file most recently can be ignored
because it is not significant to the file content. In some
implementations, a modification can be ignored because the change creates
a conflict in the system. For example, the system can ignore all
modifications and back up an original version of elements corresponding
to the state when the backup process began. These determinations can be
made by the change identifying engine 218.

[0063] When the time machine engine determines that a change has occurred
during a backup operation, several options can be presented to the user
during or after the initial backup operation. In the example above, the
time machine modified an initial backup file to restore a file
relationship between the files. In some implementations, the time machine
engine can automatically resolve the changed file inconsistencies
(replace data) until a maximum number of iterations occurs, in which case
the user can be prompted to make a decision regarding subsequent backup
operations. In some implementations, the time machine engine can notify
the user each time a change has occurred during a backup operation. If
modifications to backup data cannot be resolved because the user is
modifying too many files during the backup operation, the time machine
engine can attempt to resolve the data when the computer system is not in
use.

[0064] FIG. 4 is a block diagram depicting another data backup operation.
In contrast to the example in FIG. 3, the system here will, upon
detecting a change made during the backup process, modify the backup
folder to correspond to the state when the backup process began. The
block diagram 400 schematically shows a folder 402 and a backup 404. The
folder 402 can include several files in a computer system. Similar to the
example described with respect to FIG. 3, a folder 406 includes file A,
file B, and file C when the backup operation is initiated. As described
earlier, the backup 404 (in analogy to the backup 304) can over time
include copies of files, such as file A, file B, or file C, as they are
backed up. As shown in FIG. 4, the backup component 117 (FIG. 1) has been
instructed to back up the files A, B and C included in the folder 406. At
time TA, a backup has been initiated and begins to backup files. For
example, the backup operation has successfully backed up file A in a
backup folder 410. At time TB thereafter, the user makes a
modification to file A in folder 406, thus changing the file A to file
A'. Similarly, the user at time TB changes the file C to C'. At time
TB, file B is successfully backed up to backup folder 410. The time
machine engine can continue to backup data at time Tc adding file C'
from folder 406 to folder 410.

[0065] Upon nearing the end of the group of files to back up, the time
machine engine can now resolve the inconsistency at time TD. In the
example in FIG. 3, the time machine engine attempted to resolve the
conflict by performing subsequent backup operations to capture
modifications to each file. Here, the time machine engine will
deliberately ignore, at least for the time being, the modifications made
to one or all of the files. At TD, the backup folder 410 is modified
using the version of each file when the backup operation was initiated.
Particularly, the already backed up file C' in the backup 404 is replaced
with the file C that existed when the backup operation was initiated.
This backup operation was triggered by detecting that a change between
the original file C and the new file C' occurred after the backup
operation had begun. Thus, the change in the backup folder at TD
seeks to give that folder the state that the folder 302 had when the
backup operation was initiated. The current state of the folder 402, A' B
C', can be backed up in a subsequent backup procedure.

[0066] In some implementations, the time machine engine can trigger
another backup operation because a file modification was detected to one
file, but not others. For example, modifying files that are related can
introduce a conflict because related files can require a specific
hierarchy or formatting to function properly in the computer system 102.
The time machine engine can monitor file changes and check for any
relatedness to other files in the system. Thus, modifying one file and
not its related counterparts can trigger one or more future backup
operations.

[0067]FIG. 5 is a flow chart of exemplary operations 500 that can be
performed to backup elements or items, such as data files and folders.
The operations 500 can be performed by a processor executing instructions
stored in a computer program product. The operations 500 begin in step
502 with initiating a backup operation of data. For example, a user can
choose to back up files or folders on a particular time schedule, and the
time machine engine can begin the backup operation according to the time
schedule. In step 504, the operations comprise monitoring for file
modification to one or more items of the related items during the backup
operation. For example, the time machine engine can monitor file changes
made by a user and determine whether or not the modifications cause an
inconsistency between related items. In some implementations, the time
machine engine can initially ignore modifications that have been made to
related files, and back up the original files before determining whether
or not the modifications cause an inconsistency in the files. The initial
backup operation is completed in step 506.

[0068] The time machine engine monitors, in step 508, modifications that
can occur during the backup operation. A query can be sent to a
processing device, such as the backup management engine 216, for example,
to determine whether or not modifications occurred during a particular
backup operation. If modifications did not occur during the backup
operation, the backup can be determined complete, in step 510. If
modifications did occur, the time machine engine can modify a backup
version, in step 512. In one implementation, the backup version is
modified to correspond to the state that the files (or other items) have
at the end of the initial backup operation, for example as described with
reference to FIG. 3. In another implementation, the backup version is
modified to correspond to the state that the files (or other items) have
at the beginning of their initial backup operation, for example as
described with reference to FIG. 4. In some implementations, the user can
be given a prompt or an option to decline further backup operations. For
example, when a modification is insignificant to the structure and
content of the files (e.g., a title change or file name change), the time
machine engine can present a pop-up window containing a decline or ignore
option. Upon completion of the backup operation, in step 514, it can be
determined whether or not modifications have occurred during the backup
operation. If modifications did not occur during the backup operation,
the backup can be determined complete, in step 510. When modifications
have occurred during a backup operation, a query can be sent to determine
whether or not additional backup operations can be allowed, in step 516.
For example, a user can set a maximum number of backup operations that
can be carried out by configuring the time machine engine with a
predetermined number of iterations. If further backup operations are
allowed, the back up can be performed again to resolve the
inconsistencies, in step 512. The time machine engine can attempt to
resolve inconsistencies by performing steps 512, 514, and 516 until the
maximum number of iterations has been reached. Upon reaching the maximum
number of backup operations, the time machine engine can generate an
alert to the user, in step 518. The alert can notify the user of the
intended resolution and can allow the user to decline, continue, or
modify the backup operation. In some implementations, the user can choose
to be prompted each time the time machine engine triggers the performance
of the backup operation.

[0069] FIG. 6 shows a screen shot depicting an example of a time machine
settings dialog 602 within a desktop user interface 604. In one
implementation, the dialog 604 is generated by the preference management
engine 214 (FIG. 2). A general settings tab 604 is selected. A user can
select a drop down menu 606 to establish backup location. The user can
select a slide bar control 603 to switch the backup operations on or off.
A drop-down menu 608 can be used to set the frequency of making backups
(e.g. every day, every week, every other week, every month, etc.). In
another implementation, a time of day or other granularity setting can be
available. Such a setting would allow the user to request that the
utility run during a typically inactive period, such as overnight. In one
implementation, an event-driven trigger can be specified, such as having
the backup utility run upon system start-up. In another example of an
event-driven trigger, the time machine could be set to back up when there
has been activity relating to the item that is to be backed up. In one
implementation, the backup operation can be set to run in periods of
inactivity when there can be less user demand on system performance.

[0070] A user can select from a set of applications 610 which type(s) of
data is eligible for a backup. The applications list can contain specific
products (e.g. iTunes) and/or general categories (e.g. photos, address
book, e-mail inbox). In one implementation, each application name can be
individually selectable. For example, within an internet browser
application, the user can set the bookmarks and personal settings to be
backed up but not the history or cookies. One implementation can allow a
user to select specific disk drives, folders, and/or files for inclusion
in a backup.

[0071] A message block 614 alerts the user as to the date and time of the
last backup event. As shown in FIG. 6, the last backup occurred thirty
minutes earlier. In one implementation, this information is obtained from
the backup capture engine 220 (FIG. 2). A user can select a backup now
button 616 to trigger a backup event. In one implementation, the backup
now button 616 calls the backup capture engine 220 (FIG. 2) to initiate a
capture event using the settings provided within the time machine
settings dialog 602.

[0072] If a checkbox 618 is selected, the time machine engine provides a
status icon 620 within a menu bar 621 of the desktop user interface 604.
The status icon 620 can alter in appearance depending upon the time
machine engine's status, e.g. when the time machine engine is disabled,
when it is actively backing up files, or when it is in standby mode, etc.
The status icon 620 can provide the user with an additional method of
accessing the time machine settings dialog 602. In one implementation, a
different type of status indicator can be used, or a different way of
initiating it can be provided.

[0073] If a lock icon 619 is selected, the time machine engine backup
configuration is essentially locked into place until the icon 619 is
selected again. For example, selecting the lock icon 619 in the settings
dialog 602 can ensure daily (automatic) backup operations are performed
using backup device 606 ("Steve's backup device") as the storage medium
until the lock icon 619 is selected, thus unlocking the current backup
configuration.

[0074] A user can select a help button 622 to open a help dialog regarding
the time machine settings. The help dialog can be presented within the
time machine settings dialog 602 or in a separate pop-up window, for
example. In another implementation, a mouse over of individual controls
within the time machine settings dialog 602 can provide the user with a
brief description of that control's functionality.

[0075] FIG. 7 shows a screen shot depicting an example of the time machine
settings dialog 602 in which a backup options tab 702 is selected. A
backup options view 704 allows the user to configure the process of
storing archived items. In this example, several options are presently
available to the user. A user can select a "Most Current Version(s)"
option 706 to indicate that the backup should include the most current
versions of data each time a backup operation occurs. In one
implementation, this corresponds to the example in FIG. 3. The user can
also choose a "Prompt Me" option 708 to be prompted each time a backup
operation is initiated. The user can then decide whether or not to back
up the current version, or alternatively decide to back up multiple
versions of consistent data. For example, the user can choose to back up
the original version, and a second, resolved version. In addition, the
user can select a "Wait for Inactivity" option to postpone the backup
operation until the data is not being used, or similarly, when the user
is not actively using the computer system.

[0076] As shown in FIG. 7, the user can also select a "Version(s) when
Backup Initiated" option 712 to back up data as it existed when the
backup operation initiated. In this example, the time machine engine can
store the version available at the time of a backup operation. In one
implementation, this corresponds to the example in FIG. 4. Thus, any
modifications made after the backup operation has been initiated would
not be included in the current backup version. In some implementations,
the user can be prompted to save one or more versions of the files if an
inconsistency is identified.

[0077] Another option available in the backup options view 704 is a
"Significant Changes Only" option 714. The "Significant Changes Only"
option 714 can use predefined or user-entered criteria to determine which
changes are sufficient to trigger a new backup version. The "Significant
Changes Only" option 714 can be applied to both the "Most Current
Version(s)" option 706 and the "Version(s) when Backup Initiated" option
712.

[0078] The backup options view 704 includes a "Number of Iterations"
option 716 allowing the user to limit the number of times a backup
operation is attempted when the monitoring detects changes being done
during the backup operation.

[0079] As noted above, the management of backup versions can be handled by
the backup component 117 (FIG. 1). That component can generate a time
machine interface with which the user can control the restoration of
selected content and see the results thereof. Such an interface can be
generated by the backup restoration engine 222 (FIG. 2). There will now
be described an example of how such an interface can reflect a
modification of a previously backed up element. FIG. 8 is a screen shot
depicting an example of a time machine user interface after the time
machine engine has been activated. The time machine interface 802
includes a presentation window 804, a timeline 806, and function buttons.
The timeline 806 presents a history view associated with the current
view. The time machine interface 802 is shown in FIG. 8 as a layer
differentiated from the desktop user interface 800 by a dashed line
around the perimeter of the user interface. In one implementation, the
desktop user interface 800 and an associated application window are
obscured or otherwise hidden while the time machine is active.

[0080] The presentation window 804 can show the currently selected
snapshot, or a portion thereof. As used herein, a snapshot refers to a
backup element stored in an archive that includes a backup of selected
items or content as specified by the backup component 117. Alternatively,
the presentation window 804 can show a selected one of several available
snapshots. In one example, a user can operate the time machine interface
802 so as to sequentially select each snapshot and can restore elements
from these selected snapshots until the current version engulfs the
entire history of the timeline 806, or some portion thereof. For example,
the user can select a snapshot in the timeline 806 and merge its contents
with the contents of the current presentation window 804 by restoring
each element individually, and keeping both versions in some cases, to
achieve a merged list of elements. In some implementations, the active
window can be scaled upon entering the time machine to fit within the
interface. For example, if an application is running in full screen mode
(e.g., iTunes) when the time machine session is initiated, the
application window can be scaled down to fit within the time machine
interface.

[0081] The timeline 806 can include a number of snapshots representing
slices of time for active window elements. Each snapshot provides a
screenshot representation of an earlier version of the selected
application at a particular point in time. The snapshots can represent
periodic backup points in time or can represent snapshots of the active
window where a change has occurred.

[0082] Arrow buttons 807a and 807b shown to the left and right of the
snapshots allow the user to navigate additional snapshots not shown, thus
there can be a large number of snapshots to select from.

[0083] In some implementations the timeline 806 includes a visual
representation of elements, and can appear across the top portion of the
time machine interface 802 (as shown). Alternatively, the timeline 806
can not appear in the top portion of the time machine interface 802 until
a user moves their cursor to the top portion of the time machine
interface 802.

[0084] In alternative implementations, all snapshots can be shown
according to when they are taken regardless of changes between snapshots.
In another alternative implementation, the snapshot can indicate a range
of time covered by a single snapshot where no changes have occurred
(e.g., Jun. 1-Aug. 8, 2005). In another implementation, the rate of
snapshots can vary over time. For example, there can be a number of
snapshots in the newest archives, but the snapshots become more spaced in
time as they reach further into the past. For example, hourly snapshots
for the current day can turn into daily snapshots, which turn into weekly
snapshots that become monthly snapshots as their file dates reach further
into the past. The transition to later snapshots can be achieved, in one
implementation, by selecting a representative snapshot from a group of
snapshots and deleting the rest.

[0085] As shown in FIG. 8, a most recent snapshot 810 is shown with a
highlighted border. This represents the present state of the contents of
the presentation window 804. The other snapshots shown in the timeline
806 represent states of the selected application in the past. For
example, the snapshot 812 represents a state that the folder 306 (FIG. 3)
has at the time TA. As such, the snapshot 812 corresponds to a
backup performed at or before TA. Next, a snapshot 813 is the backup
ultimately created in the FIG. 3 example. As described above, changes are
monitored during the backup operation and the backup folder is modified
to include A', B and C', the state at the end of the initial backup
operation. Accordingly, the snapshot 813 here is identical to the most
recent snapshot 810, which corresponds to the current state.

[0086] The other snapshots in the timeline 806 can show other
configurations of past states of the selected application. For example,
different numbers of elements show additions and deletions have occurred
over time. The time machine interface 802 can also show modifications
that have been made between different versions of folders, files, or
items, and the like.

[0087] The time machine interface 802 includes a restore button 814, a
changed items only button 816, and an information button 818. Other
buttons are possible. The restore button 814, when selected, restores the
window to the selected state represented by the selected snapshot
presented within the presentation window 804 and exits the time machine
interface 802 (e.g., restoring the desktop user interface 800). A user
can select a snapshot and then select the restore button 814 to modify
the current version of the element selected. The changed items only
button 816 filters the snapshots to show only those that differ vary from
the current state. That is, the changed items only button 816 does not
refer to the incremental changes between snapshots in the timeline 806,
rather, it refers to omitting those snapshots whose states are identical
to the current state of the selected application window. For example, if
the most recent snapshot 810 is identical to a snapshot 812 that occurs
earlier in time, selecting the changed items only button 816 will cause
the time machine to cease displaying one of the copies, e.g., remove the
snapshot 812 from the timeline. This can help the user locate a previous
version from which to restore contents different than those in the
current version.

[0088] The information button 818 provides information regarding the
selected snapshot. In one implementation, selecting the information
button 818 opens a panel display. The panel display provides, in one
implementation, information including: the date and time the snapshot was
made; the location of actual elements of a snapshot; the size of the
snapshot; and a comment section.

[0089] There will now be described an example of how a time machine
interface can reflect a backup created when file modifications during
backup operations are deliberately omitted. FIG. 9 is a screen shot
depicting another example of a time machine user interface after the time
machine engine has been activated. A most recent snapshot 902 is shown
with a highlighted border. This represents the present state of the
contents of the presentation window 804. The other snapshots shown in the
timeline 806 represent states of the selected application in the past.
For example, the snapshot 812 represents a state that the folder 406
(FIG. 4) has at the time TA. As such, the snapshot 812 corresponds
to a backup performed at or before TA. Next, a snapshot 904 is the
backup ultimately created in the FIG. 4 example. As described above,
changes are monitored during the backup operation and the backup folder
is modified to include A, B and C, the state at the beginning of the
initial backup operation. Accordingly, the snapshot 904 here is identical
to the snapshot 812, which corresponds to the state of the folder at time
TA.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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 can 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.