ADMINISTRATION GUIDE IntelliSnap EMC Isilon

Transcription

1 ADMINISTRATION GUIDE IntelliSnap EMC Isilon Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 44

2 IntelliSnap User Guide - EMC Isilon TABLE OF CONTENTS PRE-DEPLOYMENT UNIX WINDOWS GETTING STARTED OVERVIEW DEPLOYMENT CONFIGURATION SETUP CLIENTS OPTIONS ARRAY MANAGEMENT ARRAY PROPERTIES INTELLISNAP BACKUP - SUPPORT SAPTEST TOOL Published On: 11/19/2013 V10 Service Pack 4A Page 2 of 44

3 IntelliSnap Getting Started EMC Isilon IntelliSnap backup enables you to create a point-in-time snapshot of the data used for backups. An effective way to back up live data is to quiesce it temporarily, take a snapshot, and then resume live operations. IntelliSnap backup works in conjunction with storage arrays to provide snapshot functionality for backup. You can use the IntelliSnap backup to perform any level of backups (for example, Full, Incremental, or Differential). When you switch from a snap to a traditional backup or vice-versa, the next job is converted to a full backup. While you perform an IntelliSnap backup or any subsequent operations, you can use a proxy server to reduce the load on the production server. The backup copy operation uses the proxy to move the snap to backup media. Proxy server is supported with hardware storage arrays. The following illustration describes the process involved in IntelliSnap backup: ADVANTAGES OF USING INTELLISNAP BACKUP The following table lists some of the advantages of using IntelliSnap backup over other available backup solutions. FEATURE SUPPORT Backup to Tape During incremental or log backups only relevant incremental or log data is moved to media which enables significant reduction in media usage. Hardware Independent - No dependency on the hardware array Snapshot copy, backup copy, and tape copy creation and management are seamless. Application aware snapshots creation can be scheduled. The snapshots can be cataloged/indexed for restore and movement to media based on policies. To reduce load on the production server, a proxy server can be used for operations like movement to media and integrity check. Restores can be performed directly from media to the application server. Ability to mix and match IntelliSnap backup with traditional backups. You can perform full IntelliSnap backups combined with incremental log backups that are moved to media. All data management operations can be performed from the CommCell Console. GENERIC SOFTWARE SOLUTION DATA PROTECTION SUITE INTELLISNAP BACKUP HOW DOES INTELLISNAP BACKUP WORK Backup job is scheduled using the CommCell Console. When the backup job is started: The array is accessed to create a snapshot. Published On: 11/19/2013 V10 Service Pack 4A Page 3 of 44

4 The snapshot is mounted on the proxy or source computer for post backup operations. The snapshot is unmounted. This snapshot is used for backup copy operations. This can also be used for restore/mount operations. During the Backup Copy operations: The snapshot is mounted to the source or proxy computer. The mounted snapshot is treated like a file system and the required contents are read. The file system backup is performed on the Primary Copy of the storage policy. When the backup copy job is finished, the snapshot is unmounted. Data Aging: The jobs for the snapshot are pruned based on the retention policy for the snapshot copy. The snapshots that are related to the pruned jobs are deleted from the array periodically. TERMINOLOGY The IntelliSnap Backup documentation uses the following terminology: A device used for backup or archival purposes. STORAGE DEVICE A high-end disk storage system. The IntelliSnap software is designed to work in conjunction with the snapshot STORAGE ARRAY ability built into the storage array. A computer other than the production server on which you can perform IntelliSnap operations. A proxy is PROXY used to decrease the load on the production server. An additional copy of the protected data that is used in IntelliSnap operations. SNAPSHOT COPY Published On: 11/19/2013 V10 Service Pack 4A Page 4 of 44

5 IntelliSnap Getting Started EMC Isilon WHERE TO INSTALL Install the CommServe on a Windows computer that you want to use as your production server. If you have a cluster environment, perform the steps described in Install the CommServe in a Clustered Environment. Follow the steps given below to install the CommServe Modules. BEFORE YOU BEGIN System Requirements Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements. Download Software Packages Download the latest software package to perform the install. INSTALLATION The software can be installed using one of the following methods: METHOD 1: INTERACTIVE INSTALL - STANDARD Use this procedure to install the software using the standard installation options. METHOD 2: INTERACTIVE INSTALL - CUSTOM Use this procedure to install the software by specifying installation settings and options. METHOD 1: INTERACTIVE INSTALL - STANDARD 1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer. 2. Run SetupAll.exe from the Software Installation Discs. 3. Click I accept the terms in the license agreement. Click Next. 4. Click Standard. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 5 of 44

6 5. Click Create a New CommCell. Click Next. 6. The CommServe Module is selected by default. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 6 of 44

7 7. Verify the default location for software installation. Click Next. If necessary, click Browse... to change the default location. Do not install the software to a mapped network drive Do not use the following characters when specifying the destination path: / : *? " < > # It is recommended that you use alphanumeric characters only 8. Click Install. The Search Advanced Document Type Support package is installed along with Web Server. The Summary on your screen should list the components that you selected to install, and might look different from the example shown. Published On: 11/19/2013 V10 Service Pack 4A Page 7 of 44

8 s 9. Click Yes. 10. Select one of the following options: If you do not want to disable Windows Firewall, click Next. If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next. 11. Verify the path to the SQL Server database files. Click Browse to change the default location. Published On: 11/19/2013 V10 Service Pack 4A Page 8 of 44

9 Click Next. Ensure that the drive has at least 1GB of free space. Do not specify a mapped network drive or a FAT drive. Do not save the database files to a compressed drive. 12. Select Create a New Database, and, then click Next. 13. Enter the username and password for the CommCell Console administrator account. Note down the username and password because you need it to access the CommCell Console. Published On: 11/19/2013 V10 Service Pack 4A Page 9 of 44

10 14. Click Next. If you do not want to allow the CommServe to install software and updates to remote client computers, click to clear the Setup Software Cache check box and then click Next. 15. Click Yes. 16. Click Yes to wait for the installer to copy the software packages required for the CommServe. If you want to finish the installation, click No. The software packages will be copied in the background process. Published On: 11/19/2013 V10 Service Pack 4A Page 10 of 44

11 17. Click Finish. DEFAULT OPTIONS SELECTED DURING STANDARD INSTALL Listed below are the default options that are automatically selected while performing the Standard Install. OPTION ENABLED / DESCRIPTION DISABLED Setup Software Cache Enabled This option is used to automatically download software packages and updates from FTP sites. By default, software packages and updates will be stored in the following location: C:\Program Files\hds\Data Protection Suite\SoftwareCache METHOD 2: INTERACTIVE INSTALL - CUSTOM 1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer. 2. Run SetupAll.exe from the Software Installation Discs. 3. Click I accept the terms in the license agreement. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 11 of 44

12 4. Click Custom. Click Next. 5. Click Select components to install on this computer and click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 12 of 44

13 6. Select the following components: Expand CommServe, and then click CommServe. The Web Console, Web Server and Work Flow packages are automatically selected. Expand Consoles, and then click CommCell Console. If you want to install additional CommServe features, expand CommServe and click Operations Manager. To learn the features included in this package, see What are the Components that are included in different Install Packages. Click Next. 7. Verify the installation path of the CommServe database engine. This will be the location for the SQL Server System databases. Click Browse to change the default location, and then click Next. If you plan to perform VSS enabled backups on the CommServe computer, it is recommended that the CommServe database is not installed on the system drive. VSS restores could cause system state restore issues. The install program installs the database instance. Published On: 11/19/2013 V10 Service Pack 4A Page 13 of 44

14 8. Verify the installation path for the Microsoft SQL Server. Click Browse to change the default location, and then click Next. This step might take several minutes to complete. 9. Verify the default location for software installation. Click Next. If necessary, click Browse... to change the default location. Do not install the software to a mapped network drive Do not use the following characters when specifying the destination path: / : *? " < > # It is recommended that you use alphanumeric characters only Published On: 11/19/2013 V10 Service Pack 4A Page 14 of 44

15 10. Click Install. The Search Advanced Document Type Support package is installed along with Web Server. The Summary on your screen should list the components that you selected to install, and might look different from the example shown. 11. Click Yes. 12. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 15 of 44

16 The CommServe Client Name and CommServe Host Name are filled automatically. 13. Select one of the following options: If you do not want to disable Windows Firewall, click Next. If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next. 14. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion List. Click Next. This option enables CommCell operations across Windows firewall by adding CommCell programs and services to Windows firewall exclusion list. It is recommended to select this option even if Windows firewall is disabled. This will allow the CommCell programs and services to function if the Windows firewall is enabled at a later time. Published On: 11/19/2013 V10 Service Pack 4A Page 16 of 44

17 15. Verify the path to the SQL Server database files. Click Browse to change the default location. Click Next. Ensure that the drive has at least 1GB of free space. Do not specify a mapped network drive or a FAT drive. Do not save the database files to a compressed drive. 16. Select Create a New Database, and, then click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 17 of 44

18 17. Specify the network or local path where you want to store the Disaster Recovery backup files. Click Next. If you selected Use Network Path, you must also provide the Network share username and the Network share password. The Network share username is the domain\username of the user that has administrative rights to the Disaster Recovery Backup destination path. The Network share password is the password of the network share username. 18. Enter the username and password for the CommCell Console administrator account. Note down the username and password because you need it to access the CommCell Console. Published On: 11/19/2013 V10 Service Pack 4A Page 18 of 44

19 19. Click Next. If you do not want to allow the CommServe to install software and updates to remote client computers, click to clear the Setup Software Cache check box and then click Next. 20. Skip this step if you did not select the Setup Software Cache option. Specify the path where you want to store the software packages and updates from the FTP site. Click Browse to change the default location, and then click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 19 of 44

20 21. Click Yes. 22. Click Yes to wait for the installer to copy the software packages required for the CommServe. If you want to finish the installation, click No. The software packages will be copied in the background process. 23. Click Finish. Published On: 11/19/2013 V10 Service Pack 4A Page 20 of 44

21 ADDITIONAL INSTALLATION METHODS Install the CommServe in a Clustered Environment Deploy the CommServe in a clustered environment. Install the CommServe with an Existing Database Rebuild the CommServe after a Disaster Recovery. Silent Install Deploy the CommServe silently on a client. Published On: 11/19/2013 V10 Service Pack 4A Page 21 of 44

22 IntelliSnap - Getting Started - EMC Isilon SET UP THE ARRAY INFORMATION Before setting up the array, find out the array name and control host identity in the Isilon OneFS Storage Administration. FIND THE ARRAY NAME Use the OneFS command line to find out the array name: isi target list --lun -v grep EUI tail -1 awk '{print $3}' cut -c 1-12 Use the OneFS Storage Administration tool: 1. From the OneFS Storage Administration interface, click the Cluster Management tab. 2. Click the General Settings tab and the Cluster Identity tab. 3. The first 12 characters of Cluster GUID are name of the array. FIND THE CONTROL HOST IDENTITY Use the OneFS Storage Administration tool: 1. From the OneFS Storage Administration interface, click the Dashboard tab. 2. Click the the Cluster Overview tab and the Cluster Status tab. 3. The Control Host is the external IP or host name of any node of the Isilon cluster. SET UP THE ARRAY The following section provides step-by-step instructions for setting up the array information. 1. From the CommCell Browser, click the Storage tab and then click the Array Management icon. 2. In the Array Management dialog box, click Add. 3. Select Isilon from the Snap Vendor list. Specify the identification information for the storage array in the Name field. Enter the name of the device manager server where the array was configured in the Control Host field. Click Change and enter the access information of user with administrative privileges in the Username and Password fields in Enter User Name and Password dialog box. The user must have root user credentials. Use the Description field to enter a description about the entity. This description can include information about the entity's content, cautionary notes, etc. Click OK to save the information. Published On: 11/19/2013 V10 Service Pack 4A Page 22 of 44

23 Published On: 11/19/2013 V10 Service Pack 4A Page 23 of 44

24 IntelliSnap Getting Started EMC Isilon The following agents are supported for EMC Isilon: SUPPORTED AGENTS - CHOOSE THE AGENT TO CONFIGURE LOTUS NOTES DATABASE UNIX FILE SYSTEM VMWARE WINDOWS FILE SYSTEM Published On: 11/19/2013 V10 Service Pack 4A Page 24 of 44

25 Array Management Use this dialog box to view, add, or modify the access information for an array. AVAILABLE ARRAY This is the list displays all the available arrays in the CommCell. You can associate any array to a subclient and perform the IntelliSnap backup. The list displays following information about each array: Name Name of the array Control Host The name of the device manager server where the array was configured. User Name The user account to be used for accessing the array. Snap Vendor Name The name of the selected snapshot engine vendor for the array. Type Type of array Description The additional information specified for the array. ASSOCIATED ARRAY This is the list displays all the arrays associated with a subclient or a storage policy copy. The list displays following information about each array: Name Name of the array Control Host The name of the device manager server where the array was configured. User Name The user account to be used for accessing the array. Snap Vendor Name The name of the selected snapshot engine vendor for the array. Type Type of array Description The additional information specified for the array. Add Click to access the Array Management dialog box, which enables you to add access information for an array. Edit Click to edit the array information. Delete Published On: 11/19/2013 V10 Service Pack 4A Page 25 of 44

26 Click to delete the access information for an array. List Snaps Click to view the list of snapshots corresponding to the selected array. Note: It is highly recommended that you do not delete an array which has snapshots associated with it. All snapshots associated with a deleted array are no longer valid and cannot be used for any data recovery operations. Published On: 11/19/2013 V10 Service Pack 4A Page 26 of 44

27 Filer Properties (General) - EMC Isilon Snap Vendor Lists the available storage array vendors. In the Snap Vendor box, select the storage array that you want to use. Name Use this field to specify the identification information for the storage array. Control Host Use this field to specify the name of the device manager server where the array was configured. User Account Use this field to type the name of the user account that has rights to access the array. Description Use this field to enter a description about the entity. This description can include information about the entity's content, cautionary notes, etc. The user must have root user credentials. Published On: 11/19/2013 V10 Service Pack 4A Page 27 of 44

28 Filer Properties (Security) - EMC Isilon Use this dialog box to associate user groups who can edit and delete storage arrays. You can do the following using this dialog box: Identify the user groups to which this CommCell object is associated. Associate this object with a user group. Disassociate this object from a user group. Available Groups Displays the names of the user groups that are not associated with this CommCell object. Associated Groups Displays the names of user groups that are associated with this CommCell object. Published On: 11/19/2013 V10 Service Pack 4A Page 28 of 44

29 IntelliSnap Backup - Support TABLE OF CONTENTS Initial IntelliSnap Setup License Requirements Supported Storage Arrays Backup Types Platforms Supported Volume Managers Multipath I/O Support INITIAL INTELLISNAP SETUP Initial deployment and successful run of IntelliSnap backup may take around 4 weeks due to the various environment dependencies. 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 CommCell 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 Data Protection Replication 1 license per CommCell for n Terabytes (TB) of protected data 1 license per CommCell for n Terabytes (TB) of protected data SUPPORTED STORAGE ARRAYS Published On: 11/19/2013 V10 Service Pack 4A Page 29 of 44

30 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/FIRMWARE REQUIRED REQUIRED PROTOCOL NOTES/CAVEATS LICENSING SOFTWARE DELL COMPELLENT DELL EQUALLOGIC Snapshot Snapshot Clone Firmware version and above for 5.x and and above for 6.x. Snapshot Replay licensing None Fibre Channel iscsi Supported on Windows, Linux VMware and HyperV. Compellent Live Volume feature is not supported Included None iscsi On Red Hat Linux and CentOS computers using version 5.5 (32-bit and 64bit) No UNIX 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 Licensing Solutions Enabler or higher on Client and Proxy Navisphere CLI on Client and Proxy NaviAgent on Client and Proxy Fibre Channel FCoE (Fibre Channel over Ethernet)* No HyperV 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 5100, 5300, 5500, 5700, 7500 VNX OE for Block Version or higher is required for VNX Snapshots SnapView Snapshot/Clone Solutions Enabler Licensing Solutions Enabler 7.2 or higher on Client and Proxy Unisphere CLI on Client and Proxy Unisphere Host Agent on Client and Proxy Fibre Channel iscsi VMware with NFS datastores are supported. ISCSI PowerPath LUNs are 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. For configuring a VNX array, refer to the step-by-step instructions provided for EMC Clariion. EMC VNX / CELERRA SnapSure Snap DART 5.5 or Newer SnapSure Snap License Solutions Enabler Licensing Solutions Enabler or higher on Client and Proxy NFS Supported on VMware 4.x. No HyperV Navisphere CLI on Client and Proxy Published On: 11/19/2013 V10 Service Pack 4A Page 30 of 44

31 EMC ISILON Snapshot Support for OneFS 6.5 and OneFS 7.0 SnapshotIQ License iscsi EMC SYMMETRIX EMC VMAX FUJITSU ETERNUS DX HDS AMS TimeFinder Snap, Clone, and Mirror TimeFinder Snap, Mirror and Clone SnapOPC Snap EC Clone Copy-on- Write Shadow Image HDS Shadow Image VSP/HUS-VM USING CCI Thin Image ENGINE HDS HUS Copy-on- Write Shadow Image DMX3 or Newer VMAX Fujitsu ETERNUS V10L or higher ETERNUS DX S2 series - 80, 90, 410, 440, 8100, 8700 AMS 100, 200 & 500 AMS 100, 2100, 2300, & 2500 HDS HUS-VM, VSP HUS 100 series TimeFinder Snap, Mirror, Clone Licenses Solutions Enabler Licensing TimeFinder Snap, Mirror, Clone Licenses Solutions Enabler Licensing Local Copy Thin Provisioning Solutions Enabler 6.4 or higher on Client and Proxy Solutions Enabler 7.2 or higher on Client and Proxy None Licenses for Copy-on- Device Write (COW) snapshot Manager and Shadow Image Licenses for Thin- Image (TI) snapshot and Shadow Image (or higher) Agent installed on Client and Proxy Device Manager Server (or higher) installed on any computer RAID Manager ( /05 or higher) installed on Client and Proxy RAID Manager ( /05 or higher) installed on Client and Proxy Device Licenses for Copy-on- Write (COW) snapshot Manager and Shadow Image (or higher) Agent installed on Client and Proxy Device Manager Fibre Channel FCoE (Fibre Channel over Ethernet)* Fibre Channel FCoE (Fibre Channel over Ethernet)* iscsi Fibre Channel Fibre Channel FCoE (Fibre Channel over Ethernet)* Fibre Channel FCoE (Fibre Channel over Ethernet)* 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 necessary and required for all snap operations. No HyperV 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. No HyperV HDP Volumes not supported for COW. The Virtual Machine HotAdd feature is not supported. SI & TI support for VSP & HUS-VM volumes. Dynamic Provisioned volumes (DP-VOL) are also supported. No HyperV The Virtual Server idataagent must be installed on a physical server and not on a virtual machine. Published On: 11/19/2013 V10 Service Pack 4A Page 31 of 44

32 Server (or higher) installed on any computer The Virtual Machine HotAdd feature is not supported. Copy-on- HDS USP/VSP Write Shadow Image HP EVA HP (HDS OEM) XP, P9500 ARRAYS HP 3PAR EVA Business EVA Copy Snapshot and Clone Licenses for Copy-on- Device Write (COW) snapshot Manager and Shadow Image Copy-on- Write Shadow Image Snapshot and Clone HDS USP, USPv, VSP XP P9500 F-Class and V-Class CIM and higher is installed RAID Manager ( /02 or higher) installed on Client HP Business Copy EVA feature (or higher) Agent installed on Client and Proxy Device Manager Server (or higher) installed on any computer RAID Manager ( /05 or higher) installed on Client and Proxy HP SMI-S EVA on Server Command View Version 9.1, 9.3 Licenses for Copy-on- HP Write (COW) snapshot StorageWorks and Shadow Image Thin Provisioning (4096G) license is required when Thin Provisioning is enabled for Cloning Virtual Copy Command View Advanced Edition Agent (Device Manager or higher) installed on client and proxy computers HP StorageWorks Command View Advanced Edition Server (Device Manager or higher) installed on any computer. HP StorageWorks RAID Manager installed on client and proxy computers. 3PAR SMI-S on Server Fibre Channel FCoE (Fibre Channel over Ethernet)* Fibre Channel iscsi Fibre Channel FCoE (Fibre Channel over Ethernet)* Fibre Channel iscsi No HyperV 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. No HyperV No HyperV The Virtual Machine HotAdd feature is not supported. The snap recovery is supported by retaining the child snap. Also supports (MU4) or higher, except , MU1 + Patch 10, (MU2), Published On: 11/19/2013 V10 Service Pack 4A Page 32 of 44

33 IBM SVC IBM XIV NETAPP E- SERIES (LSI ARRAYS) Flash Copy Spaceefficient Flash Copy SVC / V or higher FlashCopy IBM SMI-S on Server Snap ANY XIV Array Included IBM XCLI 2.3 or higher on Client and proxy Snapshot VolumeCopy Dell MD Series 3000(i), 3200(i), 3220(i) IBM DS , 3300, , 3524, 3950, 4100, 4200, 4300, 4400, , 4800, 5020, 5100, 5300 SGI IS 220, 350, 400, 4xxx, 5xxx SGI TP 9300(s), 9400 (s), 9500(s) Snapshot VolumeCopy LSI SMI-S on Server and server or higher Fibre Channel iscsi Fibre Channel iscsi Fibre Channel iscsi and (MU2) No HyperV Revert operation for space-efficient Flash Copy is not supported. No HyperV LSI Volume Copy is not supported for Hyper-V. Sun - 25xx, 61xx, 65xx, 6780, 9176, FLX210, FLX240, FLX280 NETAPP Snapshot ONTAP or higher ONTAP 8.0.1, 8.0.2, 8.1.0, and mode supported C-mode supported for ONTAP 8.3 FlexClone SnapRestore SnapVault/Mirror for replication OnCommand Fibre Unified Channel Manager - A iscsi server running NetApp NFS OnCommand Unified Manager server software or later, or OnCommand Unified Manager5.x is required. Supported on HP-UX running on Intel Itanium processors using Fiber Channel. Operations Manager, Provisioning Manager, and Protection Manager licenses are required for the OnCommand Unified Manager. OnCommand Unified Manager In order to support the NetApp cluster mode, install OnCommand Unified Manager6.0. SnapMirror - NetApp replication technology used for disaster recovery. SnapVault - NetApp Published On: 11/19/2013 V10 Service Pack 4A Page 33 of 44

34 NIMBLE Snapshot replication technology used for backup and recovery. Included None iscsi Supported on x64- bit Windows, Vmware and Hyper- V. SUPPORTED HARDWARE ARRAYS FOR REPLICATED ENVIRONMENTS VENDOR SNAPSHOT VERSION/FIRMWARE REQUIRED REQUIRED PROTOCOL NOTES/CAVEATS LICENSING SOFTWARE SnapVault NETAPP SnapMirror WITH SNAPVAULT SNAPMIRROR ONTAP or higher ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2 (7-mode supported) ONTAP 8.2 or higher (Cluster mode supported) SnapVault/SnapMirror Primary and Secondary FlexClone SnapRestore OnCommand Unified Manager version (Apr 2011) or OnCommand Unified Manager 5.0 with ONTAP Provisioning Manager, Protection Manager, & Operation Manager Licenses Fibre Channel iscsi NFS CIFS Supported on HP-UX running on Intel Itanium processors using Fiber Channel. vfilers as a destination supported for Netapp 7-mode. vfilers as NFS/CIFS share sources will have no indexing due to lacking SnapDiff support. OnCommand Unified Manager 6.0 for ONTAP 8.2 or higher (Cluster 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/FIRMWARE REQUIRED REQUIRED NOTES/CAVEATS LICENSING SOFTWARE DATA REPLICATOR Not applicable Not applicable Local native snapshot license (Volume manager snapshot license or QSnap license) ContinuousDataReplicator Oracle Solaris Solaris ZFS Hardware Snap Engine or native snap or QSnap license Solaris (Global zone only) Local native Solaris OS has ZFS snap snapshot license capability Set the EnableNativeSnapEngine global parameter to 1 using the SetKeyIntoGlobalParam qscript. Example: qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si EnableNativeSnapEngine - si y -si 1 Published On: 11/19/2013 V10 Service Pack 4A Page 34 of 44

35 LUNs should be from same storage array. LUNs from different storage arrays of same model/vendor or different models/vendors are 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 may occur if these operations are performed from one of the servers in the cluster. The use of iscsi is not supported when performing IntelliSnap operations on computers running Solaris. Boot from SAN volumes is not supported. IntelliSnap backups of Raw Device Map (RDM) disks are supported for any Windows-based agents configured in a virtual machine in physical compatibility mode, provided that iscsi initiator is configured on the client computer to mount the Snapshot or Physical proxy server is configured to mount Snapshot over Fibre Channel This capability is not supported for HDS storage arrays. NAS attached tape libraries are not supported for IntelliSnap operations. For information on the supported snapshot engines, see Hardware Snapshot Engine Compatibility Matrix. 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 VIRTUAL SERVER (VMWARE) EXCHANGE DATABASE Lotus Notes Database MYSQL ORACLE DIFFERENTIAL BACKUP NOTES Before performing revert operations, ensure that all the disks reside on the NFS data store. If the data does not reside on the 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 backups are not supported on Exchange 2007 CCR Passive nodes. DDR snapshots are not supported on Exchange 2010 DAG clients. SRM is not supported. 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. Incremental backups are applicable for Backup copies. Published On: 11/19/2013 V10 Service Pack 4A Page 35 of 44

36 ORACLE RAC MICROSOFT SQL SERVER NAS VIRTUAL SERVER (HYPER-V) Incremental backups are applicable for Backup copies. Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy. IntelliSnap backups support online virtual machines with NetApp file servers. Other storage array vendors use the traditional backup method. To perform a IntelliSnap backup, the virtual machine must be offline. SAP ORACLE DB2 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 LVM configuration is not supported. On HP-UX, non-lvm volumes are not supported for IntelliSnap Backup. WINDOWS FILE SYSTEM On Demand Backup Set is not supported for IntelliSnap Backup. 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, IntelliSnap backups are supported for clients using the 32-bit packages of Data Protection Suite. OPERATING CLUSTER SUPPORT FILE SYSTEMS DATABASES APPLICATIONS SYSTEM WINDOWS 2003 AND HIGHER MSCS NTFS SQL version 2005 and later Exchange 2003, 2007, 2010, 2013 including DAG Oracle 10g R2, Oracle 11g R1 & R2 DB2 version 9 or higher Published On: 11/19/2013 V10 Service Pack 4A Page 36 of 44

37 VMWARE ESX iscsi/fc/nfs datastores ESX vsphere 4.x & vsphere 5.0 AIX 5.3, 6.1, 7.1 (LPARS SUPPORTED, VIRTUAL SCSI DEVICES NOT SUPPORTED) Veritas Cluster, HACMP JFS, JFS2, VxFS, VxCFS, IBM General Parallel File System (GPFS)* or higher Oracle 10g R2, Oracle 11g R1 & R2 DB2 version 9 or higher Oracle RAC version 10g R2 or higher DB2 DPF version 9 or higher SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2 HP-UX 11 V2/V3 (PA- RISC AND ITANIUM) Service Guard, Veritas Cluster HFS, VxFS, VxCFS Oracle 10g R2, Oracle 11g R1 & R2 DB2 version 9 or higher Oracle RAC version 10g R2 or higher SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2 ORACLE ENTERPRISE LINUX 5.X AND 6.X RED HAT LINUX 4.X AND 5.X CENTOS LINUX 4.X AND 5.X RED HAT LINUX 6.X CENTOS LINUX 6.X Linux Cluster, Veritas Cluster Linux Cluster Linux Cluster, Veritas Cluster Linux Cluster ext2, ext3, ext4, reiserfs, VxFS, VxCFS, OCFS2 ext2, ext3, ext4, reiserfs, VxFS, OCFS2, VxCFS, IBM General Parallel File System (GPFS)* or higher ext2, ext3, ext4, reiserfs, OCFS2 ext2, ext3, ext4, reiserfs, VxFS, VxCFS, OCFS2, IBM General Parallel File System (GPFS)* or higher ext2, ext3, ext4, reiserfs, OCFS2 DB2 DPF version 9 or higher Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher DB2 DPF version 9 or higher Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher DB2 DPF version 9 or higher Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher DB2 DPF version 9 or higher Oracle 10g R2, Oracle 11g R1 & R2; Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher DB2 DPF version 9 or higher Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2,Oracle 12c SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 DPF version 9 or higher SOLARIS 10 SPARC (SOLARIS ZONES SUPPORTED) Sun Cluster, Veritas Cluster UFS, VxFS, VxCFS, ZFS Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 DPF version 9 or higher Published On: 11/19/2013 V10 Service Pack 4A Page 37 of 44

38 SOLARIS 11 SPARC (SOLARIS ZONES SUPPORTED) Sun Cluster, Veritas Cluster UFS, VxFS, VxCFS, ZFS Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 DPF version 9 or higher SOLARIS 11 EXPRESS UFS, ZFS SOLARIS 11 X64 SUSE LINUX ENTERPRISE SERVER 10.2 AND 11 Veritas Cluster UFS, VxFS, VxCFS, ZFS ext2, ext3, ext4, reiserfs, VxFS, VxCFS, IBM General Parallel File System (GPFS)* or higher Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c Oracle RAC version 10g R2 or higher Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c DB2 version 9 or higher Oracle RAC version 10g R2 or higher DB2 DPF version 9 or higher SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 12c SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c *All the 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. 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.0 for AIX, Linux, Solaris SPARC and Solaris x64 VERITAS CFS (VxCFS) version 5.1 or higher Solaris ZFS Mirror Solaris Volume Manager ASM Volume Manager When using the Solaris Volume Manager, ensure that a complete disk is used for a metaset. Non-metaset volumes are not supported. Also, ensure that the metaset is owned by single host and the ownership of the metaset is attained before performing the IntelliSnap backup operations. Supported Configurations: One Physical Volume containing one Logical Volume One Physical Volume containing one or more Logical Volumes Multiple Physical Volumes containing one Logical Volume 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 Multipath I/O software. This support is provided using Published On: 11/19/2013 V10 Service Pack 4A Page 38 of 44

39 the SNAP_WITH_MULTIPATH_SOFTWARE additional setting. EMC Powerpath on AIX, Linux and Solaris. For Dell EqualLogic, install Dell EqualLogic Host Integration Tools package to support Multipath I/O. HP PVlinks, Solaris MPxIO, Linux Device Mapper and AIX MPIO are supported in HPUX, Solaris, Linux and AIX respectively. VXVM DMP is supported in AIX, Solaris and HPUX. HDLM is not a supported MPIO solution with IntelliSnap. Published On: 11/19/2013 V10 Service Pack 4A Page 39 of 44

40 IntelliSnap Backup - SnapTest Tool TABLE OF CONTENTS Overview Usage Setup Array Configuration Prerequisites Exercise Vendor Snap Engine Detect Snap Engine Type Show HBA/iSCSI Address Send SCSI inquiry to mount point Mount Snapshot on Proxy OVERVIEW The SnapTest tool is used to test basic snap engine operations and as a diagnostic tool to verify host and array connections. The SnapTest tool is capable of working with multiple mount points for each operation and supports interactive and command line modes. PREREQUISITES MediaAgent installed on the computer for SnapTest. USAGE Use the SnapTest tool to derive the HBA/iSCSI, the vendor, product, and version details for an array. You can also use the SnapTest tool to: create, mount, unmount, delete, revert snapshots for an array. test proxy computers by mounting snapshots. By default, when Data Protection Suite installation is decoupled, the SnapTest tool will be started in decoupled mode. If Data Protection Suite is in normal mode, then start the SnapTest in decoupled mode. Use the command line: SnapTest -local When multiple instances are installed on the system, the default instance will be selected. To select a specific instance, use the command: SnapTest -vm <InstanceName> SETUP ARRAY CONFIGURATION Set up the array once, for each new array you will use. The setup is mandatory in decoupled mode and you need to do it before doing any snap operation. To set up the array information: 1. Navigate to <installed_directory>\base and double-click SnapTest.exe. 2. In the Introductory dialog box, press Enter. 3. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 4. In the Advanced Operations dialog box, type 2 for Array Configuration and press Enter. 5. In the Configure Arrays dialog box, press Enter to add a new array. 6. In the Add Array dialog box, specify the number corresponding to the snap engine vendor to add and press Enter. 7. Specify the following information for the detected array: Array ID Published On: 11/19/2013 V10 Service Pack 4A Page 40 of 44

41 Control host name/ip User name Password Reenter password Device group Use only devices belonging to the above device group [y/n] EXERCISE VENDOR SNAP ENGINE To create, mount, unmount, delete, revert snapshots for an array. 1. Navigate to <installed_directory>\base and double-click SnapTest.exe. 2. In the Introductory dialog box, press Enter. 3. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 4. In the Advanced Operations dialog box, press Enter to Perform individual Snap Operations. 5. In the Snap Engine Test dialog box, specify the number corresponding to the snap engine and press Enter. 6. In the Exit dialog box, specify the operation. For e.g., type 1 to create a snapshot and press Enter. DETECT SNAP ENGINE TYPE To detect the type of storage array in your environment: 1. Navigate to <installed_directory>\base and double-click SnapTest.exe. 2. In the Introductory dialog box, press Enter. 3. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 4. In the Advanced Operations dialog box, type 3 for Miscellaneous Tasks and press Enter. 5. In the Miscellaneous Tasks dialog box, press Enter to Detect Snap Engine Type. This will prompt you to specify the source mount path. 6. In the Snap Engine Detection, specify the source mount path or the device path and press Enter. The mount path should be specified as follows, <drive>:\\ For example: f:\\ The snap engine type configured for the mount or device path is displayed, press Enter to continue SHOW HBA/ISCSI ADDRESS To derive the HBA/iSCSI information for an array: 1. Navigate to <installed_directory>\base and double-click SnapTest.exe. 2. In the Introductory dialog box, press Enter. 3. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 4. In the Advanced Operations dialog box, type 3 for Miscellaneous Tasks and press Enter. 5. In the Miscellaneous Tasks dialog box, type 2 and press Enter to Show HBA/iSCSI address. 6. In the List Adapters dialog box, press Enter to List Adapters. This will prompt you to enter the name of the snap engine. The HBA/iSCSI information including the WWPN number for the fiber card is displayed. SEND SCSI INQUIRY TO MOUNT POINT To derive the vendor information for an array: Published On: 11/19/2013 V10 Service Pack 4A Page 41 of 44

42 1. Navigate to <installed_directory>\base and double-click SnapTest.exe. 2. In the Introductory dialog box, press Enter. 3. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 4. In the Advanced Operations dialog box, type 3 for Miscellaneous Tasks and press Enter. 5. In the Miscellaneous Tasks dialog box, type 3 and press Enter to Send SCSI inquiry to mount point. This will prompt you to enter the name of the snap engine. 6. In the Send SCSI Inquiry dialog box, type the drive letter of mount directory and press Enter. The vendor information, source path, and the mount path details are displayed. MOUNT SNAPSHOT ON PROXY To create a snapshot on your source computer and mount it to a proxy computer: 1. Navigate to <installed_directory>\base and double-click SnapTest.exe. 2. In the Introductory dialog box, press Enter. 3. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 4. In the Advanced Operations dialog box, press Enter to Perform individual Snap Operations. 5. In the Snap Engine Test dialog box, specify the number corresponding to the snap engine and press Enter. This will prompt you to specify the Mount points to snap. 6. In the SnapTest Create Snap, specify the drive letter of mount directory and press Enter, for example: Enter all the mount points that you want to test separated by commas, if more than one. E:\ 7. In the SnapTest Create Snap dialog box, a message will appear to indicate the creation of the snapshot, press Enter to continue. 8. Type 0 and press Enter until you exit the tool. 9. Navigate to <installed_directory>\base and copy the SnapTestSnapInfo.xml file to a temporary location on the proxy computer. 10. Connect to the proxy computer and do the following: Rename the current SnapTestSnapInfo file to SnapTestSnapInfo_old. Copy the new SnapTestSnapInfo.xml file to the <installed_directory>\base folder. Double-click SnapTest.exe to start the tool. 11. In the Introductory dialog box, press Enter. 12. In the Main Menu dialog box, type 2 for Advanced Operations and press Enter. 13. In the Advanced Operations dialog box, press Enter to Perform individual Snap Operations. 14. In the Snap Engine Test dialog box, specify the number corresponding to the snap engine and press Enter. 15. In the Snap Engine Test dialog box, type 3 to Mount Snap and press Enter. 16. Type the number corresponding to the snapshot you want to mount and press Enter. This will prompt you to type the Snap numbers to mount. Type the numbers separated by commas, if more than one and press Enter. 17. The snapshot is successfully mounted on the proxy computer. 18. To remove the snapshot after perform the test: Type 0 and press Enter until you exit the tool. Navigate to <installed_directory>\base and remove the SnapTestSnapInfo.xml file you copied. Published On: 11/19/2013 V10 Service Pack 4A Page 42 of 44

43 Rename the SnapTestSnapInfo_old file to SnapTestSnapInfo. Back to Top CommVault Systems Inc. All rights reserved. This document may not be copied or further distributed, in whole or in part, without written permission from CommVault Systems Inc. Published On: 11/19/2013 V10 Service Pack 4A Page 43 of 44

44 Published On: 11/19/2013 V10 Service Pack 4A Page 44 of 44