Lines Matching refs:restore
11 <p><code>bmgr</code> lets you control the backup/restore system on an Android device.
16 <li><a href="#restore">Forcing a Restore Operation</a></li>
32 and restore operations so that you don't need to repeatedly wipe data or take similar
70 <h2 id="restore">Forcing a Restore Operation</h2>
72 <p>Unlike backup operations, which are batched together and run on an occasional basis, restore
73 operations execute immediately. The Backup Manager currently provides two kinds of restore
77 perform. The second kind of restore operation restores
80 invoke this second restore operation with the {@link
86 <p>While testing your application, you can immediately invoke the restore operation (bypassing the
88 for your application by using the <code>bmgr restore</code> command:
90 <pre class="no-pretty-print">adb shell bmgr restore <em><package></em></pre>
93 participating in the backup/restore mechanism, which you would like to restore. The Backup
94 Manager will immediately instantiate the application's backup agent and invoke it for restore. This
139 data will be saved from the device, and no restore operations will be possible, unless the Backup
150 <p>A "backup transport" is the code module responsible for moving backup and restore data
170 command. From this point forward, backup and restore operations will be directed through the
180 as a group that is collectively called a "restore set," because each data set is
181 most often manipulated during a restore operation. When a device is provisioned for the first
182 time, a new restore set is established. You can get a listing of all the restore sets available to
187 <p>The output is a listing of available restore sets, one per line. The first item on each line is
188 a token (a hexadecimal value that identifies the restore set to the transport). Following
189 the token is a string that briefly identifies the restore set.
190 Only the token is used within the backup and restore mechanism.