• 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.

Migration Requires Backup for selected GPFS only?

avv

Active Newcomer
#1
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!
 

marclant

ADSM.ORG Moderator
#2
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.
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.

include "/GPFS/gpfs2/.../*" MC-backup-NO
include "/GPFS/gpfs2/*" MC-backup-NO
The 2nd line is redundant, the first one includes that.

include "/.../*" MC-backup-YES
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.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

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: 7 23.3%
  • Keep using TSM for Spectrum Protect.

    Votes: 16 53.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 4 13.3%
  • Other (please comement)

    Votes: 3 10.0%

Forum statistics

Threads
30,889
Messages
131,422
Members
21,194
Latest member
jamesmacd40