Who is this article for?
CrashPlan for Small Business, yes.
Code42 for Enterprise, yes.
Link: Product plans and features.
This article applies to version 4.
CrashPlan doesn't back up new files, even though "Watch files in real-time" is turned on. This issue is caused by a daemon, or process, within the operating system failing to report these changes to CrashPlan.
Before you begin
First, make sure that real-time watching is enabled in the CrashPlan app.
- Go to Settings > Backup
- Locate Advanced settings and click Configure
- Confirm that the box next to Watch file system in real-time is selected
- Click Ok and then click Save
To determine whether or not real-time file watching is working, you can manually start the file verification process.
- Go to Settings > Backup.
- Locate the Verify Selection Every setting and click Now.
If CrashPlan file verification scan detects your new files, proceed to the section below about your operating system to continue troubleshooting.
CrashPlan uses Spotlight to detect file changes. If you notice that new files are not being detected and backed up by CrashPlan, re-index Spotlight by following the steps outlined in this Apple support article.
CrashPlan's real-time file watching doesn't detect file changes in locations that Spotlight does not index. By default, Mac OS X v10.6.8 Server doesn't index volumes that are not shared. To use CrashPlan's real-time file watching on a volume that is not shared, you must index the volume for Spotlight on your operating system.
Real-time file watching relies on NTFS (New Technology File System) events posted from the operating system to keep track of changes in your files. Real-time file watching does not work on volumes that are not in the NTFS format.
To check which format your drive is using:
- Open a file browser.
- Right-click on the drive you want to check (typically the C: drive) and select Properties
- From the General tab, locate the File System description
VSS on Windows
If you are working on an open file, CrashPlan relies on a system-level service called VSS (Volume Shadow Copy Service) to make a copy of this file for backup. If VSS is unable to provide a copy, CrashPlan skips the file and tries again the next time it performs a backup. However, if you notice that your backups are not reaching 100%, or that the open file has not backed up newer versions recently, please refer to our VSS troubleshooting guide.
CrashPlan requires the kernel extension called inotify to run when files are added, removed, or changed. Verify that inotify is installed and running so CrashPlan can watch files in real time.
If inotify is installed and running, but real-time file changes are still not detected, you may be running into inotify's max watch value. Please see this article for troubleshooting and resolution.