ADSM-L

Re: [ADSM-L] [TSM] Client Options Set - A bit confuse

2009-09-17 15:46:31
Subject: Re: [ADSM-L] [TSM] Client Options Set - A bit confuse
From: Flavio Junior <billpp AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 17 Sep 2009 16:45:32 -0300
Well..
A new problem comes up to my setup..

This is how I'd setup my clientopt set:
# Client opt definitions
define clientopt oddie compression no force=yes
define clientopt oddie subdir yes force=yes
define clientopt oddie dirmc DIRETORIOS force=yes

# Includes
define clientopt oddie inclexcl "include /projetosfechados/.../*
1Ver3Anos" force=yes
define clientopt oddie inclexcl "include /arquivodigital/.../*
1Ver3Anos" force=yes

define clientopt oddie inclexcl "include /backups/* 7Ver3Anos" force=yes

define clientopt oddie inclexcl "include /backups/databases/*
14Ver3Anos" force=yes

define clientopt oddie inclexcl "include /projetos/.../* 3Anos" force=yes
define clientopt oddie inclexcl "include /plotagem/.../* 3Anos" force=yes
define clientopt oddie inclexcl "include /imagens/.../* 3Anos" force=yes
define clientopt oddie inclexcl "include /home/.../* 3Anos" force=yes
define clientopt oddie inclexcl "include /sharedadm/.../* 3Anos" force=yes
define clientopt oddie inclexcl "include /sharedprod/.../* 3Anos" force=yes

define clientopt oddie inclexcl "exclude.dir
/backups/backup_mail/mailman/" force=yes
define clientopt oddie inclexcl "exclude.dir
/backups/backup_mail/vmail/" force=yes
define clientopt oddie inclexcl "exclude.dir /.../*" force=yes
define clientopt oddie inclexcl "exclude.dir /*" force=yes
define clientopt oddie inclexcl "exclude /.../*" force=yes
define clientopt oddie inclexcl "exclude /*" force=yes

#### How client shows q inclexcl:
tsm> q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
---- --------- ------------------------------ -----------------
No exclude filespace statements defined.
Excl Directory /*                             Server
Excl Directory /.../*                         Server
Excl Directory /backups/backup_mail/vmail/    Server
Excl Directory /backups/backup_mail/mailman/  Server
Excl Directory /.../.TsmCacheDir              TSM
Exclude All       /*                             Server
Exclude All       /.../*                         Server
Include All       /sharedprod/.../*              Server
Include All       /sharedadm/.../*               Server
Include All       /home/.../*                    Server
Include All       /imagens/.../*                 Server
Include All       /plotagem/.../*                Server
Include All       /projetos/.../*                Server
Include All       /backups/databases/*           Server
Include All       /backups/*                     Server
Include All       /arquivodigital/.../*          Server
Include All       /projetosfechados/.../*        Server
No DFS include/exclude statements defined.
tsm>


####

But, when I run "dsmc incremental", ALL filesystem's is backed up or
at least create filespaces...


How can I say to TSM only backup (create filespace) for those
"includes" directories ?

I'm afraid that my schedule client task, defined as
"action=incremental" will create a FULL backup from node, that is not
the intention...


Thanks again, in advance :)

--

Flávio do Carmo Júnior aka waKKu
Florianópolis/SC - Brazil


On Thu, Sep 17, 2009 at 1:02 PM, Flavio Junior <billpp AT gmail DOT com> wrote:
> Hi Shawn..
>
> Many thanks for your explanation and that "trick" with q inclexcl from 
> client..
> It will be very helpful for my tests :)
>
> Cya.
>
> --
>
> Flávio do Carmo Júnior aka waKKu
>
> On Thu, Sep 17, 2009 at 12:19 PM, Shawn Drew
> <shawn.drew AT americas.bnpparibas DOT com> wrote:
>> As you know, it works from the bottom up.
>>
>> Once a pattern is found that matches the file. It backs up the file and
>> moves on.  All the other inclexcl lines, above it, are ignored once it
>> matches the pattern for that file.  (With the exception of "exclude.dir",
>> which is never ignored)
>>
>> As long as you have /backups/databases/* under the /backups/*  that will
>> be the first pattern that is matched for those
>> files and it will not be backed up twice.
>>
>> Remember to perform a "q inclexcl" from the client to make sure everything
>> looks as you expect.  Also remember that "q inclexcl" shows everything in
>> the "correct" order from top to bottom and combines all the
>> inclusions/exclusions from the registries, option files and server clopts.
>>
>> Regards,
>> Shawn
>> ________________________________________________
>> Shawn Drew
>>
>>
>>
>>
>>
>> Internet
>> billpp AT GMAIL DOT COM
>>
>> Sent by: ADSM-L AT VM.MARIST DOT EDU
>> 09/16/2009 06:51 PM
>> Please respond to
>> ADSM-L AT VM.MARIST DOT EDU
>>
>>
>> To
>> ADSM-L
>> cc
>>
>> Subject
>> [ADSM-L] [TSM] Client Options Set - A bit confuse
>>
>>
>>
>>
>>
>>
>> Hi folks, evening all...
>>
>> I'm trying to write my first CLIENTOPT (at server side) and i'm
>> totally confused...
>>
>> What I need is:
>> (all mgmtclass are already defined)
>>
>> /backups/backup_mail/mailman IS EXCLUDED
>> /backups/backup_mail/vmail IS EXCLUDED
>> /backups/* goes to 7Ver3Anos
>> /backups/databases/* goes to 14Ver3Anos
>>
>> I could easily write it dir by dir, but I want to understand how to
>> use "more specific" clause...
>>
>> I know that inclexcl is read from bottom to top and already read that
>> /backups/.../* would backup everyting under /backups directory...
>> But I can't find how to use it with different Mgmtclass...
>>
>> If I do:
>>
>> /backups/.../* 7Ver3Anos
>> /backups/databases/.../* 14Ver3Anos
>>
>> Will "databases" dir be backed up twice?
>> Can it be done? (I'm almost sure it can).
>>
>> Thanks in advance.
>>
>> --
>>
>> Flávio do Carmo Júnior aka waKKu
>> Florianópolis/SC - Brazil
>>
>>
>>
>> This message and any attachments (the "message") is intended solely for
>> the addressees and is confidential. If you receive this message in error,
>> please delete it and immediately notify the sender. Any use not in accord
>> with its purpose, any dissemination or disclosure, either whole or partial,
>> is prohibited except formal approval. The internet can not guarantee the
>> integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
>> not therefore be liable for the message if modified. Please note that certain
>> functions and services for BNP Paribas may be performed by BNP Paribas RCC, 
>> Inc.
>>
>