I've a client on windows 5.3.0.0 (He's thinking about moving to 5.4.0.2) who's seeing, every day, reports like this:
Total number of objects inspected: 1,323,867(SESSION: 6278) Total number of objects backed up: 0(SESSION: 6278) Total number of objects updated: 1(SESSION: 6278) Total number of objects rebound: 0(SESSION: 6278) Total number of objects deleted: 0(SESSION: 6278) Total number of objects expired: 25,022(SESSION: 6278) Total number of objects failed: 1,323,867(SESSION: 6278) I would normally expect a scheduler log full to overflowing with 1.3M iterations of "Can't get file [x] for reason [y]". But the scheduler log is nearly empty: Just the normal expiration messages. So, a riddle: What is it that fails a million files, but makes no noise? - Allen S. Rout
