1-Touch and Virtualize Me for Linux: System Requirements

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

Operating System: Client

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.4 with glibc 2.34.x

• Oracle Linux 9.3 with glibc 2.34.x

• Oracle Linux 9.2 with glibc 2.34.x

• Oracle Linux 9.1 with glibc 2.34.x

• Oracle Linux 8.6 with glibc 2.28.x

• Oracle Linux 8.5 with glibc 2.28.x

• Oracle Linux 8.4 with glibc 2.28.x

• Oracle Linux 8.3 with glibc 2.28.x

• Oracle Linux 8.2 with glibc 2.28.x

• Oracle Linux 8.1 with glibc 2.28.x

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

• Oracle Linux 6.8 with glibc 2.12.x

• Oracle Linux 6.5 with glibc 2.12.x

• Oracle Linux 6.4 with glibc 2.12.x

• Oracle Linux 6.3 with glibc 2.12.x

• Oracle Linux 6.2 with glibc 2.12.x

• Oracle Linux 6.1 with glibc 2.12.x

• Oracle Linux 6.0 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

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

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

Rocky Linux

• 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 SP5 with glibc 2.22.x

• SuSE Linux Enterprise Server 12 SP4 with glibc 2.22.x

• SuSE Linux Enterprise Server 12 SP3 with glibc 2.22.x

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

• SuSE Linux Enterprise Server 12 SP1 with glibc 2.19.x

• SuSE Linux Enterprise Server 12 (Initial Release/SP1/SP2/SP3/SP4/SP5) with glibc 2.19.x

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

• x86

• x64

• Power PC (PPC)

  PPC is supported only with ReaR. For more information, see Bare Metal Recovery for PPC Architecture Using 1-Touch for UNIX.

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

For a list of operating system utilities that are required for 1-Touch, see FAQs - Operating system utilities to perform 1-Touch recovery.

Driver Modules

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

Bootloader

• Only BIOS is supported

• Support for UEFI is limited. For more information, see 1-Touch for Linux - UEFI.

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 and Virtualize Me are supported.

• Second Extended File System (ext2)

• Third Extended File System (ext3)

• Fourth Extended File System (ext4)

• Reiser File System (reiserfs)

• XFS

Virtual Machines

• VMware

• Microsoft Hyper-V: Host operating system version of Microsoft Windows Server 2012 R2 Editions or a more recent version.

• Oracle VM: For Oracle VM and Citrix Xen guest VM, perform recovery using the 1-Touch for Linux - Single-Stage DVD procedure. For in-place restores of Citrix Xen guest VMs or for restores to another VM running on Citrix Xen, perform recovery using the 1-Touch for Linux - Single-Stage DVD procedure. To migrate Citrix Xen guest VMs to a non-Citrix Xen environment, see Migrating Citrix Xen Guest VMs to Another Hypervisor or Physical Host.

• Kernel-based VM for Linux (KVM)

• Citrix Xen guest VM: For Oracle VM and Citrix Xen guest VM, perform recovery using the 1-Touch for Linux - Single-Stage DVD procedure. For in-place restores of Citrix Xen guest VMs or for restores to another VM running on Citrix Xen, perform recovery using the 1-Touch for Linux - Single-Stage DVD procedure. To migrate Citrix Xen guest VMs to a non-Citrix Xen environment, see Migrating Citrix Xen Guest VMs to Another Hypervisor or Physical Host.

CommServe

• To enable 1-Touch recovery, the Force per-client certificate authentication on CommServe option has to be turned off on the CommServe at least for the duration of the recovery. This option can be accessed from the CommServe Control Panel by clicking on Certificate Administration.

Client

• iSCSI disks are supported for Virtualize Me. All the backed up iSCSI disks will be re-created as regular SCSI disks on the virtual machine if they are selected during restores.

• 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 and Virtualize Me. For Virtualize Me, as FC HBA (Fibre Channel Host Bus Adapter) virtualization is not supported, multipath SAN disks will be re-created as regular SCSI disks.

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

• 1-Touch supports native Linux multipathing. Vendor-specific multipath implementations are not supported.

• 1-Touch recovery and Virtualize Me for Hyper-V is not supported if the virtual machine is generated using the Generation 2 specification.

• 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 is supported on clients with Linux kernel executable in vmlinuz-* format.

• 1-Touch recovery is supported for LUKS-encrypted disks with LUKS version 1.6.4 or more recent versions. After the first phase of 1-Touch recovery, 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.