+

WO2008019259A2 - Architecture pour une sauvegarde et/ou une récupération de données électroniques - Google Patents

Architecture pour une sauvegarde et/ou une récupération de données électroniques Download PDF

Info

Publication number
WO2008019259A2
WO2008019259A2 PCT/US2007/074863 US2007074863W WO2008019259A2 WO 2008019259 A2 WO2008019259 A2 WO 2008019259A2 US 2007074863 W US2007074863 W US 2007074863W WO 2008019259 A2 WO2008019259 A2 WO 2008019259A2
Authority
WO
WIPO (PCT)
Prior art keywords
backup
data
preferences
user
file system
Prior art date
Application number
PCT/US2007/074863
Other languages
English (en)
Other versions
WO2008019259A3 (fr
Inventor
Pavel Cisler
Steve Ko
Peter Mcinerney
Robert Ulrich
Eric Weiss
Original Assignee
Apple Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Apple Inc. filed Critical Apple Inc.
Priority to EP07813593A priority Critical patent/EP2069935A2/fr
Publication of WO2008019259A2 publication Critical patent/WO2008019259A2/fr
Publication of WO2008019259A3 publication Critical patent/WO2008019259A3/fr

Links

Classifications

    • 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
    • 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/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/1456—Hardware arrangements for backup
    • 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

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.
  • 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 might not be possible to automatically undo any previous edits.
  • a backup daemon can perform backup operations and store the backup date as a file system hierarchy. Additionally, a interface can be provided for setting back up preferences, for example, scheduling of backup operations, particular applications to include in a backup, and a selection of particular backup devices to store backups.
  • a method is provided.
  • a backup process is initialized on a device.
  • An initial backup is performed for the device including storing data from the device on a first storage device.
  • the stored data has a format corresponding to a file system structure of the device.
  • Implementations of the method can include one or more of the following features.
  • the method can further include performing an incremental backup.
  • Performing an incremental backup can include identifying changed data on the device from the initial backup and storing the changed data and data representing a current file system hierarchy of the backup data, where the data representing the current file system hierarchy includes links to data of the initial backup.
  • Initializing a backup process can include loading the backup process at system startup and running the backup process continuously as a background process.
  • Performing an initial backup can include identifying one or more storage devices for storing the initial backup.
  • Identifying changed data can include monitoring for events indicating a change to data on the device. Identifying changed data can include comparing data on the device with the data of the initial backup. Identifying changed data can include identifying a change according to one or more rules defining change events. Performing the incremental backup can further include monitoring system resources identifying system inactivity and initiating the incremental backup when system inactivity is identified. The incremental backup can be performed according to a schedule. The incremental backup can be performed in response to a change in data on the device. [0009] In general, in one aspect, a system is provided. The system includes a graphical user interface. The graphical user interface is configured to present a preferences menu include general preferences and backup device preferences. The backup device preferences including a destination location for a backup.
  • the general preferences include information associated with backup scheduling.
  • Implementations of the system can include one or more of the following features.
  • the preferences menu can include scheduling preferences for scheduling a backup operation.
  • the general preferences can include a plurality of applications for selection as included in a backup operation.
  • a method is provided. A backup system is initiated. One or more preferences are selected for backup operations. One or more backup operations are performed according to the identified preferences, the backup operations generate a backup having stored data corresponding to a file system structure.
  • Implementations of the method can include one or more of the following features.
  • Selecting one or more preferences can include selecting one or more applications to be included in the generated backup, selecting a schedule for performing the backup operations, or selecting a particular storage device of one or more storage devices to store the generated backup.
  • the one or more storage devices can be external storage devices.
  • a storage device can be a remote storage device.
  • the file system structure of the stored backup can be a hierarchical file system.
  • a method is provided.
  • One or more criteria are defined for capturing a state of a view of a user interface.
  • a backup daemon is used to capture the state of the view in accordance with the criteria.
  • a captured view is stored on an external storage device.
  • a prompt is received to suspend presentation of a current view and present the captured view. The captured view is reinstated into the current view of the user interface.
  • FIG. 1 is a block diagram of an example of an architecture for modifying a user interface view in a display environment.
  • FIG. 2 is a block diagram of an example of an architecture for backing up and restoring application files.
  • FIG. 3 shows an example of a desktop user interface for accessing the time machine settings dialog.
  • FIG. 4A shows an example of a time machine settings dialog.
  • FIG. 4B shows another example of a time machine settings dialog for setting general preferences.
  • FIG. 5 shows an example of a time machine settings dialog for setting backup storage device options.
  • FIG. 6 shows an example of a time machine settings dialog over which a pop-up window for a particular storage device is displayed.
  • FIG. 7 shows an example of a time machine settings dialog over which a pop-up window for a newly detected storage device is displayed.
  • FIG. 8 shows an example of a time machine settings dialog for setting backup storage device options in which two devices are available.
  • FIG. 9 shows an example of a time machine settings dialog over which a pop-up window for a particular storage device is displayed.
  • FIG. 10 shows is a flow diagram of a method illustrating a backup process scenario.
  • FIG. 1 is a block diagram of an architecture 100 for capturing at least one earlier version of a user interface view and allowing a user to initiate a restoration based on it.
  • a view refers to an item, element or other content, capable of being stored and/or retrieved in an interface, that can be subjected to a backup operation by a backup component 117 (to be described later).
  • 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.).
  • 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).
  • input devices 114 e.g., keyboard, mouse, etc.
  • output devices 115 e.g., a display device.
  • a user interacts with the architecture 100 via the input and output devices 114, 115.
  • 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.
  • the systems 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.
  • an operating system e.g., MAC OS® X, WINDOWS XP, LINUX, etc.
  • 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.).
  • platforms and/or networks e.g., client/server networks, wireless networks, stand-alone computers, portable electronic devices, mobile phones, etc.
  • software applications e.g., email, media player, browser, etc.
  • the computer 102 includes the backup component 117 (e.g., a backup daemon) that allows for the storage of versions of the computer's files or other items (e.g., restoring a view including past state of a file, application, application data, parameters, settings, and the like), for example within the local storage 106 or in an external storage repository.
  • 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.
  • FIG. 2 is a block diagram of an exemplary architecture 200 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, a state of an application or state of the system, preferences (e.g., user or system preferences), and the like all can be candidates for archiving. Other types of candidates are also possible.
  • the backup component 117 includes a storage device 204 (e.g., a local storage device) and a storage device 232 (e.g., an external storage device). 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.
  • the backup component 117 runs as a background task on an operating system 230, that 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 that 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. Alternatively, the activity monitoring engine 212 triggers a backup event a time in which the user is not actively using the system (e.g., idle time).
  • 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 earlier versions.
  • the preference management engine 214 could determine the frequency of a 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 as to 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 and system settings), a user selection/identification of specific items, 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 with a format corresponding to a file system structure.
  • the file system structure allows the user to navigate data in the stored version.
  • 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 versions 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.
  • the backup component 117 can include a link management engine 224 that coordinates the links between version sets. In such an implementation, the backup component 117 can manage multiple versions of an item using links. There will now be described an example of how links can be coordinated between versions.
  • a first backup archive 206 (“Version A") is a backup version of an item. Version A contains three separate archived items labeled 1, 2 and 3.
  • the Version A corresponds to the contents of the items at a particular point in time.
  • a user in this example changes the item 2 somewhat, for example by editing a document.
  • another capture event creates a second backup archive 208 ("Version B") of the item (e.g., a capture event recognized by the activity monitoring engine 212 or the change identifying engine 218 results in the generation of a second version by the backup capture engine 220).
  • Items 1 and 3 are identical to those in Version A.
  • the link management engine 224 can be used to create a link 205 from the item 1 in Version B to the item 1 in Version A as part of the generation process. Accordingly, only one copy of item 1 is required to be stored within the storage device 204 at the time Version B is created.
  • a link 207 connects item 3 in Version B to the item 3 in Version A.
  • the item 2 in Version B in contrast, is not identical to the item 2 in Version A and is therefore stored in Version B with its current contents.
  • a user can access any of the items in the Version A, or any of the items listed in the Version B, or all of them. In one implementation, the user may not be able to detect that some items are accessed directly (e.g., the item 2 accessed through Version B), and some are accessed using a link (e.g., the item 1 in Version A accessed using the link in Version B).
  • a third backup archive 210 (“Version C”) can then be generated (by for example, the backup capture engine 220).
  • the item 1 in Version C is different from the item 1 in Version A and the modified contents of item 1 are therefore stored in Version C. Accordingly, there is no link equivalent to the link 205 from this item to the item 1 in Version A.
  • the modified contents of the item 3 are stored in Version C.
  • the link management engine 224 can create a link 209 from the item 2 in Version C to the item 2 in Version B as part of the version archive process. In this example, it is seen that the link management engine 224 manages links across multiple version sets. That is, each of Version B and Version C contains one or more links to an earlier version where appropriate. Other configurations of items, item entries and links can be used.
  • a backup preview engine 226 is configured to provide a preview of at least one of the captured earlier versions.
  • the preview can allow a user to peruse the contents of a backup copy of a view (e.g., a file, data, or file set) before opting to restore the element (e.g. file(s)) using the backup restoration engine 222.
  • a backup copy of a view e.g., a file, data, or file set
  • 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 can 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.
  • FIG. 3 is a screen shot 300 depicting a desktop user interface 302.
  • the system where the user interface 302 is generated is provided with a component that captures and manages versions of views (including items such as files, folders, etc.). That component is here referred to as a "time machine".
  • the time machine could be part of the backup component 117.
  • a menu bar 304 within the desktop user interface 302 allows access to the system settings dialog 306.
  • a time machine icon 308 is available within the system settings dialog 306.
  • a user can select the time machine icon 308 to open a time machine settings dialog such as any of the ones portrayed within FIG. 4A-B.
  • the time machine icon 308 is here accessible in the context where the user can configure other system aspects, such as hardware peripherals, system utilities, network connectivity, etc.
  • the time machine engine could be accessible within the desktop user interface 302 itself, through an applications menu or file listing, or as part of the functionality included within another application, etc.
  • FIG. 4A shows a screen shot 400 depicting an example of a time machine settings dialog 402 within the desktop user interface 302.
  • the dialog 402 is generated by the preference management engine 214 (FIG. 2).
  • a general settings tab 404 is selected.
  • a user can select a device name within a drop-down menu 406 to establish a backup location.
  • a drop-down menu 408 can be used to set the frequency of making backups (e.g. every day, every week, every other week, every month, etc.).
  • a time of day or other granularity setting can be available.
  • a setting can allow the user to request that the utility run during a typically inactive period, such as overnight.
  • an event-driven trigger can be specified, such as having the backup utility run upon system start-up.
  • the time machine could be set to back up when there has been activity relating to the item that is to be backed up.
  • the backup operation can be set to run in periods of inactivity when there could be less user demand on system performance.
  • the backup operation can be set to run according to one or more rules, programmatic instructions, or otherwise scheduled.
  • a user can select from a set of applications 410 which type(s) of data is eligible for inclusion in a backup.
  • the applications list can contain specific products or applications (e.g. iTunes) and/or general categories (e.g. photos, address book, e-mail inbox).
  • each application name is individually selectable.
  • the user can set the bookmarks and personal settings to be backed up but not the history or cookies.
  • One implementation could allow a user to select specific disk drives, folders, and/or files for a backup operation.
  • a scroll bar 412 allows the user to view additional applications or candidates that would otherwise not fit within the viewing window.
  • all system data is included in the backup unless excluded by the user.
  • a message block 414 alerts the user as to the date and time of the last backup event. In one implementation, this information is obtained from the backup capture engine 220 (FIG. 2). The user can select a slide bar control 403 to switch the backup operations on or off. A user can select a backup now button 416 to trigger a backup event. In one implementation, the backup now button 416 calls the backup capture engine 220 (FIG. 2) to initiate a capture event using the settings provided within the time machine settings dialog 402.
  • the time machine engine provides a status icon 420 within the menu bar 304 of the desktop user interface 302.
  • the status icon 420 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 420 can provide the user with an additional method of accessing the time machine settings dialog 402. In one implementation, a different type of status indicator could be used, or a different way of initiating it could be provided.
  • a lock icon 419 is selected, the time machine engine backup configuration is essentially locked into place until the icon 419 is selected again.
  • selecting the lock icon 419 in the settings dialog 402 can ensure daily (automatic) backup operations are performed using a backup device (e.g., "Steve's backup device") as the storage medium until the lock icon 419 is selected, thus unlocking the current backup configuration.
  • a backup device e.g., "Steve's backup device
  • a user can select a help button 422 to open a help dialog regarding the time machine engine.
  • the help dialog can be presented within the time machine settings dialog 402 or in a separate pop-up window, for example.
  • a mouse over of individual controls within the time machine settings dialog 402 provides the user with a brief description of that control's functionality.
  • FIG. 4B shows a screen shot 401 depicting another example of the time machine settings dialog 402 in which a general settings tab 404 is selected.
  • the current example lets the user specify content that is not to be backed up.
  • a display window 424 contains sets of information specifying the content(s) that should not be backed up. In this scenario, the default action would be for the time machine to back up all of the information (i.e. all that is stored on the system, storage drive, or storage segment, etc.) unless otherwise instructed within the display window 424.
  • the display window 424 here contains a folder 426 named "Final Cut Pro Documents".
  • the folder 426 has an associated size 428 of 21 GB.
  • An add/delete key 430 allows the user to remove or include items within the display window 424.
  • the user can activate the "+" side of the add/delete key 430 to generate a file system browser to allow the user to select one or more files, folders, etc. to add to the display window 424.
  • by highlighting the folder 426 and activating the "-" side of the add/delete key 430 the user can remove the folder 426 from the display window 424.
  • a scroll bar 432 allows the user to view additional listings (files, folders, application data sets, etc.) that would not otherwise fit within the viewing window. [0056] FIG.
  • FIG. 5 shows a screen shot 500 depicting an example of the time machine settings dialog 402 in which a backup devices tab 502 is selected.
  • a backup devices view 503 allows the user to select one or more repositories for storing archived items.
  • a first device 504 is the only option presently available to the user.
  • a user can select an options button 506 associated with the first device 504 to view a settings dialog for this device. In one implementation, selection of the options button 506 triggers the display of another pop-up window.
  • An information field 508 informs the user of the present size of the archived information. In this example, the backup information is taking up 237 gigabytes of space.
  • a screen shot 600 contains a pop-up window 602 overlaying the time machine settings dialog 402.
  • the pop-up window 602 displays options relating to the first device 504.
  • An information field 604 contains the storage device name, in this example "Device 1".
  • a bar graph 606 illustrates the amount of free space available on the first device 504. According to the text beneath the bar graph 606, 237.04 gigabytes of memory has been used, and 12.96 gigabytes of memory is free on the first device 504.
  • a user can select a checkbox 608 to have the corresponding backup information encrypted.
  • this causes the existing archives within the associated backup device to be placed in an encrypted format.
  • only the archives generated after the time of selecting the checkbox 608 will be generated in an encrypted format.
  • the backup capture engine 220 (FIG. 2) creates the encrypted copies for the archives.
  • a user can select a checkbox 610 to enable the backup component 117 to use the first device 504 as an archive storage location.
  • the name field 604 can be user- selectable to define the storage location in greater detail. For example, a particular segment or segments of a backup device could be selected rather than the entire device.
  • a user can select an OK button 612 to close the popup window 602 and return to the time machine settings dialog 402.
  • FIG. 7 shows a screen shot 700 depicting an example of the time machine settings dialog 402 overlaid by a pop-up window 702 alerting the user to this situation.
  • the message within the pop-up window 702 prompts the user to select whether or not the time machine engine should use this new device for storing archives.
  • the user can select an OK button 704 to accept the device as an additional archive storage repository.
  • user selection of the OK button 704 adds the device information to the options list in preference management engine 214.
  • user selection of the OK button 704 could add the device to the backup devices view 503 within the time machine settings dialog 402 (see FIG. 8).
  • a help button 708 provides the user with more information regarding the addition of the new device.
  • the help button 708 can cause detailed information regarding the device to be displayed within the pop-up window 702.
  • the new storage device automatically appears in the backup devices view 503 (FIG. 5).
  • the user can access the device options in the manner illustrated in FIG. 6 to enable the device as a backup archive repository or to modify or enter specific settings for the device, to name two examples.
  • FIG. 8 shows a screen shot 800 depicting an example of the time machine settings dialog 402 in which a backup devices tab 502 is selected, as in the example in FIG. 5.
  • a second device 802 has been added.
  • the second device 802 could have been detected by the system and selected by the user via an automatic detection pop-up window (FIG. 7).
  • a user can select an options button 804 associated with the second device 802 to view a settings dialog for this device.
  • selection of the options button 804 triggers the display of another pop-up window.
  • a scroll bar 806 allows a user to access additional storage devices that would otherwise not fit into the viewing window.
  • a user is presented with side- by-side displays of storage devices in use and storage devices presently available.
  • the user could add or remove archive repositories, e.g. by dragging and dropping individual storage device listings. Other methods of selecting archive repositories are possible.
  • FIG. 8 a screen shot 900 containing a pop-up window 602 overlaying the time machine settings dialog 402 can then be presented.
  • the pop-up window 602 displays options relating to the second device 802.
  • An information field 604 contains the storage device name, in this example "Device2".
  • a bar graph 606 illustrates the amount of free space available on the second device 802. According to the text beneath the bar graph 606, zero gigabytes of memory have been used, and 250 gigabytes of memory are free on the second device 802.
  • a user can select a checkbox 608 to have the corresponding backup information encrypted.
  • encryption can be an application-wide setting rather than an individual device setting.
  • a user can select a checkbox 610 to enable the backup component 117 to use the second device 802 as an archive storage location.
  • the name field 604 can be user-selectable to define the storage location in greater detail.
  • the user can specify that the second device 802 is a secondary storage archive, and that the first device 504 (FIG. 5) is to be used as the primary archive space. In this manner, once the first device 504 is full, the time machine engine will switch to the second device 802 for archive storage.
  • the user can associate different storage devices with different archive contents.
  • FIG. 10 is a flow diagram of a method 1000 illustrating a backup process scenario.
  • the method 1000 can be performed in a computer system with a storage device, to name one example.
  • the method includes a backup application setup procedure (step 1002).
  • the setup procedure could be available through a graphical user interface (GUI), for example, and could involve recording settings that are entered by the user.
  • GUI graphical user interface
  • the user could be allowed to designate a schedule for running the backup process, one or more storage devices to use for archival storage, a set of items to be backed up, etc.
  • step 1004 the backup application is loaded onto the system.
  • An initialization of the backup process can involve loading the backup process at system startup and running the backup process continuously as a background task. For example, the backup process could run outside of the user space and could occur without requiring user interaction.
  • the method involves performing an initial backup operation (step 1006).
  • the application identifies one or more storage devices for storing the initial backup archives and then stores data from the device on the storage device(s).
  • the stored data can have a format corresponding to a file system structure of the device. For example, this can provide that the stored data can be perused, for instance, using a standard file system navigation application.
  • the backup application could perform an incremental backup operation (step 1008).
  • An incremental backup operation can capture changes in the data since the time of the initial backup process.
  • the backup application can identify data on the device that has changed since the initial backup operation.
  • the backup application can monitor for events indicating a change to data on the device.
  • the backup application can compare data on the device with the data of the initial backup to discover changes.
  • a variety of events could trigger an incremental backup operation.
  • the backup application can monitor system resources to identify a period of system inactivity during which it can initiate an incremental backup operation.
  • the incremental backup could be performed according to a schedule (e.g. daily, weekly, etc.).
  • An incremental backup operation could, in another circumstance, be performed in response to a change in data on the device.
  • a user can designate that an incremental backup operation be automatically triggered whenever the backup application recognizes a change in a particular data set.
  • An incremental backup event can include storing the changed data and data representing a current file system hierarchy of the backup data, where the data representing the current file system hierarchy includes links to data of the initial backup.
  • the incremental back up can create a link to the location of the data within the initial backup archive. Any number of incremental backup events can occur, with each event building upon the linked hierarchical file system structure of backup data sets.
  • the method 1000 could end upon occurrence of an event, such as a predefined ending time, a user input, or system shutdown.
  • 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. [0074] 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.
  • 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.
  • ROMs read-only memories
  • RAMs random access memories
  • EPROMs EPROMs
  • EEPROMs electrically erasable programmable read-only memory
  • magnetic or optical cards or any type of media suitable for storing electronic instructions
  • modules, features, attributes, methodologies, and other aspects can be implemented as software, hardware, firmware or any combination of the three.
  • a component can be 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne des systèmes et des procédés comprenant une architecture de système de sauvegarde pour réaliser des opérations de sauvegarde. Dans une mise en oeuvre, un procédé est proposé. Un procédé de sauvegarde est initialisé sur un dispositif. Une sauvegarde initiale est réalisée pour le dispositif comprenant des données de stockage provenant du dispositif sur un premier dispositif de stockage. Les données stockées ont un format qui correspond à une structure de système de fichier du dispositif.
PCT/US2007/074863 2006-08-04 2007-07-31 Architecture pour une sauvegarde et/ou une récupération de données électroniques WO2008019259A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07813593A EP2069935A2 (fr) 2006-08-04 2007-07-31 Architecture pour une sauvegarde et/ou une récupération de données électroniques

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/499,880 US20080126442A1 (en) 2006-08-04 2006-08-04 Architecture for back up and/or recovery of electronic data
US11/499,880 2006-08-04

Publications (2)

Publication Number Publication Date
WO2008019259A2 true WO2008019259A2 (fr) 2008-02-14
WO2008019259A3 WO2008019259A3 (fr) 2009-05-28

Family

ID=38954768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/074863 WO2008019259A2 (fr) 2006-08-04 2007-07-31 Architecture pour une sauvegarde et/ou une récupération de données électroniques

Country Status (3)

Country Link
US (1) US20080126442A1 (fr)
EP (1) EP2069935A2 (fr)
WO (1) WO2008019259A2 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009109925A2 (fr) * 2008-03-04 2009-09-11 Rico Raja Procédé et appareil pour un déploiement de logiciel personnalisable par utilisateur
EP2477123A3 (fr) * 2011-01-14 2012-11-14 Apple Inc. Documents sans enregistrement
US8775378B2 (en) 2006-08-04 2014-07-08 Apple Inc. Consistent backup of electronic information
WO2015153523A1 (fr) * 2014-04-02 2015-10-08 Microsoft Technology Licensing, Llc État d'enregistrement et de synchronisation de document de conception innovante
US10303652B2 (en) 2011-01-14 2019-05-28 Apple Inc. File system management
US10891020B2 (en) 2007-06-08 2021-01-12 Apple Inc. User interface for electronic backup

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080034019A1 (en) * 2006-08-04 2008-02-07 Pavel Cisler System for multi-device electronic backup
US8370853B2 (en) * 2006-08-04 2013-02-05 Apple Inc. Event notification management
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
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
US7853566B2 (en) * 2006-08-04 2010-12-14 Apple Inc. Navigation of electronic backups
US9009115B2 (en) * 2006-08-04 2015-04-14 Apple Inc. Restoring electronic information
US7853567B2 (en) * 2006-08-04 2010-12-14 Apple Inc. Conflict resolution in recovery of electronic data
US7809688B2 (en) * 2006-08-04 2010-10-05 Apple Inc. Managing backup of content
US7856424B2 (en) * 2006-08-04 2010-12-21 Apple Inc. User interface for backup management
US20080034017A1 (en) * 2006-08-04 2008-02-07 Dominic Giampaolo Links to a common item in a data structure
US20080115141A1 (en) * 2006-11-15 2008-05-15 Bharat Welingkar Dynamic resource management
US20080256312A1 (en) * 2007-04-12 2008-10-16 International Business Machines Corporation Apparatus and method to detect and repair a broken dataset
CN101290577A (zh) * 2007-04-20 2008-10-22 鸿富锦精密工业（深圳）有限公司 嵌入式设备及其加载方法
US8429425B2 (en) 2007-06-08 2013-04-23 Apple Inc. Electronic backup and restoration of encrypted data
US8725965B2 (en) * 2007-06-08 2014-05-13 Apple Inc. System setup for electronic backup
US8745523B2 (en) * 2007-06-08 2014-06-03 Apple Inc. Deletion in 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
US8307004B2 (en) 2007-06-08 2012-11-06 Apple Inc. Manipulating electronic backups
US20080307017A1 (en) * 2007-06-08 2008-12-11 Apple Inc. Searching and Restoring of Backups
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
US8219766B1 (en) * 2008-03-31 2012-07-10 Symantec Corporation Systems and methods for identifying the presence of sensitive data in backups
US8527876B2 (en) * 2008-06-12 2013-09-03 Apple Inc. System and methods for adjusting graphical representations of media files based on previous usage
EP2300921B1 (fr) * 2008-10-30 2011-11-30 International Business Machines Corporation Gestion de copie instantanée
US20100293147A1 (en) * 2009-05-12 2010-11-18 Harvey Snow System and method for providing automated electronic information backup, storage and recovery
US20100306171A1 (en) * 2009-06-02 2010-12-02 Microsoft Corporation Timeline Experience for Restore User Interface
US8972355B1 (en) * 2009-08-31 2015-03-03 Symantec Corporation Systems and methods for archiving related items
CN101901175A (zh) * 2010-02-11 2010-12-01 宇龙计算机通信科技(深圳)有限公司 一种数据备份的方法及电子终端
US8935212B2 (en) * 2010-03-29 2015-01-13 Carbonite, Inc. Discovery of non-standard folders for backup
US8903773B2 (en) * 2010-03-31 2014-12-02 Novastor Corporation Computer file storage, backup, restore and retrieval
US8983870B2 (en) 2010-08-18 2015-03-17 Snap-On Incorporated Apparatus and method for managing software applications using partitioned data storage devices
US8943026B2 (en) 2011-01-14 2015-01-27 Apple Inc. Visual representation of a local backup
CN102495771A (zh) * 2011-09-30 2012-06-13 奇智软件（北京）有限公司 一种基于云架构的终端对象分类备份及恢复方法
WO2013044794A1 (fr) * 2011-09-30 2013-04-04 北京奇虎科技有限公司 Procédé de sauvegarde et de récupération de terminal
CN102508740A (zh) * 2011-10-26 2012-06-20 上海文广互动电视有限公司 文件系统远程复制方法
US10055091B2 (en) * 2013-02-01 2018-08-21 Microsoft Technology Licensing, Llc Autosave and manual save modes for software applications
US10452484B2 (en) * 2014-05-15 2019-10-22 Carbonite, Inc. Systems and methods for time-based folder restore
US10530724B2 (en) * 2015-03-09 2020-01-07 Microsoft Technology Licensing, Llc Large data management in communication applications through multiple mailboxes
US10530725B2 (en) 2015-03-09 2020-01-07 Microsoft Technology Licensing, Llc Architecture for large data management in communication applications through multiple mailboxes

Family Cites Families (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
EP0955591A3 (fr) * 1992-04-30 2004-05-12 Apple Computer, Inc. Procédé et appareil d'organistaion des informations dans un système informatique
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
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
US6604118B2 (en) * 1998-07-31 2003-08-05 Network Appliance, Inc. File system image transfer
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
US5572709A (en) * 1993-06-18 1996-11-05 Lucent Technologies Inc. Using dynamically-linked libraries to add side effects to operations
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
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
US5758359A (en) * 1996-10-24 1998-05-26 Digital Equipment Corporation Method and apparatus for performing retroactive backups in a computer system
US6112318A (en) * 1997-08-11 2000-08-29 Digital Equipment Corporation Performance counters controlled by programmable logic
EP1008048B1 (fr) * 1997-08-29 2001-10-31 Hewlett-Packard Company Systemes de sauvegarde et de recuperation de donnees
JP3547300B2 (ja) * 1997-12-04 2004-07-28 株式会社日立製作所 情報交換システム
US6901493B1 (en) * 1998-02-24 2005-05-31 Adaptec, Inc. Method for protecting data of a computer system
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
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
US6486896B1 (en) * 1999-04-07 2002-11-26 Apple Computer, Inc. Scalable scroll controller
JP2003532169A (ja) * 1999-10-12 2003-10-28 シーエムエス ペリフェラルズ インコーポレイテッド 自動バックアップシステム
US6424626B1 (en) * 1999-10-29 2002-07-23 Hubbell Incorporated Method and system for discarding and regenerating acknowledgment packets in ADSL communications
US6918124B1 (en) * 2000-03-03 2005-07-12 Microsoft Corporation Query trees including or nodes for event filtering
JP3522181B2 (ja) * 2000-03-27 2004-04-26 日本電気株式会社 バックアップデータ管理装置及び方法
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 (ja) * 2000-07-07 2002-01-25 Toshiba Corp 情報処理装置、データバックアップ方法、データバックアッププログラムが記憶された記憶媒体
US7072916B1 (en) * 2000-08-18 2006-07-04 Network Appliance, Inc. Instant snapshot
US6785751B1 (en) * 2000-09-19 2004-08-31 Intel Corporation Method and apparatus for minimizing bus contention for I/O controller write operations
US6728735B1 (en) * 2001-03-12 2004-04-27 Network Appliance, Inc. Restartable dump that produces a consistent filesystem on tapes
US7711771B2 (en) * 2001-05-25 2010-05-04 Oracle International Corporation Management and synchronization application for network file system
US6912645B2 (en) * 2001-07-19 2005-06-28 Lucent Technologies Inc. Method and apparatus for archival data storage
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
JP2003140940A (ja) * 2001-10-19 2003-05-16 Internatl Business Mach Corp <Ibm> 外部記憶装置を管理するプログラム、記録媒体、管理装置及び計算機システム
US6948039B2 (en) * 2001-12-14 2005-09-20 Voom Technologies, Inc. Data backup and restoration using dynamic virtual storage
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
US7620908B2 (en) * 2001-12-28 2009-11-17 Sap Ag Managing a user interface
US20030126247A1 (en) * 2002-01-02 2003-07-03 Exanet Ltd. Apparatus and method for file backup using multiple backup devices
US20030220929A1 (en) * 2002-01-22 2003-11-27 Columbia Data Products, Inc. Managing finite data storage utilizing preservation weights
DE10211606B4 (de) * 2002-03-12 2017-06-08 Kip Cr P1 Lp Datenverarbeitungseinrichtung mit einem Metadatensicherungsmanagement
US6857001B2 (en) * 2002-06-07 2005-02-15 Network Appliance, Inc. Multiple concurrent active file systems
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
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
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
US20050138081A1 (en) * 2003-05-14 2005-06-23 Alshab Melanie A. Method and system for reducing information latency in a business enterprise
CA2525587C (fr) * 2003-05-15 2015-08-11 Comcast Cable Holdings, Llc Procede et systeme de jeu video
US7660817B2 (en) * 2003-05-22 2010-02-09 Microsoft Corporation System and method for representing content in a file system
US7111136B2 (en) * 2003-06-26 2006-09-19 Hitachi, Ltd. Method and apparatus for backup and recovery system using storage based journaling
US7225208B2 (en) * 2003-09-30 2007-05-29 Iron Mountain Incorporated Systems and methods for backing up data files
US7698728B2 (en) * 2003-11-12 2010-04-13 Home Box Office, Inc. Automated playlist chaser
WO2005048085A2 (fr) * 2003-11-13 2005-05-26 Commvault Systems, Inc. Systeme et procede de mise en oeuvre d'un instantane de niveau d'image et de restauration de donnees a volume partiel
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 (ja) * 2003-12-26 2005-07-14 Hitachi Ltd 複数世代のバックアップデータの管理
US7103740B1 (en) * 2003-12-31 2006-09-05 Veritas Operating Corporation Backup mechanism for a multi-class file system
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
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
US20060026218A1 (en) * 2004-07-23 2006-02-02 Emc Corporation Tracking objects modified between backup operations
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
JP4576936B2 (ja) * 2004-09-02 2010-11-10 ソニー株式会社 情報処理装置、情報記録媒体、コンテンツ管理システム、およびデータ処理方法、並びにコンピュータ・プログラム
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
KR100667767B1 (ko) * 2004-10-20 2007-01-11 삼성전자주식회사 홈 네트워크 환경에서 방송 컨텐츠의 백업 기능을 갖춘멀티미디어 장치 및 그 백업 방법
US7531012B2 (en) * 2004-10-21 2009-05-12 Bathium Canada Inc. Thin film electrochemical cell for lithium polymer batteries and manufacturing method therefor
US20060106893A1 (en) * 2004-11-02 2006-05-18 Rodger Daniels Incremental backup operations in storage networks
US20060117309A1 (en) * 2004-11-24 2006-06-01 Upanshu Singhal Software configuration methods and client module communication component
US7788592B2 (en) * 2005-01-12 2010-08-31 Microsoft Corporation Architecture and engine for time line based visualization of data
US7461221B2 (en) * 2005-03-24 2008-12-02 International Business Machines Corporation Apparatus, system, and program for automatic backup of related data
US20080065663A1 (en) * 2005-04-14 2008-03-13 Emc Corporation Reestablishing process context
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
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
CN101300621B (zh) * 2005-09-13 2010-11-10 时空3D公司 用于提供三维图形用户界面的系统和方法
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
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
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
US7698318B2 (en) * 2006-02-10 2010-04-13 Microsoft Corporation Automatically determining file replication mechanisms
JP4749266B2 (ja) * 2006-07-27 2011-08-17 株式会社日立製作所 情報資源の重複を省いたバックアップ制御装置及び方法
US20080033969A1 (en) * 2006-08-04 2008-02-07 Sing Chi Koo Electronic document management method and system
US20080034017A1 (en) * 2006-08-04 2008-02-07 Dominic Giampaolo Links to a common item in a data structure
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
US20080141029A1 (en) * 2006-12-11 2008-06-12 Migo Software, Inc. Digital content protection
US20080177961A1 (en) * 2007-01-23 2008-07-24 International Business Machines Corporation Partial Backup and Restore with Backup Versioning
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

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8775378B2 (en) 2006-08-04 2014-07-08 Apple Inc. Consistent backup of electronic information
US10891020B2 (en) 2007-06-08 2021-01-12 Apple Inc. User interface for electronic backup
WO2009109925A2 (fr) * 2008-03-04 2009-09-11 Rico Raja Procédé et appareil pour un déploiement de logiciel personnalisable par utilisateur
WO2009109925A3 (fr) * 2008-03-04 2009-12-03 Rico Raja Procédé et appareil pour un déploiement de logiciel personnalisable par utilisateur
EP2477123A3 (fr) * 2011-01-14 2012-11-14 Apple Inc. Documents sans enregistrement
US10303652B2 (en) 2011-01-14 2019-05-28 Apple Inc. File system management
WO2015153523A1 (fr) * 2014-04-02 2015-10-08 Microsoft Technology Licensing, Llc État d'enregistrement et de synchronisation de document de conception innovante
US10635540B2 (en) 2014-04-02 2020-04-28 Microsoft Technology Licensing, Llc Modern document save and synchronization status

Also Published As

Publication number Publication date
WO2008019259A3 (fr) 2009-05-28
EP2069935A2 (fr) 2009-06-17
US20080126442A1 (en) 2008-05-29

Similar Documents

Publication Publication Date Title
US20080126442A1 (en) Architecture for back up and/or recovery of electronic data
US7809688B2 (en) Managing backup of content
US9009115B2 (en) Restoring electronic information
US8311988B2 (en) Consistent back up of electronic information
US9454587B2 (en) Searching and restoring of backups
US9286166B2 (en) Electronic backup of applications
US7809687B2 (en) Searching a backup archive
EP2372553B1 (fr) Sauvegarde et restauration d&#39;informations électroniques basées sur application
US8504527B2 (en) Application-based backup-restore of electronic information
US7853567B2 (en) Conflict resolution in recovery of electronic data
US8370853B2 (en) Event notification management
US20080034019A1 (en) System for multi-device electronic backup
US8745523B2 (en) Deletion in electronic backups
US20080034004A1 (en) System for electronic backup
US8468136B2 (en) Efficient data backup
US20080034017A1 (en) Links to a common item in a data structure
US20080307175A1 (en) System Setup for Electronic Backup

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07813593

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

WWE Wipo information: entry into national phase

Ref document number: 2007813593

Country of ref document: EP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载