By any chance, does this client's file system have over a million files? it looks like a fulle backup according to the schedule name, but it also shows the Change Journal is not being used.
Yes, NetBackup does scan the file system to determine all of the file names that need to be backed up before it begins backing up anything. This could be based on the archive bit, or on timestamps, of each file, depending on what you have configured for that client.
This is in addition to the time it takes to do a Volume Shadow Copy snapshot, if configured on the client.
The more files it has to scan through, the longer this takes. On a client with a slow disk system that is also performing batch processing/database crunching/other non-backup related activity (like a UAT client might be doing!), this can take a really long time. If the CLIENT_READ_TIMEOUT (or other configurable timeout values) are set too low, the connection between the media server and the client could be closed before the backup has begun.
The Windows Change Journal is a feature that was introduced in Windows 2003 (I think) that tracks (or "journals") all the new or changed file names on each drive on the clients. NetBackup can read this journal instead of traversing the entire filesystem structure to build the list of files to be backed up. This can save considerable time, particularly on a busy client.
The only negatives of using the Change Journal feature:
