Where is crashplan logs

With the forced migration of CrashPlan Home users to CrashPlan for Small Business, many people were pretty disappointed with the UI of the new client compared to what they were used to.

There were many issues, but what I disliked the most personnally was the removal of any relevant info about the upload progress. In CrashPlan Home it was possible to see the upload speed and the file currently uploading, which gave a pretty good idea of what was happening. Now all we have is an overall percentage of completion as well as the "done" and "remaining" totals rounded to the nearest unit, which in the case of terabytes is pretty vague.

This little package aims to provide some details that the standard interface does not. One limitation is that the CrashPlan backup entries do not specify the seconds in their timestamp, only the minute.

So for files uploading in less than 5 minutes, the speed might not be super accurate. Also, CrashPlan logs other stuff not directly related to uploaded items in that log file. I try to ignore those lines, but it might happen that unexpected lines appear in the output. Don't worry, it's normal, I just didn't have the time and knowledge to cover all possible cases.

Skip to content. Star 9. This is the more secure option, but it means that no one including the ITS Helpdesk can recover your files without your passphrase. Need Help? Was this helpful? Thank you. Your feedback has been recorded. Comments Do not fill this field out. It is used to deter robots.

Submit Cancel Feedback. Blank Blank. Blank Details. Article ID: Recipient s - separate email addresses with a comma. Check out this article I found in the Carleton Client Portal knowledge base. To read the files, navigate to the log folder and open the log with a text editor. More advanced users may prefer to use the Command Line or Terminal. When reading through the logs, it is often helpful to search for WARN as a starting point. If you see an "Unable to connect to the backup engine" message when you try to open the Code42 app, and the below error appears in service.

For more details, see Cannot connect to background service. One extremely common reason for the "unable to connect to the backup engine" messages is that the backup engine is running out of memory.

This is visible in the service. See Code42 app does not run for complete details. Client cache issues can manifest themselves in a few different ways, including: some or all files missing from the Restore tab , stopped backups, incorrect reports, and incorrect file selection size. Real-time file watching can have issues that manifest slightly differently on Mac and Linux. For more information, see Understand and troubleshoot backup issues with Mac file watching services and Linux real-time file watching errors.

Lines that begin with a "W" indicate files that are failing to back up. The first two numbers summarize the Code42 app's analysis of the file:. If the first number is greater than zero, and the second number is zero, then it's a new file that's backing up for the first time. For example:. If the first number in the bracketed sequence is zero, and the second number is greater than zero, then it's an existing file that has already backed up.

There is nothing new to back up.