Two things come to mind.
Does the backup copy group for the management class to which the backups
are sent to have retain-only-version set to 0? If not, the "last good
copy" of a "file" (the active version which is inactivated when a file
is deleted from the fs) is retained for that number of days (60 by
default).
Also, my understanding of how the server operates is that when you
delete the file-version with the agent, the version gets mark inactive
(as the last active version). Later, when expiration runs, the policy
of the management class is used to determine that yes, that version
should be deleted from the database.
Cheers...
Bruce
Fred Johanson wrote:
>
> I've a user who is using the MS-SQL connect agent. Works find from a
> schedule and everything. But getting rid of old copies is a problem. the
> user a\has sat at the keyboard and done a delete according to the
> documentation, but when I do a Q OCC, the number never diminishes. (I've
> got the same problem with SQL-Backtrack, but that's for BMC.) Has anyone
> out there figured out a way to automate the deletion process that actually
> gets rid of old copies? Any help will be appreciated.
|