Professional Documents
Culture Documents
Agenda
Introduction to RMAN VXBSA Architecture Oracle RMAN Agent Architecture RBI Sets and Restore View
Oracle RAC
Agent Configuration Agent Features Q&A
Symantec Confidential
Example Database
Consider following database for this presentation. ORCL TableSpace1
DataFile11 DataFile12
TableSpace2
DataFile21 DataFile22
Symantec Confidential
RMAN
RMAN implies Oracles Recovery MANager. Introduced in Oracle 8i. Ships with Oracle. Prior to that the only way to backup database was either shutdown and copy files or put Table Spaces in the backup mode and backup files (the way its done by 10.0 Oracle Agent.)
Symantec Confidential
RMAN
Out of the box RMAN can backup to disk without involving any backup products. For example, RMAN> backup database; would backup ORCL database to the configured destination lets say c:\rmandisk folder. A few files like following will be created under c:\rmandisk folder.
C:\rmandisk\aaabbb1_1 C:\rmandisk\aaabbb1_2 C:\rmandisk\aaabbb1_3 C:\rmandisk\aaabbb1_4 C:\rmandisk\aaabbb1_5 C:\rmandisk\aaabbb1_6
Symantec Confidential 5
RMAN
RMAN creates names of these files. RMAN will also add following entries in ORCLs ControlFile. aaabbb1_1 DataFile11 TableSpace1.. aaabbb1_2 DataFile11 TableSpace1.. aaabbb1_3 DataFile12 TableSpace1.. aaabbb1_4 DataFile21 TableSpace2.. aaabbb1_5 DataFile22 TableSpace2.. aaabbb1_6 DataFile22 TableSpace2..
So ControlFile stores backup history and mapping between the on disk files and logical objects (datafiles, tablespaces). In other words, ControlFile acts as RMANs catalog and RMAN uses backup history to decide which on disk files to read during restore.
Symantec Confidential 6
RMAN
Since RMAN does not have media (tape) management capabilities, it provides facilities by which 3rd party backup vendor can manage the on disk files (backup data) instead. Backup vendors to create Media Management Library ( example, orasbt.dll on Windows ) as per the proprietary RMAN specifications. In that case, instead of creating the on disk files, RMAN would load MML and send data to it instead. RMAN would still update the ControlFile in the same fashion.
Symantec Confidential
RMAN
RMAN Disk Backup data flow, RMAN c:\rmandisk\ RMAN 3rd Party MML Backup data flow, RMANorasbt.dllMedia Server(BEWS)Tape or B2D
Symantec Confidential
VXBSA
SBT
SBT makes VxBSA calls
SQLUV
SQLUV makes VxBSA calls
VxBSA Interface
Symantec Confidential
Symantec Confidential
10
Symantec Confidential
11
Symantec Confidential
12
Crete BEWS media server has substantial changes to support multi device acquisition, multiple streams, job coalescing, job logging.
Symantec Confidential
13
Symantec Confidential
14
Application Server
RAWS
FS_DoCommand
StreamCollator
NDMP control
Register
DBSB
Env (Jobcookie)
DB application
StoreJob NDMPEngine
Env (JobCookie)
Bengine
Loads VxBSA.DLL
Symantec Confidential
15
Symantec Confidential
16
Symantec Confidential
17
RMAN Catalog.
RMAN tags the data it saves with piece identifiers (example, aaabbb1_1 etc. we discussed earlier ) Thats all it gives you its up to the backup vendor to track these piece identifiers, and when a restore occurs, RMAN will request data using only these tags RMAN restore and recovery commands are always based on:
What you want to restore (i.e. whole database, just a tablespace or datafile, etc.)
Which point in time you want it recovered to (can be time or SCN)
RMAN has its own catalogs to map between the logical selection (what you want) and the physical location (piece identifier)
What this means: ANY restore/recovery operation may request data from ANY backup set that Backup Exec has stored. For this reason, the traditional backup set-driven view makes no sense for our users.
Symantec Confidential
18
Symantec Confidential
19
Symantec Confidential
20
Symantec Confidential
21
Using data from the RBI sets (within the time range), we show the selectable schema
History for datafiles is provided in the preview pane (B2) Archived log files will be shown here as well
Symantec Confidential 22
Symantec Confidential
23
Symantec Confidential
24
Symantec Confidential
25
Symantec Confidential
26
Symantec Confidential
27
Symantec Confidential
28
Symantec Confidential
29
Symantec Confidential
30
Symantec Confidential
31
Symantec Confidential
32
Symantec Confidential
34
Q&A