You can create a single policy to protect multiple Oracle databases or RAC databases that are spread over multiple clients.

All databases that you want to back up must be registered with credentials. If multiple database share the same credentials, you can select the same credential for those databases.

The database administrator can use Credential management (CMS) to manage credentials and the registration of databases and RMAN catalogs, through the NetBackup web UI or the APIs. The use of the CMS provides improved security throughout the system.

You are not required to know RMAN or to write RMAN scripts. Instead, this feature automatically generates the scripts at run-time.

The job details in the Activity monitor let you view the backup summary, database state, RMAN input, and RMAN output for the OIP. The Client or display name column indicates the database that was backed up by the associated policy.

Enhanced error codes enable faster identification, troubleshooting, and correction of problems. You can easily restart a failed job.

OIP only requires automatic backup schedules for the data movement, which simplifies how retention works on the backup pieces. Application backup schedules are not needed. An archived log schedule backs up the archived redo logs within intervals of minutes.

The OIP automatically selects parameter settings at run-time that enable optimal deduplication.

An OIP can protect an Oracle database when the Oracle DBA places database backups in the share on a NetBackup appliance.

The OIP can create and maintain a full set of data file copies in the share on a NetBackup appliance. The Accelerator option is used to update the data file copies using only the changed blocks since the last full backup.

Container databases (CDB) and pluggable databases (PDB) and can be protected.