intellisnap recovery manager quick start guide -...

IntelliSnap™ Recovery Manager

Quick Start Guide

October 2012 – v1.0

IntelliSnap™ Quick Start Guide September 2012 – v0.1 2

IntelliSnap™ Recovery Manager Quick Start Guide ........................................ 4

Introduction to Simpana IntelliSnap™ Recovery Manager (IRM) ................... 5

IRM POD .................................................................................................................................. 5

CommCell .......................................................................................................................... 5 CommServe....................................................................................................................... 5 MediaAgent ....................................................................................................................... 6

IRM Clients .............................................................................................................................. 7

Backup Set ........................................................................................................................ 7 Subclient ............................................................................................................................ 7

Index / Collect Files ................................................................................................................. 7

IntelliSnap™ Recovery Manager Installation Use Cases ................................ 8

When to leverage a Physical Server with IRM ........................................................................ 8

System Requirements ........................................................................................ 9

IntelliSnap™ Recovery Manager POD .................................................................................... 9

Clone and Snapshot Technology .................................................................... 10

Clone ...................................................................................................................................... 10

Snapshot (Copy-On-Write / Redirect-On-Write) .................................................................... 10

Supported Hardware Clone and Snapshot Technology ........................................................ 11

Supported IRM Client – Data Protection and Recovery ........................................................ 12

Supported Applications and Operating Environments ........................................................... 12

IntelliSnap™ Recovery Manager Installation ................................................. 13

Installing the IRM POD .......................................................................................................... 13

Installing the CommServe ............................................................................................... 13 Applying Licenses ........................................................................................................... 22

Installing and Registering Clients .......................................................................................... 23

Required IRM Components ............................................................................................. 23 Installing the IRM Components and registering a new IRM Client.................................. 25

Login to the CommCell Console ............................................................................................ 32

Configuring Disk Library for Index storage ............................................................................ 33

Operation of IntelliSnap™ Recovery Manager ............................................... 36

IntelliSnap™ Pre-Requisites .................................................................................................. 36

Steps to Configure the Hardware Array .......................................................................... 36 IntelliSnap™ Storage Policy Configuration ..................................................................... 38

Enabling a Client for Snapshots ............................................................................................ 41

IntelliSnap™ Enabler ....................................................................................................... 41 IntelliSnap™ Enabler for VMWare .................................................................................. 41 IntelliSnap™ Operations ................................................................................................. 41 Initiate IntelliSnap™ jobs On-Demand ............................................................................ 42 Configure IntelliSnap™ jobs through Schedule Policy .................................................... 42 Viewing Schedules .......................................................................................................... 44

Data Recovery ....................................................................................................................... 45

Browse and Recover ....................................................................................................... 45 Hardware Revert ............................................................................................................. 47 Mounting the Clone and Snapshot for manual recovery ................................................. 49

Security & Storage Policy Best Practices ...................................................... 51

Security Roles ........................................................................................................................ 51

Storage Policies ..................................................................................................................... 52

Appendix ........................................................................................................... 54


Verification of Configuration Using SnapTest ........................................................................ 54

Snap Reconciliation Registry Key.......................................................................................... 57

Snapshot Delete (Asynchronous) Registry Key .................................................................... 58


IntelliSnap™ Recovery Manager Quick Start Guide

This Quick Start Guide provides detailed descriptions for configuring hardware-based snapshot

mechanisms with the IntelliSnap Recovery Manager (IRM). This guide is an introductory how-to along

with the licenses and configuration requirements to integrate IntelliSnap Recovery Manager in a

heterogeneous storage environment. This document covers any of the storage systems supported by

IntelliSnap Recovery Manager and use cases in detail with best practices for scheduling and storage

policies to achieve consistent results both for recovery and protection needs.

IntelliSnap™ Recovery Manager seamlessly executes hardware storage systems snapshots

directly into a protection/recovery process. By automatically integrating application and hypervisor

intelligence with the array snapshot abilities, IntelliSnap™ Recovery Manager interrogates the

applications, hypervisors and their associated file systems to discover volume/disk configurations for

complete snapshot operations. IRM will then coordinate these operations with proper application and

virtual machine quiescent – minimizing administrative configuration and eliminating any scripting

requirements.

Executed as a scheduled protection job, the source system quiesces the selected application or

in a VMware environment will quiesce the selected virtual machines and automatically create a set of

persistent snapshots within the production storage system. The originating system or a defined

secondary proxy server mounts the snapshot and catalogs the application, virtual machine or file-level

contents of the snapshots relative to the production host and the selected contents. This enables an

immediate recoverable consistent data image in minutes with RPOs aligning with the frequency of

schedule all while providing recovery granularity of the data residing inside the storage system

snapshot.

Unlike typical hardware-based snap approaches IntelliSnap™ Recovery Manager extends

beyond simply creating or deleting snapshots. IntelliSnap blends the speed and efficiency of array

snapshots directly into the backup /recovery process – offering full recovery or single file/search and

restore. Once the cataloging completes, the snapshot is retained in the array as a persistent recovery

copy to provide the rapid recovery option to revert or restore the data volumes until the retention has

been met according to the policies within IRM.

IntelliSnap™ supports leading SAN/NAS storage solutions from Dell, EMC, NetApp, LSI, HP,

SUN, IBM and Hitachi Data Systems – and this list continues to expand. Please refer to

documentation.commvault.com for the most up to date revision of the supported hardware and

software configurations.

http://documentation.commvault.com/


Introduction to Simpana IntelliSnap™ Recovery Manager (IRM)

Simpana IntelliSnap™ Recovery Manager is a lightweight solution that can be leveraged from a

physical or virtual server environment. There are specific considerations for these requirements

discussed in detail in the following section. IRM uses the same components as a standard

CommVault Simpana install; however the specific use case for managing snapshots simplifies the

architecture requirements. With IRM it is recommended to leverage the CommServe and MediaAgent

components together on the same server call the POD.

IRM POD

Based on Microsoft Windows platform along with Microsoft’s SQL Server Express, the IRM Pod

retains all job management functionality, metadata, scheduling and reporting under a single console.

This IRM Pod composed of two standard CommVault components, the CommServe application and

the MediaAgent. Together these two components live in a operating domain know as a single

CommCell.

CommCell

The CommCell is a collection or domain of computers, servers, data and infrastructure managed

under the control of a single interface. That interface links a specific CommServe with a uniquely

identified CommCell ID. This CommCell ID includes all of the licensed options for the IRM

environment and the build out for the IRM Pod.

CommServe

The CommServe is the master server managing the configuration and operations for the

CommCell. It is implemented on a Windows host server and contains an embedded version of MS

SQL Express used as the top level database in IRM. One CommServe is used per CommCell and it

must be available to run operations. Only job control and metadata flow through the CommServe.

Indexing and snapshot management routines are executed via the MediaAgent configured with in the

CommCell.

CommServe Database

CommServe Database is based on Microsoft SQL Express Edition containing all the history and

usage of the CommServe. Information such as the job history, the settings for each of the clients,

media type, etc. are all stored within the database and every piece of information that is extracted /

saved / deleted gets recorded within the CommServe Database.

CommServe Services

Job Manager

Displays all information pertaining to a particular running job – data protection / recovery /

Auxiliary copy, settings, and media usages. From within the Job Manager, snapshot jobs may be

started, suspended, resumed and killed.

Media Manager

The Media Manager is responsible for managing the available media(snapshots in IRM) and

ensuring data aging, the pruning of snapshots is running in accordance to retention settings. It

will also provide any hardware related I/O errors that may have been returned by the MediaAgent.

Application Manager

The Application Manager ensures connection from all clients / MediaAgents to the CommServe

and communicates for any changes, updates, or jobs to be run. It also allows for the CommCell

console access – GUI access to the CommServe server.


Schedule Policy

Schedule Policies provide a policy control for job execution for each of the individual clients, client

groups, backupsets, and subclients. It pre-defines the appropriate job properties, such as

Full/Incremental/Differential as well as the advanced configuration / settings, for the scheduled

and defined data set.

Storage Policy

Storage policy controls where the data is stored and how long the retention duration of the

snapshot will be. Inside a Storage Policy are copies. These copies define retention for the

selected storage devices in the IRM environment. There are only two copies of interest within

IRM. The Primary Snapshot Copy and the Primary copy. The Primary Snapshot copy simply

defines the retention of the snapshots that are taken, and the MediaAgent that will be cataloging

the snapshot. The Primary Copy defines where the cataloged indexes are stored.

CommCell Console

Above is the single console (GUI) which embeds all the management features and functions for

the CommCell environment under a single pane of glass. The console is java based and can be run

as a local GUI instance or it can be accessed from anywhere via a browser. All policies, schedules,

operations, alerting and reporting are consolidated in this console and presented to users based on

the security rights and roles they are authorized for.

MediaAgent

The MediaAgent serves as a data mover and indexing resource in a data movement workflow in

the data management environment. This component is used in various roles in the snapshot

creation/mounting operations and the cataloging of content relevant to the client policy. The

MediaAgent will also serve as the media library manager for the disk library to host index data. Those

indexes are written in the CV Archive File format; those data sets are not available for direct

mounting/use rather you would initiate a restore process to produce a native recovery copy of the

data for use.


IRM Clients

Clients are the servers / systems leverage snapshot integration with the production storage

arrays in IRM. A base File System iDataAgent will be installed on each of the servers to provide the

core communication with the CommServe. From there depending on the information or data you wish

to protect, you may load additional iDataAgents for application integration or VMware integration.

These agents provide the proper level of integration at either File System, Database, Exchange, SQL,

or VMware guest point of view to ensure that the correct data is protected at the right level. These

agents will also ensure VSS writers are properly called to ensure the data in the snapshot at the point-

in-time is consistent, provide the ability to call “ESEUtil” commands for Exchange Database

consistency checking, and ensure VMware calls the appropriate software quiescing mechanisms for

creating consistent VMs.

Backup Set

A sub container found within each of these agents is a backup set. The backup set is the overall

container of the client. The easiest way to understand a backup sets is to link it to context of the

system that is being snapped in the environment. The basic physical system storage environment is

the backup set for the file system iDataAgent, while the Exchange Information Store or SQL instance

is the backup set for these two database agents. In a Virtual Context, an overall vCenter is the backup

set as it contains many ESX servers housing and managing the virtual machines.

Subclient

Subclients are the smallest subset of a client. It may be a single folder, a single database, a

single VM or it may be a single LUN or a drive letter from a Windows host perspective (regardless of

how many LUNs are meta-LUN’ed to provide 1 large LUN pool). Subclients are the definition inside of

backup sets that are linked to Storage Policies which will define retention and location of the snapshot

data.

Index / Collect Files

Collect Files are smaller text files that will capture information on what are on each of the clone /

snapshots during an IntelliSnap job. When the snapshot is mounted to be cataloged, the original

information residing on the snapshots are indexed by the collect files stored under the job result

directory under each of the IRM clients. Once the cataloging has been completed, the information will

be sent directly to the MediaAgent responsible for keeping that information longer term within indexes.

These indexes will live on the MediaAgent for the life of the retention of the snapshot either on the

local MediaAgent index cache, or as a part of the disk library defined to protect the indexes and the

POD database backup.


IntelliSnap™ Recovery Manager Installation Use Cases

The Simpana IRM POD components are supported in a physical and virtual deployment

assuming the recommended requirements are met for resource allocation in both configurations.

However, the storage environment and storage connectivity options utilized in the managed

deployment will dictate the requirement for a physical or virtual IRM POD configuration.

IRM requires snapshots to be mounted after successful creation to complete the indexing

activities. This enables POD to provide a stream lined recovery mechanism for all storage arrays

under management. These snapshots can be mounted back to the original host that created them

(the production host) or they may leverage a proxy server (off host) to offload this operation to. The

POD is typically a viable off host option for executing this indexing operation. However there are a

few details to bear in mind:

1. Simpana IRM does not currently support creating or mounting snapshots of Fibre

Channel physical RDMs.

2. IRM cannot mount snapshots of Fibre Channel devices from a physical server to a virtual

machine.

3. If a Fibre Channel device is being snapped and the POD is virtual, the production host, or

an alternate physical server with array masking and access defined must be used.

4. An alternate physical server or the production host will need to be used for processing

ESEUtil consistency checks for Exchange Databases with Fibre Channel devices.

5. ISCSI configurations are supported for both snapshot creation and mounting from a

physical RDM.

6. ISCSI snapshots from a physical host device may also be direct mounted to a virtual

machine and is supported.

When to leverage a Physical Server with IRM

Since the POD can always be installed as a virtual machine it should also be leveraged for more

than just GUI management for the IRM configuration. The POD is an ideal component processing

workload for indexing snapshot data and executing consistency checks as well as being the

management point for granular mining toolsets against the data in the consistent snapshots. All these

capabilities will execute in either a physical or a virtual server environment. However, the physical

architecture of how devices are provisioned and masked will define whether the POD management

server or an alternate physical proxy server should be made available.

An alternate physical server to run the POD components or to manage off host operations is

recommended when:

When the use of Fibre Channel Devices are managed by IRM

When dedicated resources are desired for indexing and processing of snapshot data

If a Virtual Environment cannot provide the resources necessary to successfully implement an

IRM solution.

A physical server will handle all IRM scenarios and provide support for both FC and iSCSI

devices. This server, sized appropriately can easily handle all of the management and recovery

operations for the IRM solution. As always, ensure the physical server environment meets the

minimum recommended specifications for performance expectations.


System Requirements

IntelliSnap™ Recovery Manager POD

IntelliSnap™ Recovery Manager POD server should follow these system requirements:

Item Description

Computer / Processor x64 capable CPU minimum required

5

Allocate multiple virtual CPUs to a virtual machine, if the anticipated SQL Server workload can take advantage of all the virtual CPUs

Memory

8 GB RAM minimum required / 32 GB RAM recommended

Virtual Memory should be set to twice the amount of available physical memory. Memory page sharing and memory ballooning must be enabled on the virtual machine

Hard Disk

2.5 GB of log disk space for installing the software and future data growth

2.2 GB of temp space on the drive on which the Operating System and temp directory resides (This space is used for temporary files copied during the installation or upgrade of the Microsoft SQL Server and CommServe software)

1.5 GB of permanently available disk space on a local or mapped network drive for CommServe Disaster Recovery

100GB of index cache space is required locally to temporarily store the index data

SQL Data files and log files must reside on different disks (different VMFS). It is recommended to place the log files on RAID 1+0 or RAID 1 disks

Disk Library

1TB of disk storage is required for the Disk Library to store the Index:

Network Attached Storage Exclusive 10 GigE port 7200 rpm SAS spindles

Direct Attached Storage SAS (6GB HBA) / FC (8GB HBA) / iSCSI (Exclusive 10GigE) 7200 rpm SAS or SATA Minimum RAID-5 with 7 spindles each

Dedicated Storage Adapters Operating System Windows Server 2008 (32-bit and x64 editions) and 2008 R2

1 2 5

Peripherals DVD-ROM drive

Network Interface Card (with TCP/IP Services configured) with a static IP Address

3 4

Display Any mode other than VGA

The software requires to function with Java Runtime Environment version 1.6.x or higher.

If a JRE version 1.6.0_06 or higher is already available, the software will use the existing JRE software.

If JRE version 1.6.0_05 or lower is available, or no JRE version is available at all, you will be prompted to install JRE version 1.6.0_16.

The software should not be installed on a compressed drive.

1Core Editions are not supported.

2Hyper-V Editions are not supported. However the CommServe may be installed within a Virtual Machine

3Make sure to use the VMXNET virtual network adapter and separate virtual switches, each connected to its own physical

network adapter 4No DHCP support for the CommServe

5IA64 is not supported


Clone and Snapshot Technology

Clone

Clone is a full copy of the data from one device to another target device. It may or may not

represent the data at the Point-In-Time, but will represent the data at the Point-In-Time when the

clone has been split or activated for use. Clones are usually Read-Only until the copy has been

completed. However, recent storage arrays now allow Smart Cloning features, whereby a copy may

not have fully copied but data may still be access – when the data is asked to be read from the clone

target, the read operation is intercepted so that a copy may be done prior to servicing the read

operation. Unlike snapshots since clone is a full copy of the production device, reading the data from

the clone target device will not affect data and performance on the production device.

Snapshot (Copy-On-Write / Redirect-On-Write)

Snapshot is a Point-In-Time recovery solution, where rather than all the production data having

an extra copy, a timestamp is written within the storage array to point to the production device,

signifying a basic pointer to the Point-In-Time data, such as versioning:

Only when it needs to – such as when the original data on the production device needs to be

overwritten – the data will either be copied before the data is overwritten, or some storage arrays will

prefer to redirect the new data that needs to be overwritten and is relinked back to the user as the

“current version” of the data.


Supported Hardware Clone and Snapshot Technology

The following Hardware Clone and Snapshot technology is supported under IntelliSnap™

Recovery Manager:

Vendor Model Requirements

Dell Compellent Storage Center 5.5.2

Dell MD Series Arrays MD Series array must support the SMIS provider 10.10.GG.40 or higher

Dell EqualLogic PS Series Firmware 4.2.0 or higher

EMC Symmetrix DMX-3000 and above

Solutions Enable 7.2 or higher VMAX (Microcode 1108+)

EMC Clariion / VNX

CX500 and above Solutions enabler 7.2 or higher Navisphere / Unisphere Agent VNX in block mode

EMC Celerra / VNX

Celerra / VNX File DartOS 5.6.60 and higher (SUPPORTED FOR VMware ONLY)

Fujitsu Eternus DX S2 series V10L22-1000 and higher

Hitachi Data Systems

AMS / USP / VSP / HUS HDvM and HDS Device Manager 7.2.1 and higher, Raid Manager/LIB version 01-10-03/02 or higher

HP EVA Command View EVA and SMI-S EVA 9.1 or higher

HP 3PAR InServ V-Series 3PAR InServ F-Series

2.3.1 (MU4) or higher

IBM DS3000 Series DS4000 Series DS5000 Series

DS Series array must support the SMIS provider 10.10.GG.40 or higher

IBM SVC 6.1.0.7 or higher

IBM XIV Firmware 10.1 or higher XIVCLI 2.3 or higher

NetApp All FAS OnTap 7.2.6 and higher

Nimble Storage All All

Sun

25XX Series 61XX Series 65XX Series

6780 9176

SUN arrays must support the SMIS provider 10.10.GG.40 or higher


Supported IRM Client – Data Protection and Recovery

The following Environments are supported under IntelliSnap™ Recovery Manager:

Type Supported Versions Requirements / Notes

File System Windows Server 2003 Windows Server 2008

1.5 GB Recommended for S/W

1 GB for log growth

1 GB of temp space for install or upgrade

Microsoft SQL Microsoft SQL Server 2005 Editions Microsoft SQL Server 2008 Editions

Microsoft SQL Server 2008 R2 Editions

170 MB minimum of hard disk space for software/ 498 MB recommended

50 MB of additional hard disk space for log file growth

724 MB of temp space required for install or upgrade (where the temp folder resides)

Microsoft Exchange Microsoft Exchange 2003 32-bit Server Microsoft Exchange 2007 64-bit Server Microsoft Exchange 2010 64-bit Server

114 MB minimum of hard disk space for software/ 498 MB recommended

50 MB of additional hard disk space for log file growth

726 MB of temp space required for install or upgrade (where the temp folder resides)

Virtual Server VMware vSphere 4 and Up

Cluster Support iDataAgents Types Remarks

File System Microsoft

Non-Microsoft

Non-Microsoft Cluster supports VERITAS Cluster and HP Scalable NAS/PolyServe Cluster

Microsoft SQL Microsoft

Non-Microsoft

Microsoft Cluster supports Geo-Dispersed Cluster

Non-Microsoft Cluster supports VERITAS Cluster and HP Scalable NAS/PolyServe Cluster

Microsoft Exchange Microsoft

Non-Microsoft

Microsoft Cluster supports Geo-Dispersed Cluster

Non-Microsoft Cluster supports VERITAS Cluster

Offline Mining Support

SharePoint Document

MOSS 2007 WSS v3.0 SharePoint 2010 Foundation SharePoint Server 2010

Exchange Mailbox Microsoft Exchange 2003 32-bit Server Microsoft Exchange 2007 64-bit Server Microsoft Exchange 2010 64-bit Server

Support is for Mailbox-level recovery for Snapshots of Exchange Database (not VMWare level)

Supported Applications and Operating Environments

Please visit Books On-Line for a complete listing of supported IntelliSnap Applications and

Operating Environments and any potential solution caveats.

http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/default.htm


IntelliSnap™ Recovery Manager Installation

Installing the IRM POD

Installing the CommServe

This procedure describes the steps involved in performing a Standard IRM POD Install, which

includes installation of the CommServe, CommCell Console, File System iDataAgent and MediaAgent.

Before installing the IRM POD, ensure that you have:

Log on to the computer as a local Administrator or as a member of the Administrators

group on that computer.

Close all applications and disable any programs that run automatically, including anti-

virus, screen savers and operating system utilities. Some of the programs, including

many anti-virus programs, may be running as a service. Stop and disable such services

before you begin. You can re-enable them after the installation.

Insert CD labeled #1 into the CD-ROM or DVD-ROM drive.

If the installation program does not launch automatically:

Click the Start button on the Windows task bar, and then click Run.

Browse to the CD-ROM or DVD-ROM drive, select Setup.exe, click Open, then click OK.

Choose the language you want to use during installation. Click the down arrow and select the desired

language from the drop-down list, and click Next to continue:

Select the option to create a new CommCell:


Read the Welcome screen. Click Next to continue, if no other applications are running.

Read the virus scanning software warning. Click OK to continue, if virus scanning software is disabled.

Read the license agreement, then select I accept the terms in the license agreement. Click Next to

continue:

Click Yes to set up the required privileges for the local administrators group:


This option will only appear if the Windows user account used to install the software does

not have the required administrator rights (e.g., if the operating system was newly

installed).

If you choose to click Yes, the install program will automatically assign the required rights

to your account. You may be prompted to log off and log back on to continue the

installation.

If you choose to click No, the installation will be aborted.

You will be prompted at the end of the installation to decide if you want these privileges

to be revoked.

Click Next to continue.


Select either Standard Install or Custom Install as appropriate for your installation, then click Next

to continue:

If applicable, select the components that you wish to install, then click Next to continue:


If you choose to install additional components, you will be prompted to perform additional steps in

configuring the components you choose.

Click OK to install Microsoft .NET Framework:

This option will only appear if Microsoft .NET Framework has not been installed on this

computer.

Click Yes to set up a dedicated instance of Microsoft SQL Server for the CommServe Server:

This prompt will only be displayed if SQL Server database instance is not installed on this

computer.

Clicking No will exit the install program.

The System Reboot message may be displayed. If so, select one of the following:


Reboot Now

If this option is displayed, the install program has found files required by the software that are in use and need to be replaced. Reboot the computer at this point. The install program will automatically continue after the reboot.

Exit Setup

If you want to exit the install program, click Exit Setup.

If you would like to disable firewall on Windows Operation system, then select Yes, otherwise select

No:



If necessary, select this option for automatic FTP downloading and installation of software updates.

If you do not select this option, you can schedule these updates later from the CommCell

Console.


Specify the location where you want to install the software:

Do not install the software to a mapped network drive.


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

/ : * ? " < > | ! ; @ ^ ]

It is recommended that you use alphanumeric characters only.

Click Browse to change directories. Click Next to continue.

Click Enable password check for CommCell to enable a password and then click Next to continue.

If you do not want a password to open the CommCell Console click Next to continue.

This user name and password is used to log on to the CommCell Console - the Graphical

User Interface (GUI) which is used to initiate backups, restores and other related

functions on the computer.

If you enter the password, note down this login and password. You will find it useful later

when you open the CommCell Console.

Select Setup Software Cache option to download the software updates automatically.

Select Schedule FTP Download of Automatic Updates option to schedule automatic FTP

downloading of software updates.



Verify the summary of selected options. Click Next to continue or Back to change any of the options.

The install program now starts copying the software to the computer. This step may take

several minutes to complete. Click Finish to exit the install program and launch CommCell

Console.


Applying Licenses

You may apply your IRM license from the License Administration page. Go to your Control Panel and

select License Administration:

From the License Administration page, we can now select the appropriate license and Click on Apply:

Once the appropriate IRM license has been applied, you can check whether the appropriate IRM

license is enabled from the License Summary:


Installing and Registering Clients

Required IRM Components

IntelliSnap Recovery Manager Solution requires the appropriate components installed as defined by

the customer configuration for each of the clients. Below we will define couple of examples of

installable set for each client / application types in use from this document:


Basic Windows File System Environments

As with all configurations, a CommServe, necessary storage capacity, and MediaAgents must

exist to enable a completely functional solution. On top of the basic infrastructure components, the

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

Windows File System iDataAgent

MediaAgent

CommVault VSS Software Provider

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

agents on the Proxy server:


MediaAgent

Application Environments

When implementing for Application Environments simply add the appropriate IntelliSnap

supported Application iDataAgent to the SnapProtect base configuration as follows on the Production

Host:


MediaAgent

CommVault VSS Provider Software Provider

Application iDataAgent for selected Application

o Exchange – use the Exchange Database iDataAgent

o Microsoft SQL / Sharepoint – use the MSSQL iDataAgent

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

agents on the Proxy server.


MediaAgent

Application specific iDataAgent (Must be the same to Production Host) to enable Proxy

Application API (i.e. – Exchange Management Pack, etc.)

Virtual Environments

The IntelliSnap operation with the Virtual Server Agent enables point-in-time snapshots with

hardware snapshot engines to provide snapshot functionality for data protection operations of virtual

guests. To enable IntelliSnap for the Virtual Environment ensure the following:


MediaAgent

Virtual Server Agent (VSA) iDataAgent

The virtual server Agent may be running as a Hot Add mode guest external to the production

farm to eliminate processing. The Virtual Server Agent leverages Proxy capabilities by default with no

agents installed on the ESX server.

Clustered Environments

Clustered configurations are similar to the basic file system and application configuration.

Providing a supported clustered configuration with IntelliSnap, you require the following on the

Physical Instances and Virtual Instances in a production clustered environment:

Physical Instance


MediaAgent



Virtual Instance


MediaAgent


Application iDataAgent for selected Application (Optional)

o Exchange – use the Exchange Database iDataAgent

o Microsoft SQL / Sharepoint – use the MSSQL iDataAgent

For a configuration where snapshots mount off host to a Proxy server, the Proxy server must be a

non-virtual instance and must have the following agents on the Proxy server.


MediaAgent

Application specific iDataAgent (Optional: Must be the same to Production Host) to enable

Proxy

Application API (i.e. – Exchange Management Pack, etc.)

Installing the IRM Components and registering a new IRM Client

This procedure describes the steps involved in performing a Standard IRM client Install, which

includes installation of the File System iDataAgent and MediaAgent and other required components.

Before installing and registering a new IRM Client, ensure that you have:

Log on to the computer as a local Administrator or as a member of the Administrators

group on that computer.

Insert CD labeled #1 into the CD-ROM or DVD-ROM drive.

If the installation program does not launch automatically:

Click the Start button on the Windows task bar, and then click Run.

Browse to the CD-ROM or DVD-ROM drive, select Setup.exe, click Open, then click OK.

Choose the language you want to use during installation. Click the down arrow and select the desired

language from the drop-down list, and click Next to continue:


Select the option to join / upgrade an existing CommCell:

Read the Welcome screen. Click Next to continue, if no other applications are running.

Read the virus scanning software warning. Click OK to continue, if virus scanning software is disabled.

Read the license agreement, then select I accept the terms in the license agreement. Click Next to

continue:

Click Yes to set up the required privileges for the local administrators group:


This option will only appear if the Windows user account used to install the software does

not have the required administrator rights (e.g., if the operating system was newly

installed).

If you choose to click Yes, the install program will automatically assign the required rights

to your account. You may be prompted to log off and log back on to continue the

installation.

If you choose to click No, the installation will be aborted.

You will be prompted at the end of the installation to decide if you want these privileges

to be revoked.


Select either Standard Install or Custom Install as appropriate for your installation, then click Next

to continue:

If applicable, select the components that you wish to install, then click Next to continue:


If you choose to install additional components, you will be prompted to perform additional steps in

configuring the components you choose.

Click OK to install Microsoft .NET Framework:

This option will only appear if Microsoft .NET Framework has not been installed on this

computer.

Provide the CommServe hostname that you would like to register the IRM client to and Click Next to

continue:


Select the new client name to be used for the IRM client registration and the default communication

interface for the client and Click Next to continue:


If you would like to disable firewall on Windows Operation system, then select Yes, otherwise select

No:


If necessary, select this option for automatic FTP downloading and installation of software updates.

If you do not select this option, you can schedule these updates later from the CommCell

Console.


Specify the location where you want to install the software:


Do not install the software to a mapped network drive.

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

/ : * ? " < > | ! ; @ ^ ]

It is recommended that you use alphanumeric characters only.

Click Browse to change directories. Click Next to continue.

Verify the summary of selected options. Click Next to continue or Back to change any of the options.

The install program now starts copying the software to the computer. This step may take

several minutes to complete. Click Finish to exit the install program.


Login to the CommCell Console

Go to Programs, CommVault, Simpana Express and Click CommCell Console GUI:

Enter your Username and Password configured for the IRM POD:

You may now view the CommCell Console GUI for administrative operations:


Configuring Disk Library for Index storage

You may configure your IRM Disk Library for Index and IRM POD database protection from the

Library and Drive page. Go to your Control Panel and select Library and Drive:

Select the name of the IRM POD and Click Add and OK:


Select Add and then Disk Library

Specify a of the Disk Library:

Specify a Mount Path where the data will be stored.


Note:

You may have many Mount Paths configured under a Disk Library to spread the load between LUNs.

Refer to the Best Practice section for more information.


Operation of IntelliSnap™ Recovery Manager

IntelliSnap™ Pre-Requisites

Steps to Configure the Hardware Array

Defining configuration properties for hardware storage arrays leveraged for IntelliSnap occurs in

the Array Management area of the IRM Control Panel. Example of defining a Dell Compellent array to

the platform enables execution of snapshot operations during the appropriate backup jobs using the

credentials provided.

How to define a Dell Compellent Array:

1. Click on the Array Management in the Control Panel:

2. Select Add on the Array Management Dialog Box:

3. Select Dell Compellent from the Snap Vendor list

4. Specify the Management IP Address or hostname of

the Storage Center in the Name and Control Host

field

5. Specify the access information for the Storage

Center in the User Name and Password fields

(Note: User Name and Passwords are all case

sensitive)

6. Device Group field is not used with Dell Compellent

storage, thus a simple “none” will suffice.


Array Information Matrix

Use the following table to determine the Name, Control Host, Device group options for the supported

storage array in use:

Snap Vendor Name Control Host Device Group Remarks

Dell Compellent Storage Center IP Address “none”

Storage Center Username and Passwords are case sensitive

Dell Equallogic EQL System

Management IP Address

EQL Group IP Address

Storage Pool to be used for clones

EMC Clariion / VNX

Serial Number of Clariion / VNX for

Block

Ensure that the symcfg auth has been enabled for both Service Processors

EMC Celerra NFS Server IP Address Celerra Control

Host

EMC Symmetrix Serial Number of the

Symmetrix

Ensure that the symcfg disc shows the correct Symmetrix

Fujitus Eternus CM IP Address CM IP Address

Hitachi Data Systems

Serial Number of the HDS array

IP Address of the HDvM server

<COW_POOL_ID>-<LABEL>

or

<LABEL>-<COW_POOL_ID>

COW_POOL_ID is the POOL_ID to be used for V-VOLs under COW LABEL to be used with Shadow Image for specific P-VOLs

HP EVA World Wide Name of

the Array Node

Management Server IP Address

of server

HP 3PAR Management

Server IP Address CPG group to be

used for snapshots

IBM SVC Storage ID in 16 digits Cluster IP Address

Physical storage pool used for the

FlashCopy

IBM XIV Serial Number of the

XIV array CM IP Address

LSI Based

Serial Number (Storage Subsystem

World-wide ID)

Device Manager Server IP Address

Device group created on the

array to be used

NetApp FAS IP Address

Nimble

Data IP Address (If more than 1 IP, each

Array Information will be for each Data IP

Address)

Management IP Address

Detailed Field Guides for each Storage Array type are available on Maintenance advantage.

http://documentation.commvault.com also provide details for Array Management Implementation.

http://documentation.commvault.com/


IntelliSnap™ Storage Policy Configuration

IntelliSnap™ operations require a “Primary Snap Copy” to house the indexing information for the

data retained internal to the snapshots. Any currently defined or newly created storage policy

supports the addition of an additional “Primary Snap Copy”. For detailed information on storage policy

creation and the options available for configuration see the online documentation at:

http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/index/ind

ex.html

Create and configure a Storage Policy with a Snapshot Copy:

1. Select a Storage Policy and right click; select “All Tasks”; select “Create New Snapshot Copy”

2. Define a unique Copy Name of the newly created Snapshot Copy and define the Library and

MediaAgent where the Snapshot Copy Indexing information will be stored:

http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/index/index.html

http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/index/index.html


3. Select the Retention tab and define the retention for the number of days or cycles the

snapshot will live internal to the Array and click OK to create the Snapshot Copy within the

Storage Policy:

4. The configured Storage Policy will now show both the previously defined Primary Copy and

the new Snapshot Copy as seen below:

5. To protect Snapshot data in the Primary Snap Copy to the Primary Storage Policy Copy

initiate a Backup Copy to back up the selected jobs. To define which snapshots are marked

for inclusion of the backup copy operation, select the previously configured storage policy,

right click and go to properties.

6. Select the “Snapshot” tab. Under the Snapshot tab are the options to define which snapshots

generate backup copies. The selective rules allow all snapshot operations to drive a

synchronous backup copy or selectively choose snapshots based upon timing or manual

select. Any job meeting the rules for backup copy will be mounted on the defined proxy upon

executing the backup copy operation.


7. To execute the Storage Policy Backup Copy operation, simply right click on the Storage

Policy, select All Tasks, and Run Backup Copy. The Backup Copy dialog box allows for

backup copy creation on demand or through a schedule:


Enabling a Client for Snapshots

IntelliSnap™ Enabler

To enable IntelliSnap™ operations for a given client, you must ensure that the client is enabled

for IntelliSnap™(In Version 9 the IntelliSnap™ name will still show the previous “SnapProtect” name).

Right-click on the client, under Properties select the Advanced tab, and ensuring that

SnapProtect/IntelliSnap is checked:

IntelliSnap™ Enabler for VMWare

To enable IntelliSnap™ for Virtual Machines, you must enable IntelliSnap™ on the Virtual Server

client instead of each individual Virtual Machine. Right-click on the VSA client, under Properties

selected the Advanced tab and ensure that SnapProtect/IntelliSnap is checked.

IntelliSnap™ Operations

IntelliSnap™ operations consist of the following operations:

1. The snpashot job initiates from the CommCell Console via schedule or an on-demand

IntelliSnap job.

2. When the job starts, the file system, associated applications, or Virtual Machines properly

quiesce (VSS calls). 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:

a. Verify the backup job contents (validating the underlying disk structure for file

systems, databases, VM Data stores, etc.. and the required log files)

b. Hardware Level Clone or Snapshot is taken to provide the Point-In-Time copy of

the data within the VSS allowed quiescent time

c. Change the LUN mapping to allow the clone / snapshot to be mounted for

validation of the information on the clone / snapshot

d. Validate mount of the clone / snapshot for post operations (E.g. Scan & Catalog

for File System, Integrity checks for Exchange Database). For VMWare the

Virtual Machines are registered by the proxy application software for granular

cataloging.

4. Array API is finally called to unmounts and unmap the clone / snapshot and retain based

upon retention rules set by the Storage Policy settings.


5. This clone or snapshot now provides availability high speed restore / mount / revert

operations.

Initiate IntelliSnap™ jobs On-Demand

Point to the subclient you wish to run, and right click, Backup. You will be presented with the

following screen:

Even though from a Clone/Snapshot perspective, IRM still defines Fulls as the overall data vs.

Incremental being only changed data. Running Fulls for every clone/snapshot operation is allowed,

however the time to index the data maybe slower compared to running an incremental for only the

changed data.

Configure IntelliSnap™ jobs through Schedule Policy

Click on the Schedule Policy tab under the Policies section. You may also notice some default

scheduled policies have been created:

Right-click on Schedule Policies, then select Add. Select a name for the schedule policy, along

with a schedule to run by clicking Add:


You may also filter out specific Application aware iDataAgents thru the Agent Type

dropdown menu

You may also choose to run a schedule for scheduled Data Recovery under the Type

dropdown menu

Configure the schedule you wish to run:


Apply your backup options as per an On-Demand job and associate clients / backupsets /

subclients you wish to run the schedule on:

Viewing Schedules

Click on the Scheduling icon from the Tool bar:

You may view the entire scheduled data protection job, which may be filtered as well:


Data Recovery

Browse and Recover

To restore data using the browse and recover feature, you may right click on your client, backup

set or the subclient, and look for Browse or Browse Backup Data:


You may now specify to browse the latest protected data, or you may also specify a specific time to

look for especially if you know specifically when the last time the data was indeed on the production

LUN:

Once browsed, you may now select the individual files you wish to restore:


Clicking the Recover All Selected, you may now select to restore the data you have selected:

Hardware Revert

To successfully revert the entire LUN back to the PIT recovery, right click on the Backup Set / Sub

client and click List Snaps:


Choose the time and the IntelliSnap job you wish to restore the LUN back to the point in time, and

select Use Hardware Revert:

Once completed, the LUN in question will have been reverted back to the point in time the data was

protected.

Note: Since you are utilizing a Hardware Revert functionality, all data on that LUN will be

restored back to the point in time of when the data was protected. Ensure that this is what you

are trying to achieve before you proceed with this method.


Mounting the Clone and Snapshot for manual recovery

To mount the Clone or Snapshot for manual recovery, right click on the subclient | List Snaps |

Mount:

Choose a destination path you wish to mount the Clone/Snapshot to:


Click OK, and you will now be able to access the mounted clone/snapshot as such:

Browse through the directory and restore the file as necessary.


Security & Storage Policy Best Practices

Security Roles

The power of a Storage Array in providing fast full volume recovery changes data architectures

and SLA alignment. Any technology providing fast sweeping recovery directly linked to production

data can be potentially dangerous without proper controls. Revert operations are perfect for massive

data corruptions on productions volumes that require fast recoveries, assuming the proper controls

are in place to allow only those who understand what the defined action will do for/to the business.

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 bring an entire

production database environment down and cause catastrophic data loss. Further, restoring data

through array based reverts when a single file/database is all that is necessary can destroy entire

collections of data resetting the environment back hours or days if done incorrectly. Recent mail,

revenue transactions, business data, etc. would all be lost due to a simple mistake in operation.

Rather than risking the business to make or beat the backup window with scripts or standalone

tool sets, an integrated data management platform should provide proper safety controls to allow

critical actions to entrust the right users at the right time while ensuring a reporting and audit system

to overlay the full end-to-end view. In most

medium to large environments, application

operational responsibilities, backup, DR,

compliance and audit may be distributed functions

that need to be coordinated into a single policy.

The embedded role based security system native

to Simpana automates this function.

For Example, a customer may have three

specific roles within an operations environment:

Backup Admins

Application owners (DBAs)

Audit & Business Compliance

Each of these roles “owns” specific

responsibilities for managing and protecting the

enterprise. Backup Admins are the typical day to

day operators with access to perform standard

backup and recoveries, manage media, issue

reports, etc. However, the Backup Admin Role

may not be the right team to execute application -

level recoveries or have the capabilities to issue

array-based reverts for recoveries due to

knowledge and awareness of the application architecture. The Application Owner Role is not so

concerned about the general day to day backup environment, but is laser focused on the application

space they own. They need to know what tools are available to them and who has the capabilities to

execute on those toolsets at any time as they manage the applications running the business. Any

recovery operations involving their applications, especially powerful techniques such as Array reverts

and snapshots must be managed from their group to mitigate any risk to the business. The Audit Role

simply needs to eliminate red flag events and provide security, operational, and process proof of who

can perform what and how.


To meet this requirement specific roles should be defined solely for the SnapProtect and

Application iDA’s within the CommCell. An example of this basic security structure as defined in

Simpana Security Roles as noted here:

Storage Policies

Managing proper retention on the snapshot copies becomes another critical requirement.

Improper retention either increases the amount of tier 1 storage that is holding recovery points, or it

causes the snapshots to fall short of fully meeting SLA requirements for the business. Simpana’s

Storage Policies are broken down into copies for managing retention on the proper tier of storage. In

the typical Storage Policy for SnapProtect, three copies will be available, the Primary SnapCopy, the

Primary backup to disk copy, and the Offsite disk/tape copy. Properly meeting SLA requirements for

the business requires proper alignment for the retention characteristics of each of the storage tiers.

For example, SLAs for Sub 24hr RPO/RTO drastically lower the returns on leveraging snapshot

technology on copies beyond 48 hours. The typical Best Practice for Storage Policy configuration will

change from environment to environment. The standard retention should align with the recovery

requirement for data residing in the SnapCopy or snapshot area of the array. The primary backup to

disk and tape copies would then provide SLA coverage for complete Site based disasters. For

Example, with the previous description retention may be set in the following way:

Primary SnapCopy – 2days & 0 Cycles

Primary Disk Copy – 28days & 1 Cycle

Offsite Disk/Tape Copy – 60days & 1 Cycle


This definition allows snapshot retention on a 48 hour rotation providing multiple high-speed

recovery points available on the array to meet the SLA requirement. This configuration 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.

The other recommended option for SnapCopy retention sets the “days” variable to 0 and focuses

solely on the Number of cycles. In this configuration full backups must occur frequently to allow for

proper snap management. With this setup, the # of snapshots retained will be determined on the

number of cycles configured. The scheduled frequency becomes very important to defining the

environment conditions. If eight snapshots execute over a week timeframe, then 7 days of delta

change must be available in the Array configuration. If eight Snapshots execute in a 48 hour period,

only 48 hours of delta change must be available in the Array configuration. Fully understanding the

schedule and process configurations enable making the proper retention setting when keying off of

“cycles.” Improperly setting retention and effects of days and cycles can adversely affect the available

recovery scenarios for the business applications.

This definition will then enable the Primary and Secondary backup to disk and tape copies.

Backup Copies should follow that standard backup schedule for the production (i.e. – daily backups

should equate into at least one Snap Copy Point in time to drive local and offsite backups).

Remember, backup copies will execute synchronously, and the failure to “backup” Snap Copies to

disk/tape will extend the storage requirement on the Array, as the snapshots will not prune until the

selected recovery points execute in a Backup Copy to disk/tape copies. Application data will always

be consistent on this data movement. Backup Copy operations will always use File System

mechanisms to protect the properly quiesced applications except in the instance of RMAN Proxy’s in

an Oracle configuration. The rest of the data aging follows the standard days and cycles rules for

purging off data sets.

Snapshots may be deleted from the array due to factors like low disk space on the array, number

of snapshots exceeds the threshold etc. and the jobs corresponding to these deleted snapshots can

no longer be used for any data recovery or backup copy operations. Use the nRunSnapRecon

registry key to start snap reconciliation to check for missing snapshots once in every 24 hours and

marks jobs corresponding to the missing snapshots as invalid. See Appendix for detailed information.


Appendix

Verification of Configuration Using SnapTest

Validation of the SnapProtect configuration prior to running production jobs occurs through

the SnapTest utility. This tool is located in the Base folder of the Simpana installation, allows one to

check array connectivity and exercise the hardware snap engine to create and remove snapshots.

Running this prior to productions routines will validate the configuration is properly defined on the

Production Host side.

1. Locate the SnapTest executable in the base directory (..\Simpana\Base\SnapTest.exe) and

run it from the Command Line:

2. Check the Host HBA WWN by selecting Option 2:

We can now validate our HBA WWN to continue the test.

3. Check if we can send a SCSI inquiry to the storage device by selecting Option 3:

For Windows you must enter a drive letter or a mount path (junction point). Unix/Linux

environment is currently not supported.


4. You will now get a result similar to the following:

Confirm that this device is a Dell Compellent device that you are interested in where 4552

equates to 0x11C8 in Hexadecimal and confirms the serial number of the device:

5. Choose option 1 “Perform Individual Snap Operations”:


6. Select Dell Compellent Snap by selecting Option 22:

7. Exercise the selected Snapshot Engine by selecting Option “C”:

This will create a new Snapshot based on the Engine (Dell Compellent Snap – Local Replay) you

have selected and will give you the necessary information to confirm all works. Ensure to step

through steps to delete the snapshot just created to ensure it is removed from the system by selecting

“D” Delete Snap and following the on screen prompts.


Snap Reconciliation Registry Key

This key validates snapshot created by Simpana have not been altered or deleted externally of

Simpana’s management calls, potentially invalidating recovery options within Simpana.

Location

Windows HKEY_LOCAL_MACHINE\SOFTWARE\CommVault

Systems\Galaxy\Instance<xxx>\MediaManager

Unix Not Applicable

NetWare Not Applicable

Key nRunSnapRecon (optional)

Value Not Applicable

Value Type DWORD

Valid Range 1 or x, where ‘x’ is any other value than 1

Default Value None

Created in CommServe

Description

To enable Snap Reconciliation from the Media Manager. When this registry key is set to 1, the snap reconciliation is enabled and the MM will run the snap reconciliation every 24 hours. When this registry key is set to 0, the snap reconciliation is disabled. Also, the absence of this registry key is considered as if the value is set to 0 and hence the snap reconciliation will not be started.

Additional Information

N/A

Applies To IntelliSnap Backup


Snapshot Delete (Asynchronous) Registry Key

This key allows Simpana created snapshots to be deleted at certain intervals when Data Aging

has removed the snapshots from the CommServe Database.

Location

Windows HKEY_LOCAL_MACHINE\SOFTWARE\CommVault

Systems\Galaxy\Instance<xxx>\MediaManager

Unix Not Applicable

NetWare Not Applicable

Key nDeleteSnapsIntervalMin (optional)

Value Not Applicable

Value Type DWORD

Valid Range 1 or x, where ‘x’ is in minutes

Default Value None

Created in CommServe

Description To enable Asynchronous Snap delete management from the

Media Manager. When this registry key is set to x, the snap DELETE command is sent as per the specified interval.

Additional Information

N/A

Applies To IntelliSnap Backup

intellisnap recovery manager quick start guide -...

Documents