I need to retask (fdisk) a machine here, but it still has some crunching to do. I have another machine with it\'s own work units that is a physical duplicate of the first (same make/model, etc). Is it possible to merge the work units from machine A with that of Machine B? I can\'t wait for either machine to finish the work units it has before this retasking takes place.

Computers are Dell Poweredge 2600\'s running Win2k3 server (same number cpu\'s, same raid config, same amount of ram, etc..)

---

No, it\'s not possible to merge BOINC data/programs from 2 computers into 1.
Your best bet is to copy the entire BOINC folder onto a dvd from the computer that\'s to be fdisked, and then copy it back after.

One problem with this is the folder/file attributes, which will end up as Read Only on the dvd. You can zip the folder before the copy, or change all of the attributes to Read/Write after copying back.

---

Backups: Here

No, it\'s not possible to merge BOINC data/programs from 2 computers into 1.
Your best bet is to copy the entire BOINC folder onto a dvd from the computer that\'s to be fdisked, and then copy it back after.

One problem with this is the folder/file attributes, which will end up as Read Only on the dvd. You can zip the folder before the copy, or change all of the attributes to Read/Write after copying back.

Thanks for the quick reply. I just hate to lose so much work (combined cpu time on 2 threads = 8021 with 4086 til completion.

I won\'t be able to copy it back after, machine will become part of production systems...can\'t load boinc there or I\'d break my own security policies.

:(

---

In that case, nail the dvd to the wall so that you don\'t lose it, and wait until the models on the other computer are finished. Then copy the lot to that computer. (And reload BOINC after the copy back, to fix the registry!)

Right now, set all projects on both computers to No new tasks so that you don\'t end up getting more work units accidently.

If you know what you\'re doing it is actually possible to merge work from one computer onto another, but there\'s lots of potential to create a disaster. By far the easiest option is to do a zipped backup of the BOINC directory on the system you\'re decommissioning as Les suggested, set the other system to fetch no new work and then replace the BOINC directory with the backup when all of the tasks have been completed.

Edit: SNAP!

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

If you know what you\'re doing it is actually possible to merge work from one computer onto another, but there\'s lots of potential to create a disaster. By far the easiest option is to do a zipped backup of the BOINC directory on the system you\'re decommissioning as Les suggested, set the other system to fetch no new work and then replace the BOINC directory with the backup when all of the tasks have been completed.

Edit: SNAP!

No new tasks implemented! I\'ve done the backup/restore bit before, so I\'ve experience with that recovery method. By \'knowing what I\'m doing\' I expect you mean xml file expertise? :(

Sorry, while I can build you a fully integrated network out of whatever and keep it productive, but I haven\'t coded since the release of \'C\'. Turns out I\'m not exactly xml compliant. Cut/Paste I can do, as well as follow complex instructions....if you have any, send \'em on. I\'ll backup the \'B\' machine before I begin creating disaster. :)

---

You just have to make sure that the boinc folder package from the computer you\'re decommissioning doesn\'t remain in storage ie without crunching & trickling for more than the 6-week time limit. Beyond that limit the server will assume the tasks have been abandoned and may reissue them to another cruncher.

---

Cpdn news