How to allow Oracle RMAN to backup and restore from Protector managed datastores

It is assumed that the following tasks have been performed:

The Protector Master software has been installed and licenses on a dedicated node.
The Protector Client software has been installed on all servers of the Oracle setup and the clients have been authorized on the Master.

This workflow describes the steps to follow when setting up Protectors RMAN SBT integration from scratch, so a database administrator can use Oracle RMAN to backup a database to an Ops Center Protector managed UBI datastore. For illustration this workflow will use a Gen2 Repository, however the workflow is identical with other datastore nodes like Amazon S3 or Hitachi Content Platform (HCP).

Figure. Oracle RMAN Access

Table. Oracle RMAN full access policy
Classification Type	Parameter	Value
Oracle RMAN	Allow Databases	Refer to Oracle RMAN Database Selection Wizard for details on how to allow databases access
Oracle RMAN	Deny Databases	Refer to Oracle RMAN Database Selection Wizard for details on how to deny databases access

Table.
Operation Type	Parameter	Value	Assigned Nodes
Access	Access Level	Read / Write	Repository, Amazon S3, Hitachi Content Platform(HCP)

Locate the source OS Host node in the Nodes Inventory and check that it is authorized and online.
This node represents the Protector Client installed on the Oracle server.
Create a new Oracle Database node using the Oracle Application Node Wizard and check that the node it is authorized and online.
The Oracle Database node type is grouped under Application in the Node Type Wizard. This node will be used in the dataflow to represent the Oracle Database setup to be protected.
Create a new destination node, for example a Repository, using the Repository Storage Node Wizard (see Hitachi Ops Center User's Guide) and check that it is authorized and online.
The destination nodes, like the Repository node are grouped under Storage in the Node Type Wizard (see Hitachi Ops Center User's Guide). You can direct data from multiple nodes to a single repository so there is no need to create a new repository if a suitable one already exists

If a new Repository node is being created please the default Generation 2 type.
Define a policy as shown in the table above using the Policy Wizard (see Hitachi Ops Center User's Guide), Oracle RMAN Classification Wizard and the Access Operation Wizard (see Hitachi Ops Center User's Guide)
Draw a data flow as shown in the figure above, that shows the Oracle Database source node connected to the Repository destination node via a Batch mover, using the Data Flow Wizard.
Assign the Oracle-RMAN-full-access policy to the Oracle Database source node and to the repository destination node on the data flow.
Compile and activate the data flow, checking carefully that there are no errors.
Connect to the Oracle Server command line (e.g. via SSH) and use the schedulershow command line utility to retrieve the RMAN channel definition for use on this server
In RMAN create a channel using the definition provided by schedulershow and use it to backup and restore Oracle data. Please refer to the documentation provided by Oracle on how to backup and restore using an SBT channel