The following requirements are for the Sybase Agent:
Application/Operating System |
Architecture |
|
Sybase Adaptive Server Enterprise 16.0 SP03 PL07 and later on: |
||
Linux |
Red Hat Enterprise Linux 8.x |
x86, x64 or compatible processors |
Windows |
Microsoft Windows Server 2019 Editions |
All Windows-compatible processors supported |
SAP Adaptive Server Enterprise 16.0, Sybase ASE 15.7/15.5/15.0.3 64-bit on: |
||
AIX |
AIX 7.2 64-bit |
Power PC (Includes IBM System p) |
AIX 7.1 64-bit |
Power PC (Includes IBM System p) |
|
AIX 6.1 TL 02 SP00 64-bit or higher |
Power PC (Includes IBM System p) |
|
HP-UX |
HP-UX 11i v3 (11.31) |
Itanium |
Linux |
Red Hat Enterprise Linux/CentOS |
|
Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x |
x86, x64 or compatible processors |
|
Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x |
x86, x64 or compatible processors |
|
Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x |
x86, x64,or compatible processors |
|
SuSE Linux (SLES) |
||
SuSE Linux 15.x with glibc 2.26.x and later |
x86, x64, Power PC or compatible processors |
|
SuSE Linux 12.x with glibc 2.19.x |
Intel Pentium, x64 or compatible processors |
|
SuSE Linux 11.x with glibc 2.9.x and later |
Intel Pentium, x64 or compatible processors |
|
SuSE Linux 11.x with glibc 2.6.x |
x64 |
|
Solaris |
Solaris 11.x |
x64, Sparc T/M series |
Solaris 10 Update 6 or equivalent |
x64, Sparc T/M series |
|
Windows |
Windows 2012 |
|
Microsoft Windows Server 2012 x64 Edition |
||
Microsoft Windows Server 2012 R2 Editions |
||
Windows 2008 |
||
Microsoft Windows Server 2008 x64 Editions* *Core Editions are not supported. |
All Windows-compatible processors supported |
|
Windows 2016 |
||
Microsoft Windows Server 2016 Editions *Nano Servers are not supported. See Considerations for Microsoft Windows Server 2016 for more information. *You must have Sybase ASE SP02 PL04 HF1 or later. |
||
Sybase ASE 15.7/15.5/15.0.X 32-bit on: |
||
Linux |
Red Hat Enterprise Linux/CentOS |
|
Red Hat Enterprise Linux/CentOS 5.x |
Intel Pentium, x64 or compatible processors |
|
SuSE Linux (SLES) |
||
SuSE Linux 12.x with glibc 2.19.x |
Intel Pentium, x64 or compatible processors |
|
SuSE Linux 11.x with glibc 2.6.x |
Intel Pentium, x64 or compatible processors |
|
SuSE Linux 10.x with glibc 2.4.x |
Intel Pentium, x64 or compatible processors |
|
Solaris |
Solaris 10 Update 6 or equivalent |
x64 |
Windows |
Windows 2012 |
|
Microsoft Windows Server 2012 R2 Editions |
||
Windows 2008 |
||
Microsoft Windows Server 2008 32-bit Editions* *Core Editions are not supported. |
Cluster Support
You can install the software on a cluster, if clustering is supported by the operating system. For information about supported cluster types, see Support for Cluster Configuration.
Hard Drive
2 GB of minimum disk space is required for software installation.
256 MB of free disk space is required for the job result directory.
256 MB of free disk space is required for the log directory.
Solaris Containers and Zones
You can back up and restore data in both global and non-global zones.
For a list of supported components, see Unix Virtualization.
File System Agent Requirements
-
When this software is installed, the appropriate file system agent is also installed (if it is not already installed). For system requirements for the file system agents, see the following:
The operating system must have been installed with at least the user level software option selected.
SELinux
If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.
To create an SELinux policy module, perform the following steps as user "root":
-
Create the following files in the /usr/share/selinux/devel directory:
File Name
Content of the File
<directory>/<file_name>.te
where:
<directory> is /usr/share/selinux/devel
<file_name> is the name of the UNIX file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.
For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te
The content of the file should be as follows:
policy_module(<name>,<version>)
##############################
where:
<name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.
<version> is the version of the policy module. It can be any number, such as 1.0.0.
For Example: While creating a policy module for the backup_IDA application, you can use the following content.
policy_module(backup_IDA,1.0.0)
<directory>/<file_name>.fc
where:
<directory> is /usr/share/selinux/devel
<file_name> is the name of the UNIX file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.
For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc
The content of the file should be as follows:
Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.
/opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)
/opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)
-
Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.
[root]# make backup_IDA.pp
Compiling targeted backup_IDA module
/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp
/usr/bin/checkmodule: policy configuration loaded
/usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod
Creating targeted backup_IDA.pp policy package
rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc
[root]# semodule -i backup_IDA.pp
[root]#
-
Execute the policy module. Use the following command:
[root]# restorecon -R /opt/<software installation directory>
SELinux is now configured to work with this application.
.NET Framework
.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.0 can co-exist with other versions of this software.
Microsoft Visual C++ Redistributable 2017 is Automatically Installed
Starting in Service Pack 18, Microsoft Visual C++ Redistributable 2017 (vcredist2017.exe) is automatically installed. If a computer does not have the latest Windows updates, the installation of Microsoft Visual C++ Redistributable 2017 will fail in installing Universal C Runtime.
The following Windows updates must be installed to prevent the installation failure:
KB2919355
KB2939087
KB2975061
KB2999226
Updates are not required on latest Windows operating system versions, such as Microsoft Windows 10 and Microsoft Windows Server 2016, as these versions come with the Universal C Runtime already installed.
DISCLAIMER
Certain third-party software and service releases (together, “Releases”) may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.