MySQL Agent: System Requirements

The following requirements are for the MySQL Agent:

MySQL Community Server Edition or Enterprise, Standard or Classic Edition - 8.0.x

Operating System

Operating System Version

Architecture

Linux

Debian

Debian 9.x

x64 or compatible processors

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 8.x

x86, x64 or compatible processors

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 7.x with glibc 2.17.x

x86, x64 or compatible processors

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 6.x with glibc 2.12.x

x86, x64 or compatible processors

SuSE Linux (SLES)

SuSE Linux 15.0

x64 or compatible processors

SuSE Linux 12.0

x64 or compatible processors

Ubuntu

x64

Ubuntu 16.04 LTS

x64 or compatible processors

Ubuntu 14.04 LTS

x64 or compatible processors

MySQL Community Server Edition or Enterprise, Standard or Classic Edition - 5.5.x, 5.6.x and 5.7.x OR

MariaDB 5.5.x, 10.0.x, 10.1.x, 10.2.x and 10.3.x

Operating System

Operating System Version

Architecture

FreeBSD

FreeBSD 10.x

x64 or compatible processors

FreeBSD 9.x

x64 or compatible processors

HP-UX

HP-UX 11i v3 (11.31)

Itanium

Linux

Asianux

Asianux 4

x64 or compatible processors

Debian

Debian 9.x

x64 or compatible processors

Debian 8.x

x64 or compatible processors

Debian 7.x

x64 or compatible processors

Debian 6.x with glibc 2.11.x

x64 or compatible processors

Debian 5.x

x64 or compatible processors

Gentoo

Gentoo release 10.1 with glibc 2.6.x

x64

NeoKylin Linux 7.4

x64

OpenSuSE

OpenSuSE 12.1 with glibc 2.14.x

x64

OpenSuSE 11.1 with glibc 2.9.x

x64

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 8.x

x86, x64 or compatible processors

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 7.x with glibc 2.17.x

x86, x64 or compatible processors

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 6.x with glibc 2.12.x

x86, x64 or compatible processors

Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 5.x with glibc 2.5.x

x86, x64 or compatible processors

Source Mage Linux

Source Mage Linux

x64

SuSE Linux (SLES)

SuSE Linux 12.0

x64, Power PC (Little endian) or compatible processors

SuSE Linux 11.x with glibc 2.9.x and later

x64, Power PC (Little endian) or compatible processors

Ubuntu

Ubuntu 9.x

x64 or compatible processors

Ubuntu 8.04

x64 or compatible processors

Ubuntu 18.04 LTS

x64 or compatible processors

Ubuntu 16.04 LTS

x64 or compatible processors

Ubuntu 14.04 LTS

x64 or compatible processors

Ubuntu 12.04 LTS

x64 or compatible processors

Ubuntu 10.04 LTS

x64 or compatible processors

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 Editions

*Core Editions not supported

Windows 2008

Microsoft Windows Server 2008 R2 Editions*

*Core Editions are not supported.

All Windows-compatible processors supported

Microsoft Windows Server 2008 32-bit and x64 Editions*

*Core Editions are not supported.

All Windows-compatible processors supported

Windows 2016

Microsoft Windows Server 2016 Editions

All Windows-compatible processors 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

Component

Space required

Software

1 GB

Job results folder

256 MB

Log folder

256 MB

Notes on Block-Level Backups

  • Block-level backups are supported only on Linux platforms.

    For supported Linux kernel version details of MySQL block-level backups, see MySQL Block-Level Backup.

  • Network File System (NFS) is not supported for MySQL block-level backups.

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

The operating system must have been installed with at least the user level software option selected.

On Ubuntu 9.x 64-bit computers, it is required that you install the libstdc++.so.5 compatibility package. To install the package, use the following command:

[root]# sudo apt-get install libstdc++5

On Ubuntu and Debian computers, it is recommended that you install the latest packages for the operating system before installing the Agent. To install the latest packages, use the following command:

[root]# apt-get upgrade

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":

  1. 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)

  2. 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]#

  3. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

Microsoft Visual C++

The following Redistributable Package is installed automatically. Note that the Redistributable Package can co-exist with other versions of this software.

Microsoft Visual C++ 2010 Redistributable Package

DISCLAIMER

Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software. Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.

Loading...