No it doesn't, depends on what versions of TDP you have.
With TDP SQL 2.2 you can do normal versioning like you
would for plain old NT or unix files. With TDP SQL prior to 2.2
and for TDP Oracle (all versions as far as I know) you set
Verdeleted =0
Retonly=0
(Per manual)
The Oracle RMAN scripts actually do the deleting, the difficulty
depends on the verion of Oracle you have.
If you have TDP SQL earlier than 2.2, then as I recall you setup
copy group similarly (check manual) and you have to either delete
manually from client or with ver 1.1.2 they provided an autodelete
on client that you could set to run and delete versons over certain
number of days.
A last email at night answer.
David Longo
[EMAIL PROTECTED] 05/02/02 09:33PM
I'm in the process of setting up TDP for Oracle and SQL. Can someone tell me if the
co group definitions work the same for all of the TDP products.
For example. I've set up TDP for Exchange as follows...
VDE no limit
VDD no limit
REV 60
ROV 60
And I expect this to keep my exchange data available for 60 days. On day 61, my first
backup should expire (I hope). Does it work the same for TDP for Oracle and SQL?
Any help would be greatly appreciated.
Regards, Joe
MMS health-first.org made the following
annotations on 05/02/02 23:27:08
--
This message is for the named person's use only. It may contain confidential,
proprietary, or legally privileged information. No confidentiality or privilege is
waived or lost by any mistransmission. If you receive this message in error, please
immediately delete it and all copies of it from your system, destroy any hard copies
of it, and notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended
recipient. Health First reserves the right to monitor all e-mail communications
through its networks. Any views or opinions expressed in this message are solely
those of the individual sender, except (1) where the message states such views or
opinions are on behalf of a particular entity; and (2) the sender is authorized by
the entity to give such views or opinions.
==