Abstract: The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

Abstract: The subject technology displays an application window showing first contents of a given level of a hierarchical content structure associated with an electronic device. Upon receiving a first user input, a navigation bar is displayed. The navigation bar displays a path including levels for arriving at the first contents within the hierarchical content structure. The displayed path is determined based on metadata associated with contents displayed in the application window. Responsive to a user selection of one of the items of the hierarchical content structure displayed in the navigation bar, content items displayed in the application window are changed.

Abstract: The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

Abstract: The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

Abstract: A method is provided that includes initiating a copy operation to copy a set of files from a source location on a first storage device to a destination location on a second storage device. Metadata is stored on the second storage device in association with the destination location to include the source location on the first storage device and an indication that the copy operation has been initiated. The metadata is updated with identifying information of files from the set of files successfully copied from the source location to the destination location during the copy operation. After an interruption in the copy operation, the copy operation is resumed based on the metadata identifying the source location of the set of files and the identified files successfully copied from the source location to the destination location prior to the interruption.

Abstract: The subject technology displays an application window showing first contents of a given level of a hierarchical content structure associated with an electronic device. Upon receiving a first user input, a navigation bar is displayed. The navigation bar displays a path including levels for arriving at the first contents within the hierarchical content structure. The displayed path is determined based on metadata associated with contents displayed in the application window. Responsive to a user selection of one of the items of the hierarchical content structure displayed in the navigation bar, content items displayed in the application window are changed.

Abstract: Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described.

Abstract: The embodiments set forth techniques for performing incremental backups of a source file system volume (FSV) managed by a source computing device. According to some embodiments, the source computing device can be configured to generate a current snapshot of the source FSV, where the current snapshot complements a previous snapshot of the source FSV (e.g., established during a previous backup). In some cases, to free up storage space, the data for files belonging to the source FSV can be stripped from the previous snapshot (where metadata for the files remains intact). Next, the source computing device can generate, within a destination storage device, a second snapshot of a destination FSV (that corresponds to the source FSV). In turn, the source computing device identifies changes made to the source FSV based on the current snapshot and the previous snapshot, and reflects the changes within the second snapshot of the destination FSV.

Abstract: The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

Abstract: A set of elements, such as, for example, a path, a directory list, a playlist, and a listing of information associated with a file or a song, may be truncated so that a partial set may be generated and displayed. The truncation may be performed in an intelligent manner to produce a meaningful truncated portion. Such a partial set may be beneficial when the space allotted for display of the set is small to begin with or is reduced. In one implementation, a display size of a set is compared with a size of a display area. A data element is selected based on the comparison, and a display space size is determined for the selected data element. A truncated, yet meaningful, portion is determined for the selected data element, the portion fitting within the display space size.

Abstract: Systems and methods are provided for storing and restoring digital data. A method includes receiving, a first user input requesting that a backup interface be displayed, displaying the backup interface, the backup interface including a display area for presenting at least a first visual representation of an earlier version of a current view and a visual representation of the current view, the earlier version including a first element, receiving, while the backup interface is displayed, a second user input requesting that the current view be modified according to the earlier version, at least with regard to the first element, animating the modification of the first element as moving from the visual representation of the earlier version to the visual representation of the current view, and modifying, in response to the second user input, the current view according to the earlier version, at least with regard to the first element.

Abstract: Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described.

Abstract: Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for file system management. In one aspect, a method includes receiving a request at a kernel to perform a file operation on a particular file; identifying a flag bit associated with the file; invoking user space file handler to perform particular action when the flag bit is set; determining whether notification that action has been performed by file handler is received; and allowing the file operation on the file when notification is received.

Abstract: The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

Abstract: The embodiments set forth techniques for performing incremental backups of a source file system volume (FSV) managed by a source computing device. According to some embodiments, the source computing device can be configured to generate a current snapshot of the source FSV, where the current snapshot complements a previous snapshot of the source FSV (e.g., established during a previous backup). In some cases, to free up storage space, the data for files belonging to the source FSV can be stripped from the previous snapshot (where metadata for the files remains intact). Next, the source computing device can generate, within a destination storage device, a second snapshot of a destination FSV (that corresponds to the source FSV). In turn, the source computing device identifies changes made to the source FSV based on the current snapshot and the previous snapshot, and reflects the changes within the second snapshot of the destination FSV.

Abstract: The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

Abstract: An application-centric model is employed for the storage, searching and retrieval of documents. By entering a command directed to a particular application program, such as clicking on an icon for that program, a user interface panel displays documents stored on the computing device that are associated with that application. From the panel, the user can perform various actions with respect to the displayed documents.

Abstract: Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described.

Abstract: In one embodiment, non-transitory computer-readable medium stores instructions for implementing tagged management of stored items, wherein an embodiment can receive an input indicating the selection of a graphical representation of a file in the GUI of an operating system, and can also receive an input indicating the intent to attach a tag to the file. The system can perform an automatic search through the metadata of files associated with the user and the user account to find the set of files having the tag, responsive to the request to display the set of files. Having located the set of files, an operation can be performed to display the set of files having the requested tag, regardless of the storage location of the files.