VNXe Series - Technical Doc

1© Copyright 2011 EMC Corporation. All rights reserved.

The VNXe SeriesTechnical Presentation

NameTitle

October 2011


• Architecture

• Hardware

• Operating Environment

• Storage Pools

• Data Services– Thin Provisioning– File-level

Deduplication & Compression

– Data Protection– Snapshots– Replication

Topics• Data Services

(continued)– Antivirus– File Level Retention– Backup

• Windows Integration & Support

• Management

• Support Ecosystem


A new way to

think about shared storag

e

Simple. Efficient. Affordable.

Configure inseconds

Get more capacity at

less cost

Rest easy, rock solid

Starting under $10K


Architecture & Hardware


VNXe's Purpose Designed Architecture

• Designed for IT generalist– Maximizing simplicity and easy

of use (no X-Blades, Control Stations etc.)

– Providing balanced performance, scalability and flexibility

iSCS

INFS CI

FS

Flexible Drive Options

Storage

Processor BStorage

Processor A

HighestCapacity (NL-SAS)

Performance

(SAS)

Integrated Unified Storage

Flare

Backend disksBackend disks

VNXe OE• File• Block• EMC Apps• Unisphere

VNXe OE• File• Block• EMC Apps• Unisphere

SP A SP B

SP A

… Multi-core Processors

Shared Memory Resources


VNXe Series HardwareSimple. Efficient. Affordable.

VNXe 3100 VNXe 3300Form factor (Minimum) 2U 3U

Storage Processors (SPs) 1 or 2 2

Total System memory 4 or 16 GB 24 GB

Maximum drives (Single or Dual SP)

48 or 96 120

Drive types 3.5” SAS, NL-SAS 3.5” SAS, NL-SAS, Flash

Protocols NFS , CIFS, iSCSI

Embedded I/O ports per SP 2 X 1 Gb Ethernet 4 X 1 Gb Ethernet

Configurable I/O slots per SP 1 1

I/O slot options available 4 x 1 Gb Ethernet 4 x 1 Gb Ethernet2 x 10 GB Ethernet

Backend Connectivity per SP 4 x 6Gb/s SAS 4 x 6Gb/s SAS


VNXe3100 2U Platform Overview

Storage Processor

Front View 12 x 3.5” Disks

Rear

Chassis• 2U DPE (Disk Processor

Enclosure)• 6Gb SAS-2 drive interface

– Max 12, 3.5” Drives per enclosure

• Dual Energy Star Gold Power Supplies– Power Consumption ~

330W• 1 or 2 SPs - CPU Module

Canisters• Battery-backed Write Cache

(BBWC) for single SP configurations

• Dimensions: 20in depth x 3.5in height x ~19in width

2 CPU Modules, each containing

• Intel, Dual Core Processor• 2, DDR3 1066MHz DIMM slots• Integrated, 3-cell Li-ion BBU• Solid State Disk (SSD), eFLASH

uSSD

I/O Technology per SP

• One Back End SAS-2 Port ( 6 Gb/s x4)

• Two Embedded GbE Host Ports

• One I/O Slot per CPU module– 4 x 1GbE

• GbE Management Port

• Serial Console and USB Port


Cost-effective Data Persistence• Single Storage Processor

Configuration– Low cost entry point in the VNXe

Series– Upgradeable to dual processor

configuration

• Cache Protection Module– Fits into second storage processor

slot

• Vault-to-Flash (VTF) technology – Runs off of low-power battery

technology – No need for standby power

supplies

• System recovery– Memory contents restored from

SSD– Buffer and cache pools/pages are

recreated at same physical addresses as initial boot

– System verifies restore operation and resumes I/O processing

VNXe3100 - Single SP Configuration

Cache Protection Module


VNXe3300 3U Platform Overview

Rear

Front View 15 x 3.5” Disks

Storage Processor

Chassis• 3U, DPE (Disk Processor

Enclosure)• 6Gb SAS-2 drive interface

– Max 15, 3.5” Drives per enclosure

• Holds 2 SP “Suitcases” with Integrated Cooling

• Dual Energy Star Gold Power Supplies– Power Consumption ~ 500W

with 15 drives• Battery Backup Module in Power

Supply • Dimensions: 24in depth x 5.25in

height x ~19in width • NEBS Level 3• DC Power option

2 CPU Modules, each containing

• Quad Core Processors• 3 DIMM Slots with 3 channels @

800MHz• PCI-E x4 CMI Path• Solid State Disk (for persistence)

I/O Technology per SP

• One Back End SAS-2 Port (6 Gb/s x4)

• Four Embedded GbE Host Ports

• One I/O Slot per CPU module – 4 x 1GbE,– 2 x 10GbE

• GbE Management Port• Serial Console and

USB Port


Flexible Storage Capacity• Disk Options, 3.5” Drives

– SAS Performance: 300GB, 600GB, 15K RPM

– Near line SAS Capacity: 1TB, 2TB, 7.2K RPM

– Flash (Tier 0): 100GB (VNXe3300 only)

• Scale– Up to 7 additional disk enclosures per

system– Max 120 drives in VNXe3300– Max 96 drives in VNXe3100– Mix drive types within an enclosure

• Optional “disk pack” offerings– SAS Performance pack: RAID 5 or

RAID 10– SAS Capacity pack: RAID 6– Flash pack: RAID 5

• Scale to 240 Terabytes with 2TB drive

Flexible Storage Options


Modular Design

• Modular system design– All major components are

customer replaceable units– Easy to identify and access

• Simple to service and upgrade– Clear visual repair instructions– Tool-less access to replaceable

components– “How-to” videos

• Minimal component sparing

• Efficient CRU replacement process


VNXe Interoperability and Standards• Host Operating Systems

– Microsoft Windows– Linux: SUSE, Red Hat,

AsiaNUX– UNIX: AIX, HP-UX, Solaris– VMWare– Hyper-V– Citrix XenServer

• Storage Applications– NDMP Backup Software– Anti-Virus Scanning

Software

• US Dept of Defense – Common Criteria– DISA STIG

• Telecom

• Telcordia NEBS Level 3


High Availability


Platform No single point of failure n + 1 power and battery backup Redundant, hot-pluggable components

Function RAID protection Active/Active controllers

Data cache mirroring between controllersBattery-backed cache for single SP

configurations Dynamic failover/failback Automatic management control failover Vault-to-Flash technology

Service Non-disruptive upgrades Hot-swap CRU and drive replacement Remote maintenance, call-home, automatic

diagnostics

High Availability


VNXe Vault to Flash – Cache Persistence CIFS Exchange

I/OVNXe

Platform Services

Block Services

File Services

ManagementServices

Network, I/O, Service Shims

SAS PCIeNIC

192.168.5.1\\cifs\myshare

192.168.5.2IQN:C0T0L0

Platform Services

Block Services

File Services

ManagementServices

SASNIC PCIe


Memory

Power DownRoutin

eCach

e

Memory

Power DownRoutin

eCach

e

Cache

Cache

Cache

Cache

1.

1. AC power is lost to arrayA battery holds up SP and SSD device

Transition to special power fail routine

3.

3. Power Down Code waits for dump completeDisables battery hold up

2.

2. Power Down Routine sheds unnecessary power draws

Checksums Contents of memory to dumpInitiates memory dump to SSD

Cache

Cache


VNXe – Deployed and Operating Normally CIFS Exchange

I/OVNXe

Platform Services

Block Services

File Services

ManagementServices


SAS PCIeNIC


192.168.5.2IQN:C0T0L0

Platform Services

Block Services

File Services

ManagementServices

SASNIC PCIe



VNXe HA Services Support – SP Failure CIFS Exchange

I/OVNXe

Block Services

ManagementServices


SAS PCIeNIC

File Services

Platform Services


192.168.5.2IQN:C0T0L0

192.168.5.2IQN:C0T0L0

Platform Services

Block Services

File Services

ManagementServices


SASNIC PCIe

File Services

3.

3. Health/Alert Business Logic detects status change

Indicates Alert to userEmail Alert to EMC Support & configured email

address

2.

2. HA Service starts new file serviceIP network failover is invoked

iSCSI LUN is exported

1.

1. Cluster Manager Detects problem with other node

Validates node failure Invokes HA failover service


VNXe HA Services Support – Service Failure CIFS Exchange

I/OVNXe

Block Services

ManagementServices


SAS PCIeNIC

Platform Services

Block Services

File Services

ManagementServices


SAS PCIeNIC

File Services

X Platform Services1.

1. Local Resource Manager Detects problemTries restarting services 3 times

Invokes HA failover service


192.168.5.2IQN:C0T0L0

2.

2. HA Service starts Management Service on other node

IP network failover is invokedManagement Services started on 2nd Storage

Processor

ManagementServices

Mgmt IP192.168.5.1

Mgmt IP192.168.5.1

3.


Indicates Alert to userEmail Alert indicates to Support and configured

emails


VNXe HA Networking Feature Support

FAILSAFE NETWORKING PLUS TRUNKING IMPLEMENTATION • FailSafe Networking (FSN)

• Network configuration beneficial against switch & cable failures

• End-to-end network availability

• Automatically configured between SPs

• VLAN, 802.1Q-VNXe in a VLAN-enabled network• Added security and Ease of management

LINK

Switch

Primary paths Standby paths

Network

SwitchSwitch

E-mailserver

Accountingdatabaseserver

Salesdatabaseserver

NetWarefileserver

UNIXfileserver

Accounting Sales Engineering

UNIX file server VLAN

NetWare file server VLAN

Sales database server VLAN

Accounting database server VLAN

E-mail server VLAN

VNXe Series

VNXe Series

• Link Aggregation• IEEE 802.3ad standard for port grouping; improves

availability

• One port fails, other ports take over

• Automatic configuration with statistical load balancing based on source and destination MAC addresses

• Does not increase single-client throughput, may increase throughput if there are multiple clients.


Storage Pools


VNXe Storage Pools

Stage 1

Stage 2

Disks


VNXe Storage Pools

Global Performance

Stage 1

Stage 2

Disks

RAID Groups


VNXe Storage Pools

Global Performance

Stage 1

Stage 2

Disks

RAID Groups

LU’s


VNXe Storage Pools

Global Performance

Stage 1

Stage 2

Disks

RAID Groups

LU’s

Disk Volumes


VNXe Storage Pools

Global Performance

Stage 1

Stage 2

Disks

RAID Groups

LU’s

Disk Volumes

Stripe Volume


Global Performance

Stage 1

Stage 2

VNXe Storage Pools

Disks

RAID Groups

LU’s

Disk Volumes

Stripe Volume

Pool Volume


Data Services


Disks

RAID Groups and Global Pools

Flare LUN’s

Disk Volumes

Stripe Volume

Pool Volume

10 GB

18.5 GB

Pool Volume

CIFS Shared Folder

Reserved storage (Size)

User provisions a Shared Folder…

Thick Provisioning – Shared Folders


2Xmore efficient

Twice the EfficiencyMore storage, better utilization, lower cost

File Deduplicatio

n and Compressio

n

Thin Provisioning

Traditional storage


Thin Provisioning


5 GB

18.5 GB

Pool Volume

CIFS Shared Folder

15 GB

Allocated (Initial Size)

Reserved storage (Maximum Size)

Disks

RAID Groups and Global Pools

Flare LU’s

Disk Volumes

Stripe Volume

Pool Volume

User provisions a Shared Folder…

Thin Provisioning – Shared Folders


VNXe THIN PROVISIONING

VNXe Thin Provisioning• Capacity oversubscription

– File systems– iSCSI LUNs– Logical size greater than physical

size

• Physical allocation in real time to logical size

• VNXe Virtual Provisioning safeguards

• Automatic File System Extension past logical size

• iSCSI Dynamic LUN Extension past logical size

Logical application and user view

Physical allocation

User B10 GB

User A10 GB

User C10 GB

4 GB

2 GB2 GB

Physical consumed storage


File-level deduplication


VNXe File-Level Deduplication and Compression Architecture

• Deduplication processes:

– Policy engine scans all production files looking for data that meets certain criteria:

• Last accessed/modified time, minimum/ maximum size, file extension, directory

– Or, files selected via API

– Candidates are compressed

– Duplicated files are removed by using SHA-1 or byte-by-byte data comparison

– Stubs point to files in the hidden deduplication store

• Deduplication is transparent to clients:– Process runs in the background

– Files pre- and post processing look the same

– Hidden deduplication store is a “working area” that is not visible

– Reads decompress data in memory, not on disk

– Writes are stored alongside deduplicated data

– Modifying one instance of a file has no impact on other deduplicated instances

VNXe FILE DEDUPLICATION

Deduplication-enabled file system

User visiblearea

Hidden deduplication store

File A

File B

File A

File A

File C

File B

Active file

File B

File C

File AStub A

Stub B

Stub C

Stub A

Stub CCompress anddeduplicate file

Stub B


User visible area Hidden reduced data store

VNXe FILE SYSTEM

VNXe File Deduplication and Compression: Data Modification

• File modification does not cause file to be reinflated:– Allows targeting large files (Terabytes

sized), and files that may show some level of activity while preserving user experience on access to these files

• Deduplicated files can be modified while still preserving commonality:– New data is stored alongside old

• File is either reinflated or reprocessed when new+old reaches logical file size:– Reinflated if selected for deduplication by

the internal policy engine– Reprocessed if selected for deduplication

via API

File Data File Data

New

Data


Data Protection


VNXe: Takes Care of the Complexities of Data Protection • Problem:

– Calculating the space required for data protection is complicated. It require formulas and an intimate understanding of underlying snapshot and replication technology.

• Typical Result: – Data Protection either gets slapped together in a “probably

should work” fashion, or a Professional Services engagement is required.

• VNXe eliminates complexity by: – Integrating best practices for provisioning data protection

reserve space– Easy to configure snapshot schedules and Application

Consistent Snapshots– Simplified replication configuration and management


• VNXe provisioning best practices also cover Data Protection storage

– Application specific best practices for data protection space. – Thin provisioning aware: Applications using thin provisioning will not require as much

data protection storage.– Auto-adjustment of Data Protection space as your production storage resource grows

Data Protection Storage Recommendations


Snapshots


• Shared Folder snapshots use Copy On first Write (COW)– Snapshot creation and deletion is very quick– The space required for snapshots continues to

grow as changes are made to the production volume

• iSCSI snapshots use Redirect on Write (ROW)– Snapshot creation is very quick– Perfect for your latency sensitive applications– Snapshots don’t grow once created

The differences between Shared Folder & iSCSI snapshots


Example: VNXe Shared Folder Snapshot

• Provides a read-only or read-write, point-in-time view of data– File system-level or iSCSI LUN view– Multiple snapshot versions – 96 r/o + 16 r/w– Typically has a 10% capacity overhead

• Primary applications include– Simple user initiated file un-deletes– Efficient logical backup and restore

• Copy on first write technology– Avoids fragmentation of primary FS– One side file data protection space for all file

system snaps

• Automatic extension of data protection space

• Online full file system instant restore from any snap

• Snaps can be deleted out of order

Production file system

SnapshotLogical point-in-time copy

PFS files at 4PMPFS files at 4PM

PFS files at 4PMPFS files at 4PM.ckpt_PFS_9AM.ckpt_PFS_12PM.ckpt_PFS_3PM


PFS_12PM

Single SavVol

PFS_3PM

PFS_9AM

PFS_12PM

PFS_3PM

PFS_9AM

Empty Space

SavVol extended

Restore PFS to 12:00 p.m.

snap

PFS_4PM

.ckpt_PFS_4PM


PFS files at 4PMPFS files at 4PM.ckpt_PFS_9AM.ckpt_PFS_12PM.ckpt_PFS_3PM




VNXe Family


Snapshots Consistency Options• Crash consistent snapshots– VNXe provides the ability to create manual and

scheduled crash consistent snapshots through Unisphere• Shared Folder:

Crash consistent snaps are acceptable• iSCSI:

Good for an emergency. Only applicable to applications with a single virtual disk


Snapshots and Application Consistency• iSCSI Application consistent snapshots

– Using 3rd party backup applications• Leverages the VSS framework for Microsoft Applications to create

“Hardware Snapshots” for the application

– Preferred Solution: Using the Application Protection Suite• Application protection Suite includes Replication Manager (RM)

software• An RM agent runs on the host, which guarantees the applications

using the storage are quiesced prior to creating snapshots• Leverages the VSS framework for Microsoft Applications• For applications with multiple virtual disks, Application Sets

ensure consistency across all the storage resources• Exchange will automatically undergo snapshot consistency

checks following the creation of the snapshot


• Snapshots– Shared Folder: User initiated recovery using

hidden .ckpt directory or Microsoft “Previous Versions” interface

– iSCSI: Snapshot promotion and revert performed using either Unisphere or RM

Microsoft Previous Versions tab

Data Recovery options


Replication


VNXe Replication

•Replication can be*:–VNXe to VNXe–VNXe to VNX–VNXe to Celerra (DART 6.0+)–Celerra (DART 6,0+) to VNXe–VNXe to VNXe fan-out & fan-in ratio 5 to 1

•Same technology for file & block

Productionsite

Disaster recovery

remote site

WAN

Snaps

FS/LUNVDM

Snaps

FS/LUNVDM

Network Network

* See the “EMC Simple Support Matrix” (ESSM) for the VNXe Series, url: Simple Support Matrix EMC VNXe Series for any prerequisites and requirements.

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Interoperability_Matrix/300-012-439.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tTZWFyY2hSZXN1bHRzRXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwNWQwNjc1LGRhdGFTb3VyY2U9RENUTV9lbl9VU18w

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Interoperability_Matrix/300-012-439.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tTZWFyY2hSZXN1bHRzRXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwNWQwNjc1LGRhdGFTb3VyY2U9RENUTV9lbl9VU18w


Replication Frequency • Shared Folder replication driven from Unisphere

– Manual synchronization– Automatic synchronization based on RPO (Recovery

Point Objective)

• iSCSI replication using RM– Schedule-driven synchronization frequency– Application consistency is guaranteed


Anti-Virus


Virus-checking request

�

VNXe Anti-Virus Support

• Shared bank of virus-checking servers

• Can deploy multiple vendors’ engines concurrently

• Virus-checking server only reads part of files

• File access is blocked until it is checked– Scan after update– Scan on first read–Automatic access-time update

• Notification on Virus Detect

• Anti-Virus Sizing Tool

• Runs over VNX Event Enabler

Virus-checkingserver

User

Write/close or first read after new virus-definition file

Œ

Virus-checking signatures

VNXe Family


File Level Retention


VNXe File Level Retention – Enterprise (FLR-E)

• Enables adherence to good business practices • Provides for retention periods per file• Retention is managed on a per-file

basis


File Level Retention Workflow

• Not-locked files– Traditional non-FLR files

• Locked files (WORM)– Retention periods are set on a per-file

basis– Retention period is set to “infinite” if

left unspecified – Cannot be deleted, renamed, or

modified– Retention periods can be extended

• Append files– Protected files to which content can

be added but not modified or deleted

• Expired files– Files can be deleted after retention

time expires

FILE LEVEL RETENTION WORKFLOW

Non-File Level Retention-enabled filesSet retention periods—enable File Level Retention and commit to “WORM” stateRetention period extendedRetention period expiresLocked or expired empty filesFile deleted

1

2

3

4

5

6

Not-lockedLocked(WORM)

1 2Expired

3

Append

2

4

6

3

5


File Level Retention Capabilities Tamper-proof clock:

Software clock maintained per FLR file system Maintains an additional clock that is separate from

the system clock– Changes in the system clock time cannot be used to fool the

file into “expiration”

Used for all File Level Retention time comparisons File Level Retention clock cannot be modified or

reset

Activity logging: Log is maintained in the File Level Retention logs

subdirectory Information for each event:

– Time of event (system time)– File with which the event is associated– Action (create, append-only file, etc.)– Operation being performed– The user ID of who performed or attempted the action


Backup


• NDMP (Network Data Management Protocol) Heterogeneous 3-Way configuration support

• Extensive NDMP qualification performed. Supported Backup Software Vendors include:• EMC NetWorker• EMC Networker FastStart• CommVault Simpana• Symantec Backup Exec• Symantec NetBackup

VNXe Supports Traditional Backup Software

Tape Library

Backup Server

Backup

Restore

Control &

Data Path

VNXe


VNXe Supports EMC Data Domain

Deduplication storage systems

• Scalable Systems• Reduce storage by an average of 10-30x

and protect up to 28.5 PB of logical capacity in a single system

• High-speed deduplication• Complete backups faster - Throughput of

up to 26.3 TB per hour• Network efficient replication

• Send only deduplicated and compressed data across the network, requires a fraction of the bandwidth, time, and cost compared to traditional replication methods

• Easy Integration• Qualified with all leading enterprise

backup and archiving applications—integrates easily into existing storage infrastructures


VNXe Supports EMC Avamar

Deduplication backup software and system

• Faster backup over existing LAN/WAN• Data deduplication significantly reduces

backup windows and network traffic by only storing unique changes, while always maintaining daily full backups for immediate single-step restore

• Enterprise-wide backup and recovery for both physical and virtual environments• Optimized for VMware, NAS, Remote Office

and Desktop/Laptop• Flexible deployment

• Avamar Data Store scales to 124 TB of deduplicated capacity, and integrates with Data Domain systems for further scalability of high change rate workloads

• High reliability• Patented RAIN technology to provide

uninterrupted data accessibility


Windows Integration & Support


VNXe Windows Integration• Quotas (groups and user) – Yes, supported through AD only

• GPO’s – Defined & Parsed by AD

• Home directories – Yes

• Windows 2008 AD support – Yes

• DFS support :

• Supports root DFS in standalone mode only

• Can be supported as a leaf node

• Does not support DFS-R

• Support ACLs at the share, level directory and the file – Yes via AD


Windows Group Policy

Group Policy Object

User and Computers

Domain

Windows Domain Controller

Windows Support Enhancements

• Windows Group Policy• GPOs are defined and

parsed by Active Directory

• VNXe supports GPOs through Active Directory


Operating System Refresh

Windows Support Enhancements

• Windows 2008 R2 Server• Based on the new “Windows 7”

kernel• VNXe to support all Windows 2008

R2 server flavors and platforms• Windows 2008 R2 hosts can

connect to the VNXe over CIFS SMB2, CIFS SMB1, iSCSI

• VNXe CIFS servers can be part of a Windows 2008 R2 based domain

• Listing in Microsoft Windows Server catalog


Management


Challenge• Graphical, task-oriented model– Approachable, intuitive design– “Web-familiar” look & feel

• Simplifies management for the storage novice– No storage background required– Immediate productivity

• Users can easily:– Create storage for an application– Monitor and manage that application’s

storage– Customize the interface according to

personal preferences or local language requirements

– Identify and resolve hardware failures– Perform software upgrades from interface

Click icon to add pictureDesigned for IT

Generalist

Focus on applications

storage – Built-in Best

Practices

Online Support Ecosystem

Introducing VNXe’s Unisphere


Application-Enabled Management• Managing storage is

always in the context of the application• Capacity usage• Storage provisioning

• Integrated application best practices • Automate and simplify

storage provisioning• No guesswork

• Best-practice wizards for key applications


Enables VMware storage to be fully managed from VNXe

Simplified Virtualization Integration• Best Practice Provisioning

Wizard for Hyper-V• Automates storage

provisioning & data protection

• Allows users to monitor Hyper-V storage on VNXe

• API integration with vCenter• Discovers existing

datastores and VMs hosted on VNXe to streamline provisioning tasks

• Allows the VNXe admin to allocate additional storage to datastores directly

• Automatically creates and configures the datastore on ESX after provisioning


EMC VSI for VMware vSphere

NFS data store management for the VMware Administrator

Unified Storage Management

Increase storage efficiency while maintaining operational integrity

Celerra

• Storage Admin & VMware Admin share same visibility into storage resources

• VNX Plug-in allows VMware admin to Provision VNXe storage• Create VMFS Datastores

(iSCSI)• Create NFS Datastores • Enables Thin Provisioning


Instant ExpertiseBest-practice wizards configure storage with just a few clicks

Share WizardSetup NFS and CIFS shares in minutes

Volume WizardSetup iSCSI volumes in minutes

Hyper-V WizardSetup 1TB Hyper-V

datastore in 10 minutes

E-Mail WizardSetup hundreds of Exchange mailboxes in fewer than 10 clicks

VMware WizardSetup 1TB VMware

datastore in 10 minutes


Built-In Best Practices Examples

• Exchange• Calculating the number and size of Exchange storage

groups• Selecting correct storage pool and RAID set for

customer• Calculating the amount of storage for snapshots

• VMware• Automatically updating VMware when storage changes

take place• Thin provisioning enabled by default for NFS

datastores• Default snapshot schedule for data protection


The VNXe Support Ecosystem


• Failed component easily identified

• Alert Notification with access to remedial help

• Direct access to EMC support options

• Order replacement part from Unisphere

Simplified Troubleshooting


VNXe Health/Alert – Drive FailureCIFS Exchange

I/OVNXe

Platform Services

Block Services

File Services

ManagementServices


SAS PCIeNIC

Platform Services

Block Services

File Services

ManagementServices


SAS PCIeNIC

X


192.168.5.2IQN:C0T0L0

1.

1. Disk driver detects failed or removed deviceReconstructs data for pending I/O

Marks device as removed from system

2.


Indicates Alert to userEmail Alert to EMC Support & configured email

address


The VNXe On-line Support Experience

• Key Benefits• Direct access to product

community• Just a click away…

• Self-help resources:• Whitepapers, FAQs, online

training, how-to videos• Knowledgebase search

• EMC-assisted support resources:• Live chat• Assisted parts replacement• My support page

• EMC-assisted support resources:• Live chat• Assisted parts replacement• My support page


How-To-Videos (Replace Parts)


Software Downloads


Verify Software Entitlements


Update Software


Support Forums


Check on your Support Contract with EMC?


A Place You Can Always Go


A new way to

think about shared storag

e

Simple. Efficient. Affordable.

Configure inseconds

Get more capacity at

less cost

Rest easy, rock solid

Starting under $10K


THANK YOU

Documents

VNXe Series - Technical Doc