Data Domain - DD VE 2.0-Data Domain Virtual Edition v2.0 Install Admin Guide
Data Domain - DD VE 2.0-Data Domain Virtual Edition v2.0 Install Admin Guide
Topic
DD VE 2.0
Selections
DD VE 2.0 Initial Configuration Guide: Data Domain Virtual Edition v2.0 Install Admin Guide
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]
Copyright © 2022 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell
EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be
trademarks of their respective owners.
The information in this publication is provided “as is.” Dell Inc. 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 software described in this publication requires an applicable
software license.
This document may contain certain words that are not consistent with Dell's current language guidelines.
Dell plans to update the document over subsequent future releases to revise these words accordingly.
This document may contain language from third party content that is not under Dell's control and is not
consistent with Dell's current guidelines for Dell's own content. When such third party content is updated
by the relevant third parties, this document will be revised accordingly.
Page 1 of 44
Contents
Preliminary Activity Tasks .......................................................................................................4
Read, understand, and perform these tasks.................................................................................................4
Introduction to DD VE .............................................................................................................5
What is DD VE? ............................................................................................................................................5
DD VE capabilities and licensing ..................................................................................................................5
DD VE management ...............................................................................................................7
Supported VMware Environments ..........................................................................................7
Preparing Physical Storage on the VMware Server......................................................................................7
Performance Monitoring ..........................................................................................................................8
Configuring SAN Datastores....................................................................................................................8
NFS Datastore Configuration...................................................................................................................8
Configuration of Other Resources ................................................................................................................8
Collecting performance counters ...........................................................................................................10
Performing the DD VE Download..........................................................................................10
Performing the DD VE Installation ........................................................................................10
Installing on a VMware ESXi Server ...........................................................................................................11
Installing through a VMware vCenter Server ..............................................................................................13
Page 2 of 44
Disk (Spindle) Group Configuration .......................................................................................................34
Extensions to DD OS for DD VE.................................................................................................................34
DD VE-only commands.........................................................................................................36
Modified DD OS Commands.................................................................................................36
Unsupported DD OS Commands..........................................................................................38
Performance Troubleshooting...............................................................................................42
Migrating DD VE ...................................................................................................................44
Page 3 of 44
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.
Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity
2. This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.
Note: There may not be any top trending service topics for this product at any given time.
Page 4 of 44
Introduction to DD VEDDVE Installation and Administration Guide
What is DD VE?
Data Domain Virtual Edition (DD VE) is a software protection appliance: a virtual deduplication appliance
that provides data protection in the enterprise environment. Like any Data Domain system, DD VE is
always paired with backup software.
DD VE runs the Data Domain operating system (DD OS), and provides the DD OS command line
interface (CLI) and the Data Domain System Manager graphical user interface (GUI) for performing all
system operations.
Like a physical Data Domain system, DD VE ensures data integrity and provides multiple levels of data
compression, reliable restorations, and data replication. DD VE can be configured as a storage
destination for leading backup and archiving applications. For more information about the features and
capabilities of Data Domain systems (both physical and virtual), see the EMC Data Domain Operating
System Administration Guide.
Page 5 of 44
• Directory replication
• Instant access
• Retention lock
DD OS commands related to these unsupported features, and commands for hardware features that are
not applicable to a virtual machine, are not supported on the DD VE platform. Unsupported DD OS
Commandsdescribes unsupported commands.
DD VE is licensed through the Electronic License Management System (ELMS). When you purchase DD
VE, you receive an email which email contains a license authorization code (LAC) to redeem for the DD
VE software license. Follow the instructions in the email to create the license for the DD VE instance.
The software package includes a license for the 500 GB evaluation version. This license must be installed
manually after setting up the virtual machine. The evaluation version does not include a time limit or
disable any DD VE functionality, it is only limited by capacity.
Sample LAC email shows a sample email generated by the ELMS system.
Page 6 of 44
After the DD VE is configured and running, the elicense reset, elicense show, and elicense
update commands provide the ability to manage the DD VE license.
DD VE contains the following Data Domain feature licenses:
• DDVE_CAPACITY
• DDVE_DDBOOST
• DDVE_ENCRYPTION
• DDVE_REPLICATION
Note: MTree replication and managed file replication are the only supported forms of replication in
DD VE.
DD VE management
You use the VMware vSphere client software or the VMware vSphere Web client to install the DD VE and
define its virtual hardware: CPUs, memory, network interfaces, and virtual disks.
The DDSM GUI provides a configuration wizard to guide you through the steps required to configure DD
OS after the virtual appliance is installed.
Once the DD VE is configured and running, you can access the system console to run DD OS commands
by using the vSphere client or Web client. You can also administer the DD VE by using a terminal
emulator or ssh command line to use the command-line interface.
The default login credentials for the DD VE instance are:
• Username: sysadmin
• Password: changeme
Page 7 of 44
Performance Monitoring
Data Domain recommends that you enable the performance monitoring features of the DD VE instance. If
you ever need to troubleshoot a DD VE performance problem, you should begin by using the
performance monitoring software to detect and resolve any performance problems on the physical
storage layer.
Data Domain provides a deployment assessment tool (DAT) to scan the storage available on the ESXi
server, to determine if the storage meets the DD VE requirements. Table 1 lists the required physical
storage specifications for DD VE.
1. [ ] Run the DAT to make sure the underlying physical storage meets the requirements for DD VE.
Table 1 lists the required physical storage specifications for DD VE.
Note: Storage can still be configured even if the ESXi server fails the DAT assessment, but there will
be a negative impact on system performance and stability. EMC recommends deploying DD VE only
on storage that passes the DAT assessment.
2. [ ] Create a volume with the recommended RAID level that is dedicated to the DD VE system.
These disks should not be used for any other purpose.
3. [ ] Export one or more LUNs from this volume.
4. [ ] Create exactly one datastore for each LUN.
Like the volume, these datastores should be dedicated to the DD VE system and should not be used
for any other purpose.
Also see Configuring Disk (Spindle) Groups.
Note: Storage can still be configured even if the ESXi server fails the DAT assessment, but there will be a
negative impact on system performance and stability. EMC recommends deploying DD VE only on
storage that passes the DAT assessment.
NFS volumes and shares should be dedicated to the DD VE system and should not be used for any other
purpose.
Always present NFS storage to the ESXi hosts with a consistent identifier, so that each NFS folder gets
treated as the same unique datastore by all ESXi hosts. If you refer to the same storage host with
different names on different ESXi hosts, the hosts will see the NFS volumes as different datastores. This
problem can occur if you use a partial server name on one host (for example, nfssrv1) and the full server
name on another host (for example, nfssrv1.mycompany.com). In this scenario, the same folder on the
NFS server may be presented as two different datastores in the vSphere client, and it will be difficult to
ensure that the DD VE system is using a dedicated datastore.
Page 8 of 44
Initial Virtual Machine Configuration with the vSphere Client lists the memory requirements.
Note: Do not reduce system memory after you have created the file system in DD OS. This makes the file
system unusable.
DD VE can support up to four virtual network adapters. Two VMXNET3 virtual network adapters are
configured by default. If they are necessary, the third and fourth virtual network adapters must be
configured manually.
DD VE supports up to four VMware Paravirtual SCSI Controllers. Other types of SCSI controllers are not
supported. One SCSI Controller is configured by default. The maximum number of disks for each
controller is 15. Do not add extra SCSI HBA controllers to the DD VE system, or change the HBA
controller type. If you make changes accidentally, power off the virtual machine and restore the original
settings.
If you put DD VE systems into resource pools or vApp containers, do not override the default memory and
CPU resource allocation settings. The DD VE virtual machine will fail to boot up and report an
insufficient resource message if it cannot satisfy the minimum resource requirements shown in
the next table.
Resources Up to 4 TB 4 TB to 8 TB 8 TB to 16 TB
Computing resources CPU 2 x 1.5 GHz vCPU 4 x 1.5 GHz
vCPU
Memory 6 GB 8 GB 16 GB
Shares Normal
Limit Unlimited
Underlying storage Random IOPS 160 320 650
requirements
Random I/O latency 10 ms
Sequential throughput 40 MB/s 80 MB/s 160 MB/s
RAID RAID 5 or 6
SCSI controllers Up to 4 SCSI controllers
NVRAM simulation file 512 MB
size
System disks • 250 GB root disk
• 10 GB NVRAM disk
Note: The root disk and NVRAM disk are
required to deploy DD VE.
Page 9 of 44
Resources Up to 4 TB 4 TB to 8 TB 8 TB to 16 TB
disk was created because of overhead
requirements. DD VE storage guidelines
provides additional details about DD VE storage
overhead requirements.
The system displays an error message if you attempt to configure a higher capacity with fewer memory
and CPU resources than the amounts listed in the table above. To check these settings, use the
Resources tab of the Virtual Machine Properties dialog box in the vSphere client, or the system
vresource show requirements command.
Note: The 500 GB evaluation version is also available from the EMC Trial Download page.
All capacity configurations are available from the same zip file.
DD VE requires a minimum of 330 GB of available storage to deploy. The 330 GB breaks down as
follows:
• System disk: 250 GB
• NVRAM disk: 10 GB
• First data disk: 200 GB
Page 10 of 44
You can also use ovftool to install the software from the command line. For help, see the VMware
documentation.
1. [ ] Open the vSphere client and log in to the VMware ESXi Server.
2. [ ] Select File > Deploy OVF Template to launch the deployment wizard.
3. [ ] Do one of the following:
• Choose Deploy from file, browse to the local .ova file, and click Open. Then click Next.
• Choose Deploy from URL, enter the URL, and click Next.
Page 11 of 44
The Details page of the wizard appears to show information about the virtual machine.
4. [ ] Click Next, review the license agreement, and click Accept.
5. [ ] Click Next and enter the name of this DD VE.
This name identifies the virtual machine on the VMware server; it does not become a host name on
your LAN.
6. [ ] Click Next and choose a datastore for the virtual machine files.
Page 12 of 44
For best performance, Data Domain recommends that you use a dedicated datastore, one that is not
shared by other virtual machines.
7. [ ] Click Next, review the Ready to Complete summary, and then click Finish.
The next step is to configure the new virtual machine. See Initial Virtual Machine Configuration with the
vSphere Client.
Note: When using version 5.5 of the vSphere web client to install DD VE, the system displays the
following warning: The OVF package contains extra configuration options, which
possess a potential security risk. Review the extra configuration options
below and accept to continue the deployment. Select Accept extra configuration options to
continue.
1. [ ] Open the vSphere client and log in to the VMware vCenter Server.
Page 13 of 44
2. [ ] Select File > Deploy OVA Template to launch the deployment wizard.
3. [ ] In the deployment wizard that opens, do one of the following:
• Click Browse, browse to the local .ova file, and click Open. Then click Next.
• Enter the URL for the .ovf file and click Next.
Page 14 of 44
The Details page of the wizard appears to show information about the virtual machine.
4. [ ] Click Next, review the license agreement, and click Accept.
5. [ ] Click Next and enter the name of this DD VE. This name identifies the virtual machine on the
VMware server; it does not become a host name on your LAN.
Page 15 of 44
8. [ ] Click Next and select the storage location.
Page 16 of 44
The datastore must have 260 GB of free space available for the DD VE system software, and
NVRAM virtual disks. The disks should be contained within the same datastore.
9. [ ] Click Next and specify the provisioning option. For best performance, choose the Thick Provision
Eager Zeroed option, but be aware that creating the disk will take several hours. Data Domain
recommends that you choose the Thick Provision Lazy Zeroed option to reduce the time required to
create the disk.
Page 17 of 44
10. [ ] Click Next, review the Ready to Complete summary, and then click Finish.
Note: You can add the first or additional virtual data disks while the virtual machine is running, provided
that you do not also need to add more virtual memory to support the additional disks. DD VE supports
virtual disk hot-plugging, but not CPU or memory hot-plugging.
Depending on the amount of disk space, you may also need to add memory to the virtual machine. The
next table shows the supported storage configurations and their virtual CPU and memory requirements.
The system displays an error message if you attempt to configure a higher capacity with fewer memory
and CPU resources than the amounts listed in the table above. The system vresource show
requirements command lists the virtual resources available on the host.
Page 18 of 44
Note: The list of hardware shows two existing virtual disks. Those disks are used for the system
software and cannot be used for storage. Do not change any properties of these disks.
3. [ ] Adjust the value of Memory Size to the correct value for the amount of storage you will add to
this DD VE. Adding extra memory beyond the suggested value does not improve performance, and
prevents other virtual machines from using those resources.
4. [ ] Click the Resources tab, highlight Memory, and change the value of Reservation to match the
value you set for Memory Size in the previous step.
5. [ ] Click the Hardware tab and then click Add to open the Add Hardware wizard.
Page 19 of 44
6. [ ] Select Hard Disk and click Next.
7. [ ] On the Select a Disk page of the wizard, Choose Create a new virtual disk and click Next.
8. [ ] In the Create a Disk page of the wizard, set Disk Size to the amount of storage you want to add.
The minimum size of the first data disk is 187 GiB (200 GB). The minimum size of any subsequent
data disks is 94 GiB (100 GB).
Check that there is enough free space on the target datastore.
For information about how block size constrains the maximum size of the disk, visit
http://kb.vmware.com and see article 1003565, Block size limitations of a VMFS datastore.
Page 20 of 44
Figure 2 Create a Disk Page of the Add Hardware Wizard (VMware version 5.0)
Note: Although the VMware client displays units of GB, the actual units are 230 bytes (GiB).
Note: You cannot specify the disk provisioning format if the disk resides on an NFS datastore. The
NFS server determines the allocation policy.
10. [ ] For best performance, select Specify a datastore under Location and browse to select a
datastore.
11. [ ] Click through the remaining pages of the wizard and click Finish to create the disk.
To add additional storage or memory in the future, follow the previous steps. It is not necessary to shut
down the virtual machine before adding storage.
Note: The virtual disk cannot be expanded. Create a new virtual disk to add additional storage to the
virtual machine.
Page 21 of 44
Setting Up NTP Time Synchronization
NTP is disabled on the DD VE system by default, and the Synchronize guest time with host option is
selected in the VMware Tools.
If you need to enable NTP on the DD VE, follow these steps:
Note: Skip this task if you are going to join the DD VE to an Acrive Directory domain. Because the
Windows domain controller obtains the time from an external source, NTP must be configured. See the
Microsoft documentation on how to configure NTP for theWindows operating system version or service
pack that is running on your domain controller. After joining the domain, the system time is peridocally
synchronized with the domain controller time. When the host joins the Active Directory, the DD VE
displays a warning if multiple time sources are in use.
1. [ ] Click the Options tab in the Virtual Machine Properties dialog box.
2. [ ] Click VMware Tools.
3. [ ] Deselect Synchronize guest time with host.
Page 22 of 44
Later, while performing initial configuration of the DD VE system, enable NTP by selecting the appropriate
options from the configuration wizards. If you do not use the wizards to perform initial configuration, you
can use the ntp enable command on the DD OS command line. Enabling NTP with the ntp enable
command automatically disables synchronizing the time on the guest to the host time.
To reenable synchronizing the guest time to the host time, run the ntp disable command.
Note: NTP is disabled by default. The ntp reset command also deactivates NTP on the guest.
1. [ ] In the vSphere Client window, click Power On in the Commands box of the Summary tab.
Page 23 of 44
Note: There may be a delay of several minutes until the DD OS prompt appears, depending on your
hardware and configuration.
As the system starts up, the list of commands in the Summary tab updates.
2. [ ] Optionally, click Open Console to view the boot and initialization process. You should see the
CLI prompt to log in for a successful boot.
3. [ ] Note the IP Address assigned to the system by DHCP and shown in the previous figure.
You can use this address to configure or administer the system outside the vSphere Client.
The next step is the initial system configuration in DD OS. See Error! No bookmark name given. for an
overview, and see the EMC Data Domain Operating System Initial Configuration Guide for detailed
instructions.
Note: To shut down the DD VE virtual machine, you can use the Shut Down Guest command in the
vSphere client or Web client Summary tab. Do not use the Power Off or Reset commands, because they
perform a "hard" reset of the system rather than an orderly shutdown.
•
•
Initial System ConfigurationYou can connect to the system to perform the initial system
configuration with the command-line configuration wizard, or the DDSM Configuration Wizard.
DHCP is enabled on the DD VE system by default. If the DHCP service is available, the DD VE system
will receive IP addresses from the DHCP server. You can see the DHCP-assigned IP addresses in the
Summary tab of the vSphere Client window. You can change these IP addresses to static IP addresses
during initial configuration.
Note: DHCP is only activated automatically for the first two network interface cards (NICs) which are built
into the virtual machine template. Any extra NICs must be configured manually.
Page 24 of 44
Access DDSM by entering the IP address of the DD VE into a web browser, and logging in.
The GUI Configuration Wizard contains six sections: Networking, File System, System Settings, DD
Boost, CIFS, and NFS.
Deploying DD VE in Data Domain System Manager describes how to configure the DD VE from the GUI.
There are two ways to access the CLI:
• By using the vSphere Client to access the DD OS console
• By using ssh or a terminal emulator to access the DD OS command line
The CLI configuration utility contains four sections: Network, eLicenses, System, and DD Boost.
Provisioning the storage with the CLI describes how to configure the DD VE manually with the CLI
instead of using the configuration utility.
DD VE storage guidelines
Be aware of the following virtual storage guidelines for DD VE before deploying a DD VE instance.
DD VE licenses are sold in Terabytes (TB), but VMware disk sizes are actually measured in Tebibytes
(TiB). 1 TB is equal to 1.1 TiB. Because of this, DD VE allows a 10% buffer to reach the licensed capacity
measured in TB.
Individual virtual disks are subject to overhead that reduce their amount of usable capacity to amounts
lower than their specified capacity.
• The first data disk is subject to 120 GB of base overhead, with 5.6% of the remaining capacity
reserved for RAID-on-LUN
• All subsequent data disks are subject to 5.6% overhead reserved for RAID-on-LUN
Page 25 of 44
Deploying DD VE in Data Domain System Manager
DD VE licensing and configuration can be accomplished through the Configuration Wizard in Data
Domain System Manager. After the initial installation of a DD VE instance, the Configuration Wizard
automatically appears after the licensing screen on the first launch of DDSM.
Enter the DD VE virtual machine IP address into a web browser to launch Data Domain System Manager.
Log in with the following credentials:
• Username: sysadmin
• Password: changeme
The Apply Your License window is the first screen that appears when DDSM is launched for the first time.
The DD VE instance is locked until a license file is applied.
Click Browse, locate the license file for a purchased capacity license or the evaluation license included
with the DD VE download, then click Apply.
Note: If you begin the configuration with the evaluation license, but wish to purchase a license later, you
will need the Node Locking ID for the DD VE instance. Click Administration > Licenses to view the Node
Locking ID.
After applying the DD VE license, the Configuration Wizard begins automatically. The wizard assists in
configuring the following aspects of the DD VE:
• Networking
• DHCP or manual settings
• Virtual interface ethV0 and ethV1 configuration
• DHCP or manual DNS configuration
Page 26 of 44
Figure 4 Configuration Wizard - Network
• File system
Note: DD VE supports a maximum of six MTrees active at a given time, however up to 100 MTrees
can be created on DD VE.
Page 27 of 44
Figure 5 Configuration Wizard - File System
• System settings
• Update the sysadmin password
• Optionally configure alert and autosupport email settings
Page 28 of 44
• DD Boost
• Create a Boost storage-unit, and assign a user ID to own it
• CIFS
• Select workgroup or Active Directory mode
• Create CIFS shares and add clients
Page 29 of 44
Figure 8 Configuration Wizard - CIFS Protocol
• NFS
• Create NFS exports and add clients
Page 30 of 44
Provisioning the storage with the CLI
1. [ ] Log into the system with the user name of sysadmin.
The default password is changeme.
At the first login, use the elicense command to add a DD VE license.
2. [ ] Type control-C to exit the configuration utility.
3. [ ] Confirm that virtual disk dev3 exists and has the expected size:
# disk show hardware
The output should include a line similar to the following example:
dev3 VMware Virtual disk 1.0 (unknown) 256.00 GiB SAS n/a
The first two virtual disks (dev1 and dev2) are used for the system software and cannot be used for
storage. The disk show state command shows System Dev for these system disks.
4. [ ] Add the storage disk to the active storage tier:
# storage add dev3
If you are adding more than one virtual disk, repeat the storage add command for each disk. For
guidelines on specifying the optional spindle-group argument, see Configuring Disk (Spindle) Groups
on page 46.
5. [ ] Create the file system:
# filesys create
6. [ ] Enable the file system:
# filesys enable
You can now complete the initial system configuration. See Completing Initial Configuration with the
Command-Line.
Page 31 of 44
Follow the configuration utility instructions for entering appropriate values. At the end of each
configuration section, you can choose to: Save, Cancel, or Retry (restart the input entry as the
beginning of the current section).
Note: If you need to enable NTP, you can do so with the configuration utility.
Page 32 of 44
Information about installing licenses and configuring optional software can be found in the EMC Data
Domain Administration Guide. Access the latest documents at https://support.emc.com.
Note: Any system command that accepts a list, such as a list of IP addresses, accepts entries separated
by either commas or spaces. See the EMC Data Domain Operating System Command Reference Guide
for command details.
It is not possible to extend a virtual disk if it has already been used by the file system. Instead, expand the
storage by adding a new virtual disk.
In DDSM, click Hardware > Storage > Configure Storage to add additional devices to the DD VE active
tier.
Note: If no addable devices exist, create new virtual disks as described in Adding Disks and Memory.
Page 33 of 44
After adding the storage, click Data Manage > File System > More Tasks > Expand Capacity > Next to
launch the DAT to verify the hardware supporting the virtual storage meets the requirements for DD VE.
When you add a new virtual data disk to an existing DD OS file system, use the filesys expand
command instead of the filesys create command. For instructions and restrictions, see Initial Virtual
Machine Configuration with the vSphere Client.
Extensions to DD OS for DD VE
Several DD OS commands are supported on the DD VE platform only. This section describes these
commands.
Note: Running DAT before expanding the file system requires the presence of at least one device to add
to the active storage tier.
In DDSM, click Data Manage > File System > More Tasks > Expand Capacity.
Click Configure to add devices to the active tier, or click Next if you have already added the devices to the
active tier.
Run the DAT to analyze the underlying storage performance.
disk benchmark requirements
Displays the currently configured recommended performance characteristics by disk capacity.
disk benchmark start devdisk-id[,devdisk-id ...] [devdisk-id[,devdisk-id]...]
Start a performance benchmark test on one or more data disks in series or in parallel. Specify one or
more disks, separated by commas or spaces. Disks separated by spaces are tested in parallel. Disks
separated by commas are run in series. The comma separator takes precedence over the space and
nesting is not supported. This means that you can run serial tests in parallel, but not a series of parallel
tests. Only specify a device once in the list.
Page 34 of 44
Test dev3. When that test finishes, test dev4.
# disk benchmark start dev3+dev4
Test dev3 and dev4 in parallel.
disk benchmark start dev3 dev4
Start two series of tests in parallel. The two series of tests are dev3 followed by dev4, and dev5 followed
by dev6.
# disk benchmark start dev3+dev4 dev5+dev6
disk benchmark show {[[detailed] test-id] | all | requirements}
Print disk performance benchmark test results and report a recommended capacity for the tested
configuration. With no arguments, the command prints information about the most recent test for every
disk. Specify a test-id to see information about a single test. Specify all to see a table of previous
and currently running tests. Specify requirements to see a table of performance goals.
Note: The disk benchmark show command conducts a test of the cache performance on the host
system to determine which DD VE capacity configurations can be supported on the host.
perf
Collect and show DD VE performance statistics.
perf disable trace event-regexp [module {default | ddfs}]
Disable tracing of specified events.
perf enable trace event-regexp [module {default | ddfs}]
Enable tracing of the specified events.
perf start histogram [module {default | ddfs}
Start collecting performance histograms. This command may reduce performance marginally.
perf start stats
Start printing statistics. This command may reduce performance marginally.
perf start trace [allow-wrap] [module {default | ddfs}]
Start tracing events. This command may reduce performance marginally.
perf status trace event-regexp [module {default | ddfs}]
Shows whether tracing is enabled or disabled for the specified events.
perf stop histogram histogram-filename [module {default | ddfs}
Stop collecting histograms and write the collected histograms to the specified file.
perf stop stats
Stop printing statistics.
Page 35 of 44
perf stop trace trace-filename [module {default | ddfs}]
Stop tracing events and write the collected traces to the specified file.
system vresource
Display details about the virtual CPU and memory resources on the DD VE host.
system vresource show [current | requirements]
Display details about the virtual CPU and memory resources on the DD VE host.
DD VE-only commands
The following commands only work on DD VE, and are not supported on physical Data Domain systems.
Command Description
disk benchmark [[detailed] <test-id>] Create a disk benchmark test, and specify a unique ID
for the test. Use the detailed option to collect more
advanced information.
disk benchmark show all List all the disk benchmark tests stored on the system.
disk benchmark show requirements Displays the physical storage requirements for running
DD VE.
disk benchmark start <dev-list> Start disk benchmarking tests on the specified device.
disk benchmark stop Stop all disk benchmarking.
disk benchmark watch Displays information about an in-progress disk
benchmarking test, including the test being run, the
device being tested, and the percent complete. This
command blocks the system until the test completes, or
the user types Ctrl + C.
elicense update Update license information.
elicense show Show current license information.
elicense reset Reset license settings to their default values.
system set serialno <serialno> Set the DD VE serial number to the specified value.
system vresource show [requirements] Displays the number of virtual CPUs, the number of
cores per virtual CPU, and the amount of memory
assigned to the virtual machine running the DD VE
instance. The requirements option displays
the physical storage requirements for DD
VE.
vserver config set Set the vServer credentials for DD VE.
vserver config reset Reset the vServer credentials for DD VE to their default
values.
vserver config show Display the vServer credentials for DD VE.
Modified DD OS Commands
The behavior of the following commands has been modified on the DD VE platform:
Page 36 of 44
Table 7 Modified DD OS Commands
Command Changes
alert The tenant-unit parameter is not supported.
compression The tenant-unit parameter is not supported.
config setup show Arguments for configuring features not available in DD
VE have been removed.
ddboost clients show active The tenant-unit parameter is not supported.
ddboost file-replication show active The tenant-unit parameter is not supported.
ddboost file-replication show detailed- The tenant-unit parameter is not supported.
file-history
ddboost file-replication show file- The tenant-unit parameter is not supported.
history
ddboost option reset The fc parameter is not supported.
ddboost option show The fc parameter is not supported.
ddboost storage-unit create The tenant-unit parameter is not supported.
ddboost storage-unit modify The tenant-unit parameter is not supported.
ddboost storage-unit show The tenant-unit parameter is not supported.
ddboost streams show active The tenant-unit parameter is not supported.
ddboost streams show history The tenant-unit parameter is not supported.
disk rescan The <enlcosure-ID>.<disk-ID> parameter is not
supported.
disk show state DD VE system disks show the System Dev state.
disk show stats The DD VE format for this command is disk show
stats [dev <n>]
disk status The Spare row has been removed from the output. The
System row has been added.
enclosure show all The [<enclosure>] parameter is not supported.
enclosure show controllers The [<enclosure>] parameter is not supported.
enclosure show cpus The [<enclosure>] parameter is not supported.
enclosure show io-cards The [<enclosure>] parameter is not supported.
enclosure show memory The [<enclosure>] parameter is not supported.
filesys encryption keyes delete The [tier {active | archive} | archive-
unit <unit-name>] paramater is not supported.
filesys encryption keys show The [tier {active | archive} | archive-
unit <unit-name>] paramater is not supported.
filesys fastcopy The [retention-lock] parameter is not supported.
filesys show compression The [tier {active | archive} | archive-
unit <unit-name>] paramater is not supported.
filesys show space The [tier {active | archive} | archive-
unit <unit-name> | arcjove-unit {all |
Page 37 of 44
Command Changes
<unit-name>] paramater is not supported.
mtree create The tenant-unit parameter is not supported.
mtree list The tenant-unit parameter is not supported.
mtree show compression The tenant-unit and tenant-unit parameters are
not supported.
mtree show performance The tenant-unit parameter is not supported.
net create interface The <virtual-ifname> parameter is not supported.
net destroy The <virtual-ifname> parameter is not supported.
perf The vtl option is not supported on any perf
command.
storage add The tier, enclosure, and disk parameters are not
supported.
storage remove The tier, enclosure, and disk parameters are not
supported.
storage show The archive option is not supported.
system show stats NVRAM statistics are not reported, because DD VE
systems do not have physical NVRAM.
quota The tenant-unit parameter is not supported.
replication MTree replication is the only type of replication
supported.
snapshot The tenant-unit parameter is not supported.
Unsupported DD OS Commands
The following DD OS commands and command options are not supported on the DD VE platform.
Page 38 of 44
Unsupported Command or Command Option Notes
instead.
archive
authorization
autosupport display Deprecated. Use autosupport show report
instead.
autosupport reset support-list Deprecated. Use autosupport reset { all |
alert-summary | asup-detailed | support-
notify } instead.
autosupport show support-list Deprecated. Use autosupport show { all |
asup-detailed | alert-summary | support-
notify } instead.
cifs set authentication nt4 Deprecated. Use cifs set authentication
active-directory instead.
cluster
ddboost fc
ddboost option reset fc
ddboost option set fc
ddboost option show fc
ddboost show image-duplication Deprecated. Use ddboost file-replication
show instead.
ddboost user option set user default-
tenant-unit tenant-unit
ddboost user option reset user [default-
tenant-unit]
disk add devdisk-id [spindle-group 1-16] Deprecated. Use storage add instead.
disk add enclosure enclosure-id Deprecated. Use storage add instead.
disk beacon enclosure-id.disk-id
disk expand Deprecated. Use storage add instead.
disk failenclosure-id.disk-id
disk multipath
disk port
disk rescan [enclosure-id.disk-id]
disk show detailed-raid-info Deprecated. Use disk show state and storage
show instead.
disk show failure-history
disk show raid-info Deprecated. Use disk show state and storage
show instead.
disk show reliability-data
disk unfail
enclosure beacon
Page 39 of 44
Unsupported Command or Command Option Notes
enclosure show all [enclosure] This command is supported, but not with the
enclosure argument.
enclosure show chassis
enclosure show controllers enclosure This command is supported, but not with the
enclosure argument.
enclosure show cpus [enclosure] This command is supported, but not with the
enclosure argument.
enclosure show fans
enclosure show io-cards [enclosure] This command is supported, but not with the
enclosure argument.
enclosure show memory [enclosure] This command is supported, but not with the
enclosure argument.
enclosure show nvram
enclosure show powersupply
enclosure show summary
enclosure show temperature-sensors
enclosure show topology
enclosure test topology
filesys archive
filesys clean update-stats Deprecated. Use filesys show space instead.
filesys encryption
filesys encryption passphrase change Deprecated. Use system passphrase change
instead.
filesys retention-lock Deprecated. Use mtree retention-lock instead.
filesys show compression tier The tier option is not supported.
filesys show history Deprecated. Use filesys show compression
daily instead.
filesys show space
ipmi The archive-unit and tier options are not
supported in DD VE.
license The license commands are not supported because
DD VE uses new elicense commands.
mtree retention-lock
mtree show compression mtree_path tier
net aggregate
net config ifname type cluster
net create interface virtual-ifname
net create interface physical-ifname vlan
vlan-id
net create virtual vethid
Page 40 of 44
Unsupported Command or Command Option Notes
net destroy virtual-ifname
net destroy vlan-ifname
net failover
net modify virtual-ifname bonding
{aggregate | failover
net set portnaming
ndmp
ndmpd
nfs option disable report-replica-as- Deprecated. Use filesys option disable
writable report-replica-as-writable instead.
nfs option enable report-replica-as- Deprecated. Use filesys option enable
writable report-replica-as-writable instead.
nfs option reset report-replica-as- Deprecated. Use filesys option reset report-
writable replica-as-writable instead.
nfs option show report-replica-as- Deprecated. Use filesys option show report-
writable replica-as-writable instead.
perf * module vtl
san
snapshot add schedule name [days days] Deprecated. Use snapshot schedule create
time time [,time...] [retention period] instead.
snapshot add schedule name [days days] Deprecated. Use snapshot schedule create
time time every mins [retention period] instead.
snapshot add schedule name [days days] Deprecated. Use snapshot schedule create
time time-time [every hrs | mins] instead.
[retention period]
snapshot del schedule {name | all} Deprecated. Use snapshot schedule destroy
instead.
snapshot modify schedule name {[days Deprecated. Use snapshot schedule modify
days] | time time [,time...] | [retention instead.
period]}
snapshot modify schedule name {[days Deprecated. Use snapshot schedule modify
days] | time time every {mins | none} | instead.
[retention period]}
snapshot modify schedule name {[days Deprecated. Use snapshot schedule modify
days] | time time-time [every {hrs | mins instead.
| none}] | [retention period]}
snapshot reset schedule Deprecated. Use snapshot schedule reset
instead.
snapshot show schedule Deprecated. Use snapshot schedule show instead.
storage add tier
storage add enclosure enclosure-id
storage add disk enclosure-id.disk-id
Page 41 of 44
Unsupported Command or Command Option Notes
storage remove enclosure enclosure-id
storage remove disk enclosure_id.disk-id
storage show tier
system firmware
system option set console
system passphrase
system retention-lock
system sanitize
system show anaconda
system show controller-inventory
system show nvram
system show nvram-detailed
system show oemid
system upgrade continue
user
user change priv Deprecated, with no replacement.
vtl lunmask Deprecated. Use vtl group instead.
vtl lunmask add Deprecated. Use vtl group add instead.
vtl lunmask del Deprecated. Use vtl group del instead.
vtl lunmask show Deprecated. Use vtl group show instead.
Performance Troubleshooting
You can check DD VE performance statistics by using the features of the vSphere client Performance
tab, the esxtop command on the ESXi server, and the resxtop command in the vSphere Management
Assistant (vMA).
You can also use the perf show and disk benchmark commands in DD OS to monitor and
benchmark performance. See Extensions to DD OS for DD VE for information about these commands.
Figure 10 shows a Performance chart in the vSphere client.
Page 42 of 44
Figure 10 Performance Chart in the vSphere Client
Note: The controls and names for these statistics and counters are quite different in some versions of the
vSphere client. See your VMware documentation for help displaying these statistics in your version of the
VMware software.
Page 43 of 44
Migrating DD VE
The virtual machine running DD VE supports live migration and cold migration in VMware vCenter
environments.
Live migration supports moving the virtual machine from one datastore to another.
Cold migration supports moving the virtual machine from one datastore to another, moving the DD VE
from one virtual host to another, or both.
Note: After changing the virtual host, verify the network adapters are connected with the correct network
label, otherwise the virtual machine will not be able to acquire an IP address. The system generates a
warning when a virtual machine host does not have the network label available.
Page 44 of 44