Oracle Backup Types

Backup:
Copy of Data files(oracle/SID/sapdata*) to Tape/Disk or some alternate location using third party tools like Symantec,Tivoli Storage Manager.
Offline Backup:
The Database is Shut Down and the SAP System is not available for Business Purpose.it is also called as Cold Backup.
Online backup:
The Database is Online and the SAP System is available for Business Purpose,but users may experience system slow.it is also called Hot Backup.
Whole Backup:
The backup could be offline/online but does not allow any subsequent incremental backups.it is a standalone backup.it is allowed when the backup completes with in 2 or 3 hours.
Full Backup:
The backup could be offline/online and allows subsequent incremental backups.it is also a standalone backup and allows further catalog backups.
Ex: A System with Database Size of 3TB requires 30 hours for Full backup.So it is not possible to take a Full Backup on daily Basis.So it is recommended to take a weekly full backup followed by incremental backup on daily basis.
Note: it is performed by using RMAN(oracle specific tool).
A Full backup is performed weekly(30 hours) and incremental daily(15min to 30 in) depends upon data increments.
Incremental Backup:
The Backup followed by full backup.it is only takes backup of the data incremented after the last full backup.it consumes less time to take the backup.
Partial Backup:
It is used to take the backup at tablespace level.
when backup of entire database is consuming more time then partial backup can be taken,but it could not be used for complete restore and recovery.
Redolog Backup:
It is used to take the backup of Oraarch directory to tape or disk.These are used for recovery of the database until point of time.
Possible backup in DB13(DBA Calender)
1.Whole Offline Backup
2.Whole Online Backup
3.Whole Offline Backup + Redolog Backup
4.Whole Online Backup + Redolog Backup
5.FULL Offline Backup
6.FULL Online Backup
7.FULL Offline Backup + Redolog Backup
8.FULL Online Backup + Redolog Backup
9.Offline Backup
10.Incremental Online Backup
11.Incremental Offline Backup + Redolog Backup
12.Incremental Online Backup + Redolog Backup
13.Partial Offline Backup
14.Partial Online Backup
15. Redolog backup
Note:
Brbackup is used to take the backup of the database. brarchive is used to take the backup of the redolog database. During Backup combination with redolog backup the brbackup completes the DATBASE backup and initializes the brarchive to take the redolog backup. Ex:Whole Offline+Redolog Backup:(brbackup completes and initialize brarchive)

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more