Help - Delete backup

[girreis]

Hi,

How to delete a specific backup (a server) knowing that this same backup is retained in several volumes?

[domino]

delete filespace <nodename> *

Use this command to delete all file spaces for selected node from the server. Files that belong to the file space are deleted from all primary and copy storage pools.

[moon-buddy]

Is the backup a specific file, directory or an entire drive?

[girreis]

It's a backup specific example, a backup file ORACLE RMAN.

This backup is stored in, say, 15 volumes. So how do we delete this without deleting the backup volumes.

[moon-buddy]

If it is a RMAN backup, ask your DBA the specific file can be deleted from within RMAN.

[girreis]

Ok, moon-buddy!
But the actual DBA who runs it? How? Excluding the RMAN catalog?
And after that's done, must be done with TSM synchronization, correct?

But we have a complicated case, ie, the server does not exist anymore, right? His backups still exist and are in various volumes but how can we delete this backup, so to speak, by specific TSM, without communicating to the DBA?

[moon-buddy]

The real scenario is that when an Oracle DB is backed up by RMAN, RMAN controls everything. TSM is just a medium.

If the backup exist in the TSM world but the physical server Oracle server is gone, RMAN can still delete the backups as long as RMAN has the DB in the RMAN catalog.

[girreis]

I realized friend!

Turns out I did what problem is occurring with the backup's former retained in TSM.
The DBA deleted an instance RMAN without even delete the files that reference the instance to the RMAN catalog as well after synchronization with TSM would make the backup's retained would be excluded from the TSM and the volumes released, correct?
Then, as the DBA deleted the instance as we do to delete the backup's retained in TSM and are associated with various volumes (remembering that the same volume can have other backup's another instance) since it is not possible to retrieve the instance in Oracle ?

[moon-buddy]

Then, for all intent, the backup in TSM is orphaned and will go to limbo.

[girreis]

So to say that there's no way to delete a situation like this anyway correct before deleting the instance was delete the files that reference the RMAN catalog for this instance, is not it?

There is no way around this?