The following table lists the platforms supported for IntelliSnap backup.
Install the latest updates on all platforms.
Note
IntelliSnap with Veritas Volume Manager requires ALUA compliant LUNs (primary and secondary). For non-compliant ALUA LUNs, a workaround is explained in this Symantec KB article TECH1856668 (SF 6.0 NETAPP ASL/APM dropped support for A/P mode and support only ALUA mode).
Operating System |
Version |
Cluster Support |
---|---|---|
AIX |
AIX 7.2 (LPARS supported, WPAR and Virtual SCSI devices not supported) |
|
AIX 7.1 (LPARS supported, WPAR and Virtual SCSI devices not supported) AIX 6.1 |
Veritas Cluster PowerHA for AIX (formerly HACMP)
|
|
Amazon Linux |
Amazon Linux 2023 AMI Note Certified only for Amazon FSx for NetApp ONTAP storage array |
|
Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type |
|
|
CentOS Linux |
CentOS Linux 8.x** |
Linux Cluster Veritas Cluster |
CentOS Linux 7.x** |
Linux Cluster |
|
CentOS Linux 6.x |
Linux Cluster |
|
CentOS Linux 5.x |
Linux Cluster |
|
HP-UX |
HP-UX 11 v3/v2 (Itanium) |
Service Guard Veritas Cluster |
Oracle Enterprise Linux |
Oracle Enterprise Linux 8.x**, 7.x**, 6.x, and 5.x |
|
Red Hat Linux |
Red Hat Linux 9.x** |
Linux Cluster Veritas Cluster |
Red Hat Linux 8.x** |
Linux Cluster Veritas Cluster |
|
Red Hat Linux 7.x** |
Linux Cluster Veritas Cluster |
|
Red Hat Linux 6.x |
Linux Cluster Veritas Cluster |
|
Red Hat Linux 5.x |
Linux Cluster Veritas Cluster |
|
Rocky Linux |
Rocky Linux 9.x** |
Linux Cluster Veritas Cluster |
Rocky Linux 8.x** |
Linux Cluster Veritas Cluster |
|
Solaris |
Solaris 11.4*** |
|
Solaris 11.3*** |
||
Solaris 11.2*** |
||
Solaris 11 Express |
||
Solaris 11 SPARC (Solaris Zones Supported) |
Sun Cluster Veritas Cluster |
|
Solaris 11 x64 |
||
Solaris 10 SPARC (Solaris Zones Supported) |
Sun Cluster Veritas Cluster |
|
SuSE Linux |
SuSE Linux Enterprise Server 15 (Initial Release/SP4/SP3/SP2/SP1) |
Linux Cluster Veritas Cluster |
SuSE Linux 15 (Initial Release/SP4/SP3/SP2/SP1 and higher) with glibc 2.26.x and later |
||
SuSE Linux 12.x Initial Release/SP3 or later |
||
SuSE Linux 11 (Initial Release/SP4/SP3/SP2/SP1) with glibc 3.x |
||
SuSE Linux 11 (Initial Release/SP4/SP3/SP2/SP1) with glibc 2.11.x |
||
SuSE Linux 11 (Initial Release/SP4/SP3/SP2/SP1) with glibc 2.9.x and later |
||
SuSE Linux 10 (Initial Release/SP4/SP3/SP2/SP1) with glibc 2.6.x |
||
SuSE Linux 10 (Initial Release/SP4/SP3/SP2/SP1) with glibc 2.4.x |
||
Ubuntu |
Ubuntu 22.04 |
|
Ubuntu 19.04 |
||
Ubuntu 18.04 |
||
Ubuntu 16.x |
||
Ubuntu 14.x and later |
||
VMware vCenter |
vCenter Server (VMware vCenter Server Appliance, VMware ESX or ESXi) |
|
Windows |
Windows Server 2025 Windows Server 2022 Windows Server 2019 Windows Server 2016 |
MSCS |
-
*All disks should support snap and must be available on the client computer where the IntelliSnap job initiates.
-
Mount, backup copy, and backup operations are supported using proxy GPFS cluster only; this is due to GPFS's limitation which does not allow NSD clone mount on the same GPFS cluster.
-
Set the path to the GPFS binaries in the PATH environment variable for the root user. You can either modify the root user's .profile file and add the following line, or execute the command every time before you start the Commvault services.
export PATH=$PATH:/usr/lpp/mmfs/bin
-
If you want to use a Logical Domain (LDOM) with the IntelliSnap feature, the disk that is presented to the LDOM cannot be in a ZFS ZPool on the LDOM host.
-
** To enable Linux support, disable automatic activation of volumes. Having automatic activation of volumes interferes with HotAdd operations during backup and recovery. For more information, see Best Practices - IntelliSnap for UNIX File System.
-
*** For IntelliSnap operations:
-
Solaris 11.2 supports zpool 35 only.
-
For Solaris zoned systems, if you want to run snapshot backup operations for raw devices on non-global client computers, then map both the character device and the block device to the local zone client computer.
If your Solaris release is 11.1 or earlier, first, run the zonecfg command on the global zone computer, and then reboot the local zone computer. The zonecfg settings take effect only after the local zone computer rebooted.
If your Solaris release is 11.2 or more recent, first, on the global zone computer, map the block device and its corresponding character device to the local zone computer. -
Configure a proxy computer.
-
The proxy computer must have the same operating system and the same zpool version of the source computer.
-
A zpool of the same name must not exist on the proxy computer.
-
For the backup copy, the proxy computer must be a Solaris global zone and either a stand-alone Solaris machine or an Oracle VM for Sparc (AKA LDOM) with connectivity to the array (FC or iSCSI).
-
Run restore operations from the proxy computer.
-
Revert operations are not supported.
-
For kernel zone operations, device configuration using either the
match
property or thestorage
property normal device name format is supported. Storage URIluname
format is also supported for device configuration. Cluster device names using /dev/did format are not supported. -
IntelliSnap for clustered disks in a kernel zone is not supported.
-
When a zpool is created on clustered disks, the kernel zone must send the original disk name to the global zone.
-
-
Linux operating systems, IntelliSnap for UNIX is supported on x86, x64 or compatible processors.
Note that this list does not provide a comprehensive list of supported platforms for each agent. See System Requirements for information on the platforms supported by the individual Agents.