1. 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.
  2. 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.

Understanding Query OCCupancy on HSM filesystem

Discussion in 'Hierarchical Storage Management' started by avv, Mar 7, 2016.

  1. avv

    avv Active Newcomer

    Joined:
    Mar 7, 2016
    Messages:
    7
    Likes Received:
    0
    Hi,

    I have the following HSM FS, which migrates data from 20TB GPFS to lto5 tapes:


    tsm: tsm-srv-a>q filesp hsm-node-a /gpfs/hsm-1

    Node Name: hsm-node-a
    Filespace Name: /gpfs/hsm-1
    FSID: 14
    Platform: Linux x86-64
    Filespace Type: GPFS
    Is Filespace Unicode?: No
    Capacity: 20,479 GB
    Pct Util: 48.9

    tsm: tsm-srv-a>q occ hsm-node-a /gpfs/hsm-1

    Node Name: hsm-node-a
    Type: Bkup
    Filespace Name: /gpfs/hsm-1
    FSID: 14
    Storage Pool Name: BCK-1
    Number of Files: 3,183,589
    Physical Space Occupied (MB): 21,560,257.28
    Logical Space Occupied (MB): 21,545,729.28

    Node Name: hsm-node-a
    Type: Bkup
    Filespace Name: /gpfs/hsm-1
    FSID: 14
    Storage Pool Name: BCK-1-COPY
    Number of Files: 3,183,587
    Physical Space Occupied (MB): 21,556,129.28
    Logical Space Occupied (MB): 21,539,937.28

    Node Name: hsm-node-a
    Type: SpMg
    Filespace Name: /gpfs/hsm-1
    FSID: 14
    Storage Pool Name: HSM-1
    Number of Files: 1,293,109
    Physical Space Occupied (MB): 12,474,465.28
    Logical Space Occupied (MB): 12,474,465.28

    Node Name: hsm-node-a
    Type: SpMg
    Filespace Name: /gpfs/hsm-1
    FSID: 14
    Storage Pool Name: HSM-1-COPY
    Number of Files: 1,293,109
    Physical Space Occupied (MB): 12,474,465.28
    Logical Space Occupied (MB): 12,474,465.28



    Due to a failure of disk array I'm restoring (dsmc restore) contents of this FS to a different disk array.
    New FS is *not* HSM-managed - it's just a regular filesystem on another linux box.

    I have already restored about 80TB of files and restore is still going.

    This value does not correspond with above output of "q occ" command - Physical/Logical Space Occupied is much smaller that 80TB.

    Can you comment on this?

    Thanks in advance!
     
  2.  
  3. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,814
    Likes Received:
    358
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    In HSM, similar files have been marked by a stub file and does not get backed up.

    Restoring in non-HSM will required similar files to be restored according to the storage location and thus will run longer and restore more files, most of which are similar ones.
     
  4. avv

    avv Active Newcomer

    Joined:
    Mar 7, 2016
    Messages:
    7
    Likes Received:
    0
    @moon-buddy,

    can you elaborate?

    Do you mean that many files can be assigned to a single stub file?

    What do you mean by "does not get backed up" ?

    Is there any way to get reliable information how many files and TBs are in fact in backup storage pool for that FS ?

    Thanks in advance.
     
: hsm, gpfs, occupancy

Share This Page