IntelliSnap Backup - Support

Table of Contents

Initial IntelliSnap Setup

Deployment and a successful initial run of an IntelliSnap backup in some complex environments may require customization, due to specific dependencies in your environment. The following parameters are known to affect the deployment and initial run and hence need a thorough evaluation:

  • Firmware versions on the array
  • Device types
  • Mode of access
  • Security configuration
  • Operating Systems interacting with the storage array
  • Application layout on the storage array LUNs

License Requirements

You can choose to use one of the following licensing mechanisms:

  • Traditional License, based upon products and features in your CommCell.
  • Capacity License, based on the amount of data you want to protect.

For comprehensive information on licensing, see License Administration.

Traditional License

The following license types are available for IntelliSnap.

Feature License Type License Consumption
IntelliSnap Operations Hardware Snapshot Enabler 1 license per Client
NetApp SnapVault and SnapMirror NetApp Snap Management 1 license per CommCell

Capacity License

If you plan to use capacity licenses, the following licenses must be obtained for IntelliSnap and the NetApp SnapVault/SnapMirror features.

License Type License Consumption
Data Protection Snapshot 1 license per CommCell for n Terabytes (TB) of protected data
Data Protection Replication 1 license per CommCell for n Terabytes (TB) of protected data

Supported Storage Arrays

For information and compatibility check on supported snapshot engines, see IntelliSnap Support Matrix  in interactive view.

The IntelliSnap backup is designed to work in conjunction with the following storage arrays, which provide snapshot functionality for data protection operations:

Supported Hardware Arrays

Vendor Snapshot Version or Firmware Required Licensing Required Software Protocol Notes/Caveats
DataCore SANsymphony-V Snapshot

Clone

SANsymphony-V version 9.0 PSP4 Update 4 or later

SANsymphony -V version 10.0 PSP3 or later

  None

Fibre Channel

iSCSI

Supported on Windows(x64), Windows 2008 R2 cluster, Hyper-V and VMware.

SAN transport mode is not supported for VMware.

Dell Compellent Snapshot

Firmware version 5.5.14 and later for 5.x and 6.2.2, 6.5.2, 6.6.4

Data Instant Replay license None

Fibre Channel

iSCSI

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

Compellent Live Volume feature and replication are not supported.

Dell EqualLogic Snapshot

Clone

5.0.8 or later Included None iSCSI On Red Hat Linux and CentOS computers using version 5.5 (32-bit and 64bit).

No UNIX.

For Linux:

RedHat 5.5, 5.7, or 5.8

CentOS 5.5, 5.7, or 5.8

Boot from SAN volumes is not supported.

EMC VNX / CLARiiON SnapView Snap

SnapView Clone

CX500 / CX700

CX3-10 thru CX3-80

CX4-120 thru CX4-960

SnapView Snapshot/Clone

 

Solutions Enabler 7.2 or later, except Solutions Enabler 8.x, on client and proxy computers

Navisphere Host Agent on Client and Proxy

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

 

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

EMC VNX SnapView Snap

SnapView Clone

VNX Snapshots

VNX 5100, 5300, 5500, 5700, 7500

VNX 5200,5400,5600,5800,7600,8000

VNX OE for Block Version 05.32 or later is required for VNX Snapshots

 

SnapView Snapshot/Clone

 

Solutions Enabler 7.2 or later, except Solutions Enabler 8.x, on client and proxy computers

Navisphere CLI on Client and Proxy (only required for VNX snapshots)

Navisphere/Unisphere Host Agent on client and proxy computers

Fibre Channel

iSCSI

VMware with NFS datastores are supported.

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

For configuring a VNX array, refer to the step-by-step instructions provided for EMC Clariion.

Hyper-V and UNIX are supported through Field Certification* for VNX 5200, 5400, 5600, 5800, 7600, and 8000.

EMC VNX / Celerra SnapSure Snap DART 5.5 or later SnapSure Snap License

Solutions Enabler Licensing

Solutions Enabler 6.5.1 or later, except Solutions Enabler 8.x, on Client and Proxy

Navisphere CLI on Client and Proxy

NFS Supported on VMware 4.x.

No Hyper-V

EMC Symmetrix TimeFinder Snap

TimeFinder Clone

TimeFinder Mirror

DMX3 or later Licenses for:

TimeFinder Snap

TimeFinder Mirror

TimeFinder Clone

Solutions Enabler Licensing

Solutions Enabler 6.4 or later on client and proxy computers

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No Hyper-V

Remote SymApi Server is not supported.

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

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

EMC VMAX TimeFinder Snap

TimeFinder Mirror

TimeFinder Clone

TimeFinder  VP Snap

VMAX Licenses for:

TimeFinder Snap

TimeFinder Mirror

TimeFinder Clone

TimeFinder VP Snap

Solutions Enabler Licensing

Solutions Enabler 7.2 or later on client and proxy computers

For TimeFinder VP Snap, Solutions Enabler 7.6.2.8 or later on client and proxy computers

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No Hyper-V

Remote SymApi Server is not supported.

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

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

If EMC Solutions Enabler installer is not available for a specific 32 bit platform, use Remote Snap MediaAgent installed on a different platform.

EMC VPLEX Snapshot

Clone

GeoSynchrony® Release 5.2   On the client or on the Remote Snap MA:

Python 2.6 or later

Solutions Enabler 7.2 or later (VMAX backend)

On UNIX: openssl-devel package

Fibre Channel

 

Current support is for storage volumes originating from EMC VMAX arrays only.

Support is available for VPLEX virtual volumes created on one device, one extent, and one storage volume, with the extent having the same size as the storage volume.

When adding multiple VPLEX virtual volumes, they must all originate from one backend storage array.

VPLEX distributed volumes are not supported.

VPLEX virtual volumes are not supported by IntelliSnap Data Replicator.

Fujitsu ETERNUS DX SnapOPC Snap

EC Clone

SnapOPC+ Snap

ETERNUS DX S2 V10L54-1000 or later

ETERNUS DX S2 series - 80, 90, 410, 440, 8100, 8700

ETERNUS DX S3 V10L20-0000 or later

ETERNUS DX S3 series - 100, 200, 200F, 500, 600

ETERNUS DX S3 V10L25-0000 or later

ETERNUS DX S3 series - 60

ETERNUS DX S3 V10L40-0000

ETERNUS DX S3 series - 8700, 8900

Local Copy

Thin Provisioning

None iSCSI

Fibre Channel

 
HDS AMS Copy-on-Write

Shadow Image

AMS 100, 200 & 500

AMS 100, 2100, 2300, & 2500

Licenses for Copy-on-Write (COW) snapshot and Shadow Image Device Manager 7.1.1 (or later) Agent installed on Client and Proxy

Device Manager Server 7.1.1 (or later) installed on any computer

RAID Manager (01-25-03/05 or later) installed on Client and Proxy

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No Hyper-V

HDP volumes are supported for HDvM 7.3.0 or later.

The Virtual Machine HotAdd feature is not supported.

 

HDS HUS Copy-on-Write

Shadow Image

HUS 100 series Licenses for Copy-on-Write (COW) snapshot and Shadow Image Device Manager 7.2.1 (or later) Agent installed on Client and Proxy

Device Manager Server 7.2.1 (or later) installed on any computer

RAID Manager (01-26-03/02 or later) installed on Client

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No Hyper-V

The Virtual Server iDataAgent must be installed on a physical server and not on a virtual machine.

The Virtual Machine HotAdd feature is not supported.
HDS USP/VSP Copy-on-Write

Shadow Image

HDS USP, USPv, VSP Licenses for Copy-on-Write (COW) snapshot and Shadow Image Device Manager 7.1.1 (or later) Agent installed on Client and Proxy

Device Manager Server 7.1.1 (or later) installed on any computer

RAID Manager (01-25-03/05 or later) installed on Client and Proxy

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No Hyper-V

COW support for USP volumes.

COW and SI support for VSP volumes. Dynamic Provisioned volumes (DP-VOL) are also supported.

The Virtual Machine HotAdd feature is not supported.  
HDS VSP/HUS-VM using CCI Engine Shadow Image (SI)

Thin Image (TI)

HDS HUS-VM, VSP Licenses for Thin Image and Shadow Image RAID Manager (01-29-03/05 or 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.
HP EVA EVA Business Copy Snapshot and Clone

HP EVA

HP Business Copy EVA feature HP SMI-S EVA on Server

Command View Version 9.1 , 9.3, 10.3

Fibre Channel

iSCSI

No Hyper-V 

HP EVA clone does not support revert operations.

HP (HDS OEM) XP, P9500 Arrays Copy-on-Write

Shadow Image

XP 12000 – 24000

P9500

Licenses for Copy-on-Write (COW) snapshot and Shadow Image HP StorageWorks Command View Advanced Edition Agent (Device Manager 7.1.1 or later) installed on client and proxy computers

HP StorageWorks Command View Advanced Edition Server (Device Manager 7.1.1 or later) installed on any computer.

HP StorageWorks RAID Manager installed on client and proxy computers.

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No Hyper-V The Virtual Machine HotAdd feature is not supported.
HP 3PAR Snapshot and Clone

2.3.1(MU4), 3.1.2(MU3), 3.1.3(MU1), 3.2.1(MU2), 3.2.1 (MU3), and 3.2.2

Virtual Copy

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

3PAR SMI-S on Server

Fibre Channel

iSCSI

Hyper-V snap is supported.

3.1.2(MU1) does not support Simpana clone operations.

Not supported with 3.1.1.342 , 3.1.1 MU1 + Patch 10, 3.1.1 (MU2) and 3.1.1(MU3)

HP 3PAR clone does not support revert operations.

HP 3PAR revert with RDM is not supported.

HP 3PAR revert is not supported for virtual volume sets.

Huawei Snapshot

Clone

Huawei OceanStor 18000 Series Storage

Huawei OceanStor V3 Converged Storage

Huawei OceanStor T Series Storage S2600T/S5500T/S5600T/S5800T/S6800T

V200R002C00/V200R002C10/V200R002C20

HyperSnap

HyperClone

Smart Thin (optional for Thin Clone)

None

Fibre Channel

iSCSI

Huawei does not support UNIX.
IBM N-Series Snapshot For 7-Mode:

ONTAP 7.3.5 or later

ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2

For Cluster-Mode:

ONTAP 8.2P3 (or later patch level) and 8.3

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

FlexClone

SnapRestore

SnapVault/Mirror for replication

Operations Manager, Provisioning Manager, and Protection Manager licenses are required for OnCommand Unified Manager.

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

OnCommand Unified Manager 5.1 or 5.2 is required for ONTAP 8.1.0.

To create SnapVault and SnapMirror copies of clustered Data ONTAP snapshot copies, use OnCommand Unified Manager 6.0, 6.1, 6.2 and 6.3 P1. Refer to NetApp Interoperability Matrix Tool (IMT) to verify the latest support for your product configuration.

Fibre Channel

iSCSI

NFS

CIFS

Supported on HP-UX running on Intel Itanium processors using Fibre Channel.
IBM SVC Flash Copy

Space-efficient Flash Copy

SVC / V7000 6.1.0.7 until 7.3.0.4; 7.3.0.9, 7.4.0.2, 7.5.0.2

V9000 7.4.1.2

FlashCopy IBM SMI-S on Server

Fibre Channel

iSCSI

 

IBM XIV Snap Any XIV Array Included IBM XCLI 2.3 or later on client and proxy

Fibre Channel

iSCSI

Supported on Windows 2012 R2 cluster.
INFINIDAT Snapshot Version 1.5.1.8 or later Included None

Fibre Channel

UNIX is supported for Linux x86 and x64.
NetApp E-Series (LSI arrays) Snapshot

VolumeCopy

PiT (Point-in-Time)

Dell MD Series – 3000(i), 3200(i), 3220(i)

IBM DS - 3200, 3300, 3400 - 3512, 3524, 3950, 4100, 4200, 4300, 4400, 4500 - 4700, 4800, 5020, 5100, 5300

SGI IS – 220, 350, 400, 4xxx, 5xxx

SGI TP – 9300(s), 9400(s), 9500(s)

Sun - 25xx, 61xx, 65xx, 6780, 9176, FLX210, FLX240, FLX280

NetApp E-Series E5500

Snapshot

VolumeCopy

Legacy license for LSI Snapshot engine with NetApp E-series arrays

LSI SMI-S server versions 10.10.6054, 10.30.0G00.009, and 10.32.0G00.002

Fibre Channel

iSCSI

VolumeCopy is not supported for Hyper-V.

Snapshot and VolumeCopy do not support revert operations.

Fibre Channel is not supported with SMI-S version 10.30.

NetApp Snapshot For 7-Mode:

ONTAP 7.3.5 or later

ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2

For Cluster-Mode:

ONTAP 8.2P3 (or later patch level) and 8.3

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

FlexClone

SnapRestore

SnapVault/Mirror for replication

Operations Manager, Provisioning Manager, and Protection Manager licenses are required for OnCommand Unified Manager.

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

OnCommand Unified Manager 5.1 or 5.2 is required for ONTAP 8.1.0.

To create SnapVault and SnapMirror copies of clustered Data ONTAP snapshot copies, use OnCommand Unified Manager 6.0, 6.1, 6.2 and 6.3 P1. Refer to NetApp Interoperability Matrix Tool (IMT) to verify the latest support for your product configuration.

Fibre Channel

iSCSI

NFS

CIFS

Supported on HP-UX running on Intel Itanium processors using Fibre Channel.

Nimble Snapshot 1.4.x

2.0.x

Included None iSCSI Supported on Windows(x64) and VMware.
Nimble CS- Series Snap and Replicate

2.1.x

2.2.x

2.3.x

Included None Fibre Channel support for version 2.2.x or later

iSCSI

Supported on Windows(x64) and VMware.
Oracle ZFS Snapshot Snapshot ZS3-2, ZS3-4 with minimum firmware versions

7x20 (2011.1.4.2 for non-VMware & 2013.1.0.1 for VMware)

Separate cloning license per controller or node None

Fibre Channel

iSCSI

Supported on Windows (x64), Linux, Solaris, and VMware.

Pure Storage Snapshot Purity version 4.1.1

REST API version 1.4

None None

Fibre Channel

iSCSI
 

 

Supported Hardware Arrays for Replicated Environments

Vendor Snapshot Version or Firmware Required Licensing Required Software Protocol Notes/Caveats
IBM N-Series SnapVault SnapMirror For 7-Mode:

ONTAP 7.3.5 or later

ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2

For Cluster-Mode:

ONTAP 8.2P3 (or later patch level) and 8.3

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

SnapVault/SnapMirror Primary and Secondary

FlexClone

SnapRestore

Operations Manager, Provisioning Manager, and Protection Manager licenses.

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

OnCommand Unified Manager 5.1 or 5.2 is required for ONTAP 8.1.0.

To create SnapVault and SnapMirror copies of clustered Data ONTAP snapshot copies, use OnCommand Unified Manager 6.0, 6.1, 6.2 and 6.3 P1. Refer to NetApp Interoperability Matrix Tool (IMT) to verify the latest support for your product configuration.

Fibre Channel

iSCSI

NFS

CIFS

Supported on HP-UX running on Intel Itanium processors using Fibre Channel.

vFilers as a destination supported for NetApp 7-Mode.

NetApp with SnapVault SnapMirror SnapVault SnapMirror For 7-Mode:

ONTAP 7.3.5 or later

ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2

For Cluster-Mode:

ONTAP 8.2P3 (or later patch level) and 8.3

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

SnapVault/SnapMirror Primary and Secondary

FlexClone

SnapRestore

Operations Manager, Provisioning Manager, and Protection Manager licenses.

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

OnCommand Unified Manager 5.1 or 5.2 is required for ONTAP 8.1.0.

To create SnapVault and SnapMirror copies of clustered Data ONTAP snapshot copies, use OnCommand Unified Manager 6.0, 6.1, 6.2 and 6.3 P1. Refer to NetApp Interoperability Matrix Tool (IMT) to verify the latest support for your product configuration.

Fibre Channel

iSCSI

NFS

CIFS

Supported on HP-UX running on Intel Itanium processors using Fibre Channel.

vFilers as a destination supported for NetApp 7-Mode.

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

Supported Software Snapshot Engines

Vendor Snapshot Version or Firmware Required Licensing Required Software Notes/Caveats
IntelliSnap Data Replicator Not applicable Not applicable Local native snapshot license (Volume manager snapshot license or QSnap license)

Hardware Snap Engine or native snap or QSnap license

ContinuousDataReplicator IntelliSnap Data Replicator does not support revert operations.

IntelliSnap Data Replicator is not supported with EMC VPLEX arrays.

Oracle Solaris Solaris ZFS Solaris (Global zone only) Local native snapshot license Solaris OS has ZFS snap capability Set the EnableNativeSnapEngine global parameter to 1 using the SetKeyIntoGlobalParam qscript.

Example:

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si EnableNativeSnapEngine -si y -si 1

Subclients should contain LUNs (Logical Unit Number) from the same storage array. LUNs from multiple storage arrays are not supported on the same subclient, except for NetApp. NetApp supports LUNs from different 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.

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.

Boot from SAN volumes is not supported.

The IntelliSnap feature is not supported for VMware datastores created using local disks. The datastores should be created from RDM LUNs.

NAS attached tape libraries are not supported for IntelliSnap operations.

IntelliSnap backups of Raw Device Map (RDM) disks are supported for all agents, except VMware and Microsoft Hyper-V, configured in virtual computer in physical compatibility mode, provided that

  • the iSCSI initiator is configured on the client computer to mount the snapshot or
  • the physical proxy server is configured to mount snapshot over Fibre Channel
  • the proxy MediaAgent, used for a IntelliSnap operation, is installed on a physical computer and not on a virtual computer
  • the virtual computer has File System or any other agent installed on it for IntelliSnap
  • the host of the virtual computer has ESX server version 5.0

Raw Device Map disks are not supported by the HDS HDvM engine.

For Microsoft Hyper-V, disks presented via virtual Fibre Channel adapters are supported for IntelliSnap backups, but pass-through disks are not supported.

For information and compatibility check on supported snapshot engines, see IntelliSnap Support Matrix  in interactive view.

Backup Types

The following table lists the Agents supporting the IntelliSnap backup and provides information about the various options supported by each of these Agents.

Agents Full Backup Incremental Backup Differential Backup Notes
Virtual Server (VMware)   Before performing revert operations, ensure that all disks reside on the NetApp NFS data store. If the data does not reside on the NetApp NFS data store, you cannot perform revert operations.

Backup of VM Templates is not supported.

Virtual Server instances configured with ESX server are not supported. Instances should be configured using Virtual Center.

IntelliSnap for VMware is not supported for virtual machines in vCloud.

Exchange Database IntelliSnap backups are not supported on Exchange 2007 Cluster Continuous Replication (CCR) Passive nodes.

IntelliSnap Data Replicator snapshots are not supported on Exchange DAG clients.

SRM is not supported.

Notes Database      
MySQL   Incremental backups are traditional MySQL log backups. Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy.
Oracle   Incremental backups are applicable for Backup copies.
Oracle RAC   Incremental backups are applicable for Backup copies.
Microsoft SQL Server   Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy.
NAS  
Virtual Server (Hyper-V)  
SAP Oracle      
DB2     Backup of partial databases is not supported.

Log files always use the traditional backup method.

DB2 MultiNode     Backup of partial databases is not supported.

Log files always use the traditional backup method.

UNIX File System

On Demand Backup Set is not supported for IntelliSnap Backup.

Raw partitions in UNIX are supported.

Mirrored storage configurations (i.e., physical LUNs from separate filers) are supported for mirrored LVs on AIX LVM, Linux LVM, mirrored Solaris ZFS zpools, and mirrored VxVM volumes.

Windows File System

On Demand Backup Set is not supported for IntelliSnap Backup.

Application Clone

The Application Clone operation duplicates a source database by creating read-write clones from snapshots taken during a snap backup job. This operation leverages the cloning capability of the storage array hardware. By using the Application Clone operation, you can duplicate large databases in less time.

Arrays Agents
NetApp

Oracle

Oracle RAC

Microsoft SQL Server

Nimble

Microsoft SQL Server

Pure Storage

Oracle

Microsoft SQL Server

Platforms

The following table lists the platforms supported for IntelliSnap backup. The latest updates should be installed on all the platforms.

For AIX and Solaris Sparc, IntelliSnap backups are supported for clients using the 32-bit packages of Simpana only.

For Solaris x86, IntelliSnap backups are supported for clients using 64-bit packages of Simpana (64-bit packages of Simpana are installed by default).

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 Cluster Support File Systems Databases Applications
Windows 2003 and later MSCS NTFS

Cluster shared volumes (CSV) is supported only for Hyper-V snap. Snap with CSV is not supported for  any other application, including Filesystem.

SQL 2005 and later

Exchange 2003 or 2007, and Exchange 2010 or later (including DAG environments)

Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c (ASM databases not supported)

DB2 version 9 or later

 
VMware ESX or ESXi

VMware vCenter Server Appliance

  iSCSI, FC, NFS, and VSAN datastores ESX vSphere 4.1 or later, 5.0.x, 5.1.x, 5.5, 5.5.1, 5.5.2, 5.5.3, 6.0  
AIX 5.3, 6.1, 7.1 (LPARS Supported, Virtual SCSI devices not supported) Veritas Cluster

PowerHA for AIX (formerly HACMP)

  • PowerHA on AIX 7.1 computers requires:
    • AIX 7.1 TL 03 SP1 (or higher)
    • PowerHA 7.1.2 SP4 (or higher)
  • PowerHA on AIX 6.1 computers requires:
    • AIX 6.1 TL 09 SP3 (or higher)
    • PowerHA 6.1.0 SP13 (or higher)
JFS, JFS2, VxFS, VxCFS, IBM General Parallel File System (GPFS)* 3.5.0.7 or later Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2
HP-UX 11 v2/v3 (Itanium) Service Guard

Veritas Cluster

HFS, VxFS, VxCFS Oracle 10g R2, Oracle 11g R1 & R2

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2
Oracle Enterprise Linux 5.x , 6.x and 7.x**   ext2, ext3, ext4, reiserfs, VxFS, VxCFS, OCFS2 Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
Red Hat Linux 4.x and 5.x Linux Cluster

Veritas Cluster

ext2, ext3, ext4, reiserfs, VxFS, OCFS2, VxCFS, IBM General Parallel File System (GPFS)* 3.5.0.7 or later, GFS2 (5.x only) Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
CentOS Linux 4.x and 5.x Linux Cluster ext2, ext3, ext4, reiserfs, OCFS2, GFS2 (5.x only) Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
Red Hat Linux 6.x and 7.x** Linux Cluster

Veritas Cluster

ext2, ext3, ext4, reiserfs, VxFS, VxCFS, OCFS2, IBM General Parallel File System (GPFS)* 3.5.0.7 or later, GFS2 Oracle 10g R2, Oracle 11g R1 & R2; Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
CentOS Linux 6.x and 7.x** Linux Cluster ext2, ext3, ext4, reiserfs, OCFS2, GFS2 Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
Solaris 10 SPARC (Solaris Zones Supported) Sun Cluster

Veritas Cluster

UFS, VxFS, VxCFS, ZFS 5 with zpool version 33 Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
Solaris 11 SPARC (Solaris Zones Supported) Sun Cluster

Veritas Cluster

UFS, VxFS, VxCFS, ZFS 5 with zpool version 33 Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
Solaris 11 Express   UFS, ZFS 5 with zpool version 33    
Solaris 11 x64   UFS, VxFS, VxCFS, ZFS 5 with zpool version 33 Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

Oracle RAC version 10g R2 or later

SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 12c
Solaris 11.2***   UFS, ZFS 5 with zpool version 35    
SuSE Linux Enterprise Server 10.2 and 11 Veritas Cluster ext2, ext3, ext4, reiserfs, VxFS, VxCFS, IBM General Parallel File System (GPFS)* 3.5.0.7 or later Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

DB2 version 9 or later

Oracle RAC version 10g R2 or later

DB2 DPF version 9 or later

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c
  • *All disks should support snap and must be available on the client where the IntelliSnap job will be initiated.
  • Mount, backup copy, and backup operations are supported using proxy GPFS cluster only; this is due to GPFS's limitation which doesn’t allow NSD clone mount on the same GPFS cluster.
  • You need to set the path to the GPFS binaries in the PATH environment variable for the root user. To do this, 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 Simpana services.

    export PATH=$PATH:/usr/lpp/mmfs/bin

  • ** To enable Red Hat and CentOS 7.x support:

    1. Disable and stop the lvm2-lvmetad service. To do this, run the following command:

    systemctl disable lvm2-lvmetad
    systemctl stop lvm2-lvmetad

    2. Disable lvmetad in to the LVM config file. To do this, run the following command:

    edit /etc/lvm/lvm.conf to include use_lvmetad = 0

  • *** For IntelliSnap operations:
    • For Solaris 11.2, only zpool version 35 is supported.
    • A proxy computer is required.
    • The proxy computer must have the same operating system and zpool version as the source computer.
    • A zpool of the same name must not exist on the proxy computer.
    • Restore operations from a snapshot must use the proxy computer.
    • Revert operations are not supported.

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.

Supported Volume Managers

  • VERITAS Volume Manager (VxVM) 5.x and 6.x for AIX, Linux, Solaris SPARC, Solaris x64, and HP-UX
  • VERITAS CFS (VxCFS) version 5.x and 6.x
  • ZFS or LVM Mirroring on UNIX
  • Solaris Volume Manager
  • ASM Volume Manager

If you use Veritas Volume Manager, you must install the Enterprise license for the useclonedev snapshot feature, which is not enabled in the Standard license. Refer to the Symantec KB article TECH64201 (The "useclonedev" feature requires Enterprise license and is not enabled with the Standard license)

If you use Solaris Volume Manager, ensure that a complete disk is used for a metaset. Also, ensure that the metaset is owned by single host and the ownership of the metaset is attained before performing the IntelliSnap backup operations.Non-metaset volumes are not supported.

Supported Configurations

  • One Physical Volume containing one or more Logical Volumes
  • Multiple Physical Volumes containing one or more Logical Volume

The following diagram summarizes the Volume Manager support for IntelliSnap backup.

Multipath I/O Support

  • For EMC VNX/CLARiiON, IntelliSnap backup is supported on the following MPIO software: EMC Powerpath on AIX, Linux, and Solaris.
  • For Dell EqualLogic, install Dell EqualLogic Host Integration Tools package to support MPIO on Windows.
  • For HDS using CCI engine, HDLM 7.6 is supported on AIX, Linux, and Windows.
  • HP PVlinks, Solaris MPxIO, Linux Device Mapper, and AIX MPIO are supported in HP-UX, Solaris, Linux, and AIX, respectively.
  • VXVM DMP is supported on AIX, Linux, Solaris, and HP-UX.