Lines Matching defs:backup

17 package android.app.backup;
20 import android.app.backup.IBackupManager;
43 * application and Android's data backup infrastructure. An application that wishes
44 * to participate in the backup and restore mechanism will declare a subclass of
45 * {@link android.app.backup.BackupAgent}, implement the
48 * and provide the name of its backup agent class in its {@code AndroidManifest.xml} file via
56 * <a href="{@docRoot}guide/topics/data/backup.html">Data Backup</a> developer guide.</p></div>
62 * {@link android.app.backup.BackupManager#dataChanged() BackupManager.dataChanged()} method.
64 * to update its backup image. The Backup Manager, in turn, schedules a
65 * backup pass to be performed at an opportune time.
70 * begins an immediate restore pass to deliver the backup data as part of the installation
73 * When a backup or restore pass is run, the application's process is launched
74 * (if not already running), the manifest-declared backup agent class (in the {@code
77 * agent instance to run the actual backup or restore logic. At this point the
83 * A backup data set consists of one or more "entities," flattened binary data
93 * {@link android.app.backup.BackupAgentHelper}. That class is particularly
95 * backup and restore.
97 * @see android.app.backup.BackupManager
98 * @see android.app.backup.BackupAgentHelper
99 * @see android.app.backup.BackupDataInput
100 * @see android.app.backup.BackupDataOutput
130 * to do one-time initialization before the actual backup or restore operation
140 * sort of shutdown process after backup or restore is completed.
149 * time it performed a backup operation. The state data recorded during the
150 * last backup pass is provided in the <code>oldState</code> file
152 * is available and the application should perform a full backup. In both
153 * cases, a representation of the final backup state after this pass should
157 * Each entity written to the {@link android.app.backup.BackupDataOutput}
159 * over the current backup transport and stored in the remote data set under
165 * last backup state provided by the application. May be
167 * provided and the application should perform a full backup.
169 * file descriptor pointing to the backup data destination.
170 * Typically the application will use backup helper classes to
173 * empty file. The application should record the final backup
181 * The application is being restored from backup and should replace any
182 * existing data with the contents of the backup. The backup data is
207 * empty file. The application should record the final backup
209 * When a full-backup dataset is being restored, this will be <code>null</code>.
260 * Write an entire file as part of a full-backup operation. The file's contents
261 * will be delivered to the backup destination along with the metadata necessary
334 * omitted from the backup process.
558 Log.e(TAG, "Unable to finalize backup stream!");