Basically, I am keen to provide researchers with completed tasks. Consequently when six of eight tasks recently crashed I used a three day old backup, restored the whole Boinc directory and restarted crunching those tasks.

Erroneously, I did not update the <rpc_seqno> for the projects I restored in client_state.xml to a figure greater than the "Number of times client has contacted server" shown in the computer details for the same machine.

As a result, the server then created a new cross-project ID. A day later I then merged host-ids to the newest host-id.

Since then I have left Boinc to crunch and it has surpassed the task progress percentage at which it had earlier crashed.

However I am now concerned that the server does not seem to log or accept the trickles these tasks are generating. Uploads now take 1-8 seconds where previously they took 8-15 minutes....

So the Boinc Client says it is progressing but the Boinc Server does not seem to be registering any trickles.

Does anyone have a suggestion on how to cure this immediate problem and avoid it happening in future task restores?

Thanks

I think I spoke too soon...the trickles have now started to upload at their normal speed...

That's encouraging.

The BOINC server side code ignores duplicate trickles and zips, so you won't get more until the model reaches a new model time.

Yes that was what I was expecting but it took much longer than I anticipated...

morale of the story = take more frequent backups! :)

b.t.w. I was looking at http://climateapps2.oerc.ox.ac.uk/cpdnboinc/forum_thread.php?id=5064#25408 and found it interesting to see some old names and some long explanations...

Les, you certainly put a lot of time into CPDN - great effort, thanks for everything you do.