> Commvault Cloud > File & Object Storage > Files

System Requirements for 1-Touch for Linux

Verify that your environment meets the system requirements for 1-Touch on Linux.

Client

Important

Use the most recent version of the operating system that is listed. The Commvault Cloud software fully supports the most recent version of an operating system, until the vendor ends support. More recent versions of the Commvault Cloud software might not install on operating systems that are not supported by the vendor anymore. For information about the support lifecycle of an operating system, contact the vendor.

AlmaLinux

  • AlmaLinux 9.4 with glibc 2.34.x

  • AlmaLinux 9.3 with glibc 2.34.x

  • AlmaLinux 9.2 with glibc 2.34.x

  • AlmaLinux 9.1 with glibc 2.34.x

  • AlmaLinux 9.0 with glibc 2.34.x

Debian

  • Debian 12.0 with kernel 6.1.0-26

  • Debian 11.0 with kernel 5.10.0-33

  • Debian 10.0 with kernel 4.19.118-2

  • Debian 9.0 with kernel 4.9.0-6

  • Debian 8.0 with kernel 3.16.0

Oracle Linux

  • Oracle Linux 9.5 with glibc 2.34

  • Oracle Linux 9.4 with glibc 2.34

  • Oracle Linux 9.3 with glibc 2.34

  • Oracle Linux 9.2 with glibc 2.34

  • Oracle Linux 9.1 with glibc 2.34

  • Oracle Linux 9 with glibc 2.34

  • Oracle Linux 8.x with glibc 2.28.x

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

  • Oracle Linux 6.x with glibc 2.12.x

  • Oracle Linux 5.x (Carthage) with glibc 2.5.x

Red Hat Enterprise Linux/CentOS

  • Red Hat Enterprise Linux 9.4 with glibc 2.34.x

  • Red Hat Enterprise Linux 9.3 with glibc 2.34.x

  • Red Hat Enterprise Linux 9.2 with glibc 2.34.x

  • Red Hat Enterprise Linux 9.1 with glibc 2.34.x

  • Red Hat Enterprise Linux 9.0 with glibc 2.34.x

  • Red Hat Enterprise Linux/CentOS 8.x with glibc 2.28.x

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

Rocky Linux

  • Rocky Linux 9.5 with glibc 2.34.x

  • Rocky Linux 9.4 with glibc 2.34.x

  • Rocky Linux 9.3 with glibc 2.34.x

  • Rocky Linux 9.2 with glibc 2.34.x

  • Rocky Linux 9.1 with glibc 2.34.x

  • Rocky Linux 9.0 with glibc 2.34.x

SuSE Linux (SLES)

  • SuSE Linux Enterprise Server 15 SP6 with glibc 2.31.x

  • SuSE Linux Enterprise Server 15 SP5 with glibc 2.31.x

  • SuSE Linux Enterprise Server 15 SP4 with glibc 2.31.x

  • SuSE Linux Enterprise Server 15 SP3 with glibc 2.31.x

  • SuSE Linux Enterprise Server 15 SP2 with glibc 2.26.x

  • SuSE Linux Enterprise Server 15 SP1 with glibc 2.26.x

  • SuSE Linux Enterprise Server 15 with glibc 2.26.x

  • SuSE Linux Enterprise Server 12 from SP2 to SP5 with glibc 2.22.x

  • SuSE Linux Enterprise Server 12 and 12 SP1 with glibc 2.19

  • SuSE Linux Enterprise Server 11 SP4 with glibc 2.11.3

  • SuSE Linux Enterprise Server 11 SP3 with glibc 2.11.3

  • SuSE Linux Enterprise Server 11 SP2 with glibc 2.11.3 and kernel 3.0.13-0.5

  • SuSE Linux Enterprise Server 11 (Initial Release/SP1/SP2/SP3/SP4) with glibc 2.9.x

Ubuntu

  • Ubuntu 24.04 LTS with glibc 2.39

  • Ubuntu 22.04 LTS with glibc 2.35

  • Ubuntu 20.04 LTS with glibc 2.31

  • Ubuntu 18.04 LTS with glibc 2.27

  • Ubuntu 16.04 LTS with glibc 2.23

  • Ubuntu 14.04 LTS with glibc 2.19

  • Ubuntu 12.04 LTS with glibc 2.15

Hard Drive

5 GB of free disk space is required for the /tmp directory.

No additional disk space required beyond File System Agent disk space requirements.

Memory (RAM)

8 GB, or minimum memory requirements of the applications running on the server, whichever is greater.

Processors

Peripherals

A CD-ROM drive or the ability to boot from an ISO image file is required to boot the client for recovery.

Operating System Utilities

1-Touch backups for UNIX computers require that the standard operating system utilities that are distributed with the Ubuntu and RHEL/SuSE Linux distributions. If the prerequisites for a system state (1-Touch) backup are not met, the backup job will continue to back up the file system data and report the error during the post-backup phase. This ensures that the data remains protected even when the 1-Touch phase fails.

Debian and Ubuntu

arch

e2image

last

mv

swapon

kexec

awk

echo

ldd

netstat

sync

mkfs.vfat

basename

egrep

ln

openvt

tail

mkfs.xfs

bash

eject

locale

parted

tar

cat

env

ls

passwd

tee

chgrp

expr

lsmod

pidof

test

chmod

false

lspci

ping

time

chown

fdisk

lvdisplay

ping6

top

chroot

fgrep

lvm

ps

touch

chvt

file

lvmdiskscan

pvcreate

tr

cksum

find

lvscan

pvdisplay

true

clear

fsck

mkdir

pvs

tset

cp

fsck.ext2

mke2fs

pvscan

tty

cpio

fsck.ext3

mkfifo

pwd

umount

cut

getopt

mkfs

reboot

uname

date

grep

mkfs.ext2

rm

uptime

dd

gunzip

mkfs.ext3

rmdir

vgcfgbackup

depmod

gzip

mkinitramfs

rmmod

vgcfgrestore

df

head

mkswap

route

vgchange

diff

host

modinfo

sdiff

vgcreate

dir

hostname

modprobe

sed

vgdisplay

dirname

ifconfig

mknod

sleep

vi

dmesg

insmod

mktemp

stty

whereis

du

kill

more

su

which

e2fsck

killall

mount

swapoff

zcat

Oracle Linux, CentOS, RHEL, and SuSE Linux

arch

echo

last

mv

sync

awk

egrep

ldd

netstat

tail

basename

eject

ln

openvt

tar

bash

env

locale

parted

tee

cat

expr

ls

passwd

test

chgrp

false

lsmod

pidof

time

chmod

fdisk

lspci

ping

top

chown

fgrep

lvcreate

ping6

touch

chroot

file

lvdisplay

ps

tr

chvt

find

lvm

pvcreate

true

cksum

fsck

lvmdiskscan

pvdisplay

tset

clear

fsck.ext2

lvscan

pvs

tty

cp

fsck.ext3

mkdir

pvscan

umount

cpio

gawk

mke2fs

pwd

uname

cut

getopt

mkfifo

reboot

uptime

date

grep

mkfs

rm

dd

grub or grub2

mkfs.ext2

rmdir

vgcfgbackup

depmod

gunzip

mkfs.ext3

rmmod

vgcfgrestore

df

gzip

mkinitrd | dracut

route

vgchange

diff

head

mkswap

sdiff

vgcreate

dir

host

modinfo

sed

vgdisplay

dirname

hostname

modprobe

sleep

vi

dmesg

ifconfig

mknod

stty

whereis

du

insmod

mktemp

su

which

e2fsck

kill

more

swapoff

zcat

e2image

killall

mount

swapon

Driver Modules

The usb-storage module must not be blocked from the system.

Bootloader

  • Only BIOS is supported

  • Support for UEFI is limited. UEFI secure boot is not supported.

File System and Volume Managers

  • Linux Logical Volume Manager (LVM) Version 2: Unencrypted LVMs are supported. Thin volumes are not supported.

  • B-tree File System (Btrfs): Only 1-Touch recovery on similar systems is supported.

  • Second Extended File System (ext2)

  • Third Extended File System (ext3)

  • Fourth Extended File System (ext4)

  • Reiser File System (reiserfs)

  • XFS

Note

Mount and back up the snapshot data as snapshot volumes are not recovered as part of the 1-touch recovery.

Virtual Machines

  • VMware

  • Kernel-based VM for Linux (KVM)

Client

  • You need an additional computer to create bootable media from the backup. This computer can be the same computer or a different one with an Intel Pentium, x64, or a compatible processor.

  • iSCSI disks are not supported for 1-Touch. These disks need to be manually unselected during interactive restores if any iSCSI disks are backed up.

  • SAN disks are supported for 1-Touch recovery operations.

  • Loop devices are not supported for 1-Touch, and they are not included in 1-Touch backups.

  • 1-Touch recovery operations support native Linux multipathing. Vendor-specific multipath implementations are not supported.

  • For VMware ESX 6 or more recent versions, set the Virtual Machine compatibility to ESXi 5.5 and later (VM version 10) during the creation of the virtual machine.

  • Itanium (IA64) processor is not supported.

  • FCoE (Fibre Channel over Ethernet) is not supported.

  • 1-Touch recovery operations are supported on clients with Linux kernel executable in vmlinuz-* format.

  • 1-Touch recovery operations are supported for LUKS-encrypted disks with LUKS version 1.6.4 or more recent versions. After the first phase, provide the passkey for encrypted disks in plain format by entering the following command on an alternate terminal:

    create /tmp/override/cryptFile.key

    where the cryptFile.key format is:

    encrypted_disk_name p passkey_in_plain_format

    Note

    Entries for LUKS-encrypted partitions and LV's will be excluded from the final fstab.

    Example

    For an encrypted disk /dev/sdb1 opened as luks1 during backup, the key file must be in the following format:

    /dev/mapper/luks1 p passkey

    Note

    • 1-Touch restore for LUKS encrypted device is only supported when encryption is done using passphrase.

    • To open multiple devices, add an entry for each device on a new line.

  • Booting a HPE ProLiant DL380 Gen10 hardware with a 1-Touch ISO file attached via iLO fails. Use a different method to attach the ISO.

  • Booting the destination machine from a 1-Touch ISO file on a bootable USB is not supported.

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