> Commvault SaaS > Snapshots > Snapshot Backup Support

Supported Hardware Storage Arrays and Cloud Platforms

Commvault Systems, Inc. tests major versions and some minor versions of firmware, so the best practice is to use the supported versions listed in this topic. If you encounter a problem with a minor version during an IntelliSnap operation, contact Commvault Systems, Inc..

IntelliSnap backup is designed to work in conjunction with the following storage arrays/cloud platforms that provide snapshot functionality for data protection operations:

Vendor

Snapshot

Version or Firmware

Licensing

Software

Protocol

Notes/Caveats

Amazon Web Services

EBS Snapshot

None

None

None

None
  • Supported for Linux file system, Oracle agents, SAP HANA agents, SAP for Oracle agents, and Virtual Server Agent for Amazon.

Amazon FSx for NetApp ONTAP

Snapshot

ONTAP 9.16.1, 9.15.1, 9.14.1, 9.13.1, 9.12.1, 9.11.1

  • CIFS, NFS

  • iSCSI

  • If the volume of the file server that contains the LUN has a SnapMirror Synchronous (SM-S) relationship configured, then IntelliSnap operations on that LUN are not supported.

  • NetApp Open Replication with SnapMirror Cloud is not supported.

  • The storage array is a NetApp OEM partner and uses NetApp Snap engine.

Azure NetApp Files

Snapshot

  • CIFS

  • NFS

SAP HANA requires the NFSv4.1 protocol according to Microsoft and SAP requirements.

Dell EMC Isilon/PowerScale

Snapshot

OneFS 9.10 through 7.0

SnapshotIQ License

  • CIFS, NFS

  • NDMP

  • The support for the CIFS/NFS protocols is for network share backups only.

  • The revert operation is not supported.

Dell PowerStore

Snapshot

  • PowerStore T 1.0.2, 1.0.4

  • PowerStore 2.1.1, 2.0.1, 2.0.0

  • PowerStore 4.1, 4.0, 3.6, 3.5.0.1, 3.2.0.0, 3.0.0.1

None

None

  • Fibre Channel

  • iSCSI

  • NFS

None

Dell PowerFlex

Snapshot

  • VR2_6.10000.123

  • R3_6.100.102

  • R3_5.1300.111

  • R2_0.11000.0

None

ScaleIO Data Client (SDC) drivers on the client computer and proxy computer where snapshots are mounted.

ETH/IB

  • Supported on Windows(x64), Hyper-V, and VMware.

  • Commvault Cloud software does not support hardware snap revert for the versions - R3_6.100.102 and R3_5.1300.111.

Dell EMC Storage Center (DSM)

Snapshot using DSM

  • 7.5.1, Dell EMC Storage Manager 2020 R1 build 20.1.1.716

  • 7.4.2, Dell EMC Storage Manager 2019 R1 build 19.1.579

  • 7.3.2.48 Dell EMC Storage Manager (DSM) 2018 R1.10 build 18.1.10.171

  • 7.2.11.4, Dell EMC Storage Manager 2016 R3.20 build 16.3.20.22

  • Data Instant Replay (snapshots)

  • Remote Instant Replay (replication)

  • Live Volume

Dell EMC Storage Manager: Dell EMC Storage Manager client, Dell EMC Storage Manager data collector, and Dell EMC Storage Manager Server

  • Fibre Channel

  • iSCSI

  • Supported on Windows, Linux, VMware, and Hyper-V.

  • The replication feature is not supported.

  • Compellent Live Volume supported with DSM.

  • The Microsoft Hyper-V agent is not supported with the metro cluster configuration.

Dell EMC Unity

Snapshot

Firmware: 5.5, 5.4, 5.3.1, 5.2.0, 5.1.2.0.5.007, 5.0.6.0.5.008, 5.0.3, 5.0.2.0.5.009, 4.5.1, 4.4.0, 4.3.1, 4.2.1, 4.1.2, 4.1.0

Models:

  • Unity 600/500/400/300

  • Unity 650F/550F/450F/350F

  • Unity VSA

Enterprise license

  • CIFS, NFS

  • Fibre Channel

  • LUN over iSCSI

  • NDMP

  • Dell EMC Unity does not support the revert operations.

  • Support for the CIFS protocol and the NFS protocol is for network share backups only.

  • NDMP: Snapshot cataloging and live browse operations are supported only if the Linux/UNIX shares (NFS) option or the Multiprotocol Shares (SMB and NFS) option is selected while creating the File System in the Dell EMC Unity Filer. Browsing from a backup copy is supported for File Systems created using NFS, SMB, or multiprotocol.

Dell EMC PowerMAX VMAX All Flash/ VMAX3

Dell EMC TimeFinder SnapVX

Dell EMC TimeFinder VP Snap

Dell EMC TimeFinder Clone

PowerMAX

VMAX All Flash

VMAX3

TimeFinder SnapVX

TimeFinder VP Snap

TimeFinder Clone

Solutions Enabler Licensing

  • For the TimeFinder SnapVX(SYMCLI) engine, Solutions Enabler 10.0.0.5, 9.x on client and proxy computers or on Remote MA

  • For the TimeFinder SnapVX engine, Solutions Enabler 9.x on SMI-S server

  • For the TimeFinder VP Snap and TimeFinder Clone engines, Solutions Enabler 9.x on client and proxy computers or on Remote MA and Solution enabler 9.x on SMI-S server

  • Fibre Channel

  • iSCSI for TimeFinder SnapVX only

  • FCoE (Fibre Channel over Ethernet)*

Dell EMC VMAX

Dell EMC TimeFinder VP Snap

Dell EMC TimeFinder Clone

Dell EMC TimeFinder Snap

Dell EMC TimeFinder BCV

VMAX

TimeFinder VP Snap

TimeFinder Clone

TimeFinder Snap

TimeFinder Mirror

Solutions Enabler Licensing

  • For the TimeFinder SnapVX(SYMCLI), Solutions Enabler 10.0.0.5, 9.x on client and proxy computers or on Remote MA.

  • For the TimeFinder SnapVX, Solutions Enabler 9.x or 8.x on the SMI-S server.

  • For the TimeFinder VP Snap, TimeFinder Snap, TimeFinder Clone and TimeFinder BCV engines, Solutions Enabler 9.x, 8.x or 7.6.2.8 on client and proxy computers.

  • Fibre Channel

  • FCoE (Fibre Channel over Ethernet)*

  • Remote SymApi Server is not supported.

  • Client Components (SYMCLI) are required only during the initial one-time configuration. Base Components (with SYMAPI) are required for all snapshot operations.

  • SYMCLI and SYMAPI do not need to be installed on source host when Remote Snap MA is configured for VMAX.

Dell EMC Symmetrix

Dell EMC TimeFinder Clone

Dell EMC TimeFinder Snap

Dell EMC TimeFinder BCV

DMX3 and later

Licenses for:

TimeFinder Clone

TimeFinder Snap

TimeFinder Mirror

Solutions Enabler Licensing

Solutions Enabler 6.4 or later on client and proxy computers

  • Fibre Channel

  • FCoE (Fibre Channel over Ethernet)*

  • Remote SymApi Server is not supported.

  • Client Components (SYMCLI) are required only during the initial one-time configuration. Base Components (with SYMAPI) are required for all snapshot operations.

  • SYMCLI and SYMAPI do not need to be installed on source host when Remote Snap MA is configured for VMAX.

Dell EMC VPLEX

Snapshot

Clone

GeoSynchrony® 6.2, 6.1.0.1, 6.0

Metro node 8.0, 7.1

On the client or on the Remote Snap MA:

Python 3.11.4, 3.9.11, 3.9.6, 3.9.2, 3.8.1, 3.6.4, 2.7, 2.6

On UNIX: openssl-devel package

Fibre Channel

Dell EMC XtremIO

Snapshot

  • XMS versions 6.3.3-8, 6.3.0-62, 6.0.2-17, 4.2.1 Build 8, 4.2.0

  • Cluster versions 4.0.2 Build 80, 4.0.15-24

  • For the XtremIO X2 Model:

    • XMS version 6.3.3-8, 6.2.0-85 Build 85, 6.0.2-17, 6.0.1-30 Build 30

    • Cluster version 6.3.3-8_X2, 6.3.0-62_X2, 6.2.0-85_X2, 6.0.2-17, 6.0.1-27_X2

  • Fibre Channel

  • iSCSI

Google Cloud

Snapshot

None

None

None

None

Hitachi NAS

Snapshot

15.1, 14.9, 14.8, 14.7, 14.6, 14.5, 14.4, 14.3, 14.2, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, 13.0, 12.7

REST API Version 7.0, 4.0

CIFS, NFS

For Hitachi NAS versions 13.2.x and later, use the in-built metro server.

For Hitachi NAS earlier versions than 13.2.x , install an external metro server version 4.0.

  • CIFS, NFS

  • NDMP
  • The support for the CIFS/NFS protocols is for network share backups only.

Hitachi Vantara VSP using CCI Engine

ShadowImage (SI)

Thin Image (TI)

  • VSP 5600H, 5600, 5500H, 5500, 5200H, 5200, 5100H, 5100

  • VSP E Series

  • VSP F900, F700, F370, F350

  • VSP G900, G700, G370, G350

  • VSP G1500*, G1000, G800, G400, G200

  • VSP One Block

For information on HTI and HTIA snapshot support, see system requirements.

  • Thin Image

  • ShadowImage

RAID Manager (01-29-03/05 and later) installed on client and proxy.

For VSM, use RAID Manager (01-32-03/01 and later) installed on client and proxy.

Fibre Channel

  • SI and TI of replicated volumes, Dynamic Provisioned volumes (DP-VOL) and External volumes (ELUN) are also supported.

  • Hitachi Vantara VSP using CCI supports multi-array configuration.

  • On Hitachi Vantara VSP G Series, mixed pools Hitachi Dynamic Provisioning (HDP) can contain Thin Image snapshots.

HPE Alletra 5000 Series

Snap and Replicate
  • 6.1.x

Included

None

  • Fibre Channel

  • iSCSI
  • The storage array uses the HPE Nimble Storage Storage engine.

HPE Alletra 6000 Series

Snap and Replicate
  • 6.1.x, 6.0.x

Included

None

  • Fibre Channel

  • iSCSI
  • The storage array uses the HPE Nimble Storage Storage engine.

HPE Alletra 9000 Series

Snapshot and Clone

  • 9.6.1*

  • 9.5.21

  • 9.5.18

  • 9.5.15

  • 9.5.7**

  • 9.3.3

*If you have upgraded to HPE Alletra 9000 Series 9.6.1 version, ensure to set the SMIS Server Port to 5989 and enable Use secure connection to SMIS Server snapshot configurations. For more information, see snapshot configuration properties.

Virtual Copy

None

  • Fibre Channel

  • iSCSI (firmware versions 9.5.15 and above)

  • The storage array uses the HPE 3PAR StoreServ Snap engine.

  • HPE Alletra 9000 Series versions 9.5.4 and 9.5.3 are not supported.

HPE GreenLake for Block, powered by Alletra MP

Snapshot and Clone

  • 10.4.0**

  • 10.3.0

  • 10.2.0*

*Supports only Linux and VMWare systems with iSCSI protocol.

**Replication for this array version is not supported by Commvault due to the behavioral changes done by HPE in virtual volume sets and RCG.

Virtual Copy

None

  • Fibre Channel

  • iSCSI
  • The storage array uses the HPE 3PAR StoreServ Snap engine.

HPE Primera

Snapshot and Clone

  • 4.6.1*

  • 4.5.15.9

  • 4.5.7.8**

  • 4.4.1.7

  • 4.3.3.2

  • 4.2.1

  • 4.0.1.3+1 (snapshot only)

*If you have upgraded to HPE Primera 4.6.1 version, ensure to set the SMIS Server Port to 5989 and enable Use secure connection to SMIS Server snapshot configurations. For more information, see snapshot configuration properties.

Virtual Copy

None

  • Fibre Channel

  • iSCSI

  • The storage array uses the HPE 3PAR StoreServ Snap engine.

  • HPE Primera versions 4.5.4 and 4.5.3 are not supported.

HPE 3PAR StoreServ

Snapshot and Clone

  • 3.3.2.159(MU1)

  • 3.3.1.648 (MU5)

  • 3.3.1.410 (MU2)+P30, P32, 3.3.1.269 (MU1)+P08, P14, P17

  • 3.2.2.709(MU6), 3.2.2.390 (EMU2), 3.2.2 (MU4), 3.2.2, 3.2.1 (MU3), 3.2.1 (MU2)

  • 3.1.2 (MU3)

  • 2.3.1 (MU4)

Virtual Copy

Thin Provisioning (4096G) license is required when Thin Provisioning is enabled for cloning

None

  • Fibre Channel

  • iSCSI

HPE Nimble Storage

Snap and Replicate

6.1.x, 6.0.x, 5.2.x, 5.1.x, 5.0.x, 4.x, 3.x

Nimble CS-Series, AF-Series, and HF-Series

Included

None

  • Fibre Channel

  • iSCSI

HPE Nimble dHCI

Snap and Replicate

5.2.x

Nimble AF-Series, and HF-Series

Included

None
  • iSCSI

Microsoft Azure

Snapshot

None

None

None

None
  • Supported for the following agents: SAP Oracle, SAP HANA, and SQL Server.

NetApp

Snapshot

For 7-Mode:

Product

  • ONTAP / Data ONTAP

    ONTAP versions

  • ONTAP 7.3.5 and later 7.3.x subversion

  • ONTAP 8.2, 8.1, and 8.0 including subversions

For Cluster-Mode:

Product

  • ONTAP / Data ONTAP

  • Cloud Volumes ONTAP

  • ONTAP Select

    ONTAP versions

  • ONTAP 8.3 and 8.2P3 (and later patch level) including subversions

  • Cluster-Mode ONTAP 8.2.1 NFS configurations require 8.2.1P1 and later patch level with fix for NetApp BURT 806823

  • ONTAP 9.16.1, 9.15.1, 9.14.1, 9.13.1, 9.12.1, 9.11.1, 9.10.1, 9.9.1, 9.8, 9.7, 9.6, 9.5, 9.4, 9.3, 9.2, 9.1, and 9.0

  • FlexClone

  • SnapRestore

  • SnapVault or SnapMirror for replication, installation on the primary storage array and on the secondary storage array

  • For OCUM 5.x: Operations Manager, Provisioning Manager, and Protection Manager licenses

  • For SnapMirrorCloud Replication: SnapMirror Cloud and S3 SnapMirror licenses

  • For SnapLock Enterprise and Tamperproof: SnapLock Enterprise license

  • To create SnapVault and SnapMirror copies of 7-Mode snapshots, use OnCommand Unified Manager server running OCUM 5.2, 5.1, or 5.0.

    For ONTAP 8.1, use OCUM 5.2 or 5.1.

  • CIFS, NFS

  • Fibre Channel

  • FCoE (Fibre Channel over Ethernet)*

  • iSCSI

  • NDMP

Pure

Snapshot

  • Product

    • Pure Storage FlashArray

    • Cloud Block Store

  • Purity version 6.5.2, 6.4.3, 6.3.6, 6.2.14, 6.1.10, 6.1.3, 5.3.10, 5.3.8, 5.3.6, 5.3.2, 5.2.3, 5.1.6, 5.1.1, 5.0.1, 4.10.9, 4.10.7, 4.9.6, 4.8.10, 4.8.7, 4.7.5, 4.6.11, 4.5.5, 4.1.1

  • REST API version 2.16, 1.4

None

None

  • Fibre Channel

  • iSCSI
  • For any of the Purity ActiveCluster releases from 5.0.5 to 5.0.0, when the source volume is externally deleted on the array and a snapshot of the source volume is mounted inside a pod, the source volume and the snapshot mount clone are deleted.

VAST Data Platform

Snapshot

5.0.0.x

None

None

  • CIFS

  • NFS

Western Digital IntelliFlash

Snapshot

  • NFS for the VMware agent:

    • INTELLIFLASH 3.11.0, 3.10.0, 3.9.1, 3.7

    • REST API 2.5, 2.4, 2.3, 2.1

    • NFS 4.0–2.0

  • For all other agents:

    • INTELLIFLASH 3.11.0, 3.10.0, 3.9.1, 3.7, 3.5

    • REST API 2.5, 2.4, 2.3, 2.1, 2.0

None

None

  • Fibre channel

  • iSCSI

  • NFS 2.0 -4.0 for the VMware agent

*Supported through Field Certification. Contact your Software Provider or Professional Services to see if the specific FCoE can be supported.

**Replication for this version of array is pending validation by Commvault.

Notes

  • Do not install the Commvault Cloud software on the same volume that you are protecting with the IntelliSnap backup feature.

  • Subclients must contain LUNs (Logical Unit Number) from the same storage array. You can configure subclients with LUNs from multiple storage arrays of the same vendor for NetApp, Pure Storage FlashArray, and Hitachi Vantara VSP running the Hitachi Vantara CCI engine. Do not use this configuration on other storage vendors.

  • NetApp storage arrays support LUNs from multiple NetApp storage arrays, if the subclients are on the same filer operating system. For example, LUNs from 7-Mode and LUNs from Cluster-Mode cannot be part of the same subclient.

  • Commvault Cloud software supports IntelliSnap backups of subclients that have LUNs from multiple Hitachi Vantara VSP storage arrays that use Hitachi Vantara CCI engines.

  • Most capabilities of Data ONTAP 7-Mode apply to Cluster-Mode, but cascaded replication of primary to snapvault to snapmirror on a single policy is not supported.

  • Dynamic Disks on Window Operating Systems are not supported.

  • When performing IntelliSnap backup for a Windows MSCS Cluster, a separate proxy server (external to the cluster nodes) must be used for mount, backup, and restore operations as disk signature conflicts might occur if these operations are performed from one of the servers in the cluster.

  • Booting from SAN volumes is not supported.

  • The IntelliSnap feature is not supported for VMware data stores created using local disks. The data stores should be created from LUNs.

  • NAS attached tape libraries are not supported for IntelliSnap operations.

  • The backup copy operation is not supported on a client computer that is upgraded to a version higher than its associated MediaAgent. For example, there is no support for backup copy operations if the client runs version 10 and the MediaAgent runs version 11.

  • IntelliSnap backups of Raw Device Map (RDM) disks (passthrough disks for Hyper-V) are supported for all agents, but the Virtual Server Agent only provides support for VMware and Microsoft Hyper-V virtual machines:

    • For VMware, see Include RDMs and Independent Disks in IntelliSnap Backup Operations.

    • Hyper-V backups include passthrough disks if the following conditions are met:

      • The virtual machine has a File System agent or another supported agent installed on it and uses that agent for IntelliSnap backups.

      • The client computer (physical or virtual) is configured to mount snapshots using the iSCSI initiator, or the physical proxy server is configured to mount snapshots over Fibre Channel.

      • The passthrough disk on the virtual machine is attached using a virtual Fibre Channel adapter.

  • For VMware VMs, the host of the virtual computer must have ESX server version 5.0 or later.

  • RDM disks are not supported by the Hitachi Vantara HDvM engine.

  • Revert operation is not supported for LUNs configured as RDMs for the NetApp storage array.

  • For NetApp arrays and arrays that use the NetApp Snap engine, if you are using AIX, HP-UX, or Solaris clients or access nodes, the following conditions apply:

    • For ONTAP versions earlier than 9.11.1, snapshot and other operations are not supported. However, you can configure and use a Windows or Linux-based remote MediaAgents or proxy access node to perform those operations.

    • For ONTAP versions 9.11.1 or later:

      • Snapshot and other operations are supported only if REST APIs are enabled on the array. For information on enabling REST APIs, see the How to enable REST API based authorization? section on Frequently Asked Questions for the NetApp Storage Array.

      • Configure and use a Windows or Linux-based data path MediaAgents for the storage policy copy to perform snapshot replication.

×

Loading...