job stuck on "scan" but never backs anything up

Last post 12-30-2011, 1:19 PM by Liam. 6 replies.
Sort Posts: Previous Next
  • job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 10:18 AM

    Using commvault 8.0 trying to back up a Windows 2003 target, 32-bit file system.  The last 3 jobs have been getting stuck during the 'scan' process and the job never actually starts backing anything up.  The job just sits at 5% and never goes any further.  Other sub-clients of the target system are being backed up successfully (so it's not a connectivity issue).  I have tried restarting services on the target machine.  Right now the job has a little yellow/orange warning when I look at the Job Controller.

     

    Errors in the job log:

     Can't initialize proxy host mapper. Exiting.

    .

    .

    :GetCertificateServerSkipList() - fnCertSrvIsServerOnline() failed for server <servername> - Error Code: -2147221164

    .

    .

    ErrorCallBack() - ErrorCallBack(594): -Error-:  returned error code 2,System\CurrentControlSet\Services\NtFrs\Parameters\Replica Sets: The system cannot find the file specified.
    5368 c80 12/30 08:46:49 445786 FrsClass::EnumReplicatedPaths(432): -Warn--: NtFrsApiGetBackupRestoreSets returned 8004
    5368 c80 12/30 08:46:49 445786 CvFilterFile::IdentifyFilterItem(562): -Debug-: Error Finding File  e:\indexes Err: [2] The system cannot find the file specified.
    5368 c80 12/30 08:46:49 445786 CvFilterFile::ReadFilterItemsIntoList(402): -Debug-: WildCard Filter *.[l-n]df corrected as \**\*.[l-n]df
    5368 c80 12/30 08:46:49 445786 CvFilterFile::IdentifyFilterItem(562): -Debug-: Error Finding File  {One Touch Files} Err: [123] The filename, directory name, or volume label syntax is incorrect.

    .

    PATHCACHE: insert failed, value is zero and no path store

     

     

    What is going on?  Nothing has changed on the Media server or the target machine.

     

  • Re: job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 10:54 AM

    Hello,

    Are you running a Full backup?  If not, please try to run a Full to see if that helps with the scan time (it will build the collect files in the Job Results dir).  I would also recommend checking the backup history on this subclient to see how long the scan times usually take (on both Incrementals & Fulls). 

    If you right-click on the backupset properties, what scan type are you using?

    JW

  • Re: job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 11:21 AM

    The last few jobs have been differentials, an average scan on past successful jobs has been ~25 minutes.  But these problem jobs just sit and scan for hours and hours.

    The jobs are using Change Journal.  It's interesting that other sub-clients of the same target are being backed up just fine  (e.g. the sub-client to back up the C: drive is OK, but this sub-client to back up the E: drive is just spinning its wheels).

     

     

  • Re: job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 11:28 AM

    Thanks for the update.  I would proceed with running a new Full backup to see if this clears up the condition.

    JW

  • Re: job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 12:01 PM
    • Aplynx is not online. Last active: 05-22-2019, 12:46 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,587
    are you seeing a lot of failed files in the prior job for the sub client stuck in scan?
  • Re: job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 1:14 PM

    yes, there are over 1 million failed files in the last "successful" job before things started going haywire.  Although, with that many failed files, I'm not sure why the job would be considered successful   Undecided

    Tech support finally got in touch with me, and explained what happens with the index cache when there's that many failed files, or more like what doesn't happen... we are running a full backup now and it appears to be going well.

    I'm impressed with the quick responses in this forum!  Thank you to all who offered suggestions and advice!

    Andi

  • Re: job stuck on "scan" but never backs anything up
    Posted: 12-30-2011, 1:19 PM
    • Aplynx is not online. Last active: 05-22-2019, 12:46 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,587
    you can probably track this back to a vss or volsnap event during the backup where the vss service was not allocated enough space for the snapshot. this means the source for all the open files is missing and becomes the failed to find file error. when there is that many failed files the next backup scans the normal information then goes back for the millions of failed files which increase the length of scan time.

    this can be resolved by running a full backup as this will clear the failed file results which is only carried over for incs or diffs. the issue may reoccur if the vss issue is not addressed.

    the job is considered successful because it ran from 0-100%. a job summary report would show the amount of failed files and can be modified to show all the failed files.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy