Who is this article for?
Incydr Professional and Enterprise, no.
Incydr Basic and Advanced, yes.
CrashPlan Cloud, yes.
Other product plans, yes.
CrashPlan for Small Business, yes.
This article applies to app versions 6, 7, and 8.
Other available versions:
If the file verification scan is not running as frequently as expected or if you see the error, "The chosen backup schedule is outside of the file verification schedule. Choose a different backup schedule, or update the file verification schedule," update your file verification scan schedule. This article explains what is a file verification scan, and gives some troubleshooting tips for scheduling the file verification scan.
What does the file verification scan do?
When the file verification scan begins, a synchronization process compares the cache indexes at the source with the destination. The file verification scan then examines the locations selected for backup. If the scan detects any new, changed, or deleted files, those changes are added to the to-do list, then backed up to your archive at the destination.
Update the file verification scan schedule
You may want to change file verification scan setting for various reasons, as described in the sections below.
To change the file verification schedule:
- Sign in to the Code42 app.
- Navigate to Device Preferences:
- Code42 app version 6.8.3 and later: Select Settings.
- Code42 app version 6.8.2 and earlier:
- Click Details.
- Select the arrow next to your device name.
- Choose Device preferences.
- Under the General tab, click Manage account on the web... .
- A web browser opens, and the Code42 console appears.
- Sign in using your Code42 app username and password.
- Select Administration > Devices.
- Choose the device for which you want to update the file verification scan.
- Select the action menu in the upper-right corner.
- Choose Edit.
- Click the Backup tab.
- Change the Preferred time for verification scan option as needed.
- Click Save.
When to update your file verification scan
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, check your power settings to see when the computer is set to go to sleep. For example, if your computer sleeps after 15 minutes of inactivity, you're in bed by midnight, and the file verification scan is set to run at 3 a.m., then 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. The Code42 app uses different logic for the two:
- If the scan is set to run every 1 day at 3 a.m., the Code42 app 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, the Code42 app 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 determine 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 (for example, every 30 days during a large initial backup). Learn more about adjusting the Code42 app settings for large backups.
The chosen backup schedule is outside of the file verification schedule
If you have configured the Code42 app to run only between specified times, and the file verification scan schedule is set to run outside of your backup window, you see the error "The chosen backup schedule is outside of the file verification schedule. Choose a different backup schedule, or update the file verification schedule." If you see this error, update your backup schedule or the file verification scan. This way, the Code42 app can analyze what needs to be backed up early in your backup window and your backup will progress more quickly.
For example, if Code42 backs up from 12:00 a.m. - 7:00 a.m., the verification scan should be scheduled at 12:00 a.m.
Will Code42 run while I am logged out?
Yes. Code42 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, the Code42 app continues to back up your files as long as the computer is awake.
For Windows, Code42 always continues to back up because it runs as a background service. For OS X, Code42 continues to back up unless you specifically customized your installation to run the Code42 app "as User.”
Frequently Asked Questions
When does the file verification scan occur?
By default, the scan is set to automatically run every day, but this schedule can be changed by updating the Preferred time for verification scan setting in device backup settings. The Code42 app periodically runs additional verification scans to detect data corruption, purge files that are no longer selected for backup, and prune file versions and deleted files according to your frequency and version settings.
In addition, there are times when a file verification scan is automatically triggered:
- Changing the file selection: If you update your backup file selection, either to add or remove files, the scan runs to look for new, changed, or deleted files.
- Replacing your device: After replacing a device (for example, if you recently changed devices), the scan runs to compare the files on your device to the files in your existing backup archive.
- Clearing your cache: The cache includes information about your destinations and the data on your device. When the cache is cleared, a file verification scan initiates to help rebuild this information.
- Attaching an external drive: When you attach an external drive, the scan runs to compare the files on the drive to the files in your existing backup archive.
- At device reconnection (version 6.8.3 and later): If the device is powered off or asleep at the scheduled scan time, the scan runs 15 minutes after the device reconnects.
- Manually: The file verification scan can be triggered at any time from the Backup Set Settings Menu.
What does a file verification scan look like?
Initially, the Code42 app displays a message on the Backup tab that reads, "Scanning." If this initial scan determines that there have changes to the files, the file verification scan starts.
This file verification scan may look like your backup is starting over because the estimated time to complete doesn't account for the data that has already been backed up. During the file verification scan, the Code42 app compares each block in your file selection to the blocks that have already been backed up in your archive. Once the blocks have been analyzed, the Code42 app only backs up the differences.
Verification and backup is prioritized as follows:
- Newer, smaller files
- Newer, larger files
- Older, smaller files
- Older, larger files
How long does a file verification scan take?
The file verification scan normally runs within minutes and most users do not notice it. The larger your file selection, the longer the file verification scan takes. Although the scan may take longer for large backups, it is much faster than backing up the files. The estimated time to complete the file verification scan initially reports the time it would take to back up all files, but drops sharply once it finishes backing up new files and starts de-duplicating the data that is already backed up.
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. Keep the scan intervals reasonable (e.g., every 30 days during a large initial backup). If you set the value too high, like every 10,000 days, the value overflows and the Code42 app ends up running the scan daily, which is the opposite of what you want!