Hi Del,

Yes it help me.

Sorry but I'm not english naturaly speaking so I need "plain" explanation... 
And your's are perfectly clear.
I already know the rebinding of incremental data's when changing the management 
class.
But, with some "naiveté" I thaught that the management binding by TSM was 
different with DP for Exchange.
In fact, what I understand is that, whatever data's are sended by the ba/client 
or a TDP or an other one, at the moment TSM manage data's with a backup 
management class, it is obvious that it will rebind them if the management 
class change.
So if, for example, it is a MQSQL backup, using TDP For MSSQL, the same 
phenomenon happend.

Thanks,

Pierre 

-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de 
Del Hoobler
Envoyé : lundi 21 mai 2007 13:52
À : ADSM-L AT VM.MARIST DOT EDU
Objet : Re: [ADSM-L] TDP Exchange

Hi Pierre,

Sorry I was not very clear the first time.
Since many people are familiar with the TSM Backup/Archive client, I was trying 
to relate the policy management of an Exchange backup with how the TSM 
Backup/Archive client handles "file-level" 
policy management. With the TSM Backup/Archive, if you back up a file with one 
management class, and then back it up again tomorrow with a different 
management class, the TSM Server will "rebind" yesterday's backup to the new 
management class. The same is true for Data Protection for Exchange FULL type 
backups. 
I hope this helps explain what I was was trying to say.

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/19/2007
08:40:25 AM:

> Thanks Del,
> 
> I didn't understand what you mean about "files" ?
> 
> Pierre
> 
> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part 
> de Del Hoobler Envoyé : vendredi 18 mai 2007 18:31 À : 
> ADSM-L AT VM.MARIST DOT EDU Objet : Re: [ADSM-L] TDP Exchange
> 
> Hi Pierre,
> 
> It is working correctly. This is the same way it works when backing up 
> "files" to the TSM Server.
> If you want to have DP/Exchange backups with different policies...
> 
> One way that many customers are doing this is to use Data Protection 
> for Exchange COPY type backups.
> You can create a separate management class for COPY type backups and 
> bind the COPY type backups to that special management class.
> (See User's Guide on how to bind COPY-type backups with the INCLUDE 
> statement in the DSM.OPT file for DP/Exchange.)
> 
> Another way is to create a separate NODENAME with different policy 
> sets and run occasional backups using that alternate NODENAME.
> 
> Thanks,
> 
> Del
> 
> ----------------------------------------------------
> 
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/18/2007
> 11:57:45 AM:
> 
> > Does anyone heard about problems concerning the binding of Exchange 
> > datas on a specific management class.
> >
> > I am having troubles to restore datas.
> >
> > We have two backup procedure, one runing on a daily basis, with a 
> > management class with 7 days retention And one other procedure, 
> > runing

> > on a week basis, with a management class with 42 days retention.
> >
> > We have a tdp exchange node for each exchange server.
> > Everything goes fine until we try to restore a server group...
> > We find only the last daily backups... And nothing else...
> >
> > Somebody tell me that, each time an exchange backup is done with a 
> > specific management class, Tsm, on his own will, rebind ALL 
> > filespaces

> > owned by the node on this specific management class, and so on, each 
> > time the management class change, tsm rebind filespaces...
> >
> > Can anyone confirm that ?
> >
> > We run with tsm 5.3, tdp exchange 5.3 and exchange server 2003
> >
> > Pierre