1-Touch for Linux: System Requirements
The following are the requirements for 1-Touch on Linux:
- 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 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/CentOS 8.4 with glibc 2.28.x: Virtualize Me is not supported
- Red Hat Enterprise Linux/CentOS 8.3 with glibc 2.28.x: Virtualize Me is not supported
- Red Hat Enterprise Linux/CentOS 8.2 with glibc 2.28.x: Virtualize Me is not supported
- Red Hat Enterprise Linux/CentOS 8.1 with glibc 2.28.x: Virtualize Me is not supported
- Red Hat Enterprise Linux/CentOS 8.0 with glibc 2.28.x: Virtualize Me is not supported
- Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x or a more recent version
- Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x
- Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x
SuSE Linux (SLES)
- 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 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 16.04 LTS with glibc 2.23
- Ubuntu 14.04 LTS with glibc 2.19
Ubuntu 12.04 LTS with glibc 2.15
2 GB of free disk space is required for the /tmp directory.
No additional disk space required beyond File System Agent disk space requirements.
4 GB minimum
- Intel Pentium
- Compatible processors
A CD-ROM drive or 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 required for 1-Touch, see FAQs - Operating system utilities to perform 1-Touch recovery.
- Only BIOS is supported
- Limited support for UEFI. For more information, refer to 1-Touch for Linux - UEFI
Supported file system and volume manager types
- 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)
Note: Snapshot volumes will not be recovered as part of the 1-touch recovery. Hence, it is recommended that you mount and back up the snapshot data.
- Microsoft Hyper-V*
- Oracle VM**
- Kernel-based VM for Linux (KVM)
KVM on OpenStack is not supported.
- Citrix Xen guest VM**
*Host operating system version of Microsoft Windows Server 2012 R2 Editions or higher
**For Oracle VM and Citrix Xen guest VM, perform recovery using the 1-Touch for Linux - Single-Stage DVD procedure. For information, see 1-Touch for Linux - Single-Stage DVD.
**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. For information, see 1-Touch for Linux - Single-Stage DVD.
**To migrate Citrix Xen guest VMs to a non-Citrix Xen environment, see Migrating Citrix Xen Guest VMs to Another Hypervisor or Physical Host.
- 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.
- 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 higher versions, set the Virtual Machine compatibility to 5.5 or higher (Virtual Machine Hardware Version 10) during the creation of the virtual machine.
- Itanium (IA64) processor 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 higher. 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:
where the cryptFile.key format is:
encrypted_disk_name p passkey_in_plain_format
Third-party maintenance (minor) releases or feature releases 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 feature releases. In some cases, these minor releases or feature releases affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or feature releases. 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 feature releases are compatible with the Commvault software.
Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.
Last modified: 5/25/2021 2:57:58 PM