incorrect auditoccupancy values (off by >1 TB)

[oskie]

AuditOccupancy values for a certain node is off by more than 1 TB!
This is a TDPExchange node. Can anyone explain these values below?
This is with TSM 6.2.2.0. I am about to report this to IBM but I would like a second opinion first.

tsm: WIN-TSM01>q auditocc NODE f=d
License information as of last audit on 2010-12-03 at 13:36:34.

Node Name                                  Backup       Archive     Space-Managed         Total
                                          Storage       Storage      Storage Used       Storage
                                        Used (MB)     Used (MB)              (MB)     Used (MB)
-----------------------------------     ---------     ---------     -------------     ---------
NODE                                    2 484 204             0                 0     2 484 204

tsm: WIN-TSM01>select * from auditocc where node_name='NODE'

       NODE_NAME: NODE
       BACKUP_MB: 2484204
  BACKUP_COPY_MB: 0
      ARCHIVE_MB: 0
 ARCHIVE_COPY_MB: 0
      SPACEMG_MB: 0
 SPACEMG_COPY_MB: 0
        TOTAL_MB: 2484204
BACKUP_ACTIVE_MB: 0

tsm: WIN-TSM01>q nodedata NODE

Node Name            Volume Name                        Storage Pool         Physical
                                                        Name                  Space
                                                                             Occupied
                                                                               (MB)
----------------     ------------------------------     ----------------     --------
NODE                 000006L4                           TAPEPOOL              82 929.27
NODE                 000014L4                           TAPEPOOL               1 398.11
NODE                 000030L4                           TAPEPOOL             315 404.18
NODE                 000036L4                           TAPEPOOL             230 147.86
NODE                 E:\FILE100.DSM                     FILEPOOL              16 227.89
NODE                 E:\FILE102.DSM                     FILEPOOL                   0.16
NODE                 J:\FILE103.DSM                     FILEPOOL                   0.31
NODE                 J:\FILE109.DSM                     FILEPOOL                   0.11

 

[ChrisRees]

Hi

I'm not sure about V6 but in 5.5 "audit license" had to run to update the auditoccupancy data. Do "help q auditocc" and it will tell you if that is still the case.

Cheers

 

[oskie]

Yes audit license was run minutes before the q auditocc.
Also check out this output:

tsm: WIN-TSM01>q occ NODE

Node Name     Type    Filespace      FSID    Storage       Number of     Physical      Logical
                      Name                   Pool Name         Files        Space        Space
                                                                         Occupied     Occupied
                                                                             (MB)         (MB)
----------    ----    ----------    -----    ----------    ---------    ---------    ---------
NODE          Bkup    NODE\StgGrp1       1    FILEPOOL             24            -    1 015 347.06
NODE          Bkup    NODE\StgGrp1       1    TAPEPOOL             27    320 560.41   320 560.41
NODE          Bkup    NODE\StgGrp2       2    FILEPOOL              9            -    838 977.81
NODE          Bkup    NODE\StgGrp2       2    TAPEPOOL             15    309 319.03   309 319.00

Makes one think it's related to deduplication on FILEPOOL between because physical occupancy is zero.
Both pools are sequential.

 

[sgabriel62]

whats your data retention values for exchange

 

[storm9767]

I'm experiencing the same issue with TDPExchange on 6.2.3. Did you find a resolution?

 

[chad_small]

Do you have AUDITSTORAGE set to YES in the dsmserv.opt? I had it turned off by accident by an admin who was trying to cleanup the dsmserv.opt.

 

[Harry_Redl]

Hi,

what about "q auditocc NODE pooltype=primary" - as now you are querying the complete usage in TSM - all copies combined.

Harry