Unity Fundamentals SRG

Welcome to Unity Fundamentals.
Copyright 2016 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes
the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION

MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license. The trademarks, logos, and service marks (collectively
"Trademarks") appearing in this publication are the property of EMC Corporation and other
parties. Nothing contained in this publication should be construed as granting any license or
right to use any Trademark without the prior written permission of the party that owns the
Trademark.
EMC, EMC AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync

ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated
Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Bus-Tech, Captiva, Catalog
Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC
CertTracker. CIO Connect, ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak,
CloudArray, Codebook Correlation Technology, Common Information Model, Compuset,
Compute Anywhere, Configuration Intelligence, Configuresoft, Connectrix, Constellation
Computing, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection
Suite. Data Protection Advisor, DBClassify, DD Boost, Dantz, DatabaseXtender, Data
Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document
Sciences, Documentum, DR Anywhere, ECS, elnput, E-Lab, Elastic Cloud Storage,
Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 1

EmailXaminer, EmailXtender , EMC Centera, EMC ControlCenter, EMC LifeLine,
EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass,
FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization,
Greenplum, HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover,
Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS,Kazeon, EMC
LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max
Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band
Deduplication,Navisphere, Netstorage, NetWorker, nLayers, EMC OnCourse,
OnAlert, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap,
ProSphere, ProtectEverywhere, ProtectPoint, EMC Proven, EMC Proven
Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare,
RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor,
SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure,
SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope,
SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix
VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere,
Universal Data Consistency, Vblock, Velocity, Viewlets, ViPR, Virtual Matrix,
Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything,
Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX,
VSAM-Assist, VSAM I/O PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression,
xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-
Friction Enterprise Storage.
Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals #

This course covers the EMC Unity platform. It includes the EMC Unity models, architecture,
features, functions, capabilities, and management. The peripheral products associated with
Unity are introduced.

This module focuses on the Unity product benefits and use cases.

The Unity platform is a unified Block and File offering in a single product that can be
managed with one easy to use GUI. Unity is a storage product designed for a mid-range
environment that includes small to mid-range customers. The Unity storage platforms
support the NAS protocols (SMB/CIFS for Windows and NFS for UNIX/Linux), as well as
native block protocols (iSCSI and Fibre Channel).
Unity is optimized for core IT applications. These include transactional workloads such as
Oracle, SAP, SQL, Exchange or SharePoint, server virtualization and end user computing
such as VDI, and all other applications that need traditional file, block or unified storage. All
models are available as an AF, All Flash option.
Unity is also a good fit for partner lead configurations optimized for virtual applications with
VMware and Hyper-V integration. The Unity platform with multi-core optimized architecture
unleashes the power of Flash, taking full advantage of the latest Intel multi -core
technology.
Copyright 2016 EMC Corporation. All rights reserved. Course Name 4

As mentioned on the previous slide, Unity is available in all models in an All Flash version.
The bezel has a slightly different appearance to help identify the optimal performance all
flash models.

To fill the gap in our portfolio, EMC has introduced the Unity platform of storage products.
Unity comes with Enterprise capabilities including; Unified storage for Block and File,
vVOLS, it is VM-Aware, supports a REST API and SMI-S, as well as Openstack.
Management with Cloud-Like simplicity through a responsive HTML5 GUI, interfaces with
the Proactive Assist service and provides Cloud-Based analytics. Unity provides the best
dollar per Gigabyte storage cost, highest density of storage, FLASH disk technology, and
disk tiering.
Unity will meet all of the top new customer demands, including ease of Service and
Support, low Total Cost of Ownership, it is easy to configure and implement, it has top
notch features and it is easy to manage.

Unity models directly integrate with the current VNX portfolio of products. Starting with
UnityVSA models up to the Unity 600 will replace the current VNXe1600 up through and
including the VNX5800. VNX7600 and VNX8000 will continue to be the top tier of the
Unity/VNX family of products.
Copyright 2016 EMC Corporation. All rights reserved. 7

The pressure in Exchange environments to eliminate backup windows and reduce recovery
times is stronger than ever before. With dynamic, policy-based protection management,
these dynamic environments can easily handle the demanding recovery objectives using
EMC Unity advanced technologies such as snapshots and continuous protection technology.
It also helps efficiently use storage resources and optimize protection for Microsoft
Exchange. The Unity storage array performance is optimal under heavy Exchange
workload.
Traditionally, the best practices for optimizing storage performance involved manual,
resource intensive processes. Unity allows SQL administrators to leverage an easy-to-use
and potentially hands-off mechanism for optimizing the performance of the most
demanding applications. Automating the movement of data between storage tiers saves
both time and resources. Unity eliminates the need to spend hours manually monitoring
and analyzing data to determine a storage strategy, then maintaining, relocating and
migrating LUNs (Unity logical volumes) to the appropriate storage tiers.

Online Transaction Processing (OLTP) database applications tend to be mission-critical and
usually have stringent I/O latency requirements. Traditionally, these OLTP databases are
deployed on a huge number of rotating Fibre Channel (FC) spindles to meet the low I/O
latency requirement. Consequently, the effective capacity utilization of these spindles is
very low. Unity reduces the need to buy more drives to keep up with database growth.
Also, Unity automatically and non-disruptively migrates hot and cold data between the
available storage tiers, thereby improving the effective storage utilization.
The common business requirement in SAP environments is reducing TCO while improving
performance and service level delivery. Frequently, responsiveness to sensitive SAP
applications has deteriorated over time due to increased data volumes, unbalanced data
stores, and changing business requirements. By using Unity with block data, SAP
deployments can gain a significant performance boost without the need to redesign the
applications, adjust the data layouts, or reload significant amounts of data. With
automated sub-LUN level tiering and extended cache, Administrators can properly balance
data distribution across the tiers that allow capacity and performance optimization.

The Unity platform is optimized for virtualization, and thus supports all leading Hypervisors,
simplifying desktop creation and storage configuration. Unity leverages advanced
technologies to optimize performance for the virtual desktop environment, helping support
service level agreements.
Virtualization management integration allows the VMware administrator or the Microsoft

Hyper-V administrator to extend their familiar management console for Unity related
activities.
VMware vStorage APIs for Array Integration (VAAI) for both SAN and NAS connections,
allows Unity to be fully optimized for virtualized environments. EMC Virtual Storage
Integrator (VSI) is targeted towards the VMware administrator. VSI supports Unity
provisioning within vCenter, full visibility to physical storage, and increases management
efficiency.
In the Microsoft Server 2012 and Hyper-V3.0 space, the Array Offloaded Data Transfer
(ODX) allows Unity to be fully optimized for Windows virtual environments. This technology
offloads storage-related functions from the server to the storage system.
EMC Storage Integrator (ESI) for Windows provides the ability to provision block and file
storage for Microsoft Windows or Microsoft SharePoint sites.

This module focuses on the Unity models, terminology, components, and configurations.

All Unity Disk Processor Enclosures (DPEs) are a 2U form factor. Each has two Storage
Processor suitcases, each with a single multi-core processor with six to twelve cores.
Memory per Storage Processor (SP) ranges from 24GB to 128GB. Drive count maximums
range from 150 disk drives to 500 disk drives, providing array capacities ranging from
900TB to 3000TB. All Disk Processor Enclosures support two additional I/O Modules. The
Operating Environment (OE) is SUSE Linux SLES12 based.
All Flash models Maximum capacity will vary from this chart.

Above are the maximum configurable capacities for the Unity product models.

The Unity DPE is available in both a 12-disk and a 25-disk configuration. Standard power &
enclosure fault LEDs are located on the front of the DPE.

The Unity DPE supports 12 Gb/s transfer speeds for both 12- and 25-disk configurations.
The Unity DPE can be expanded by connecting the built in 12 Gb/s SAS ports (2 ports) to
a 15- or 25-disk Unity DAE.
Older VNX DAE and disk versions operating at 6Gb/s are not supported in Unity.

The Storage Processors are the core of the Unity platform. They deliver the Block and File
components and services, as well as managing multicore optimization. The two Storage
Processors, SPA and SPB, provide Block and File data access via I/O module technology that
supports Fibre Channel and iSCSI protocols, providing access for all external hosts and
multi-protocol support for NFS and SMB.
The Unity Storage Processors operate in Asymmetric Active/Active mode, in that both
controllers are active/on-line and receiving host I/O simultaneously for the back-end
storage.
The large orange knob is part of a torque limiting system for engaging and dis-engaging the
Storage Processor from the DPE chassis. Note the multiple back-plane contact points and
the actual engagement screw for the SP to chassis fitment.

Unity supports file services through the use of NAS servers. The Control Station and Data
Mover hardware are no longer needed to support file services. NAS servers used to access
file systems must be configured before creating file systems. NAS servers are used for NAS
protocols only; iSCSI block storage is provided natively and not through a NAS server.
The NAS server root file system and configuration data requires a storage pool and an
owning Storage Processor. Each NAS server is a separate file server and allows for IP
Multitenancy.
Users on one NAS server cannot access data on another NAS server. Each NAS server has
a separate configuration with independent network interfaces, sharing protocols, directory
services, NDMP backup and Security.

In addition to converting AC line voltage to usable DC voltage, the DPE power supplies
provide information necessary for Unisphere to monitor and display the ambient
temperature and power consumption of the individual power supplies. The power supplies
are Customer Replaceable Units (CRUs). Each power supply includes two power LEDs and a
status LED.
DC power supplies are available for Unity models. DC power supplies allow these models to
be installed in network telecommunication facilities or central offices, and makes these
models NEBS (Network Equipment Building System) compliant.

There are two styles of DAEs available for Unity expansion, the 15 drive, 3U enclosure using
a 3.5 inch disk form factor, and the 25 drive 2U enclosure using a 2.5 inch form factor disk.
Standard power & enclosure fault LEDs are located on the front of the DAEs.

Be careful cabling the DAEs to the DPE (LCC connectors are on opposite sides of the Rack);
SP-A connectors are located on the left side, SP-B connectors are located on the right side.
12Gb cables/connectors are not keyed uniquely for Primary vs Expansion ports and will
work in either port. The recommendation for back-end cabling is to use the 0 labeled Port
for the Primary, and the 1 labeled Port for Expansion.
The following slide shows all currently available disk drives and their capacities.

Disk drives supported for the Unity DPEs and DAEs include SAS Flash-2, SAS Flash-3, and
rotating disk at 15,000 rpm, 10,000 rpm, and 7,200 rpm. All drives leverage 12Gb/s SAS
back-end connections. 6Gb/s drives are not supported in Unity arrays. The Unity Drive
Matrix displayed gives available capacities for each class of disk drive.
SAS and NL-SAS drives will use the new 4K block size. This is due to an industry trend
towards larger sector sizes for drives. The use of 4K block sizes better aligns with typical
I/O patterns and can lead to greater efficiency. SSDs will continue to use the 520 block
size in order to remain optimized within the OE software.
Please note, the first release of Unity code will support all flash models. The OE will reject
any HDD that might be installed into a Unity All Flash (AF) model. The forthcoming Unity
SP1 release will block any HDD from being installed in an AF configuration. The default
RAID configuration for the Flash tier in an AF or Hybrid Flash (HF) is RAID5 (4+1) but other
RAID types are supported.

To increase capacity and efficiency, drive vendors are moving to larger physical block sizes
of 4K. Unity will ship with 4K spindle drives only, both in system and user slots. As part of
larger sector size implementations, drive vendors must provide spliced write protection to
prevent losing or corrupting data within a 4K sector that is not being updated during a write
at the time of a power loss. Note that SSD drives will continue to present a 520 byte block
size.
The logical block size used and observed by multi-core control software will remain 520
bytes per block with 512 bytes of user data followed by 8 bytes of metadata. The major
change required is to align all RAID write requests to a multiple of 8 logical blocks when
writing to a 4K drive. All disk operations will be done on a 4K boundary. The 4K sectors are
4160 bytes in length.
For parity RAID types, there are two write request types: partial and full stripe. Full stripe
writes are aligned to the 4K block size so no changes are required to support 4K drives.
Partial stripe writes already perform a pre-read for each affected position. The only change
required when the drive is 4K is to align the pre-read, merge the new data and then write.
For non-parity RAID types an additional pre-read will be required for a 4K RAID group
where the write request is unaligned or small.

The 1Gb Base-T front-end I/O module allows iSCSI block connectivity and NAS file connections to be
configured at the same time. Each port can operate at speeds up to 1 Gb/sec. The controller chip is a
Broadcom BCM5719 device. Each of the four ports uses an RJ45 copper Ethernet plug.
The 10GbE 4-port optical I/O module operates only at 10 Gb/s speeds. It allows block (iSCSI) and file
connections at the same time and can use SFP and Twin-Ax(active) cables. The Emulex Skyhawk
(XE104) device is the controller for this I/O module.
The 10GbE Base v2 front-end I/O module provides iSCSI block connectivity and NAS file connections
to be configured at the same time. Each port can operate at speeds up to 10 Gb/sec. The controller
chip is a Broadcom BCM57840S device. Each of the four ports uses an RJ45 copper Ethernet plug.
The 16Gb FC I/O module will be used to serve FC block protocol in a direct connect configuration or
via a switch. The quad port QX I/O modules will be offered as an array option in pairs (one for each
SP) and has a different connector (X-connector) from the 16Gb FC I/O module that ships on VNX2.
They are not interchangeable. Each of the 4 ports uses an optical 16Gb capable SFP+ and are hot
swappable. Supported SFPs include EMC PN# 019-078-042 2/4/8 Gbps (Note: 2Gbps is not
supported by the ASIC), and EMC PN# 019-078-045 4/8/16 Gbps.
The 12Gb/s SAS BE I/O module is a Quad Port, 4-lane interface per port module designed to
accommodate DAE expansion. This I/O module uses a PMC Sierra PM8073 SPCve 16x12G SAS
Controller. Common Characteristics include a per port LED indicator to signal an active link, an eight-
lane PCI Express Gen 3.0 interface, quad x4 lane mini-SAS HD (High Density) connector and
encryption that is FIPS 140 certifiable and is fully compliant to SAS 3.0 standards. The 12Gb SAS I/O
module is only available on Unity 500 and 600 models for DAE expansion.
The 10GbE Optical front-end I/O module has two ports and can be configured for fiber optic or Twin-
Ax iSCSI cables. This I/O module has a full iSCSI offload engine, supports VLAN tagging, and
supports 32 virtual ports per physical port. Each port can operate at 10Gbps. All Host Operating
Systems supported by EMC 10GbE iSCSI array connections are supported. Removing a powered on
I/O Module will cause the SP to immediately reboot. Alerts will inform the customer of the missing
module. The interface to the Storage Processor is via a PCIe Gen3 x4 interface. A Qlogic Hilda 8324
ASIC provides controller functions.

This table shows the currently available I/O module options. Unity uses I/O modules in
various combinations for front-end and back-end connectivity. Each I/O module is protocol
independent and hot swappable. Options for block I/O include Fibre Channel and iSCSI.
Options for file I/O include 1 Gb/s and 10 Gb/s Ethernet with either copper or optical
connections.
At GA, only new I/O module installations are supported. You cannot upgrade existing I/O
modules installed in Unity systems. I/O modules for the Unity platforms use SLIC 2.0
connectors. Older VNX I/O modules are not compatible with Unity systems.

This module focuses on the Unity architecture, software bundles, licensing, features and
capabilities. It explains high availability, storage efficiency, local protection, performance,
and replication.
Also covered in this module are common features with VNX2, new features unique to Unity,
and features from VNX2 that are no longer available in Unity.

The Unity architecture is designed to deliver a true unified native block and file solution with
dedicated components that are optimized for the specific use cases. Unity leverages the
hardware and core technologies across both the block and file implementations providing
optimal use of all available resources.
Access to Block Storage is provided by containers on both Storage Processors to hosts

connected via FC or iSCSI IO modules. A common software structure provides access to
the Virtual Storage Pool and configured LUN resources.
Access to Network Attached Storage (NAS) is also provided by containers on both Storage
Processors to Unix or Windows based clients and virtualized server environments via
Ethernet IO modules. Again, a common software structure provides internal access to the
File Systems stored in the Unity Virtual Storage Pool.
This architecture is a significant departure from the previous generation of VNX products.
Similar unified storage functionality is provided at the host and network interface, while
much greater utilization of resources and higher performance capabilities are provided to
the customer.

Storage is provisioned from pools. A pool is a collection of disks that are dedicated to
create LUNs. A pool is somewhat similar to a RAID group. However, a pool can contain a
few disks or hundreds of disks, whereas a RAID Group is limited to 16 disks. Pools can be
heterogeneous (made up of more than one type of drive) or homogeneous (composed by
only one type of drive).
Homogeneous pools are recommended for applications with limited skew, such that their
access profiles can be very random across a large address range. Multiple LUNs with similar
profiles can share the same pool resources. These LUNs provide more predictable
performance based on the disk type employed. In a homogeneous pool, only one disk type
(flash, SAS, or NL-SAS) is selected during pool creation.
Heterogeneous pools consist of multiple disk types. The system supports flash, SAS, and
NL-SAS disks in the same pool. There can be a maximum of three disk types in a
heterogeneous pool. Data in a particular LUN can reside on some or all of the different disk
types. FAST VP is able to relocate slices across different disk types in a heterogeneous pool
to ensure the hottest data resides on the highest performance drives.

This table lists the maximum capacities for pool related resources.

Here is a comparison of the features and functionality of VNX2 and the Unity product.
There are some deprecations, such as Classic LUNs, and several enhancements that will be
discussed throughout this training.

UFS64 is a 64-bit file system architecture being introduced in Unity and has a 64TB
maximum file system size. All NAS servers and file systems in Unity will use only UFS64.
There is no ability to create a UFS32 file system in Unity. UFS64 exhibits greater
scalability, availability, space efficiency, and is compatible with all array data services.
UFS64 supports various NAS protocols such as SMB (including SMB 3.02), NFS v3 & v4,
FTP/SFTP, and multiprotocol access to the same file systems.
Better performance is also provided through faster fail overs, file shrink and expand, space
efficient snapshots and simpler quotas.

This table shows a comparison of the attributes of the old UFS32 and the enhancements the
UFS64 filesystem provides as used in all models of Unity.

Above are the published maximum limits for Unity filesystems.

Unity Software is made up of the Unity Starter Software Package and the Unity Essentials
Software Package.
The Unity Starter Software Package provides management software including Unisphere
Element Manager; Unisphere Central, a consolidated dashboard and alerting software; thin
provisioning; Proactive Assist to configure remote support, online chat and open a service
request; Quality of Service for block storage; and EMC Storage Analytics Adapter for
VMware vRealize. Unified protocols included with Unity Starter Software include file, block
and VVols. Local data protection for Unity Starter Software is provided by local point-in-
time copies, anti-virus software, and optional controller-based encryption.
Unity Essentials Software Package includes all of the features of Unity Starter Software and
adds to it Remote data protection with Native Asynchronous Block and File Replication,
Native Synchronous Block Replication, RecoverPoint Basic, and RecoverPoint for VMs.
Performance Optimization is provided by FAST Cache, and FAST VP.
Supported interface protocols for all Unity models include NFSv3, NFSv4, and NFSv4.1;
CIFS (SMB 1), SMB 2 and SMB 3; FTP and SFTP; and FC and iSCSI.
Optional software includes RecoverPoint Advanced, PowerPath Multipathing, PowerPath

Migration Enabler, VPLEX and the Data Protection Suite of Backup, Archive and
Collaboration Software.

Unity availability and redundancy features include dual Storage Processors (SPs) with
mirrored write cache. Each Storage Processor contains both primary cached data for its
LUNs and a secondary copy of the cache for its peer Storage Processor.
Available RAID protection levels include 1/0, 5, and 6 and can co-exist in the same array
simultaneously to match different protection requirements.
Each disk drive has two data ports. This gives two separate paths to each drive, one from
each Storage Processor. If an SP fails, or any component of the path fails, the drive can
still be accessed by the other SP.
Proactive hot sparing enhances system robustness and delivers maximum reliability and
availability.
Redundant power supplies, one for each Storage Processor, are included. In the event of a
failure, one power supply can power the entire Disk Processor Enclosure.
Each SP also has a Battery backup to allow for an orderly shutdown and cache de-staging to
the Vault SSD. In the event of a power failure, the Vault SSD provides the de-stage area
for data in write cache that is not yet committed to the disk.

FAST Cache Flash Drives are configured in RAID 1 pairs using SAS Flash Drives and are
labeled as SAS Flash 2. SAS Flash-2 drives are designed for an activity of 10 writes per
day (WPD). Dynamic Over-Provisioning is utilized to increase the useful lifetime of the
drives.
When Unity models are offered in an All Flash configuration, the Fast Cache and FAST VP
features are not available.

Flash drive over-provisioning is the difference between the physical capacity of the flash
drive and the logical capacity as seen by the user. The additional space is used for garbage
collection, wear leveling, and bad block remapping. Increasing the amount of over-
provisioning decreases write amplification and therefore increases endurance of the flash
drive.
FAST Cache monitors the wear on flash disks and dynamically removes capacity (pages) via
an unmap command. This increases the amount of over-provisioning within the flash disks.
FAST Cache updates wear information every 7 days, and adjusts the amount of over-
provisioning in flash disks to attempt to maintain a minimum of 5 years lifetime of flash
disks. Based on the latest wear information, the weekly wear information report can
increase or decrease the amount of over-provisioning in the flash drive.

Unity FAST Cache supports online expansion. Each RAID 1 pair is considered a FAST Cache
object. Flash drives are added in pairs (RAID 1 Mirroring) up to the system maximum
capacity. Currently, only expansion with the same drive type and size is supported. Upon
completion of the reconfiguration, the new space is available for use by FAST Cache.

Unity FAST Cache also supports online Shrink. Each RAID-1 pair is considered a FAST Cache
object and the Unity OE will allow the removal of all but one RAID-1 pair. The Shrink
process is lengthy and requires flushing all dirty data from each set being removed to back-
end disk. Data will need to re-promote to be serviced from FAST Cache.

Unified snapshots provide point-in-time copies of data by using redirect-on-write
technology. This avoids the copying of data when source data is modified. In this example,
the Source LUN points to data A, B, C, and D. Then a snapshot is taken and it also points
to data A, B, C, and D. If the user modifies data D on the Source LUN, this new data is
simply written to a new location and the LUNs mapping is updated to point at the new
data. Similarly, if data A on the Snapshot is modified, the new data is simply written to a
new location and the snapshots mapping is updated to point at the new data.
Attach block snapshots to a mount host to make them read/write accessible to the mount
host. Mount file snapshots to provide access to network clients and utilize the Previous
Versions of file snapshots for restoring operations. Hierarchical snapshots, snap of a
snap, are also supported for multiple uses of the same point in time copy of data.

Unified Snapshots provide point-in-time copies of data. Snapshots are provided for both
block and file resources. With Unified Snapshots, the storage required for your snapshot
data comes out of the same storage pool as your source LUN data so there is no separate
management of Reserved LUNs. Unified Snapshots are also the foundation for native
asynchronous replication in Unity.
Auto-delete and expiration can be configured so that snapshots are automatically deleted at
a specified time or based on user defined storage consumption thresholds.
Consistency Groups can group a set of LUNs together and manage that group as a single
entity using a unique name. This insures correct write order among the Consistency Group
devices. There is support for 256 snapshots per LUN and filesystem.

Here are the limits as defined for unified Snapshots.

Remote Replication is one method that enables data centers to avoid disruptions in
operations. In a disaster recovery scenario, if the source site becomes unavailable, the
replicated data will still be available for access from the remote site. Remote Replication
uses a Recovery Point Objective (RPO) which is an amount of data, measured in units of
time to perform automatic data synchronization between the source and remote systems.
The RPO for asynchronous replication is configurable. The RPO for synchronous replication
is set to zero. The RPO value represents the acceptable amount of data that may be lost in
a disaster situation. The remote data will be consistent to the configured RPO value.
Remote Replication is also beneficial for keeping data available during planned downtime
scenarios. If a production site has to be brought down for maintenance or testing the
replica data can be made available for access from the remote site. In a planned downtime
situation, the remote data is synchronized to the source before being made available and
there is no data loss.

Unity Replicator is an IP-based replication solution that produces a read-only, point-in-time
copy of a source filesystem. The Unity Replicator service periodically updates this copy,
making it consistent with the production file system. Replicator uses internal point-in-time
copies to ensure availability of the most recent point-in-time copy. This read-only replica
can be used by a NAS Server in the same Unity cabinet (local replication), or in a NAS
Server at a remote location (remote replication) for content distribution, backup and
application testing. Remote replication can also be used to cascade replicas to multiple
sites. Remote replication can be used as an asynchronous disaster recovery solution. In
the event of a failure at the primary site, a failover to the secondary site can be initiated.
When the primary site is ready to resume functionality, a failback can also be enacted.
Native Asynchronous Replication is built into the Unity platform and leverages Unified
Snapshots technology. The same technology and management is used for asynchronous
block and file replication. Native Asynchronous Replication can be performed between Unity
and UnityVSA systems for both block and file storage and also between Unity or UnityVSA
and VNXe3200, VNXe1600, or vVNX systems for block storage.
Native Asynchronous Replication can be managed from Unisphere, UEMCLI, and the REST
API. Supported Block Resources include LUNs, Consistency Groups, and VMFS Datastores.
Supported File Resources include File Systems, NAS Servers, and VMware NFS Datastores.
For Remote Replication, replication interfaces are used to send data between systems. The
replication interfaces on each system must be able to communicate with the other system.
Replication interfaces can be used for both block and file asynchronous replication
connections/sessions.
Remote Replication is a single licensed feature for Unity that enables replication between
Unity systems for storage resources. Replication connections can be asynchronous,
synchronous, or both. Both requires separate replication interfaces for Async and Sync to
be configured.

Synchronous block replication provides remote protection and a zero RPO solution for local
block resources. Data is mirrored from a local source system to remote destination system
over short distances.
Synchronous Block Replication is configurable through GUI, CLI, and the REST API to
provide protection for LUNs, Consistency Groups, and VMFS Datastores. The first FC port is
used for transmission of data between systems. Port location will change depending on the
I/O Module and CNA layout in the Unity array. A Fibre Channel Port on the local system
Storage Processor A and B must be zoned to see the Fibre Channel Port on the remote
systems Storage Processor A and B. The FC port does not require configuration in
Unisphere and can simultaneously be used for Host I/O. Synchronous Replication data
transfer connections are supported in switched or direct connect environments.
The Sync Replication Management Port is used for communication of operations between
the local and remote systems. A Sync Replication Management Port vPort must be
configured on each system. Management commands are transferred over the SPs MGMT
Port via a LAN or WAN. The management ports must be on the same subnet as the
Unisphere interface and VLAN tagging is not supported on this port.
A synchronous block replication session is configured from the source location. Upon
enabling the local block resource for synchronous replication, the synchronous replication
session creates the destination resource matching the size and thin/thick allocation. An
initial synchronization is then started from the source resource to the destination resource.
As changes are made to the source resource, they will be propagated to the destination
resource. Replication objects are 1:1. A destination resource cannot be used as the source
for another session. Shrink/Extend of a replicated block resource is not supported.

This table reflects the maximum limits for synchronous replication in the four Unity models.

Unity supports RecoverPoint and RecoverPoint for VMs. RecoverPoint CDP provides block
replication functionality across all RecoverPoint supported platforms and can be used for
VNX1/VNX2 migration or replication to Unity. RecoverPoint for VMs provides VM-granular
protection of your VMs and associated data, is compatible with Unity and other EMC
products.

This module will explore the concepts of Data At Rest Encryption, and NDMP backup
solutions for Unity products.

Unity with multi-core optimization offers controller-based Data At Rest Encryption (D@RE).
D@RE uses hardware embedded in the SAS IO controller chip in all SAS IO modules and
embedded in the Storage Processor instead of hardware embedded in the disk drive as with
self-encrypting drives (SEDs). D@RE supports all drive types. The IO modules encrypt data
as its sent to the disks. Since the encryption/decryption functions occur in the SAS
controller, it has minimal impact on data services such as replication, snapshots, etc.
D@RE primarily achieves the security of information stored on disks in the event of theft,
ensuring that data is encrypted with strong encryption, based on FIPS 140-2 Level 1
compliant encryption using Advanced Encryption Standard (AES) algorithms.
An internal key manager generates and manages encryption keys. This method is simpler,
lower cost, and more maintainable than self-encrypting drives. With the encryption
hardware embedded in the array, drive vendor and drive type are agnostic, allowing use of
any disk drive type and eliminates drive specific vendor overhead.
This provides protection against data being read from a lost, stolen, or failed disk drive.
Compliance is with industry or government data security regulations that require or suggest
encryption including, HIPAA (healthcare), PCI DSS (credit cards), and GLBA (finance).
Securely decommissioning arrays is easily accomplished by deleting pools, this in turn

deletes all drive encryption keys and most often eliminates the need to shred disk drives.
Encryption is a licensed feature and will not appear in the licenses page if the license is not
active. No data-in-place upgrades are supported and changing the encryption state
requires a destructive reinitialization.

EMC Common Anti Virus Agent provides an antivirus solution to clients using a Unity
system. It uses an industry-standard CIFS protocol in a Microsoft Windows Server domain
as well as supporting Windows clients. The antivirus agent uses third-party antivirus
software to identify and eliminate known viruses before they infect files on the storage
system. There are three key components to this solution: A Microsoft Windows server
running a 3rd party antivirus engine and EMCs Common Anti -Virus Agent, or CAVA, and the
VC Client running on the virtual NAS server.

Network Data Management Protocol (NDMP), enables backup of Unity file data to a tape
library or virtual tape appliance such as Data Domain or Avamar. Unity supports remote
NDMP, also known as 3-way NDMP. Direct attach (2-way) is not supported. Maximum
concurrent streams are: two for UnityVSA, eight for Unity 300-500, and twenty for Unity
600.
The introduction of UFS64 will require a new tape format. The format is named Format N.
The previous generation format for UFS32 is named Format N-1.
The backup module will format the data on tape in different ways based on the type of file
system on which the backup is performed. When backing up data on a UFS64 file system,
the data will be written to the tape in Format N. When backing up data on a UFS32 file
system, the data will be written to the tape in Format N-1.
The restore module will recognize the backup data in Format N-1 from older generation
systems (VNX, Celerra, VNXe, VNX2e, etc.) and restore them to a UFS64 file system on
Unity arrays. When restoring the backup data in Format N-1 to a UFS64 file system on a
Unity systems, all the new attributes will be set with their default values as specified by the
file system. When data is restored to UFS32 on a VNX, Celerra, VNXe, VNX2e, etc., all the
new attributes will be discarded as they are only applicable to UFS64. Backup data in
Format N cannot be restored to old generation systems (VNX, Celerra, VNXe, VNX2e, etc.).
Caution: Deduped files in legacy backup can not be restored to UFS64 filesystem.

This module explores the various management tools available in Unity.

EMC Unisphere for Unity provides a flexible, integrated experience for managing Unity
storage systems. Unispheres wizards help the user to provision and manage the storage
while automatically implementing best practices for the configuration. Unisphere is
completely web-enabled for remote management of the storage environment. The
Unisphere Management Server runs on the Storage Processors.
Administrative users must authenticate to the Unity login screen when using Unisphere.
Unity provides flexible options for administrative user accounts. For deployments where
Unity will be administered by multiple people, Unity offers the ability for creating multiple
unique administrative accounts. Different administrative roles can be defined for the user
accounts to distribute different administrative tasks for the users.
The new GUI has a more contemporary look and feel, delivers high performance (i.e. app
load, data retrieval, updates) and eliminates security concerns about using browser plugins.
Supported platforms include Unity, UnityVSA, and Unisphere Central. Supported browsers
and versions include: Google Chrome v33 or later, Internet Explorer v10 or later, Mozilla
Firefox v28 or later, and Apple Safari v6 or later.
A Needs Attention panel on the Enclosure View in the lower right corner is displayed only
if there are faulted components. A Health Panel allows the administrator to click on a
hardware component to bring up the Health Panel of a faulted component that will include
links to web help pages and option for ordering replacement hardware.

The interface has a more contemporary look and feel with two menus, sub-menus and a
main page. The navigation pane on the left has the Unisphere options for provisioning
storage, providing host access, protecting the data and monitoring the system operation.
The main page is where the navigation pane selection is displayed - it could be information
retrieved from the system, or configuration options for storage provisioning, host access,
and data protection. In this example, the page shows the Dashboard content.
A sub-menu with different tabs (links) on the top of the main page provides additional
options for the navigation pane selection.
The top menu on the right-corner has links for the system alarms, job notifications, help
menu, and the configuration of Unisphere preferences and global settings.

The Unisphere Main Dashboard provides a quick view of the storage system status including
the health information. A user can create a customized dashboard and save it. The
customized dashboards can be modified and deleted.
View blocks can be added to a dashboard. These view blocks can be used to view a
summary of system storage usage, monitor system alerts, view health of storage and
system resources, and provide graphs of system performance at a high level.
To add view blocks to the selected dashboard, the user must open the sub-menu on the
top, select the desired block, and click the Add View Block button.

UEMCLI is a management tool which provides a way for users to manage a system through
prompts from a Microsoft Windows or UNIX/LINUX platform. It uses EMC Unisphere for
managing a system and supports various kinds of tasks against both block and file storage.
Supported tasks include configuring and monitoring the system, managing users,
provisioning storage, protecting data, and controlling host access to storage.
UEMCLI is intended for advanced users who want to use commands in scripts for
automating routine tasks, such as provisioning storage or scheduling snapshots to protect
stored data. It can also be used as an interface in addition to other data exchange
protocols, such as SNMP, that are supported by Unity when integrating with other projects.
For example, the third party who decides to develop a centralized monitor which collects
alerts and other information from a set of systems including Unity can take advantage of
UEMCLI.

Representational State Transfer (REST) is a popular web Application Programming Interface
(API) design model that uses simple HTTP calls to create, read, update, and delete
information on a server. REST defines a data format such as JSON, XML, etc. for
information exchange.
Communications are stateless, meaning all information required to complete a request is

contained within the request. It is a set of resources, operations, and attributes that lets
you manage the array through web browsers, command-line HTTP tools, programming
languages like C++ and Java, and scripting Languages like Perl and Python.
Customers, Partners, and Internal EMC groups have created a strong demand for this type
of management API. REST is very common within the IT industry and allows programs to
easily integrate with the storage system. REST API is more programmer-friendly than
UEMCLI and doesnt require a separate client.
The REST API allows interaction with Unisphere management functionality, including system
settings and monitoring, host and remote system connections, network settings, storage
management, data protection, including snapshots and replication, and it supports
configuration management.

Storage reclamation is the ability to evacuate portions of the file system block address
space and repurpose or release underlying storage of the file system using the shrink
operation. It can be initiated manually by the user or automatically to reclaim allocated,
but unused space, back to the pool.

This animation shows the steps involved in manually shrinking a Thick UFS64 filesystem.
The filesystem is 1 TB in size and contains 250 GB of data. The user wishes to Shrink the
filesystem to 300 GB in size.
The user makes the request to Shrink the 1 TB filesystem by 700 GB to a new size of 300
GB. The Storage Manager scans the space involved and determines some data must be
moved or Evacuated from the space to be reclaimed. The data is moved to free space
within the filesystem to complete the Evacuation. The filesystem is resized to 300 GB,
freeing up 700 GB of storage. Finally, the 700GB of newly freed space is returned to the
Storage Pool and is added to the Storage Pool free space.

This animation shows the steps involved in manually shrinking a Thin UFS64 filesystem.
The filesystem is 1 TB in size and contains 250 GB of data. This filesystem is not fully
allocated and only 450 GB of Pool Storage is in use. The user wishes to Shrink the
filesystem to 300 GB in size.
The user makes the request to Shrink the 1 TB filesystem by 700 GB to a new size of 300
GB. The Storage Manager scans the space involved and determines some data must be
moved or Evacuated from the space to be reclaimed. The data is moved to free space
within the filesystem to complete the Evacuation. The filesystem is resized to 300 GB,
freeing up 150 GB of storage. Finally, the 150 GB of newly freed space is returned to the
Storage Pool and is added to the Storage Pool free space.

This animation shows the steps involved in the Auto Shrink process of a Thin UFS64
filesystem. In this case, OE parameters have been set to check for conditions and Shrink
when the conditions are met. The filesystem is 1 TB in size and contains 250 GB of data.
This filesystem is not fully allocated and only 450 GB of Pool Storage is in use. The user
wishes to Shrink the filesystem to 300 GB in size and has set the Shrink parameters to
check for a used-to-allocated ratio of less than 70%.
The Auto Shrink starts monitoring the filesystem at 12:00. Every hour and a half, the
Auto Shrink mechanism checks to see if the filesystem is below the specified used-to-
allocated ratio of 70%. The Auto Shrink mechanism will initiate the Shrink operation when
it has five checks that meet the specification. In this case, the Shrink will now take place.
The Storage Manager scans the space involved and determines some data must be moved
or Evacuated from the space to be reclaimed. The data is moved to free space within the
filesystem to complete the Evacuation. The filesystem is resized to 300 GB, freeing up 150
GB of storage. Finally, the 150 GB of newly freed space is returned to the Storage Pool
and is added to the Storage Pool free space.

This module covers Dynamic Access control and Quality of Service (QoS).

Domain-based Dynamic Access Control enables administrators to apply access control
permissions and restrictions based on well-defined rules that can include the sensitivity of
the resources, the job or role of the user, and the configuration of the device that is used to
access these resources.
For example, a user might have different permissions when they access a resource from
their office computer versus when they are using a portable computer over a virtual private
network. Or, access may be allowed only if a device meets the security requirements that
are defined by the network administrators. When Dynamic Access Control is used, a users
permissions change dynamically without additional administrator intervention if the users
job or role changes (resulting in changes to the users account attributes in AD DS).
Dynamic Access Control is not supported in Windows operating systems prior to Windows
Server 2012 and Windows 8. When Dynamic Access Control is configured in environments
with supported and non-supported versions of Windows, only the supported versions will
implement the changes.

The Quality of Service Feature is used to limit the amount of host IO that is serviced by the
storage system. It is not a guarantee of a level of IO. QoS is supported for LUNs, attached
snapshots, and VMFS Datastores. QoS has the ability to limit host IO based on Maximum
IOPS or Maximum Bandwidth (KBPS or MBPS). Because Unity Quality of Service
management is array resident, there is no host component to load, and no performance
impact on the host. UQM controls array performance by allocating resources to user-
defined classes of I/O. This resource allocation allows the specified IO classes to meet pre-
defined performance goals.
QoS may be managed by Unisphere GUI or UEMCLI and is supported on both Unity
hardware and the UnityVSA. Controls include a system wide Pause/Resume function. Host
IO Limits are based on a user-created policy. A LUN without a Host IO Limit is not
impacted. QoS policies do not limit internal IO (migration, replication, etc.). Host IO Limit
settings can be changed at any time without Pausing/Resuming Host IO Limits on the
system.
Considerations: Unisphere Quality of Service is either enabled or disabled. All Host IO

Limits are active if the feature is Active. A LUN can be associated with only one Host IO
Limit policy at a time. The administrator must specify if a policy will be shared or not
shared at the time of the policy creation as there is no ability to change this setting at a
later time. A maximum of 512 Host IO Limits is permitted on a single storage system and
is Unity model independent. Each individual Host IO Limit counts towards the maximum
with each shared Host IO Limit only counted once regardless of the number of LUNs
assigned to it.

Under the System option, select Performance, then select the Dashboard for the system
that will include the performance charts. The time range for all the charts displayed in the
performance dashboard is configured using the Custom link on the top of the main page.
Select the start and end dates and times of the values displayed. Then select Update to get
the latest data.
To include additional performance metric charts, click on the Add Charts button, then
select the resource type from the list of performance charts. From the selected performance
chart, choose the available metrics for the resource type to be displayed. Then select
Generate Charts.

This module discusses the integration of Unity into virtualized system environments.

This feature is designed to provide File (NFS) and Block (iSCSI) Vvols, runs as a single SP
configuration only, so code upgrades and reboots are disruptive. The Boot Blocking
function will cause the VSA to go into service mode if a vCPU or VM memory requirements
are not met or if network interfaces are changed.
For serviceability, Data Collects contain additional VSA-specific information. The REST API
is fully supported. If the admin password is lost, there is a VSA procedure to reset the
password. First, reboot the UnityVSA. Second, when EMC Boot is displayed, press the
Tab key to stop the boot process. Third, append vvnx_reset_admin_password to the
kernel parameters and press the Enter key. Fourth, after the VSA boots up, log into
Unisphere with the default password of Password123# and you will be prompted to
change the password.

This table shows the maximum limits for Unity VVols.

Storage Analytics for Unity provides automated operations management using patented
analytics and an integrated approach to performance, capacity and configuration
management. EMC Unity Storage Replication Adapter is a storage replication adapter that
extends the disaster-restart management functionality of VMware SRM to the EMC Unity
storage environment.
Unity is optimized for virtualized environments, not only in its storage capabilities, but also
in its close integration with VMware. Unity has EMC tools to enhance its integration with
VMware, plus it works closely with existing VMware features. Key features which Unity
seamlessly integrates are, VMware vSphere Storage APIs Array Integration for SAN,
VMware vSphere Storage APIs Array Integration for NAS, Virtual Storage Integrator, and
VMware vCenter Site Recovery Manager.

VASA is an acronym that stands for vStorage API for Storage Awareness. VASA is a
VMware-defined API meant to provide a common way for VMware to integrate with storage
vendors. The API is implemented using an out-of-band, Simple Object Access Protocol
(SOAP) over HTTPS. VASA was introduced with vSphere 5.0 in 2011.
The initial release (v1.0) of VASA is a read-only API that simply gathers information about
the storage system, focusing on LUN and File System properties and data services, and
displays this information in vCenter. VASA v2.0 adds significant functionality to the
protocol, including additional insight into the storage, reporting of granular IO statistics,
and active management of new storage concepts such as virtual volumes and their related
entities.
In general, a VASA session is created when a vCenter connects to the VASA Provider using
the VASA protocol; the protocol allows (and enforces) only one session per vCenter.
Sessions are created with information about the clients context (FC/iSCSI initiators, NFS
mounts, etc.) for use in filtering results. Sessions are maintained in memory only; they are
not currently persisted across restarts. vCenter will detect a failed session and
automatically start a new one.

SMI-S (Storage Management Initiative Specification) is a standard developed by the
Storage Network Industry Association (SNIA) that is intended to facilitate the management
of storage devices from multiple vendors in storage area networks (SANs).
Microsoft Windows Server 2016 and its System Center Virtual Machine Manager (SCVMM)
will continue to use the SMI-S API to manage external storage. The Unity array is designed
to integrate with the Microsoft Windows Server and SCVMM next version, coming in Q2
2016, and provides more APIs to support their new feature of storage health monitoring.
Health monitoring requires storage vendors to deliver lifecycle indication of alerts on

specific storage objects, including: Array, LUN/Disk, LUN/Pool Capacity, LUN/LUN group
replication, Filesystem, File Share, File System Capacity, Fan/Power supply, LUN/LUN group
replication as defined in the SMI-S Indication and Health Profiles.

EMC Storage Integrator (ESI) for Windows is a tool targeted at Windows and Microsoft
application administrators. ESI for Windows provides storage viewing and provisioning
capabilities. ESI also enables the user to create a file share and mount that file share as a
network attached drive in the Windows environment.
ESI supports the EMC Unity and the UnityVSA series, VNX, Symmetrix VMAX and the
VMAXe.
ESI supports Hyper-Vvirtual disks in release 1.3 and beyond.

This module discusses the concepts, uses, and licensing for the UnityVSA (Virtual Storage
Appliance).

UnityVSA runs on general purpose hardware on a VMware ESXi hypervisor. The UnityVSA is
a Unified Array, providing both Block (iSCSI) and File (NFS & SMB/CIFS), and VVols in one
integrated platform. A consistent look and feel across the Unity platform is made possible
using HTML5 Unisphere. A consistent feature set and data services such as Unified
Snapshots and Replication are available with the UnityVSA.
The UnityVSA can coexist with and provide storage to applications running on the same
server hardware. Multiple VSA instances can be deployed on a single server.

For the virtual systems, the license keys are based on the systems UUID (Universally
Unique Identifier). These keys, which are included in the License (.lic) files can be obtained
through the Get License Online link in the window. The user must provide the virtual
system UUID and the license authorization code (LAC) ID to download the license file
locally.
The license file must then be transferred to a computer with access to the virtual Unity
system. By clicking on the Install License link, the user can upload the license file from the
local machine to the storage system after accepting the license agreement.
The following will be a typical scenario for your UnityVSA. The customer purchases a
license which will be valid for 12 months. A month before expiration, they see license
expiration alerts in Unisphere. These are repeated periodically- 28 days to expiry, 21 days,
14, 7, 6, 5, 4, 3, 2, and 1. There is also a Get License link in the GUI that directs
customers to Software Licensing Central where they can renew their license. Once the
license expires, users can continue to use the UnityVSA but not provision anything new
until they renew their license.
Please note that support is bundled in with the VSA. So if a license expires, the customers
support contract expires too. They can never have the software without support or just
support with an expired software license. From a diagnosis standpoint, the support
contract is your best gauge. The license expiration date is also stored in ELMS.

This chart shows the Unity features that are supported by the UnityVSA. Note that the
features that rely on specific physical hardware are not supported by the UnityVSA.

This module discusses the benefits of ESRS Virtual Edition (VE).

EMC Secure Remote Services (ESRS) is a secure, bi-directional connection between EMC
products in end user environments and the EMC Support infrastructure. It enables EMC to
remotely monitor configured systems by receiving system-generated alerts and to connect
into the customer environment for remote diagnosis and repair activities. It also provides a
high-bandwidth connection for large file transfers, enables proactive Service Request (SR)
generation and usage license reporting, and operates on a 24x7 basis.
ESRS Virtual Edition (VE) is available with Unity as a Gateway version installed on an off-
array Virtual Machine (VM) and can be managed with Unisphere, UEMCLI, and REST API.
Electronic licensing is an EMC wide service that allows products to send electronic licensing
and usage information to EMC via ESRS VE . Unity systems automatically send information
on licensed features to EMC on a weekly basis. Both EMC personnel and customers can
view this information. The feature is enabled automatically when ESRS VE is enabled.
Customer service will have the ability to disable/enable this feature via a script.

This module will discuss the available block and file migration options available to new Unity
installations.

Above are the options available to migrate file data to a Unity target machine.

Above are the options available to migrate block data to a Unity target machine.

The following tools can be used for VNX2 to Unity/UnityVSA data migration:
RecoverPoint/RecoverPoint for VMs and VPLEX for replication; SAN Copy, PPME, and
VMware Storage vMotion for block migration; and EMCopy and Rsync for file migration.
The following tools can be used for VNXe3200 to Unity/UnityVSA: Native Asynchronous
Block Replication/RecoverPoint/RecoverPoint for VMs and VPLEX for replication; PPME and
VMware Storage vMotion for block migration; and EMCopy and Rsync for file migration.
The following tools can be used for VNXe1600 to Unity/UnityVSA: Native Asynchronous
Block Replication for replication and VMware Storage vMotion for block migration.

This course covered the Unity storage solution models, features, data features,
architecture, and management.
This concludes the Unity Fundamentals training.

Unity Fundamentals SRG

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unity Fundamentals SRG

Uploaded by

Copyright:

Available Formats

Welcome to Unity Fundamentals.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION

EMC, EMC AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 1

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals #

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 2

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 3

Copyright 2016 EMC Corporation. All rights reserved. Course Name 4

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 5

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 6

Copyright 2016 EMC Corporation. All rights reserved. 7

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 8

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 9

Virtualization management integration allows the VMware administrator or the Microsoft

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 10

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 11

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 12

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 13

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 14

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 15

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 16

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 17

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 18

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 19

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 20

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 21

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 22

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 23

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 24

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 25

Access to Block Storage is provided by containers on both Storage Processors to hosts

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 26

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 27

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 28

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 29

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 30

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 31

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 32

Optional software includes RecoverPoint Advanced, PowerPath Multipathing, PowerPath

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 33

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 34

Copyright 2016 EMC Corporation. All rights reserved. 35

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 36

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 37

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 38

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 39

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 40

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 41

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 42

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 43

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 44

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 45

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 46

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 47

Securely decommissioning arrays is easily accomplished by deleting pools, this in turn

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 48

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 49

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 50

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 51

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 52

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 53

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 54

Copyright 2016 EMC Corporation. All rights reserved. Unity Fundamentals 55