Databases Reference
In-Depth Information
The following command shows a variation of the
configure
command, where we use the
tablespace
option
with the
configure
command to specify encryption for a specific tablespace named example:
RMAN> configure encryption for tablespace example on;
tablespace EXAMPLE will be encrypted in future backup sets
new RMAN configuration parameters are successfully stored
RMAN>
When you back up the database, only the example tablespace backup will be in an encrypted form. You can disable
encryption for the tablespace example by using the following command:
RMAN> configure encryption for tablespace example off;
Tablespace EXAMPLE will not be encrypted in future backup sets
new RMAN configuration parameters are successfully stored
RMAN>
If you back up an already encrypted backup set using the backup . . . backupset command, no further encryption
takes place. Oracle simply backs up the previously encrypted backup set. However, if you use transparent data
encryption in some tables to encrypt selected columns, the encrypted RMAN backups will encrypt the already
encrypted columns again when backing up the data.
You can look up the available algorithms for encryption in the V$RMAN_ENCRYPTION_ALGORITHMS view.
You can configure the compression alogorithm to something other than the default by executing the
configure
encryption algorithm
command, as shown here:
RMAN> configure encryption algorithm 'AES256';
new RMAN configuration parameters:
CONFIGURE ENCRYPTION ALGORITHM 'AES256';
new RMAN configuration parameters are successfully stored
RMAN>
The previous command configures the compression algorithm to AES 256-bit encryption.
It's important to note the following about RMAN backup encryption:
•
RMAN backups created as a backup set can be encrypted. RMAN image copies cannot be
encrypted.
•
RMAN encrypted backups can be taken to disk. ASO licensing is required.
•
RMAN encrypted backups to tape are possible only with Oracle Secure Backup as the media
manager. ASO licensing is not required.
