| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: move jobs to a different computer system |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
Redearl
Cruncher Joined: Nov 6, 2010 Post Count: 1 Status: Offline Project Badges: 
|
Got a new computer, and i need to move my current jobs/tasks from the old one to the new one.
I looked thru the forum and did not find directions on how to do this. |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Got a new computer, and i need to move my current jobs/tasks from the old one to the new one. I looked thru the forum and did not find directions on how to do this. Hi and welcome to the forums, Congratulations on your new cruncher. The reason you could not find a topic is, because it cannot be done [  We could make a help topic for that of course]. Tasks assigned to a computer have to be returned by the same computer. Best is to do following on old cruncher:1) Set old client not the fetch more new work (Select WCG in project tab and hit *no new tasks* button) 2) Abort all tasks that have not started yet 3) Finish all running jobs. 4) Select WCG in the project tab and hit Update to force result reporting. You need to do a clean install on your new cruncher. WCG will stop showing your old computer in the active device list in about 14 days and your new will start to show in the device manager as soon as a first work unit has been fetched or crunched and reported [sometimes this is a bit slow to happen]. [Edit 1 times, last edit by Former Member at Sep 20, 2012 7:08:14 AM] |
||
|
|
a_mobile_humanist
Cruncher Joined: May 20, 2011 Post Count: 34 Status: Offline Project Badges: 
|
[EDIT: No need to repeat SekeRob above. Curse my slow typing.
----------------------------------------  ][Edit 1 times, last edit by a_mobile_humanist at Sep 20, 2012 7:12:41 AM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
Got a new computer, and i need to move my current jobs/tasks from the old one to the new one. I looked thru the forum and did not find directions on how to do this. Moving tasks from an old computer to a new computer is normally easy, except if a project uses Homogeneous Redundancy (HR) like atleast some of WCG's projects uses (don't remember if all uses HR). So, if you're only running WCG, the easiest is to follow Sekerob's suggestion and just delete the old install. For multi-project BOINC-users, and especially anyone with one or more long-running CPDN-units that can have 1+ month left to do, follow these steps: 0: Both computers must run the same OS-type, meaning can example upgrade from WinXP to Win7 or Linux-something to Linux-somethingelse, but you can't upgrade from example Win to Linux or Mac. 1: You can't switch from 64-bit to 32-bit OS, but switching from 32-bit to 64-bit will work. Since it's a new computer, it should be running 64-bit OS... 2: In BOINC set "no new work" on all projects. Report any finished work, and afterwards disable network & crunching. 3: Shutdown and afterwards uninstall BOINC. (to make sure no problems with boinctray still running). 4: Copy your BOINC data-directory (including sub-directories) from your old computer to your new computer. If switches from example XP to win7, it's a good chance you'll need to choose another location of the data-directory. 5: On the new computer, install BOINC, making sure to choose the correct location of BOINC data-directory. 6: Start BOINC, try resuming crunching, and if everything seems to work enable network again. BTW, some upgrades will also work for WCG-projects even if they're using HR. Example upgrading from one win7-64-system running i7-2600K to another win7-64-system running i7-2700K should work, since appart for cpu-speed it's the same cpu & OS. It's possible any partially-crunched tasks will give validation-errors, but the rest should not.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
ALL sciences, Ingleside. Like for like [Windows to Windows, Linux to Linux], with exception for HPF2, which has a cross-platform quorum, but assigned to a device ID [say 1234567] requires return by same device ID [1234567] or you get the approximate message of "Task unknown for this device". If you manage to clone that and make the WCG servers believe the new is the same as the old [hardware], then feel free to try your luck ;>)
|
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Are you going to be using the same OS on your new computer that you used on your old one?
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
ALL sciences, Ingleside. Like for like [Windows to Windows, Linux to Linux] This type of HR isn't an issue, since you can't use linux-applications under windows and so on anyway... But HR often means Amd and Intel is in separate HR-classes, and it's also possible for finer divitions like example Amd-Bulldozer needed a separate HR-class for some of WCG's projects to not be marked invalid. It's even possible to have HR between example XP & win7, but not sure if WCG is using this. with exception for HPF2, which has a cross-platform quorum, but assigned to a device ID [say 1234567] requires return by same device ID [1234567] or you get the approximate message of "Task unknown for this device". If you manage to clone that and make the WCG servers believe the new is the same as the old [hardware], then feel free to try your luck ;>) Since you're copying the full BOINC data-directory, you'll keep the device-ID so this part isn't a problem. The hardware points back to HR again, and depending how different the old and new system is this can give validation-errors. But, for "fairly similar" systems like example i7-2600K and i7-2700K it would be really strange if these is put in different HR-classes. Anyone overclocking their cpu can easily get an i7-2600K to run at the same speed as i7-2700K. For modern cpu's there's also the turbo-frequency automatically increasing speed if only 1 or 2 of the cores is being used. As for "try your luck", well, SN2S continued validating after swapping data-directories between i7-920/Win2008R2 & i7-2700K/Win7 atleast... "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." [Edit 1 times, last edit by Ingleside at Sep 21, 2012 10:01:38 AM] |
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1460 Status: Offline Project Badges: 
|
i would move these jobs only if they are "rare", e.g. BETA or DDDT2 tasks
----------------------------------------all other can be aborted and they will be resent to another computers |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
ALL sciences, Ingleside. Like for like [Windows to Windows, Linux to Linux] This type of HR isn't an issue, since you can't use linux-applications under windows and so on anyway... But HR often means Amd and Intel is in separate HR-classes, and it's also possible for finer divitions like example Amd-Bulldozer needed a separate HR-class for some of WCG's projects to not be marked invalid. It's even possible to have HR between example XP & win7, but not sure if WCG is using this. with exception for HPF2, which has a cross-platform quorum, but assigned to a device ID [say 1234567] requires return by same device ID [1234567] or you get the approximate message of "Task unknown for this device". If you manage to clone that and make the WCG servers believe the new is the same as the old [hardware], then feel free to try your luck ;>) Since you're copying the full BOINC data-directory, you'll keep the device-ID so this part isn't a problem. The hardware points back to HR again, and depending how different the old and new system is this can give validation-errors. But, for "fairly similar" systems like example i7-2600K and i7-2700K it would be really strange if these is put in different HR-classes. Anyone overclocking their cpu can easily get an i7-2600K to run at the same speed as i7-2700K. For modern cpu's there's also the turbo-frequency automatically increasing speed if only 1 or 2 of the cores is being used. As for "try your luck", well, SN2S continued validating after swapping data-directories between i7-920/Win2008R2 & i7-2700K/Win7 atleast... Wish you all the luck fooling the WCG servers into accepting that the combo of OS [family], Hardware etc [5 metrics], are seen as the same device beyond the first connection. I've done it. Woosh no later than 2nd connect. |
||
|
|
BSD
Senior Cruncher Joined: Apr 27, 2011 Post Count: 224 Status: Offline |
I've had mixed results with this. I've done it four times, twice on Windows and twice on a Linux device. In each case I reinstalled on the same device with the same OS, same BOINC version, and the same hostname.
1 out of 4, magically kept the same device ID and only showed up once in my device list. The others showed up with a different device ID with the same hostname on the device list. WU's that hadn't finished, error'd out when resumed under the new assumed identity. New WU's processed normally. When reinstalling the OS, I normally just let all the WU finish and not grab anymore, detach and do a fresh BOINC install once I get the new OS up and running. That's why WCG thinks I have 108 devices when in fact I only have 9 devices. I'm a computer hobbyist, I like reinstalling OS's to keep me busy. |
||
|
|
|