ADSM-L

Re: binding backups to different management classes

2003-03-17 03:37:12
Subject: Re: binding backups to different management classes
From: Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 17 Mar 2003 10:34:31 +0200
It is always highly recommended to use separate nodes for B/A client
(files) and TDP (application). TSM licenses are processor-based (v5.1) or
system-size (v4.2 and below) and do not depend on number of nodes over the
system.
For TDPO (RMAN) I would highly recommend to look at TDP for Oracle manual
(you can see there a separate option file is used, not one used by B/A
client).

Zlatko Krastev
IT Consultant






shekhar Dhotre <Shekhar.Dhotre AT LENDLEASEREI DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
17.03.2003 04:21
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: binding backups to different management classes


Zlatko,
We have Oracle DB and other Data on same node (APT75) . We are backing up
all file systems (excluding Oracle DB) using DAILYMGMT management class. I
am in process of    TDP/RMAN configuration   for Oracle DB backups.
Configuration requires Retain Extra Versions=0
 And Retain Only Version=0, so I created new management class  (TDPMGMT)
with Retain extra Versions=0 and Retain Only Version=0 as I cannot change
these values in DAILYMGMT class. DAILYMGMT class is
used for Daily backups   values for Retain Extra Versions=180 and Retain
Only Version=180.

How TDPMGMT class can be used for TDP/RMAN configuration?  Is there any
other way to accomplish this?

Thanks
SD









Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/16/2003 07:43 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To

ADSM-L AT VM.MARIST DOT EDU
cc





Subject
Re: binding backups to different management classes






You are not binding a whole node. You can bind a set of files to a class,
another set to different class, etc.
If bindings are not defined through include options (dsm.sys for UNIX,
dsm.opt from Windows, cloptset for both) it is equivalent to binding of
everything to the default class.
Only one class can be default in a policy domain and node can belong to
only one domain at any particular moment (later another class can become
default or node can be moved to another domain).

Thus you have two options:
- bind everything to a particular class
        -- for UNIX - "include  /.../*  <class name>"
        -- for Windows - "include ?:\...\*      <class name>"
- move the node to a domain in which the class is default - "upd no <node
name> dom=<domain name>"

Zlatko Krastev
IT Consultant






shekhar Dhotre <Shekhar.Dhotre AT LENDLEASEREI DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
17.03.2003 01:51
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: binding backups to different management
classes


let me correct my question : How I can  bind a node with different
management class .

...