Snap Netapp Admin Guide

Administration GUIDE
IntelliSnap NetApp
Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 117

IntelliSnap User Guide - NetApp
Table of Contents
Pre-Deployment
UNIX
Windows
Getting Started
Overview
Prerequisites
Deployment
DataFabric Manager
Setup SnapVault/Mirror
Configuration
Setup Clients
Advanced
Configure Selective Copy For SnapVault
Online Help
Array Management
Array Properties
Best Practices
Frequently Asked Questions
Troubleshooting
IntelliSnap Support
SnapTest Tool
White Papers
IntelliSnap Guide For NetApp Storage Systems

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

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]

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

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

{ Do not use the following characters when specifying the path:
!@#$%^&*():/?\

{ 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

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:

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

{ [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.
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

one) : /snap1
10. Press Enter to add the detected array.

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

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

--------------------------------------

0. Exit
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

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.

5. Click Create a custom package to install on a different computer and click Next.
6. Click Create a Recording of Packages.

7. Click Next.
8. Verify the default location for software installation.
Click Next.
If necessary, click Browse... to change the default location.

{ Do not use the following characters when specifying the destination path: / : * ? " < > | #

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

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.

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.

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

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


{ 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.
20. Select the Configure for Laptop or Desktop Backup option to install Backup Monitor utility. This utility

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

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.

4. The installation proceeds silently. This may take several minutes to complete.
5. Click OK on the dialog box.
6. Click Finish.

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.

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.
6. Press Enter.

--------------------------------------
0. Exit
7. Type Y and press Enter.

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

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

{ Array ID
{ User name
{ Password
{ Reenter password
{ Device group
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.

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

--------------------------------------

0. Exit
evaluation:

z Device types
z Mode of access

Not accurate

Not enough depth

Type your comment
here.

IntelliSnap– Getting Started – NetApp
OnCommand Clustered
Setup Setup
Overview Prerequisites Deployment Unified Data Configuration
SnapVault/Mirror Agents
Manager ONTAP
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 Solution Suite IntelliSnap
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
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.
SnapVault and SnapMirror

SnapVault allows a secondary NetApp file server to store IntelliSnap snapshots. Multiple primary NetApp file servers
can back up data to this secondary file server. Typically, only the changed blocks are transferred, except for the first
time when the complete contents of the source need to be transferred to establish a baseline. After the initial transfer,
snapshots of data on the destination volume are taken and can be maintained independently for recovery purposes.
SnapMirror is a replication solution that can be used for disaster recovery purposes, where the complete contents of a
volume or qtree is mirrored to a destination volume or qtree.
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

Type your comment
here.

IntelliSnap – Getting Started – NetApp
OnCommand Clustered
Setup Setup
Manager ONTAP
Array Licenses
z SnapRestore license for Revert operations (LUNs and NFS shares).
z FlexClone license for backup and restore operations of NFS shares.
z FCP, ISCSI, CIFS, NFS licenses for features such as Fiber Channel Protocol, iSCSI protocol, CIFS file sharing,
and NFS File Sharing. Use the appropriate license for the specific data types.
z HTTP/HTTPS licenses on the NetApp file server to allow communication.
z If you are using SnapVault and SnapMirror you will require the following additional licenses:
{ The NetApp SnapVault/SnapMirror feature requires the NetApp Snap Management license.
{ iSCSI Initiator must be configured on the client and proxy computers to access the storage device.
For the Virtual Server Agent, the iSCSI Initiator is required when the agent is configured on a separate
physical server and uses iSCSI data stores. The iSCSI Initiator is not required if the agent is using NFS
data stores.
{ SnapMirror Primary and Secondary Licenses for disaster recovery operations.

{ SnapVault Primary and Secondary License for backup and recovery operations.
Array Software
The following are required for making backup copies:
z 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 Manager licenses are required for the OnCommand
Unified Manager.
OnCommand Unified Manager 6.0 - In order to support the NetApp cluster mode, install OnCommand Unified
Manager6.0.
z SnapMirror - NetApp replication technology used for disaster recovery.
z SnapVault - NetApp replication technology used for backup and recovery.
Additional Requirements for VMware
When performing IntelliSnap operations on VMware using NFS file-based protocol, ensure the following:
The VMkernel IP address of all ESX servers that are used for mount operations should be added to the root Access of
the NFS share on the source storage device.

Setup The SnapVault/Mirror
Perform the following steps before using SnapVault and SnapMirror:
1. On your source file server, use the license command to check that the sv_ontap_pri and sv_ontap_sec
licenses are available for the primary and secondary file servers respectively.
2. Enable SnapVault on the primary and secondary file servers as shown below:
options snapvault.enable on
3. On the primary file server, set the access permissions for the secondary file servers to transfer data from the
primary as shown in the example below:
options snapvault.access host=secondary_filer1, secondary_filer2
4. On the secondary file server, set the access permissions for the primary file servers to restore data from the
secondary as shown in the example below:
options snapvault.access host=primary_filer1, primary_filer2

Not accurate

Not enough depth

Type your comment
here.

OnCommand Clustered
Setup Setup
Manager ONTAP
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 in the Installation section to install the CommServe Modules.
Before you Begin

System Requirements
Verify that the computer where you want to install the software meets the minimum requirements that are specified in
System Requirements.
Download Software Packages
Download the latest software package to perform the install.
Installation
Use one of the following methods to install the software:
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

Click Next.

4. Click Standard.
Click Next.
5. Click Create a New CommCell.
Click Next.

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


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
9. Click Yes.

10. Select one of the following options:
{ If you do not want to disable Windows Firewall, click Next.

{ If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all
profiles and then click Next.
11. Verify the path to the SQL Server database files.
Click Browse to change the default location.
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.

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.

15. Click Yes to restart the Internet Information Services.
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.

Default Options Selected During Standard Install
These are the default options that are automatically selected when you perform the Standard Install.
Option Status Description

This option is used to download software packages and updates from
FTP sites automatically.
Setup Software Cache Enabled
By default, software packages and updates are stored in the location:
C:\Program Files\hds\Data Protection Suite\SoftwareCache
Method 2: Interactive Install - Custom

Click Next.

4. Click Custom.
Click Next.
5. Click Select components to install on this computer and click Next.

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, then click Operations
Manager. To see what features are 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.

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.
This step might take several minutes to complete.
Click Next.

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
11. Click Yes.

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.

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.

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.

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.

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.
21. Click Yes.

22. Click Yes to wait for the installer to copy the software packages required for the CommServe.
If you want to finish the installation, click No. The software packages will be copied in the background process.
23. Click Finish.
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


Type your comment
here.

OnCommand Clustered
Setup Setup
Manager ONTAP
The following section describes the installation and configuration steps needed to setup the OnCommand Unified
Manager server and its components. For OnCommand Unified Manager 6.0, go to OnCommand Unified Manager 6.0.
Deployment
Install the OnCommand Unified Manager Server
The OnCommand Unified Manager server must be installed before the CommCell™ is set up. The following steps
describe how to install and configure the OnCommand Unified Manager server.
1. Download the OnCommand Unified Manager version 4.0.2 installer from the NetApp Support web site.
{ If installing on a Windows computer, click here.
{ If installing on a Linux computer, click here.
It is recommended that you do not install the CommServe and OnCommand Unified Manager on the same
computer.
2. Launch the executable file.
3. Follow the OnCommand Unified Manager setup prompts to complete the installation.
After the OnCommand Unified Manager software is installed, the OnCommand Unified Manager server starts
discovering, monitoring, collecting, and saving information about objects in its database.
Install the NetApp Host Agent
The NetApp Host Agent is installed on third-party (Windows, Linux or Solaris) hosts. The following steps describe
how to download and install the agent:
1. Log in to the NetApp Support web site.

2. Navigate to Service and Support | Software Download | Download Software | NetApp Host Agent.
3. Select your platform and click Go!.
4. Follow the NetApp Host Agent setup prompts to complete the installation.
Install the NetApp Management Console
The NetApp Management Console is a client software that contains a number of storage system management
applications. The console should not be installed on the OnCommand Unified Manager server as it impacts the server
performance.
The following steps describe how to download and install the NetApp Management Console:
1. From the Setup menu of the Operations Manager, select Download Management Console.
2. Click the link for the version of the NetApp Management Console required for your operating system. For
example;
{ If you are installing on a Windows computer, launch nmconsole-setup-3-0-win32.exe.
{ If you are installing on a Linux computer, enter the following command:
rpm -i <rpm filename>
3. Follow the setup prompts to complete the installation.

Configuration
Configure the NetApp Host Agent
The NetApp Host Agent interface can either be accessed from a computer on which the agent is installed or from any
other computer on the network. The following steps describe how to configure the user access information for the
administrator:
1. Connect to the agent using the web browser:
http://<agent-name>::4092
2. Log in as the super user and configure the management password.

3. Change other options as needed.
4. Click Update.
Discovery of Storage Systems and Networks
The OnCommand Unified Manager server depends on Simple Network Management Protocol (SNMP) to discover
and periodically monitor storage systems. If your storage system is not SNMP-enabled, you must enable it before the
server can discover them. The server needs to locate and identify storage systems so that it can add them to its
database.
Automatic discovery is typically the primary process the server uses to discover storage systems and networks.
However, you can also manually add storage systems and networks:
1. Keep the defaults for the discovery options of Host Discovery (enabled), and Network Discovery (disabled).
2. Start the discovery process by manually adding one storage system from each network.
When you add a storage system, its network is also added. Other storage systems on the same network are found
automatically.
3. After verifying that all of the storage systems have been added, disable the host discovery to save network
resources.
4. After attaching a new storage system to your network, add hosts by using the OnCommand Unified Manager
server or using the following commands through the command line:
dfm host add storage system name
dfm host add -N storage system name
Create Resource Pools
Use the following steps to add Resource Pools to be used for the Vault/Mirror storage provisioning.
1. From the NetApp Management Console, navigate to Set Up | Resource Pools.

2. Click Add in the right pane.
Provide the required information requested in the wizard.

Provisioning Policies
OnCommand Manager Unified Manager has three pre-defined provisioning policies for IntelliSnap.
Such policies will be picked up automatically by Intellisnap and will be displayed in the Provisioning tab of the Snap
Copy Properties dialog box.
Policy Definition
Recommended for SnapVault Destinations
Has on demand de-duplication enabled on secondary

volumes
SnapProtect_Dedupe
Has RAID-DP (double disk failure) enabled that protects
against double disk failures
Recommended for Mirror destinations
SnapProtect_Mirror_Destination Does not have de-dupe or RAID-DP enabled
Has RAID-DP (double disk failure) enabled which protects

SnapProtect_RAID-DP
against double disk failures
To use a provisioning policy from the OCUM server, prefix the provisioning policy name with the string
"SnapProtect_".

Not accurate
Not enough depth


Type your comment
here.

OnCommand Clustered
Setup Setup
Manager ONTAP
Skip this page if you are not using SnapVault and/or SnapMirror
Configuration
Once you have the environment setup for using SnapVault and SnapMirror, you need to configure the following
before performing a SnapVault or SnapMirror operation.
When you select a storage policy, consider that for NetApp 7-Mode and Cluster Mode Filer Snapshots, the same
storage policy cannot be used if you are planning to use the vault/mirror feature. For NetApp 7-Mode Filer snapshot,
use storage policy associated with OnCommand Unified Manager 4.0.2 or OnCommand Unified Manager 5.X and
for NetApp Cluster Mode Filer snapshot, use storage policy associated with OnCommand Unified Manager 6.0.
Create Storage Policy
Use the following steps to create a storage policy.
1. From the CommCell Browser, navigate to Policies.
Right-click the Storage Policies node and click New Storage Policy.
2. Click Next.

3. Specify the name of the Storage Policy in the Storage Policy Name box.
Select Provide the OnCommand Unified Manager Server Information.
Click Next.
4. In the Library list, select the default library to which the Primary Copy should be associated.
It is recommended that the selected disk library uses a LUN from the File server.
Click Next.

5. Select a MediaAgent from the MediaAgent list.
Click Next.
6. Click Next.

7. By default, Yes check box is selected, which enables (MediaAgent side) deduplication on primary copy.
Clear Enable Client Side Deduplication and then click Next.
8. By default, name for deduplication database is displayed in Name box.
Under DDB Location, perform the following:
{ From the MediaAgent list, click the name of the MediaAgent that will be used to store the deduplication
database.
{ In the Location box, type the name of the folder or Browse to the folder in which the deduplication
database must be located.
{ Click OK.
z The deduplication database must be located in a folder and not directly under the root of a disk volume.
z For Linux, make sure to host the deduplication database on LVM volumes.

9. Provide the OnCommand Unified Manager server information.
{ If a OnCommand Unified Manager server exists, click Select to choose from the drop-down list.
{ If you want to add a new OnCommand Unified Manager Server, click Add and provide the OnCommand
Unified Manager server information.
Click Next.
10. Click Finish.

The new Storage Policy creates the following:
{ Primary Snap Copy, used for local snapshot storage

{ Primary Classic Copy, used for optional data movement to tape, disk or cloud.
Create a Secondary Snapshot Copy
After the Storage Policy is created along with the Primary Snap Copy, the Secondary Snap Copy must be created on
the new Storage Policy.
1. From the CommCell Browser, navigate to Policies | Storage Policies.
Right-click the <Storage Policy> and click All Tasks | Create New Snapshot Copy.
2. Type the Copy Name..
Select the Library and MediaAgent from the drop-down list.

Click Vault/Backup or Mirror protection type based on your needs.
It is recommended that the selected disk library uses a CIFS or NFS share or a LUN on the File server.
3. Click the Copy Policy tab.
Depending on the topology you want to set up, click Specify Source for Auxiliary Copy and select the source
copy.
Copies can be created for the topologies listed in the following table:
Topology Source Copy

Primary-Mirror Primary
Primary-Mirror-Vault Mirror
Primary-Vault Primary
Primary-Vault-Mirror Vault
Primary-Mirror-Mirror Mirror

4. Click the Provisioning tab.
Click Refresh to display the entities.
Select the Provisioning Policy from the drop-down list.
OnCommand Manager Unified Manager has three pre-defined provisioning policies for IntelliSnap.
Such policies will be picked up automatically by Intellisnap and will be displayed in the Provisioning tab of
the Snap Copy Properties dialog box.
Policy Definition
Recommended for SnapVault Destinations
Has on demand de-duplication enabled on secondary

volumes
SnapProtect_Dedupe
Has RAID-DP (double disk failure) enabled that
protects against double disk failures
Recommended for Mirror destinations
SnapProtect_Mirror_Destination Does not have de-dupe or RAID-DP enabled
Has RAID-DP (double disk failure) enabled which

SnapProtect_RAID-DP
protects against double disk failures
To use a provisioning policy from the OCUM server, prefix the provisioning policy name with the string
"SnapProtect_".
Select the Resource Pools available from the list.
vfiler option will be shown on the provisioning tab only if the storage policy is associate with OnCommand
Unified Manger 5.x.
When Select vfiler option is selected, all vfilers on the selected resource pools will be shown in the drop-down
list. Resource pool members should be complete filers and not aggregates.
New volumes on this storage policy copy will be provisioned under selected vfiler.
Click OK.
The secondary snapshot copy is created.

5. If you are using a Primary-Mirror-Vault (P-M-V) or Primary-Vault (P-V) topology on ONTAP version higher
than 7.3.5 (except ONTAP 8.0 and 8.0.1), perform the following steps:
{ Connect to the storage device associated with the source copy of your topology. You can use SSH or
Telnet network protocols to access the storage device.
{ From the command prompt, type the following:
options snapvault.snapshot_for_dr_backup named_snapshot_only
{ Close the command prompt window.
It is recommended that you perform this operation on all nodes in the P-M-V topology.
During snap copy creation, if you select the copy to be vault, the selective copy will be checked by default and the
default selection rule will be "All Fulls".
If you do not want the vault copy to be selective, please uncheck the selective copy option during creation and
proceed.
When the selective copy option is checked at the time of vault copy creation, mirror copy will be greyed out.
If you need to switch to mirror copy at the time of creation, uncheck selective copy and change the copy to mirror.
Once a snap copy is created as vault, you cannot change it to mirror and vice-versa.
Similarly, once a selective vault copy is selected, you cannot change it to non selective vault copy and vice-versa.
Configure Backup Copy
Follow the steps given below to configure Backup Copy for moving snapshots to media.

1. From the CommCell Browser, navigate to Policies | Storage Policies.
Right-click the <Storage Policy> and click Properties.
2. Click the Snapshot tab.
Select Enable Backup Copy checkbox to enable movement of snapshots to media.
Click Yes in the Confirm dialog box.
3. Select Specify Source for Backup Copy.
From the drop-down list, select the source copy to be used for performing the backup copy operation.
Click OK.

Not accurate
Not enough depth


Type your comment
here.

OnCommand Clustered
Setup Setup
Manager ONTAP
Setup the Array Information

Only one array management entry should be specified for each NetApp array. Specify the array name or IP that will be
used for sending snapshot management commands. If an array has multiple interfaces, a list of corresponding names is
maintained for each array, so that the proper array management entry is always used.
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 NetApp from the Snap Vendor list.
Specify the name of the primary file server in the Name field.
The name of primary file server may be different in the OnCommand Unified Manager, CommServe,
MediaAgent and other entities, but it should resolve to the same IP address. However, if you plan to create a
Vault/Mirror copy, ensure the IP address of the primary file server resolves to the primary IP of the network
interface and not to an alias.
You can provide the host name, fully qualified domain name or TCP/IP address of the file server.
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.
User to be able to perform the following:
z Create/delete snapshots, volume & lun clones, cifs shares & nfs exports, initiator groups.
Select File Server, then click Primary checkbox for the array type.
Use the Description field to enter a description about the entity. This description can include information about
the entity's content, cautionary notes, etc.

4. Click the Snap Configuration tab and configure the following:
In the Initiator Group Name box, specify the name of the initiator group to be configured on the client
computer and proxy computer to access the array.
In the Mount Retry Count box, type or select the number of retry attempts for a mount operation.
In the Mount Retry Interval (in seconds) box, type or select the time interval after which the next mount
operation will be attempted.
Select Skip busy LUN check to enable skipping busy LUN on the array. When enabled snap job will not go
into pending if there is a mounted snapshot in the volume.
Click OK.

5. Click Add again to enter the information for the secondary array.
Specify the name of the secondary file server in the Name field.
The name of secondary file server may be different in the OnCommand Unified Manager, CommServe,
MediaAgent and other entities, but it should resolve to the same IP address.
Select File Server for the array type.
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.
6. To detect and add Storage Virtual Machines, see Configuring Storage Virtual Machines on NetApp Arrays.
The detect and add option allows you to automatically detect and add Storage Virtual Machines (vfilers or
vservers) on either 7-mode or C-mode NetApp Arrays. When a Storage Virtual Machine is added through the
detect and add option, an array management entry and a deconfigured NAS client are automatically created for

the Storage Virtual Machine. The tunneling option is set by default on the array management entry that
corresponds to the Storage Virtual Machine. The tunneling option enables snap operations to be triggered on the
Storage Virtual Machine via the cluster/physical file server.

Not accurate

Not enough depth

Type your comment
here.

OnCommand Clustered
Setup Setup
Manager ONTAP
The following agents are supported for NetApp:
Supported Agents - Choose the Agent to configure

DB2
DB2 DPF
Exchange Database
Lotus Notes Database
Microsoft Hyper-V
Microsoft SQL Server
NAS
MySQL
Oracle
Oracle RAC
SAP Oracle - Unix
Unix File System
VMware
Windows File System

Not accurate
Not enough depth


Type your comment
here.

IntelliSnap - Advanced - NetApp
Configure Selective Copy for SnapVault
Use the following steps to configure Selective Copy for SnapVault:
1. From the CommCell Browser, navigate to Policies | Storage Policies

2. Right-click the <Storage Policy> and then click Create New Snapshot Copy.
3. From the Snap Copy Properties dialog box, select the following:
a. In the Copy Name box, specify the snap copy name.
b. Select the Selective Copy check box.
c. Select the Library and MediaAgent from the drop-down list.
d. From the Protection Type, click Vault/Backup option.
4. Click the Copy Policy tab.
Click Specify Source for Auxiliary Copy and select the source copy (Primary-Vault).
5. Click Selective Copy tab.
By default, Weekly Fulls will be copied.
6. Click OK.
7. Click OK in the Auxiliary Copy schedule dialog box.
8. From the CommCell Browser, navigate to Policies | Storage Policies | <Storage_Policy>.
The Selective Copy appears in the right pane of the CommCell Browser.
For further information on all other operations you can perform, such as Configuring Frequency of Backup and
Managing Properties, see Selective Copy.

Not accurate
Not enough depth



Type your comment
here.

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

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


Type your comment
here.

Filer Properties (General) - NetApp
General Storage Virtual Machine 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.
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.
User to be able to perform the following:
z Create/delete snapshots, volume & lun clones, cifs shares & nfs exports, initiator groups.
Type
z File Server
Use this option to select storage array as a file server.
Primary
Use this option to select the file server for primary storage array.
z OnCommand Unified Manager
Use this option to select storage array as a data fabric manager.

Not accurate
Not enough depth


Type your comment
here.

Filer Properties (Snap Configuration) -
NetApp
Use this dialog box to specify the details of snap configuration.
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.
Mount Retry Count
Specify the number of retry attempts for a mount operation. By default, the value is set to 5.
Skip busy LUN check
Select this option to enable skipping the busy LUN check on the array. When enabled, a snap job will not go to
pending if there is a mounted snapshot in the volume.
Initiator Group Name
Specify the name of the initiator group to be configured on the client and proxy computer to access the array.
Use Tunneling
Select this option to associate a Storage Virtual Machine with a NetApp array. When selected, all jobs that are
scheduled through the array will apply to the Storage Virtual Machine, too.
To disassociate the Storage Virtual Machine from the NetApp array, clear this option. All jobs scheduled through the
array will no longer run for the disassociated Storage Virtual Machine.

Not accurate
Not enough depth


Type your comment
here.

Filer Properties (Security) - NetApp
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

Type your comment
here.

IntelliSnap – Best Practices - NetApp
Review the following best practices before using NetApp.
General
z It is recommended that you do not use the system volume (typically vol0) for user data.
z For any ONTAP version, it is recommended to provide the host name or IP address of a data port (e.g., e0A,
e0B) during the NAS client or storage array configuration instead of using the management port (e.g., e0M). If
you are using the management port, you must reassign the host name or IP address of the management port to a
data port on the file server.
z To perform snapshots and backup to tape operations in parallel for the same data, use two backupsets.
z ONTAP 8.1.2 is not recommended for performing IntelliSnap backup of NetApp LUNs due to slower
performance when reading from a mounted LUN. Please consider using a later ONTAP version such as 8.1.3.
Please consult with NetApp for recommendations on the ONTAP version which is best for your environment.
Space Utilization
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.
When planning for Snapshots, group LUNs according to their rate of change. For example, group LUNs with a high
rate of change in the same volume and group LUNs with a low rate of change in another, separate volume. When
calculating the size of volumes, use the rate of change to determine the amount of space necessary for Snapshots.
Volume to LUN
IntelliSnap provides the full suite of capabilities for recovery regardless of the Volume to LUN relationship and ratio.
However, a 1 to 1, Volume to LUN, relationship might simplify storage and application management. It is also best to
ensure that each LUN resides within a Qtree in SnapMirror and SnapVault configurations. Thin Provisioned Volumes
with LUNS make your storage provisioning and snapshot management flexible.
NetApp Schedule for Snapshots

Disable the native NetApp schedule for snapshots on volumes that Data Protection Suite manages. This ensures
snapshot retention and storage use is in line with the policies defined within Data Protection Suite. Using the default
setting for internal snapshot scheduling might cause contention problems if multiple calls to create snapshots occur at
the same time. To change the default setting, you can clear the Scheduled checkbox for the volume from Filer View or
System Manager.

Not accurate
Not enough depth


Type your comment
here.

IntelliSnap - Frequently Asked Questions
- NetApp
Table of Contents
What Is The Maximum Number Of Snapshots Created For Each Volume?
Can I Create Additional Provisioning Policies For Secondary Copies And Use Them For IntelliSnap?
Can I Use A Non Root User To Configure An Array Or NDMP?
How Do I Verify That The Destination Filer Has SnapMirror Access To The Source Filer?
How Does The SnapMirror Process Work?
How Does Data Aging Work With SnapMirror?
Can I Disable Tunneling for a Storage Virtual Machine?
How do I select vfiler as destination for secondary(vault/mirror) copy?
What is the maximum number of snapshots created for each volume?

The maximum number of snapshot created for each volume is 255.
Can I create additional provisioning policies for secondary copies and use
them for IntelliSnap?
Additional provisioning policies for secondary copies can be added to the OnCommand Unified Manager. Any
provisioning policy with a name starting with “SnapProtect_” (case in-sensitive) will be displayed in the IntelliSnap
console for use in storage policy copies.
Can I Use a Non Root User to Configure an Array or NDMP?

You can use a Non-Root user for the Array configuration and NDMP configurations. To configure the array with a
non-root user, execute the following commands:
z To create IntelliSnap role with proper rights:
NetApp1> useradmin role add snapprotectrole -c ”[SnapProtect Management

Role]" -a login-ndmp,login-http-admin,api-*
Example:
NetApp1> useradmin role add snapprotectrole -c ”SP Mgmt Role" -a login-ndmp,login-http-admin,api-*
z To add a role to the newly created IntelliSnap group:
NetApp1> useradmin group add snapprotectgroup -c ”[SnapProtect Management

Group]" –r snapprotectrole
Example:

NetApp1> useradmin group add snapprotectgroup -c ”SP Mgmt Group" –r snapprotectrole
z To create an user for the Array credential in the Data Protection Suite Control Panel.
NetApp1> useradmin user add snapprotectuser -c ”[SnapProtect Management

Account]" -n ”S Admin" –g snapprotectgroup
Example:
NetApp1> useradmin user add snapprotectuser -c ”SP Mgmt Account" -n ”S Admin" –g

snapprotectgroup
Use the Same Credentials for NDMP
You can use the same credentials for NDMP that you use for the array.
To configure NDMP with the same credentials, enter the encrypted password in the following command, and then
execute it:
NetApp1> ndmpd password [snapprotectuser]
For example:
NetApp1> ndmpd pswd1 snapprotectuser
How Do I Verify that the Destination Filer Has SnapMirror Access to the
Source Filer?
To ensure that SnapMirror jobs run, the destination filer must have SnapMirror access to the source filer. If the name
or IP address of the SnapMirror filer appears in "/etc/snapmirror.allow", then the destination filer has access.
To add entries to "/etc/snapmirror.allow" execute the following command:
source-filer> wrfile /etc/snapmirror.allow

destination-filer
<Ctrl+C>
source-filer> rdfile /etc/snapmirror.allow
destination-filer
Alternatively, you can go into each of the hosts in OnCommand Unified Manager and configure the the proper
security rights for source and destination in the Fabric-Attached Storage settings.
How Does the SnapMirror Process Work?

1. To get the full, detailed Snap Management plan so that SnapMirror/SnapVault can run, NetApp runs a
conformation check during the first auxiliary copy job.
{ On NetApp

{ On Data Protection Suite
2. During each SnapMirror auxiliary copy job, SnapMirror creates a “BackupVersion," which is a new Snapshot of
the entire volume that requires replication.
3. Once a new Snapshot for SnapMirror is available, the Snapshot is listed under the volume on the Primary Filer.

4. The new Snapshot also appears in the current SnapMirror session.
5. On the destination filer site, the same Snapshot appears. In addition, if there were any previous SnapMirror on-
demand jobs run, only the very last one remains on the target box.
NetApp calls this a “Swizzling Process”. That is, the primary Fabric-Attached Storage (FAS) creates a delta set
between the original snapshot used from the previous SnapMirror job and the new snapshot created for the
current SnapMirror job. Only the details of the snapshot and the deltas are sent to the destination FAS, and refer
to the previous snapshot, which was formerly the target SnapMirror session. The volume is updated to match
what is in the primary FAS. The previous snapshot is not deleted because the entire process is a background job.
How Does Data Aging Work with SnapMirror?

1. Once a job has been Data-Aged or manually deleted, the job no longer appears in the SnapMirror target either.
SnapVault is not affected by this process.
{ Before deletion on Data Protection Suite
{ Before deletion on SnapMirror
{ After deletion on Primary FAS

{ After deletion on Data Protection Suite
{ After deletion on the secondary FAS
2. The DataAging process does not remove this snapshot either. Only the next auxiliary copy job deletes this
snapshot. After a new job runs, AuxCopy reports that there is no new data to move.
The primary FAS shows that a new snapshot is used for SnapMirror.

3. The secondary FAS shows the new snapshot here, but the process has not removed the volume snapshot that
pertained to Job 18.
Now the job has been deleted from Data Protection Suite. This won’t affect the SnapMirror relationship until the
next job runs and another auxiliary copy job runs. The latest SnapMirror snapshot that was synchronized to the
secondary FAS is responsible for deleting the snapshot on the destination FAS box.
Can I disable Tunneling for a Storage Virtual Machine?

Yes. If you want to disassociate a particular Storage Virtual Machine from a NetApp array, then you can turn off the
tunneling option.
All jobs scheduled through the array no longer run for the disassociated Storage Virtual Machine.
To turn off tunneling:
1. Log into CommCell Console.

2. Click the Storage tab, and then click Array Management.
3. Select the Storage Virtual Machine for which you want to enable tunneling, and then click Edit.

4. Click the Snap Configuration tab, clear Use Tunneling, and then click OK.
5. Click the General tab, and then under Credentials, click Change.

6. In the User Name and Password boxes, enter the NDMP credentials, and then click OK.
7. Click OK to close the Filer Properties dialog box.

8. Click OK to close the Array Management dialog box.
How do I select vfiler as destination for secondary(vault/mirror) copy?

1. Create resource pool with physical filer and not aggregate as resource pool member.
2. When creating secondary snapshot copy, then
Select the resource pool(s) created in (1), and
Enable the "Select vFiler" option and select the required vfiler from the dropdown list.

Not accurate
Not enough depth


Type your comment
here.

IntelliSnap - Troubleshooting - NetApp
Snap creation fails with a busy LUN error
A snapshot enters a busy state in the following scenarios:
z When there are LUN clones backed up in the snapshot

z When snapshots are mounted manually outside of the IntelliSnap backup, through the CommCell Console, or
for IntelliSnap backup operations such as backup copy creation
Busy snapshots may cause IntelliSnap backups to go pending. If you have busy snapshots, consider the following:
z Delete the snapshots in the reverse order they were created in.
z Do not mount a volume and create another IntelliSnap backup for the volume.
The IntelliSnap backup software will detect busy snapshots and will not allow an additional snapshot to be
created until there are no busy snaps. To avoid this snapshot dependency, do not manually create a snapshot of a
volume while you have a snapshot mounted.
z If you have a situation where the busy snapshot is no longer mounted but still shows as busy, proceed to delete
all the additional snaps that were created while the busy snap was mounted. The snapshot will no longer be
busy.
To avoid the snap dependency for NetApp ONTAP version 7.3, use the snapshot_clone_dependency volume
option to enable the system to lock the backup of snapshot copies for the active LUN clone. You will be able to
delete the base Snapshot copy without having to first delete all of the more recent backing Snapshot copies.
If you are using any other applications on the LUN, review the documentation for impacts caused by using the
snapshot_clone_dependency volume option. If you delete the snapshot cloned by the LUN with the volume
option enabled, you will not be able to restore the clone from one of the later snaps. The IntelliSnap backup
will detect if the dependency option is enabled and will allow additional snapshots to be created, even if the
snapshot is mounted.

Not accurate
Not enough depth


Type your comment
here.

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

evaluation:

z Device types
z Mode of access
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

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

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

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

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

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),

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

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

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.

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

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

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

higher

11g R1 & R2, Oracle

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

higher
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

higher
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

higher
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

higher

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

higher
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

higher
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

higher
Solaris 11 Express UFS, ZFS
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
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

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

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


Type your comment
here.

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

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:

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.
{ Array ID
{ User name
{ Password
{ Reenter password
{ Device group
Exercise vendor snap engine

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

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:

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:

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:

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:

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.

15. In the Snap Engine Test dialog box, type 3 to Mount Snap and press Enter.
16. Type the number corresponding to the snapshot you want to mount and press Enter. This will prompt you to
type the Snap numbers to mount.

Type the numbers separated by commas, if more than one and press Enter.
17. The snapshot is successfully mounted on the proxy computer.
18. To remove the snapshot after perform the test:

{ Type 0 and press Enter until you exit the tool.
{ Navigate to <installed_directory>\Base and remove the SnapTestSnapInfo.xml file you copied.
{ Rename the SnapTestSnapInfo_old file to SnapTestSnapInfo.
Back to Top

Not accurate
Not enough depth


Type your comment
here.

IntelliSnap Guide on NetApp Storage
System
Table of contents
IntelliSnap Guide Objective and Overview
NetApp Storage System Overview
Integration Requirements for IntelliSnap
Array and Solutions Enabler Software Licenses
Supported Applications and Operating Environments
Data Protection Suite Software
IntelliSnap Array Configuration Details with NetApp FAS
SnapVault and SnapMirror Configuration - DataFabric Manager (DFM)
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
Manipulating Snapshots
Appendix
VADP-SPE User Permissions
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.
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.
In addition, IntelliSnap can use SnapVault and SnapMirror to perform disk to disk backups between NetApp arrays by
moving only the changed blocks from one NetApp Array to another, based on the relationships that are defined on the
storage. When Snapshots replicate from one NetApp Array to another, they maintain all capabilities for off-host proxy
backups and index all snapshot copies, etc. Therefore, you can manage large data sets with one data management
platform to do all of the following:
z Create, mount, dismount, retain, recover, and delete snapshots

z Create thin provision replication policies
z Provision storage on the secondary NetApp Array
NetApp Storage System Overview

NetApp provides customers with a storage platform that meets all storage needs, from NAS-based storage to block-
based storage. NetApp File-Attached Storage (FAS) devices provide a unified storage platform for mixed data types
and access protocols via the ONTAP operating system. NetApp’s Data ONTAP implements snapshots by tracking
changes to disk-blocks on the WAFL file system.
While very similar in function, NetApp's SnapVault and SnapMirror are two different technologies. SnapMirror
relationships exist between a source volume on a primary array and a destination volume where the copy resides on
the secondary array. SnapVault relationships exist between a source volume/qtree on a primary array and a destination
volume/qtree where the copy baseline and snapshot-vaulted versions reside on the secondary array.
In IntelliSnap all of these operations are orchestrated by a set of APIs built into DFM (Data Fabric Manager). DFM
registers each of the arrays, and creates policies and relationships that define the replication topology, schedule, and
retention. Required DFM components are:
z Operations Manager

z Protection Manager
z Provisioning Manager
This guide is a brief overview of NetApp FAS arrays and the necessary steps to configure Data Protection Suite with
NetApp FAS systems.
For further NetApp FAS support, documentation, and training material, visit now.netapp.com.
Integration Requirements for IntelliSnap

Array and Solutions Enabler Software Licenses
The Data Protection Suite software requires enabling certain array components and licenses on the NetApp storage
system to achieve a successful integration with the software. Refer to the IntelliSnap Backup - NetApp 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.
Server mounting the snapshot or clone for backup purposes off of the Production
Proxy Host Host.
Array Hardware Storage Array executing the snapshots.
Agent for protecting the file system of a host. It is the base requirement for most
File System iDataAgent
Application iDataAgent.
Agent for creating and managing snapshots as well as for writing data to backup
MediaAgent
targets.
Agents that provide application-aware data protection operations for applications
Application iDataAgent such as SQL, Exchange, Oracle, etc. Allows you to create application-aware
snapshots.
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.
NAS iDataAgent Logical agent that is linked to an NDMP host for data protection operations.
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 host to a Proxy server, implement the following agents on the Proxy
server:
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, add the

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

z MediaAgent
z VSS Software Provider (Windows Only)
z Application iDataAgent for selected Application (e.g.,
Exchange, SQL, Oracle)
For a configuration where snapshots mount off host to a Proxy server,

implement the following agents on the Proxy server.
With SnapVault and SnapMirror capabilities, you can also choose

a Proxy Server from the Secondary Array. To do so, the same
software components must be available in the Proxy to Tape
Server.
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.
NAS Environments

For Network Attached Storage environments (NetApp Only) the configuration
is slightly different. Since a NAS iDA is a logical agent pointing to an assigned
IP address to the NetApp FAS, nothing must be installed for the Production
host. Simply configure the NAS iDA per Books Online and check the “enable
IntelliSnap” box under the client advanced properties to enable local ONTAP
snaps to drive the protection operation. There is no notion of a Proxy in this
configuration due to the local nature of the ONTAP snapshot. NDMP
operations will simply function from the primary FAS.
In the scenario where the customer wants to execute “crash-consistent”

snapshots of VM, database, or application environments, the best way to
achieve this is through the NAS iDA. It allows the customer to define the
Volume, qtree, or LUN as the contents of a NAS iDA subclient and execute a
crash consistent snap at the schedule defined on the subclient.
Refer to Getting Started - NAS for configuration steps.
VMWare 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 VMWare install the following on the physical
server(s) or virtual hot-add guest(s):

z MediaAgent
z Virtual Server Agent (VSA) iDataAgent
Refer to Getting Started - VMware for deployment and configuration steps.
Microsoft Hyper-V Environments
IntelliSnap enables fast protection of large or volatile Hyper-V environments

placing minimal load on the production Virtualization Farm. IntelliSnap
technology integration with the Virtual Server Agent (VSA) enables the Array
to perform backups in minutes even with large numbers of virtual machines
and sizable data stores. Granular access provides individual file and folder
recovery from the secondary tier of storage along with the full guest .vhd files.
Prior to configuring the virtualization environment, deploy the proper agents

requiring snapshot integration with the Array. Microsoft Hyper-V is very
similar to an application environment for the components necessary to execute
IntelliSnap operations. Microsoft Hyper-V virtualization environments require
the following agents:
To enable IntelliSnap for the Virtual Environment install the following on the
physical server(s) or virtual hot-add guest(s):

z MediaAgent

z Virtual Server Agent (VSA) iDataAgent
z VSS Software Provider
Refer to Getting Started - Microsoft Hyper-V for deployment and

SnapVault and SnapMirror Environments
IntelliSnap now extends enterprise

management for backup and recovery in the
data center for local Snapshot copies on
NetApp primary storage and replication to
secondary and tertiary storage, as well as tape
creation. Any of the above environments
discussed (application data, file data for NAS,
file data in LUNs, or data in virtualized
environments) with SnapVault and SnapMirror
enables management, storage provisioning,
cataloging, and the granular recoverability for
seamless operation off of any copy.
Refer to Setup SnapVault/SnapMirror for

IntelliSnap Array Configuration Details with NetApp Fabric-Attached

Storage (FAS)
Provisioning storage as a NFS/CIFS target or a LUN requires physical disks assignment in the Array to an Aggregate
for storage usage. Volumes creation occurs within the Aggregate grouping of disks internal to the Array. Generation of
Shares and Qtrees for NFS/CIFS access occurs within these volumes. Additionally LUNS live internal to the volumes
for block-based access to hosts. NetApp’s snapshot mechanism is a pointer-based approach so blocks of the active file
system blocks co-mingle with snapshot blocks internal to the LUN. Ensure sufficient space is available for snapshot
generation and retention of the point in time copies. The required space directly correlates to the change rate of the
data stored on the LUN and the number of snapshots retained. NetApp’s default setting is 20% for snapshot capacity.
In the graphic below, note that the total volume size is greater than the total capacity. The extra space designates the
reserved area for snapshots.
Refer to the IntelliSnap Configuration - NetApp documentation for array configuration steps.
SnapVault and SnapMirror Configuration - DataFabric Manager (DFM)
To Integrate SnapVault and SnapMirror it required to install Data Fabric Manager 4.0.2 and register all pertaining
NetApp arrays with the Management Console. DFM may be installed on any Windows server in the environment and
will require licensing keys for Operations Manager, Provisioning Manager and Protection Manager. Multiple DFM
instances can be leveraged for distributed environments and redundancy control.

Once installed it is required to define “Resource Pools” for the SnapVault secondary and SnapMirror secondary
targets. IntelliSnap will automatically provision the proper Qtree, volume, and/or LUN configuration for the desired
source contents of the defined resource pools. Resource Pools are allocated by adding defined aggregates in the
NetApp FAS. These can be created from within the NetApp Management Console.
Refer to the IntelliSnap Configuration - NetApp SnapVault/SnapMirror 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.
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).
{ Create a snapshot or clone.
{ 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 and retain based on retention rules.
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.
With SnapVault and SnapMirror operations, you can perform backup operations with the SnapVault or SnapMirror
copy. To do so, you must define the SnapCopy for Backup Copy operation in the Storage Policy properties. You can
set the Subclient Option, Separate Proxy for Snap to Tape to activate servers that are local to the secondary and
tertiary copies to mount snapshots and drive the data protection operations to disk or tape.
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
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
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.

Manipulating 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.
Appendix
VADP-SPE User Permissions
A dedicated account can be used for performing VSA with IntelliSnap. This account requires additional permissions
for the VADP User role. This account is only required in the event that you want to create a restricted account.
Backup Permissions
z Allocate Space
z Browse a Datastore
Datastore
z Configure Datastore
z Remove Datastore
Host - Configuration Storage partition configuration

z Disk Change Tracking
Virtual Machine - Configuration z Disk Lease
z Low Level file operations
z Allow read-only disk access

Virtual Machine - Provisioning z Allow virtual machine download
z Clone virtual machine
z Create snapshot
Virtual Machine - State
z Remove snapshot
restore Permissions
Datastore Allocate Space
Host - Configuration Storage partition configuration
Network Assign network
z Assign virtual machine to resource pool
Resource
z Assign vApp to resource pool
z Add existing disk

z Add new disk
z Add or Remove device
z Advanced
z Change CPU count
z Change Resource
z Disk change Tracking
Virtual Machine - Configuration z Disk Lease
z Host USB device
z Memory
z Modify device setting
z Raw device
z Reload from path
z Remove disk
z Rename
z Reset guest information

z Settings
z Swapfile placement
z Upgrade virtual hardware
z Power Off
Virtual Machine - Interaction
z Power On
z Create new
Virtual Machine - Inventory z Register
z Remove
z Unregister
z Allow disk access
Virtual Machine - Provisioning z Allow read-only disk access
z Allow virtual machine download
z Create snapshot
Virtual Machine - State z Remove snapshot
z Revert to snapshot

Not accurate
Not enough depth


Type your comment
here.
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.

Snap Netapp Admin Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Snap Netapp Admin Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Administration GUIDE

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

Configure Selective Copy For SnapVault

Frequently Asked Questions

IntelliSnap Guide For NetApp Storage Systems

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

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

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

Selecting Unix Setup Task

6. Type 2 and press Enter.

Selecting 32bit or 64bit Base

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

Selecting Unix Setup Advanced Options

Setting Client/Physical Machine Host Name

Setting Client Name

Selecting Modules to Install.

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

Selecting Modules to Install.

12. Press Enter.

Deciding if to Config for Laptop or Desktop Backups

13. Press Enter.

Deciding if to Install Agents for Restore Only

14. Verify the default path for software installation.

{ Do not install the software to a mapped network drive

{ It is recommended that you use alphanumeric characters only

Preparing Installation Directory

15. Verify the default path for log files.

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

{ It is recommended that you use alphanumeric characters only

Preparing Log Directory

16. Press Enter.

Deciding If to Use a Unix Group

17. Type the Group name and press Enter.

Press Enter again.

Setting Unix Group

Setting Access Permissions for Group and Other Users

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

Setting Instance Port Number of cvd

20. Press Enter.

Port Number for EvMgrC: [8402]

21. Do one of the following:

For firewall options and configuration instructions, see Firewall Configuration.

Deciding If to Configure Firewall

22. Press Enter.

Setting CommServe Host Name

23. Press Enter.

Deciding if to Install Decoupled

Else, press Enter.

Specifying If CommServe Per-Client Certificate is Enabled

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

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

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

For example, use the following command:

mkvg –y vg_name hdisk12

3. Create a Logical Volume in the Volume Group.

For example, use the following command:

mklv -y lv_name -t jfs2 vg_name 2G hdisk29

lvcreate –n lv_name –L 2G vg_name

4. Create a File System on the Logical Volume.

For example, use the following command:

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

mkfs -t ext3 /dev/vg_name/lv_name

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

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