Backing Up Oracle - Computing at Cornell

copy mgmtclass API_DOMAIN API_POLICY API_MGMTCLASS DSKPOOL1
update copygroup API_DOMAIN API_POLICY DSKPOOL1 dest=API_DISK
activate policy API_DOMAIN API_POLICYT
In the tdpo.opt file, we added TDPO_MGMT_CLASS2 DSKPOOL1.
The RMAN cmdfile looks like this:
Because of the duplex option, the format parameter has to include the %c
string, which specifies the copy number of the backup piece within a set of
duplexed backup pieces.
As shown next, we listed the objects in TSM and RMAN and deleted them
with the following steps:
Established an RMAN session and allocated a maintenance channel.
Started a TSM administrator session.
Under one backup set key, there are two different backup pieces because
of the set duplicate=2 option. The format parameter .copy%c created
names ending with .copy1 and .copy2.
In the TSM administrator session, we listed the first to TSM objects with a
SQL select command.
The next step was the change backupset 2773 delete, which marks the two
objects BERLIN/backuppiece27.backupset1.copy1 and
BERLIN/backuppiece27.backupset1.copy2 in TSM as inactive.
In the TSM administrator session, a expire inventory command was
invoked.
A new SQL select in the TSM session returned no rows.
Here is the RMAN list backup and change delete backup:
218 Backing Up Oracle using Tivoli Storage Management