Welcome to Enterprise Copy Data Management 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², the EMC logo, AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica,
Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Aveksa, 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, CoprHD, 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, DSSD, 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,
Isilon, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint,
MirrorView, Mozy, Multi-Band Deduplication,Navisphere, Netstorage, NetWitness, NetWorker, EMC OnCourse, OnRack, 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, Silver Trail, 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, VCE. 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.

Revision Date: August 2016

Course Number: MR-1WN-ENTCDMFUN

Copyright 2016 EMC Corporation. All rights reserved. 1

Enterprise Copy Data Management Fundamentals
This course provides an introduction to Enterprise Copy Data Management (eCDM). It
includes an overview of the eCDM architecture, features and functionality. Additionally, it
includes a review of basic troubleshooting, best practices as well as where to find additional
information.

Copyright 2016 EMC Corporation. All rights reserved. 2

Enterprise Copy Data Management Fundamentals
This module provides an introduction to eCDM along with use cases and benefits of the
solution.

Copyright 2016 EMC Corporation. All rights reserved. 3

Enterprise Copy Data Management Fundamentals
In past data centers, there was typically one role responsible to create backup and copies.
As the environment is evolving, more users are having their roles expanded to also take up
the responsibility to create backups and copies.

For these users, it eliminates the need to wait for the backup admin to perform specific
backup-related jobs. One issue that arises from that is oversight. There is no one tool to
manage these users and define specific service levels to satisfy these users’ needs. As a
result, a user ends up having more copies than needed, or copy data growth. This creates a
$51 billion dollar problem, according to IDC. Thus having the multitude of silos in the data
center presents two opportunities:

• A risk: where there is no one overseeing the environment to make sure everyone
complies – including occurrences where only one user has the right to delete primary and
protection copy.

• A cost: it may be cheaper to organize in silos, but no one has awareness on the exact
amount of copies there are and how long they should exist.

Copyright 2016 EMC Corporation. All rights reserved. 4

Enterprise Copy Data Management Fundamentals
Data protection is evolving from the wave of traditional server-centric backup designed
around centralized control with backup servers and agents sending data to protection
storage.

Modern data management is designed for self service to empower application owners,
storage admins to backup directly from the data source (an application, storage array, etc.)
to protection storage. This model is becoming increasingly popular because it puts control
directly in the hands of the data owners – rather than relying on a centralized backup team.

However, the new self-service model requires intelligent oversight on copies and service
levels across the business to ensure that data is protected and you maintain consistent
service levels across the business.

A layer is required within modern data management that provides copy oversight and
enforces the rules of the business by discovering and tracking of copies regardless of who
created them.

Finally – to tie it all together, you need intelligent analytics and search that can cross both
the traditional and modern approaches ensuring that you optimize operations across all
data centers globally.

Copyright 2016 EMC Corporation. All rights reserved. 5

Enterprise Copy Data Management Fundamentals
Let’s take a moment to understand how eCDM is used to address the copy data
management issue:

• In three easy to follow steps, eCDM builds out a catalog by discovering “protectable”
assets on a VMAX or XtremIO and “protect to” assets on a Data Domain. It counts and
relates the copies back to primary data sources by displaying the relationship between
the two - regardless of how the copy was created.

• It automates copy management based on the Service Level Agreement (SLA). It focuses
on what the user wants to achieve, and provides the end-user with an easy to read list of
SLO that can be assigned to data.

• It makes sure the copies are being efficiently used. This is basically making sure that the
environment achieve compliance, and this is done either by eCDM or by eCDM
discovering copies created by a 3rd party application like Unisphere or Application Agent.
ProtectPoint, XtremIO Virtual Copies (XVC) and SnapVX are strongly leveraged for
delivery this feature.

Copyright 2016 EMC Corporation. All rights reserved. 6

Enterprise Copy Data Management Fundamentals
Enterprise Copy Data Management software is a enterprise-wide solution that streamlines
the process of monitoring, managing, and analyzing copies of data while addressing copy
sprawl. The eCDM software is a tool that is designed for self-service copy orchestration,
automated Service Level Objectives (SLO) compliance and actionable insight that optimizes
efficiency.

Some of the key benefits that eCDM offers include: (1) it can discover data anywhere; (2)
its intelligence enables self-service and (3) it’s efficient where it’s creating or storing copies.
Copies typically have four potential use cases: text/dev, operations, protection and
analytics.

Copyright 2016 EMC Corporation. All rights reserved. 7

Enterprise Copy Data Management Fundamentals
With the introduction of ‘Enterprise Copy Data Management’, EMC delivers copy data
management for the modern data center by:

• Discovering copies for non-disruptive global oversight.

• Automating SLO compliance via efficient copy creation.

eCDM is designed to enable self-service while still providing global oversight and address
the $50 billion copy data problem by significantly reduce storage and data protection costs.
Let’s take a look into each of these two aspects of eCDM in respective use cases.

Copyright 2016 EMC Corporation. All rights reserved. 8

Enterprise Copy Data Management Fundamentals
Unlike traditional CDM solutions, eCDM will non-disruptively discover existing copies across
primary and protection storage to gain global oversight of what already exists in the
environment. Non-disruptive discovery maintains self service by enabling storage admins
and DBAs to continue creating copies from their native interfaces instead of inserting a
solution into the copy data path. However, the addition of global oversight on copy data
ensures that only the right number of copies are stored on the right tiers of storage.

Copyright 2016 EMC Corporation. All rights reserved. 9

Enterprise Copy Data Management Fundamentals
The core of eCDM is the user-defined service plans to monitor or proactively manage SLO
compliance. For example, admins can create service plans for each department – like
Finance, Accounting and HR - to define the service level that data requires. A customer can
then simply monitor compliance by verifying whether the defined service level objectives
are being met across the organization.

Alternatively, compliance management proactively ensures that all copy data is in

compliance with SLOs.

Copyright 2016 EMC Corporation. All rights reserved. 10

Enterprise Copy Data Management Fundamentals
This module covered the introduction of eCDM along with its use cases and benefits.

Copyright 2016 EMC Corporation. All rights reserved. 11

Enterprise Copy Data Management Fundamentals
This module focuses on eCDM key features and how they are used in an IT environment.

Copyright 2016 EMC Corporation. All rights reserved. 12

Enterprise Copy Data Management Fundamentals
eCDM runs as a virtual machine appliance on a VMware vSphere environment. It can be
deployed either through a vCenter server, or directly onto an ESXi host. This eCDM
appliance comes with all the necessary software and services installed.

In order to properly function, eCDM must be able to communicate with and manage the
storage systems and protectable assets within the environment. This means that in order to
interface with any VMAX, XtremIO, RecoverPoint, and Data Domain systems, it must have
IP connectivity and credentials to the those systems’ programmatic interfaces.

For example, to monitor and manage a Data Domain, eCDM needs access to the Data
Domain Management Center. To interface with VMAX, eCDM utilizes SMI-S Provider.
Because these programmatic interfaces are used to provide a source for eCDM’s inventory
of storage systems, they are all called Inventory Sources. eCDM can query these
inventory sources to discover any storage systems, protectable assets, and any other
information needed.

Copyright 2016 EMC Corporation. All rights reserved. 13

Enterprise Copy Data Management Fundamentals
The eCDM Appliance has many internal components that can be divided into three main
categories.

The core system of eCDM provides the main services. This includes creating and managing
various eCDM assets, inventory sources that are necessary in using eCDM. It also provides
a REST API server, license manager, and user interface.

eCDM also stores metadata within its internal catalog and media manager. These catalogs
are used to keep track of the various storage devices storage groups and consistency
groups. They also store the location and relationships between the copies of data.

The Protection components of the eCDM appliance interact between the eCDM appliance
and the other storage systems within the environment. This includes components, such as
the storage manager, workflow manager, and discovery service. These components are
used to discover information about each storage system, interface with them, and run
workflows to run actions on them.

Copyright 2016 EMC Corporation. All rights reserved. 14

Enterprise Copy Data Management Fundamentals
The eCDM eLicensing solution has three different types of licenses: the Trial license, the
Front-end Protected Capacity by Terabyte license, and the Appliance Key license.

When eCDM is first installed, a free 90 day trial license is automatically applied. This license
allows full use of the product for an unlimited amount of capacity. This license allows you to
be able to try the eCDM product and also to discover how much capacity you are likely to
use. If needed, you may extend the trial period an additional 30 days by applying an
emergency license. However, a permanent FETB or Appliance Key license must be applied
before the trial expires.

The Front-end Protected Capacity by Terabyte, or FETB license is a permanent license based
on the actual capacity that you need to protect. It allows full use of the product up to the
licensed capacity. Capacity is measured based only on the amount of front-end capacity
being protected. The FETB license is not dependent on the size of the LUN so it is not
impacted by thin provisioning of a LUN. Also, the capacity used by any copies are not
counted toward the front-end capacity. For example, if an Oracle database uses 5 TB of
capacity on a 15 TB thin provisioned LUN, and backups and other replicated copies use a
total of 100 TBs, the license only needs to be for 5 TBs - the actual capacity used by the
database. If needed, the amount of licensed capacity can be expanded.

The Appliance Key license is a permanent license that provides unlimited, full access to
eCDM with no capacity restrictions. Once an Appliance Key license is applied, eCDM can
function indefinitely.

Copyright 2016 EMC Corporation. All rights reserved. 15

Enterprise Copy Data Management Fundamentals
Before eCDM can manage any storage systems or assets, it must build an inventory of the
storage systems and assets in the environment. This process is called Discovery.

eCDM runs the discovery process by interrogating the inventory sources, such as Data
Domain Management Console, SMI-S Provider, XMS, or the RecoverPoint Cluster Manager.
This allows it to determine what storage systems exist and what resources exist on them
that can be protected. This includes copies of LUNs, VMAX Storage Groups, and XtremIO
Consistency Groups. Data about these systems and storage devices populates the metadata
components in the eCDM appliance so that it can keep track of these assets.

When a new inventory source is added to eCDM, it will automatically run a basic discovery
process on that inventory source to discover its storage arrays. A deeper level of discovery
can also be run on demand to discover storage within the array and to discover if any new
storage arrays have been added.

Copyright 2016 EMC Corporation. All rights reserved. 16

Enterprise Copy Data Management Fundamentals
When eCDM runs a discovery, it will find the storage systems within the environment.

VMAX, VMAX All Flash, and XtremIO systems are categorized as Storage Assets since they
are used as primary storage for the servers and applications in the environment. eCDM will
discover information about these storage systems, and also the storage and consistency
groups stored on them.

Data Domain systems are typically used to store copies of data for protection, so they are
categorized as Protection Storage Assets. A Protection Storage Asset can either be an entire
Data Domain system, a Data Domain MTree that is a vDisk pool, or a RecoverPoint Cluster.
eCDM discovers information about the Data Domain systems, along with any copied data
residing on them.

Copyright 2016 EMC Corporation. All rights reserved. 17

Enterprise Copy Data Management Fundamentals
Storage assets, such as VMAX and XtremIO, contain application data and storage groups
that hold that data. These are the primary resources that are going to be protected, so they
are called Protectable Assets. Protectable Assets include VMAX Storage Groups and
XtremIO Consistency Groups. VMAX Storage Groups are a collection of logical volumes that
are used by an application, server, or a collection of servers to present storage to hosts.
XtremIO Consistency Groups are configured on the XtremIO system to replicate source
LUNs to Data Domain static images. eCDM will detect any storage or consistency groups
during the discovery process and list them as protectable assets.

Both storage and consistency groups can also be combined into user definable Custom
Groups to provide further efficiency in management.

Copyright 2016 EMC Corporation. All rights reserved. 18

Enterprise Copy Data Management Fundamentals
Each protectable asset will likely have been copied, either within the storage array itself, to
a separate storage array, or to a Data Domain system. eCDM tracks these copies as Point in
Time Copies, or PITs. eCDM will not only keep track of the location of each point in time
copy, but also keep track of the relationship between the copies and their original
protectable asset. This gives you greater visibility into all the copies throughout the
environment.

Copyright 2016 EMC Corporation. All rights reserved. 19

Enterprise Copy Data Management Fundamentals
Copyright 2016 EMC Corporation. All rights reserved. 20
Enterprise Copy Data Management Fundamentals
It is not enough to simply track and monitor the location of existing copies. We also want to
be able to ensure that the right amount of copies are created and kept in the right locations
for the right amount of time. In other words, we want to ensure that service levels are
being met.

eCDM does this through the use of protection plans. Protection plans define sets of
objectives that will apply to protectable assets for their configured periods of time. For
example, you could define a protection plan that will ensure there are always at least 6
point in time copies of an asset available from the last three days, and that they are spaced
no more than 12 hours apart. The protection plan could also specify what type of storage
the copies must reside on.

Copyright 2016 EMC Corporation. All rights reserved. 21

Enterprise Copy Data Management Fundamentals
Protection plans ensure that service level objectives are being met. There are a number of
different service level objectives that can be configured in an eCDM protection plan.

A Recovery Point objective will set the maximum amount of time that is allowed to elapse
between protection copies. For example, setting a Recovery Point of 6 hours will ensure
that a point in time copy is made at least every 6 hours.

A Storage Class objective will ensure that protection copies are stored on the proper type
of storage. The Storage Class can either be set to Primary, meaning a top level storage
array such as VMAX or XtremIO, or Protection, meaning a Data Domain.

The Data Consistency objective specifies whether the copies are Application consistent or
Crash consistent. An application consistent copy will first ensure that the application data is
in a consistent state, while a crash consistent backup does not. An application consistent
copy can only be created using DD Boost for Enterprise Applications software in order to
interface with the application.

A Retention objective will ensure that protection copies have a minimum specified
retention period. For example, setting a retention objective to 2 months will ensure that
copies will not expire until 2 months from when they were created.

The Maximum Copies and Minimum Copies objectives will ensure that the total number
of protection copies for a protectable asset fall within the specified range. These objectives
are useful for ensuring that enough copies are made, but not so much that they use up
valuable storage space.

All of these service level objectives can be used in combination.

Copyright 2016 EMC Corporation. All rights reserved. 22

Enterprise Copy Data Management Fundamentals
When creating a protection plan, you need to define a time period for which the service
level objectives are applied. Simply providing an objective of, for example, a minimum of 3
copies without specifying a time frame would not be very useful. Should an old copy from a
year ago or more satisfy this objective? This is probably not what the administrator is
intending.

A protection plan will have one or more stages in order to define a time period for the
service level objectives to be applied. The time period of a stage always refers to a time
relative to the current date. For example, a stage could be created to apply service level
objectives for the past 5 days. This would create a 5 day rolling time window so that the
objectives must be satisfied for the past 5 days. Note that the stage does not expire after 5
days - it remains active for the lifetime of the protection plan, but always refers to the 5
days before the present day.

Multiple stages can be added to a protection plan so that different service level objectives
can be applied to different time periods. This is very helpful in creating protection plans that
offer stringent service levels for more recent data, and more relaxed service levels of older
data. Multiple stages can also apply to the same time period to allow service level
agreements to be applied more flexibly. For example, two stages could apply to the same
time period - one to check how many copies reside on primary storage, and another to
check how many reside on protection storage.

Copyright 2016 EMC Corporation. All rights reserved. 23

Enterprise Copy Data Management Fundamentals
Let’s put these concepts together to see what a protection plan might look like.

Imagine that we want to ensure the protection of an Oracle database that has a high initial
RPO. It requires copies to be available for the last 2 days which are each taken 12 hours
apart. However, after those 2 days, the businesses recovery point objective drops and only
one daily copy is needed. No copies are required after a total of 6 days.

A protection plan for these requirements would have two stages: one for the high RPO
period, and one for the low RPO period. The first stage would be set to go from 1 to 2 days
ago, and be configured with a recovery point objective of 12 hours. The second stage would
be set to apply from 3 to 6 days ago, and be configured with a recovery point objective of 1
day.

As time goes on, this protection plan would ensure that, during the first stage, copies exist
no more than 12 hours apart. Once those copies enter the second stage time period, some
of them would become candidates for removal. But the protection plan will ensure that the
maximum time between two copies is not more than the recovery point objective of one
day. Eventually, copies that no longer fall within any of the stage’s time periods no not need
to be retained.

Copyright 2016 EMC Corporation. All rights reserved. 24

Enterprise Copy Data Management Fundamentals
eCDM also allows the creation of tenants. Tenants are organizational structures that allow
you to logically separate assets and protection plans into different units. For example, you
may want a certain protection plan to only be available for some protectable assets, but not
others. To do this, you would create a tenant that would contain that protection plan and
those protectable assets. All other assets and protection plans would be assigned to
different tenants.

Each eCDM has one System Tenant. This tenant is the root tenant of all others, which are
sub-tenants. The System Tenant can manage all the sub-tenants.

Users can be assigned within the System Tenant and granted various roles. These Roles
allow the users various levels of access to eCDM.

Copyright 2016 EMC Corporation. All rights reserved. 25

Enterprise Copy Data Management Fundamentals
This module covered eCDM key features and how they are used in an IT environment.

Copyright 2016 EMC Corporation. All rights reserved. 26

Enterprise Copy Data Management Fundamentals
This module focuses on administration and management of eCDM. We will deploy,
examine, and provide practical examples of eCDM in action.

Copyright 2016 EMC Corporation. All rights reserved. 27

Enterprise Copy Data Management Fundamentals
This lesson covers the requirements for eCDM deployment and an overview of the
installation process.

Copyright 2016 EMC Corporation. All rights reserved. 28

Enterprise Copy Data Management Fundamentals
eCDM is packaged in the open virtual appliance/application or .ova format. The required
.ova file is obtained from the support.emc.com web site. The benefit of using the .ova
format is that most virtual machine information and specifications are pre-configured for
the installation process so the operator does not to define them. The pre-configured
resources include the operating system, CPU, memory, disk space requirements. These
requirements need to be validated prior to deployment.

eCDM is deployed in a VMware environment by either using vCenter or installing it directly

on an ESXi host that is version 5.5 or higher. When deploying the .ova file, there are a few
variables which the operator must define such as the IP address and datastore location.
Once this basic information is provided, the eCDM appliance is deployed.

Copyright 2016 EMC Corporation. All rights reserved. 29

Enterprise Copy Data Management Fundamentals
After the eCDM virtual machine has been deployed and powered on, you are ready to
perform the initial setup which consists of six easy steps. In step 1, the process starts by
using a supported web browser and connecting to the IP address you defined during the
installation. In step 2, you will read the license agreement and accept it.

Copyright 2016 EMC Corporation. All rights reserved. 30

Enterprise Copy Data Management Fundamentals
Step 3 is to determine the install type which can be either new or a restoration of a backup
copy. As eCDM is new to the environment, we will select the new install option. The other
option, Recover from Backup is for disaster recovery. Step 4 is to set the default password
for the OS accounts which must meet complexity requirements. Note that this configures
the OS passwords, but not the default GUI password. In step 5, we need to select the
appropriate time zone. Finally in step 6, we need to define a name the default System
Tenant.

Copyright 2016 EMC Corporation. All rights reserved. 31

Enterprise Copy Data Management Fundamentals
When the install finalizes, you will automatically be redirected to the eCDM dashboard and
you are now ready to begin.

Copyright 2016 EMC Corporation. All rights reserved. 32

Enterprise Copy Data Management Fundamentals
This lesson covers an exploration of eCDM by defining and explaining the information that it
provides from the graphical user interface.

Copyright 2016 EMC Corporation. All rights reserved. 33

Enterprise Copy Data Management Fundamentals
Using the eCDM GUI is a straight forward process. The menu icon located in upper right
hand side is the primary method used to navigate between functional locations.

By selecting the upper menu icon, the operator simply selects the desired section they
would like to navigate to. Each of these selections will be shown in more detail.

Copyright 2016 EMC Corporation. All rights reserved. 34

Enterprise Copy Data Management Fundamentals
While examining the eCDM dashboard for the first time, you are presented with the default
view. Here, you will customize this dashboard. There are four main displays that can be
altered by expanding views, adding widgets, and adjusting the presentation order. The
information displayed will vary depending on existing configuration. In this example, only
the initial setup has been performed.

Copyright 2016 EMC Corporation. All rights reserved. 35

Enterprise Copy Data Management Fundamentals
When eCDM is first deployed, inventory sources will need to be added. It is these inventory
sources that will give eCDM access to the various storage assets and protection storage
assets. eCDM is designed for cloud infrastructure so it is an expectation that many
inventory sources may need to be added to the configuration. As long as you have the
required information, like hostnames, IP address, and authorized usernames and
passwords, the discovery process is simple. This task is not required to be performed by
the inventory source owner, but they should be aware of the role that eCDM will play.

Copyright 2016 EMC Corporation. All rights reserved. 36

Enterprise Copy Data Management Fundamentals
Inside the Tenant Management section, you can create, delete, and edit tenants. A tenant
consists of five sections. If you examine a tenant, you can adjust the characteristics. The
profile contains the name and a description of the tenant. Users can be assigned to the
tenant to allow new logins. Users can either be authenticated internally by eCDM or
optionally through an LDAP authentication system. The only other items that require
definition are the protectable assets, which define which protectable assets are available to
the tenant, and protection storage assets, which define which protection storage assets are
available to the tenant. This allows a self-service model in which landlord controls tenant
access to services and security.

Copyright 2016 EMC Corporation. All rights reserved. 37

Enterprise Copy Data Management Fundamentals
Initially, when you navigate to the assets section of the GUI, you will notice there are no
objects. If you adjusted the settings and added inventory sources they would appear in the
assets section of the GUI as seen above. There are four primary classes of assets
presented as seen on the left. These include: protectable assets, storage assets, protection
storage assets, and custom groups. Selecting the asset type, provides additional
information such as usage summary of all assets of this type and individual asset
information. Depending on the asset selected, you will also be able to filter the results.
This can be extremely useful in large environments.

Copyright 2016 EMC Corporation. All rights reserved. 38

Enterprise Copy Data Management Fundamentals
After selecting any protectable asset, you can view the details of that asset. This will
provide granular information that includes all the point in time copies available for that
asset when they were created and some information about them. The details view also
shows protection plan and compliance status so that you can see whether the asset is being
properly protected. Here we see that the asset is has not been assigned to a protection
plan. The asset details also shows a graphical view of inventory source relationships.

Copyright 2016 EMC Corporation. All rights reserved. 39

Enterprise Copy Data Management Fundamentals
This lesson covers integration and implementation topics related to eCDM. We will explain
some common task and situations you will be presented with when using eCDM in a
production environment.

Copyright 2016 EMC Corporation. All rights reserved. 40

Enterprise Copy Data Management Fundamentals
The Protection Plans section shows the existing protection plans and allows you to create
new ones. Protection plans can be active, inactive, or suspended.

An inactive plan is not available to tenants and can still be edited. Once a plan is activated,
it is available to tenants and may be assigned to protect assets. When a plan has tenants
assigned to it, it cannot be deactivated until those tenants are removed, since the purpose
of an inactive plan is for it to be unavailable to tenants. However, the plan can be
suspended which will suspend its activity, validation, and protection actions.

Copyright 2016 EMC Corporation. All rights reserved. 41

Enterprise Copy Data Management Fundamentals
When creating a protection plan, you will be guided through a wizard in which you will
define at least one stage. The stage defines a time period and a set of service level
objectives. The time period is defined by a start and end time which form a rolling window
in time that looks back from “now.” For example, a stage that starts on day 1 and ends on
day 10 would be looking back at the last 10 days. On the other hand, a stage that starts on
day 7 and ends on day 8 would refer to a two day period from 7 days before now.

In addition to specifying a time period, a stage will define a set of objectives. There are six
options for setting objectives. These options were covered earlier in the course. By
combining the different objectives, various service level objectives can be created.

Copyright 2016 EMC Corporation. All rights reserved. 42

Enterprise Copy Data Management Fundamentals
In complex environments, an individual asset may have many Service Level Objectives
(SLO). In addition, SLOs have different inventory asset requirements. Examining the chart
above, the operator can configure the stage required to determine and achieve one or more
SLOs based on the configuration. Using the proper stage, the operator can create
protection plans as simple or complex as the situation requires.

Copyright 2016 EMC Corporation. All rights reserved. 43

Enterprise Copy Data Management Fundamentals
If a production volume were to fail or become corrupt, you may need to recover that
volume. eCDM has the ability to initiate recoveries of point-in-time copies.

This is done by selecting a point-in-time copy from the assets section and starting the
recovery wizard. You will have the option of exporting the copy to a target destination,
recovering it to an alternate location, or rolling back to the original production location.
Exporting for reuse and recovering to an alternate location are useful for testing use cases,
while the rollback option is commonly used for disaster recovery. Performing a rollback to
the production will cause the original data to be overwritten, so this option should be used
with care.

Copyright 2016 EMC Corporation. All rights reserved. 44

Enterprise Copy Data Management Fundamentals
Copyright 2016 EMC Corporation. All rights reserved. 45
Enterprise Copy Data Management Fundamentals
Additional support is available for eCDM within the EMC ecosystem. Please take a moment
to familiarize yourself with some of them.

Copyright 2016 EMC Corporation. All rights reserved. 46

Enterprise Copy Data Management Fundamentals
This module covered eCDM deployment, management options, and administration.

Copyright 2016 EMC Corporation. All rights reserved. 47

Enterprise Copy Data Management Fundamentals
This course covered an introduction to Enterprise Copy Data Management (eCDM). It
included an overview of the eCDM architecture, features and functionality. Additionally, it
included a review of basic troubleshooting, best practices as well as where to find additional
information.

Copyright 2016 EMC Corporation. All rights reserved. 48

Enterprise Copy Data Management Fundamentals