You will not have any issues with DR if you use the same nodename and same initSID.utl file when connecting with the DR machine.
Saludos / Regards Arshad Munir Sharif -----Original Message----- From: Martin Trcka [mailto:[EMAIL PROTECTED]] Sent: Tue, April 09, 2002 1:55 PM To: [EMAIL PROTECTED] Subject: Re: tdp r3 and versioning Becky, yes, it does. Data that are backed up either by brbackup or brachive are stored as archive objects in TSM database and they are deleted when eligible, thus freeing up the tapes. I don't know of any issues during disaster recovery, when using TDP versioning. The only thing that you should be aware of is either using TDP versioning (and having retain version set to nolimit or 9999) or TSM versioning only. Martin Trcka > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On > Behalf Of Davidson, Becky > Sent: Monday, April 08, 2002 9:18 PM > To: [EMAIL PROTECTED] > Subject: Re: tdp r3 and versioning > > > Does it then delete them from the TSM database and free up the tapes? Are > there any issues with doing this and disaster recovery? > thanks > Becky > > -----Original Message----- > From: Martin Trcka [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 08, 2002 3:54 AM > To: [EMAIL PROTECTED] > Subject: Re: tdp r3 and versioning > > > Becky, > yes, we use it in our environment and works exactly as designed; > SAP backup > (brbackup/brarchive) utilities manage backup IDs > and delete apropriate ones according to the option MAX_VERSIONS in an > initSID.utl file (see below). > > Martin Trcka > > <log> > ... > ..... > Versioning : enabled > Current Version : 158 > Versions to keep : 5 > Delete Versions : <= 153 > .... > .... > BKI2009I: Deleting all versions with version number <= 153 on server TSM. > BKI2003I: File O10___9C04010330_TSM@LOG2#025001 2.COPY 00153 > /oracle/O10/sparch/O10arch1_10497.db > f deleted. > BKI2003I: File O10___9C04010330_TSM@LOG1#025000 1.COPY 00153 > /oracle/O10/saparch/O10arch1_10497.db > f deleted. > BKI2003I: File O10___9C04010330_TSM@DATABASE#135007 00153 > /oracle/O10/saparch/archO10.log deleted. > BKI2003I: File O10___9C04010330_TSM@DATABASE#135006 00153 > /oracle/O10/saparch/adhqwtee.svd deleted > . > BKI2003I: File O10___9C04010330_TSM@DATABASE#135005 00153 > /oracle/O10/sapreorg/structO10.log delet > ed. > BKI2003I: File O10___9C04010330_TSM@DATABASE#135004 00153 > /oracle/O10/sapreorg/reorgO10.log delete > d. > .... > .... > </log> > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On > > Behalf Of Davidson, Becky > > Sent: Friday, April 05, 2002 5:50 PM > > To: [EMAIL PROTECTED] > > Subject: tdp r3 and versioning > > > > > > Has anyone out there used the tdp for r3 versioning instead of > expiration? > > How does it work with disaster recovery? What are the bonuses or > > detriments? > > > > Thanks > > > > Becky Davidson > > Data Manager/AIX Administrator > > EDS/Sara Lee Bakery Group > > voice: 314-259-7589 > > fax: 314-877-8589 > > email: [EMAIL PROTECTED]
