NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
InterClaw
May 31, 2015Aspirant
NAS not starting any services #25220444
I had a hard time coming up with a good subject for this problem, since I don't really know what's wrong and how to describe it. Here's the story: Suddenly I noticed that CIFS was not behaving norm...
InterClaw
Jul 01, 2015Aspirant
Yeah, the compact button does not seem to do anything at the moment. Did you get some sort of progress bar when you did this? I think the backup needs to be stopped for something to happen. Or maybe the compact command is queued now after backup completes. Just 4.7 months left! :D My speeds are 1-2 Mbit/s... If I ever get to complete this backup I'll take another look at compacting. For now it seems to be under control memory wise though and I should be able to increase the allocation from 2048 towards ~3700 if things get hairy. Just need to check /tmp once in a while for accumulating Java files.
I used to have my PC backups on the NAS selected for backup as well, but deselected those since there are too many changes and it takes too long to upload to the server. 5.1TB -> 4.6TB. I feel it's enough with the live version on the computers + the one backup on the NAS. The data unique to the NAS is what is being backup up now. And being without all those versions related to the PC backups might be what I need to fly below the radar here in terms of memory consumption.
It's a bit weird, my cache now is only 41MB in /usr/local/crashplan/cache so it doesn't seem to be filling up my OS partition very much. If things change I might take another stab at moving the cache to C instead though, like you have.
It seems to me as well that CrashPlan can handle a lot more than the memory requirements state. Perhaps they include really large margins or error. Good news for us if that's the case. :)
I used to have my PC backups on the NAS selected for backup as well, but deselected those since there are too many changes and it takes too long to upload to the server. 5.1TB -> 4.6TB. I feel it's enough with the live version on the computers + the one backup on the NAS. The data unique to the NAS is what is being backup up now. And being without all those versions related to the PC backups might be what I need to fly below the radar here in terms of memory consumption.
It's a bit weird, my cache now is only 41MB in /usr/local/crashplan/cache so it doesn't seem to be filling up my OS partition very much. If things change I might take another stab at moving the cache to C instead though, like you have.
It seems to me as well that CrashPlan can handle a lot more than the memory requirements state. Perhaps they include really large margins or error. Good news for us if that's the case. :)
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!