Apple Inc.

Christopher A Wolf

Pavel Cisler

Eric A Weiss

Loic E Vandereyken

Bertrand Serlet

Darin Benjamin Adler

Maciej Stachowiak

Christina Elizabeth Warren

David Vernon Payne

Dominic Benjamin Giampaolo

Kevin Tiene

David Joshua Hart

Robert R Ulrich

Jack R Matthew

Kristen A McIntyre

Daniel I Feldman

Pavel Sokolov

Erika Misaki

Mike Metas

Robert M Cadwallader

Richard B Blair

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.

Techniques for preserving clone relationships between files

The described embodiments set forth techniques for providing a backup progress estimate for a backup of a source file system volume (FSV). The techniques involve determining, for the source FSV, a backup size during performance of backup operations. The operations can include determining the backup size based on a number of files on the source FSV. Additionally, the operations can include copying files of the source FSV and/or propagating corresponding files of a destination FSV to a location of the backup of the source FSV on a destination storage device and updating one or more metrics using a number of files and/or a number of bytes copied and/or propagated to the backup. In this manner, a progress indication for the backup may be determined based on the one or more metrics responsive to files and/or directories of the source file system volume being stored on a destination storage device.

Techniques for providing incremental backup progress indications

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.

Techniques for performing incremental data backups

The embodiments set forth a technique for restoring a computing device to an operable state when a software update renders the computing device inoperable. According to some embodiments, a snapshot of a file system volume is automatically generated prior to executing the software update. When an issue is detected with the software update&#x2014;e.g., the computing device freezes, the computing device cannot boot into an operable mode, etc.&#x2014;the computing device can (1) automatically enter into a restoration mode, and (2) restore the file system volume to its previous state in accordance with the snapshot. In this manner, the issues caused by the software update are entirely mitigated, and the computing device can transition back into an operable state.

Software update rollbacks using file system volume snapshots

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for storing data are disclosed. In some implementations, visual representations of files are generated for presentation in a backup user interface. The visual representations are generated from sparse file system metadata stored on the computing device, thus allowing faster navigating of the backup user interface. During a restore operation, the metadata can be used to retrieve the items from their physical storage locations. In some implementations, when the storage capacity of a backup storage device exceeds a threshold, the data for the N oldest backups are replaced with sparse file system metadata, which can be used to generate visual representations for presentation in the backup user interface.

Backup user interface

Provided is a method for mitigating the effects of an application which crashes as the result of supplemental code (e.g., plug-in), particularly a plug-in from a source other than the source of the operating system of the device or the source of the application that crashes. The method includes executing the application. As the application is running, it may be monitored to determine if normal execution of instructions ceases. When that occurs, the system will make a determination if code from a supplemental code module was the cause of the crash, and will make an evaluation if that supplemental code module is from a source other than the source(s) of the operating system and application in question. In some implementations, remedial steps may be provided, such as providing information on subsequent executions of the application.

System and method for mitigating repeated crashes of an application resulting from supplemental code

Systems and methods are provided for storing and restoring digital data. In some implementations, a method is provided. The method includes detecting a remote storage device, prompting the user to use the detected remote storage device for backup operations, receiving a user input to use the detected remote storage device for backup operations, and automatically configuring backup operations using the remote storage device. Other embodiments of this aspect include corresponding systems, apparatus, computer program products, and computer readable media.

System setup for electronic backup

A system, method, and computer program for analyzing code execution and software performance characteristics are disclosed. Samples of code during run-time or from crash logs can be displayed as both a top-down tree of calls from a particular function and a bottom-up tree of calls to the particular function. Data mining techniques, including filtering and focusing, remove code that is not of interest and display code that is more relevant to performance analysis. In particular, functions contained in libraries such as system libraries can be stripped from view. The cost associated with an excluded function can be propagated to a calling function, in either the top-down or bottom-up tree.

Growing community of inventors

Bahama, NC, United States of America

Christopher A Wolf