NBU Master - Solaris 10, Netbackup 7.1.0.1, 10Gbit interface.

Client - Windows 2008 R2, NetBackup 6.5.6, 1Gbit interface.

File system is located on SAN and has 2.5 million files.  About 10,000 files change per day. 

We're trying to get Windows Change Journal to work, but our initial testing is showing no backup speed improvement versus previously reading the entire directory structure.

We have confirmed that the Windows Change Journal is active on all drives on the client using "fsutil usn queryjournal".  This has been enabled (by default) since the box was built a few months ago; we are just getting to the point of trying this feature now.

I checked the box on the client properties to use the Change Journal, stopped/started the NetBackup Client Service on the client, and initiated a Full backup that completed successfully.  The client is only defined to one policy in NBU.

Prior to this change, incrementals were taking about 25 minutes every day.  After the change, still taking 25 minutes every day for the past 3 days. 

Backups are being written to Data Domain disk.  I don't see any peformance issues (CPU, network, disk I/O, memory) on the client, the media server, or the Data domain during the backup period.

I don't see any messages in the job details that indicate any problems with Change Journals not being enabled or nor available.

Any ideas why the incrementals are no faster now than they were before?  I would have expected to see at least some improvement.