Helmonder

As far as I understand it is never a good idea to update the app itself.. Is that what happened? Verzonden vanaf mijn iPhone met Tapatalk

Try to open the webgui of crashplan using Edge... Guessing you are using Chrome or Internet Explorer ? Maybe using Kaspersky as a virus scanner ?

start the docker wait 5 minutes open the webgui copy the url of the webgui paste that url in another browser (edge for example) should work.. in my case it was solved after deinstalling kaspersky..

For anyone having issues with NoVNC not showing anything when connecting to the webui from chrome.. I used to have this, today I switched from Kaspersky virusscanner to symantec and the issue is gone.. Works perfectly now.

I think that is correct... the desktop container is depreciated, you should use the combined version... There is no need for the seperate desktop docker, the gui is now integrated in the basic version. gfjardim/crashplan:latest

You can work fine without cache drive..

performance with a cache drive pool there is no higher risk on data loss then within the array.

Do you use chrome ? It works very badly with vnc.. try with Edge, IE or firefox...

I use crashplan but I backup to a secundairy unraid server.. So not to their cloud.. I also tried uploading to their cloud but that is totally unpracticle...

I guess you should ask on a synology forum ?

600mb of memory ? everyone... 1TB of memory would be for approx 1500tb of storage... I think you misread my post.. Their requirements are the same as zfs asks... so probably not that over the top..

It works on linux also.. As long as you connect the app thru a putty tunnel... OR... use the unraid Docker.. This brings a desktop interface without any special tricks, works great.

Or, using the desktop interface: Open the CrashPlan app Double-click the CrashPlan logo in the upper-right corner Enter the following command, using a value appropriate for the size of your backup selection (for example, 1536 for a 1.5 TB selection): java mx 1536, restart Crashplan advices to change this parameter if you backup more then 1 terabyte (which is what we probably all do over here). They advice 1GB of memory for every TB (or for every 1 million files) of backupped data. They also state that Crashplan actually needs 600MB of memory for every TB of data, they advice the 1GB because of future growth. I just entered 8192, this should be enough for 14TB according to their calculation. I actually allready backupped 12TB of data with the initial 1GB of java heap storage.. So their calculation is not on the mark.. I am thinking that the average media storage is way more relaxed on this requirement then average file storage.. So we'll see..

All looks good... files are being sent again... I'll let it finish this testrun and then add the whole 14tb again.. See if it holds..

Increased it to 8 gig... I'll monitor the log to see what happens...

service.log shows outofmemory errors in java heap... I have seen solutions for that and will try right away, thanks !!

I have nothing with crashplan.. I am backing up to my own secundairy server... The data was never backupped to that other server (unless "analyizing" means its actually backupping).. The folder that it was " analyzing" for two weeks was removed out of the backup set, crashplan makes a point of it to tell me it is really gone then.. So there should be nothing it can dedupe.. As far as I understand the process..

Am using something like 40kb/s .. Not doing anything else..

I agree... I removed the complete folder from the backup however... Maybe it still recognises the blocks as beiing there... Still doesn't explain how they got there in the first place though... Ever since I added that 14TB folder I have only seen "analyzing"..

One thing I notice... It is still "analyzing", nothing is getting uploaded, but the "remaining files" number decreases... Its doing all little files so the gb counter doesnt change.. Can it be that it is actually backupping but not telling me it is ? It should show "uploading" and a speed counter right ?

Has been "analyzing" 5 separate series all day... Not uploading, just "analyzing"... I will let it running just to get an idea of what is going on...

And now it has starting "analyzing" my itunes folders... I forgot about that taking more then a week last time... So I removed that from the backup set also.. I am at the point I just want to get this to work, finding out what is going on.. More important than actually having a backup..

Its now scanning the changes on my other folders.. It finds them quick enough but scanning -them- still takes a few seconds per file.. Lets say five.. The 14TB folders (tv shows) contains approx 250,000 files, that would mean 1,250,000 seconds.. That comes down to 14 days of scanning for 250,000 files.. That is approx the same I was experiencing.. I am wondering if some tinkering with the docker settings for cpu and memory could make a difference.. Read somewhere that crashplan advices 1GB per terabyte of backup.. I don't even have that amount of memory in the system... If all else fails I will move to rsync ..

I run my Crashplan in a VM. Yesterday I added an additional 25TB of data to my backup files and wondered how the resources in the VM were doing, so I brought up the resources monitor utility. The VM barely used any memory and ran very smoothly as did the unraid stats themselves. I noticed I had too many cores dedicated to the VM, so I removed 5 of them and just now have 2. Everything still runs smooth in the VM and also the host runs good too. The scanning of the extra files took about 10 minutes. Damn... then something is seriously wrong here... Any thoughts ? I have mailed crashplan support.. How many memory are you giving the VM ? I have been giving the VM 16MB, but seeing how it only uses %9 of during a peak time I'm lowering that to 2MB. (%10 of 16MB - 1.6MB) - I think 2MB would be fine and I could care less how long it takes. Kind of set it and forget it. I left the resource monitor on the entire time it scanned all the new files and the memory never went over %9. I was under the impression Crashplan was using a lot more resources but when I finally checked myself it was not. What happens when you try to to select just one folder with 1GB or less in it? Does your Crashplan go to work after that? You are right, that is a good way to check... I just removed the 14TB share I added from the backup set.. So now we are back on the level that worked before.. I will let that recalculate and stuff till it tells me its done.. Then I;ll slowly add more..

I run my Crashplan in a VM. Yesterday I added an additional 25TB of data to my backup files and wondered how the resources in the VM were doing, so I brought up the resources monitor utility. The VM barely used any memory and ran very smoothly as did the unraid stats themselves. I noticed I had too many cores dedicated to the VM, so I removed 5 of them and just now have 2. Everything still runs smooth in the VM and also the host runs good too. The scanning of the extra files took about 10 minutes. Damn... then something is seriously wrong here... Any thoughts ? I have mailed crashplan support.. How many memory are you giving the VM ?