MaxExchange Remote Backup Files

>Is there any way of forcing the MaxExchange remote to request that all
>packets/data has been received/verified from the server and purge these
>files?

No, because the master (network) address book and the various synchronized remotes are separate databases. The users can either synchronize their remote copies periodically, or get a complete refresh before heading out on a road trip. It's their choice....

Hi Gord,

What is the best practice to recover the data from the local Maxexchange DB that has not been synchronised when you need to send a refresh cause the synchronisation failed?

Regards,

>What is the best practice to recover the data from the local
>Maxexchange DB that has not been synchronised when you need to send a
>refresh cause the synchronisation failed?

Reconciling replicated databases after a synchronization failure can get messy. The best thing to do in a case like that would be to seek expert advice on the particular situation, either from a knowledgeable Maximizer Business Partner or from Maximizer Software itself.

I don't think you get what I mean.

The remotes synchronize every hour, so the remote DB's are constantly updated, but they only occasionally log-on to the remote DB.

Because of this, the 'Back-up' files of the data packets remain until they log-on to the remote DB and the next they synchronize, the packets are gone.

Is there any way of forcing MaxExchange to check that the packets were received correctly so the 'Back-up' files can be deleted?

I'm talking about 'Backup' packets and NOT 'Trans' packets.

>The remotes synchronize every hour, so the remote DB's are constantly
>updated, but they only occasionally log-on to the remote DB.
>
>Because of this, the 'Back-up' files of the data packets remain until
>they log-on to the remote DB and the next they synchronize, the packets
>are gone.

Logging into the remote copy of the database does not affect the disposition of the backup packets. Processing packets (i.e., activating MaxExchange ) is what matters. The backup packets remain until MaxExchange at that end of the connection (server or remote) has received confirmation from MaxExchange at the other end of the connection (remote or server) that those packets have been received and processed successfully.

Your users can process packets and sync their remote copies without having to log into the remote database. Just put a shortcut to MaxExchange Remote on their desktop and get them to run it periodically (say, every morning). That should prevent the backup packets from piling up.

>Logging into the remote copy of the database does
>not affect the disposition of the backup packets.

Correction: I should have said that it "... *should* not affect the disposition of the backup packets". I'm pretty sure that the more recent versions will generate an acknowledgement packet even if there have been no other changes to the database, but earlier versions might have required some other activity in the address book before the acknowledgement was sent.

Sorry, but that's not how this one works!

The 'back-up' packets only get deleted after the remote has logged-on to his remote database and then does a 'Process Data Packets'.

They to a sync when they log-on to there computer and then every hour. The 'trans' packets get downloaded and deleted when complete, but the 'back-up' packets remain.

We are working on Maximizer Enterprise 9, with all service releases and hot fixes.

Weird. You should take this up with your Business Partner or Maximizer Support.

Does any one else have this problem or is it just me?

.. or shall I just add it to the list of things that Maximizer says it does, but doesn't!