Considerations and Limitations

The following considerations and limitations should be taken into consideration when working with Veeam Explorer for Oracle.

General

• 32-bit Oracle running on 64-bit operating systems is not supported.
• Oracle XE on Linux is not supported.
• Oracle Real Application Clusters (RAC) are not supported.
• Veeam Explorer for Oracle operation in the standalone mode is not supported: it can be installed and launched only with Veeam backup server or with Veeam backup standalone console.

Backup

• When backing up Oracle on Linux server, application-aware processing operations may appear with Success status in the job session data, though the process of detecting Oracle on Linux system had failed (for example, due to the failure of connection to server via SSH).

Mount

• If planning to restore Oracle on Linux, consider that mount using fuse is not supported on kernel versions 4.0.0 - 4.1.33 due to its known issue. To work around this limitation, upgrade the kernel to version 4.1.37 or higher.
• If a Windows 2003 server is used for mount operations (for example, as a staging system), it requires Microsoft iSCSI Initiator service to be installed; if this service is not found, an error message like the following will be displayed:
  "ExplorerManagementService: Failed to wait for OIB mounted. MountID <ID>, Timeout <timeout> (sessionID <ID>). Microsoft sSCSI Initiator service is not installed."

Restore

• Veeam Explorer for Oracle does not support restore via PSDirect, VIX, or Sphere API.

• Database restore from the Oracle servers using Data Guard is not supported in the current version. Also, current version does not support creating transactionally-consistent backups of a standby database in case you are using Oracle Active Data Guard; only crash-consistent backups can be created in this case. However, a primary database can be backed up in a transactionally-consistent way.
• 1-Click restore to the original Oracle server from the storage snapshots is not supported, as the original server may not be detected properly in that case. So, the corresponding menu command will be unavailable for such database backup. As a work-around, you can use the Restore to another server command to start the Restore Wizard and specify the necessary target directly at its step 3.
• Restore to selected point in time and to selected transaction is not supported for replicas and backups stored to DR site by backup copy job, as well as for backups stored to cloud repository, as such repositories cannot be used as a destination for archived logs backup in current version of Veeam Backup & Replication.
• Database restore to current restore point is supported for restore points created by Veeam backup job, replication job, for VeeamZIP, as well as for imported backup and storage snapshot.
• If OS authentication on Oracle server is disabled on target, then databases with enabled ASM cannot be restored.
  If OS authentication on Oracle server is disabled on staging system, user will be unable to view the list of transaction and perform restore to selected transaction in case of database with enabled ASM.
• Database restore may fail if backed up Oracle server version and target server version have different patch levels.