I need an explanation as to why a select group of client nodes do not have
their filespace backup statistics updating to the ADSM server. The common
denominator between these client nodes is that they have been recently
registered within the last 2 months to the ADSM server. Does anyone know how
to rectify this situation, accompanied by the proper procedure/precautions
so that this will not happen in the future ?


Environment and case particulars -

ADSM ver 2.1.09

Schedule to client node setup:
old/existing schedule - new registered node associated to existing schedule
(one-to-one association)
new schedule - new registered node associated to new defined schedule
(one-to-one association)


ADSM client:
client dsmerror log:
clean - no event errors

client dsmsched log:
clean - no failures, i.e.:
"scheduled event completed successfully
sending results for scheduled event
results sent to server for scheduled event"

To verify that the backups actually exist, I have restored client files
(client logged as backed up the previous day) which are known to fallen
within the ADSM client's schedule criteria - all restores were successful !


ADSM server:
q event <domain>  <sched_name> f=d
backup start date/times with completed status
results=0

q node <node_name> f=d
stats updated i.e.:
last access d/t, days since last access, bytes rec'd, bytes sent, duration
of last session

q file <node_name> f=d
no backup stats i.e.:
last backup start DT
days since last
last backup completion DT
day since last backup completed

q auditoccupancy
select group of client nodes show 0 MG backup storage used
2 of the client nodes display low MG storage contradicting the "q file
<node_name> f=d" reporting


Any insight and direction for resolution will be greatly appreciated !


Thanks,
Becky Gordon
John Deere Health Care
Infrastructure Support
(309)765-1109
(309) 748-1022  Fax