• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

incorrect auditoccupancy values (off by >1 TB)

oskie

ADSM.ORG Member
Joined
Jul 14, 2008
Messages
62
Reaction score
2
Points
0
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.

Code:
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

ADSM.ORG Senior Member
Joined
Jul 24, 2008
Messages
542
Reaction score
13
Points
0
Location
Birmingham, UK
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

ADSM.ORG Member
Joined
Jul 14, 2008
Messages
62
Reaction score
2
Points
0
Yes audit license was run minutes before the q auditocc.
Also check out this output:

Code:
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.
 

storm9767

Newcomer
Joined
Aug 3, 2011
Messages
1
Reaction score
0
Points
0
Location
NC, USA
I'm experiencing the same issue with TDPExchange on 6.2.3. Did you find a resolution?
 

chad_small

ADSM.ORG Moderator
Joined
Dec 17, 2002
Messages
2,262
Reaction score
52
Points
0
Location
Gilbert, AZ
Website
www.tsmadmin.com
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

Moderator
ADSM.ORG Moderator
Joined
Dec 29, 2003
Messages
2,295
Reaction score
140
Points
0
Location
Czech Republic
Hi,

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

Harry
 

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 22 19.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 66 58.9%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.4%
  • Other (please comement)

    Votes: 9 8.0%

Forum statistics

Threads
31,834
Messages
134,890
Members
21,794
Latest member
CALEB
Top