Continuous Data Protection for Oracle database

using IBM Spectrum Protect

Stay protected up to last archived transaction log by following this simple example.

It is very common to use RMAN to schedule backup of archive logs, typically once per day.

As the scheduled are performed once per day, one can loose 24 hours of data, it can even be more if the last backup is ongoing while a system failure occur, perhaps 48 hours of data.


The terminology Recovery Point Objective (RPO), refers to what are the recovery points? which also includes data loss. However, as most part of databases today has the ability to recover to almost any time between using transaction logs, it is better to refer to the maximum data loss using various recovery techniques.

With classical RMAN scheduled backups of archive logs, you can loose more data than having an integrated backup method described below here.

Integrated backup of archived transaction logs

Backing up the transaction log data immediately when a redo log file becomes full will improve the RPO, as it will send a copy of the full redo log directly to the backup server.


To integrate automatic backups of transaction logs in Oracle is simple, just follow these steps

Download and install SPFS

# rpm -i spictera*.rpm
# rpm -i spfs*.rpm


# dpkg -i spfs*.deb
# dpkg -i spictera*.deb

Configure SPFS

# vi /etc/spfs/spfs.opt

MOUNTPOINT /archivelogs
OPTIONFILE /etc/spfs/dsm.opt
OPTIONFILE /etc/spfs/dsm.opt

DATATYPE archive


# vi /opt/tivoli/tsm/client/api/bin64/dsm.sys

TCPSERVERADDRESS backup.server.com

ERRORLOGNAME /var/log/dsmerror_spfs.log

Configure Spectrum Protect


Select Stanza

# echo spfs > /etc/spfs/dsm.opt


Register the node

# dsmadmc -id=admin -password=admin “REGISTER NODE spfs secretpwd”

Save initial password

# setpassword /etc/spfs/TSM.PWD <<< secretpwd

# echo spfs > /etc/spfs/dsm.opt

# mount -t spfs /archivelogs

Mount the SPFS file system

Edit Oracle configuration file

# vi ${ORACLE_HOME}/dbs/init_${ORACLE_SID}.ora


Restart the Oracle instance

You now have an extra copy of your archived redo log files that are sent directly at each redo log switch on the Spectrum Protect backup server

Even though you still uses RMAN to backup the archive log files, it will not add extra space on the Spectrum Protect backup server if the target storage pool is a de-duplication enabled storage pool.

Restoring archive log files are no longer required, as Oracle will request restoration of archive logs automatically during the recovery process. This is true as Oracle knows about the different locations of the archive log destinations, where one of the destinations are the mount point of the SPFS file system.


This can also help to take online snapshots of Oracle databases, as you do not need to take care of the archive log backups directly during a snapshot process. This happens automatically.


You can also have add multiple Spectrum Protect target servers, in different locations. Just follow the example above. Or having the flexibility to mix media types, such as Harddisk drives, CD WORM, Cloud, NAS and Tape as a backup media.

Scroll to Top