Article ID: 54061
Article Type: Troubleshooting
Last Modified:
The backup job fails because the backup content cannot be found.
Job fails during scan with error code 17:11 File system scan failed - there is nothing to backup.
Applies to: Windows File System
FileScan.log may show entries similar to:
CReviewClientContentNodeCallback::OnNode() - Client content path does not exist, SourcePath=
Applies to: UNIX File System
During NFS volume backups, the following error message appears in the FileScan.log file on the client computer. The log file is located in the Commvault Log_Files directory (by default, /var/log/commvault/Log_Files).
CScanner::StartScan(116) - Scanner reported that content is missing or inaccessible, skipping and continuing with rest of the content
Applies to: Windows File System
Explicit content associated with subclient is missing or defined incorrectly. For example, a specified drive letter has been changed or a specified folder renamed.
In rare instances, defragmentation or drive maintenance software running concurrently with backup job may cause this error.
In other rare instances, the client is a virtual server on a cluster that has moved to another node and Commvault cluster client was not configured/used.
Applies to: UNIX File System
The local settings on the NFS server and the NFS client (where the NFS share is mounted for backup) do not match.
Applies to: Windows File System
Verify subclient content is listed correctly and can be browsed as defined.
If regular expressions (wildcard characters) are used, make sure the "Treat character as regular expressions" is selected.
If backing up a virtual server on a cluster, configure cluster client. See BOL for directions.
http://documentation.commvault.com/commvault/v10/article?p=features/clustering/deployment.htm
Applies to: UNIX File System