Then, since TSM see them all as still active, I'd guess that Backtrack is not
expiring the files.
David
>>> [EMAIL PROTECTED] 05/20/05 11:05 AM >>>
Yes, SQL-BACKTRACK is responsible for updating the status of the
uniquely name file.
>>> [EMAIL PROTECTED] 05/20/2005 10:43:53 AM >>>
In TSM for Da
Yes, SQL-BACKTRACK is responsible for updating the status of the
uniquely name file.
>>> [EMAIL PROTECTED] 05/20/2005 10:43:53 AM >>>
In TSM for Databases, each backup file has a unique name and rman is
responsible for "deleting" them, thus triggering the TSM expiration
cycle. Does Backtrack work
In TSM for Databases, each backup file has a unique name and rman is
responsible for "deleting" them, thus triggering the TSM expiration cycle.
Does Backtrack work the same way?
>>> [EMAIL PROTECTED] 05/19/05 2:34 PM >>>
Hi:
We've just discovered q peculiar problem with expiration involing the
> Hi:
> We've just discovered q peculiar problem with expiration involing the
> SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not
> appear to be expiring.
>
> The managment class rules are:
>
> DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA RETONLY DESTINATION
> SPAIX DBBKUP1
Hi:
We've just discovered q peculiar problem with expiration involing the
SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not
appear to be expiring.
The managment class rules are:
DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA
RETONLY DESTINATION
S
