ADSM-L

Re: Management Classes

2004-04-16 12:23:14
Subject: Re: Management Classes
From: Tom Kauffman <KauffmanT AT NIBCO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 16 Apr 2004 11:19:06 -0500
You may have confused us by using 'schedules' and not 'nodes' in the
original question.

My approach, for what it's worth, would be to set up a new management class
for the critical nodes and point them to a different disk and tape storage
pool. I currently have management classes for SAP/R3 production,
MS-Exchange, Other NT, AIX, and general archiving (usually Oracle
databases). And management classes for Oracle off-line redo logs (two
classes for two storage pools) and SAP archiving (seven classes with 1 thru
7 year archive retention, all aimed at the same storage pool). I've
optimized my copy pools for D/R -- we can recover SAP, MS-Exchange, and our
payroll system all at the same time with no tape contention -- because
they're on different tape copy pools.

Which, of course, required different primary storage pools, both tape and
disk. I've found it more expedient in defining storage pools to start with
the D/R requirement and work my way backward.

Tom Kauffman
NIBCO, Inc

-----Original Message-----
From: Sam Rudland [mailto:Sam.Rudland AT INGDIRECT.CO DOT UK]
Sent: Friday, April 16, 2004 2:15 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Management Classes

Thanks for your information/ideas guys. The reason behind this
requirement is a bit messy. My company has a 3584 library on site with a
3583 at our DR site. Obviously we couldn't fit all the DR media into the
3583 at one time so the plan is to put data from key nodes into a
separate tape pool so that in a DR scenario those tapes can be loaded
into the 3583 and we can do restores without having to check tapes in
and out repeatedly.

I was hoping it would be a simple option I could use on the server side
fo things. I have a little TSM knowledge but not a lot so I think we are
going to get an expert in for a couple of days to relook at our
configuration and help design a new standard to ensure we are following
best practice.

Thanks for your help again,

Sam

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Raibeck
Sent: 15 April 2004 15:54
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Management Classes

Kent, your questions are very good ones and you make legitimate points.
My intent was to provide an answer to the question that was asked, which
was how to change the MC. Even then, your points notwithstanding, that
answer does not work if uses more than one MC at a time. But then
followed on with an invitation to be more specific about what he wanted
to do, and an admonition against modifying MC's in this fashion. If that
wasn't clear, then I should have probably emphasized that point first
and more strongly.
  :-)

As you point out, there are multiple ways to deal with this sort of
thing, but rather than speculate or write at length on the topic, I
think it better to understand the real need first.
Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
Raibeck/Tucson/[email protected] Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.



Kent Monthei <Kent.J.Monthei AT GSK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/15/2004 06:43
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Management Classes






Andy, if the clients/filesystems overlap with the other schedules, won't
this lead to excessive/unintended management class rebinding?
If they don't overlap, it would make more sense to just define a new
domain.  If they do overlap, it might be safer to configure an alternate
node name for each client, for use with the special schedules - but this
can lead to timeline continuity issues that will complicate future
point-in-time restores.   Would it be safer to follow your plan, but
just
toggle the existing MC's COPYGROUP settings and do the ACTIVATE
POLICYSET, instead of toggling between two MC's?

Kent Monthei
GlaxoSmithKline




"Andrew Raibeck" <storman AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
15-Apr-2004 09:24
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: Management Classes






Why not define admin schedules that change the default management class
prior to the scheduled backup (create server macros that run ASSIGN
DEFMGMTCLASS followed by ACTIVATE POLICYSET, then schedule the macros)?

If that does not provide sufficient granularity, then it would help to
have more specific information on what you wish to do, and, just as
important, why. Normally I would recommend against flip-flopping
management classes in this fashion, at least not without knowing a lot
more about your scenario.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
Raibeck/Tucson/[email protected] Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.



Sam Rudland <Sam.Rudland AT INGDIRECT.CO DOT UK> Sent by: "ADSM: Dist Stor
Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/15/2004 06:06
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Management Classes






I have looked everywhere but been unable to find a solution to my needs.
I have am running the TSM server 5.1.8 and I have one policy domain with
several management classes. There is a default class that data goes to
but I want the data from selected schedules to go to a separate
management class, and in turn a separate tape pool. Both this and the
default MC are incremental backups.

Are there any options I should be employing the use of?

Many thanks in advance,

Sam Rudland



-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you receive
this message by mistake, you are hereby notified that any disclosure,
reproduction, distribution or use of this message is strictly
prohibited. Please inform the sender by reply transmission and delete
the message without copying or opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the files have
NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------

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