Oracle Database 12c available for download :

p=284 4 en-cumulative-and-differential-backup/ RMAN differential Incremental and Cumulative Backups an overview: =-----------------------------------------------------------------= http://www.o

There will be always a misconception about Incremental Backups of RMAN between l evel 0 and level 1. Level 0 backups are base level backups which are base for future incremental bac kups, where as full db backup can not be used for incremental backup strategy. Level 1 backups are incremental backups either on top of level 0 or level 1 back ups , Level 1 backups can be differential or cumulative. differential means rman will backup only the changed blocks from last level 1 ba ckup or level 0 but when it is cumulative it backs up the entire changed blocks since the last level 0. Differential level 1 RMAN Incremental Backups The following command performs a level 1 differential incremental backup of the database: RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE; The following command performs a cumulative level 1 incremental backup of the da tabase: RMAN> BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE; # blocks changed since lev el 0

RMAN Incremental Backups difference between cumulative and differential ! ---------------------------------------------------------------------------oracle incremental backups. basically in incremental backups, we have two differ ent types, one is differential and the other one is cumulative. Generally we do a level 0 backup in the weekends and level 1 incremental(differe ntial or cumulative) during the weekdays. level 0 incremental backup will backup all the changes in the datbase right from the creation oracle incremental level 1 differential backup will backup those blocks from the previous level 0 or level 1 backup (differential). the syntax for this is as below RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE; oracle incremental level 1 cumulative backup will backup all the changes from th e previous level 0 backup (cumulative)

it you loose the required flashback logs then almost the Restore point b ecomes using the following syntax .Lets assume that y our FRA size is 20GB. it keeps that till the init para meter flashback_retetion period and then purges it automatically. then you can reset it to its original value. it bas ically used oracle flash back technology and db backups and archived logs. Oracle Flashback Area is no ex ception to that. you have to bear with the maintenance part of it.since it requires flashback logs. why is that? because Oracle maintains that info in a table called v$recovery_area_usage and t hough you manually delete or move logs in FRA . this v$ view holds important piece of information . you can ask . Maintaining Oracle Flashback Area Howto: -----------------------------------------Oracle has introduced Flashback Area from 10g and Now in 11g it has been improve d a lot. If you create a guaranteed Restore points then the req . what happens if i delete all my archive logs using RMAN but its full of flashbac k logs. then oracle clears all flashba ck logs. when you enjoy sophisticated technologies. in real terms you cant tell oracle to delete flashback logs. means when it reaches the full space in FRA oracle automatically deletes these f lashback logs and clears up the space. ------------------------------------------------In Oracle 11g . and you take nightly archive log backups and clear the arc hivelogs nightly. if you use RMAN to backup and delete or delete then only the space is released. its not reflected Practically. still you can trick oracle think that the space is reached by setting the init p arameter DB_RECOVERY_FILE_DEST_SIZE to null. Oracle Restore Points in 11gR2-RMAN New Features. you c an name it anything you want when you backup with RMAN . what about flashback logs. you should be aware of the fact if you dont clear FRA then the database will bec ome stale(no user cant login in db except sys and system) okay now comes the next trickiest part. As a traditional DBA you may think that deleting manually or moving the archive logs to other location will free up the space. but its not the case. well the space used by oracle flashback logs will be re used automatical ly.Flashback Area contains both archive logs and flashback logs(use d for flashbacking the db and for other flashback operations). it depends upon how big is your flashback area(Recovery Area).a new feature in RMAN is introduced called Restore points.speed of backup and recovery time. SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE= .it simplifies the proces s of recovery and cloning of oracle database. # blocks changed since lev el 0 To decide whether to go for cumulative or differential depends upon the disk spa ce.yo u cant keep it for long. what happens if the db does more transactions in one days and fills up the FRA? Big question?.To overcome this you should create a bit advanced Restore point(G uaranteed Restore point). as how much % what is stored in FRA.the syntax for the above is below RMAN> BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE.

PADDR and CLIENT_INFO like rman channel=% . zonecfg:vtest1> exit . p2. p1. set lines 120 column sid format 9999 column spid format 99999 column client_info format a25 column event format a30 column secs format 9999 SELECT SID. create: Using system default template SYSdefault zonecfg:vtest1> set zonepath=/export/zones/vtest1 zonecfg:vtest1> set autoboot=true zonecfg:vtest1> set bootargs= -m verbose zonecfg:vtest1> verify zonecfg:vtest1> commit. How to create zones in Solaris 11 and manage?: =---------------------------------------------= From Solaris 10 . you need to use Oracle s online repo or have to setup a enterprise repository with in your network .uired flashback logs are preserved till you manually delete it. zonecfg:testzone> create root@oratst1>zfcfg -z vtest1 zonecfg:vtest1>create vtest1: No such zone configured Use create to begin configuring a new zone. I have done a quick test with the features which I have given below. SPID. b ut zones are more fast and manageable than traditional lpar s and vm s . p3 FROM V$PROCESS p. START_TIME. V$SESSION s WHERE p.zoning works effectively and using zones we can reduce the hardware footprint . this is similar to LPARs in AIX .ADDR = s. event. create the zone configuration first using zonecfg:=============================================== root@global:~# zonecfg -z vtest1 testzone: No such zone configured Use create to begin configuring a new zone.TOTALWORK.zoning has been introduced . sofar. (sofar/totalwork) * 100 done. CLIENT_INFO. Lets see ho w to create zones and administer it. sysdate + TIME_REMAINING/3600/24 end_at from v$session_longops where totalwork > sofar AND opname NOT LIKE %aggregate% AND opname like RMAN% . Find how long the RMAN job will run: -----------------------------------use the following sql to find how long the RMAN job will run alter session set nls_date_format= dd/mm/yy hh24:mi:ss . select SID. seconds_in_wait secs.

388 seconds.install root@oratst1:~# ======================================================= . Done: Installation completed in 2866.root@oratst1:~# dladm show-link LINK CLASS MTU STATE OVER net0 phys 1500 up root@oratst1:~# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / solaris shared testzone configured /export/zones/testzone solaris excl vtest1 configured /export/zones/vtest1 solaris excl now start the installation:======================================================= root@oratst1:~# zoneadm -z vtest1 install The following ZFS file system(s) have been created: rpool/export/zones/vtest1 Progress being logged to /var/log/zones/zoneadm.xml.install Image: Preparing at /export/zones/vtest1/root.vtest1.vtest1. Log saved in non-global zone as /export/zones/vtest1/root/var/log/zones/zoneadm. Next Steps: Boot the zone.2/222.20131103T135204Z.9BaaYe SC Profile: /usr/share/auto_install/sc_profiles/enable_sci. AI Manifest: /tmp/manifest.xml Zonename: vtest1 Installation: Starting Creating IPS image Startup linked: 1/1 done Installing packages from: solaris origin: http://localhost:1008/solaris/1f27c7f999901463e7d6e1ae5a56a35ddd08f9eb/ DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 183/183 33556/33556 222.2 123k/s PHASE ITEMS Installing new actions 46825/46825 Updating package state database Done Updating image state Done Creating fast lookup database Done Installation: Succeeded Note: Man pages can be obtained by installing pkg:/system/manual done. then log into the zone console (zlogin -C) to complete the configuration process. 20131103T135204Z.