Hi james,

yes and no.

Rman has the possibility to define a backupset to be not needed anymore (
within its own repository ). The "Connect" or "Data Protection" agent then
sets this files to be deleted via the api. Deletion is done with the next
*SM "expire inventory". This is usually the good way keep control over the
Oracle backups. DBA defines generations to be kept.
Although you could overrule this with TSM policies. ( But your DBAs wont be
very happy ...)

herfried




james Healy <bkupmstr AT YAHOO DOT COM>@VM.MARIST.EDU> on 09.05.2000 15:22:19

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  rman interaction


I haven't dug into it yet but, my DBAs are telling me that rman interfaces
with TSM in a way where it tells it when to scratch tape and this is not
controlled by TSM policies. Can anyone tell me if this is true?


---------------------------------
Do You Yahoo!?
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.