RMAN Backup Compressions tested in our Test ENV

-
RMAN Backup Compressions

The compression levels are BASIC, HIGH, MEDIUM and LOW

To use this option, we can run the following RMAN commands

RMAN> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
followed by ..

RMAN> CONFIGURE COMPRESSION ALGORITHM ‘BASIC’;   -Default by Oracle
or

RMAN> CONFIGURE COMPRESSION ALGORITHM ‘HIGH’;
or

RMAN> CONFIGURE COMPRESSION ALGORITHM ‘MEDIUM’;
or

RMAN> CONFIGURE COMPRESSION ALGORITHM ‘LOW’;

Tests carried out our Etick - Test Database & Verified. However, it should be noted that use of

 LOW, MEDIUM and HIGH, The backup set size and backup duration are shown below.
Compression Level ‘Basic’

backupset size: 327 M
time: 56 sec

 Compression Level ‘HIGH’
backupset size: 266 M
time: 3 mins

 Compression Level ‘Medium’
backupset size: 346 M
time:  35 sec

 Compression Level ‘Low’
backupset size: 418 M
time: 15 sec

 To summaries’ we can conclude:

LOW – corresponds to LZO (11gR2) – smallest compression ratio, fastest

MEDIUM – corresponds to ZLIB (11gR1) – good compression ratio, slower than LOW

HIGH – corresponds to unmodified BZIP2 (11gR2) – highest compression ratio, slowest

BASIC (which is free) – corresponds to BZIP2 (10g style compression) – compression ratio in the range of MEDIUM, but slower

 To verify the time taken by backup & size etc

sqlplus>desc v$backup_files


===============Hence Refer my test example in future =================

Comments

Post a Comment

Popular posts from this blog

ORA-01110: data file 1: '/oradata/datafiles/system01.dbf'

-
ORA-01110: data file 1: '/oradata/datafiles/system01.dbf' Error occur while restoring the database from the backup of RMAN RMAN> alter database open resetlogs; using target database control file instead of recovery catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of alter db command at 09/03/2017 16:05:14 ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/oradata/datafiles/system01.dbf' To resolve this error fallow the below procedure – Hopefully you will succeed If you’re primary database is flashback & it has the standby – Fallow below procedure RMAN> run { 2> recover database; 3> } ORA-00283: recovery session canceled due to errors RMAN-11003: failure during parse/execution of SQL statement: alter datab
Read more

Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4)

-
Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4) Export on 12c (12.1.0.2)   – Tested in our env : 10.20.0.82 ==================== SQL> select instance_name,version from v$instance; INSTANCE_NAME    VERSION ---------------- ----------------- ora12c           12.1.0.2.0 SQL> conn sys/sys as sysdba Connected. SQL> conn hassan/( password ); Connected. SQL> select table_name from user_tables; TABLE_NAME -------------------------------------------------------------------------------- TEST SQL> select * from test; COLUMN1              NAME -------------------- -------------------- 1                    abc 2                    xyz [oracle@ora12c u02]$ mkdir dump [oracle@ora12c u02]$ chmod -R 777 dump/ [oracle@ora12c u02]$ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Wed Jan 25 16:22:46 2017 Copyright (c) 1982, 2014, Oracle.  All
Read more

Solutions: error while starting of Oracle Single instance ASM Database

-
1 st – Starting ASM [root@asmdb ~]#su - grid [grid@asmdb ~]$ asmcmd Connected to an idle instance ASMCMD> ls ASMCMD-08102: no connection to ASM; command requires ASM to run ASMCMD> [grid@asmdb ~]$ sqlplus / as sysasm SQL*Plus: Release 11.2.0.4.0 Production on Mon Jan 23 17:44:30 2017 Copyright (c) 1982, 2013, Oracle.  All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Automatic Storage Management option SQL> conn / as sysasm Connected to an idle instance SQL> startup ORA-01078: failure in processing system parameters ORA-29701: unable to connect to Cluster Synchronization Service SQL> exit Disconnected 2nd : Starting DB [oracle@asmdb ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Mon Jan 23 17:15:15 2017 Copyright (c) 1982, 2013, Oracle.  All rights reserved. Connected to an idle instance. SQL> startup ORACLE instance started. Total System Gl
Read more