EMC Clariion Storage System Guide for SnapProtect

SnapProtect Guide Objective and Overview

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

• discover volume/disk configurations for the snapshot operations
• coordinate snapshot operations with proper application quiesce
• minimize administrative configuration and eliminating scripting requirements

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

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

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

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

EMC Clariion Storage System Overview

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

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

This guide will provide an in-depth storage technology overview, examples of configuration and necessary steps to configure Calypso with EMC Clariion systems.

For further EMC Clariion training material, please visit powerlink.emc.com.

Architecture of Clariion and Navisphere

The architecture of EMC Clariion is based on the following components: Hardware Components 2 Storage Processors Software Components Disk Array Enclosure FLARE Code These components provide the storage-system performance and functionality for today's Small-to-Medium Business needs. The following sections provide a brief description for each component.

Storage (or Service) Processors / Storage Processor Enclosure

EMC provides connectivity between the customer environment and the Clariion through Storage Processors. There are two Storage Processors for each of the Clariion systems for Trespassing capability (Fail-over capability). Each storage processors have their own Memory for processing all input/output locally with trespassing capabilities. Each storage processor provide the following: Front-End connectivity (customer environment) using either Fiber Channel and/or iSCSI Back-End connectivity (storage) using Fiber Channel Loops. Both storage processors reside within a Storage Processor Enclosure, and each provide user interface and command line interface level console connection to provide customers ways to manage Disk provisioning through Navisphere (Clariion management software). An example report from Navisphere with the basic configuration of each Storage Processor is shown on the right.

Disk Array Enclosure

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

FLARE Code

FLARE (Fibre Logic Array Runtime Environment) is the proprietary code from EMC that controls each component in Clariion, much like Enginuity running throughout the high-end EMC Symmetrix family. FLARE code usually runs off the first five disks of the first Disk Array Enclosure, which is also supplied by the integrated Uninterrupted-Power-Supply (UPS). All write cache contents will be stored in an event of power failure for complete restoration upon power-on. An example of the Flare code running on a particular Clariion model is shown on the right.

Navisphere

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

SnapView

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

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

The following snapshot capabilities are available:

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

SnapView/Snap It provides the ability to provide a Point-In-Time view of the source volume using pointers with reserved volumes. Pointers will initially point to the original data on the source volume. Once new data is written to the source volume, the original data is copied to the reserved volume to preserve the Point-In-Time view. During the first SnapView session on a given source volume, a reserved volume is assigned to the source volume. If the SnapView session runs long enough that the reserved volume is filled, the next reserved volume will be assigned to the source volume.

Storage Systems Series Support

The Calypso software supports all CX series models. AX series are not supported.

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

AX Series

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

CX Series

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

CX3 Series

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

CX4 Series - Ultrafex

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

Integration Requirements for SnapProtect

Array and Solutions Enabler Software Licenses

The Calypso software requires enabling certain array components and licenses on the EMC Clariion storage system to achieve a successful integration with the software. Refer to the SnapProtect Backup - EMC Clariion documentation for more information.

Supported Applications and Operating Environments

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

Calypso Software

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

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

• CommServe, MediaAgent and File System installation
• Storage Device and Storage Policy Configuration

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

Basic File System Environments

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

• Windows/Unix File System iDataAgent
• MediaAgent
• VSS Software Provider (Windows Only)

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

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

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

Application Environments

Protecting application databases and log volumes through an Array snapshot provide fast access for recovery and many flexible options for backups. SnapProtect integrates application awareness together with the Array and Calypso to deliver all of the benefits of traditional streaming backups with all of the performance and proxy capabilities of a snapshot. This application awareness allows backups with appropriate log management operations based on the snapshot data. When implementing for Application Environments simply add the appropriate Application iDataAgent to the SnapProtect base configuration as follows on the Production Host: Windows/Unix File System iDataAgent MediaAgent VSS Software Provider (Windows Only) Application iDataAgent for selected Application (e.g., Exchange, SQL, Oracle) For a configuration where snapshots mount off the host to a Proxy server, implement the following agents on the Proxy. File System iDataAgent (Must be similar to Production Host Operating System) MediaAgent Application specific iDataAgent (Must be the same to Production Host) to enable Proxy. This is required for RMAN integrated backups. Application API (e.g., Exchange Management Pack, Oracle for RMAN integration) Refer to Getting Started - Setup Clients to select your application iDataAgent and perform the required deployment and configuration steps.

Virtual Environments

SnapProtect enables fast protection of large or volatile VMware environments without placing load on the production Virtualization Farm. SnapProtect technology integration with the Virtual Server Agent enables the Array to perform backups in minutes even with large numbers of virtual machines and sizable data stores. A dedicated ESX server for proxy data movement removes any utilization on the ESX farm providing file and folder recovery from the secondary tier of storage. To enable SnapProtect for the Virtual Environment install the following on the physical server(s) or virtual hot-add guest(s): Windows/Unix File System iDataAgent MediaAgent Virtual Server Agent (VSA) Refer to Getting Started - VMware for deployment and configuration steps.

SnapProtect Array Configuration Details with Clariion

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

Refer to the SnapProtect Backup - EMC Clariion documentation for array configuration steps.

The SnapProtect Process

The following sections describe the different SnapProtect operations.

SnapProtect Backup Operation

SnapProtect backups consist of the following operations:

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

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

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

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

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

Backup Copy Operation

During the Backup Copy operation:

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

Proxy Configuration

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

• File System iDataAgent (Must be similar to Production Host Operating System)
• MediaAgent
• Application specific binaries for proxy (e.g., Exchange Management Pack, Oracle for RMAN, etc)

Verify Configuration using SnapTest Tool

Security and Storage Policy Best Practices

Security Roles

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

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

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

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

Security Roles (for application Clients or Groups)	Backup	Application	Audit Team
Administrative Management
Agent Management
Agent Scheduling
Alert Management
Browse
Browse and In-Place Recover
Browse and Out of Place Recover
Compliance Search
Data Protection
Data Protection Management
End User Search
Job Management
Library Management
Library Administration
License Management
MediaAgent Management
Report Management
Storage Policy Management
User Management
VaultTracker Operations

Storage Policies

• increase the amount of tier 1 storage that is holding recovery points.
• cause the snapshots to fall short of fully meeting SLA requirements for the business.

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

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

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

• Primary snapshot copy – 2 days & 0 Cycles
• Primary backup copy – 28 days & 1 Cycle
• Offsite Disk/Tape copy – 60 days & 1 Cycle

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

Managing Snapshots

Managing Clariion SnapView Clone/Snap and Calypso Data Aging

SnapView Clone and Snap allow 1-to-Many relationships between the production volume and the clone volume (or reserved volume). When a SnapProtect job starts, each job consumes a volume residing on a particular RAID group for each production volume as shown in the table. Each job will behave differently during the cataloging phase as required by the Application iDataAgent during backup. Since each Clone and Snap contains a single job, the very first SnapProtect job against the production volume will always be a Full Synchronization, which requires the snapshots to be activated. Once the Clone has been attached with the production volume, the Clone target requires to be synchronized before it can be reused against the production volume. Depending on the maximum number of Clones/Snaps listed in the table – please check powerlink.emc.com for other systems. Data Aging must run against aged Clones/Snaps to free up resources to be reused for the next SnapProtect Job.

Back to Top