content_image/998748.jpg
## Tivoli Storage Manager for ERP for Oracle using BACKINT 

Using this feature, you can perform the traditional Oracle online backup with automation provided by BACKINT . Figure 20-10 shows the data interface between Oracle Databases and Tivoli Storage Manager for ERP for Oracle using the BACKINT  interface. 

<img src='content_image/998748.jpg'>

The backup proceeds as follows: 

1. BR*Tools takes control. 

2. BRBACKUP  calls the Tivoli Storage Manager for ERP by using BACKINT . 

3. BACKINT  changes the table spaces to backup mode with the following command: alter tablespace <tablespace name> begin backup 

4. BACKINT  using Tivoli Storage Manager for ERP reads all the data files and saves them to Tivoli Storage Manager server. 

5. BR*Tools updates the catalog with information about the backed up data file. 

Logs:  BR*Tools logs are stored in the /oracle/<SID>/saparch  directory. 

BRBACKUP  automatically backs up the logs and profiles after every backup operation. In the case of bare metal restore or disaster recovery, logs and profiles must be restored to enable BR*Tools to restore data files. The process can be simplified if the logs and profiles are backed up by a Tivoli Storage Manager backup archive client during the file system backup. 

Using this method, the chosen data files are sent to Tivoli Storage Manager one by one. No compression or block checking is performed at this level. 

When a database is in backup mode, the amount of redo logs that are written to disk increases because Oracle writes the entire dirty block to the disk, not just the updated data. In some cases, when the backup routine fails for any reason, the data file remains in active backup mode, which can cause some performance effect and additional I/O to the disk. 

