lib: Splitting up configfile.cc to contain Unix and Windows support in separate sourc...
[barry.git] / doc / www / migrate.php
blobc7dc1199164eae801cf127ced02fb5ce215bd210
1 <? include ("barry.inc"); ?>
3 <? createHeader("Migrating Device Data"); ?>
5 <p>
6 <center>
7 <? createImageEx("desktop-migrate.png", 'width="480" height="152" border="1" alt="Barry Desktop migrate dialog"'); ?>
8 </center>
10 <p>The Migrate dialog provides an easy method of backing up the device's
11 databases, and restoring them to another device.
13 <p>It currently only supports the database data, and does not migrate any
14 of the Java applications that might be on the existing device.
16 <p>There are three main combo boxes: the source device, the destination
17 device, and the write mode. If both devices are plugged in at the
18 same time, it is possible to select them both at the beginning, but
19 if you only have one USB cable, let it prompt you for the new device.
21 <p>The available write modes are described below:
23 <p>
24 <ul>
25 <li> <b>Erase all, then restore</b> - (default) Erases all existing
26 data for each database restored before uploading records.</li>
27 <li> <b>Add new, and overwrite existing</b> - Only deletes existing
28 records if there is a conflict in the record ID, and adds
29 all other records.</li>
30 <li> <b>Add new, don't overwrite existing</b> - Only adds records,
31 never deletes or overwrites. Will skip uploading records
32 where the IDs already exist. This may mean that not all the
33 data from the old device will make it to the new one.</li>
34 <li> <b>Add every record as a new entry</b> - Deletes nothing, and
35 adds everything new. This may cause duplicates, depending
36 on the data in both devices.</li>
37 </ul>
39 <p>Use the default write mode if you are unsure which option to use.
42 <? createSubHeader("Internal Details"); ?>
44 <p>The Migrate dialog will basically perform a full backup of the source
45 device, and will create a new backup tarball in the usual location, with
46 the label "migrate".