Data Domain Extended Retention Installation, Configuration and Administration - MR-1WP-DDEXRET SRG

Welcome to the Data Domain Extended Retention: Installation, Configuration and
Administration course.
Copyright ©2015 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, 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.
Revision Date: August 2015
Revision Number: MR‐1WP‐DDEXRET.DDOS5.5.2
Copyright 2015 EMC Corporation. All rights reserved. Data Domain Extended Retention 1
This course covers the features, benefits, and architecture of the Data Domain Extended
Retention software. This course is meant for any support professionals, field installation
personnel, storage administrators, or implementation engineers responsible for maintaining
a Data Domain system with Extended Retention.
This module covers DD Extended Retention as a solution, features and benefits, system
architecture, hardware options, licensing requirements, and common use cases.
This lesson covers the need for long term retention of backup data, challenges of tape, and
the data domain extended retention software.
There are several reasons why businesses keep certain sets of backup data for very long
periods of time, 7 years, 30 years, or even longer. For example, a corporation or
institution might need to comply with company governance policies, industry requirements,
legal mandates, and so on. Preserving intellectual property would be another motivation.
The most common approach that businesses use to perform backup retention is to put
select copies of backup images, weekly fulls or monthly fulls off to tape, and then keep it
onsite or offsite to meet the retention requirements. Tape is still a common solution for
long-term retention of backup data. Data storage, specifically long-term backup storage, is
one of the last holdouts for tape media.
Tape is still common in data centers due to the perceived economic advantages. Tape
cartridges are inexpensive, but they make up just a small fraction of the total cost of
ownership. Tape automation, transport and storage space are expensive and ongoing. This
is particularly true when upgrading and replacing large tape libraries. Also, companies
expend significant resources to manage the tape infrastructure that could otherwise be
creating business value.
Additionally, there are significant operational challenges with tape infrastructure. Accessing
a retained file stored on tape takes a significant amount of time, especially if it is offsite. In
addition, the measured failure rate for restoring data from tapes is relatively high. Also,
offline tapes do not provide search-ability and online information access. Finally, the risk of
theft from data on tapes during transportation also poses serious security challenges.
Data Domain has made very significant inroads in eliminating tape as the preferred media
for short-term backups for disaster recovery, but for long-term retention and despite all of
its shortcomings, tape is still the more common media.
Data Domain Extended Retention software enables long-term backup retention on Data
Domain systems without the need for tape.
Data Domain Extended Retention is a software option on supported Data Domain systems.
Data Domain Extended Retention software transparently incorporates two tiers of storage
on a Data Domain system to achieve cost-effective scalability while delivering the high
throughput required to ingest hundreds of terabytes of backup data.
With DD Extended Retention Software, Data Domain systems are now positioned to provide
cost-effective long-term backup retention and completely eliminate tape from the
infrastructure.
This lesson covers Extended Retention features and benefits, VTL protocol support, and
replication flexibility.
This a quick review of the benefits a DD Extended Retention platform delivers.
These systems provide Multi-tiered storage, with cost optimization for long term storage,
while leveraging standard Data Domain system advantages, including high throughput
deduplication.
VTL is supported with DD Extended Retention software. This includes Open Systems and
IBM i for all supported backup applications, with simultaneous CIFS, NFS, DD Boost and VTL
support.
Note that NDMP Tape Server is not supported on Data Domain systems with DD Extended
Retention.
MTree replication is supported between two DD systems with DD Extended Retention
software in the active tier, with the conditions shown here.
This lesson covers Data Domain Extended Retention Overview, Data Movement to the
Retention Tier, and Single File System with a Scalable Namespace.
This topic presents the basic architecture enabling its unique capabilities of the DD
Extended Retention Software on a Data Domain system.
Data Domain Extended Retention software transparently incorporates two tiers of storage
on a Data Domain system to achieve cost-effective scalability. Data initially lands in the
active tier of the Data Domain system that is optimized to deliver the high throughput
required to ingest hundreds of terabytes of backup data retained for operational recovery.
With DD Extended Retention software, the Data Domain system transparently incorporates
a very large second tier of storage, namely the retention tier, that is optimized for the long-
term backup retention.
A periodic process, configured as a policy, moves aging data out of the active tier and into
the retention tier. It continues to do this until the retention unit is full.
One unique property of this architecture is that when full, the unit is sealed for fault
isolation. The retention unit becomes a completely self-contained unit of data preservation.
The active tier holds the short-term data for disaster recovery purposes, while the retention
tier holds static long-term backup data. This separation of data types is what allows the
impressive scalability of the retention tier, while still keeping the performance required for
the active tier. With the scalability of the retention tier, the average cost of the system per
gigabyte becomes lower and lower as the system scales, making Data Domain systems very
cost-effective at scale.
Now let’s look at how an administrator would configure the Data Domain system enabled
with DD Extended Retention software.
The administrator can configure the data movement policy that moves data from the active
tier to the retention tier. This policy is configured for every use case or data stream coming
into the Data Domain system. This policy is based on the last-modified time of every file
stored in the system and frequency of data movement.
When the policy is enforced, data is moved out of the active tier, and into the retention unit
(the unit that is marked as “ready target”). Note that each file is only moved once. There is
no need for files to be moved again. This out-of-band data movement process capitalizes on
more capacity-optimized compression algorithms, so that data that is moved out of the
active tier is recompressed and packed more tightly into the retention tier as it is moved.
The data movement process can be scheduled to run at a specified time; it can be stopped,
restarted, or throttled.
A Data Domain system enabled with DD Extended Retention software presents one large,
scalable file system. The file system simply looks like a much larger Data Domain system to
end users and applications.
Of course, this file system can be completely or partially exposed as CIFS shares (for
Windows), NFS mount points (for UNIX/Linux), VTL for open systems and IBM i and through
DD Boost for backup applications.
An important point to note is that all incoming data is initially stored in the active tier, and
it can land very fast. Data can also be read from each tier without any read performance
degradation, except when the system approaches its maximum capacity. Data Domain
systems enabled with DD Extended Retention provide between 2 to 4 times the scalability
of an equivalent Data Domain system without the DD Extended Retention software option.
However, one trade-off for this capacity is that some of the data in the retention unit may
not be readily available in the memory of the controller. This data could be swapped out of
memory, creating a slight delay in accessing. The delay can be a matter of seconds.
By contrast, recalling a tape into a tape library can take hours or days, compared with a
rare, low-probability, less-than-a-minute delay in accessing the data in the retention units
of a Data Domain system.
Because the Data Domain systems is designed as a storage of last resort – in other words,
a petabyte-scale system that is the last stop for all data when it comes to protection and
retention — the Data Domain system with DD Extended Retention feature also provides
data integrity features and fault isolation capabilities that ensure long-term data access and
recoverability.
The system is protected by RAID 6 functionality that enables the system to withstand dual
disk failures without interruption. Additionally, Data Domain’s Data Invulnerability
Architecture continuously scrubs all stored data, checking data integrity and preventing
long-term deterioration from ever affecting the fidelity of stored data.
Another unique feature that Data Domain system with DD Extended Retention software
provides is the fault isolation of retention units. Specifically, when a retention unit gets full,
it is sealed off and no new data is written to this unit. The sealed retention unit becomes a
self-contained system to ensure long-term data preservation.
If the Data Domain system experiences an issue where the retention unit is unavailable, the
system continues to operate with all unaffected components. Most other storage systems
experiencing this kind of major component failure beyond a RAID group would be
completely unavailable and the customer would likely be experiencing partial or total data
loss. In the case of the Data Domain system with DD Extended Retention, the system is up
and available, and all unaffected data is accessible.
At this point, one of three things can happen:

• If it’s a minor failure (cable, connector, fan, etc.), the devices can be reconnected or
fixed, and the retention unit would simply come back online.
• If it’s a failure where the retention unit is no longer usable, a new unit can be seeded
in the remote site and sent back.
• If the retention unit is completely lost, and no secondary disaster recovery system is
present, the file system can be removed and the system can continue to operate
beyond the fault.
Fault isolation goes even further. If this catastrophe is larger in scope, and most of the
system is affected a secondary replica can be plugged into a brand new Data Domain
system and all data that survived the disaster and was salvaged will be available in the new
system.
This lesson covers Supported Platforms, DD Extended Retention Software System
Capacities, and DD990 versus DD880 Specifications.
The DD Extended Retention software option is available on the hardware platforms shown in
this table.
ES20s and ES30s provide various storage capacities depending on configuration.
These are the capacities and memory requirements of the supported systems as of the DD
OS 5.5.2 release. For the very latest information regarding supported systems and
capacities, visit the product pages at EMC.com, or search the Data Domain support site.
• Product pages and data sheets are available at:
http://www.emc.com/backup-and-recovery/data-domain/data-domain.htm#!software
• Support resources:
https://support.emc.com/products/
This lesson covers Extended Retention Software Option, Shelf Capacity Licensing
Requirements, Expanded Storage Licensing Requirements, and DD Retention Lock with
Extended Retention.
There are three licenses required to properly configure and enable a Data Domain system
with DD Extended Retention.
The first is the DD Extended Retention software option. This license enables the software
features and functionality for this type of configuration.
Two additional types of licensing are required to enable the hardware storage architecture
of the system, based on the system configuration.
There are also optional licenses concerning the locking of files for added security.
The licenses can be viewed or added using the System Manager. Within the System
Manager, open the System Settings and then the Licenses tab.
The appropriate shelf capacity license is required for each new shelf added.
The shelf capacity license:

• Enables customer to incrementally add storage capacity.
• Not supported with systems running DD OS 5.0 and below.
• One license issued for each new shelf purchased (ES30 + ES20).
• Shelf capacity license differs for active and extended retention tiers with DD Extended
Retention.
• ES20s purchased prior to DD OS 5.1 are grandfathered (no license).
The license is specific to an active or an retention tier shelf and some differences remain
between DD OS releases. Take a minute to review the table to understand these differences
before proceeding.
The expanded-storage license allows for the upgrade of storage capacity for Data Domain
systems.
An Expanded-Storage license is required to expand the active tier storage above the entry-
level capacity, depending on the controller model.
For example, a DD860 with the DD Extended Retention software option provides an entry-
level capacity of 64 TB. This can be expanded to 142 TB by applying an expanded storage
license.
A DD990 with the DD Extended Retention software option provides an entry-level capacity
of 144 TB. This can be expanded to 570 TB by applying an expanded storage license.
An Expanded-Storage license also enables the upgrade of a 7-disk DD160/DD620/DD640 to

12 disks.
DD Retention Lock Compliance Software Edition is a software offering enabling users to
apply strict retention requirements on archive data per the data regulation standards such
as SEC Rule 17a-4(f).
The DD Retention Lock Compliance Software Edition is available on all Data Domain
platforms except GDA, and co-exists with backup data and applies different retention
periods for different types of archive data.
DD Retention Lock Compliance licensing preserves archive data in a non-rewritable, non-
erasable format. It involves a dual sign-on mechanism, which requires a Security Officer to
also sign-on to complete certain administrative actions. It also has a Secure Clock which
prevents any data locked with the Retention Lock Compliance license from being altered,
mutilated, or destroyed. Once Retention Lock Compliance is enabled it can not be disabled.
There is Audit Logging, and also Granular Compliance capabilities which allows
administrators to activate on an MTree to enable compliance on a portion of the system,
with replication support via collection replication only.
If DD Retention Lock Compliance is enabled on a system, then as part of the compliance

requirements, it is necessary to have a secondary copy of the locked data on the
destination Data Domain system. For replication, both systems need to have DD Retention
Lock Compliance enabled.
Data Domain Retention Lock Governance Software Edition is the option to use when your
retention locking needs are not as stringent as complying with federal regulations and
standards such as SEC 17a-4f.
This lesson covers Customer Profile and two use cases.
A typical customer profile for the DD Extended Retention solution might include the
characteristics shown here.
The main use case for Data Domain Extended Retention software is long-term retention of
backups with backup directly to the Data Domain system.
Data Domain systems allow easy integration using CIFS, NFS, VTL or DD Boost into existing
environments and supports all leading backup applications - including EMC NetWorker,
Symantec NetBackup, IBM TSM and others.
By setting the Active tier to be large, the Data Domain system can store short-term backup
data for disaster recovery purposes. The active tier needs to be sized for short-term
disaster recovery. The retention Tier would be sized based on the retention policy.
Optionally, the configuration might include a Data Domain system at a secondary site for
disaster recovery purposes.
In this use case, the Data Domain system with DD Extended Retention software can be
used as an aggregation of long-term backups coming from other Data Domain systems in
remote sites. Depending on how much data is coming in, the Active Tier may not need to
be as big as it would when backing up directly to the system. Leveraging DD Boost
software, the complexity of replicating data between systems and implementing different
retention periods on the replica can be eliminated and all management would be done from
the backup application hosting the DD Boost functionality.
Optionally, there could be a Data Domain system in the second site for disaster recovery
purposes.
This module covered DD Extended Retention as a solution, features and benefits, basic
system architecture, hardware options, licensing requirements, and use cases.
This module covers how to describe basic installation and configuration steps, cable
systems with extended retention, configure the active tier, add an archive tier, and
configure data movement.
Installation and configuration of Data Domain systems with Extended Retention follows the
same high-level workflow as with all other Data Domain systems. There are six basic steps:
1. Install hardware
2. Define the Data Domain system information for your site
3. Perform initial system configuration
4. Configure the system for data access
5. Configure optional software
6. Perform optional additional system configuration
This course focuses on details specific to DD Extended Retention as they affect the first step
(installing hardware) and the third step (performing initial configuration).
For more detailed information on all installation and configuration activities, refer to the
Installation and Setup Guides available at the Data Domain support site, or enroll in the
EMC Data Domain System Installation course available from EMC Education Services.
This lesson covers HBA to Shelf Cabling Rules: HBA Ports, Adding Shelves, and Cable
Lengths, and DD Extended Retention Schematic: 25-56 Shelves.
This slide provides review of the cabling rules, using the example of a DD990 with DD
Extended Retention software option, which supports up to five Racks, with up to 56 ES30
Shelves arranged in eight strings, at seven shelves per string.
On the DD990, the SAS HBA ports are located in slots 4, 5, 8, and 9 of the DD990
controller.
PCI slot 8 is populated with the fourth SAS HBA supporting the DD Extended Retention
configuration.
The ES30 shelves use these markings to indicate a HOST port and an EXP’N port.
The cabling and racking are designed so that shelves are added from the bottom up in a
rack.
Cabling between adjacent shelves in a string is done with the 1 meter SAS cables that are
delivered with the shelves.
One cable runs from the B Controller EXPANSION port of the lower shelf to the B controller
HOST port of the next higher shelf in the string.
Then a second cable runs from the A Controller HOST port of lower shelf to the A controller
EXPANSION port of the next higher shelf.
When adding shelves to an existing string, the cable is moved from the B controller HOST
port to the new shelf. Then another 1 meter cable is added shelf-to-shelf.
The shelves are labeled Vn.m, where V is volume numbered with “n” as the number of the
string, and the “m” as the number of the shelf in the string. For example, V3.2 refers to the
second shelf in the third string.
Notice the cable length required for each HBA port to connect to the correct storage shelf
port. Beginning with the fourth string of expansion shelves, the required cable length
increases from 2 to 5 meters.
This lesson covers initial configuration of the active and archive tier, and configuration with
the System Manager.
Before you write data to a Data Domain system with DD Extended Retention, you need to
configure an active tier for the system. The active tier is analogous to a standard Data
Domain system and should be sized similarly. The maximum amount of storage that can be
added to the active tier depends on the DD controller used. This procedure is typically done
in the CLI.
1. Add the DD Extended Retention license.
# license add <license>
2. Enable DD Extended Retention by entering:
# archive enable
Each storage shelf requires a shelf capacity license. This license is specific for either active
or archive tier usage of the shelf. An expanded storage license to increase the size of the
active tier might also be required.
3. To add shelf capacity licenses, enter the license add command followed by one or
more license keys, separated with a space. For example: # license add
<license(s)>
4. Issue this command once for each enclosure that is to be added to the active tier:
# storage add tier active enclosure <enclosure id>
To create and enable the file system:
1. Create the file system.
# filesys create
2. Enable the file system.
# filesys enable
3. Verify that file system is up and running.
# filesys status
When the file system is up and running, the DD Extended Retention is ready to start
servicing read and write requests.
Next you add an Archive Tier. Each archive unit also is a fault-isolation domain.
To add an archive unit:

1. Issue this command for all enclosures to be added:
# storage add tier archive enclosure enclosure-id
2. Create an archive unit and add it to the file system.
# filesys archive unit add
3. Verify that the archive unit is created and added to the file system.
# filesys archive unit list all
This simulation covers the initial configuration of Extended Retention using the command
line interface.
Click the Launch button to view the video.
You can use the System Manager instead of administrative archive commands to perform
many configuration tasks. For example, you can add Shelf Capacity licenses and configure
storage, as well as create a two-tiered file system, configuring both the Active Tier and the
Retention Tier.
To add shelf capacity licenses:
1. Within the System Manager, Open the System Settings >Licenses tab.
2. Click Add Licenses.
3. Enter one or more licenses, one per line.
Note: If there are any errors, a summary of the added licenses and those not added
because of error are listed. Click Fix Errors and reenter the licenses keys. Click Add.
The licenses for the Data Domain system are displayed in two groups:
• Software option licenses, required for DD Extended Retention.
• Shelf Capacity Licenses, which displays shelf capacity in TiB, the shelf model, such as
ES30, and the shelf’s storage tier (active or archive).
To delete a license, select the license in the Licenses list and click Delete Selected Licenses.
If prompted to confirm, read the warning and click OK to proceed.
Additional storage requires the appropriate license or licenses, and the Data Domain system
must have enough installed memory to support it. Error messages display if more licenses
or memory is needed.
To configure storage:
1. Within the System Manager, Open the Hardware > Storage tab.
2. In the Overview tab, click Configure Storage.
3. In the Configure Storage tab, select the storage to be added from the Available
Storage list.
4. Select the appropriate Tier Configuration (Archive or Active) from the menu.
The two bars show the portion of licensed capacity used/remaining for each shelf model
(ES20 and ES30).
5. Select the check box for the Shelf to be added.
6. Click the Add to Tier button.
7. Click OK to add the storage.
To remove an added shelf, select it in the Tier Configuration list and click Remove from
Configuration. Click OK.
Follow these steps to create a new file system:
1. Add appropriate licenses as required.
2. Within the System Manager, Open the Data Management > File System tab.
3. Select Create file system from the More Tasks menu. Create file system is not
available as an option if a file system exists.
4. Storage is classified in tiers—either active tier or archive tier.
Select the type of file system to be created: either an archive capable file system
(the default), or a non-archive file system (to implement DD Extended Retention at
a later date).
5. Click Next.
6. Storage must be configured before the file system can be created. Click Configure in
the File System Create dialog box.
7. When the Configure Storage Status dialog box shows the disk enclosures addition
has completed, click Close.
8. Click Next to confirm.
9. Select the size of the first archive unit from the menu.
10. Click Next.
A Summary page shows the size of the active and archive tiers in the new file
system.
11. Click Finish to create the file system.
This simulation covers configuring Extended Retention with the System Manager.
This lesson covers the data movement policy, common sizing errors, cleaning and
snapshots, and configuring data movement.
System administrators can use the System Manager to configure the policy that guides data
movement from the active tier to the archive tier of a Data Domain system. Data
movement policies are managed on an MTree basis and only those files that meet the policy
threshold in that MTree are moved to the retention tier. If different datasets require
different data movement policies in the same DD Extended Retention system, they should
be placed in different MTrees.
The data movement policies are driven by two user-defined settings:

• A selected last modified time of a file (for example, 60 days)
• A periodic schedule for moving the data (for example, every week)
During the data movement process, files that satisfy the conditions of the data movement
policies are moved out of the active tier and into the retention tier.
This slide is an example of a data movement policy.
Create MTree A for the daily-incremental backups and create MTree B for the weekly fulls.
Set the age threshold for MTree A such that the data in MTree A is never moved. Then set
the age threshold for MTree B to two weeks. You should not set an aggressive migration
threshold for B, such as one day. At least one full backup from MTree B should always be
retained on the Active Tier to obtain good de-duplication and performance for the new
incoming backup.
Note: Ensure that the active tier is large enough to hold the data that is changing.
In this example, the data cannot be separated into MTrees A and B. The retention period of
daily-incremental backups is eight weeks and the retention period of weekly full backups is
three years. In this case, set the age threshold to nine weeks. If you set it lower, you would
be moving daily incremental data that is soon to be deleted.
Avoid these common sizing errors:
• Setting a data movement policy that is overly aggressive in which data is moved
too soon.
• Setting a data movement policy that is too conservative. Once the active tier fills
up, no more data can be written to the system.
• Defining an undersized active tier, such that the active tier fills up prematurely.
Caution: Creating an overly aggressive movement policy to compensate for an undersized

active tier. Space is not always reclaimed in the archive tier so moving files that are to be
deleted or updated soon into the archive tier results in wasted space. When a unit is sealed,
space can no longer be reclaimed until all of the data in the archive unit expires.
Cleaning is performed on the active tier either as scheduled, or by default immediately after
files have been moved from the active to the retention tier.
Files in snapshots are not cleaned, even after they have been moved to the archive tier.
The space cannot be reclaimed until the snapshots have been deleted. Set the retention for
snapshots to less than two weeks.
Data Movement Packing
Data is compacted in the target partition after every file migration. By default, this feature,
which is called data movement packing, is set to ON. When this feature is enabled, the
overall compression of the archive tier improves, but there is a slight increase in migration
time. To see if this feature is enabled, enter:
# archive show config
The output shows whether packing data during archive data movement is enabled or
disabled. Consult with a system engineer to disable data movement packing.
The space reclamation feature on the retention tier enables customers to recover space for
expired data on the retention tier, and allows the reclaimed space to be used for storing
new data. Space reclamation occurs as a background process that can be suspended,
paused, re-started and is applicable to data already stored on the retention tier.
To take advantage of the space reclamation feature, EMC recommends that you schedule
data movement and file system cleaning every two weeks. Also, update existing data
movement schedules to occur every two weeks. Before changing the data movement
schedule, provision storage in the active tier to hold one additional week of data. Schedule
cleaning to run after data movement completes. Do not schedule cleaning separately.
Both CLI and the System Manager provide capabilities to start, stop, suspend, or resume
the process and report high level detailed status.
Note that once started, Space Reclamation will run until stopped. Also, since Space
Reclamation is an intensive process that uses a lot of system resources, it may be
suspended from time to time by the system to accommodate higher priority processes.
To configure data movement:
1. In the System Manager, Go to Data Management > File System.
The File System page for a DD Extended Retention system shows the status of data
as it is moved from the active to the archive tier. The target unit in the archive tier is
the recipient of the data. The status includes when the data movement completed,
the number of files copied, and the amount of data copied in GB.
2. Clicking the Data Movement Status Start button starts the data movement based on
your defined data movement policy.
If cleaning is already in progress, starting the data movement schedules the data
movement to run after the clean completes.
3. The data movement status is shown in the File System tab. The Start button is
replaced by a Stop button.
4. Clicking Stop stops the data movement. Click OK in the Stop Data Movement dialog
box to confirm.
To configure data movement policy:

1. In the Data Management > File System tab, click the Configuration tab.
2. Under Data Movement Policy, click the Edit button.
3. In the Data Movement Policy dialog box, configure the parameters that require
customization. Otherwise, accept the defaults. You can set policies for:
– File Age Threshold
– Data Movement Schedule
– File System Cleaning
This simulation covers configuring Data Movement Policy.
Click the Launch button to start the simulation.
This module covered Basic installation and configuration steps, cabling systems with
Extended Retention, configuring the Active Tier, configuring the Archive Tier, and
configuring Data Movement.
This module covers Data Domain Extended Retention upgrade requirements and
procedures.
This lesson covers general requirements, caveats and restrictions.
DD Extended Retention Software can be enabled on already deployed systems.
For more detailed information on the procedures, see documentation on the Data Domain
support portal.
These are the general requirements for adding DD Extended Retention software option to
an existing system.
• The controller must be a supported controller.
• Must be DD OS 5.2 or greater.
• Extra SAS cards on the controller might be required for connectivity.
• Ensure that the memory requirements are met.
There are several caveats and restrictions when upgrading an existing system to include the
DD Extended Retention software option.
A Data Domain system enabled with DD Extended Retention software CANNOT be a source
of directory replication.
If you want to add DD Extended Retention software on a Data Domain system using
directory replication, then the system has to be changed to use a supported replication
method.
Encryption at rest, NDMP Tape Server and Data Shredding (Sanitization) features are NOT
supported on DD systems with DD Extended Retention software. Users who want to
convert an existing Data Domain system to a system with the Extended Retention software
option can cause file system disruptions if they do not completely prepare the system for
the Extended Retention services. It is not sufficient to disable encryption prior to installing
the Extended Retention license. If encryption was ever enabled on the Data Domain system
that will be converted to an Extended Retention system, contact your contracted EMC Data
Domain support provider for detailed instructions and removing encryption to prepare an
existing Data Domain system to operate with the Extended Retention software option.
Once DD Extended Retention is enabled on a Data Domain system, it CAN ONLY be disabled
after data migration off of the system and file system destruction.
This lesson covers how to convert a Data Domain file system to a file system with the DD
Extended Retention Software option, and Upgrading a DD Controller with DD Extended
Retention.
To convert a Data Domain file system to a file system with the DD Extended Retention
software option, follow these steps:
1. Ensure that the correct license is applied. Go to System Settings and check the
Feature list for the DD Extended Retention license.
2. Within the System Manager, Go to Data Management > File System.
3. From the More Tasks menu, select Enable DD Extended Retention. The Enable EE
Extended Retention menu option is available only if the file system has not already
been configured for Extended Retention.
a. If the file system is already enabled (as a non-Extended Retention file system),
you are prompted to disable it. Click Disable to do so.
b. If prompted to confirm that you want to convert the file system for use by DD
Extended Retention, click OK. After a file system is converted into an Extended
Retention file system, the file system page is refreshed to include information
about both tiers, and there is a new tab labeled Retention Units.
4. Go to Data Management > File System > Summary. Verify Space Usage summary
that the compression statistics for the Active and Retention tiers.
5. Verify that there is an Retention Units tab.
When upgrading a DD Controller with DD Extended Retention software option enabled, the
upgrade policy is the same as for a standard Data Domain controller. Upgrading from up to
two major prior releases is supported. The upgrade process is initiated by the following
command where file specifies a .rpm in the /ddvar/releases directory:
# system upgrade <file.rpm>
The process proceeds to upgrade the active tier and all available retention units, and puts
the system into the state that the previous upgrade has not been verified to be complete.
This state is cleared by the file system after the file system is enabled and has verified that
all retention units belonging to the file system have been upgraded. A subsequent upgrade
is not permitted until this state is cleared.
If the active tier is not available, the upgrade process upgrades the system chassis and
places it into the state where it is ready to create or accept a file system.
If a retention unit becomes available after the upgrade process has finished, the unit is
automatically upgraded when it is plugged into the system, or at the next system start.
This module covered upgrade requirements and procedures.
This module covers how to perform common administrative tasks, describe replication types
with DD Extended Retention, and describe disaster recovery options with Extended
Retention.
This lesson covers an Overview of Administrative Tasks, and a practice simulation on
common administrative tasks.
Administrators can perform a number of common tasks involved in maintaining a Data
Domain system with the Extended Retention software option. You perform these tasks in
the System Manager, under Data Management > File System.
Here you can do the following:

• Modify the data movement policy settings.
• Expand a retention or active tier
• Expand a retention unit
• Change retention tier compression
• Delete an retention unit
You can also reuse a retention unit. If all of the files on a retention unit are no longer
needed, deleting them makes the unit available for reuse. You can generate a file location
report to make sure that the retention unit is indeed empty, delete the retention unit, then
add it as a new retention unit.
This simulation covers how to modify the Data Movement Policy.
This simulation covers some common administrative tasks for systems using extended
retention.
This lesson covers MTree Replication, DD Boost Managed File Replication, Collection
Replication, and Directory Replication.
This chart shows the basic topology for MTree replication with DD Extended Retention.
Note that a Data Domain System with DD Extended Retention license can be the
destination for MTree replication from any DD system.
Replication is supported starting with DD OS 5.2.
This enables you to protect the data within the active tier of one system by replicating it to
the active tier of another controller with DD Extended Retention.
Note that although you can use MTree replication to protect data for certain MTrees on a
controller with DD Extended Retention, data movement must not be configured for those
MTrees. This is applicable only for those MTrees that need to stay only in the active tier.
Bi-directional replication is supported between systems that have the DD Extended

Retention license. This is applicable for data written via CIFS, NFS and VTL.
This chart shows the basic topology for DD Boost managed file replication with DD Extended
Retention. With DD Boost managed file replication, supported topologies are one-to-one,
many-to-one, bi-directional, one-to-many, and cascaded.
Note that with DD Boost 2.3 or later you can specify how multiple copies are to be made
and managed within the backup application.
This chart shows the basic topology for collection replication with DD Extended Retention.
Collection replication takes place between corresponding active tier and retention tier. If the
active tier or retention tier at the source fails, the data can be copied from the
corresponding unit at the remote site onto a new unit, which is shipped to your site as a
replacement unit.
The requirements for setting up collection replication on systems with DD Extended
Retention are listed on this slide.
This chart shows the basic topology for directory replication with DD Extended Retention.
Take a moment to review the details before proceeding.
With directory replication, the system with DD Extended Retention is used as a replication
target and supports one-to-one and many-to-one topologies from any Data Domain system.
Note that DD Global Deduplication Array systems are not supported for directory
replication.
Requirements for directory replication on systems with DD Extended Retention are shown
here. Take a minute to review before proceeding.
To copy data into DD Extended Retention using directory replication:

1. Set up directory replication into a directory within /backup.
2. On the controller with DD Extended Retention enabled, perform a fast copy from
/backup into the target MTree. A fast copy ensures that data on a system with DD
Extended Retention is not deleted when the source data on the Data Domain
system, which has shorter retention, is deleted
3. Manage each MTree with per-MTree data movement policies.
Ingest the data in age-order (oldest data first) to maximize deduplication and to improve
performance.
This table presents supported configurations by protocol and retention requirements.
The DD Boost protocol is supported for both short and long term backup retention on the
source and destination systems using DD Boost managed file replication or collection
replication.
The CIFS, NFS, and VTL protocols are supported on the source and destination systems
with extended retention for both short and long term retention using collection replication
or MTree replication.
The CIFS, NFS, and VTL protocols are not supported for long term retention on only the
destination system.
This lesson covers disaster recovery configurations, granular collection replication, and
overall recovery strategy.
For customers needing a disaster recovery configuration to keep a second copy of all stored
data in a separate system that is protected from disasters and catastrophes in a remote
site, EMC Data Domain Replicator software provides simple, fast, robust WAN-based
disaster recovery for the enterprise. It offers numerous replication types and policies and
also supports a wide variety of topologies to meet the needs of various deployments.
A system with DD Extended Retention is equipped with tools to address failures in different
parts of the system.
If the active tier and the retention unit are lost and there is no replica available, contact
Data Domain Support for assistance.
A system with the DD Extended Retention software option is designed to remain available
to service read and write requests when a retention unit is lost. The file system may not
detect that a retention unit is lost until the file system restarts or tries to access data stored
in the retention unit. The latter circumstance may trigger a file system restart. After the file
system has detected that the retention unit is lost, it returns an error in response to
requests for data stored in that unit.
If the lost data cannot be recovered from a replica, Data Domain Support might be able to
clean up the system by deleting the lost retention unit and any files that reside fully or
partially in it.
In a failure situation, perform recovery actions in the order listed below.

• Restore connection between the system controller and storage.
• If the system controller is lost, replace it with a new system controller.
• If there is loss of data and a replica is available, try to recover the data from the
replica.
If a replica is not available, limit any loss of data by leveraging the fault isolation features of
the DD Extended Retention through Data Domain Support.
The new source must be configured as a DD Extended Retention system. The file system
must not be enabled on the new source until the archive unit has been added and
replication recovery has been initiated.
1. Install the replication license on the new source.
# license add replication-license-key
2. Reset the authentication key on the destination.
# replication reauth col://hostB
3. Reconfigure replication on both the new source and destination.
# replication add source col://hostC destination col://hostB
4. Initiate recovery on the new source. The file system must not have been enabled
on the new source before this step.
# replication recover col://hostB
5. Check the replication status.
# replication status
This module covered common administrative tasks, supported replication types, and
disaster recovery.
For more information, documentation, and knowledge base articles go to the EMC support
portal.
For further study, and additional training covering installation, maintenance, integration,
implementation, administration and troubleshooting go to the EMC Education Services web
site.
This course covered Extended Retention features, benefits, architecture, use cases,
licensing options and installation and configuration, upgrading to Extended Retention and
managing and administering systems with Extended Retention.
This concludes the training. Proceed to the course assessment on the next slide.

Data Domain Extended Retention Installation, Configuration and Administration - MR-1WP-DDEXRET SRG

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Data Domain Extended Retention Installation, Configuration and Administration - MR-1WP-DDEXRET SRG

Încărcat de

Drepturi de autor:

Formate disponibile

Welcome to the Data Domain Extended Retention: Installation, Configuration and

Revision Date: August 2015

Revision Number: MR‐1WP‐DDEXRET.DDOS5.5.2

At this point, one of three things can happen:

ES20s and ES30s provide various storage capacities depending on configuration.

The shelf capacity license:

An Expanded-Storage license also enables the upgrade of a 7-disk DD160/DD620/DD640 to

If DD Retention Lock Compliance is enabled on a system, then as part of the compliance

To add an archive unit:

Click the Launch button to view the video.

Click the Launch button to view the video.

The data movement policies are driven by two user-defined settings:

Caution: Creating an overly aggressive movement policy to compensate for an undersized

Data Movement Packing

To configure data movement policy:

Click the Launch button to start the simulation.

Here you can do the following:

Click the Launch button to view the video.

Click the Launch button to view the video.

Replication is supported starting with DD OS 5.2.

Bi-directional replication is supported between systems that have the DD Extended

To copy data into DD Extended Retention using directory replication:

In a failure situation, perform recovery actions in the order listed below.

S-ar putea să vă placă și