Not a solution for everyone, but those who know how to move distinct models between different BOINC installations might like this idea :

If a CPDN task detects an executable file \"cpdn_backup.sh\" / \"cpdn_backup.cmd\" in the BOINC root directory, after each model year ...

1. close all files open for write/update

2. call this script with the slot number, the model name and the model year as parameters

3. wait for the script to finish (don\'t send it to background)

4. reopen/reposition the files that you have closed in 1.

5. continue with the next model year

This would allow to plug in individual backup solutions that work without any user interaction.

Of course that backup script needs to include some XML files from the BOINC base directory too, but that\'s a known constant on the host so it doesn\'t need to be a parameter.

As CPDN is the most demanding BOINC project, it\'s sure OK for a full BOINC backup as well, especially when CPDN has the host for its own.