TDP for Exchange (2.2) ?COPY backups Expiring premature

[landom]

Hi, we have

Version 2.2 TDP For Exchange

Exchange 2000

4.2.1.19 TSM Server



We run a weekly full backup, differential and logs during the week, all works,

this is kept for 28 days, 2 versions

We also run a monthly backup, type 'copy', bound via an include to a class

that should keep unlimited versions for a year (runs 1st day of each month)



The issue is, it seems that the first 'Full' backup that runs expires the 'copy' backup!



Now, to complicate the issue, this is Exchange 2000 on a cluster.



The only thing I can think of is use a dummy nodename for the 'copy' monthly

backup (we already use a seperate dsm.opt file which is the same as the

regular except for the include to bind to the MC for 1 year)



Any other thoughts, is this expected behaviour ?



Dominic

 

[Geirr]

Hi there,

I believe you've got it right. The way to do this is to use a different node-name for the copy.

What happens is that TSM rebinds the data to the management-class specified in the opt-file. Now, your weekly full runs fine, and once you do a full backup with the other management-class, it "changes" the policy for the data. Next weekend, you do a another full backup, where data is being rebound "back" to the original mgmt-class.



I've had to use a different nodename, to use different retention for the same data, and this way I have implemented a GFS-like backup system for Exchange.



Rgds.

Geirr Halvorsen