Everend Posted September 5, 2015 Share Posted September 5, 2015 I've been using Crashplan for years from two computers. Last night I converted one of the computers to unRAID! - It was really simple setup, thanks for making it painless. The computer that became unRAID had 1.5TB of data on it, backed up through Crashplan. The other computer has 3.5TB that I've just started transferring to unRAID. Once all the data has been copied to unRAID I'll install crashplan to keep it backed up. I'm trying to figure out the correct procedure for doing this without needing to upload 5TB since CP already has it all. I think the answer is to adopt the old computer (1.5TB) and then to adopt the other computer (3.5TB) both by the new unRAID system. Any thoughts, suggestions, advise? thanks Everend Link to comment
Leifgg Posted September 5, 2015 Share Posted September 5, 2015 I've been using Crashplan for years from two computers. Last night I converted one of the computers to unRAID! - It was really simple setup, thanks for making it painless. The computer that became unRAID had 1.5TB of data on it, backed up through Crashplan. The other computer has 3.5TB that I've just started transferring to unRAID. Once all the data has been copied to unRAID I'll install crashplan to keep it backed up. I'm trying to figure out the correct procedure for doing this without needing to upload 5TB since CP already has it all. I think the answer is to adopt the old computer (1.5TB) and then to adopt the other computer (3.5TB) both by the new unRAID system. Any thoughts, suggestions, advise? thanks Everend Done this in the past but don’t remember all details Suggest checking the CrashPlan pages here: http://support.code42.com/CrashPlan/Latest/Configuring/Replacing_Your_Device Link to comment
Everend Posted September 5, 2015 Author Share Posted September 5, 2015 yea, that page and http://support.code42.com/CrashPlan/Latest/Configuring/Replacing_A_Device_With_A_Different_Operating_System_Or_File_System seem to be the most relevant. The main thing I don't know yet is if it will let the new unRAID computer adopt both of the others without needing to upload it all. I see this note on the page you linked that makes me question it. "Information On Your New Computer - ?Any information backed up from your new computer before adopting must be backed up again after adoption. Before adopting the previous computer, make sure your new computer has all the information you need." Link to comment
Leifgg Posted September 5, 2015 Share Posted September 5, 2015 yea, that page and http://support.code42.com/CrashPlan/Latest/Configuring/Replacing_A_Device_With_A_Different_Operating_System_Or_File_System seem to be the most relevant. The main thing I don't know yet is if it will let the new unRAID computer adopt both of the others without needing to upload it all. I see this note on the page you linked that makes me question it. "Information On Your New Computer - ?Any information backed up from your new computer before adopting must be backed up again after adoption. Before adopting the previous computer, make sure your new computer has all the information you need." Agree, that looks scary to me as well. Unless somebody else responds you might contact CrashPlan support. Even if the unRAID configuration is unsupported they might be able to give advice to this type of questions. I have used them in the past and they was very helpful then. Link to comment
Everend Posted September 5, 2015 Author Share Posted September 5, 2015 thanks. I asked there too, so far no response. Link to comment
Everend Posted September 9, 2015 Author Share Posted September 9, 2015 I asked Crashplan Support... I have crashplan protecting two Win7/10 computers, one has 1.5TB data the other 3.5TB data. The 1.5TB machine is being converting to unRAID and I'll install crashplan to protect it. I'll also be moving the 3.5TB data (and HDDs) to the unRAID machine. I'd like to do this without having to upload the data again or loose crashplan backup history. I believe the path is to adopt the 1.5TB backup (using new OS procedure) then once that's complete, adopt the 3.5TB machine (using the same procedure). Will this work, is this the correct way of doing it? Any advise? Here is what Crashplan support said Thank you for contacting Code42 Support. Unfortunately, the adoption process does not work as you described. Each installation of CrashPlan is unique, with it's own unique ID and backup archive. The adoption process doesn't fold that archive into the computer that adopted it. Instead, the ID for the computer is changed to the computer being adopted, and the backup archive is carried over because it's attached to the ID. So unfortunately, you will have to re-upload data. But, you have a choice of what gets re-uploaded in a manner of speaking. I'd suggest first adopting the 3.5 TB machine onto the UnRAID, and then moving the 1.5 TB of data to reside physically on that computer. This will allow you to retain the lion's share of data, while only having to re-upload that 1.5 TB. So in effect, this is what the steps would be: [*]Manually copy 1.5 TB of data from the computer being converted to UnRAID to removable storage. [*]Format/setup ( depending on what steps you need) the UnRAID. [*]Install CrashPlan, login as existing user, then restore the 3.5 TB of data ( if it does not physically exist on the computer already). [*]Adopt ( we have instructions on adoption here ) [*]Manually place the 1.5 TB of data on the UnRaid. [*]Change the file selection to include the new locations of all files on the computer. Do not remove the " old" or "missing" parts of the file selection. [*]Let CrashPlan run. What the program will do is de-duplicate existing data in new locations ( i.e. File A used to exist in location A. Now it exists in location B. Update the archive). [*]When CrashPlan next reports 100% completion, you can de-select the old locations of the file selection. Then, going forward, CrashPlan will look for the existing data in it's current and permanent location. Then I asked... Thanks for the detailed response! Is it important to install crashplan and adopt the 3.5tb machine before loading any of the 1.5tb data into the new unRaid server? I've already started the data transfer to the new machine and it hasn't been in the order you outlined. Some of the 1.5tb data is already there and most of the 3.5tb is already there. So once I finish transfering the 3.5tb data do I need to remove any of the 1.5 or any other new data that was not part of the 3.5tb backup before I install and adopt the 3.5tb ID? I think this is a dumb question that of course I don't need to remove the new data, but I would like confirmation because it doesn't follow your answer precisely. Thanks for taking the time to reassure me. Thier response... Is it important to install crashplan and adopt the 3.5tb machine before loading any of the 1.5tb data into the new unRaid server? Not especially. I just took the whole process from the top in the way I'd do it. I mainly opt to restore and then adopt before any other changes so that you can ensure that all of the data in the selection physically exists on the computer. So once I finish transfering the 3.5tb data do I need to remove any of the 1.5 or any other new data that was not part of the 3.5tb backup before I install and adopt the 3.5tb ID? No. You'll only want to remove duplicate files. CrashPlan would detect any duplicates and skip over them anyway. Plus it gives you a change to do some digital housekeeping ( which I'm always a fan of). Basically, moving the data over to the computer outside of CrashPlan gives you a chance to remove defunct files and folders which would allow CrashPlan going forward to perform more efficiently. Once the files on the computer reflect how you want them stored, you can adopt the 3.5 Tb archive. Immediately after the adoption, you'll want to change the file selection to include any new locations of data. Do not remove the old selection. Then let CrashPlan run until it reports 100% completion. Once that happens, you can de-select the old parts of the file selection without losing data. Link to comment
Leifgg Posted September 9, 2015 Share Posted September 9, 2015 I asked Crashplan Support... I have crashplan protecting two Win7/10 computers, one has 1.5TB data the other 3.5TB data. The 1.5TB machine is being converting to unRAID and I'll install crashplan to protect it. I'll also be moving the 3.5TB data (and HDDs) to the unRAID machine. I'd like to do this without having to upload the data again or loose crashplan backup history. I believe the path is to adopt the 1.5TB backup (using new OS procedure) then once that's complete, adopt the 3.5TB machine (using the same procedure). Will this work, is this the correct way of doing it? Any advise? Here is what Crashplan support said Thank you for contacting Code42 Support. Unfortunately, the adoption process does not work as you described. Each installation of CrashPlan is unique, with it's own unique ID and backup archive. The adoption process doesn't fold that archive into the computer that adopted it. Instead, the ID for the computer is changed to the computer being adopted, and the backup archive is carried over because it's attached to the ID. So unfortunately, you will have to re-upload data. But, you have a choice of what gets re-uploaded in a manner of speaking. I'd suggest first adopting the 3.5 TB machine onto the UnRAID, and then moving the 1.5 TB of data to reside physically on that computer. This will allow you to retain the lion's share of data, while only having to re-upload that 1.5 TB. So in effect, this is what the steps would be: [*]Manually copy 1.5 TB of data from the computer being converted to UnRAID to removable storage. [*]Format/setup ( depending on what steps you need) the UnRAID. [*]Install CrashPlan, login as existing user, then restore the 3.5 TB of data ( if it does not physically exist on the computer already). [*]Adopt ( we have instructions on adoption here ) [*]Manually place the 1.5 TB of data on the UnRaid. [*]Change the file selection to include the new locations of all files on the computer. Do not remove the " old" or "missing" parts of the file selection. [*]Let CrashPlan run. What the program will do is de-duplicate existing data in new locations ( i.e. File A used to exist in location A. Now it exists in location B. Update the archive). [*]When CrashPlan next reports 100% completion, you can de-select the old locations of the file selection. Then, going forward, CrashPlan will look for the existing data in it's current and permanent location. Then I asked... Thanks for the detailed response! Is it important to install crashplan and adopt the 3.5tb machine before loading any of the 1.5tb data into the new unRaid server? I've already started the data transfer to the new machine and it hasn't been in the order you outlined. Some of the 1.5tb data is already there and most of the 3.5tb is already there. So once I finish transfering the 3.5tb data do I need to remove any of the 1.5 or any other new data that was not part of the 3.5tb backup before I install and adopt the 3.5tb ID? I think this is a dumb question that of course I don't need to remove the new data, but I would like confirmation because it doesn't follow your answer precisely. Thanks for taking the time to reassure me. Thier response... Is it important to install crashplan and adopt the 3.5tb machine before loading any of the 1.5tb data into the new unRaid server? Not especially. I just took the whole process from the top in the way I'd do it. I mainly opt to restore and then adopt before any other changes so that you can ensure that all of the data in the selection physically exists on the computer. So once I finish transfering the 3.5tb data do I need to remove any of the 1.5 or any other new data that was not part of the 3.5tb backup before I install and adopt the 3.5tb ID? No. You'll only want to remove duplicate files. CrashPlan would detect any duplicates and skip over them anyway. Plus it gives you a change to do some digital housekeeping ( which I'm always a fan of). Basically, moving the data over to the computer outside of CrashPlan gives you a chance to remove defunct files and folders which would allow CrashPlan going forward to perform more efficiently. Once the files on the computer reflect how you want them stored, you can adopt the 3.5 Tb archive. Immediately after the adoption, you'll want to change the file selection to include any new locations of data. Do not remove the old selection. Then let CrashPlan run until it reports 100% completion. Once that happens, you can de-select the old parts of the file selection without losing data. Thanks for sharing! This is a lot of useful information. Link to comment
RussellinSacto Posted September 9, 2015 Share Posted September 9, 2015 Any chance you know who that Tech was at CrashPlan? I've never gotten an UnRaid aware technician before! Russell Link to comment
Everend Posted October 3, 2015 Author Share Posted October 3, 2015 Devin T (Code42 Helpdesk) Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.