Correct. Two policies require two sets of metadata. The latter ultimately
requires two nodes.
If you keep one node, it would require to keep *all* metadata forever
which is unnecessary (and will grow TSM server DB).

Zlatko Krastev
IT Consultant

P.S. My quick fingers made a joke on me in the last post :-O Please read
it as "whatever number of nodes".
ZK






"Rane, Yashwant" <Yrane AT KOCKW DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
21.05.2003 10:07
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        TOP for Exchange Backup Policy


Dear Gagan Singh,

I don't think we can use one nodename and have two policies on the same
data.

For example if we have following two policies for one nodename:-
Policy1=90 Days retention (for daily backup) for DATA xyz
Policy2=Nolimit  (Monthly Backup) for DATA xyz

Backup xyz monthly using policy2
Backup xyz daily using policy1

In this case when you backup xyz using policy1 the object xyz will get
rebound to policy1 and will expire objects older that 90 days.

I think we need to have two nodenames to address requirements like keeping
permanently monthly backups (Backups taken using TDP for exchange, here we
can not use backupset or archives).

Anybody with different findings?

Regards
Rane


-----Original Message-----
From: Gagan Singh Rana [mailto:gagan AT QUANTM DOT COM]
Sent: Tue, May 20, 2003 9:25 AM
Subject: Re: TOP for Exchange Backup Policy


Dear Mr. Rane

I will suggest you to create one more management class with retention as
NOLIMIT. Create
one more config file for Exchange client on the node where u bind this
management class to
the data backup using include statement. Write one more script where u
meantion
/CONFIGFILE=newfilename with cmdline command parameter pointing to this
config file.

Run regular script with default management class for that client on
regular days. Run the
alternate script (mentioned above) on month end which specifies different
configfile ==>
which in turn binds the data to management class with NOLIMIT retention
period.

Else u will definately lose onto one TDP for Mail License. Moreover the
restoration may
create confusion at times.

Hope this will help you.

Thanks and regards
Gagan Singh Rana
Tivoli Certified Consultant - IBM Tivoli Storage Manager  V5.1

"An error doesn't become a mistake until you choose to ignore it."

the Business Enterprise Solutions Team

QuantM Systems Pvt. Ltd.
79 Amrit Nagar, NDSE Part I
New Delhi - 110003

Voice : 91-11-4691575/4602217
Fax    : 91-11-4691188
Hand Phone : 91-9868091938

DISCLAIMER :
The information in this e-mail is confidential and may be legally
privileged. It is
intended SOLELY for the addressee. Access to this e-mail by anyone else is
unauthorized.
If you are NOT the intended recipient, any disclosure, copying,
distribution or any action
taken on it is prohibited and may be unlawful. Any opinions or advice
contained in this
e-mail are subject to the terms and conditions expressed in the governing
client
relationship engagement letter.
______________________________________________________________
Visit us at www.quantm.com



----- Original Message -----
From: "Rane, Yashwant" <Yrane AT KOCKW DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Tuesday, May 20, 2003 11:09 AM
Subject: TOP for Exchange Backup Policy


Hi All,

We have implemented the TDP for exchange (24 X 7 environment). TSM backup
policy set to 90
days.
But Management wants to retain monthly backups permanently.

In this case backup set and archives can not be used as it does not
support TDP for
exchange. Other solution is to use two node names for TDP backup. Use one
node name for
daily backup and other node name for monthly backup.

My question is whether these two node names will be counted as two license
in use?
What is the general practice followed to retain monthly backups
permanently.

Regards
Rane