Backing up Oracle databases
IBM® Storage Protect Snapshot integrates with multiple components when you back up an Oracle database.
For volume group snapshot, refer Configuring Storwize family and SAN Volume Controller dynamic target allocation (SVCDTA).
| Snapshot backup (disk only) | Backing up to an IBM Storage Protect server | ||
|---|---|---|---|
| From production database (tape only) | Integrated with snapshot | From existing snapshot | |
| acsora -f backup | RMAN by using Data Protection for Oracle | acsora -f backup1 |
fcmcli -f tape_backup2, 3 |
Note:
|
|||
You must use the Oracle instance owner ID and go to the INSTANCE_DIR directory before you enter any backup commands. IBM Storage Protect Snapshot backs up the database control file and the database profile on the production server to the IBM Storage Protect Snapshot repository. These files are required by IBM Storage Protect Snapshot on the backup server to start the database instance and to run the offloaded backup to the IBM Storage Protect server. Furthermore, the database control file can be optionally restored during a FlashCopy® restore (profile parameter DATABASE_CONTROL_FILE_RESTORE).
By default, the IBM Storage Protect Snapshot software does not back up the transaction logs of the Oracle database. The database administrator is responsible for backing up the Oracle database transaction logs. After every full database online backup, back up the transaction logs to the IBM Storage Protect server.
The same commands can be used to back up Oracle databases that use Oracle Automatic Storage Management (ASM) and Oracle Real Application Clusters (RAC) based on Oracle ASM. An Oracle recovery catalog is required for IBM Storage Protect Snapshot backups. This recovery catalog is a requirement even if a disk only backup is requested.