Oracle backup requirements

Consider the following when protecting Oracle data:

     The Unitrends agent with Oracle supports full backups and level 1 incremental backups. The incremental forever backup strategy is not supported.

     Free space equivalent to twice the size of the backup is required on the remote share for backup processing. If adequate space is not available, the backup will fail.

     A given Oracle database can be protected by one Unitrends system only, and it cannot be included in an Oracle Enterprise Manager schedule.

     Only one backup or restore operation per Oracle instance can run at any given time.

     For a given database, any backups initiated while a restore is in progress will fail. Once the restore completes, backups can be run for the given database.

     For a given database, any restores initiated while a backup is in progress will fail. Once the backup completes, restores can be run for the given database.

     For a given database, any backups initiated while a backup is in progress will fail.

     Windows Instant Recovery is not supported for Oracle on Windows environments.

     Running the Oracle database in ARCHIVELOG mode enables archiving (backup) of the Oracle redo log which guarantees you can recover all committed transactions and also enables Unitrends to back up the database while it is open and in normal system use. Archived redo log files are deleted from Oracle each time a Unitrends full backup completes successfully. This keeps the logs from overrunning tablespace.

     For Oracle on Solaris, the full pathname to each Solaris object cannot exceed 1024 characters. For details, see KB 1564.

     For Oracle on Linux, additional setup is required to use the incremental forever backup strategy. For details, see KB 1592.