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.

Migration Requires Backup for selected GPFS only?

Discussion in 'Hierarchical Storage Management' started by avv, Oct 11, 2016.

  1. avv

    avv Active Newcomer

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

    I have a HSM node with two GPFS filesystems. Both of them
    are HSM-enabled and migrate files to tapes.

    Currently I have one mgmt class and one backup copy group
    with Migration Requires Backup = YES.

    What I would like to achieve is that only gpfs1 is backuped up
    and gpfs2 not. However both filesystem should still migrate
    files to tapes.
    This means that for gpfs2 I have to have Migration Requires
    Backup = NO.

    I have constructed the following incl/excl file:
    Code:
    include "/.../*" MC-backup-YES
    include "/*"     MC-backup-YES
    
    include "/GPFS/gpfs2/.../*" MC-backup-NO
    include "/GPFS/gpfs2/*"    MC-backup-NO
    
    exclude.backup "/GPFS/gpfs2/.../*"
    exclude.backup "/GPFS/gpfs2/*"
    mgmt class MC-backup-YES is the default one.
    As I understand, incl/excl file is interpreted from bottom to top.
    TSM server/client 6.3, GPFS 3.5. Linux x86_64.

    Can you please review and comment if this is a correct
    approach?

    thanks in advance!
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,291
    Likes Received:
    329
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    What you have essentially done is exclude "/GPFS/gpfs2/*".

    You are right, it reads from the bottom up, so when TSM tries to process "/GPFS/gpfs2/*", it reads the option file from the bottom, the first hit is your exclude, so it's excluded.

    The 2nd line is redundant, the first one includes that.

    Not needed since it's the default MC.

    So you can cut that down to one line:
    Code:
    include "/GPFS/gpfs2/.../*" MC-backup-NO
    Reason for just one line:
    - Everything is included by default unless excluded.
    - Everything is bound to the default management class unless an include specifies a new one.
     
    avv likes this.
: hsm 6.3, gpfs

Share This Page