ADSM-L

[ADSM-L] Non-default management classes with mmbackup

2017-04-03 10:40:20
Subject: [ADSM-L] Non-default management classes with mmbackup
From: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 3 Apr 2017 14:37:59 +0000
I'm wondering if anyone has experience assigning non-default management
classes to new files via mmbackup (I know that it's not possible to rebind
existing files). Until recently, we've gotten away with just using the
policy domain default management class, but the documentation here suggests
that it should be possible to assign non-default management classes as
well:

http://www-01.ibm.com/support/docview.wss?uid=swg21699569

Unfortunately, when I've tested it, all I get is the default. For
instance, we have this rule in dsm.sys to assign all files in
/gpfs/gs1/noble in directories marked "backups" to the noble_lab
management class:

SErvername  gpfs-gs1-noble-vol3
   ...
   include /gpfs/gs1/noble/.../backups/.../* noble_lab

And I make a test file:

dd if=/dev/zero of=/gpfs/gs1/noble/vol3/backups/test7 bs=1M count=1000

I create a snapshot (noble_vol3 is in a fileset so we can manage quotas for
it):

# mmcrsnapshot gs1 noble_vol3:TSMsnap

And run mmbackup:

# mmbackup /gpfs/gs1/noble/vol3 \
        -t incremental \
        --tsm-servers gpfs-gs1-noble-vol3 \
        -N tsm_clients \
        -S TSMsnap \
        --tsm-errorlog /var/log/dsmerror-gpfs-gs1-noble-vol3.log \
        -a 4 \
        --expire-threads 4 \
        --backup-threads 4 \
        --scope inodespace

Querying the backups afterwards shows that it's in the DEFAULT management
class, not NOBLE_LAB:

# dsmc q b -se=gpfs-gs1-noble-vol3 /gpfs/gs1/noble/vol3/backups/test7
...
           Size        Backup Date                Mgmt Class           A/I File
           ----        -----------                ----------           --- ----
   104,857,600  B  04/03/2017 07:25:53             DEFAULT              A  
/gpfs/gs1/noble/vol3/backups/test7

But I know that rule is valid, because I can run "dsmc incremental" afterwards 
and thefile gets rebound:

# dsmc i -se=gpfs-gs1-noble-vol3 /gpfs/gs1/noble/vol3/backups/
...
Rebinding-->         104,857,600 /gpfs/gs1/noble/vol3/backups/test7 [Sent]

# dsmc q b -se=gpfs-gs1-noble-vol3 /gpfs/gs1/noble/vol3/backups/test7
...
           Size        Backup Date                Mgmt Class           A/I File
           ----        -----------                ----------           --- ----
   104,857,600  B  04/03/2017 06:48:24            NOBLE_LAB             A  
/gpfs/gs1/noble/vol3/backups/test7

Thanks!

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

<Prev in Thread] Current Thread [Next in Thread>