Administration GUIDE

IntelliSnap EMC CLARiiON/VNX

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

IntelliSnap User Guide - EMC Clariion/VNX
Table of Contents
Pre-Deployment

UNIX

Windows

Getting Started

Overview

Prerequisites

Deployment

Configuration

Setup Clients

Online Help

Array Management

Array Properties

Best Practices

Frequently Asked Questions

Troubleshooting

IntelliSnap Backup - Support

SnapTest Tool

White Papers

IntelliSnap Guide For EMC CLARiiON Storage Systems

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

Pre-Deployment Test - Unix
Unix Windows

Table of Contents
Installation

Perform Test

Installation
1. Logon to the client computer as root.
2. If you are installing the software from the Software Installation Discs, run the following command to mount the
CD:

mount -t iso9660,udf /dev/cdrom /mnt/cdrom

Run the following command from the Software Installation Package or mount point:

./cvpkgadd

You can also run this command as a SUDO user with root privileges:

./sudo cvpkgadd

For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install.
3. The product banner and other information is displayed.

Press Enter.

4. Read the license agreement. Type y and press Enter.

5. Type 2 and press Enter.

Selecting Unix Setup Task

Please select a setup task you want to perform from the list below:
Advanced options provide extra setup features such as creating custom package,recording/replaying user
selections and installing External Data Connector software.
1) Install data protection agents on this computer
2) Advanced options
3) Exit this menu
Your Choice: [1] 2

6. Type 2 and press Enter.

This screen will appear only on AIX and Solaris platform.

Selecting 32bit or 64bit Base

This machine supports both 32 bit and 64 bit binaries. By default, we will
install 32 bit binary set that has full support for all the modules included in
this package. Please note that 64 bit binary set currently only support limited
modules
1) All platforms(32 bit)
2) FS and MA only(64 bit)
Your Choice: [2]

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

 7. Type 2 and press Enter.

Selecting Unix Setup Advanced Options

Please select a setup task you want to perform from the list below:
[Custom Package Creator]
1) Create a custom install package
[De-coupled Installer]
2) Pre-install software Components (De-coupled Mode)
[Done]
3) Exit this menu
Your Choice: [1] 2

8. The default network interface name of the client computer is displayed if the computer has only one network
interface (NIC card), press Enter to accept.
{ If the computer has multiple network interfaces, enter the interface name that is preferred for
communication with the CommServe, and then press Enter.
The interface names and IP addresses depend on the computer in which the software is installed and may be
different from the example shown.

Setting Client/Physical Machine Host Name

We found one network interface available on your machine. We will associate it with the client being installed,
and it will also be used by the CommServe to connect to the client. Note that you will be able to additionally
customize Datapipe Interface Pairs used for the backup data traffic later in the Data Protection Suite Java GUI.
Please check the interface name below, and make corrections if necessary:
Client/Physical Machine Host Name: [myclient.company.com]

9. The local name of the client computer is displayed, press Enter to accept.

{ If necessary you can also enter a new (friendly) name for the client, and then press Enter. This name will
be used in the CommCell and will also be displayed in the CommCell Console.
{ Do not use spaces when specifying a new name for the client.

Setting Client Name

Please specify the client name for this machine.
It does not have to be the network host name: you can enter any word here without spaces. The only requirement
is that it must be unique on the CommServe.
Physical Machine Client name: [myclient]

10. Type the number associated with File System and MediaAgent and then press Enter.

Selecting Modules to Install.

[ ] 1) File System Core [1002] [CVGxBase]
[ ] 2) File System [1101] [CVGxIDA]
[ ] 3) MediaAgent [1301] [CVGxMA]
[ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA]
[ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA]
[ ] 6) SAP for Oracle [1205] [CVGxOrSAP]
[ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB]
[ ] 8) Informix iDataAgent [1201] [CVGxIfIDA]
[ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA]
[ ] 10) DB2 iDataAgent [1207] [CVGxDB2]
[ ] 11) MySQL iDataAgent [1208] [CVGxMySQL]
[ ] 12) PostGres iDataAgent [1209] [CVGxPostGres]
[ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]
>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>
[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 2 3

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

11. Type d for Done, and press Enter.

Selecting Modules to Install.

[ ] 1) File System Core [1002] [CVGxBase]
[X] 2) File System [1101] [CVGxIDA]
[X] 3) MediaAgent [1301] [CVGxMA]
[ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA]
[ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA]
[ ] 6) SAP for Oracle [1205] [CVGxOrSAP]
[ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB]
[ ] 8) Informix iDataAgent [1201] [CVGxIfIDA]
[ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA]
[ ] 10) DB2 iDataAgent [1207] [CVGxDB2]
[ ] 11) MySQL iDataAgent [1208] [CVGxMySQL]
[ ] 12) PostGres iDataAgent [1209] [CVGxPostGres]
[ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]
>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>
[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

12. Press Enter.

Deciding if to Config for Laptop or Desktop Backups

Do you want to configure the iDataAgent for laptop or desktop backups?
Config for Laptop or Desktop Backups? [no]

13. Press Enter.

Deciding if to Install Agents for Restore Only

Do you want to install the agents for restore only without consuming licenses?
Install Agents for Restore Only? [no]

14. Verify the default path for software installation.

Press Enter.

If necessary, enter a path to modify the default path and press Enter.

{ Do not install the software to a mapped network drive

{ Do not use the following characters when specifying the path:

!@#$%^&*():/?\

{ It is recommended that you use alphanumeric characters only

Preparing Installation Directory

Please specify where you want us to install Data Protection Suite binaries.
It must be a local directory or NFS and there should be at least 281MB of free space available. All files will be
installed in a "hds" subdirectory, so if you enter "/opt", the files will actually be placed into "/opt/hds".
Installation Directory: [/opt]

15. Verify the default path for log files.

Press Enter.

If necessary, enter a path to modify the default path and press Enter.

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

 { Do not use the following characters when specifying the path:

!@#$%^&*():/?\

{ It is recommended that you use alphanumeric characters only

{ All the modules installed on the computer will store the log files in this directory.

Preparing Log Directory

Please specify where you want to keep Data Protection Suite log files.
It must be a local directory or NFS share and there should be at least 100MB of free space available. All log
files will be created in a "hds/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed
into "/var/log/hds/Log_Files".
Log Directory: [/var/log]

16. Press Enter.

Deciding If to Use a Unix Group

Most of Data Protection Suite processes run with root privileges, but some are launched by databases and inherit
database access rights. To make sure that registry and log files can be written to by both kinds of processes we
can either make such files world-writeable or we can grant write access only to processes belonging to a
particular group, e.g. a "hds" or a "dba" group.
We highly recommend now that you create a new user group and enter its name in the next setup screen. If you
choose not to assign a dedicated group to Data Protection Suite processes, you will need to specify the access
permissions later.
If you're planning to backup Oracle DB you should use "dba" group.
Would you like to assign a specific group to Software? [yes]

17. Type the Group name and press Enter.

Press Enter again.

Setting Unix Group

Please enter the name of the group which will be assigned to all Data Protection Suite files and on behalf of
which all Data Protection Suite processes will run.
In most of the cases it's a good idea to create a dedicated "hds" group.
However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group
here.
Group name: testgrp1
REMINDER
If you are planning to install Data Protection Suite Informix, DB2, Sybase or Lotus Notes iDataAgent, please
make sure to include Informix, DB2, etc. users into group "testgrp1"..
Press <ENTER> to continue...

18. Type d for done with the selection and press Enter.

Setting Access Permissions for Group and Other Users

Installer will assign full access rights to root user for all installed Data Protection Suite files and its processes.
For group and any other users, you can specify the access permissions now.
If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other
users if you are also planning to install Data Protection Suite agents involving third party software protection.
[X] 1) Allow read permission to group users
[X] 2) Allow write permission to group users
[X] 3) Allow execute permission to group users
[X] 4) Allow read permission to other users
[ ] 5) Allow write permission to other users
[X] 6) Allow execute permission to other users
[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]

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

 Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

19. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the
port numbers.

Press Enter.

Setting Instance Port Number of cvd

Every instance of Data Protection Suite should use a unique set of network ports to avoid interfering with other
instances running on the same machine.
The port numbers selected must be from the reserved port number range and have not been registered by another
application on this machine.
Please enter the port numbers.
Port Number for CVD : [8400]

20. Press Enter.

Port Number for EvMgrC: [8402]

21. Do one of the following:

{ If firewall configuration is not required, press Enter.
{ If this computer and the CommServe is separated by a firewall, type Yes and then press Enter.

For firewall options and configuration instructions, see Firewall Configuration.

Deciding If to Configure Firewall

You need to configure firewall settings if there is a firewall between this
client and the CommServe.
Is there a firewall between this client and the CommServe? [no]

22. Press Enter.

Setting CommServe Host Name

Please specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the
name services configured on this machine.
CommServe Host Name:

23. Press Enter.

Deciding if to Install Decoupled

If you do not enter a CommServe name, the installer will treat it as a
decoupled install. Please confirm this is really what you want.
Do you want to treat the install as a decoupled install? [yes]

24. If you have enabled per-client certificate on CommServe, type y and press Enter.

Else, press Enter.

Specifying If CommServe Per-Client Certificate is Enabled

If you have checked "Force per-client certificate authentication on CommServe" on the CommServe or Proxy,
you need to provide installer with a Temp Certificate.
This Temp Certificate can be obtained by opening "Certificate Administration Applet" from the Java GUI's
Control Panel, clicking "Temp Certificate" button, selecting newly created client in the popped up window and
copying/pasting generated certificate to a local file accessible from this installer.
Have you enabled per-client certificate authentication on CommServe? [no]

25. To review the setup, you may find the following logs useful if available:

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

 Thank you for choosing Hitachi Data Systems Systems, Inc. Data Protection Suite.
[LOG INFO] To review the setup, you may find the following logs useful if available:
(1) logs under /tmp/.gxsetup
(2) install.log|env and UpdateInfo.log|env under Log Directory
(3) logs under /var/log/.gxsetup/10-116

Perform Test
The following procedure provides step-by-step instructions to configure and test your snap environment.

1. Create a Lun on the array and map it to the client computer.

Ensure that the Lun is visible on the client computer as a device node.

2. Use the mapped device node to create a Volume Group.

For example, use the following command:

On AIX

mkvg –y vg_name hdisk12

On Linux:

pvcreate /dev/sdd
vgcreate vg_name /dev/sdd
vgchange –a y vg_name

3. Create a Logical Volume in the Volume Group.

For example, use the following command:

On AIX:

mklv -y lv_name -t jfs2 vg_name 2G hdisk29

On Linux:

lvcreate –n lv_name –L 2G vg_name

4. Create a File System on the Logical Volume.

For example, use the following command:

On AIX:

crfs -v jfs2 -a logname=INLINE -d lv_name -m /snaptest

On Linux:

mkfs -t ext3 /dev/vg_name/lv_name

5. Use the following commands to run the Snaptest tool:

{ Locate /opt/Simpana folder by running the below command.

[root@ntr Simpana]# cd /opt/Simpana/Base

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

 { [root@ntr Simpana]# ./SnapTest
If you have multiple instance installed, run the following command for SnapTest tool:

[root@ntr Simpana]# ./SnapTest -vm Instance<XXX>

6. Press Enter.

This tool helps to perform operations such as...

-> Automatic Snap Tests
-> Individual Snap Tests
-> Hardware Snapshot Engine Detection
-> SCSI Inquiry
-> Scan HBA/IQN Adapters
NOTE: Please make sure that the mount points used for this test are not
being used by any other application. If they are in use, it may cause data
corruption or data loss. Please refer to our online documentation for list
of supported Operating systems, Hardware Snapshot engines and File systems.
Press <ENTER> to continue...

7. Press Enter.

SnapTest Version Main Menu

--------------------------------------
Perform automatic snap tests or launch Advanced Operations such as Array
Configuration, Snapshot Engine Detection etc. Automatic snap tests take one
or more source mounts to snap and performs series of Snap related
operations on them. In order to perform these snap operations, array
configuration such as array id, control host and user credentials is
required. If no array configuration is found, Automatic Snaptests takes you
to Array Configuration screen.
1. Automatic Snap Tests
2. Advanced Operations
0. Exit
Choose your option [1]:

8. Type Y and press Enter.

SnapTest Automatic Snap Operations

-----------------------------------------------------
We will perform the following operations on the given mount point[s].
- Create snapshots
- Mount snapshots
- Unmount snapshots
- Revert original volumes to snapshots
- Delete snapshots
WARNING:
Revert is inherently risky and can cause data loss.
Do you want to perform revert operation as part of this test? [Y/N] [N] : Y

For NetApp, it is recommended that the revert operation is not tested

using the automatic test. Revert should be tested using manual
operations.
9. Specify the path of mount directory and press Enter.
Enter all the mount points that you want to test.

Enter source mount paths to snap (separate by commas, if more than

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

 one) : /snap1

10. Press Enter to add the detected array.

SnapTest Automatic Snap Operations

-----------------------------------------------------------
Source Mount Point : /snap1
Detecting underlying devices... /dev/sdh
Detecting snapshot engine... <Array Name> SNAP
No [<Array Name> SNAP] arrays found in database. Array configuration is
required to do snap operations.
Do you want to add <Array Name> Array? [Y/N] [Y] :

11. Specify the following information for the detected array:

{ Array ID
{ Control host name/ip
{ User name
{ Password
{ Reenter password
{ Device group
{ Use only devices belonging to the above device group [y/n]

SnapTest Add Array

-----------------------------------
Vendor : <Array Name>
Enter array ID :
Enter control host name/ip :
Enter user name :
Enter password :
Enter password again :
Enter device group :

12. The setup is tested for snapshot operations (create, mount, unmount, revert, and delete).

The snap test is now complete. You can now use this environment for performing IntelliSnap operations.

SnapTest Automatic Snap Operations

------------------------------------------------------------
Mount points to be snapped : /snap1
Engine for /snap1 : <Array Name> SNAP
Creating snapshot... SUCCESS
Snapshot name : SP_805326_805326_-1
Mounting snapshot...SUCCESS
Unmounting snapshot... SUCCESS
Reverting to snapshot... SUCCESS
Deleting snapshot... SUCCESS
Congratulations!!! Automatic Snap test completed successfully.
Press <ENTER> to continue...

13. Type 0 and press Enter.

SnapTest Version Main Menu

--------------------------------------
Perform automatic snap tests or launch Advanced Operations such as Array
Configuration, Snapshot Engine Detection etc. Automatic snap tests take one
or more source mounts to snap and performs series of Snap related

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

 operations on them. In order to perform these snap operations, array
configuration such as array id, control host and user credentials is
required. If no array configuration is found, Automatic Snaptests takes you
to Array Configuration screen.
1. Automatic Snap Tests
2. Advanced Operations
0. Exit
Choose your option [1]:

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:

z Firmware versions on the array

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





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

Pre-Deployment Test - Windows
Unix Windows

Table of Contents
Installation

Perform Test

Installation
The following sections describe the steps involved in installing the components using the Decoupled Installation
package:

1. Create Decoupled Installation Package

2. Install Using the Decoupled Installation Package

Create Decoupled Installation Package

Use the following steps to create the Decoupled install package

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 Custom.

Click Next.

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

 5. Click Create a custom package to install on a different computer and click Next.

6. Click Create a Recording of Packages.

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

 7. Click Next.

8. 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 101

 9. Click Next.

10. Select the Software edition of the Custom Package you want to create.

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

11. Specify the location where you wish to create the custom package. By default the custom package is created at
C:\CustomInstallPackageName.

Specify a folder under any drive. If the folder does not exist, it is automatically created.
Do not use the following characters when specifying the destination path:
/:*?"<>|
It is recommended that you use alphanumeric characters only.

Click Browse to change directories.

Click Next to continue.

12. Select one of the following:

{ Select Create a new instance option to install the Agents as a new instance.

If you select this option and create a custom package, later when you install the Agents using this
custom package, the Agents will always be installed as a new instance irrespective of the existence of
any other instances on the client computer.
{ Select Install to existing instance to install the Agents to a specific instance existing on the client
computer.

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

 From the Select an instance drop-down list, select the instance name to which you want the agents to be
added at the time of installation.

Make sure that the instance name that you select here exists on the client computers on which you
would install the agents using this custom package. Once you specify the instance name and create a
custom package, later when you install the Agents using this custom package on a client computer, the
Agents will always be installed to the instance that you specify in this step. If the installer does not find
any matching instance name on the client computer, then a new instance with this name will be created
and the Agents will be installed to this instance

Click Next.

13. Select the components that you want to install.

If you have plans to create a De-coupled custom package, the components that you select here will be included
in the De-coupled custom package.
Click Next.

14. Click Next.

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

 z If you want to include .NET Framework 4.0 Installer in the custom package, select Include .NET
Framework 4.0 Installer.
z If you just want to create an answer file without creating the package, select Create answer file
(without packages). If you select this option, the self-extracting executable will not be created.

15. Select one of the following:

{ If firewall configuration is not required, click Next.

{ If this computer and the CommServe is separated by a firewall, click Configure firewall services.

For firewall options and configuration instructions, see Firewall Configuration and continue with the
installation.

If you want this screen to be displayed while installing the components from the custom package, select the
Show to user check box.

16. Click Next.

CommServe name can be specified later.

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

 If you want this screen to be displayed while installing the components from the custom package, select the
Show to user check box.

17. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the
port numbers.

Click Next.

This screen will not appear if the default port numbers are not used for CommCell communication.

If you want this screen to be displayed while installing the components from the custom package, select the
Show to user check box.

18. Verify the default location for software installation.

Click Next.

If necessary, click Browse... to change the default location.

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

 { 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

If you want this screen to be displayed while installing the components from the custom package, select the
Show to user check box.

19. Select one of the following:

{ Click Use Cell level Policy to inherit the global filter policy configuration set for the CommCell.
{ Click Always use Global Filters to apply the global filters policy to the default subclient regardless of the
policy set for the CommCell.
{ Select Do not use Global Filters if you plan to define specific filters for the Agent.

Click Next.

If you want this screen to be displayed while installing the components from the custom package, select the
Show to user check box.

20. Select the Configure for Laptop or Desktop Backup option to install Backup Monitor utility. This utility

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

 allows you to view the backup job summary from the client computer without opening the CommCell Console.
See Monitor - Laptop User for more information.

Select the Contact the master CommServe to perform automatic registration option if you have plans to
deploy this installation package to multiple client computers and want each client computer to to be
automatically registered to the appropriate CommServe of your choice.

Click Next.

If you want this screen to be displayed while installing the components from the custom package, select the
Show to user check box.

21. Click Finish.

This screen will reflect the components you selected for install, and may look different from the example
shown.

Install Using the Decoupled Installation Package

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

Use the following procedure to install the De-Coupled package:

1. Locate the custom package and double-click the .exe file to start the installation. For example:
For a Windows X64 system using default paths, this file can be located at
C:\CustomPackageName\CustomPackageName_WinX64

If you want to install this de-coupled package on a different computer, you must copy the executable file to the
desired client computer and double-click the .exe file.

2. Custom Installation Package screen will be displayed. Click k Next to continue.

3. Provide a path for the installer to extract the installation package.

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

 4. The installation proceeds silently. This may take several minutes to complete.

5. Click OK on the dialog box.

6. Click Finish.

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

 7. In the Administrative Console (Register Me tab).

Specify the Username and Password to register to the CommServe.

This screen will be displayed only when you select the create de-coupled installation package option while
creating the decoupled install package (step 14).

Perform Test
The following procedure provides step-by-step instructions to configure and test your snap environment.

1. Create a Lun on the array and map it to the client computer.

Ensure that the Lun is visible on the client computer as a Disk.

2. Using the Disk Management on the client computer locate the disk and assign a drive letter.
3. Create a directory to mount snapshots.
4. Navigate to <installed_directory>\Base and double-click SnapTest.exe.

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

 5. Press Enter.

This tool helps to perform operations such as...

-> Automatic Snap Tests
-> Individual Snap Tests
-> Hardware Snapshot Engine Detection
-> SCSI Inquiry
-> Scan HBA/IQN Adapters
NOTE: Please make sure that the mount points used for this test are not
being used by any other application. If they are in use, it may cause data
corruption or data loss. Please refer to our online documentation for list
of supported Operating systems, Hardware Snapshot engines and File systems.

Press <ENTER> to continue...

6. Press Enter.

SnapTest Version Main Menu

--------------------------------------
Perform automatic snap tests or launch Advanced Operations such as Array
Configuration, Snapshot Engine Detection etc. Automatic snap tests take one
or more source mounts to snap and performs series of Snap related
operations on them. In order to perform these snap operations, array
configuration such as array id, control host and user credentials is
required. If no array configuration is found, Automatic Snaptests takes you
to Array Configuration screen.
1. Automatic Snap Tests
2. Advanced Operations
0. Exit
Choose your option [1]:

7. Type Y and press Enter.

SnapTest Automatic Snap Operations

-----------------------------------------------------
We will perform the following operations on the given mount point[s].
- Create snapshots
- Mount snapshots
- Unmount snapshots
- Revert original volumes to snapshots
- Delete snapshots
WARNING:
Revert is inherently risky and can cause data loss.
Do you want to perform revert operation as part of this test? [Y/N] [N] : Y

For NetApp, it is recommended that the revert operation is not tested

using the automatic test. Revert should be tested using manual
operations.
8. Specify the drive letter of mount directory and press Enter.
Enter all the mount points that you want to test. Ensure to specify two "\" after the drive letter e.g., E:\\.

Enter source mount paths to snap (separate by commas, if more than one):
E:\\

9. Press Enter to add the detected array.

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

 SnapTest Automatic Snap Operations
-----------------------------------------------------------
Source Mount Point : E:\\
Detecting underlying devices... \\.PhysicalDrive1
Detecting snapshot engine... <Array Name> Snapshot
No [<Array Name> Snapshot] arrays found in database. Array configuration is
required to do snap operations.
Do you want to add <Array Name> Array? [Y/N] [Y] :

10. Specify the following information for the detected array:

{ Array ID
{ Control host name/ip
{ User name
{ Password
{ Reenter password
{ Device group
{ Use only devices belonging to the above device group [y/n]

SnapTest Add Array

-----------------------------------
Vendor : <Array Name>
Enter array ID :
Enter control host name/ip :
Enter user name :
Enter password :
Enter password again :
Enter device group :

11. The setup is tested for snapshot operations (create, mount, unmount, revert, and delete).

The snap test is now complete. You can now use this environment for performing IntelliSnap operations.

SnapTest Automatic Snap Operations

------------------------------------------------------------
Mount points to be snapped : E:\\
Engine for /snap1 : <Array Name> SNAP
Creating snapshot... SUCCESS
Snapshot name : SP_805326_805326_-1
Mounting snapshot...SUCCESS
Unmounting snapshot... SUCCESS
Reverting to snapshot... SUCCESS
Deleting snapshot... SUCCESS
Congratulations!!! Automatic Snap test completed successfully.
Press <ENTER> to continue...

12. Type 0 and press Enter.

SnapTest Version Main Menu

--------------------------------------
Perform automatic snap tests or launch Advanced Operations such as Array
Configuration, Snapshot Engine Detection etc. Automatic snap tests take one
or more source mounts to snap and performs series of Snap related
operations on them. In order to perform these snap operations, array
configuration such as array id, control host and user credentials is
required. If no array configuration is found, Automatic Snaptests takes you
to Array Configuration screen.

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

 1. Automatic Snap Tests
2. Advanced Operations
0. Exit
Choose your option [1]:

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:

z Firmware versions on the array

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





 Not accurate




 Not enough depth
 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Getting Started – EMC
VNX / CLARiiON
Overview Prerequisites Deployment Configuration Setup Agents

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.

Data Protection
Generic Software
Feature Support Suite IntelliSnap
Solution
Backup
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

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

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.

How does IntelliSnap Backup Work

Backup job is scheduled using the CommCell Console. When the backup job is started:

z The array is accessed to create a snapshot.

z The snapshot is mounted on the proxy or source computer for post backup operations.
z 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:

z The snapshot is mounted to the source or proxy computer.

z The mounted snapshot is treated like a file system and the required contents are read.
z The file system backup is performed on the Primary Copy of the storage policy.
z When the backup copy job is finished, the snapshot is unmounted.

Data Aging:

z The jobs for the snapshot are pruned based on the retention policy for the snapshot copy.
z The snapshots that are related to the pruned jobs are deleted from the array periodically.

Terminology
The IntelliSnap Backup documentation uses the following terminology:

Storage device A device used for backup or archival purposes.

Storage Array A high-end disk storage system. The IntelliSnap software is designed to work in conjunction with
the snapshot ability built into the storage array.
Proxy A computer other than the production server on which you can perform IntelliSnap operations. A
proxy is used to decrease the load on the production server.
Snapshot Copy An additional copy of the protected data that is used in IntelliSnap operations.





 Not accurate
 Not enough depth




 Need more code examples





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

Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Getting Started – EMC
VNX / CLARiiON
Overview Prerequisites Deployment Configuration Setup Agents

Array Licenses
z Clariion SnapView and AccessLogix licenses for Snap and Clone
z BASE/Symmetrix licenses for SYMAPI, required to discover Clariion storage systems

You can use the following command to check the licenses on the host computer:

C:\SYMAPI\Config> type symapi_licenses.dat

Array Software
On the client and proxy computers:

z EMC Solutions Enabler (6.5.1 or higher) for Clariion

z EMC Solutions Enabler (7.2 or higher) for VNX
Client Components (SYMCLI) are required only during the initial one-time configuration. Base Components
(with SYMAPI) are necessary and required for all snap operations.
z Navisphere CLI and Navisphere/Unisphere Host Agent

On the EMC VNX / CLARiiON, ensure the following:

z Navisphere/Unisphere Storage-System Initialization Utility is run to initialize Navisphere/Unisphere

functionality.
z AccessLogix is enabled. Follow the steps below to enable AccessLogix:
1. Log in to the Navisphere/Unisphere console.
2. Right-click EMC VNX / CLARiiON Storage System and click Properties.
3. From the Data Access tab, select Enable AccessLogix.
z Ensure enough reserved volumes are configured for SnapView/Snap to work properly.
z Free LUN should be of the same size (block count) as the clone source and this LUN should not be a part of any
storage group.

Setup the EMC VNX / CLARiiON

Perform the following steps to provide the required storage for IntelliSnap operations:

1. Create a RAID group.

2. Bind the LUN.
3. Create a Storage Group.
4. Register the client computer (covered by installing NaviAgent).
5. Map the LUNs to the client computer where the NaviAgent resides.
6. Reserved/Clone volumes target properly for SnapView.

For example, as shown in the image below, the Clariion ID of APM00033400899 has the following
configuration:

{ a RAID Group 0 provisioned as a RAID-5 group (Fiber Channel drives)

{ LUNs are mapped to Storage Group SG_EMCSnapInt1 with LUN ID of #154 present to client computer

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

 emcsnapint1.

The example shows the serial number of LUN 154:

{ RAID Group: RAID Group 0, containing 3 physical disks

{ Storage Group: currently visible to a single client computer
{ LUN is shown as a Fiber Channel device
{ The devices under LUN 154 reside on RAID Group 0 which has RAID-5 configuration.

Authenticate Data Protection Suite user information for the Naviagent

Before running any commands ensure that the EMC commands are verified against EMC documentation for a
particular product and version.

Follow the steps below to specify the authorization information for EMC Solutions Enabler and Navishphere CLI to
ensure administrator access to the Navisphere server.

1. To set the authorize information, run the symcfg authorization command for both the storage processors. For
example:

/opt/emc/SYMCLI/V6.5.3/bin# ./symcfg authorization add -host <clariion SPA

IP> -username admin -password password

/opt/emc/SYMCLI/V6.5.3/bin# ./symcfg authorization add -host <clariion SPB

IP> -username admin -password password

2. Run the following command to ensure that the Clariion database is successfully loaded.

symcfg discover -clariion -file AsstDiscoFile

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

 where AsstDiscoFile is the fully qualified path of a user-created file containing the host name or IP address
of each targeted Clariion array. This file should contain one array per line.
3. Create a Navisphere user account on the storage system. For example:

/opt/Navisphere/bin# ./naviseccli -AddUserSecurity -Address <clariion SPA

IP> -Scope 0 -User admin -Password password

/opt/Navisphere/bin# ./naviseccli -AddUserSecurity -Address <clariion SPB

IP> -Scope 0 -User admin -Password password

4. Restart the NaviAgent service.

5. Run snapview command from the command line to ensure that the setup is ready.

On Unix computers, you might need to add the Data Protection Suite user to the agent.config file.

Additional steps on Windows client and proxy machines required for VNX Snapshots

If Navisphere CLI commands fail with "security file not found” error, then follow the steps to add user authentication
for system account.

1. Create a service with interactive command prompt

sc create ntauthcmd binpath= "cmd /K start" type= own type= interact

2. Start the service

sc start ntauthcmd

3. It will open a command prompt. Add the user security using following commands

/opt/Navisphere/bin# ./naviseccli -AddUserSecurity -Address <clariion SPA

IP> -Scope 0 -User admin -Password password

/opt/Navisphere/bin# ./naviseccli -AddUserSecurity -Address <clariion SPB

IP> -Scope 0 -User admin -Password password

4. Delete the service

sc delete ntauthcmd

5. Run a sample NaviSECCLI command, for example:

NaviSECCLI -h < Storage Processor IP> snap -feature -info

If the command fails with the error below, type [2] to accept and store the certification, otherwise snap backup job
might not complete successfully.

Only import this certificate if you have reason to believe it was sent by a trusted source.
Certificate details:
Subject: CN=172.19.126.49,CN=A-IMAGE,OU=CLARiiON
Issuer: CN=172.19.126.49,CN=A-IMAGE,OU=CLARiiON
Serial#: 06b38bc5
Valid From: 20130328142406Z
Valid To: 20180327142406Z
Would you like to [1] Accept the certificate for this session, [2] Accept and store, [3] Reject the certificate?
Please input your selection (The default selection is [1]):2

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

Remote Snap MediaAgent
On the Remote Snap MediaAgent:

z EMC Solutions Enabler 7.2 or higher

z Navisphere/Unisphere Agent
z Navisphere CLI (Required for VNX Snapshots)

You need to setup user authentication for Solutions Enabler and Navisphere secure CLI on as mentioned above.
On the client computer:

z Navisphere/Unisphere host agent





 Not accurate




 Not enough depth
 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Getting Started – EMC
VNX / CLARiiON
Overview Prerequisites Deployment Configuration Setup Agents

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.

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

 4. Click Standard.

Click Next.

5. Click Create a New CommCell.

Click Next.

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

 6. The CommServe Module is selected by default. Click Next.

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

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

 8. Click Install.
z The Search Advanced Document Type Support package is installed along with Web Server.
z The Summary on your screen should list the components that you selected to install, and might look
different from the example shown.

9. Click Yes.

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

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.

Click Next.

z Ensure that the drive has at least 1GB of free space.

z Do not specify a mapped network drive or a FAT drive.
z Do not save the database files to a compressed drive.

12. Select Create a New Database, and, then click Next.

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

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.

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.

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

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.

17. Click Finish.

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

Default Options Selected During Standard Install

Listed below are the default options that are automatically selected while performing the Standard Install.

Option Enabled / Disabled Description

This option is used to automatically download software packages and
updates from FTP sites.

Setup Software Cache Enabled 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 42 of 101

 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 43 of 101

 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.

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

 z 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.
z The install program installs the database instance.

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

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

 { Do not use the following characters when specifying the destination path: / : * ? " < > | #
{ It is recommended that you use alphanumeric characters only

10. Click Install.

z The Search Advanced Document Type Support package is installed along with Web Server.
z 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.

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

12. Click Next.
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.

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

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.

15. Verify the path to the SQL Server database files.

Click Browse to change the default location.

Click Next.

z Ensure that the drive has at least 1GB of free space.

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

 z Do not specify a mapped network drive or a FAT drive.
z Do not save the database files to a compressed drive.

16. Select Create a New Database, and, then click Next.

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.

z The Network share username is the domain\username of the user that has administrative rights to the
Disaster Recovery Backup destination path.
z The Network share password is the password of the network share username.

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

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.

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.

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

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.

21. Click Yes.

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

 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.

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.





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Getting Started – EMC
VNX / CLARiiON
Overview Prerequisites Deployment Configuration Setup Agents

Setup the Array Information

Provide the identification information for the array to ensure access.

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 EMC VNX / CLARiiON from the Snap Vendor list.

Specify the serial number of the array in the Name field.

For reference purposes, the screenshot given below shows the serial number for the EMC VNX / CLARiiON
storage device.

4. Click Change and enter the access information of a user with administrative privileges in the Username and
Password fields in Enter User Name and Password dialog box.

VNX

For Clariion/VNX it is not necessary to provide array credentials in Array Properties dialog box in the
CommCell Console.

Instead, the following authorization/privilege settings must be set for the user as part of the setup on the host
machine, and the user credentials must be added in the Array Properties dialog box;

z Minimum Required Role - SAN Administrator or Storage Administrator

z Other Roles (higher privilege) - Administrator

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

 CLARiiON

z Minimum Required Role - Manager

z Other Roles (higher privilege) - Administrator

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.

5. Click the Snap Configuration tab and configure the following:

Specify EMC SYMAPI Installation Home Directory Path, where the EMC SYMAPI library is located. For
example, set the directory to opt/emc/SYMCLI/V6.5.1 for Unix and C:/Program Files/EMC/SYMCLI for
Windows.

Select Enable physical delete of clone to disable incremental clone operations. Enabling this option forces
physical deletion of the clone during a delete operation.

Select Use EMC API to detect host device paths to use EMC APIs to detect MPIO device paths.

Click OK.

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





 Not accurate




 Not enough depth
 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Getting Started – EMC
VNX / CLARiiON
Overview Prerequisites Deployment Configuration Setup Agents

The following agents are supported for EMC VNX / CLARiiON:

Supported Agents - Choose the Agent to configure

DB2
DB2 DPF
Exchange Database
Lotus Notes Database
Microsoft SQL Server
MySQL
Oracle
Oracle RAC
SAP For Oracle
Unix File System
VMware
Windows File System





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

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:

z Name

Name of the array

z Control Host

The name of the device manager server where the array was configured.

z User Name

The user account to be used for accessing the array.

z Snap Vendor Name

The name of the selected snapshot engine vendor for the array.

z Type

Type of array

z 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:

z Name

Name of the array

z Control Host

The name of the device manager server where the array was configured.

z User Name

The user account to be used for accessing the array.

z Snap Vendor Name

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

 The name of the selected snapshot engine vendor for the array.

z Type

Type of array

z 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

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.





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

Filer Properties (General) - EMC VNX /
CLARiiON
General Snap Configuration Security

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.

VNX

For Clariion/VNX it is not necessary to provide array credentials in Array Properties dialog box in the CommCell
Console.

Instead, the following authorization/privilege settings must be set for the user as part of the setup on the host
machine, and the user credentials must be added in the Array Properties dialog box;

z Minimum Required Role - SAN Administrator or Storage Administrator

z Other Roles (higher privilege) - Administrator

CLARiiON

z Minimum Required Role - Manager

z Other Roles (higher privilege) - Administrator





 Not accurate




 Not enough depth
 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

Filer Properties (Snap Configuration) -
EMC VNX / CLARiiON
General Snap Configuration Security

Use this dialog box to specify the details of snap configuration.

EMC SYMAPI Installation Home Directory Path

Specify the the directory where the EMC SYMAPI library is located. For example, set the directory to
opt/emc/SYMCLI/V6.5.1 for Unix and C:/Program Files/EMC/SYMCLI for Windows computers.

Sync operation retry count

Specify the maximum number of times that the SYMAPI database sync retries will be attempted. By default, the value
is set to 10.

Sync operation retry interval (in seconds)

Specify the time interval (in seconds) after which the next SYMAPI database sync operation will be executed. By
default, the value is set to 5 seconds.

Maximum SnapView Sessions per Lun

Specify the maximum number of SnapView sessions to be created for any LUN. The maximum limit is 8 sessions per
LUN. You can specify any value between 1 and 8.

Enable physical delete of clone

Select this option to disable incremental clone operations. By default during a delete operation, we mark the clone
aged and do not delete it. When a new clone request comes for the same LUN, the aged clone is picked for an
incremental sync. Enabling this option forces physical deletion of the clone during a delete operation.

Use EMC API to detect host device paths

Select this option to use EMC APIs to detect MPIO device paths. By default, the option to use EMC APIs is disabled.

Powerpath Device cleanup retry count

Specify the number of times to attempt the powerpath device cleanup. By default, this value is set to 10.

EMC Powerpath Installation Home Directory

Specify the path to the EMC powerpath installation directory. The commands executed during snap or clone operation
may fail if you do not specify this path.

Path of script to sync SYMCFG (only for UNIX)

Specify the absolute path to the script containing the sync command to sync the SYMCFG database. This option is
only applicable for Unix platforms.

Full sync during Rollback

Select this option to force a full synchronization of the SYMAPI database during rollback. By default, this option is

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

disabled.

Mount Retry Interval (in seconds)

Specify the time interval (in seconds) after which the next mount operation will be attempted. By default, it is set to
300 seconds.

Enable VNX Snapshots

Select this option to enable VNX snapshots. By default, it is disabled.

EMC Navisphere CLI Installation home directory path

Specify directory where Navisphere CLI is located. It is required for VNX Snapshots.

Delete Restore Point Snapshot

Select this option to delete Restore Point Snapshots after successful revert. Revert from VNX Snapshots automatically
creates a “Restore Point Snapshot” to recover from accidental data corruption. By default, this option is disabled.





 Not accurate




 Not enough depth
 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

Filer Properties (Security) - EMC VNX /
CLARiiON
General Snap Configuration Security

Use this dialog box to associate user groups who can edit and delete storage arrays. You can do the following using
this dialog box:

z Identify the user groups to which this CommCell object is associated.

z Associate this object with a user group.
z 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.





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Best Practices - EMC VNX /
CLARiiON
z Ensure that the client and proxy computers are configured to have access to the storage array.
z Ensure that sufficient number of Save Area devices are configured to meet your retention requirements.
z Ensure that sufficient disk space is available for snapshot operations and the disk space used by snapshots is
monitored frequently.

The space requirement for snapshots created during IntelliSnap backup can vary based on your environment.
The space utilization is dependent on the number of snapshots created and the retention period defined for the
snapshots.





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Frequently Asked Questions
- EMC VNX / CLARiiON
What should be the size of Free LUN?
Free LUN should be of the same size (block count) as the clone source and this LUN should not be a part of any
storage group.

How to Assign a new LUN to a Specific Host?

Prior to assigning a new LUN to a specific host, ensure the following:

z Proper hardware zoning has been completed for the Hot Bus Adaptors (HBAs) of the server to provide visibility
to a storage processor.
z The NaviAgent is installed to allow connectivity to the Navisphere Server.

Follow the steps below to assign a new LUN:

1. Allocate a new LUN.

2. Select the Clariion system and host to be configured. You can either create a new RAID group or use an existing
one.

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

 3. Select a specific LUN parameter. You can also use the option for automatic configuration of the LUN ID to the
host.

4. Verify your selections and click Finish.

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

 5. Verify that the specified LUN has been created under the specified Storage Group for the host.

How Do I Verify that a LUN is Mapped to a Host that Requires Protection?

To verify if a LUN is already assigned to the server, check the following under Navisphere:

1. The LUN that was created based on the RAID Group is present to the Host through AccessLogix Storage
Groups.

2. From the Clariion Storage Group configuration, you are able to see the LUN.

For example, LUN 154 is based on RAID Group-0, which has RAID-5 configuration.

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

How does IntelliSnap work with SnapView/Clone?

Data Protection Suite always runs a synchronization process to Clone target columns. The screenshot below shows
that the Clone IntelliSnap job ran from Job ID #2748. The example also shows that the Clone is:

z Consistent - Synchronization was completed

z Fractured - Clone is available to be mounted to the host (client or proxy computer).

Data Protection Suite uses the following naming convention for the IntelliSnap jobs:

SP_<commcell id as per the CSDB>_<Job_ID>_XXX

When an IntelliSnap job is running, you will notice that a synchronization is required for SnapView/Clone before the

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

Clone can be fractured as shown in the screenshot above.

You must have enough space on the Clone target RAID group or enough Clone Private LUNs for IntelliSnap
operations to run successfully.

How does IntelliSnap work with SnapView/Snap?

Unlike Clones, SnapView/Snap does not need synchronization as it will copy any blocks that have been modified
based on the Copy-On-Write model. Once a snapshot has been taken, you can see in Navisphere that a new snapshot
was created as shown in the example below.

Data Protection Suite uses the following naming convention for the IntelliSnap jobs:

SP_<commcell id as per the CSDB>_<Job_ID>_XXX_<Original LUN ID>

You will also notice that a session starts when the snapshot is created as seen in the screenshot. Sessions are created
based on the snapshot to allow tracking for:

z Snapshots where the session is running and on which reserved or source volume
z Blocks that have been modified.

Once a snapshot has been activated to the host computer, it is available for the host that is specified with the Storage
Group as shown in the example below.

Also, once the snapshots have been defined, they will remain inactive until they are activated again to run the
SnapView session.

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





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap – Troubleshooting - EMC
VNX / CLARiiON
Snapshots are not being created
It is recommended that multiple IntelliSnap backups using the same host must be run one after the other. Multiple
IntelliSnap backups running at the same time may cause the snapshot creation to fail due to the database lock.

Unable to perform cloning operation

For clone operations, ensure that Clone Private LUN (CPL) is created for each storage processor prior to performing
the snapshot operations.

Clariion discovery command fails with error

The symcfg discover -clariion command fails with the following error:

Invalid certificate encountered - End-of-chain encountered without finding a

trusted certificate

The discovery command fails because there is no LUN coming from the Clariion array to the proxy computer. To
solve this issue, consider the following scenario:

If you have two storage arrays (Clariion 1 and Clariion 2) and a proxy computer, where the proxy has access to a
LUN residing on Clariion 2 and your source LUN comes from Clariion 1. Clariion 1 does not have any LUN on the
proxy. For the discovery operation to be successful, you must add a LUN to Clariion 1 and mount it to the proxy
computer to allow connectivity. It is recommended to perform this workaround instead of using the Clariion discovery
command.





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

IntelliSnap Backup - Support
Supported Storage Arrays Supported Agents IntelliSnap 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:

z Firmware versions on the array

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

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

z Traditional License, based upon products and features in your CommCell.

z 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
NetApp Snap Management 1 license per CommCell
SnapMirror

Capacity License

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

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

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

Supported Storage Arrays

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

Required
Vendor Snapshot Version/Firmware Required Licensing Protocol Notes/Caveats
Software
Supported on
Windows,
Firmware version Linux
5.5.14 and above for Fibre VMware and
Dell 5.x and 6.2.2 and Snapshot Replay Channel HyperV.
Snapshot None
Compellent above for 6.x. licensing
iSCSI Compellent
Live Volume
feature is not
supported.
On Red Hat
Linux and
CentOS
computers
using version
5.5 (32-bit
Snapshot and 64bit)
Dell
4.2.0 Included None iSCSI
EqualLogic
Clone
No UNIX

Boot from
SAN volumes
is not
supported

No HyperV

Client
Solutions Fibre Components
Enabler 6.5.1 or Channel (SYMCLI)
CX500 / CX700 higher on Client are required
and Proxy FCoE only during
SnapView CX3-10 thru CX3- SnapView (Fibre the initial
EMC VNX / Snap 80 Snapshot/Clone Navisphere CLI Channel one-time

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

CLARiiON SnapView CX4-120 thru CX4- Solutions Enabler on Client and over configuration.
Clone 960 Licensing Proxy Ethernet) Base
* Components
NaviAgent on (with
Client and SYMAPI) are
Proxy necessary and
required for
all snap
operations.
VMware with
NFS
datastores are
supported.

ISCSI
PowerPath
LUNs are not
supported.

Client
Components
Solutions (SYMCLI)
Enabler 7.2 or are required
VNX 5100, 5300,
higher on Client only during
5500, 5700, 7500
and Proxy the initial
SnapView SnapView
Fibre one-time
Snap VNX OE for Block Snapshot/Clone
Unisphere CLI Channel configuration.
EMC VNX Version 05.32 or
on Client and Base
SnapView higher is required Solutions Enabler
Proxy iSCSI Components
Clone for VNX Snapshots Licensing
(with
Unisphere Host SYMAPI) are
Agent on Client necessary and
and Proxy required for
all snap
operations.

For
configuring a
VNX array,
refer to the
step-by-step
instructions
provided for
EMC
Clariion.
Solutions
Enabler 6.5.1 or
SnapSure Snap
License higher on Client Supported on
EMC VNX / SnapSure and Proxy VMware 4.x.
Celerra Snap DART 5.5 or Newer NFS
Solutions Enabler
Navisphere CLI No HyperV
Licensing
on Client and
Proxy
SnapshotIQ License iSCSI
EMC Isilon Snapshot Support for OneFS
6.5 and OneFS 7.0

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

 Remote
SymApi
Server is not
supported.

Client
Fibre Components
Channel (SYMCLI)
TimeFinder Snap,
Mirror, Clone Solutions are required
TimeFinder Licenses FCoE only during
EMC Enabler 6.4 or
Symmetrix Snap, Clone, DMX3 or Newer higher on Client (Fibre the initial
and Mirror Channel one-time
Solutions Enabler and Proxy
over configuration.
Licensing
Ethernet) Base
* Components
(with
SYMAPI) are
necessary and
required for
all snap
operations.
No HyperV

Remote
SymApi
Server is not
supported.

Fibre Client
Channel Components
TimeFinder Snap,
Mirror, Clone Solutions (SYMCLI)
TimeFinder Licenses FCoE are required
Enabler 7.2 or
EMC VMAX Snap, Mirror VMAX (Fibre only during
higher on Client
and Clone Channel the initial
Solutions Enabler and Proxy
over one-time
Licensing
Ethernet) configuration.
* Base
Components
(with
SYMAPI) are
necessary and
required for
all snap
operations.
Fujitsu ETERNUS
V10L22-1000 or
SnapOPC iSCSI
Snap higher Local Copy
Fujitsu
None
ETERNUS DX Fibre
ETERNUS DX S2 Thin Provisioning
EC Clone Channel
series - 80, 90, 410,
440, 8100, 8700

Device
Manager 7.1.1
(or higher)
Agent installed No HyperV

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

 on Client and HDP
Proxy Volumes not
supported for
Device Fibre COW.
Copy-on- Manager Server Channel
Write AMS 100, 200 & 7.1.1 (or The Virtual
500 Licenses for Copy-
higher) installed FCoE Machine
on-Write (COW)
HDS AMS Shadow on any (Fibre HotAdd
snapshot and Shadow
Image AMS 100, 2100, computer Channel feature is not
Image
2300, & 2500 over supported.
RAID Manager Ethernet)
(01-25-03/05 or *
higher) installed
on Client and
Proxy
Fibre SI & TI
Channel support for
VSP & HUS-
RAID Manager
HDS Shadow VM volumes.
Licenses for Thin- (01-29-03/05 or FCoE
VSP/HUS-VM Image HDS HUS-VM, Dynamic
using CCI VSP Image (TI) snapshot higher) installed (Fibre Provisioned
and Shadow Image on Client and Channel
Engine Thin Image volumes (DP-
Proxy over
VOL) are
Ethernet)
also
* supported.
Device
No HyperV
Manager 7.2.1
(or higher)
The Virtual
Agent installed
Server
on Client and
Fibre iDataAgent
Proxy
Channel must be
Copy-on- installed on a
Write Licenses for Copy- Device
FCoE physical
HDS HUS on-Write (COW) Manager Server
HUS 100 series (Fibre server and not
snapshot and Shadow 7.2.1 (or
Shadow Channel on a virtual
Image higher) installed
Image over machine.
on any
Ethernet)
computer
* The Virtual
Machine
RAID Manager
HotAdd
(01-26-03/02 or feature is not
higher) installed
supported.
on Client

Device No HyperV
Manager 7.1.1
(or higher) COW support
Agent installed for USP
Copy-on-
Write Licenses for Copy- on Client and volumes.
HDS USP, USPv, on-Write (COW) Proxy Fibre
HDS USP/VSP Channel COW and SI
VSP snapshot and Shadow
Shadow Image Device support for
Image Manager Server FCoE VSP volumes.
7.1.1 (or (Fibre Dynamic
higher) installed Channel Provisioned
on any over volumes (DP-
computer Ethernet) VOL) are also

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

 RAID Manager * supported.
(01-25-03/05 or
higher) installed The Virtual
on Client and Machine
Proxy HotAdd
feature is not
supported.
HP SMI-S EVA
EVA
on Server Fibre
Business
HP Business Copy Channel
HP EVA Copy EVA No HyperV
EVA feature Command
Snapshot and
Clone View Version iSCSI
9.1 , 9.3
HP
StorageWorks
Command
View Advanced
Edition Agent
(Device
Manager 7.1.1
or higher)
installed on
client and proxy
computers Fibre
Channel
Copy-on- No HyperV
HP
Write XP 12000 – 24000 Licenses for Copy- The Virtual
HP (HDS on-Write (COW)
StorageWorks FCoE
Machine
OEM) XP, Command (Fibre
snapshot and Shadow HotAdd
P9500 Arrays Shadow P9500 View Advanced Channel
Image feature is not
Image Edition Server over
(Device supported.
Ethernet)
Manager 7.1.1 *
or higher)
installed on any
computer.

HP
StorageWorks
RAID Manager
installed on
client and proxy
computers.

The snap
recovery is
supported by
Thin Provisioning retaining the
F-Class and V-Class child snap.
(4096G) license is
Fibre
required when Thin Channel
Snapshot and CIM 3.1.2 and 3PAR SMI-S
HP 3PAR Provisioning is Also supports
Clone higher is installed on Server 2.3.1 (MU4)
enabled for Cloning
iSCSI or higher,
Virtual Copy except
3.1.1.342 ,
3.1.1 MU1 +
Patch 10,
3.1.1 (MU2),

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

 and 3.1.2
(MU2)
No HyperV
Flash Copy
Fibre Revert
SVC / V7000 IBM SMI-S on Channel operation for
IBM SVC Space- FlashCopy
6.1.0.7 or higher Server space-
efficient
iSCSI efficient Flash
Flash Copy
Copy is not
supported.
IBM XCLI 2.3 Fibre
or higher on Channel
IBM XIV Snap ANY XIV Array Included No HyperV
Client and
proxy iSCSI
Dell MD Series –
3000(i), 3200(i),
3220(i)

IBM DS - 3200,
3300, 3400 - 3512,
3524, 3950, 4100,
4200, 4300, 4400,
4500 - 4700, 4800, LSI SMI-S on
5020, 5100, 5300 Fibre LSI Volume
NetApp E- Snapshot Snapshot Server and
Channel Copy is not
Series (LSI server
supported for
arrays) VolumeCopy SGI IS – 220, 350, VolumeCopy 10.10.6054 or
iSCSI Hyper-V.
400, 4xxx, 5xxx higher

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

Sun - 25xx, 61xx,

65xx, 6780, 9176,
FLX210, FLX240,
FLX280
OnCommand
Unified
Manager - A
server running
NetApp
OnCommand
Unified
Manager server
software 4.0.2
or later, or
OnCommand
Unified
Manager5.x is
required.

Operations
Manager,
Provisioning
Manager, and
Protection
ONTAP 7.3.5 or Manager

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

 higher licenses are
required for the
ONTAP 8.0.1, 8.0.2, OnCommand
8.1.0, and 8.2 Unified
Manager.
7-mode supported
OnCommand
C-mode supported Unified
for ONTAP 8.3 Manager 6.0 -
In order to
support the
NetApp cluster Fibre
FlexClone Channel Supported on
mode, install
OnCommand HP-UX
Unified iSCSI running on
SnapRestore
NetApp Snapshot Manager6.0. Intel Itanium
processors
SnapVault/Mirror for NFS using Fiber
replication SnapMirror -
Channel.
NetApp
replication
technology used
for disaster
recovery.

SnapVault -
NetApp
replication
technology used
for backup and
recovery.
Supported on
1.2.2.0-17686 x64-bit
Nimble Snapshot Included None iSCSI Windows,
1.3.0.0-22989 Vmware and
Hyper-V.

Supported Hardware Arrays for Replicated Environments

Required
Vendor Snapshot Version/Firmware Required Licensing Software Protocol Notes/Caveats

OnCommand
Unified
Manager
version 4.0.2 Supported on
(Apr 2011) or HP-UX running
OnCommand on Intel Itanium
NetApp with
SnapVault SnapVault ONTAP 7.3.5 or Unified processors using
SnapMirror higher Manager 5.0 Fiber Channel.
SnapMirror with ONTAP
ONTAP 8.0.1, 8.1.0 Fibre vFilers as a
8.0.2, 8.1.0, and SnapVault/SnapMirror Channel destination
8.2 (7-mode Primary and Provisioning supported for
supported) Secondary Manager, iSCSI Netapp 7-mode.
Protection
ONTAP 8.2 or FlexClone Manager, & NFS vFilers as

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

 higher (Cluster SnapRestore Operation CIFS NFS/CIFS share
mode supported) Manager sources will
Licenses have no
indexing due to
OnCommand lacking
Unified SnapDiff
Manager 6.0 for support.
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

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

Hardware
Snap Engine
or native
snap or
QSnap
license
Set the
EnableNativeSnapEngine
global parameter to 1 using the
SetKeyIntoGlobalParam
qscript.
Local native
Solaris Solaris (Global Solaris OS has ZFS snap
Oracle Solaris snapshot
ZFS zone only) capability Example:
license
qoperation execscript -sn
SetKeyIntoGlobalParamTbl.sql
-si EnableNativeSnapEngine -
si y -si 1

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.

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

 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

z iSCSI initiator is configured on the client computer to mount the Snapshot

z 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 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.
Virtual Server
Backup of VM
(VMware)
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.

Exchange Database DDR snapshots are not

supported on
Exchange 2010 DAG
clients.

SRM is not supported.

Lotus Notes Database

Incremental backups

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

 are traditional MySQL
log backups.
Transactional Log
backups always use
MySQL
the traditional backup
method. Log backups
are stored in the
Primary (classic) copy.
Incremental backups
Oracle are applicable for
Backup copies.
Incremental backups
ORACLE RAC are applicable for
Backup copies.
Transactional Log
backups always use
Microsoft SQL the traditional backup
Server method. Log backups
are stored in the
Primary (classic) copy.
NAS
IntelliSnap backups
support online virtual
machines with NetApp
file servers.

Virtual Server Other storage array

(Hyper-V) vendors use the
traditional backup
method. To perform a
IntelliSnap backup, the
virtual machine must
be offline.
SAP Oracle
Backup of partial
databases is not
supported.
DB2
Log files always use
the traditional backup
method.
On Demand Backup
Set is not supported
for IntelliSnap
Backup.

Raw partitions in Unix

Unix File System are supported.

Mirrored LVM
configuration is not
supported.

On HP-UX, non-LVM

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

 volumes are not
supported for
IntelliSnap Backup.
On Demand Backup
Set is not supported
Windows File System
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 System Cluster Support File Systems Databases Applications
SQL version 2005 and
later

Exchange 2003, 2007,

2010, 2013 – including
Windows 2003 and DAG
MSCS NTFS
Higher
Oracle 10g R2, Oracle
11g R1 & R2

DB2 version 9 or
higher
iSCSI/FC/NFS ESX vSphere 4.x &
VMWare ESX datastores vSphere 5.0
Oracle 10g R2, Oracle
11g R1 & R2

AIX 5.3, 6.1, 7.1 JFS, JFS2, VxFS, DB2 version 9 or

(LPARS Supported, VxCFS, IBM General higher SAP Brtools 7.0 & 7.1
Veritas Cluster,
Virtual SCSI Parallel File System on Oracle 10g R2,
HACMP
devices not (GPFS)* 3.5.0.7 or Oracle RAC version Oracle 11g R1 & R2
supported) higher 10g R2 or higher

DB2 DPF version 9 or

higher
Oracle 10g R2, Oracle
11g R1 & R2

DB2 version 9 or
HP-UX 11 v2/v3 higher SAP Brtools 7.0 & 7.1
Service Guard, Veritas
(PA-RISC and HFS, VxFS, VxCFS on Oracle 10g R2,
Cluster
Itanium) Oracle RAC version Oracle 11g R1 & R2
10g R2 or higher

DB2 DPF version 9 or

higher

Oracle 10g R2, Oracle

11g R1 & R2, Oracle

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

 12c

DB2 version 9 or
higher SAP Brtools 7.0, 7.1 &
ext2, ext3, ext4,
Oracle Enterprise reiserfs, VxFS, 7.2 on Oracle 10g R2,
Linux 5.x and 6.x Oracle RAC version Oracle 11g R1 & R2,
VxCFS, OCFS2
10g R2 or higher Oracle 12c

DB2 DPF version 9 or

higher
Oracle 10g R2, Oracle
11g R1 & R2, Oracle
12c
ext2, ext3, ext4,
reiserfs, VxFS, DB2 version 9 or SAP Brtools 7.0 & 7.1
Red Hat Linux 4.x Linux Cluster, Veritas OCFS2, VxCFS, IBM higher on Oracle 10g R2,
and 5.x Cluster General Parallel File Oracle 11g R1 & R2,
System (GPFS)* Oracle RAC version Oracle 12c
3.5.0.7 or higher 10g R2 or higher

DB2 DPF version 9 or

higher
Oracle 10g R2, Oracle
11g R1 & R2, Oracle
12c

DB2 version 9 or SAP Brtools 7.0 & 7.1

CentOS Linux 4.x ext2, ext3, ext4, higher on Oracle 10g R2,
Linux Cluster
and 5.x reiserfs, OCFS2 Oracle 11g R1 &
Oracle RAC version R2,Oracle 12c
10g R2 or higher

DB2 DPF version 9 or

higher
Oracle 10g R2, Oracle
11g R1 & R2; Oracle
12c
ext2, ext3, ext4,
reiserfs, VxFS, DB2 version 9 or SAP Brtools 7.0, 7.1 &
Linux Cluster, Veritas VxCFS, OCFS2, IBM higher 7.2 on Oracle 10g R2,
Red Hat Linux 6.x
Cluster General Parallel File Oracle 11g R1 & R2,
System (GPFS)* Oracle RAC version Oracle 12c
3.5.0.7 or higher 10g R2 or higher

DB2 DPF version 9 or

higher

Oracle 10g R2, Oracle

11g R1 & R2, Oracle
12c SAP Brtools 7.0, 7.1 &
ext2, ext3, ext4, 7.2 on Oracle 10g R2,
CentOS Linux 6.x Linux Cluster
reiserfs, OCFS2 DB2 version 9 or Oracle 11g R1 & R2,
higher Oracle 12c

Oracle RAC version

10g R2 or higher

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

 DB2 DPF version 9 or
higher
Oracle 10g R2, Oracle
11g R1 & R2, Oracle
12c

DB2 version 9 or SAP Brtools 7.0, 7.1 &

Solaris 10 SPARC higher
Sun Cluster, Veritas UFS, VxFS, VxCFS, 7.2 on Oracle 10g R2,
(Solaris Zones
Cluster ZFS Oracle 11g R1 & R2,
Supported)
Oracle RAC version Oracle 12c
10g R2 or higher

DB2 DPF version 9 or

higher
Oracle 10g R2, Oracle
11g R1 & R2, Oracle
12c

DB2 version 9 or SAP Brtools 7.0, 7.1 &

Solaris 11 SPARC
Sun Cluster, Veritas UFS, VxFS, VxCFS, higher 7.2 on Oracle 10g R2,
(Solaris Zones
Cluster ZFS Oracle 11g R1 & R2,
Supported)
Oracle RAC version Oracle 12c
10g R2 or higher

DB2 DPF version 9 or

higher
Solaris 11 Express UFS, ZFS
Oracle 10g R2, Oracle
11g R1 & R2, Oracle
SAP Brtools 7.0, 7.1 &
UFS, VxFS, VxCFS, 12c
Solaris 11 x64 7.2 on Oracle 10g R2,
ZFS
Oracle 12c
Oracle RAC version
10g R2 or higher
Oracle 10g R2, Oracle
11g R1 & R2, Oracle
12c
ext2, ext3, ext4,
reiserfs, VxFS, DB2 version 9 or SAP Brtools 7.0 & 7.1
SuSE Linux
VxCFS, IBM General higher on Oracle 10g R2,
Enterprise Server Veritas Cluster
Parallel File System Oracle 11g R1 & R2,
10.2 and 11
(GPFS)* 3.5.0.7 or Oracle RAC version Oracle 12c
higher 10g R2 or higher

DB2 DPF version 9 or

higher

*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

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

 z VERITAS Volume Manager (VxVM) 5.0 for AIX, Linux, Solaris SPARC and Solaris x64
z VERITAS CFS (VxCFS) version 5.1 or higher
z Solaris ZFS Mirror
z Solaris Volume Manager
z 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:

z One Physical Volume containing one Logical Volume

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

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

Multipath I/O Support

z For EMC VNX / CLARiiON, IntelliSnap backup is supported on the following Multipath I/O software. This
support is provided using the SNAP_WITH_MULTIPATH_SOFTWARE additional setting.
{ EMC Powerpath on AIX, Linux and Solaris.
z For Dell EqualLogic, install Dell EqualLogic Host Integration Tools package to support Multipath I/O.
z HP PVlinks, Solaris MPxIO, Linux Device Mapper and AIX MPIO are supported in HPUX, Solaris, Linux and
AIX respectively.
z VXVM DMP is supported in AIX, Solaris and HPUX.
z HDLM is not a supported MPIO solution with IntelliSnap.





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

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:

z create, mount, unmount, delete, revert snapshots for an array.

z 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

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

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
{ 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:

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

 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:

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.

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

 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.

{ Rename the SnapTestSnapInfo_old file to SnapTestSnapInfo.

Back to Top





 Not accurate
 Not enough depth




 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

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

EMC VNX / CLARiiON Storage System
Guide for IntelliSnap
Table of contents
IntelliSnap Guide Objective and Overview

EMC VNX / CLARiiON Storage System Overview

Architecture of Clariion and Navisphere

Navisphere

SnapView

Storage Systems Series Support

Integration Requirements for IntelliSnap

Array and Solutions Enabler Software Licenses

Supported Applications and Operating Environments

Data Protection Suite Software

IntelliSnap Array Configuration Details with Clariion

The IntelliSnap Process

IntelliSnap Backup Operation

Backup Copy Operation

Proxy Configuration

Verify Configuration using SnapTest Tool

Security and Storage Policy Best Practices

Security Roles

Storage Policies

Managing Snapshots

Managing Clariion SnapView Clone/Snap and Data Protection Suite Data Aging

IntelliSnap Guide Objective and Overview

This guide is an introductory overview of the storage array with its built-in technology and feature sets, along with the
licenses and configuration requirements to integrate these controls with the Data Protection Suite software. This guide
also provides detailed descriptions for configuring hardware-based snapshot mechanisms using the Data Protection
Suite software.

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

The IntelliSnap technology of the Data Protection Suite software is a modernized approach for data protection,
allowing hardware storage systems snapshots to merge directly into the backup process. By automatically integrating
application intelligence with array snapshot abilities, Data Protection Suite is able to reach through the application and
file systems into the storage array to accomplish the following:

z discover volume/disk configurations for the snapshot operations

z coordinate snapshot operations with proper application quiesce
z minimize administrative configuration and eliminating scripting requirements

When a scheduled backup job for a defined application runs, the source system quiesces the selected applications and
automatically creates a set of persistent snapshots within the production storage system. With a confirmation of the
successful snapshot creation by the host, the workload in the protection job shifts to a secondary proxy server to
offload backup operations. This shift releases the production host, which returns to full production side operations.
This allows the creation of a consistent data image in minutes with Recovery Point Objectives (RPOs) aligning with
the frequency of schedule.

The Proxy completes the second half of the protection job by reaching into the SAN, mounting the snapshot and
automatically indexing and cataloging the file-level contents of the snapshot(s). Unlike the hardware-based snapshot
approach, Data Protection Suite blends the speed and efficiency of array snapshots directly into the backup and restore
process, offering full system recovery or single file restore. Once the content-aware indexing completes, the snapshot
is retained in the array as a persistent recovery copy to provide a quick recovery option to revert or restore the data
volumes.

The Proxy serves a secondary role after the snapshot executes. The same snapshots will mount and copy the relevant
file contents from the snapshot and apply deduplication to the data during transport to the backup copy destination.
The backup copy employs a separate retention than the snapshot allowing aggressive snapshot retention to preserve
tier1 space to meet the RTO/RPO needs. As data moves into the backup copy, the original indices are preserved and
stored along with the data to ensure access from any location. Data encryption is also another critical feature to apply
to data to keep it highly secured from unwanted eyes.

IntelliSnap supports the leading SAN/NAS storage solutions from Dell, EMC, NetApp, LSI, HP, SUN, IBM and HDS.

EMC VNX / CLARiiON Storage System Overview

EMC provides customers Clariion Storage System platform for mid-range to entry level storage needs.

EMC VNX / CLARiiON is a Storage Subsystem dedicated for mid-range system LUN-based use. It also does not
provide CIFS/NFS capabilities unlike many Network Attached Storage systems. EMC leverages the Celerra platform
for NAS based storage offerings.

This guide will provide an in-depth storage technology overview, examples of configuration and necessary steps to
configure Data Protection Suite with EMC VNX / CLARiiON systems.

For further EMC VNX / CLARiiON training material, please visit powerlink.emc.com.

Architecture of Clariion and Navisphere

The architecture of EMC VNX / CLARiiON is based on the following

components:

Hardware Components

2 Storage Processors

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

Software Components

z Disk Array Enclosure

z FLARE Code

These components provide the storage-system performance and

functionality for today's Small-to-Medium Business needs. The
following sections provide a brief description for each component.

Storage (or Service) Processors / Storage Processor Enclosure

EMC provides connectivity between the customer environment and

the Clariion through Storage Processors. There are two Storage
Processors for each of the Clariion systems for Trespassing capability
(Fail-over capability). Each storage processors have their own
Memory for processing all input/output locally with trespassing
capabilities. Each storage processor provide the following:

z Front-End connectivity (customer environment) using either

Fiber Channel and/or iSCSI
z Back-End connectivity (storage) using Fiber Channel Loops.

Both storage processors reside within a Storage Processor Enclosure,

and each provide user interface and command line interface level
console connection to provide customers ways to manage Disk
provisioning through Navisphere (Clariion management software).

An example report from Navisphere with the basic configuration of

each Storage Processor is shown on the right.

Disk Array Enclosure

Disk Array Enclosure (DAE) is a main component that connects with the Back-End modules from each of the storage
processors presenting raw disks for use. Each DAE contains 15 disk drives in a Fibre Channel loop, and can be daisy
chained to loop up to 120 disk drives per loop.

FLARE Code

FLARE (Fibre Logic Array Runtime Environment) is the proprietary

code from EMC that controls each component in Clariion, much like
Enginuity running throughout the high-end EMC Symmetrix family.
FLARE code usually runs off the first five disks of the first Disk
Array Enclosure, which is also supplied by the integrated
Uninterrupted-Power-Supply (UPS). All write cache contents will be

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

stored in an event of power failure for complete restoration upon
power-on.

An example of the Flare code running on a particular Clariion model

is shown on the right.

Navisphere

Navisphere is EMC’s customer software product that allows customers to configure, monitor and manage EMC VNX /
CLARiiON disk-array storage systems connected to hosts on a network. Navisphere has a server and client side where
each of the clients talk to the server to request changes and updates to the EMC VNX / CLARiiON storage system.

Component Description
Navisphere Agents relay configuration and status requests from Navisphere
Manager to EMC VNX / CLARiiON storage systems. These agents also
periodically retrieve information from the storage system events and can notify
personnel by e-mail, pager, or modem when any specific event occurs.
Navisphere Host and SP Agents
z Navisphere Host Agents reside on each of the Server/Hosts.
z SP Agents reside on the Storage Processors and are installed by default at
the factory.
The Navisphere Manager is a centralized storage-system management tool to
configure and manage EMC VNX / CLARiiON storage systems. It allows the
following basic functions:

z Discover EMC VNX / CLARiiON systems

Navisphere Manager (Navisphere z Show status and configuration of EMC VNX / CLARiiON systems
Command Line Interface) z Configure and allocate storage
z Reporting operations

By default, the Navisphere Manager is installed along side with Navisphere

Storage Manager Server on the storage processors. It can also be installed on
Windows Servers.
This component allows you to:

z Receive configuration requests from the Navisphere Manager

z Forward requests to the local SP Agents for processing
Navisphere Storage Manager
z Authenticate user logins and authorize logins
Server
The Navisphere Storage Manager Server can also be installed on a Windows
Server to work as a Portal for systems that are traditionally not installed from the
factory (FC5300 and FC4500 series).

SnapView

SnapView is an EMC VNX / CLARiiON feature that allows internal operations in a single Clariion system to create a
point-in-time view of a logical unit (LUN) without disrupting the source volume. The SnapView software is installed
by default and resides on the EMC VNX / CLARiiON storage-system. EMC runs a Non-Disruptive Update to enable
the feature.

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

SnapView requires a separate licensing component that is usually provided by EMC to allow Clariion customers to
take advantage of the Clone/Snap feature.

The following snapshot capabilities are available:

SnapView/Clone

It is the traditional way to take a full copy of the source volume to a

clone volume at a block by block level. SnapView/Clone requires a
full or incremental synchronization before a clone fracture can be
initiated, allowing the clone to be available for reuse by another server
or presented as another LUN.

SnapView/Snap

It provides the ability to provide a Point-In-Time view of the source

volume using pointers with reserved volumes. Pointers will initially
point to the original data on the source volume. Once new data is
written to the source volume, the original data is copied to the
reserved volume to preserve the Point-In-Time view.

During the first SnapView session on a given source volume, a

reserved volume is assigned to the source volume. If the SnapView
session runs long enough that the reserved volume is filled, the next
reserved volume will be assigned to the source volume.

Storage Systems Series Support

The Data Protection Suite software supports all CX series models. AX series are not supported.

For information on the supported storage systems for the Data Protection Suite software, see Hardware Snapshot
Engine Compatibility Matrix.

AX Series

AX Series are considered an entry level version of the EMC VNX / CLARiiON storage system. Serial-ATA drives are
only supported in this model.

Model Connectivity Max Connection Speed Max No. Disks

AX150 FC 2 GB/s 12
AX150 SC FC 2 GB/s 12
AX150i iSCSI 1 GB/s 12
AX150i SC iSCSI 1 GB/s 12
AX4-5F FC 4 GB/s 60
AX4-5I iSCSI 1 GB/s 60

CX Series

The CX series support both Serial-ATA and Fibre Channel disk drives.

Model Connectivity Max Connection Speed Max No. Disks

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

CX300 FC / iSCSI 2 GB/s and 1 GB/s 60
CX500 FC / iSCSI 2 GB/s and 1 GB/s 120
CX700 FC Only 2 GB/s 240

CX3 Series

CX3 series support both Fiber Channel and iSCSI connectivity with double the number of disks for the high end of the
CX series.

Model Connectivity Max Connection Speed Max No. Disks

CX3-10 FC / iSCSI 2 GB/s and 1 GB/s 60
CX3-20 FC / iSCSI 2 GB/s and 1 GB/s 120
CX3-40 FC / iSCSI 2 GB/s and 1 GB/s 240
CX3-80 FC / iSCSI 2 GB/s and 1 GB/s 480

CX4 Series - Ultrafex

CX4 series increases the Fibre Channel speed up to 4 Gb/s, while iSCSI support is still for 1Gb/s. This series also
allows for Solid State Drives (SSD) to be used as Back-End disk drives, and also features 64-bit FLARE code due to
the introduction of the 64-bit Intel Xeon CPUs in the Storage Processors. Again, the high end doubles the maximum
number of disks.

Model Connectivity Max Connection Speed Max No. Disks

CX4-120 FC / iSCSI 4 GB/s and 1 GB/s 120
CX4-240 FC / iSCSI 4 GB/s and 1 GB/s 240
CX4-480 FC / iSCSI 4 GB/s and 1 GB/s 480
CX4-960 FC / iSCSI 4 GB/s and 1 GB/s 960

Integration Requirements for IntelliSnap

Array and Solutions Enabler Software Licenses

The Data Protection Suite software requires enabling certain array components and licenses on the EMC VNX /
CLARiiON storage system to achieve a successful integration with the software. Refer to the IntelliSnap Backup -
EMC VNX / CLARiiON documentation for more information.

Supported Applications and Operating Environments

Refer to the IntelliSnap Backup - Support document for a complete list of supported applications and platforms.

Data Protection Suite Software

IntelliSnap solutions require the appropriate agents as defined by the customer configuration. See the following
terminology for reference in this document:

Terms Description
Production Host Server hosting the actual production LUN for snapshot or clone operations.
Proxy Host Server mounting the snapshot or clone for backup purposes off of the Production
Host
Array Hardware Storage Array executing the snapshots.
File System iDataAgent
Agent for protecting the file system of a host. It is the base requirement for most

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

 Application iDataAgent.
Agent for creating and managing snapshots as well as for writing data to backup
MediaAgent
targets.
Agent for protecting applications such as SQL, Exchange, DB2, SAP and Oracle.
Application iDataAgent
Enables application-aware snapshots to be created when backups are scheduled.
Agent providing protection of Virtualization Environments without installing
Virtual Server Agent (VSA) backup iDataAgents internal to the guests.
VSS Provider This software allows programmatic controls of the Windows VSS components.

A CommServe, a necessary storage capacity, and MediaAgents must exist to enable a completely functional solution.
See the IntelliSnap Getting Started Guide for step-by-step instructions on:

z CommServe, MediaAgent and File System installation

z Storage Device and Storage Policy Configuration

On top of this basic infrastructure, you can configure the environments described below.

Basic File System Environments

The IntelliSnap base configuration requires the following agents on the Production Host:

z Windows/Unix File System iDataAgent

z MediaAgent
z VSS Software Provider (Windows Only)

For a configuration where snapshots mount off the host to a Proxy server, implement the following agents on the
Proxy:

z File System iDataAgent (Must be similar to Production Host Operating System)

z MediaAgent

Refer to Getting Started - Setup Clients to select Windows/Unix iDataAgent and perform the required deployment and
configuration steps.

Application Environments

Protecting application databases and log volumes through an Array

snapshot provide fast access for recovery and many flexible options
for backups. IntelliSnap integrates application awareness together
with the Array and Data Protection Suite to deliver all of the benefits
of traditional streaming backups with all of the performance and
proxy capabilities of a snapshot. This application awareness allows
backups with appropriate log management operations based on the
snapshot data.

When implementing for Application Environments simply add the

appropriate Application iDataAgent to the IntelliSnap base
configuration as follows on the Production Host:

z Windows/Unix File System iDataAgent

z MediaAgent
z VSS Software Provider (Windows Only)
z Application iDataAgent for selected Application (e.g.,
Exchange, SQL, Oracle)

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

For a configuration where snapshots mount off the host to a Proxy
server, implement the following agents on the Proxy.

z File System iDataAgent (Must be similar to Production Host

Operating System)
z MediaAgent
z Application specific iDataAgent (Must be the same to
Production Host) to enable Proxy. This is required for RMAN
integrated backups.
z Application API (e.g., Exchange Management Pack, Oracle for
RMAN integration)

Refer to Getting Started - Setup Clients to select your application

iDataAgent and perform the required deployment and configuration
steps.

Virtual Environments

IntelliSnap enables fast protection of large or volatile VMware environments

without placing load on the production Virtualization Farm. IntelliSnap
technology integration with the Virtual Server Agent enables the Array to
perform backups in minutes even with large numbers of virtual machines and
sizable data stores. A dedicated ESX server for proxy data movement removes
any utilization on the ESX farm providing file and folder recovery from the
secondary tier of storage.

To enable IntelliSnap for the Virtual Environment install the following on the
physical server(s) or virtual hot-add guest(s):

z Windows/Unix File System iDataAgent

z MediaAgent
z Virtual Server Agent (VSA)

Refer to Getting Started - VMware for deployment and configuration steps.

IntelliSnap Array Configuration Details with Clariion

The Data Protection Suite software utilizes two different local replication mechanisms provided by EMC:
SnapView/Clone and SnapView/Snap. SnapView/Clone provides full replication of a Production logical device to a
Clone Target volume (target LUN), block by block. SnapView/Snap provides a block level pointer-based approach
using reserved volume so blocks of the active LUN will be copied to a reserved volume upon a new write generated on
the Production LUN. In other words, SnapView/Clone generates a reference-able clone on separate disks, while
SnapView/Snap leverages the Copy-on-Write model and pointers to provide Snapshot access.

Refer to the IntelliSnap Configuration - EMC VNX / CLARiiON documentation for array configuration steps.

The IntelliSnap Process

The following sections describe the different IntelliSnap operations.

IntelliSnap Backup Operation

IntelliSnap backups consist of the following operations:

1. The backup job (on-demand or scheduled) starts from the CommCell Console.

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

 2. The file system, associated applications, or Virtual Machines properly acquiesce (VSS calls Windows or
through application interfaces such as RMAN the database goes in a Hot Backup mode). In VMware
configurations, vStorage APIs are called to create software snapshots and enable delta file creation for each of
the guests targeted as contents of the snapshot.
3. Array API is called to:
{ Verify the backup job contents (validating the underlying disk structure for file systems, databases, etc).

SnapView/Clone establishes the Clone Volume to the Production Volume, waits for synchronization and
fractures the Clone from the Production volume.

SnapView/Snap creates and actives a Snap session between the Production and reserved volume.

Assign the Clone/Snap to the appropriate Storage group (either the production or the proxy computer).
{
Mount the snapshot on the source or the selected proxy computer for post-snapshot operations (e.g., Scan
{
and Catalog for File System). For VMware and RMAN proxy configurations, the Virtual Machines and
database files are registered by the proxy application software.
4. Unmount the snapshot.

This snapshot now provides availability for backup copy operations and high speed restore, mount and revert
operations.

Backup Copy Operation

A backup copy operation provides the capability to copy the snapshots to media and can be useful for creating
additional standby copies of data. When you enable backup copy, the snapshots are copied to media (based on the
rules specified for the snapshot copy) during the IntelliSnap backup or at a later time.

During the Backup Copy operation:

z The snapshots are copied to media in a sequential order.

z The snapshots are mounted to the source or proxy computer. The mounted snapshot receives commands to scan,
and backups like a normal file system reading the required contents.
z The file system backup is performed in the Primary Copy of the storage policy of all defined files. The data is
indexed and linked back to the original production host.
z When the backup copy job is finished, the snapshot is unmounted and retained based upon Snapshot Copy
retention settings.

Proxy Configuration

IntelliSnap provides a modernized architecture for handling backup operations within the datacenter. Proxy
capabilities enable an array-based snapshot to mount off the host eliminating backup processes on the production
servers. Each operating system with a IntelliSnap client requires a similar operating system for proxy execution. Data
Protection Suite will automatically link indexing information back to the original host enabling full application
protection for recovery purposes. Execution of application integrity checks may also occur on the Proxy servers to
validate the data prior to backup creation.

For a configuration where snapshots mount off the host to a proxy server, deploy the following agents on the proxy
server:

z File System iDataAgent (Must be similar to Production Host Operating System)

z MediaAgent
z Application specific binaries for proxy (e.g., Exchange Management Pack, Oracle for RMAN, etc)

Verify Configuration using SnapTest Tool

You can validate the IntelliSnap configuration prior to running production jobs using the SnapTest utility. Refer to the

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

IntelliSnap Backup - SnapTest Tool documentation for usage information.

Security and Storage Policy Best Practices

Security Roles

The Storage Array technology can be potentially dangerous without proper controls. Typical script based tools lack
these controls and expose environments to high risk side effects with very little oversight or reporting. A single miss-
aligned scripted argument could cause massive data loss.

Rather than risking the business with scripts or standalone tool sets, the embedded role based security system that Data
Protection Suite provides allows you to entrust critical actions to the right users at the right time. In most medium to
large environments, application, backup, and audit responsibilities may be distributed functions that need to be
coordinated into a single policy.

For Example, a customer may have three specific roles within an operations environment:

z Backup Administrators. They are the day to day operators with access to perform standard backup and
recoveries, manage media, issue reports, etc.
z Application owners (or Database Administrators). They manage the applications running the business such as
application level recoveries and array-based operations.
z Audit & Business Compliance leads. They provide security and process proof of who can perform what and
how.

Specific roles should be defined for the IntelliSnap and Application iDataAgents within the CommCell. The following
table is an example of the Data Protection Suite Security Roles basic structure:

Security Roles (for application Clients or Groups) Backup Application Audit Team
Administrative Management

Agent Management

Agent Scheduling

Alert Management

Browse

Browse and In-Place Recover

Browse and Out of Place Recover

Compliance Search

Data Protection

Data Protection Management

End User Search

Job Management

Library Management

Library Administration

License Management

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

MediaAgent Management

Report Management

Storage Policy Management

User Management
VaultTracker Operations

Storage Policies

Managing proper retention on snapshot copies becomes another critical requirement. Improper retention may cause the
following:

z increase the amount of tier 1 storage that is holding recovery points.

z cause the snapshots to fall short of fully meeting SLA requirements for the business.

Data Protection Suite storage policies are broken down into copies for managing retention on the proper tier of
storage. In a typical storage policy for IntelliSnap, three copies will be available:

z Primary snapshot copy

z Primary backup copy (movement to media)
z Offsite disk/tape copy

Storage policy configuration varies from environment to environment. For example, SLAs for Sub 24 hours RPO/RTO
drastically lower the returns on leveraging snapshot technology on copies beyond 48 hours. Based on this example,
you may set the retention in the following way:

z Primary snapshot copy – 2 days & 0 Cycles

z Primary backup copy – 28 days & 1 Cycle
z Offsite Disk/Tape copy – 60 days & 1 Cycle

This configuration allows snapshot retention on a 48 hour rotation providing multiple high-speed recovery points
available on the array to meet the SLA requirement. It also requires storage space allocation to maintain two persistent
days of change for the associated clients. By setting “cycles” to 0, the removal of old snapshots occurs regardless of
success, so proper alerting and monitoring is required. Improperly setting retention and effects of days and cycles can
adversely affect the available recovery scenarios for the business applications.

Managing Snapshots
You can also perform other operations with snapshots such as out of place refresh, single file recoveries, mount and
browse capabilities, etc. which provide flexibility to execute daily IT operations. Refer to any of the Advanced
documents for an specific Agent for the available operations you can perform to manage snapshots. For example, see
IntelliSnap - Advanced Snapshots - VMware.

Managing Clariion SnapView Clone/Snap and Data Protection Suite Data

Aging

SnapView Clone and Snap allow 1-to-Many relationships between the

production volume and the clone volume (or reserved volume). When
a IntelliSnap job starts, each job consumes a volume residing on a
particular RAID group for each production volume as shown in the

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

table.

Each job will behave differently during the cataloging phase as

required by the Application iDataAgent during backup. Since each
Clone and Snap contains a single job, the very first IntelliSnap job
against the production volume will always be a Full Synchronization,
which requires the snapshots to be activated. Once the Clone has been
attached with the production volume, the Clone target requires to be
synchronized before it can be reused against the production volume.

Depending on the maximum number of Clones/Snaps listed in the

table – please check powerlink.emc.com for other systems. Data
Aging must run against aged Clones/Snaps to free up resources to be
reused for the next IntelliSnap Job.





 Not accurate




 Not enough depth
 Need more code examples




Type your comment 
here. 
(1000 characters left) Submit

Back to Top

© 1997-2013 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 101 of 101