Leifgg
-
Posts
408 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Leifgg
-
-
6.0 Final, Crashplan GUI re-installed.
Issue persists -> I can RDP into the desktop, the crashplan GUI starts, but it does not find the engine.
Same problem as others, it looks like when an update is found on the Docker page, if you click on upgrade it moves the Crashplan version to 4.2.
If you uninstall the Crashplan Docker and Re-install to 3.7 this wipes out your saved cloud files and starts the backup process from the beginning.
If you restart your server and manually start the Docker it appears to force the update if an update is available.
App.Log in the crashplan docker folder: CPVERSION = 4.2.0 - 1425276000420 (2015-03-02T06:00:00:420+0000) - Build: 61
How do we obtain a 4.2 GUI Mate Docker?
If you uninstall and reinstall you must make sure not losing your GUID for the current installation. It is possible to move installations as well as do reinstallations and at the same time keep your current backup at CrashPlan without losing any data. Make sure to check out the support pages at CrashPlan so that you understand the procedures.
I am sure that the maintainer of this Docker will do an update when time permits.
-
I believe my engine was upgraded also, but the client I think is static at the old version. Only one that can update that is someone that knows how or the docker creator.
I think you are right about that, I didn’t find a way to get the Docker client to update either…
Well, I guess you can always use the Windows client if you are in an urgent need of doing a restore.
-
I was wrong when I previously said that the CrashPlan Docker engine couldn’t be auto updated. Sorry about that! :'(
Did a check in the app.log in the log directory and can confirm 4.2.0 running as mentioned by guygg in the post above. If you stop and start the Docker the version will remain the same but if you force update the Docker it will load 3.7.0 but it will immediately update itself to 4.2.0.
-
The CrashPlan engine Docker will not update from 3.7 to 4.2 automatically, the developer of the Docker would need to update it to pull the new release.
Edit: See correction in Reply #213 below
-
Do you have both the CrashPlan Docker container and the CrashPlan GUI Docker container installed? CrashPlan is a server/client setup where the server runs on unRAID and the client can run on either a desktop PC or on unRAID.
Yes, I have both installed, and I have been using CP without the GUI Docker for a while without difficulties. Just curious if it would be more convenient not to have to use the Windows client to connect to the unRAID engine. (I can connect to the unRAID CP engine from a Windows system as usual.)
Well, it doesn’t really matter I would say, it’s the same Java app. Only thing that I can think of is if you are going to do a restore to your Windows machine rather than to unRAID. Would guess that is best done with the Windows client.
-
I'm probably missing something obvious here, but once the GUI Docker is installed and running, how do I use it?
Thanks!
- TD
Do you have both the CrashPlan Docker container and the CrashPlan GUI Docker container installed? CrashPlan is a server/client setup where the server runs on unRAID and the client can run on either a desktop PC or on unRAID.
-
Hello,
first sorry for my bad englisch.
I need your help. I have installed Crashplan via Docker on my unraid system. It will be shown as running but I can't connect from my normal PC to the crashplan application.
The settings in the file ui.properties where made an the antivirus on the pc where shut off.
Thanks for your help.
Chris
Have a look here at #153 for the settings:
http://lime-technology.com/forum/index.php?topic=33864.msg372747#msg372747
You can also use the CrashPlan GUI that is avaliable as a Docker.
-
You have a challenge in front of you if you would like to backup all your data to CrashPlan! Your main problem will not be your bandwidth (but it will take time for sure) but the way this service works.
The data you backup is encrypted, compressed and reduced by data deduplication. Encryption and compressions doesn’t take much resources but data deduplication do. That’s why you have high CPU load. Data deduplication compares your backup data with all data you previously backed up to CrashPlan. In reality when you start your backup you will have a good upload speed but the more data you have backed up the slower it will be.
I suggest you Google data deduplication and CrashPlan for a day or two(!) and also make sure to check the CrashPlan support pages. This is a hot topic…
You should also be aware that CrashPlan recommends 1 GB memory for each 1 TB of data you have. Even if you add memory you need to reconfigure CrashPlan to use it. The reason for the memory usage is that CrashPlan rescans all your files to make sure that everything gets backed up.
After some re-configuring and de-selections the upload time dropped to 4.4 months. Crashplan never deletes, so here we go for the long haul.
I really can't wait to start building a new box. Seeing the need for more CPU power and RAM with unRaid is usually not in the same sentence. Can still be used as a "lite" box, but can certainly be used as a heavy weight now.
Great! Pls. keep us posted on progress
-
Just a note to your /mnt/user0 question, this is not created by the docker but by unRaid itself.
/mnt/user shows all your shares including the files still in the cache share
/mnt/user0 only has the files/folders that are on the array.
But unRaid created that user0 folder because of the Crashplan docker install? It wasn't there prior.
Nope, has nothing to do with CrashPlan. Would guess it’s created if you install a cash drive.
-
You have a challenge in front of you if you would like to backup all your data to CrashPlan! Your main problem will not be your bandwidth (but it will take time for sure) but the way this service works.
The data you backup is encrypted, compressed and reduced by data deduplication. Encryption and compressions doesn’t take much resources but data deduplication do. That’s why you have high CPU load. Data deduplication compares your backup data with all data you previously backed up to CrashPlan. In reality when you start your backup you will have a good upload speed but the more data you have backed up the slower it will be.
I suggest you Google data deduplication and CrashPlan for a day or two(!) and also make sure to check the CrashPlan support pages. This is a hot topic…
You should also be aware that CrashPlan recommends 1 GB memory for each 1 TB of data you have. Even if you add memory you need to reconfigure CrashPlan to use it. The reason for the memory usage is that CrashPlan rescans all your files to make sure that everything gets backed up.
-
You need to check that it can communicate with the APC UPS Deamon used in unRAID to start with. This was initially developed for APC products but other suppliers are using this protocol as well (fully or partially implemented). I did find a list with compatible devices some time ago but I am not able to find it right now. Sorry!
You can find more information about apcupsd here http://www.apcupsd.org
-
Thanks for explaining! Haven’t tried this myself but would expect that it’s only a matter of setting up the correct backup folders where your data already is stored before you actually start the backup.
When you are using Docker nothing should be stored inside the Docker container so you setup both the location where CrashPlan stores its configuration files and backup folders on your array. Suggestion is to use the cache drive (if you have one) for the configuration files. If you use the cache drive make sure the share (in my case Apps) is set to
Use cache disk: Only
. Included my mappings.
-
I'm currently on v5 and thinking of upgrading to v6 and one of the major concerns is migrating my CrashPlan install. I have other computers that back up to my unRAID's CrashPlan, and I don't want to lose all that file revision history. The backups are stored on my array. Is it possible to install this docker implementation, tell it to backup to my existing folder, and have the clients carry on like nothing happened?
I tried to search through the thread and didn't find anything, hopefully I didn't miss it.
This can be done but you need to be a bit careful. As long as you have set
“Remove deleted files”
under
“Backup Frequency and Variations Settings”
to
“Never”
your files on CrashPlan Central will stay where they are. You are mentioning that backups are stored on your array as well so it’s hard to know your configuration in detail.
However as long as CrashPlan finds files that already are backed up it will not back them up again.
Suggest you search the support pages at CrashPlan, there is a lot of information there even if it’s a bit hard to navigate. Look for transferring ChrashPlan between computers and stuff like that.
-
It seems that after a reboot I can no longer access Crashplan via the GUI to configure/monitor the status of what is going on. Has anyone else ran into this? It is real annoying, but I know the Crashplan server is functioning as my clients are backing up to it without issue.
When I first noticed this problem it was early on. So I deleted my Crashplan docker and all configs for it. Sure enough rebooted and my Windows GUI once again would not communicate with it.
So then I got Crashplan installed configured, and I let it run for about 3 weeks no issues, GUI remained responsive, and all seemed well. Then Unraid released the new beta so I prepared for another Reboot which I knew would kill it. Sure enough, unraid is updated, docker is running and accepting incoming backups, but my GUI client is still not able to connect to the server.
On the Windows client side I have uninstalled and deleted all configs for Crashplan before installing again but it still never establishes its connection.
I double checked the ui.properties file on my Windows PC and it remains configured with my unraid IP address. GUI Client continues to say it can't connect to the backup engine. I can't say this for sure as it has been a few weeks, but I'm fairly sure that when I specify reboot it, that means rebooting either unraid or my Windows PC would cause the client to never connect again. So it basically seems that I can only initialize the GUI client one time and it remains functional until its forced to reconnect at a later time.
I made some notes about my settings the last time I was able to fix my problems:
Modify the "ui.properties" file on your client machine:
#Fri Dec 09 09:50:22 CST 2005 serviceHost=192.168.1.101 <----- unRAID IP servicePort=4243 <----- #pollerPeriod=1000 # 1 second #connectRetryDelay=10000 # 10 seconds #connectRetryAttempts=3 #showWelcome=true
http://lime-technology.com/forum/index.php?topic=33864.0
Modify the "my.service.xml" file on your host machine:
<serviceUIConfig> <serviceHost>0.0.0.0</serviceHost> <----- <servicePort>4243</servicePort> <----- <connectCheck>0</connectCheck>
http://lime-technology.com/forum/index.php?topic=33864.45
But when I check my current setup servicePort=4243 is set to #servicePort=4243
Note that I am not using SSH.
BTW, why not try the Crashplan Docker GUI?
If you have uninstalled and reinstalled the client on your Windows PC you will probably need to reauthorize yourself by login again. Don’t be surprised if Crashplan does a deep scan after login, this can take some time.
-
I wondered if anyone had the system temp settings for the AsRock E3C226D2I Mini ITX Motherboard.
Thanks
This one works for me.
sensors.conf file:
# sensor configuration for unRAID1
chip "coretemp-isa-0000"
label temp1 "CPU Temp"
chip "nct6776-isa-0290"
label temp2 "MB Temp"
go file entry:
# Load drivers for temperature monitoring
modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s
-
Give this a try and let me know if it helps you. Either way, if it helped or not, let me know which cpu you tried with this command:
grep -m 1 'model name' < /proc/cpuinfo
Thanks! Works fine on Xeon E3-1240L v3 2.00GHz. Down to 800 to 1500 MHz at low load. Was up to 2800 and never below 2000 MHz before with same load.
[CONTAINER] CrashPlan & CrashPlan-Desktop
in Docker Containers
Posted
Many thanks for the update(s)! Tested to do a restore and that works fine now.