Our TSM servers are on RHEL6, and run server version 6.3.4. They have 128 GB 
RAM available. 

We have two Windows 2012 R2 servers running the 6.4.0.0 client. They both run 
DFS-R, replicating data from two corresponding servers at our offsite data 
center. The two servers have recently been setup to use Journal Based Backups. 
The two servers at the offsite data center are not using JBB, but if it is 
successfull on the local two servers the plan is to implement JBB on the 
offsite servers also. 

The incremental backups of the two WIndows servers had been running unusually 
long. Six to eight hours, sometimes much more, while scanning only 3 1/2 
million files. And, they backup only a few hundred files. Both have 4 GB of 
RAM. They are virtual machines on ESX. The new elapsed times have been 4 
minutes, 16 minutes, etc. So run times are greatly improved.

Here's my question:  both Windows servers are backing up more objects than they 
are inspecting!  For example: objects inspected 2,840, objects backed up: 
4,101, objects expired: 707.  What does that mean? 

Could it be that several new files were created after the start of the backup, 
so they were backed up immediatly, without entries being made in the journal? 
If that's the scenario, the journal contained 2840 entries for new/updated 
objects, maybe 707 entries for deleted ojects, and 1,261 objects were added or 
updated after the start of the backup.

I have no previous JBB experience, so I'm just guessing at what's happening. If 
someone has seen that behavior before, and has a good understanding of the 
cause I would be grateful to hear from you.

With my thanks and best wishes,
Keith Arbogast
Indiana University