Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Oracle Administrator's Guide
  3. Appendix A. Deduplication best practices
  4. Editing the RMAN script and configuring NetBackup for Oracle for a proxy copy backup
NetBackup™ for Oracle Administrator's Guide

Editing the RMAN script and configuring NetBackup for Oracle for a proxy copy backup

The following procedure explains how to edit the RMAN script on the client.

To edit the RMAN script

  1. On the client computer that hosts the Oracle database, open the RMAN backup script in a text editor, and make the following edits:
    • Add PROXY to the list of commands that backs up the data files.

      Example RMAN script after editing:

      BACKUP
      FORMAT 'bk_u%u_s%s_p%p_t%t'
      PROXY
      DATABASE;
    • Specify the NB_ORA_PC_STREAMS parameter in the database backup script. The NB_ORA_PC_STREAMS variable controls the number of proxy copy backup streams to be started. By default, the agent initiates one backup job for all files. If the RMAN send command passes NB_ORA_PC_STREAMS, NetBackup for Oracle splits the files into the number of groups that are specified by the variable based on the file size. The agent attempts to create streams of equal size and determines the number of processes that run to perform the backup.

    For an example that shows an edited backup script, see the following:

    See Example RMAN script for a proxy copy backup.

  2. Disable Oracle's optimization and encryption for the duration of the database backup.

    By default, Oracle disables optimization and encryption. If the optimization and encryption are enabled, run the following RMAN commands from the command line to disable optimization and encryption:

    RMAN> CONFIGURE BACKUP OPTIMIZATION OFF; 
    RMAN> CONFIGURE ENCRYPTION FOR DATABASE OFF;

    If your site requires encryption, you can specify encryption in the NetBackup for Oracle backup policy.

  3. Disable Oracle's compression for the duration of the database backup.

    By default, Oracle disables compression. If compression is enabled, Oracle compresses unused sections in streams, and the result is unpredictable deduplication rates. If compression is enabled, run the following RMAN command from the command line to disable compression:

    RMAN> CONFIGURE DEVICE TYPE SBT_TAPE BACKUP TYPE TO BACKUPSET;

    If your site requires compression, you can specify compression in the NetBackup for Oracle backup policy.

  4. Configure a NetBackup for Oracle policy.

    If you want to compress or encrypt the backup, enable compression and encryption in the NetBackup pd.conf file.

    Run a full database backup as soon as you can. You can perform incremental backups until the full backup can be run.

    Note:

    Make sure that Oracle optimization, encryption, and compression are disabled for the entirety of the database backup. Also, make sure to check specifications outside of the RMAN backup script.

Feedback

Was this page helpful?
Previous

Example RMAN script for a stream-based backup

Next

Example RMAN script for a proxy copy backup

Feedback

Was this page helpful?