To be protected by the Unitrends system, the following client and instance requirements must be met:
Oracle Requirement |
Description |
---|---|
Supported Platforms |
See the Unitrends Compatibility and Interoperability Matrix for a list of supported Windows, Linux, and Solaris platforms. |
Client Registration |
The Oracle server must be registered to the Unitrends System as described in To add a client to the Unitrends appliance. |
Credentials |
To perform backups and restores, system (Windows, Linux, or Solaris) user credentials are required, and the system user must be a member of the ora_dba group. For details, see Oracle credential considerations. |
Supported Instances |
|
Oracle on Windows |
• Must be version 12c or 11g. • Must be online and in open status. Statuses such as MOUNTED, NOT MOUNTED, and SHUTDOWN are not supported. • Must be running and configured in ARCHIVELOG mode. • Each Oracle SID on a client must be unique. • A given Oracle database can be protected by one Unitrends system only and cannot be included in an Oracle Enterprise Manager schedule. • Oracle Database instances must be deployed using the File System storage type. Other configurations are not supported. • Oracle Database must be configured as single instances. Clustered configurations, such as Oracle single-server Real Application Clusters (RAC) and Oracle multi-server RACs, are not supported. |
Oracle on Linux |
• Must be version 12c or 11g • A Samba client for Linux must be installed. • Must be online and in open status. Modes such as MOUNTED, NOT MOUNTED, and SHUTDOWN are not supported. • Must be running and configured in ARCHIVELOG mode. • Each Oracle SID on a client must be unique. • A given Oracle database can be protected by one Unitrends system only and cannot be included in an Oracle Enterprise Manager schedule. • Oracle Database instances must be deployed using the File System storage type. Other configurations are not supported. • Oracle Database must be configured as single instances. Clustered configurations, such as Oracle single-server Real Application Clusters (RAC) and Oracle multi-server RACs, are not supported. |
Oracle on Solaris |
• Must be version 12c or 11g. • A Samba client for Solaris must be enabled. See KB 1298 for details. • Ensure the Solaris client has sufficient memory available. See KB 1313 for details. • Must be online and in open status. Modes such as MOUNTED, NOT MOUNTED, and SHUTDOWN are not supported. • Must be running and configured in ARCHIVELOG mode. • Full pathname to each Solaris object cannot exceed 1024 characters. For details, see KB 1564. • Each Oracle SID on a client must be unique. • A given Oracle database can be protected by one Unitrends system only and cannot be included in an Oracle Enterprise Manager schedule. • Oracle Database instances must be deployed using the File System storage type. Other configurations are not supported. • Oracle Database must be configured as single instances. Clustered configurations, such as Oracle single-server Real Application Clusters (RAC) and Oracle multi-server RACs, are not supported. |