Three types of Oracle Rman backup encryption policies

Source: Internet
Author: User

CONFIGURE encryption for DATABASE OFF; # Default
CONFIGURE encryption algorithm ' AES128 '; # Default

Three strategies for Rman backup security are password security, Oracle Wallet security, and hybrid encryption security
Rman> show encryption for database;

The RMAN configuration parameters for the database db_unique_name for newtest are:
CONFIGURE encryption for DATABASE OFF; # Default

Rman> Show encryption algorithm;

The RMAN configuration parameters for the database db_unique_name for newtest are:
CONFIGURE encryption algorithm ' AES128 '; # Default

The default Rman is not enabled by the encryption mechanism. Encryption problem must follow the encryption algorithm, the default encryption algorithm is AES128. Viewing the view v$rman_encryption_algorithms, you can see the encryption algorithms that are currently available.

Rman> select * from V$rman_encryption_algorithms;

algorithm_id algorithm_name

AlgorithmDESCRIPTION is RES

CON_ID
       1 AES128

AES 128-bit Key YES NO
0

       2 AES192

AES 192-bit Key No No
0

       3 AES256

AES 256-bit Key No No
0
Using password encryption, first set the password using the Set encryption command.
Rman> set encryption on identified by ' Test ' only
2>;

Executing command: SET encryption

Rman> show encryption for database;

The RMAN configuration parameters for the database db_unique_name for newtest are:
CONFIGURE encryption for DATABASE OFF; # Default

Rman> backup Database plus archivelog;

Start with backup at May-February-18
The current log is archived
Start with backup at May-February-18
The current log is archived
Using channel Ora_disk_1
Channel Ora_disk_1: Starting archive log backup set
Channel Ora_disk_1: Specifying archive logs in the backup set
Input archive Log thread = 1 sequence = recid=155 stamp=967284487
Channel Ora_disk_1: May-February-18 Start Segment 1
Channel Ora_disk_1: Completed on May-February-18 Start Segment 1
Fragment handle = E:\RECOVERYFLASH\NEWTEST\BACKUPSET\2018_02_05\O1_MF_ANNNN_TAG20180205T100807f7hh47fm. BKP Mark = tag20180205t100807 Comment = NONE
Channel Ora_disk_1: Backup set Complete, spents: 00:00:01
In May-February-18 completed the backup

Starting from Control File and SPFILE Autobackup, located in May-February-18
Fragment handle = E:\CONTROLBACKUP\CF-C-1779551310-20180205-04 Comment = NONE
In May-February-18 completed the Control File and SPFILE autobackup
rman> shutdown immediate;

Database is down
The database has been uninstalled
Oracle instance is down

rman> startup Mount;

Connected to target database (not started)
Oracle instance is started
Database is loaded

Total system global Zone 2768240640 bytes

Fixed Size 8922760 bytes
Variable Size 704645496 bytes
Database buffers 2046820352 bytes
Redo buffers 7852032 bytes

rman> Restore Database;

Starting with restore at May-February-18
Allocated channel: Ora_disk_1
Channel ora_disk_1:sid=33 Device Type =disk

skipping data file 2; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBSEED\SYSTEM01. Dbf
skipping data file 4; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBSEED\SYSAUX01. Dbf
skipping data file 6; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBSEED\UNDOTBS01. Dbf
skipping data file 8; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\SYSTEM01. Dbf
Skipping data file 9; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\SYSAUX01. Dbf
skipping data file 10; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\UNDOTBS01. Dbf
skipping data file 11; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\USERS01. Dbf
skipping data file 40; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\SYSTEM01. Dbf
skipping data file 41; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\SYSAUX01. Dbf
skipping data file 42; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\UNDOTBS01. Dbf
skipping data file 43; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\USERS01. Dbf
skipping data file 45; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\FDA01. Dbf
Channel Ora_disk_1: Starting restore data file backup set
Channel Ora_disk_1: Specifying a data file to restore from the backup set
Channel ora_disk_1: Restore data File 00001 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\SYSTEM01. Dbf
Channel ora_disk_1: Restore data file 00003 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\SYSAUX01. Dbf
Channel ora_disk_1: Restore data file 00005 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\UNDOTBS01. Dbf
Channel ora_disk_1: Restore data file 00007 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\USERS01. Dbf
Channel Ora_disk_1: Reading backup fragment E:\RECOVERYFLASH\NEWTEST\BACKUPSET\2018_02_05\O1_MF_NNNDF_TAG20180205T100514F7hgyvz5. BKP
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE, STACK follows ===============
RMAN-00571: ===========================================================
RMAN-03002: The Restore command in 02/05/2018 10:11:52 failed
ORA-19870: Restore Backup Fragments E:\RECOVERYFLASH\NEWTEST\BACKUPSET\2018_02_05\O1_MF_NNNDF_TAG20180205T100514F7hgyvz5. Error when BKP
ORA-19913: Unable to decrypt backup
Ora-28365:wallet not open

Rman> set decryption identified by ' test ';

Executing command: SET decryption

rman> Restore Database;

Starting with restore at May-February-18
Using channel Ora_disk_1

skipping data file 2; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBSEED\SYSTEM01. Dbf
skipping data file 4; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBSEED\SYSAUX01. Dbf
skipping data file 6; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBSEED\UNDOTBS01. Dbf
skipping data file 8; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\SYSTEM01. Dbf
Skipping data file 9; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\SYSAUX01. Dbf
skipping data file 10; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\UNDOTBS01. Dbf
skipping data file 11; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\PDBTEST\USERS01. Dbf
skipping data file 40; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\SYSTEM01. Dbf
skipping data file 41; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\SYSAUX01. Dbf
skipping data file 42; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\UNDOTBS01. Dbf
skipping data file 43; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\USERS01. Dbf
skipping data file 45; Restored to file C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\CLONEPDB_PLUG\FDA01. Dbf
Channel Ora_disk_1: Starting restore data file backup set
Channel Ora_disk_1: Specifying a data file to restore from the backup set
Channel ora_disk_1: Restore data File 00001 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\SYSTEM01. Dbf
Channel ora_disk_1: Restore data file 00003 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\SYSAUX01. Dbf
Channel ora_disk_1: Restore data file 00005 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\UNDOTBS01. Dbf
Channel ora_disk_1: Restore data file 00007 to C:\APP\ADMINISTRATOR\VIRTUAL\ORADATA\NEWTEST\USERS01. Dbf
Channel Ora_disk_1: Reading backup fragment E:\RECOVERYFLASH\NEWTEST\BACKUPSET\2018_02_05\O1_MF_NNNDF_TAG20180205T100514F7hgyvz5. BKP
Channel Ora_disk_1: Fragment handle = E:\RECOVERYFLASH\NEWTEST\BACKUPSET\2018_02_05\O1_MF_NNNDF_TAG20180205T100514F7hgyvz5. BKP Mark = tag20180205t100514
Channel Ora_disk_1: restored backup Fragment 1
Channel Ora_disk_1: Restore Complete, spents: 00:01:05
In May-February-18 completed the Restore

rman> Recover database;

Starting from recover, located in May-February-18
Using channel Ora_disk_1

Starting recovery of media
Media recovery complete, spents: 00:00:01

In May-February-18 completed the Recover
rman> ALTER DATABASE open;

Processed statements

Rman> set encryption off;

Executing command: SET encryption
This strategy is relatively simple for the Rman backup collection encryption policy. In general, it is not used in the formal ops scene.

Three types of Oracle Rman backup encryption policies

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.