Laptop Backup (Linux): System Requirements

The following requirements are for the Laptop Backup feature running on a Linux computer:

Operating System

Operating System Version

Architecture

Linux

Amazon Linux

Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type

  • x86

  • x64

  • Compatible processors

Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type

  • x86

  • x64

  • Compatible processors

Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type

*You cannot back up and restore ACLs for Linux on ARM64 platform.

  • x86

  • x64

  • ARM64

  • Compatible processors

Asianux

Asianux 4

x64

Debian

Debian 10.x

  • x86

  • x64

  • Compatible processors

Debian 9.x

  • x86

  • x64

  • Compatible processors

Debian 8.x

  • x86

  • x64

  • Compatible processors

Debian 7.x

  • x86

  • x64

  • Compatible processors

Debian 6.x

  • x86

  • x64

  • Compatible processors

Debian 5.x

  • x86

  • x64

  • Compatible processors

EulerOS

EulerOS 2.0 SP3

x64

EulerOS 2.0 SP2

x64

Fedora

Fedora release 32 with glibc 2.31.x

  • x86

  • x64

  • Compatible processors

Fedora Release 31 with glibc 2.30.x

  • x86

  • x64

  • Compatible processors

Fedora release 30 with glibc 2.29.x

  • x86

  • x64

  • Compatible processors

Fedora release 29 with glibc 2.28.x

  • x86

  • x64

  • Compatible processors

Fedora release 28 with glibc 2.27.x

  • x86

  • x64

  • Compatible processors

Fedora release 27 with glibc 2.26.x

  • x86

  • x64

  • Compatible processors

Fedora release 26 with glibc 2.25.x

  • x86

  • x64

  • Compatible processors

Fedora release 25 with glibc 2.24.x

  • x86

  • x64

  • Compatible processors

Fedora release 24 with glibc 2.23.x

  • x86

  • x64

  • Compatible processors

Fedora release 23 with glibc 2.22.x

  • x86

  • x64

  • Compatible processors

Fedora release 22 with glibc 2.21.x

  • x86

  • x64

  • Compatible processors

Fedora release 21 with glibc 2.20.x

  • x86

  • x64

  • Compatible processors

Fedora release 20 with glibc 2.18.x

  • x86

  • x64

  • Compatible processors

Fedora release 19 with glibc 2.17.x

  • x86

  • x64

  • Compatible processors

Fedora release 18 with glibc 2.16.x

  • x86

  • x64

  • Compatible processors

Fedora release 17 with glibc 2.15.x

  • x86

  • x64

  • Compatible processors

Fedora release 16 with glibc 2.14.x

  • x86

  • x64

  • Compatible processors

Fedora release 15 with glibc 2.13.x

  • x86

  • x64

  • Compatible processors

Fedora release 14 with glibc 2.13.x

  • x86

  • x64

  • Compatible processors

Fedora release 13 with glibc 2.12.x

  • x86

  • x64

  • Compatible processors

Fedora release 12 with glibc 2.11.x

  • x86

  • x64

  • Compatible processors

Fedora release 11 with glibc 2.10.x

  • x86

  • x64

  • Compatible processors

Fedora release 10 with glibc 2.9.x

  • x86

  • x64

  • Compatible processors

Fedora release 9 with glibc 2.8.x

  • x86

  • x64

  • Compatible processors

Fedora release 8 with glibc 2.7.x

  • x86

  • x64

  • Compatible processors

Gentoo

Gentoo with glibc 2.12.x

  • x86

  • x64

  • Compatible processors

Gentoo with glibc 2.6.x

  • x86

  • x64

  • Compatible processors

Gentoo with glibc 2.9.x

  • x86

  • x64

  • Compatible processors

NeoKylin Linux

NeoKylin Linux 7.6

x64

NeoKylin Linux 7.4

x64

NeoKylin Linux 6.5

x64

OpenSuSE

OpenSuSE Leap 42.3 with glibc 2.22

  • x86

  • x64

  • Compatible processors

OpenSuSE Leap 15.x with glibc 2.26 or later

  • x86

  • x64

  • Compatible processors

OpenSuSE Tumbleweed with glibc 2.33 or later

  • x86

  • x64

  • Compatible processors

OpenSuSE 13.2 with glibc 2.19

x64

OpenSuSE 13.1 with glibc 2.18

  • x86

  • x64

  • Compatible processors

OpenSuSE 12.x with glibc 2.14 or later

  • x86

  • x64

  • Compatible processors

OpenSuSE 11.3 with glibc 2.11.x

  • x86

  • x64

  • Compatible processors

OpenSuSE 11.2 with glibc 2.10.x

  • x86

  • x64

  • Compatible processors

OpenSuSE 11.1 with glibc 2.9.x

  • x86

  • x64

  • Compatible processors

OpenSuSE 11.0 with glibc 2.8.x

  • x86

  • x64

  • Compatible processors

Oracle Linux

Oracle Linux 8.x with glibc 2.28.x

  • x64

  • Compatible processors

Oracle Linux 7.x with glibc 2.17.x or a more recent version

  • x86

  • x64

  • Compatible processors

Oracle Linux 6.x with glibc 2.12.x or a more recent version

  • x86

  • x64

  • Compatible processors

Oracle Linux 5.x with glibc 2.5.x

  • x86

  • x64

  • Compatible processors

Red Hat Enterprise Linux/CentOS

CentOS 8.x Linux with glibc 2.28.x

*You cannot back up and restore ACLs for Linux on ARM64 platform.

  • x64

  • Compatible processors

CentOS 8.x Stream with glibc 2.28.x

*You cannot back up and restore ACLs for Linux on ARM64 platform.

  • x64

  • Compatible processors

Red Hat Enterprise Linux 8.x with glibc 2.28.x

*You cannot back up and restore ACLs for Linux on ARM64 and Power PC platform.

  • x64

  • Power PC

  • ARM64

  • Compatible processors

Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x or a more recent version

*You cannot back up and restore ACLs for Linux on ARM64 and Power PC platform.

  • x86

  • x64

  • PowerPC

  • ARM64

  • Compatible processors

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

x86

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12-1.25.x or a more recent version

x64

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

  • x86

  • x64

  • PowerPC

  • Compatible processors

Rocky Linux

Rocky Linux 9.x with glibc 2.34.x

  • x64

  • Compatible processors

Rocky Linux 8.x with glibc 2.28.x

  • x64

  • Compatible processors

Scientific Linux

Scientific Linux SL 5.x with glibc 2.5.x

x64

Scientific Linux 7.x

x64

Scientific Linux 6.x

x64

Slackware

Slackware 14.0 with glibc 2.15.x

  • x86

  • x64

  • Compatible processors

Source Mage Linux

Source Mage 0.10

x86

SuSE Linux (SLES)

SuSE Linux 15 (Initial Release/SP1 and later SPs) with glibc 2.26.x and higher

  • x86

  • x64

  • PowerPC

  • Compatible processors

SuSE Linux 12 (Initial Release/SP1 and later SPs) with glibc 2.19.x or a more recent version

  • x86

  • x64

  • PowerPC

  • Compatible processors

SuSE Linux 11 (Initial Release/SP1/SP2/SP3/SP4) with glibc 2.9.x and later

Download and install the mandatory patches from the SuSE site for SLES 11 SP4 running on Power PC.

Ubuntu

Ubuntu 21.04

  • x86

  • x64

  • Compatible processors

Ubuntu 20.10

  • x86

  • x64

  • Compatible processors

Ubuntu 20.04 LTS

  • x86

  • x64

  • Compatible processors

Ubuntu 19.10

  • x86

  • x64

  • Compatible processors

Ubuntu 19.04

*You cannot back up and restore ACLs for Linux on ARM64 platform.

  • x86

  • x64

  • ARM64

  • Compatible processors

Ubuntu 18.10

  • x86

  • x64

  • Compatible processors

Ubuntu 18.04 LTS

*You cannot back up and restore ACLs for Linux on ARM64 platform.

  • x86

  • x64

  • ARM64

  • Compatible processors

Ubuntu 17.10

  • x86

  • x64

  • Compatible processors

Ubuntu 17.04

  • x86

  • x64

  • Compatible processors

Ubuntu 16.04 LTS

  • x86

  • x64

  • Compatible processors

Ubuntu 15.10

  • x86

  • x64

  • Compatible processors

Ubuntu 15.04

  • x86

  • x64

  • Compatible processors

Ubuntu 14.10

  • x86

  • x64

  • Compatible processors

Ubuntu 14.04 LTS

  • x86

  • x64

  • Compatible processors

Ubuntu 13.10

  • x86

  • x64

  • Compatible processors

Ubuntu 13.04

  • x86

  • x64

  • Compatible processors

Ubuntu 12.10

  • x86

  • x64

  • Compatible processors

Ubuntu 12.04 LTS

  • x86

  • x64

  • Compatible processors

Ubuntu 11.10

  • x86

  • x64

  • Compatible processors

Ubuntu 11.04

  • x86

  • x64

  • Compatible processors

Ubuntu 10.04 LTS

  • x86

  • x64

  • Compatible processors

Ubuntu 9.10

  • x86

  • x64

  • Compatible processors

Ubuntu 9.04

  • x86

  • x64

  • Compatible processors

Ubuntu 8.10

  • x86

  • x64

  • Compatible processors

Ubuntu 8.04

  • x86

  • x64

  • Compatible processors

Z-Linux

Linux on zSeries (System z9/z10)

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

Red Hat Enterprise Linux

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

Red Hat Enterprise Linux 8.x

Red Hat Enterprise Linux 7.5

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

Red Hat Enterprise Linux 6.x

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

Red Hat Enterprise Linux 5.x

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

SuSE Linux (SLES)

SuSE Linux 15 (Initial Release/SP1/SP2) Enterprise Server

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

SuSE Linux 12 (Initial Release/SP1/SP2/SP3/SP4/SP5) Enterprise Server

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

SuSE Linux 11 (Initial Release/SP1/SP2/SP3/SP4) Enterprise Server

  • s390x 64-bit, with 31-bit runtime libraries installed

  • s390 31-bit

Hard Drive

Component

Space required

Software

1 GB

Job results folder

5 GB

Log folder

3 GB

Miscellaneous

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.

Supported File Systems

The Laptop Backup feature supports the following file systems:

Linux File Systems That Are Supported

  • B-tree File System (Btrfs)

  • Fraunhofer FS (FhGFS or BeeGFS)

  • Extended 2 File System (ext2)

  • Extended 3 File System (ext3)

  • Extended 4 File System (ext4)

  • General Parallel File System (GPFS)

  • Global File System (GFS/GFS2)

  • GlusterFS File System (GlusterFS): Backups and restores run on the Gluster client

  • Lustre File System (Clustered File System)

  • Moose File System (MooseFS)

  • Oracle Cluster File System (OCFS2)

  • Oracle ASM Cluster File System (Oracle ACFS)

  • Panasas ActiveScale File System (PanFS)

  • Reiser File System (reiserfs)

  • VERITAS File System (VxFS)

  • VERITAS Cluster File System (VxCFS)

  • X9000 IBRIX File System (IBRIXFS) 6.x

  • 'X' File System (XFS)

Volume Managers

Volume Managers

  • Veritas Volume Manager (VxVM) 5.0 or higher

  • Logical Volume Manager (LVM)

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.

Loading...