Skip to main content

This article applies to Code42 for Enterprise version 4.

Other available versions:

Version 6icon.qnmark.png

Code42 Support

Update file verification scan schedule

This article applies to Code42 for Enterprise version 4.

Other available versions:

Version 6icon.qnmark.png


If the file verification scan is not running as frequently as expected or it is running too frequently, you may want to adjust when it is scheduled to run. Review this troubleshooting guide for tips on scheduling the file verification scan.

Recommended solution

The default file verification scan schedule, every 1 day at 3:00 AM, works for many users. However, there are situations when you may want to change these settings, as described in the sections below. To change the file verification schedule:

  1. Open the CrashPlan app and go to Settings > Backup
  2. Modify the Verify selection every options as needed
  3. Click Save

File verification

The scan is not running at the specified time

If you checked the History log and found that the file verification scan is not running, double-check your power settings to see when the computer is set to go to sleep. If, for example, the computer sleeps after 15 minutes of inactivity, you're in bed by midnight, and CrashPlan's file verification scan is set to run at 3 a.m., the scan will never run. There are a few possible solutions:

  • Change your computer's sleep settings so that the it does not sleep at night.
  • Change the time when the verification scan is set to run to a time during the day when the computer is likely to be on.
  • Set the scan to run every X hours, rather than every X days. CrashPlan uses different logic for the two:
    • If the scan is set to run every 1 day at 3 a.m., CrashPlan asks, "Is it 3 a.m.?" If so, then it runs the scan. If not, then it doesn't run it.
    • On the other hand, if the scan is set to run every 23 hours, CrashPlan asks, "Has it been more than 23 hours since the last scan ran?" If so, then regardless of the time of day, it runs the scan.
    • If it is difficult to predict when your computer may be asleep, this is your best option.

You have a very large file selection

The larger your file selection is, the longer the file verification scan takes to run. Especially during your initial backup, you may wish to set the scan to run less often, as it can consume a significant amount of time that could otherwise be used to continue the backup. You can use the History log to gauge how much time the verification scan takes. Update your scan interval to strike a balance between the time the scan takes and the interval between scans.

Keep the scan intervals reasonable (e.g., every 30 days during a large initial backup). If you set the value to something too large, like every 10,000 days, the value overflows and CrashPlan ends up running the scan daily, which is the opposite of what you want!

CrashPlan set to run between specified times

CrashPlan is set to run backup Always, by default. If you have configured CrashPlan to run only between specified times, then you should also update the file verification scan schedule to run at the start of your backup window. This way, CrashPlan can analyze what needs to be backed up early in your backup window and your backup will progress more quickly.

For example, if CrashPlan backs up from 12:00 a.m. - 7:00 a.m., the verification scan should be scheduled at 12:00 a.m.

Will CrashPlan run while I am logged out?
Yes. CrashPlan continues to run even if you are not logged in to your computer. If you log out for the day, or because you share your computer with multiple users, CrashPlan continues to back up your files as long as the computer is awake.

For Windows, CrashPlan always continues to back up because it runs as a background service. For OS X, CrashPlan continues to back up unless you specifically customized your installation to run CrashPlan “as User.”