-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steve M. Sawczyn, [SMS] wrote:

SMS> OK, if I'm understanding this correctly, the data files need to be
SMS> generated on each machine each time the synchronization is to take
SMS> place?

Oh yes. Let me put it another way. :)

Machine A:

        Hey B, I need everything that you have so we're up to date with
        each other.

Machine B:

        Well, I need to see first what you have so that I know what to
        send you. I don't see the point in sending you everything.

        Enter the first step. Creating the snapshot of the target
        system.

Machine A:

        OK. There you go. Now you can see what I have.


Machine B:

        OK. I just sent you a file with only the stuff you don't have.

        Machine B generated the second file .. synchronization data
        file.

Machine A:

        Thanks. I'm now updated.

        3rd step completed.

Sorry for the funny metaphor, but when you have young kids like I have,
everything can potentially talk and develops a personality.

Anyway, from that demonstration, it's clear that each step has to be
repeated each time a synchronisation is to be done.

SMS> For example, if I'm planning to synchronize daily, would I need to
SMS> generate the map data files daily, or could I use the same map file
SMS> over and over?

If you don't provide the source system with a current snapshot of the
target system, then the source system will not get an accurate picture
of what's *currently* on the target system. Mail would therefore get
duplicated by the synchronisation process.

AM>> Sounds like it would be better to simply backup the notebook's
AM>> installation and then restore it to the desktop's installation.

SMS> Are you suggesting that this might be the way to go initially and
SMS> then resourt to synchronization,

Yes. Since the desktop has nothing on it, you may as well just create a
complete backup of the laptops installation and then restore it to the
desktop.

After that, do synchronisations.

- --
 -= allie_M =- | List Moderator
_

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.0.2

iQA/AwUBPyyR7lfJ62ArBxfiEQLXmwCfWYeM6kvWFhwEfX0ZzqCV2LVQdW8AoM6G
V7o7ezN+namkNeGTBrThfFaZ
=U+0J
-----END PGP SIGNATURE-----


________________________________________________
Current version is 1.62r | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to