August 16, 201015 yr I am having trouble writing to disk on the unraid server while running crashplan on the unraid server. I have installed crashplan on my UnRaid server. I am trying to use the server as a backup destination for my other computers. I have a disk and share setup for this purpose. The disk is disk 7 and the share is Crashplan. I have tried both /mnt/disk7/Crashplan/Backups and /mnt/usr/Crashplan/Backups for the destination in crashplan. When another PC trys to backup to the UnRaid server it runs for a while then UnRaid runs out of memory. Looking at the UnRaid server the files never get written to the physical drive. It looks to me like the UnRaid Server is buffering in ram until it runs out of ram then it pukes. I have 2 gigabytes of ram so it takes a while. I am a Linux noob so any help is really appreciated. thanks unraid version 4.5.6
August 16, 201015 yr try this setting and see if you continue to run out of ram. sysctl -w vm.vfs_cache_pressure=100
August 16, 201015 yr Here are my settings for Crashplan: Created a share in unraid frontend: Name = backup export = dont export use cache = no use the Putty/GUI trick in the HOWTO and set the default backup archive location in crashplan: /mnt/user/backup my GO file contains: # install crashplan tar -C / -xvf /boot/packages/crashplan.tar /usr/local/crashplan/bin/CrashPlanEngine start It is all working really well. I have 2 machines backing up to Tower. I have a "friend computer" offsite that Tower backs up important files to and also receives important files. I havent checked to see if I need to do a crashplan update on the server yet as it is running smoothly. Tony (btw, I have 4gb ram and 5TB of disks in Tower)
August 17, 201015 yr Author try this setting and see if you continue to run out of ram. sysctl -w vm.vfs_cache_pressure=100 Unfortunatly this did not fix the problem. I can see the available memory going down in top and the cached number going up but no writes physicaly happen on the drive. I can write to this drive over samba. I am completely at a loss. Any other ideas? thansk
August 18, 201015 yr You are writing to ram... /mnt/usr/Crashplan/Backups = a location in the in-memory file-system. /mnt/user/Crashplan/Backups = a location on one of your disks. usr vs. user Big difference. Also, make absolutely certain the directory names have the same capitalization as those you configured. Type ls -l /mnt/user/Crashplan/Backups to make sure it exists. If not, type ls -l /mnt/user to see how you did name it.
August 18, 201015 yr Author I think I have figured it out. I evidently fat fingered the incomming location to /usr/ instead of user when i ran the install script. for some reason reconfiguring via the gui did not clean up the problem. attempting to clean up the mess. more later thanks for the help ================================================ Update - ok i confirmed the problem. Even though i set a new backup destination with the gui connected to crashplan on the unraid server - the information i messed up was still playing ghost in the machine and messing me up. I reinstalled and it is working ok now. (i found the bad info still in some xml config files even though i changed the data in the gui) Thanks a lot for the help. For what it is worth I really like the all you can eat family plan to backup to crashplans servers.
Archived
This topic is now archived and is closed to further replies.