Data Domain Virtual Edition Fundamentals

Welcome to Data Domain Virtual Edition Fundamentals.
Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks
of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the
USA.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” DELL EMC 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 DELL 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 DELL 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.
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 2017
Revision Number: MR-1WN-DDVEFUN
Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 1

This course covers a review of benefits, features, and functions of Data Domain Virtual Edition in an on-
premises configuration.

This module covers an introduction of the Data Domain Virtual Edition solutions, functional benefits,
implementations, use cases, and supported DD OS features.

This lesson covers an introduction to the DD VE solution, including in the cloud or on premises options.

As the data protection landscape continues to evolve, businesses are faced with the
increasing pressure to reduce IT costs while still meeting the demands of Service Level
Agreements (SLAs). Data protection cannot be approached as a one size fits all solution,
which is why Data Domain is designed to protect data across consumption models in the
most efficient way possible.

Data Domain Virtual Edition is a customer-deployable software-only protection storage appliance that runs
many Data Domain system features using computer hardware through VMware VSphere Hypervisor. Like
any Data Domain system, DD VE is always paired with backup software.
DD VE is agile: Designed for use with VMware, it is exceptionally quick to set up and run. You can start
with a small capacity configuration and scale as large as
96 TB.
DD VE is flexible: Offers a flexible deployment environment that includes deduplication, replication, DD

Boost, tape out to cloud feature and scalable storage capacity.
DD VE is efficient: Users can take advantage of the same powerful deduplication feature available in all
DELL/EMC Data Domain hardware products along with the security of full replication capabilities, and
optional use of DD Boost to further speed-up data transfers to your own scalable storage configurations.

Given the form factor, scalability, and ease of setup and use, DD VE is an ideal solution in two entry-level
cases.
For the remote office/branch office (ROBO) use cases, customers want to use DD VE in branch offices
where they can have functionality of Data Domain backups and restores, but lack the expertise or need for
larger capacity DD systems. DD VE is a good solution as it is customer deployable with little expertise
required. It uses a wider choice of hardware and VMware compatibility. It supports multiple backup
software apps and can replicate to a central data center running a physical Data Domain system.

DD VE is designed for the entry or small capacity use case but can grow into much larger capacity.
DD VE supports configurations from 1TB (a 500GB version is available for evaluation purposes) up to
96TB usable capacity storage - a perfect backup form factor for an office of any size.
With replication features enabled, this small office configuration can replicate to other DD VE systems or
to other local or remote Data Domain systems.

The release of Data Domain Virtual Edition (DD VE) 3.1 (with DD OS 6.1) has in the cloud and on-
premises capabilities. Customers can now deploy DD VE in the cloud to protect their applications in the
cloud. For example, you can back up and replicate data within the cloud or do so on the premises.
Customers can replicate data between on-premises and cloud or between different regions in the cloud.
Backup for applications running in the public cloud is also provided.
On-premises, DD VE provides the capabilities of a physical Data Domain system in a virtual machine
template for Microsoft Hyper-V, and VMware. Dell/EMC VxRail uses VMware, so the installation for VxRail
is the same as for VMware.

DD VE enables data protection in the cloud for applications running in the cloud. The DD VE is deployed
in the cloud and backup applications can use any existing backup protocols such as DDBoost or BoostFS
to backup and restore data to and from the DD VE.
Cloud computing resources are hosted in multiple regions worldwide. Each geographic region has
multiple, isolated locations.
You can deploy multiple DD VE systems inside the same cloud region, and use DD Management Center
to manage the DD VE systems across regions either on premises or in the cloud.
Backup applications back up the virtual apps and OS to cloud storage providing persistent block storage
volumes by the cloud provider. Backup apps can be NetWorker or other supported backup applications.
Although rare, failures can occur that affect the availability of instances that are in the same geographic
location. If you host all your instances in a single location that is affected by such a failure, none of your
instances would be available. We recommend when running a DD VE configuration with any cloud
provider you should set up an additional DD VE in a second availability zone and replicate the data to that
system.

For more information about Data Domain Virtual Edition as a compute device in the cloud, be sure to
attend the Data Domain Cloud Enablement elearning course available through Dell/EMC Education
Services.

This module covers an introduction of the Data Domain Virtual Edition on-premises solution, features,
environments, use cases, and supported DD OS features.

This lesson covers DD VE on-premises deployment options.

Whether it is deployed in the cloud or on-premises, a key DD VE benefit is the speed and ease of
deployment. You can download a working VMDK file, deploy it in VMware vSphere, and configure the
running DD VE system using DD System Manager. Once configured, you have a file system-enabled DD
VE system.

For additional reliability and ease of use, an automated deployment assessment tool can be run with DD
System Manager. This runs a check on the selected storage to ensure it meets DD VE requirements.
Through this check, you don’t have to guess whether the deployment is qualified and suitable for use. The
deployment assessment tool is accessible and supported through the DD System Manager or the
command line.

By running in VMware, DD VE gains some additional benefits by supporting VMware High Availability
(HA), Fault Tolerance (FT), and Distributed Resource Scheduler (DRS). VMware HA helps customers
meet availability needs so that if a physical server goes down, affected virtual machines are automatically
restarted on other servers with spare capacity. Should an operating system fail, HA restarts the affected
virtual machine on the same physical server. The fault tolerance capability provides continuous
availability. VMware DRS optimizes performance by providing highly available resources by balancing
workloads, and managing computing resources without disruption.
DD VE is supported on versions 5.5 or 6.0, with the corresponding versions of the VMware vSphere client
application.

Similar to running DD VE in a VMware environment, running in Microsoft Hyper-V, DD VE can support
similar storage capacities supporting up to 120 virtual disks and and similar system configurations. Hyper-
V High Availability (HA). A separate zip package is available for Microsoft Hyper-V.
DD VE runs on Hyper-V running on Microsoft Windows Server 2012 R2.

Another DD VE product configuration available to customers is through a “Try and Buy” program.
The main purpose for this program is to make our customers aware of the DD VE product.
You can obtain free a 500 GB capacity DD VE with no license time limit when you register with Dell/EMC.
The download package contains both the license and the software so, when downloaded, the DD VE is
immediately usable.
Those using the limited capacity license may upgrade to a production license and increase capacity
without the need to reinstall the DD VE software.

Three types of DD OS system features are available in DD VE:
• Features that function exactly as those in a physical Data Domain system are DDBoost, CIFS
workgroup and active directory, NFS, DD Encryption, garbage collection and DD Replication.
• Features that are optimized for use with DD VE are stream counts, MTree counts, the DD System
Manager, IPv4 and IPv6, and head unit swaps.
• New features supporting the DD VE system are the deployment assessment tool, licensing through the
Electronic Licensing and Management System (ELMS), virtual resource monitoring, and RAID-On-
LUN.

Shown here is a breakdown of features supported with the Data Domain Virtual Edition in the VMware
environment.
EMC offers a DD VE evaluation license for a limited 500 GB capacity, and full function of DD Replication,
DD Encryption, and DD Boost with no set expiration. This license can be replaced with larger capacity
licenses if needed – up to a maximum of 16 TB. Other limited time evaluation licenses are also available.
DD VE can be managed by both DD System Manager and DD Management Center. It supports all
replication topologies between virtual and physical systems. It also supports all common backup software
currently supported by Data Domain.

These are features not supported by DD VE. Please take a moment and review these items.
In some cases it makes sense that support is not available for features due to the limitations of the virtual
environment (Fibre Channel, for example).
In other cases, it is the limitation of the systems that would cause performance issues if implemented.

This lesson covers hardware and software resources used to support Data Domain Virtual Edition.

When installing and configuring DD VE, you should already be familiar with installing, configuring, and
managing VMware vSphere.
VMware management courses are available through EMC Education Services.
This diagram illustrates how a typical DD VE system is laid-out in the virtual environment.On the left is a
physical server where the VMware Hypervisor resides. Within the version of VMware, ESXi, there might
be many virtual deployments, one or more of them could be a DD VE deploymentOn the right is the
installation of DD VE that includes virtual hardware to emulate the Data Domain system including CPU,
memory, a virtual SCSI HBA that controls disk function to the root disk, NVRAM disk, and data disks. A
virtual NIC is also emulated.
The software that runs the DD VE is the same software used on a physical Data Domain system that
includes Data Domain services such as the Data Domain file system (DD FS) and systems management
services (SMS). The same Linux services used with the physical Data Domain are included for use on a
DD VE. A few VMware tools are added to aid in managing and measuring performance of the virtual
environment.

This is a list of software permitted for use with DD VE on VMware.
Configuring DD VE 3.1 or later requires the VMware Hypervisor version 5.5, or 6.0 supporting only ESXi.
It is important to note that VMware workstation is not supported.
You can use the vSphere web client from any platform with a web browser. Alternately, Windows clients
can also use the vSphere Client application.
SSH access is also available through applications such as PuTTY.

This table displays the virtual configuration requirements needed to support the various storage levels for
DD VE.
Only specify one socket when configuring the virtual CPU.
A 4 or 8 terabyte system requires two cores. A 16 terabyte system requires four cores.
Each core requires a reservation of 1.5 gigahertz. Hardware with a CPU speed less than 1.5 gigahertz is
not supported. When a hardware configuration problem exists with respect to the CPU; reconfigure the
CPU topology to a single socket with the correct number of cores for the desired storage capacity.
6 gigabytes of memory is required to support a system with 4 terabytes of storage capacity. 8 gigabytes of
memory is required to support a system with 8 terabytes of storage capacity. And 16 gigabytes of memory
is required to support a system with 16 terabytes of storage capacity. Ballooning memory is not
supported.
When you deploy DD VE, the system automatically deploys a 250 gigabyte root disk and a 10 gigabyte
NVRAM emulation disk. Within the NVRAM disk are 512 megabytes for NVRAM simulation.
DD VE allows a maximum of 4 network interface adapters. Two are provisioned by default. Up to 4 SCSI
controllers can be added to support additional storage.
By default, the system clock syncs to the ESXi host.

This lesson covers Data Domain Virtual Edition features and considerations.

To make sure the performance of chosen storage meets the needs of DD VE, the deployment assessment
tool is used as part of the deployment wizard.
Users are prompted to run this via the DD System Manager during the initial configuration and when
storage is added.
It can also be run at any time to help troubleshoot performance problems. The deployment assessment
tool can also be run through the command line interface.

This is the I/O stack diagram of data storage for DD VE.
The bottom layer is the storage array. It can be DAS, NAS, or SAN running RAID 5 or 6 to prevent data
loss in case of disk failure.
The next layer is the VMware software stack, where VMware creates the VMware file system (VMFS) on
your hardware.
The top layer is the DD VE virtual machine and Data Domain file system (DDFS) with RAID-On-LUN on
the data disks.
DD VE uses RAID-On-LUN as an added protection measure against data corruption that cannot be
handled by external RAID.

When configuring virtual disks for DD VE, disks must be formatted using thick provisioning and a lazy or eager zeroed
policy.
Thick provisioning is a type of storage allocation in which the amount of storage capacity on a disk is pre-allocated on
physical storage at the time the disk is created. This makes the allocated physical storage unavailable for anything
else. It ensures available storage space at all times for this system.
Eager zeroed is when the data remaining on the physical device is zeroed out when the virtual disk is created. It
might take much longer to create disks in this format than to create other types of disks.
The other option is Lazy zeroed, where the data remaining on the physical device is not erased during creation, but
is zeroed out on demand at a later time on first write from the virtual machine.
The only disk controller that can be used with DD VE disk configuration is the VMware para-virtual SCSI (PVSCSI)
controller.
During configuration, the DD VE configuration wizard runs the Deployment Assessment Tool against the physical
drives you are configuring for storage with your system. The survey, which takes around five minutes, determines
whether the drives will perform within performance tolerances for your DD VE system. If the drives do not pass the
survey, you may still create the file system, but survey results stress that system performance might be less than
optimal and might create an unstable system.
The virtual root disk size is 260 GB to accommodate both the provisioned root disk and the NVRAM emulation disk.
These virtual disks are automatically created with the VM. The minimum size for a data disk is 100 GB and the first
data disk should be at least 200 GB in size.
Data disks can be configured from more than one data store. You should use larger data stores instead of multiple
smaller ones. For example, if you configure a 4 TB capacity DD VE from two data stores, create a 2 TB disk on each
data store.
The maximum size of each disk is decided by Hypervisor in the VM file system and the DD VE capacity license. A
maximum of 14 data disks can be attached to a DD VE instance. The data disk aggregate size is the total capacity
plus 10% to support the file system overhead required. So if you are creating an 8 TB file system, you will need 8.8
TB of data disk attached to the DD VE.

Shown here are the VMware features supported and not supported by DD VE. Take a moment to review
this table.
Since there is only one SCSI type supported, any additional changes to a different SCSI type will cause
the instance to fail.
Changing the sequence of system disks is not supported by DD VE. The first disk in the sequence must
be the root disk and the second disk must be the NVRAM disk. These cannot be changed.
Live adding or hot adding SCSI controllers, network adapters, CPUs and memory is not supported. If you
add a new network adapter, increase the number of CPUs or add memory, the system must then be
rebooted.
Changing the size of an existing disk is not supported. Add another virtual disk if more capacity is needed.
Upgrading VMware tools is not supported because 3rd party VMware tools are being used with DD VE.
Attempting to upgrade VMware tools will result in an error.
Taking snapshots within VMware is not supported because the snapshot creates a delta disk and new
writes are written to the delta disk. This causes performance issues with the DD VE.

When controlling power to a DD VE system from VMware never use Power Off, Suspend or Reset. Power
Off and Reset act as if a power cable has been pulled on a hardware Data Domain system and could
cause data loss. Using the Suspend operation might cause unexpected results.
Instead, only use the Shut Down Guest and Restart Guest menu options when needed.

This module provided an overview of the Data Domain Virtual Edition, its use cases, configuration
requirements, and feature set.

This module covers installation, configuration, licensing, and troubleshooting a DD VE system.

This lesson covers downloading and installing DD VE.

DD VE is installed into the VMware environment from an Open Virtual Appliance (OVA) file.
The DD VE file can be identified by the OS name, “ddve” followed by the version number, then the build
number, followed by the OVA extension.
Deploy the DD VE virtual machine from either the Deploy OVF Template… wizard found in the Actions
menu of the VMware vSphere client or using the VMware ovftool in the Linux or Windows command line.

This demo covers installing and configuring a DD VE in a VMware environment.

This lesson covers increasing storage capacity to an installed DD VE.

An existing DD VE can start out with small capacity and grow.
The minimum license is 1 TB, the minimum disk capacity of a DD VE instance can be 200 GB.
Additional disks of desired capacity can be added as needed.
We recommend running the deployment assessment tool to make sure the added storage meets
performance guidelines.
Add the vDisk in VMware management to the DD VE virtual machine, then the DD System Manager can
be used to add the additional storage to expand the DD VE capacity.

This demo covers adding storage to a DD VE in a VMware environment.

This lesson focuses on the electronic licensing management system, its features, and process related to
DD VE.

Electronic licensing management system (ELMS) electronically represents software entitlements. It is the
standard method of electronic license fulfillment and activation used by EMC.
DD OS uses one license per DD VE instance.
DD VE does not support previous licenses from legacy DD OS systems.
When deploying the DD VE system, the license must be added to access the file system.
The license file must be built based upon the Node Locking ID that is unique to the DD VE instance.

Here’s the process for licensing your DD VE instance.
When you place an order through Sales, ELMS generates a license activation code. The code is sent to
you via email.
When you deploy and launch DD VE in VMware, you are shown the Node Locking ID for your DD VE
instance.
You then access ELMS and enter both the license activation code and node locking ID. ELMS provides a
license file that includes licenses for your purchased features and capacity along with with an activation
code.
You then download the license file and apply it on the selected DD VE system.

You can update the DD VE license in one of two ways through the command line interface.
Transfer the license file to the /ddvar directory. Then issue the elicense update command providing
the filename or you can paste the full license content when prompted.
Use elicense show to view current licenses, the locking ID for the DD VE system or the software ID.
Use elicense reset to remove all licenses from the system.
Note: Resetting the licenses from a system disables access to the file system until a valid license file is
added to the system.

There are two specific types of alerts related to license errors.
The first is when the node locking ID recorded in the license no longer matches the node locking ID of the
system.
A change in the locking ID can occur by cloning a DD VE system or through a virtual headswap.
When this happens, the licenses on the system continue to function for 30 days to allow you to resolve the
license issue.
Alerts are generated daily during the last seven days of the grace period.
A capacity alert is generated when licensed capacity is 0 or when the file system size becomes larger than
the amount licensed.
When the file system is equal to or larger than the licensed capacity, the system becomes read-only.
No further data can be written to the system until a license is added.

DD VE 3.1 features the Served Licensing Model for DD VE which provides the solution for managing
licensing for the deployment of DD VE(s). This solution is only available for virtual systems, not physical
systems at this time. The sales ordering process will remain the same.
Licenses are retrieved, by the customer, from the Software Licensing Central (SLC) portal. This allows you
to deploy the license server software (the hardware server is not provided) by downloading this license,
loading it into the license server, and configuring the DD VE to talk to the license server to verify its
licenses.

This lesson covers troubleshooting methods and related tools to gather data, assess, and resolve issues
with a DD VE system.

This table lists some of the more common log files on the system. When troubleshooting a DD VE system,
you might encounter issues related to the virtual nature of the system. You should make sure the research
is time correlated to when a problem first occurs so you can match log file entries on the Data Domain
system with possible log entries from the VMware system.
Performance counter logs collecting performance statistics are kept in the ddveperf.log.
If a particular job is running when a problem occurs, for instance a job using DD Boost, you will also want
to review related client log files for added information.

Troubleshooting a DD VE system requires the same skills and tools used to troubleshoot a standard Data
Domain system. Autosupports and support bundles are key documents to investigate an issue.
Autosupports provide a point-in-time status of the system status, alerts, and registry key value pairs.
In the Autosupport header, you can see a few changes when reporting on a DD VE system.
First, since a DD VE is virtual hardware, the chassis serial number will be blank.
The system model number is identified as a DD VE system.
Lastly, the Hypervisor type is identified.

While the virtual system is running, VMware software runs constant configuration verification and
monitoring. At any point in time when configuration is checked and configuration requirements are no
longer met, it displays an alert.
For example, if the VM system only finds one CPU when there are supposed to be two, an alert appears
indicating which configuration parameter is in error. This table shows a list of possible configuration issues
and their potential alert messages.
These configuration errors match to the configuration requirements presented earlier in the course. When
a configuration alert appears, be sure to check the related configuration requirement to understand what is
in error.

If storage is not performing well or if there is network latency, the system will experience performance
issues.
Troubleshooting these issues begins with the hardware chosen to run the virtual system. Validate that the
physical hardware running the virtual system is compatible for use with DD VE.
Access the vSphere web client to make sure the virtual CPU topology and reservation matches the
storage capacity selected for the configured DD VE.

In vSphere, you can check host performance by running a vSphere performance analysis.
This tool produces a performance graph that indicates host performance over time.
vCenter/ESXi performance counters collection can be enabled on demand using the vSphere web client.
From the DD VE, you can configure the vServer host and port and gather performance statistics from that
host.
Use the vserver config command to configure the vCenter IP address and port number.Use the vserver
perf-stats start command to collect performance statistics in five minute intervals.
Use this log to compare the performance statistics to the vCenter/ESXi performance counters and identify
performance issues.

The deployment assessment tool can be used to assess storage performance on a production DD VE.
On a production system, the tool is non-invasive. On a system holding user data, the deployment
assessment tool performs read-only operations on disks used by DDFS.
On unused disks, the deployment assessment tool performs read/write operations for the best possible
performance measurement.
The disk benchmark show requirements command shows the requirements for the various file
system capacities as displayed here.
To run the benchmark, use disk benchmark start with the list of disks to be tested.
To stop the tool, use disk benchmark stop.
To watch the progress of the tool, use disk benchmark watch.
The commands only work with data disks and not the root or NVRAM disks.
Use the deployment assessment tool or disk benchmark CLI commands to troubleshoot IOPS and IO
latency.
IO performance might have been acceptable when the DD VE was originally deployed, but now there
could be additional VM deployments sharing the same stack and causing reduced IOPS given to DD VE.
Run the tool to see the current performance from the storage. If there is deterioration, compare the current
measurements with the previous results saved at deployment.
Results are saved in /ddvar/log/vcenter/ddveperf.log.

If the virtual disks are running on the same data store, run the deployment assessment tool against the
disks in series.
Separate the disks you want to test by a plus sign as shown in the example.
If virtual disks are running on separate data stores, run the deployment assessment tool against the disks
in parallel.
Separate the disks you want to test by a space, as shown in this example.

Any and all physical storage array corruption issues must be handled by the storage manufacturer.
Any Virtual Machine File System corruption issues must be handled directly by VMware.Root disks hold
the DD OS binaries for the system. Root disk corruption is easily solved in a virtual environment by
performing a virtual headswap. A knowledgebase article is provided at support.emc.com.
NVRAM disk corruption is easily fixed by creating a new NVRAM disk. Contact Support for assistance.
If there are any virtual data disk corruption issues due to the complexity of most of these issues, you
should involve Support at the earliest opportunity. Data disks are where customer data is stored. It is
important not to take any action to cause further corruption.

Three tools are available to help determine causes of system instability, throughput performance, or disk
failure.
When a DD VE system hangs without any response, you can trigger a crash dump and reset the DD VE.
When the DD VE reboots, crash dump files can be exported for analysis. Files are located in the
/ddvar/core directory.
IO latency monitor in the SCSI layer – monitors latencies of reads and writes at the SCSI layer and
protocol layer and produces a log for analysis when the latency goes beyond an expected threshold.
Disk fail policy – if a storage disk is absent, the file system will shut down and an alert is generated.

This module discussed DD VE setup, configuration, management, and troubleshooting.

This course covered the features, configuration, and use for a Data Domain Virtual Edition system.


Data Domain Virtual Edition Fundamentals

Uploaded by

Document Information

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

Data Domain Virtual Edition Fundamentals

Uploaded by

Copyright:

Available Formats

Welcome to Data Domain Virtual Edition Fundamentals.

Revision Date: August 2017

Revision Number: MR-1WN-DDVEFUN

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 1

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 2

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 3

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 4

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 5

DD VE is flexible: Offers a flexible deployment environment that includes deduplication, replication, DD

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 6

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 7

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 8

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 9

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 10

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 11

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 12

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 13

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 14

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 15

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 16

DD VE runs on Hyper-V running on Microsoft Windows Server 2012 R2.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 17

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 18

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 19

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 20

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 21

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 22

VMware management courses are available through EMC Education Services.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 23

It is important to note that VMware workstation is not supported.

SSH access is also available through applications such as PuTTY.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 24

Only specify one socket when configuring the virtual CPU.

By default, the system clock syncs to the ESXi host.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 25

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 26

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 27

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 28

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 29

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 30

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 31

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 32

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 33

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 34

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 35

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 36

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 37

Additional disks of desired capacity can be added as needed.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 38

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 39

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 40

DD OS uses one license per DD VE instance.

DD VE does not support previous licenses from legacy DD OS systems.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 41

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 42

Use elicense reset to remove all licenses from the system.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 43

No further data can be written to the system until a license is added.

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 44

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 45

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 46

Copyright © 2017 Dell Inc. Data Domain Virtual Edition Fundamentals 47

The system model number is identified as a DD VE system.

Lastly, the Hypervisor type is identified.