4 ms·
36T to CrashPlan sits on 36GB of RAM at all times... screw that. rclone never uses more than ~2GB to manage my whole 50TB dataset. edit: Also, I'm using a Supe
by melp 9y ago
36T to CrashPlan sits on 36GB of RAM at all times... screw that. rclone never uses more than ~2GB to manage my whole 50TB dataset.
edit: Also, I'm using a SuperMicro chassis, not a Norco. I've got a section where I go into why I went with SuperMicro.
- dom0 9y agoUhm, what exactly is crashplan doing with all that memory?
- glenneroo 9y agoI wonder if it's related to the memory "issue" with their client, where exceeding 1TB/1 million files, a manual edit of the .ini file to bump the JVM memory allocation is necessary. I remember reading somewhere that it has to do with CRC checksum calculation for all the files? I've had to change the setting multiple times (currently at 8GB for ~8TB/1 million files). https://support.code42.com/CrashPlan/6/Troubleshooting/Adjusting_CrashPlan_Settings_For_Memory_Usage_With_Large_Backups https://support.code42.com/CrashPlan/6/Troubleshooting/Adjus...
- dom0 9y agoHm, maybe give Borg a shot. For initial backups it's not exactly the fastest thing, though much better after that.
- ValentineC 9y ago> rclone never uses more than ~2GB to manage my whole 50TB dataset. How do you handle file versions with rclone?
- melp 9y agoI guess that's the downside. It only syncs the latest version of every file it syncs.