Lines Matching full:restore
13 <li><a href="#restore">Forcing a Restore Operation</a></li>
29 and restore operations so that you don't need to repeatedly wipe data or take similar
67 <h2 id="restore">Forcing a Restore Operation</h2>
69 <p>Unlike backup operations, which are batched together and run on an occasional basis, restore
70 operations execute immediately. The Backup Manager currently provides two kinds of restore
74 perform. The second kind of restore operation restores
77 invoke this second restore operation with the {@link
83 <p>While testing your application, you can immediately invoke the restore operation (bypassing the
85 for your application by using the <code>bmgr restore</code> command:
87 <pre class="no-pretty-print">adb shell bmgr restore <em><package></em></pre>
90 participating in the backup/restore mechanism, which you would like to restore. The Backup
91 Manager will immediately instantiate the application's backup agent and invoke it for restore. This
136 data will be saved from the device, and no restore operations will be possible, unless the Backup
147 <p>A "backup transport" is the code module responsible for moving backup and restore data
167 command. From this point forward, backup and restore operations will be directed through the
174 <h2 id="restoresets">Viewing Restore Sets</h2>
177 as a group that is collectively called a "restore set," because each data set is
178 most often manipulated during a restore operation. When a device is provisioned for the first
179 time, a new restore set is established. You can get a listing of all the restore sets available to
184 <p>The output is a listing of available restore sets, one per line. The first item on each line is
185 a token (a hexadecimal value that identifies the restore set to the transport). Following
186 the token is a string that briefly identifies the restore set.
187 Only the token is used within the backup and restore mechanism.
