ClearFoundation

Decided to give CrashPlanPro a trial. No problem installing on Windows Machines, and it was simple enough to install the engine to run as a service under ClearOS. Where I'm running into issues is configuring the service under ClearOS.

I have confirmed the service is running, but the server does not show up as a "device" on the CrashPlanPro portal, nor can I connect to it using a local Windows client.

I've submitted a support ticket to CrashPlan, but was wondering if there are any members of the forum running CrashPlanPro that can provide assistance.

For General Information, I received a reply from Crashplan support indicating "headless" support is not officially supported. which basically means even though they have directions on the site for setting up a headless configuration, if it doesn't work you're on your own.

Using the instructions posted at support.crashplan.com/doku.php/how_to/co...re_a_headless_client as a starting point, I was finally able to get the service running after opening TCP ports 4242, 4243, and 4283.

I then opened a winding in Putty and used "ssh -L 4283:localhost:4243 root@xxx.xxx.xxx"

I reopened the GUI client in Windows, and everything seems to be working. I will post a follow-up if there are additional issues.

Thanks for the update! Crashplan certainly looks useful

I've had a day of living with CrashPlanPro and while I remain enthusiastic about it's possibilities, there are issues that need to be addressed.

The default backup settings need to be modified when operating in a headless configuration. By default, when the software determines there is no user activity, it allows up to 80 percent of the CPU to be dedicated to backup. While this would work as a workstation, it has the effect of virtually shutting down the server. I reduced the percentage to 30% and noticed no decrease in backup throughput while most server functions returned to normal levels of performance.

The largest issue still to be addressed is the effect it's operation has on the mail server function. Even with the CPU percentage dialed back, inbound email is piling up in the queue and not passing to user's inboxes. Outbound mail appears to send, but copies are not saved in the "sent" folder. According to the readme file, Crashplan uses TCP port 443 outbound to communicate with the CrashPlan servers and listens on TCP ports 4242, 4243, and 4283 (CrashPlanPro, only). Is it possible this communication is disrupting mail delivery?

I've tried restarting amavisd and postfix and flushing the postfix queue both at the command line level and through the ClearOS web interface without success. If any users or admins have other suggestions, please let me know. Otherwise I'm hoping that once the initial backup is complete and disk activity and CPU drain go back to normal levels, mail will start to deliver. In the interim, I will keep looking for a solution.

Quick update. I had to restart the server this morning as emails were still not delivering and I was not able to locate the process that was not working properly. Emails are now delivering and the mail queue is flushing. CrashPlanPro is continuing to backup in the background and I can go in through the web portal to check progress. I will not attempt to restart the GUI until I can locate the source of the conflict. Will post with any additional updates.