intellisnap nimble storage -...

ADMINISTRATION GUIDEIntelliSnap Nimble Storage

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

IntelliSnap User Guide - Nimble StorageTABLE OF CONTENTS

PRE-DEPLOYMENT

UNIX

WINDOWS

GETTING STARTED

OVERVIEW

PREREQUISITES

DEPLOYMENT

CONFIGURATION

SETUP CLIENTS

OPTIONS

ARRAY MANAGEMENT

ARRAY PROPERTIES

FREQUENTLY ASKED QUESTIONS

INTELLISNAP BACKUP - SUPPORT

SNAPTEST TOOL


Pre-Deployment Test - UnixTABLE 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/cdromRun the following command from the Software Installation Package or mount point:

./cvpkgadd

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 TaskPlease 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 computer2) Advanced options3) Exit this menuYour Choice: [1] 2


Selecting 32bit or 64bit BaseThis 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 modules1) All platforms(32 bit)2) FS and MA only(64 bit)Your Choice: [2]


Selecting Unix Setup Advanced OptionsPlease 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

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

./sudo cvpkgaddFor steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install.

This screen will appear only on AIX and Solaris platform.


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.

Setting Client/Physical Machine Host NameWe 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 NamePlease 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]

The interface names and IP addresses depend on the computer in which the software is installed and may be different from the example shown.


[ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

12. Press Enter.

Deciding if to Config for Laptop or Desktop BackupsDo 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 OnlyDo 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 DirectoryPlease 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 DirectoryPlease 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 GroupMost 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 GroupPlease 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: testgrp1REMINDERIf 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 UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]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 cvdEvery 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 FirewallYou need to configure firewall settings if there is a firewall between thisclient and the CommServe.Is there a firewall between this client and the CommServe? [no]

22. Press Enter.


Setting CommServe Host NamePlease 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 DecoupledIf you do not enter a CommServe name, the installer will treat it as adecoupled 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 EnabledIf 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/sddvgcreate vg_name /dev/sddvgchange –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

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 AdaptersNOTE: Please make sure that the mount points used for this test are not being used by any other application. If they are in use, it may cause data corruption or data loss. Please refer to our online documentation for list of supported Operating systems, Hardware Snapshot engines and File systems.Press <ENTER> to continue...

7. Press Enter.

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

8. Type Y and press Enter.

SnapTest Automatic Snap Operations-----------------------------------------------------We will perform the following operations on the given mount point[s].- Create snapshots- Mount snapshots- Unmount snapshots- Revert original volumes to snapshots- Delete snapshotsWARNING: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

9. Specify the path of mount directory and press Enter.

If you have multiple instance installed, run the following command for SnapTest tool:

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

For NetApp, it is recommended that the revert operation is not tested using the automatic test. Revert should be tested using manual operations.

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.

SnapTest Automatic Snap Operations-----------------------------------------------------------Source Mount Point : /snap1Detecting underlying devices... /dev/sdhDetecting snapshot engine... <Array Name> SNAPNo [<Array Name> SNAP] arrays found in database. Array configuration is required to do snap operations. Do you want to add <Array Name> Array? [Y/N] [Y] :

11. Specify the following information for the detected array:

Array ID

Control host name/ip

User name

Password

Reenter password

Device group

Use only devices belonging to the above device group [y/n]

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

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

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

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


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

Initial deployment and successful run of IntelliSnap backup may take around 4 weeks due to the various environment dependencies. The following parameters are known to affect the deployment and initial run and hence need a thorough evaluation:

Firmware versions on the array

Device types

Mode of access

Security configuration

Operating Systems interacting with the storage array

Application layout on the storage array LUNs


Pre-Deployment Test - WindowsTABLE 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.

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.

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.


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.

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

If you want to include .NET Framework 4.0 Installer in the custom package, select Include .NET Framework 4.0 Installer. 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 usercheck 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.



Click Next.






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



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.

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.

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


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 AdaptersNOTE: Please make sure that the mount points used for this test are not being used by any other application. If they are in use, it may cause data corruption or data loss. Please refer to our online documentation for list of supported Operating systems, Hardware Snapshot engines and File systems. Press <ENTER> to continue...

6. Press Enter.

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

7. Type Y and press Enter.

SnapTest Automatic Snap Operations


-----------------------------------------------------We will perform the following operations on the given mount point[s].- Create snapshots- Mount snapshots- Unmount snapshots- Revert original volumes to snapshots- Delete snapshotsWARNING: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

8. Specify the drive letter of mount directory and press Enter.

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

9. Press Enter to add the detected array.

SnapTest Automatic Snap Operations-----------------------------------------------------------Source Mount Point : E:\\Detecting underlying devices... \\.PhysicalDrive1Detecting snapshot engine... <Array Name> SnapshotNo [<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.

SnapTest Automatic Snap Operations------------------------------------------------------------Mount points to be snapped : E:\\Engine for /snap1 : <Array Name> SNAP Creating snapshot... SUCCESSSnapshot name : SP_805326_805326_-1 Mounting snapshot...SUCCESSUnmounting snapshot... SUCCESS

For NetApp, it is recommended that the revert operation is not tested using the automatic test. Revert should be tested using manual operations.

Enter all the mount points that you want to test. Ensure to specify two "\" after the drive letter e.g., E:\\.


Reverting to snapshot... SUCCESSDeleting snapshot... SUCCESSCongratulations!!! Automatic Snap test completed successfully. Press <ENTER> to continue...


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



Device types

Mode of access





IntelliSnap – Getting Started – Nimble StorageIntelliSnap 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.

HOW DOES INTELLISNAP BACKUP WORK

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

The array is accessed to create a snapshot.

FEATURE SUPPORT GENERIC SOFTWARE SOLUTION

DATA PROTECTION SUITE INTELLISNAP

BACKUPBackup to TapeDuring 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 arraySnapshot 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.


The snapshot is mounted on the proxy or source computer for post backup operations.

The snapshot is unmounted.

This snapshot is used for backup copy operations. This can also be used for restore/mount operations.

During the Backup Copy operations:

The snapshot is mounted to the source or proxy computer.

The mounted snapshot is treated like a file system and the required contents are read.

The file system backup is performed on the Primary Copy of the storage policy.

When the backup copy job is finished, the snapshot is unmounted.

Data Aging:

The jobs for the snapshot are pruned based on the retention policy for the snapshot copy.

The snapshots that are related to the pruned jobs are deleted from the array periodically.

TERMINOLOGY

The IntelliSnap Backup documentation uses the following terminology:

STORAGE DEVICE

A device used for backup or archival purposes.

STORAGE ARRAYA high-end disk storage system. The IntelliSnap software is designed to work in conjunction with the snapshot ability built into the storage array.

PROXYA 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 COPYAn additional copy of the protected data that is used in IntelliSnap operations.


IntelliSnap – Getting Started – Nimble StorageSETUP NIMBLE STORAGE

From the Nimble storage array console, ensure that the Access Control Entry for the client initiator group is set to Volume and Snapshots.

In case you are using a proxy computer for IntelliSnap operations, add the initiator group for the proxy computer and set the Access Control Entry to Snapshots Only.

Ensure that a temporary LUN is allocated to all ESX Servers that are used for snapshot operations.


IntelliSnap – Getting Started – Nimble StorageWHERE TO INSTALL

Install the CommServe on a Windows computer that you want to use as your production server.

If you have a cluster environment, perform the steps described in Install the CommServe in a Clustered Environment.

Follow the steps given below to install the CommServe Modules.

BEFORE YOU BEGIN

System Requirements

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements.

Download Software Packages

Download the latest software package to perform the install.

INSTALLATION

METHOD 1: INTERACTIVE INSTALL - STANDARD




Click Next.

4. Click Standard.

Click Next.

The software can be installed using one of the following methods:

METHOD 1: INTERACTIVE INSTALL - STANDARD

Use this procedure to install the software using the standard installation options.

METHOD 2: INTERACTIVE INSTALL - CUSTOM

Use this procedure to install the software by specifying installation settings and options.


5. Click Create a New CommCell.

Click Next.

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



Click Next.





8. Click Install.

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


s

9. Click Yes.

10. Select one of the following options:

If you do not want to disable Windows Firewall, click Next.

If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next.

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

Click Browse to change the default location.


Click Next.

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

13. Enter the username and password for the CommCell Console administrator account.

Ensure that the drive has at least 1GB of free space. Do not specify a mapped network drive or a FAT drive. Do not save the database files to a compressed drive.

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.

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

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

METHOD 2: INTERACTIVE INSTALL - CUSTOM




Click Next.

OPTION ENABLED /

DISABLED

DESCRIPTION

Setup Software Cache Enabled This option is used to automatically download software packages and updates from FTP sites.

By default, software packages and updates will be stored in the following location:

C:\Program Files\hds\Data Protection Suite\SoftwareCache


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 click Operations Manager. To learn the features included in this package, see What are the Components that are included in different Install Packages.

Click Next.

7. Verify the installation path of the CommServe database engine. This will be the location for the SQL Server System databases.

Click Browse to change the default location, and then click Next.

If you plan to perform VSS enabled backups on the CommServe computer, it is recommended that the CommServe database is not installed on the system drive. VSS restores could cause system state restore issues. The install program installs the database instance.


8. Verify the installation path for the Microsoft SQL Server.



Click Next.





This step might take several minutes to complete.


10. Click Install.

11. Click Yes.

12. Click Next.

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


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.

The CommServe Client Name and CommServe Host Name are filled automatically .

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.

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

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

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


17. Specify the network or local path where you want to store the Disaster Recovery backup files.

Click Next.

18. Enter the username and password for the CommCell Console administrator account.

If you selected Use Network Path, you must also provide the Network share username and the Network share password.

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

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.


IntelliSnap - Getting Started - Nimble StorageSETUP THE ARRAY INFORMATION

Provide the identification information for the array to ensure access.

The following section provides step-by-step instructions for setting up the array information.

1. From the CommCell Browser, click the Storage tab and then click the Array Management icon.

2. In the Array Management dialog box, click Add.

3. Select Nimble Storage from the Snap Vendor list.

Specify the Data IP Address of the array in the Name field.

Enter the Management IP Address of the array in the Control Host field.

For reference purposes, the screenshot below shows the Data IP Address and Management IP for the Nimble storage device.

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

Use the Description field to enter a description about the entity. This description can include information about the entity's content, cautionary notes, etc.

Click OK to save the information.

If you have more than one Data IP Address configured, you will need to add the array information for each of the configured Data IP addresses.

These are the user credentials used for accessing Nimble web console.


IntelliSnap – Getting Started – Nimble StorageThe following agents are supported for Nimble Storage:

SUPPORTED AGENTS - CHOOSE THE AGENT TO CONFIGURE

EXCHANGE DATABASE

MICROSOFT HYPER-V

MICROSOFT SQL SERVER

ORACLE

VMWARE

WINDOWS FILE SYSTEM


Array ManagementUse this dialog box to view, add, or modify the access information for an array.

AVAILABLE ARRAY

This is the list displays all the available arrays in the CommCell. You can associate any array to a subclient and perform the IntelliSnap backup.

The list displays following information about each array:

Name

Name of the array

Control Host

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

User Name

The user account to be used for accessing the array.

Snap Vendor Name

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

Type

Type of array

Description

The additional information specified for the array.

ASSOCIATED ARRAY

This is the list displays all the arrays associated with a subclient or a storage policy copy.

The list displays following information about each array:

Name

Name of the array

Control Host

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

User Name

The user account to be used for accessing the array.

Snap Vendor Name

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

Type

Type of array

Description

The additional information specified for the array.

Add

Click to access the Array Management dialog box, which enables you to add access information for an array.

Edit

Click to edit the array information.

Delete


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.


Filer Properties (General) - Nimble StorageSnap Vendor

Lists the available storage array vendors. In the Snap Vendor box, select the storage array that you want to use.

Name

Use this field to specify the identification information for the storage array.

Control Host

Use this field to specify the name of the device manager server where the array was configured.

User Account

Use this field to type the name of the user account that has rights to access the array.

Description

Use this field to enter a description about the entity. This description can include information about the entity's content, cautionary notes, etc.

These are the user credentials used for accessing Nimble web console.


Filer Properties (Security) - Nimble StorageUse this dialog box to associate user groups who can edit and delete storage arrays. You can do the following using this dialog box:

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

Associate this object with a user group.

Disassociate this object from a user group.

Available Groups

Displays the names of the user groups that are not associated with this CommCell object.

Associated Groups

Displays the names of user groups that are associated with this CommCell object.


IntelliSnap – Frequently Asked Questions - Nimble StorageCAN I REVERT A SNAPSHOT?

No, when using Nimble storage array, you cannot revert a snapshot.


IntelliSnap Backup - SupportTABLE OF CONTENTS

Initial IntelliSnap Setup

License Requirements

Supported Storage Arrays

Backup Types

Platforms

Supported Volume Managers

Multipath I/O Support

INITIAL INTELLISNAP SETUP



Device types

Mode of access




LICENSE REQUIREMENTS

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

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

Capacity License, based on the amount of data you want to protect.

For comprehensive information on licensing, see License Administration.

TRADITIONAL LICENSE

The following license types are available for IntelliSnap.

CAPACITY LICENSE

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

SUPPORTED STORAGE ARRAYS

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

FEATURE LICENSE TYPE LICENSE CONSUMPTION

IntelliSnap Operations Hardware Snapshot Enabler 1 license per CommCellNetApp SnapVault and SnapMirror NetApp Snap Management 1 license per CommCell

LICENSE TYPE LICENSE

CONSUMPTION

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

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


data protection operations:

SUPPORTED HARDWARE ARRAYS

VENDOR SNAPSHOT VERSION/FIRMWARE REQUIRED

LICENSING

REQUIRED

SOFTWARE

PROTOCOL NOTES/CAVEATS

DELL COMPELLENT

SnapshotFirmware version 5.5.14 and above for 5.x and 6.2.2 and above for 6.x.

Snapshot Replay licensing

NoneFibre Channel

iSCSI

Supported on Windows, Linux VMware and HyperV.

Compellent Live Volume feature is not supported.

DELL EQUALLOGIC

Snapshot

Clone

4.2.0 Included None iSCSI On Red Hat Linux and CentOS computers using version 5.5 (32-bit and 64bit)

No UNIX

Boot from SAN volumes is not supported

EMC VNX / CLARIION

SnapView Snap

SnapView Clone

CX500 / CX700

CX3-10 thru CX3-80

CX4-120 thru CX4-960

SnapView Snapshot/Clone

Solutions Enabler Licensing

Solutions Enabler 6.5.1 or higher on Client and Proxy

Navisphere CLI on Client and Proxy

NaviAgent on Client and Proxy

Fibre Channel

FCoE (Fibre Channel over Ethernet)*

No HyperV

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

EMC VNXSnapView Snap

SnapView Clone

VNX 5100, 5300, 5500, 5700, 7500

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

SnapView Snapshot/Clone


Solutions Enabler 7.2 or higher on Client and Proxy

Unisphere CLI on Client and Proxy

Unisphere Host Agent on Client and Proxy

Fibre Channel

iSCSI

VMware with NFS datastores are supported.

ISCSI PowerPath LUNs are not supported.


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

EMC VNX / CELERRA

SnapSure Snap

DART 5.5 or Newer SnapSure Snap License


Solutions Enabler 6.5.1 or higher on Client and Proxy

Navisphere CLI on Client and Proxy

NFS Supported on VMware 4.x.

No HyperV

EMC ISILONSnapshot

Support for OneFS 6.5 and OneFS 7.0

SnapshotIQ LicenseiSCSI


EMC SYMMETRIX

TimeFinder Snap, Clone, and Mirror

DMX3 or Newer TimeFinder Snap, Mirror, Clone Licenses



Fibre Channel


Remote SymApi Server is not supported.


EMC VMAXTimeFinder Snap, Mirror and Clone

VMAX TimeFinder Snap, Mirror, Clone Licenses



Fibre Channel


No HyperV

Remote SymApi Server is not supported.


FUJITSU ETERNUS DX

SnapOPC Snap

EC Clone

Fujitsu ETERNUS V10L22-1000 or higher

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

Local Copy

Thin Provisioning

None iSCSI

Fibre Channel

HDS AMS Copy-on-Write

Shadow Image

AMS 100, 200 & 500

AMS 100, 2100, 2300, & 2500

Licenses for Copy-on-Write (COW) snapshot and Shadow Image

Device Manager 7.1.1 (or higher) Agent installed on Client and Proxy

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

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

Fibre Channel


No HyperV

HDP Volumes not supported for COW.

The Virtual Machine HotAdd feature is not supported.

HDS VSP/HUS-VM USING CCI ENGINE

Shadow Image

Thin Image

HDS HUS-VM, VSP Licenses for Thin-Image (TI) snapshot and Shadow Image


Fibre Channel


SI & TI support for VSP & HUS-VM volumes. Dynamic Provisioned volumes (DP-VOL) are also supported.

HDS HUSCopy-on-Write

Shadow Image

HUS 100 series Licenses for Copy-on-Write (COW) snapshot and Shadow Image



RAID Manager (01-26-03/02

Fibre Channel


No HyperV

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



or higher) installed on Client

HDS USP/VSPCopy-on-Write

Shadow Image

HDS USP, USPv, VSP Licenses for Copy-on-Write (COW) snapshot and Shadow Image




Fibre Channel


No HyperV

COW support for USP volumes.

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


HP EVAEVA Business Copy Snapshot and Clone

EVA HP Business Copy EVA feature

HP SMI-S EVA on Server

Command View Version 9.1 , 9.3

Fibre Channel

iSCSI

No HyperV

HP (HDS OEM) XP, P9500 ARRAYS

Copy-on-Write

Shadow Image

XP 12000 – 24000

P9500

Licenses for Copy-on-Write (COW) snapshot and Shadow Image

HP StorageWorks Command View Advanced Edition Agent (Device Manager 7.1.1 or higher) installed on client and proxy computers

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

HP StorageWorks RAID Manager installed on client and proxy computers.

Fibre Channel


No HyperV The Virtual Machine HotAdd feature is not supported.

HP 3PARSnapshot and Clone

F-Class and V-Class

CIM 3.1.2 and higher is installed

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

Virtual Copy

3PAR SMI-S on Server Fibre

Channel

iSCSI

The snap recovery is supported by retaining the child snap.

Also supports 2.3.1 (MU4) or higher, except 3.1.1.342 , 3.1.1 MU1 + Patch 10, 3.1.1 (MU2), and 3.1.2 (MU2)

IBM SVCFlash Copy

Space-efficient Flash Copy

SVC / V7000 6.1.0.7 or higher

FlashCopy IBM SMI-S on Server Fibre

Channel

iSCSI

No HyperV

Revert operation for space-efficient Flash Copy is not supported.

IBM XIVSnap ANY XIV Array Included IBM XCLI 2.3 or

higher on Client and proxy

Fibre Channel

No HyperV


iSCSI

NETAPP E-SERIES (LSI ARRAYS)

Snapshot

VolumeCopy

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

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

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

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

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

Snapshot

VolumeCopy

LSI SMI-S on Server and server 10.10.6054 or higher

Fibre Channel

iSCSI

LSI Volume Copy is not supported for Hyper-V.

NETAPPSnapshot ONTAP 7.3.5 or higher

ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2

7-mode supported

C-mode supported for ONTAP 8.3

FlexClone

SnapRestore

SnapVault/Mirror for replication

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.

SnapMirror -NetApp replication technology used for disaster recovery.

SnapVault -NetApp replication technology used for backup and recovery.

Fibre Channel

iSCSI

NFS

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

NIMBLESnapshot 1.2.2.0-17686

1.3.0.0-22989

Included None iSCSI Supported on x64-bit Windows, Vmware and Hyper-V.

SUPPORTED HARDWARE ARRAYS FOR REPLICATED ENVIRONMENTS


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


LICENSING

REQUIRED

SOFTWARE

PROTOCOL NOTES/CAVEATS

NETAPP WITH SNAPVAULT SNAPMIRROR

SnapVault SnapMirror

ONTAP 7.3.5 or higher

ONTAP 8.0.1, 8.0.2, 8.1.0, and 8.2 (7-mode supported)

ONTAP 8.2 or higher (Cluster mode supported)

SnapVault/SnapMirror Primary and Secondary

FlexClone

SnapRestore

OnCommand Unified Manager version 4.0.2 (Apr 2011) or OnCommand Unified Manager 5.0 with ONTAP 8.1.0

Provisioning Manager, Protection Manager, & Operation Manager Licenses

OnCommand Unified Manager 6.0 for ONTAP 8.2 or higher (Cluster mode)

Fibre Channel

iSCSI

NFS

CIFS

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

vFilers as a destination supported for Netapp 7-mode.

vFilers as NFS/CIFS share sources will have no indexing due to lacking SnapDiff support.

SUPPORTED SOFTWARE SNAPSHOT ENGINES


LICENSING

REQUIRED

SOFTWARE

NOTES/CAVEATS

DATA REPLICATOR

Not applicable

Not applicable Local native snapshot license (Volume manager snapshot license or QSnap license)

Hardware Snap Engine or native snap or QSnap license

ContinuousDataReplicator

Oracle Solaris Solaris ZFS Solaris (Global zone only) Local native snapshot license

Solaris OS has ZFS snap capability

Set the EnableNativeSnapEngine global parameter to 1 using the SetKeyIntoGlobalParamqscript.

Example:

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

iSCSI initiator is configured on the client computer to mount the Snapshot or Physical proxy server is configured to mount Snapshot over Fibre Channel


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.

This capability is not supported for HDS storage arrays.

NAS attached tape libraries are not supported for IntelliSnap operations.

AGENTS FULL BACKUP INCREMENTAL

BACKUP

DIFFERENTIAL

BACKUP

NOTES

VIRTUAL SERVER (VMWARE)

Before performing revert operations, ensure that all the disks reside on the NFS data store. If the data does not reside on the NFS data store, you cannot perform revert operations.

Backup of VM Templates is not supported.

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

EXCHANGE DATABASEIntelliSnap backups are not supported on Exchange 2007 CCR Passive nodes.

DDR snapshots are not supported on Exchange 2010 DAG clients.

SRM is not supported.

Lotus Notes Database

MYSQLIncremental backups are traditional MySQL log backups. Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy.

ORACLEIncremental backups are applicable for Backup copies.

ORACLE RACIncremental backups are applicable for Backup copies.

MICROSOFT SQL SERVER

Transactional Log backups always use the traditional backup method. Log backups are stored in the Primary (classic) copy.

NAS

VIRTUAL SERVER (HYPER-V)

IntelliSnap backups support online virtual machines with NetApp file servers.

Other storage array vendors use the


PLATFORMS

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

traditional backup method. To perform a IntelliSnap backup, the virtual machine must be offline.

SAP ORACLE

DB2 Backup of partial databases is not supported.

Log files always use the traditional backup method.

UNIX FILE SYSTEM On Demand Backup Set is not supported for IntelliSnap Backup.

Raw partitions in Unix are supported.

Mirrored LVM configuration is not supported.

On HP-UX, non-LVM volumes are not supported for IntelliSnap Backup.

WINDOWS FILE SYSTEM

On Demand Backup Set is not supported for IntelliSnap Backup.

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

WINDOWS 2003 AND HIGHER

MSCS NTFS

SQL version 2005 and later

Exchange 2003, 2007, 2010, 2013 – including DAG

Oracle 10g R2, Oracle 11g R1 & R2

DB2 version 9 or higher

VMWARE ESX iSCSI/FC/NFS datastores ESX vSphere 4.x & vSphere 5.0

AIX 5.3, 6.1, 7.1 (LPARS SUPPORTED, VIRTUAL SCSI DEVICES NOT SUPPORTED)

Veritas Cluster, HACMP

JFS, JFS2, VxFS, VxCFS, IBM General Parallel File System (GPFS)* 3.5.0.7 or higher



Oracle RAC version 10g R2 or higher

DB2 DPF version 9 or higher

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2

HP-UX 11 V2/V3 (PA-RISC AND ITANIUM)

Service Guard, Veritas Cluster HFS, VxFS, VxCFS




DB2 DPF version 9 or

SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2


higher

ORACLE ENTERPRISE LINUX 5.X AND 6.X

ext2, ext3, ext4, reiserfs, VxFS, VxCFS, OCFS2

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




SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

RED HAT LINUX 4.X AND 5.X

Linux Cluster, Veritas Cluster

ext2, ext3, ext4, reiserfs, VxFS, OCFS2, VxCFS, IBM General Parallel File System (GPFS)* 3.5.0.7 or higher





SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c

CENTOS LINUX 4.X AND 5.X

Linux Cluster ext2, ext3, ext4, reiserfs, OCFS2





SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2,Oracle 12c

RED HAT LINUX 6.X

Linux Cluster, Veritas Cluster

ext2, ext3, ext4, reiserfs, VxFS, VxCFS, OCFS2, IBM General Parallel File System (GPFS)* 3.5.0.7 or higher

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





CENTOS LINUX 6.X

Linux Cluster ext2, ext3, ext4, reiserfs, OCFS2






SOLARIS 10 SPARC (SOLARIS ZONES SUPPORTED) Sun Cluster, Veritas

Cluster UFS, VxFS, VxCFS, ZFS






SOLARIS 11 SPARC (SOLARIS ZONES SUPPORTED) Sun Cluster, Veritas

Cluster UFS, VxFS, VxCFS, ZFS






SOLARIS 11 EXPRESS UFS, ZFS

SOLARIS 11 X64UFS, VxFS, VxCFS, ZFS



SAP Brtools 7.0, 7.1 & 7.2 on Oracle 10g R2, Oracle 12c

SUSE LINUX ENTERPRISE SERVER ext2, ext3, ext4, reiserfs,

VxFS, VxCFS, IBM



SAP Brtools 7.0 & 7.1 on Oracle 10g R2, Oracle 11g R1 & R2, Oracle 12c


*All the disks should support snap and must be available on the client where the IntelliSnap job will be initiated. Mount, backup copy and backup operations are supported using proxy GPFS cluster only; this is due to GPFS's limitation which doesn’t allow NSD clone mount on the same GPFS cluster.

Note that this list does not provide a comprehensive list of supported platforms for each agent. See System Requirements for information on the platforms supported by the individual Agents.

SUPPORTED VOLUME MANAGERSVERITAS Volume Manager (VxVM) 5.0 for AIX, Linux, Solaris SPARC and Solaris x64

VERITAS CFS (VxCFS) version 5.1 or higher

Solaris ZFS Mirror

Solaris Volume Manager

ASM Volume Manager

Supported Configurations:

One Physical Volume containing one Logical Volume

One Physical Volume containing one or more Logical Volumes

Multiple Physical Volumes containing one Logical Volume

Multiple Physical Volumes containing one or more Logical Volume

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

MULTIPATH I/O SUPPORTFor 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.

For Dell EqualLogic, install Dell EqualLogic Host Integration Tools package to support Multipath I/O.

HP PVlinks, Solaris MPxIO, Linux Device Mapper and AIX MPIO are supported in HPUX, Solaris, Linux and AIX respectively.

VXVM DMP is supported in AIX, Solaris and HPUX.

HDLM is not a supported MPIO solution with IntelliSnap.

10.2 AND 11

Veritas Cluster

General Parallel File System (GPFS)* 3.5.0.7 or higher



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.


IntelliSnap Backup - SnapTest ToolTABLE OF CONTENTS

Overview

UsageSetup Array ConfigurationPrerequisitesExercise Vendor Snap EngineDetect Snap Engine TypeShow HBA/iSCSI AddressSend SCSI inquiry to mount pointMount Snapshot on Proxy

OVERVIEW

The SnapTest tool is used to test basic snap engine operations and as a diagnostic tool to verify host and array connections. The SnapTest tool is capable of working with multiple mount points for each operation and supports interactive and command line modes.

PREREQUISITES

MediaAgent installed on the computer for SnapTest.

USAGE

Use the SnapTest tool to derive the HBA/iSCSI, the vendor, product, and version details for an array. You can also use the SnapTest tool to:

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

test proxy computers by mounting snapshots.

By default, when Data Protection Suite installation is decoupled, the SnapTest tool will be started in decoupled mode.

If Data Protection Suite is in normal mode, then start the SnapTest in decoupled mode. Use the command line:

SnapTest -local

When multiple instances are installed on the system, the default instance will be selected. To select a specific instance, use the command:

SnapTest -vm <InstanceName>

SETUP ARRAY CONFIGURATION

Set up the array once, for each new array you will use.

The setup is mandatory in decoupled mode and you need to do it before doing any snap operation.

To set up the array information:


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:





5. In the Snap Engine Test dialog box, specify the number corresponding to the snap engine and press Enter. This will prompt you to specify the Mount points to snap.

6. In the SnapTest Create Snap, specify the drive letter of mount directory and press Enter, for example:

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.




14. In the Snap Engine Test dialog box, specify the number corresponding to the snap engine and press Enter.

15. In the Snap Engine Test dialog box, type 3 to Mount Snap and press Enter.

16. Type the number corresponding to the snapshot you want to mount and press Enter. This will prompt you to type the Snap numbers to mount.

Type the numbers separated by commas, if more than one and press Enter.

17. The snapshot is successfully mounted on the proxy computer.

18. To remove the snapshot after perform the test:

Type 0 and press Enter until you exit the tool.

Navigate to <installed_directory>\Base and remove the SnapTestSnapInfo.xml file you copied.

Rename the SnapTestSnapInfo_old file to SnapTestSnapInfo.

Back to Top


intellisnap nimble storage -...

Documents