Lines Matching defs:backup

17 package android.app.backup;
21 import android.app.backup.IBackupManager;
53 * application and Android's data backup infrastructure. An application that wishes
54 * to participate in the backup and restore mechanism will declare a subclass of
55 * {@link android.app.backup.BackupAgent}, implement the
58 * and provide the name of its backup agent class in its {@code AndroidManifest.xml} file via
66 * <a href="{@docRoot}guide/topics/data/backup.html">Data Backup</a> developer guide.</p></div>
72 * {@link android.app.backup.BackupManager#dataChanged() BackupManager.dataChanged()} method.
74 * to update its backup image. The Backup Manager, in turn, schedules a
75 * backup pass to be performed at an opportune time.
80 * begins an immediate restore pass to deliver the backup data as part of the installation
83 * When a backup or restore pass is run, the application's process is launched
84 * (if not already running), the manifest-declared backup agent class (in the {@code
87 * agent instance to run the actual backup or restore logic. At this point the
93 * A backup data set consists of one or more "entities," flattened binary data
103 * {@link android.app.backup.BackupAgentHelper}. That class is particularly
105 * backup and restore.
107 * @see android.app.backup.BackupManager
108 * @see android.app.backup.BackupAgentHelper
109 * @see android.app.backup.BackupDataInput
110 * @see android.app.backup.BackupDataOutput
170 * to do one-time initialization before the actual backup or restore operation
179 * sort of shutdown process after backup or restore is completed.
188 * time it performed a backup operation. The state data recorded during the
189 * last backup pass is provided in the <code>oldState</code> file
191 * is available and the application should perform a full backup. In both
192 * cases, a representation of the final backup state after this pass should
196 * Each entity written to the {@link android.app.backup.BackupDataOutput}
198 * over the current backup transport and stored in the remote data set under
204 * last backup state provided by the application. May be
206 * provided and the application should perform a full backup.
208 * file descriptor pointing to the backup data destination.
209 * Typically the application will use backup helper classes to
212 * empty file. The application should record the final backup
220 * The application is being restored from backup and should replace any
221 * existing data with the contents of the backup. The backup data is
246 * empty file. The application should record the final backup
248 * When a full-backup dataset is being restored, this will be <code>null</code>.
255 * points to the backup destination, and the app has the opportunity to choose which
256 * files are to be stored. To commit a file as part of the backup, call the
258 * data is written to the output, the agent returns from this method and the backup
279 * @param data A structured wrapper pointing to the backup destination.
303 + " Aborting full backup.", e);
411 * Write an entire file as part of a full-backup operation. The file's contents
412 * will be delivered to the backup destination along with the metadata necessary
451 // may or may not have external files access to attempt backup/restore there
511 * omitted from the backup process.
795 // Ensure that any SharedPreferences writes have landed after the backup,
870 Log.e(TAG, "Unable to finalize backup stream!");