It does mention in TN
Log messages about the Use Change Journal option and Accelerator: http://www.veritas.com/docs/000044678
In the backup selections, a path contains a reparse point (directory junction or a symbolic link). The Use Change Journal option cannot be used. NetBackup must perform a regular file system scan to back up the directories correctly.
Unfortunately there is no way around this.
Thank you, revarooo, but I don't think so.
The path that contains a reparse point is a subdirectory of the backup selections.
And that subdirectory has been excluded from the backup selections by means of an Exclude File List.
Why is NetBackup looking for reparse points in folders excluded from backup selections?
The exclude list is used when client (bpbkar32) is sending data. Not prior for bpmount/snapshotting/create or update track file etc.
If change journal is working for netbackup it would enumerate all files including these in directory F:\THIS_FOLDER_HAS_A_REPARSE_POINT, but these files would not be send to media server.
Sorry to insist on this topic, but can NetBackup behaviour be changed so as to consider the Exclude File List before searching for reparse points?
As I don't need to backup the data pointed to by any reparse point, I don't mind if these files can't be enumerated or have change detected by windows change journal.
But I do wish to use windows change journal for enumeration of the remaining backup selections (where no reparse point exists), to improve backup performance.
I'm not sure about this... but if NetBackup cannot use the CJ for enumeration, then it is probably because the the reparse point is an object which move around the file system, i.e. one day it could here, and another day over there... on an admins whim so to speak... and MS Windows NTFS probably doesn't track these changes... and so NetBackup cannot track these changes... and so, the presence of even just one single reparse point means that software *must* take the safe option and not use CJ enumeration.