Lines Matching full:application
30 intrusive steps in order to test your application's backup agent. These commands are
33 <p>For information about adding support for backup in your application, read <a
35 your application using {@code bmgr}.</p>
40 <p>Normally, your application must notify the Backup Manager when its data has changed, via {@link
50 <p><code><em><package></em></code> is the formal package name of the application you wish to
52 backup. When you execute this backup command, your application's backup agent will be invoked to
75 a single application to its "active" data set; that is, the application will abandon its current
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:
89 <p><code><em><package></em></code> is the formal Java-style package name of the application
91 Manager will immediately instantiate the application's backup agent and invoke it for restore. This
92 will happen even if your application is not currently running.
102 <p>The data for a single application can be erased from the active data set on demand. This is
104 or saved state information. You can wipe an application's data with the <code>bmgr wipe</code>
109 <p><code><em><package></em></code> is the formal package name of the application whose data
111 erase. The next backup operation that the application's agent processes will look as
112 though the application had never backed anything up before.
122 <p>This might be useful if your application's backup agent is never being invoked for backup, to
176 <p>All of the application data that a device has written to its backup transport is tracked
