Unity Snapshots SRG

Welcome to Unity Snapshots.
Copyright ©2016 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the information in this publication is accurate as o f 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 sh ould 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, 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 Snapshots 1

This course covers the Snapshots feature for the EMC Unity platform. It includes Snapshots
for both block and file storage resources. The course provides an overview of the feature,
how Snapshots are created, managed, and used. It also includes the feature capabilities.
Demonstrations of Snapshots are also included.

In this module, an overview of Unity Snapshots is provided. The architecture of Unity
Snapshots with its Redirect on Write technology is discussed and the benefits and
capabilities are listed.

The Unity Snapshots feature is enabled with the Local Copies license for Unity that enables
space efficient point-in-time snapshots of storage resources for Block, File and VMware. The
snap images can be read-only or read/write and used in a variety of ways. They can provide
an effective form of local data protection to restore the production data to a known point-
in-time data state should data be mistakenly corrupted or deleted by the users. Images can
be accessed by hosts for data backup operations, data mining operations, application
testing, or decision analysis tasks. In the upcoming slides we will dive into the details of its
architecture, capabilities, benefits, and specifics of its operations and uses.
Note: Snapshots are not full copies of the original data. It is recommended that you do not
rely on snapshots for mirrors, disaster recovery, or high-availability tools. Because
snapshots of storage resources are partially derived from the real -time data in the relevant
storage resource, snapshots can become inaccessible (not readable) if the primary storage
becomes inaccessible.

Snapshots of storage resources (block LUNs, file systems, and VMware Datastores) are
architected using Redirect on Write technology. This architecture avoids a performance
penalty that Copy on First Write technology has when existing data is changed. With
Redirect on Write technology, when a snapshot is taken, the existing data on the storage
object remains in place and provides the snapshot point-in-time view of the data.
Production data access also uses this view to read existing data. Another benefit of Redirect
on Write is that no storage resource is needed to create a snapshot. With Copy on First
Write technology, a storage resource had to be reserved to hold original data that changed
to preserve the point-in-time view. As its name implies, with Redirect on Write technology,
when writes are made to the storage object, those writes are redirected to a new location
allocated as needed from the parent pool in 256 megabyte stripes. New writes are stored in
8 kilobyte chunks on the newly allocated stripe. Reads of the new writes are serviced from
this new location as well.
If the snapshot is writable, any writes are handled in a similar manner; stripe space is
allocated from the parent pool and the writes are redirected in 8 kilobyte chunks to the new
space. Reads of newly written data are also services from the new space.
Storage space is needed in the pool to support snapshots as stripes are allocated for
redirected writes. Because of the on-demand stripe allocation from the pool, snapped thick
file systems will transition to thin file system performance characteristics.

A LUN Consistency Group (CG) is a grouping of up to 50 LUNs to form a single instance of
LUN storage. They are primarily designed for a host application that will access multiple
LUNs, like a database application. Snapshots provide a mechanism for capturing a
snapshot of the multiple LUNs within a consistency group. When a Consistency Group
Snapshot is taken, the system will complete any outstanding IO to the group of LUNs, then
suspend writes to the LUNs until the snap operation completes. This allows the snapshot to
capture a write-order consistent image of the group of LUNs.

With Unity Snapshots, it is possible to create multiple snapshots of a LUN to capture
multiple point-in-time data states. In this example the 3 o’clock and the 4 o’clock
snapshots are two different “child” snapshots of a common parent; meaning they capture
two different data states of a common storage object.
It is also possible to copy a snapshot. In this example, the 4 o’clock snapshot is copied and
other than having a unique name, the copy will be indistinguishable from the source
snapshot and both capture identical data states.
LUN snapshots and copies of LUN snapshots are writable objects but are unmodified from
their sources until they are attached to a host. In this example a copy of the 4 o’clock
snapshot is attached to a secondary host for access. At this point the snapshot data state is
marked as modified from its source. A LUN snapshot tree supports one snapshot attach at a
time. To access different snapshots in the tree the host would have to be detached from the
snap and attached to another desired snapshot in the tree.
Any subsequent copy of the attached snapshot will capture the data state of the source
snapshot at the point-in-time of the copy operation.

As with LUN snapshots, it is possible to create multiple snapshots of a file system to capture
multiple point-in-time data states. The 3 o’clock and the 4 o’clock snapshots in this
example are two different “child” snapshots of the same file system parent and capture its
two different point-in-time data states.
Snapshots of a file system can be created either as read-only or read/write and are
accessed in different manners which will be covered later.
Copies of snapshots are always created as read/write snapshots. The read/write snapshots
can be shared by creating an NFS export or SMB share to them. When shared, they are
marked as modified to indicate their data state is different from the parent object.
It is also possible to nest copied and shared snapshots that form a hierarchy of snapshots
to a maximum of 10 levels deep.

The table defines a variety of combined Snapshot capabilities for each of the Unity platform
models. These combined limits have an interaction between each other. For example, if a
Unity 300 system had 10 LUNs and 10 file systems, each LUN and file system could not
have 256 user snapshots because that would exceed the maximum user snapshots of 1000
for the system.

This module covered an overview of Unity Snapshots. The redirect on write architecture of
Unity Snapshots was detailed and its benefits and capabilities were listed.

This module covers the creation of block and file Snapshots. It also details using a schedule
for creating Snapshots. The operations that can be performed on Snapshots are also shown.

Snapshots are created on storage resources for Block, File and VMware. And all are done in
a similar manner.
For Block, the snapshot is created on a LUN or a group of LUNs in the case of a Consistency
Group. For File, the snapshot is configured on a file system. For VMware the storage
resource is either going to be a LUN for a VMFS datastore or a file system for an NFS
datastore. When creating each of these storage resources, the Unity system provides a
wizard for their creation. Each wizard provides an option to automatically create snapshots
on the storage resource. Each resource snapshot creation is nearly identical to the other
resources.
For storage resources already created, snapshots can be manually created for them from
their Properties page. As with the wizard, the snapshot creation from the storage resource
Properties page is nearly identical to the other resources. The following few slides will show
snapshot creation within the Block storage LUN creation wizard and the File storage file
system creation wizard. It will also show creating manual snapshots from the LUN and file
system Properties pages.
Video demonstrations will be provided showing all forms of storage resource snapshot
creation.

LUN snapshots can easily be created in a number of ways. Within the wizard to create a
LUN, there is an option to automatically create snapshots for the LUN based on a schedule.
The wizard contains a dropdown selection that has three different system defined
schedules to select from to create the LUN snapshots. Within each schedule there is also a
snapshot retention value.
A customized schedule can also be created for use. The scheduler provides the ability to
configure a snapshot frequency by the hour, day or week. A snapshot retention policy can
also be defined.
Note: fields annotated with a red asterisk are required for the configuration.

For existing LUNs, snapshots are easily created from the LUN Properties page by selecting
the Snapshots tab.
Select the + icon to create a snapshot of the LUN. The snapshot must be configured with a
name; by default the system provides a name having a year, month, day, hour, minute,
second format. Customized names can also be configured. A Description field for the
snapshot can optionally be annotated. One of three Retention Policies must be configured.
The default retention configuration is the Pool Automatic Deletion Policy which will
automatically delete the snapshot if Pool space reaches a specified capacity threshold. A
customized retention time can alternately be selected and configured for snapshot deletion
on a specified calendar day and time. The other alternative is to select the No Automatic
Deletion option should the snapshot need to be kept for an undetermined amount of time.

Similar to LUNs, file system snapshots can easily be created in a number of ways. Within
the wizard to create a file system, there is an option to automatically create snapshots for
the file system based on a schedule. File system snapshots created by a schedule are read-
only.
The wizard contains a dropdown selection that has three different system defined
schedules to select from to create the file system snapshots. Within each schedule there is
also a snapshot retention value.
A customized schedule can also be created for use. The scheduler provides the ability to
configure a snapshot frequency by the hour, day or week. A snapshot retention policy can
also be defined.
As noted before, fields annotated with a red asterisk are required for the configuration.

Similar to the LUN snapshot seen earlier, existing file systems snapshots are easily created
from the file system Properties page by selecting the Snapshots tab. A manually created
file system snapshot can be read-only or read/write.
Select the + icon to create a snapshot of the file system. The snapshot must be configured
with a name; the system by default provides a name based on the creation time in a year,
month, day, hour, minute, second format. Customized names can also be configured. An
optional Description field for the snapshot can be annotated. One of three Retention Policies
must be configured. The default retention configuration is the Pool Automatic Deletion
Policy which will automatically delete the snapshot if Pool space reaches a specified capacity
threshold. A customized retention time can alternately be selected and configured for
snapshot deletion on a specified calendar day and time within a year of creation. The other
alternative is to select the No Automatic Deletion option should the snapshot need to be
kept for an undetermined amount of time.
The Access Type section requires configuration by selecting one of the two options for the
snapshot to be created read-only or read/write.

The system’s user interface provides a Snapshot Schedule page that lists all the system and
user defined schedules and if they are in use. The user defined schedules can be edited
from this page but the system defined schedules cannot be edited. User defined schedules
can be created using a frequency granularity of hours, daily or weekly and be retained for
31 days.
Additional user defined schedules can be created as shown here. This example shows a
schedule that will create weekend snapshots that will be created at midnight and retained
for two weeks.

To apply a snapshot schedule to a storage resource, simply go to the Snapshots tab on the
Properties page of the resource and select the Schedule Snapshot option. From the
Snapshot schedule dropdown list select the desired schedule to apply to the resource.

This video covers creating Snapshots for each Unity storage resource; LUN and LUN CG, file
system, and VMware datastores. Automatic creation is shown via each resource creation
wizard and manual creation is shown via each resource Properties page.

The operations that can be performed on a snapshot differ based on the type of storage
resource the snapshot is on. Operations on LUN-based snapshots are Restore, Attach to
host, Detach from host, and Copy. Operations on file system-based snapshots are Restore
and Copy.

The Snapshot Restore operation will roll back the storage resource to the point-in-time data
state that the snapshot captures. In this Restore example, a LUN is at a 5 o’clock data state
and is going to be Restored from a snapshot with a 4 o’clock data state.
Before performing a restore operation, detach hosts attached to any of the LUN snapshots.
Also ensure that all hosts have completed all read and write operations to the LUN you want
to restore. Finally disconnect any host accessing the LUN. This may require disabling the
host connection on the host-side.
Now the Restore operation can be performed. From the 4 o’clock snapshot select the
Restore operation. The system will automatically create a snapshot of the current 5 o’clock
data state of the LUN to capture its current data state before the restoration operation
begins. The LUN is restored to the 4 o’clock data state of the snapshot.
The hosts can now be reconnected to the resources they were connected to prior to the
restore and resume normal operations.

The Restore operation is accessed from the Properties page of the storage resource. Select
its Snapshots tab then select the snapshot to restore from. The Restore operation is
accesses from the More Actions dropdown list. The system will create a restore point
snapshot of the current data state of the LUN prior to the restoration operation. Once
complete the new restore point snapshot is listed.

The Snapshot Attach operation will attach a connected host to a snapshot for read/write
access to its point-in-time view of the LUN data. In this Attach example, a secondary host is
going to Attach to the 3 o’clock snapshot of the LUN.
Before performing an Attach operation, hosts must be configured for snapshot access to
the LUN. There are two possible settings: Snapshot access or LUN and Snapshot access.
The Snapshot access setting provides a secondary host read/write access to all the
snapshots associated with the LUN, but no access to the LUN itself. A host can access and
recover data from snapshots associated with the LUN but has no access to the data on the
LUN itself. The LUN and Snapshot access setting provides a primary host read/write access
to both the LUN itself and all of the snapshots associated with the storage resource. A host
can use the LUN data and can recover data from snapshots associated with the LUN.
Now the Attach operation can be performed. From the 3 o’clock snapshot, select the Attach
to host operation. The system will optionally create a copy of the snapshot to preserve its
data state before the attach operation begins. The secondary host is attached to the 3
o’clock snapshot of the LUN.

To give a host access to snapshots of a LUN, from the LUN Properties page select the
Access tab. Hosts can be added to LUN access using the + icon. To provide a listed host
access to snapshots of the LUN, select the Snapshot or LUN and Snapshot setting from the
Modify Access dropdown.
The Attach to host operation is accessed from the Properties page of the storage resource.
Select its Snapshots tab then select the snapshot to attach to. The Attach to host operation
is accessed from the More Actions dropdown list. The system will optionally create a copy
of the snapshot to preserve its integrity.

The Snapshot Detach operation will detach a connected host from a LUN snapshot. In this
Detach example, a secondary host is going to Detach from the 3 o’clock snapshot of the
LUN.
Before performing a Detach operation, allow any outstanding read/write operations of the
snapshot attached host to complete.
Now the Detach operation can be performed. From the 3 o’clock snapshot, select the
Detach from host operation. The secondary host is detached from the 3 o’clock snapshot of
the LUN.

The Detach from host operation is accessed from the Properties page of the storage
resource. Select its Snapshots tab then select the snapshot to detach from. The action for
Attach to host and Detach from host are mutually exclusive operations. The Detach from
host operation is only available for snapshots that are attached. Select an attached
snapshot to detach from. Perform the Detach from host operation by selecting it from the
More Actions dropdown list. In the Detach confirmation window, confirm the detach
operation to complete the operation.

The Snapshot Copy operation will make a copy of an existing snapshot that is either
attached or detached from a host. The copy will capture the existing data state of the
snapshot it copies. In this Copy example, a copy of an existing 4 o’clock snapshot is being
made . The copy inherits the parent snapshot data state of 4 o’clock and its retention
policy.

The Copy operation is accessed from the Properties page of the storage resource. Select its
Snapshots tab then select the snapshot to copy. Perform the Copy operation by selecting it
from the More Actions dropdown list. The system will provide a unique name for the
snapshot copy based on the time of creation or optionally a customized name can be
assigned.

The Snapshot Restore operation for a file system is similar to the Restore operation of a
LUN. It will roll back the file system to a point-in-time data state that a read-only or
read/write snapshot captures. In this Restore example, a file system is at a 5 o’clock data
state and is going to be Restored from a read-only snapshot with a 4 o’clock data state.
Before performing a restore operation, disconnect clients from any of the file system
snapshots. Also quiesce IO to the file system being restored.
Now the Restore operation can be performed. From the 4 o’clock snapshot select the
Restore operation. The system will automatically create a snapshot of the current 5 o’clock
data state of the file system to capture its current data state before the restoration
operation begins. The file system is restored to the 4 o’clock data state of the snapshot.
The connections and IO to the resources can now be resumed for normal operations.

The Restore operation is accessed from the Properties page of the storage resource. Select
its Snapshots tab then select the snapshot to restore from. The Restore operation is
accessed from the More Actions dropdown list. The system will create a restore point
snapshot of the current data state of the file system prior to the restoration operation.
Once complete the new restore point snapshot is listed.

The Snapshot Copy operation will make a copy of an existing file system snapshot that is
either read-only or read/write shared or unshared. The copy will capture the existing data
state of the snapshot it copies. In this Copy example, a copy of an existing 4 o’clock read-
only snapshot is being made . The copy will be read/write and inherits the parent snapshot
data state of 4 o’clock and its retention policy.

The Copy operation is accessed from the Properties page of the storage resource. Select its
Snapshots tab then select the snapshot to copy. Perform the Copy operation by selecting it
from the More Actions dropdown list. The system will provide a unique name for the
snapshot copy based on the time of creation or optionally a customized name can manually
be assigned.

This module covered the creation of snapshot for Unity storage resources; LUNs and LUN
Consistency groups, file systems, and VMware datastores. User customized snapshot
schedules were created and applied to Unity storage resources to automate snapshot
creation and deletion. The operations for LUN and file system snapshots were detailed.

This module covers the use of Snapshots. It details accessing block and file snapshots. It
also shows how the Checkpoint Virtual File System is accessed by Windows and NFS users
to restore corrupted or deleted files.

The process of accessing a LUN snapshot requires performing tasks on the storage system
and on the host that will access the snapshot.
On the storage system the host will have to be configured to access snapshots of the LUN.
This task is done on the LUN Properties page from the Access tab. A host has to have
connectivity to the storage, either via fibre channel or iSCSI, and be registered. Next, from
the Snapshots tab, a snapshot is selected and the snapshot operation Attach to host needs
to be performed.
Now tasks from the host will need to be done. The host will need to discover the disk
device that the snapshot presents to it. Once discovered, then the host can access the
snapshot as a disk device.
A short video follows that demonstrates a host accessing a LUN snapshot.

This is a short video demonstrating a Windows 2012 iSCSI attached host accessing a LUN
snapshot.

The process of accessing a file system read/write snapshot requires performing tasks on
the storage system and on the client that will access the snapshot.
On the storage system an NFS and/or SMB share will have to be configured on the
read/write snapshot of the file system. This task is done from their respective pages.
Now tasks from the client will need to be done. The client will need to be connected to the
NFS/SMB share of the snapshot. Once connected, then the client can access the snapshot
shared resource.
A short video follows that demonstrates client access to a file system snapshot.

This is a short video demonstrating an NFS client accessing a read/write file system
snapshot.

The process of accessing a file system read-only snapshot is very different than accessing a
read/write snapshot. The read-only file system snapshot is exposed to the client through a
checkpoint virtual file system (CVFS) mechanism that Snapshots provides. The read-only
snapshot access does not require performing any tasks on the storage system. All the
tasks are performed on the client through its access directly to the file system. The tasks
for NFS clients are slightly different than the tasks for SMB clients.
The first task for an NFS client is to connect to an NFS share on the file system. Access to
the read-only snapshot is established by accessing the snapshot’s hidden .ckpt data path.
This path will redirect the client to the point-in-time view that the read-only snapshot
captures.
Similarly, the first task for an SMB client is to connect to an SMB share on the file system.
Access to the read-only snapshot is established by the SMB client accessing the SMB
share’s Previous Versions tab. This will redirect the client to the point-in-time view that the
read-only snapshot captures.
Because the read-only snapshot is exposed to the clients through the CVFS mechanism,
the clients are able to directly recover data from the snapshot without any administrator
intervention. For example, if a user either corrupted or deleted a file by mistake, that user
could directly access the read-only snapshot and get an earlier version of the file from the
snapshot and copy it to the file system to recover from.
A short video follows that demonstrates client access to a file system read-only snapshot.

This is a short video demonstrating an NFS client and an SMB client accessing a read-only
file system snapshot via CVFS.

This module covered the process of attaching a host to a LUN snapshot to access its point-
in-time data state. Client access of a read/write file system snapshot was demonstrated.
The CVFS access of a read-only file system snapshot was shown for both NFS and SMB
clients.

This course covered an overview of the Unity Snapshots feature along with its architecture
and capabilities. Snapshots were created for the various Unity storage resources and their
specific snapshot operations were discussed. Finally snapshot usage was shown with hosts
and clients accessing the point-in-time data of snapshots.
This concludes the training.

Unity Snapshots 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 Snapshots SRG

Uploaded by

Copyright:

Available Formats

Welcome to Unity Snapshots.

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

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

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

Copyright 2016 EMC Corporation. All rights reserved. Unity Snapshots 4

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

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

Copyright 2016 EMC Corporation. All rights reserved. Unity Snapshots 7

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A short video follows that demonstrates a host accessing a LUN snapshot.

Copyright 2016 EMC Corporation. All rights reserved. Unity Snapshots 35

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

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

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

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

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

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

This concludes the training.

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

You might also like