climateprediction.net home page
Transferring a Saved Boinc folder to a new computer

Transferring a Saved Boinc folder to a new computer

Questions and Answers : Windows : Transferring a Saved Boinc folder to a new computer
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile old_user91590

Send message
Joined: 7 Aug 05
Posts: 10
Credit: 280,253
RAC: 0
Message 17209 - Posted: 15 Nov 2005, 22:40:31 UTC

Hi,

I did not made a backup, only saved my boinc folder.
I copied it to my new computer because the project was 70% ready.

I installed Boinc over this folder. I tried to run it, but boinc crushed immediately.
The log says unrecoverable error, missing data, and finally that the project is closed.


Is there any way to continue my project on my new computer or accept the fact that I am lost it???


ID: 17209 · Report as offensive     Reply Quote
crandles
Volunteer moderator

Send message
Joined: 16 Oct 04
Posts: 692
Credit: 277,679
RAC: 0
Message 17211 - Posted: 15 Nov 2005, 22:59:03 UTC

Can you copy it again from the old computer?

Also how did you copy it? If it involved a CD, you might need to reset the files from being read only.
Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.
ID: 17211 · Report as offensive     Reply Quote
Profile old_user91590

Send message
Joined: 7 Aug 05
Posts: 10
Credit: 280,253
RAC: 0
Message 17213 - Posted: 16 Nov 2005, 8:03:13 UTC - in response to Message 17211.  

Can you copy it again from the old computer?

Also how did you copy it? If it involved a CD, you might need to reset the files from being read only.



I am not a rookie in the IT world, but very green at using Boinc. :))

1. I was still running a project a several days ago.
2. Than the new hardware stuff arrived, so I shut down the computer,
3. moved the harddrive to the new computer,
4. renamed my boinc data folder to \"old boinc\"
5. copied all the files I need to a safe location incl folder \"old boinc\"
6. I formatted tha system partition
7. A new OS installed with all the applications needed


here comes the difficulties...
1. First I was told that i have to install boinc and simply copy old folder content into the new boinc installation. When i asked the \"pro\" boinc users about which files have to be copied and which not, they was not sure.

2. A new advice came: Lets create a Boinc data folder, copy my \"old boinc\" folder into this folder and install the new boinc version into this folder.
They said it will overwrite the necessary files and will running normally.
It did not. As i said boinc crashed immediately after running benchmark.

So before i try the first option also I thought it would be better if i ask the \"collegaues\" about what files are need to be copied in this case.

Possible problem sources I identified:
- the HW changed, so the old config files I checked are not contain the right information about my HW.
- I changed from version 4.43 to version 5.26
- I gave a same name to my new computer like the old one





ID: 17213 · Report as offensive     Reply Quote
Profile Keck_Komputers
Avatar

Send message
Joined: 5 Aug 04
Posts: 426
Credit: 2,426,069
RAC: 0
Message 17214 - Posted: 16 Nov 2005, 10:24:55 UTC

Advice #2 is the best course normally. I seem to recall from the other thread that you were having problems with the previous install, that may make it impossible to transfer to a new install. The reason is that everything must be noted in the client_state.xml file so if the problem inculded that file it will always cause problems.

Another thing is that the OS must be (nearly) the same. Two different versions of windows may work, two different versions of *nix may work. Changing from windows to *nix or vice versa will not work.

The problem with transfering individual files is that you have to go and edit client_state.xml to just point to the files you transfer. If you try this route just copy all CPDN files and the CPDN project directory and remove all references to non-CPDN files from client_state.xml. The other files should regenerate themselves. Once you have CPDN working again then copy all the account*.xml files to the new install.

I am afraid you are going to loose your old model though. If it didn\'t work by coping the directory and then installing the new version to that directory it may not be salvagable.
BOINC WIKI

BOINCing since 2002/12/8
ID: 17214 · Report as offensive     Reply Quote
Profile old_user91590

Send message
Joined: 7 Aug 05
Posts: 10
Credit: 280,253
RAC: 0
Message 17220 - Posted: 16 Nov 2005, 17:31:33 UTC - in response to Message 17214.  

Advice #2 is the best course normally. I seem to recall from the other thread that you were having problems with the previous install, that may make it impossible to transfer to a new install. The reason is that everything must be noted in the client_state.xml file so if the problem inculded that file it will always cause problems.

Another thing is that the OS must be (nearly) the same. Two different versions of windows may work, two different versions of *nix may work. Changing from windows to *nix or vice versa will not work.

The problem with transfering individual files is that you have to go and edit client_state.xml to just point to the files you transfer. If you try this route just copy all CPDN files and the CPDN project directory and remove all references to non-CPDN files from client_state.xml. The other files should regenerate themselves. Once you have CPDN working again then copy all the account*.xml files to the new install.

I am afraid you are going to loose your old model though. If it didn\'t work by coping the directory and then installing the new version to that directory it may not be salvagable.



OK. Thanks for all of you.

OS is the same, with same patches, it is only a new installation.
I will try manually adjust the client state.xml, if it not works, I will gave up.

Its a shame. I hope they send same WU\'s to more than one people and somebody will complete it.

And I hope if I face this reinstallation challenge next time, (not with a broken client), method #2 will work fine.
ID: 17220 · Report as offensive     Reply Quote
Profile Andrew Hingston
Volunteer moderator

Send message
Joined: 17 Aug 04
Posts: 753
Credit: 9,804,700
RAC: 0
Message 17221 - Posted: 16 Nov 2005, 17:59:37 UTC - in response to Message 17220.  

And I hope if I face this reinstallation challenge next time, (not with a broken client), method #2 will work fine.

Generally it does, and in essence it is the same process (installing to an existing folder) as when upgrading BOINC, which is something that has to be done quite often. Taking a backup first is always wise, but not guaranteed to work, and it is a good idea to backup often and to keep the one before (ie don\'t save over the top).
ID: 17221 · Report as offensive     Reply Quote
Profile old_user91590

Send message
Joined: 7 Aug 05
Posts: 10
Credit: 280,253
RAC: 0
Message 17239 - Posted: 18 Nov 2005, 20:49:14 UTC - in response to Message 17221.  

And I hope if I face this reinstallation challenge next time, (not with a broken client), method #2 will work fine.

Generally it does, and in essence it is the same process (installing to an existing folder) as when upgrading BOINC, which is something that has to be done quite often. Taking a backup first is always wise, but not guaranteed to work, and it is a good idea to backup often and to keep the one before (ie don\'t save over the top).



Good news guys! Thanks for your help it seems method #1 worked.

What I did? (step by step guide)
-1. I went offline and removed boinc
0. After a restart I installed it again. I do not let boinc to run itself.
1. Copied the \"projects\" folder into the new installation from my backup
2. Removed subfolder \"setiathome.berkeley.edu\" (only cpd was left)
3. Backed up client_state.xml (to be sure if I make a mistake under editing)
4. Opened it and removed all sections related to setiathome from it. (be cautious!)
5. Copied these files from backup to the new seti folder:
- account_climateprediction.net.xml
- global_prefs.xml
- master_climateprediction.xml
- sched_reply_climateprediction.net.xml
- sched_request_climateprediction.net.xml
- statistics_climateprediction.net.xml

... than I opened boinc and it is started normally, no error message.
---> It is recognised my climate projects and their status
---> It is recognised the hardware change
---> It is recognised the boinc version change
---> Boinc started a benchmark

When boinc finished the benchmark, I put it in \"always running\" mode.
It is started calculating normally without error messages.

I became more brave so I went on-line and pushed the \"update\" button.
Boinc worked fine.

Now everything seems OK.

To be sure:
(You know Its just because my old client was \"broken\". I dunno why, but after a while it is did not requested new WU\'s for seti anymore)

- I pushed the button \"no new work\"
- i will make a frequent backup
- I will not join to other projects to keep it safe
- I will wait till I will finish my climate WU\'s
- Then I will uninstall boinc and reinstall it and start again my boinc life with a \"clean paper\"


Thanks again to everybody for your help.
I was writing my steps in details, cause I hope i can help on others too.

Good Bye Folks!
Pic







ID: 17239 · Report as offensive     Reply Quote
Profile old_user91590

Send message
Joined: 7 Aug 05
Posts: 10
Credit: 280,253
RAC: 0
Message 17240 - Posted: 18 Nov 2005, 21:29:25 UTC - in response to Message 17239.  


SORRY!

I made some mistakes in my text.

step 0:
After the restart I shut down my internet access again. I do not know it was important or not in this case, but it happened that way.

step 4:
A note: I opened the client_state.xml at the backup folder and edited there. Thats was why I needed a backup of the backup :))

step 5:
Of course if I edited my client_state.xml in the backup folder I have to copy this file also to the new installation along with the others.

step 5 again:
a MAJOR mistake: I do not want anybody to fail so an explanation:

- my boinc folder\'s name is \"seti\"
- So when I said \"I Copied these files from backup to the new seti folder\"
it means
\"I Copied these files from backup to the new BOINC folder\"

sorry guys :))
ID: 17240 · Report as offensive     Reply Quote

Questions and Answers : Windows : Transferring a Saved Boinc folder to a new computer

©2024 climateprediction.net