Dell EMC PowerProtect DDVE in VMware

Cloud
Installation and Administration Guide
7.6

May 2021
Rev. 02
Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid
the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2016 - 2021 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 trademarks of their respective owners.
 Contents
Revision history..........................................................................................................................................................................4

Preface......................................................................................................................................... 5

Chapter 1: Getting Started............................................................................................................ 6

Purpose of this guide..........................................................................................................................................................6
Audience................................................................................................................................................................................ 6
Architecture overview........................................................................................................................................................ 6

Chapter 2: Introducing DDVE ........................................................................................................8

Introducing DDVE................................................................................................................................................................ 8
DDVE features .....................................................................................................................................................................8
DDVE cloud features ......................................................................................................................................................... 8

Chapter 3: Deploying DDVE..........................................................................................................10

Introducing VMware Cloud on AWS .............................................................................................................................10
VMC system configuration requirements ................................................................................................................... 10
Deploying DDVE in VMware Cloud on AWS ............................................................................................................... 10
Configuring DDVE in VMC using DD System Manager............................................................................................. 11
Supported stream counts................................................................................................................................................ 12
VMware Cloud on AWS commands............................................................................................................................... 12
Recovering DDVE with system headswap................................................................................................................... 13
Recovering the DDVE system ........................................................................................................................................15
Expand metadata storage................................................................................................................................................ 16

Chapter 4: Administering DDVE................................................................................................... 18

Adding virtual storage ......................................................................................................................................................18
Configuring spindle groups ....................................................................................................................................... 18
Extensions to DDOS for DDVE....................................................................................................................................... 18
perf.................................................................................................................................................................................. 18
System vresource........................................................................................................................................................ 19
DDVE-only commands...................................................................................................................................................... 19
Modified DDOS commands............................................................................................................................................. 20
Unsupported DDOS commands .................................................................................................................................... 22
Troubleshooting performance issues............................................................................................................................26

Contents 3
 Revision history
Table 1. DDVE in VMware Cloud Installation and Administration Guide revision history
Revision Date Description
02 May 2021 Update for DDOS 7.6

4 Revision history
 Preface

As part of an effort to improve its product lines, we periodically release revisions of its software and hardware. Therefore, some
functions described in this document might not be supported by all versions of the software or hardware currently in use. The
product release notes provide the most up-to-date information on product features.

Purpose
This manual describes how to install, configure, and administer DD Virtual Edition (DDVE) systems.

Audience
This manual is intended for use by both system administrators and general users of DD Virtual Edition.

Related documentation
The following publications and websites provide additional information:
● DD Operating System Release Notes
● DD Operating System Initial Configuration Guide

This manual explains configuration steps that are common to hardware and virtual DD systems.
● DD Operating System OS Command Reference Guide

This manual explains how to administer DD systems from the command line.
● DD Operating System OS Administration Guide

This manual explains how to administer DD systems with the System Manager graphical user interface.

● DD Boost for OpenStorage Administration Guide

This manual explains how to use the DD Boost protocol for data transfer between backup software and DD systems.
● Avamar, DD and NetWorker Compatibility Guide: http://compatibilityguide.emc.com:8080/CompGuideApp/

This website lists Avamar and NetWorker software support for DDVE.

Where to get help

We support, product, and licensing information can be obtained as follows:

Product For documentation, release notes, software updates, or information about products, go to Online Support
information at https://support.emc.com.
Technical For technical support of this release of DDVE, go to Online Support at https://support.emc.com.
support

Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send
your opinions of this document to [email protected].

Preface 5
 1
Getting Started
This chapter includes the following topics:
Topics:
• Purpose of this guide
• Audience
• Architecture overview

Purpose of this guide

This installation guide is intended as a supplement to the DD Operating System Administration Guide, which includes content for
all DD systems. The content describes upgrading the DDVE software and using the DD System Manager to monitor DD systems
for errors, disk space, and service events.
This guide contains content specific to deploying DD Virtual Edition (DDVE) on VMware Cloud on AWS. Use this guide with the
DD Operating System Administration Guide and applicable VMware Cloud on AWS documentation.
See VMware Cloud on AWS documentation for more information.

Audience
This document is intended for data protection and storage administrators who want to use VMware Cloud to back up DD Virtual
Edition (DDVE) content. Users should know about the following technology:
● VMware Cloud Console
● SDDC in VMware Cloud on AWS
● SDDC Networking and Security
● Clusters and Resource Pools in VMware Cloud on AWS
● vSAN Storage in VMware Cloud on AWS

Architecture overview
DDVE is a virtual deduplication appliance that provides data protection for entry, enterprise, and service provider environments.
The following diagram represents the architecture of the DDVE on VMware Cloud solution.

6 Getting Started
Figure 1. Dell EMC Power Protect DD Virtual Edition (DDVE) on VMC

Legend:
1. To keep data traffic between DDVE and the S3 bucket within the AWS infrastructure, it is recommended that you create an
S3 endpoint. The S3 endpoint keeps DDVE from depending on a NAT Gateway or Public IP address to access the S3 bucket.
2. To keep data transfers secure, Dell EMC recommends a VPN connection to replicate data from an on-premises host to
DDVE in the cloud or the opposite way.
3. DDVE is categorized as a backend server. It must be kept in a private subnet with a private address. Never set a public IP
address for DDVE.
4. The S3 bucket must be created in the same region where the DDVE is running. There must be a separate bucket for each
DDVE.
5. All DDVE instances must be secured with the appropriate security group entries.
Typically SSH (Port 22) or HTTPS (Port 443) is used for DDVE inbound access.
HTTPS (443) must be allowed for outbound S3 bucket access for DDVE.
TCP ports 2049 and 2051 are used for DD Boost and replication purposes.
See the DDVE documentation for more information and for a complete list of ports.

Getting Started 7
 2
Introducing DDVE
This chapter includes the following topics:
Topics:
• Introducing DDVE
• DDVE features
• DDVE cloud features

Introducing DDVE
DD Virtual Edition (DDVE) is a software-only protection storage appliance: a virtual deduplication appliance that provides data
protection for entry, enterprise and service provider environments. Like any DD system, DDVE is always paired with backup
software.
DDVE runs the DD Operating System (DDOS), and includes the DD System Manager graphical user interface (GUI) and the
DDOS command line interface (CLI) for performing system operations.
DDVE includes the following features:
● High-speed, variable length deduplication for a 10 to 30 times reduction in storage requirements
● Unparalleled data integrity to ensure reliable recovery, and seamless integration with leading backup and archiving
applications
● DD Boost to speed backups by 50 percent
● DD Encryption for enhanced security of data
● DD Replicator for network efficient replication that enables faster time-to-DR readiness
DDVE runs on two types of platforms:
● On premises, DDVE supports VMware, Hyper-V, KVM, and VxRail.
● In the cloud, DDVE also runs in the Amazon Web Services (AWS) (cloud and gov cloud), Azure (cloud and gov cloud),
VMware Cloud (VMC) on AWS cloud platforms, and Google Cloud Platform (GCP).
For more information about the features and capabilities of DD systems (both physical and virtual), see the DD Operating
System Administration Guide.

DDVE features
Resource configurations depend on your DDVE configuration. For features for cloud configurations within the admin guide for
your specific cloud provider, see DDVE cloud features on page 8.

The DDOS Administration Guide, DD Boost OST Guide, and DD Boost for Partner Integration Administration Guide provide
additional information about the supported protocols and features.

DDVE cloud features

DDVE provides the capabilities of a cloud DD system using the following resource configuration sizes:

Table 2. DDVE on VMC resource configuration size

Type Resource configuration size
DDVE on S3 storage up to 96 TB

8 Introducing DDVE
The following sections list supported DD protocols and features in DDVE.

Supported DD protocols
● DD Boost over IP
● DD Boost FS

Supported DD features
● DD Boost managed file replication (MFR)
● Encryption
● MTree replication
● DD System Manager GUI for DDVE management
● DD Active Tier (DD Cloud Tier is not supported)
● Secure multitenancy (SMT) with Network Isolation Support
● DD Boost/BoostFS for Big Data
● Key Management Interoperability Protocol (KMIP)
● More restricted IPtables settings
NOTE: DDVE supports these replication capabilities:
● Managed file replication and MTree replication
● Replication across availability zones and regions
● Bi-directional replication between on-premises and VMC
The DDOS Administration Guide, DD Boost OST Guide, DD Boost for Partner Integration Administration Guide provide additional
information about supported protocols and features.

Introducing DDVE 9
 3
Deploying DDVE
This chapter includes the following topics:
Topics:
• Introducing VMware Cloud on AWS
• VMC system configuration requirements
• Deploying DDVE in VMware Cloud on AWS
• Configuring DDVE in VMC using DD System Manager
• Supported stream counts
• VMware Cloud on AWS commands
• Recovering DDVE with system headswap
• Recovering the DDVE system
• Expand metadata storage

Introducing VMware Cloud on AWS

DDVE in VMware Cloud on AWS (VMC) provides a data protection solution that enables you to protect your operational data
in the cloud and to backup and restore data into the cloud object store. This section describes first-time setup procedures, and
includes how to manage and monitor DDVE in the VMC environment.

VMC system configuration requirements

Ensure that your system meets the requirements for VMC configuration.
VMC uses standard/vSAN metadata disks.
The instance type in the following table is for logical significance.

Table 3. VMC System Requirements

Instance Type DDVE Capacity #vCPU, Memory System Disk
Standard_VMC_16 16 TB 4, 16 GB 250 GiB Root disk, 10 GiB vNVRAM
disk
Standard_VMC_32 32 TB 4, 24 GB 250 GiB Root disk, 10 GiB vNVRAM
disk
Standard_VMC_96 96 TB 8, 64 GB 250 GiB Root disk, 10 GiB vNVRAM
disk

Deploying DDVE in VMware Cloud on AWS

Prerequisites
For deploying DDVE in VMware Cloud on AWS (VMC) on S3 object store:
● Ensure that you have an AWS account that is linked to your VMware cloud account.
● The SDDC in VMC is connected to an AWS account during creation. Ensure that the subnet that is selected in the AWS
account is in the same region as the SDDC.
● Ensure that you create the AWS S3 bucket for the DDVE in the same region as the SDDC and within the same AWS
account.

10 Deploying DDVE
● Ensure that the S3 traffic from VMC is routed internally toward the AWS infrastructure. (During the SDDC in VMC setup,
you should have already linked your AWS and VPC subnet account to the VMC account.)
● Ensure that you create the S3 endpoint so that the object store traffic is routed within the AWS infrastructure.
The VMC documentation provides additional details.

Steps
1. To upload the OVF file, from the vSphere Client navigation pane, under Compute Resource Pool, right-click the DD
resource and select Deploy OVF Template.
2. Follow the steps in the Deploy OVF Template wizard:
a. Select the OVF template.
b. Select the virtual machine name and folder where you want to deploy the DDVE instance.
c. Select the compute resource pool. It may be one of the nodes in the cluster or a pre-configured resource pool. Ensure
that the compatibility checks succeed.
d. Review and verify the template details.
e. Select the deployment configuration.
f. Select the storage for the metadata disks.
g. Select the parameters for the network.
h. Review the configuration details and exit the wizard.
3. Monitor the progress of the deployment under Recent tasks.
4. While the DDVE instance is being deployed from the AWS console, create an AWS S3 bucket.
NOTE:
● To avoid additional costs and potential performance issues, ensure the S3 bucket and DDVE in VMC are available in
the same region.
● Do not enable S3 versioning for the bucket that is associated with the DDVE, for the following reasons:
○ S3 versioning requires more storage and incurs increased storage costs. For example, even though the DDVE
Garbage Collection process deletes the objects that are not needed, those objects still consume storage.
○ S3 versioning can result in performance issues.

5. From the VMC console, power on the DDVE instance.

6. On the Settings page, select Add New Device and add the metadata storage.

Next steps
After deployment, do not change the virtual hardware version of the DDVE.

Configuring DDVE in VMC using DD System Manager

DD System Manager guides you through DDVE configuration in VMC.

About this task

NOTE:
● Recommended metadata storage is 10% of the total capacity.
● The default password changeme is set for DDVE in VMC. It is not required to log in to the VM web console to set a
password.
● DHCP is enabled on the DDVE system by default. If the DHCP service is available, the DDVE system receives IP
addresses from the DHCP server.

Steps
1. Log in to the DD System Manager by entering the IP address of the DDVE into the web browser.
2. For the Apply your license step, select one of the three license types available in the drop-down menu, and then click
Apply:
● Pre-install Evaluation: Provides 45 days of limited access to DDVE software for evaluation purposes and may only be
used in a non-production environment.

Deploying DDVE 11
 NOTE: If you begin the configuration with the evaluation license, but want to purchase a license later, you need the
Node Locking ID for the DDVE instance. Click Administration > Licenses to view the Node Locking ID.
● License File: Node locked license (unserved mode)
● License Server: Served mode license
3. Accept the End User License Agreement (EULA).
4. In the Configuration wizard, select File System and click Yes.
5. To configure the DDVE on S3 storage, select Configure Active Tier > Enable Object Store.
6. Enter the passphrase.
Make note of this passphrase ( you need it later).
7. Enter the S3 bucket name that is created in the same region as the DDVE instance.
8. Import the Baltimore CyberTrust Root certificate to communicate with AWS S3 Object Store.
9. Add the metadata storage.
10. Review the summary and click Submit to create the file system and enable it.
11. Review File System Creation Complete page and click OK.
12. To view the space usage and availability details for the S3 Object storage and local metadata storage, select Data
Management > File System.
13. Optional: Configure the following settings:
a. Under System settings, update the sysadmin password or configure Alert and Autosupport email settings.
b. Under DD Boost Protocol, create a DD Boost storage unit and assign an owner.
14. To configure or update the elicense on the DDVE instance, select Administration > Licenses > Replace licenses.
15. To relaunch the configuration wizard, select Maintenance > System > Configure System.

Supported stream counts

Learn about supported stream counts for the available instance types.

Table 4. Supported stream and Mtree counts

System Instance type vCPU Memory Max Stream counts
capacit (GiB) Mtree
y Read Write Replication Replication Combined
in out
16 TB Standard_VMC_16 4 16 6 30 45 45 42 60
32 TB Standard_VMC_32 8 32 14 50 90 90 82 90
96 TB Standard_VMC_96 16 64 32 50 180 180 100 180

VMware Cloud on AWS commands

VMware Cloud on AWS (VMC) enables AWS to run applications in sphere-based cloud environments while making use of AWS
services. These CLI commands have been modified for the interaction with VMC. These commands are not supported on
physical Data Domain systems.

Table 5. DDVE-only commands

Command Description
storage object-store enable Enables the object-store feature for DDVE.
storage object-store profile set Set the access credentials/profile information. Role required:
admin. When this command runs for the first time:

#storage object-store profile set

Enter access key:
Enter secret key:
Enter region:

12 Deploying DDVE
Table 5. DDVE-only commands (continued)
Command Description

Enter bucket name:

Profile is set.

storage object-store profile show Show details of the object-storage profile. Role required:
admin

#storage object-store profile show

Region: <region>
End Point: <end-point>
Bucket Name: <bucket-name>
Provider: AWS (VMware Cloud)

Recovering DDVE with system headswap

A system headswap recovers a DDVE instance from a head unit failure. The head unit is the DDVE root disk.

Prerequisites
System headswap between the same DDOS versions is recommended. When the same DDOS version is not available, system
headswap can be done with a later DDOS version. The DDOS version compatibility rules are the same as the RPM upgrade.
Ensure that the vNVRAM disk and metadata disks from system A (original system) are available for attaching to the new
instance B. If either the vNVRAM disk or any metadata disk is unavailable, use Recovering the DDVE system on page 15.

About this task

Follow these steps only to recover DDVE with a head unit (root disk) failure.

Steps
1. Create instance B with head unit (root disk only) with the same instance type as system A.
2. Detach the vNVRAM and metadata storage from the broken head unit. On the Edit Settings page of the broken head unit,
remove the vNVRAM and metadata storage.
NOTE: Do not select the checkbox Delete files from datastore.

Deploying DDVE 13
3. Attach the vNVRAM and metadata storage to instance B head unit.
a. On the Edit Settings page of instance B head unit, select ADD NEW DEVICE > Existing Hard Disk.

b. Select files from the broken head unit and add to instance B head unit one by one.
NOTE: Ensure that the vNVRAM disk is attached before attaching the metadata disks.

4. Set the system B passphrase to match the system A passphrase.

If the passphrases do not match, the headswap fails.

# system passphrase set

Enter new passphrase:
Re-enter new passphrase:
Passphrases matched.
The passphrase is set.

5. Ensure that system A is powered off.

This step is required to detach the bucket from system A and make it available to be attached with system B.
6. Run system headswap.

14 Deploying DDVE
 NOTE: The system restarts during the headswap process.

# system headswap
This command returns the system back to its prior operational
conditions. The system will be rebooted before
resuming normal operations.

** If system passphrase was set on the old head, you will

need to do one of the following after headswap completes:
- unlock the filesystem if you have encrypted data, or
- set the system passphrase if you don't have encrypted data
Are you sure? (yes|no) [no]: yes

ok, proceeding.

Please enter sysadmin password to confirm 'system headswap':

Restoring the system configuration, do not power off / interrupt process ...
Broadcast message from root (Mon Apr 30 13:44:10 2018):

The system is going down for reboot NOW!

7. Ensure that the system is running after the headswap process is complete.

# filesys status
The filesystem is enabled and running.

Recovering the DDVE system

The system recovery procedure recovers a DDVE instance from failure of the head unit, NVRAM disk, metadata disks, or any
combinations of these components. The head unit is the DDVE root disk.

Prerequisites
System recovery between the same DDOS versions is recommended. When the same DDOS version is not available, system
recovery can be done with a later DDOS version. The DDOS version compatibility rules are the same as the RPM upgrade.

About this task

Follow these steps only to recover DDVE when metadata disks or NVRAM disks are not available or failed. If both NVRAM and
metadata disks are available, then use Recovering DDVE with system headswap on page 13.

Steps
1. Create instance B with the same configuration as instance A. It must include the same memory size, maximum capacity, and
metadata disk capacity. The instance type can be a new generation type that the DDOS version supports.
2. Enable object-store.

# storage object-store enable

Object-store is enabled.

3. Set object-store profile:

a. Set the passphrase to match the system A passphrase. Otherwise, the recovery fails.
b. Set the S3 bucket name the same as system A.

# storage object-store profile set

A passphrase needs to be set on the system.
Enter new passphrase: <enter-passphrase-string-meeting-requirements>
Re-enter new passphrase: <re-enter-passphrase-string>
Passphrases matched.
The passphrase is set
DDVE is running in AWS. Role-based access will be used to access s3.
Enter the bucket name: <name-of-the-bucket>
Object-store endpoint needs the Baltimore CyberTrust Root certificate to be

Deploying DDVE 15
 imported.
Do you want to import that certificate with below fingerprint?
D4:DE:20:D0:5E:66:FC:53:FE:1A:50:88:2C:78:DB:28:52:CA:E4:74 (yes|no) [yes]:

Profile is set.

c. Follow the remaining CLI prompts.

4. Add metadata disks to the active tier to match or exceed the capacity of system A.

# storage add dev3

Checking storage requirements...done
Adding dev3 to the active tier...done
Updating system information...done
dev3 successfully added to the active tier.

5. Run system recovery precheck.

# system recovery precheck from object-store

Recovery precheck passed. Use start command to start the recovery.

6. Run the recovery.

# system recovery start from object-store

System recovery has started. Use status command to check the status.

7. Check the recovery status.

# system recovery status

System recovery is running: stage 2 of 6 (attaching object-store)

NOTE: The system reboots during the recovery process.

8. After the recovery process finishes, check the status of the file system.

# filesys status
The filesystem is enabled and running.

Expand metadata storage

Expand metadata storage by adding new metadata disks.

Prerequisites
It is recommended that you expand metadata storage by adding new metadata disks. When the total number of metadata disks
reaches its limit, you can expand metadata storage by increasing the size of existing metadata disks.
● Before expanding metadata storage, disable the file system.
● You cannot expand the first metadata disk.
● Observe the recommended increment size of 1024 GiB.
● Shrinking metadata disk size is not supported.

Steps
1. Log in to the vShpere Client. From the navigation pane, under Compute Resource Pool, find your DDVE, and stop it.
2. Right-click the VM, and select Edit Settings...
3. Select the metadata disk that you plan to expand.
NOTE: You cannot expand the first metadata disk.

4. Increase the size of the selected metadata disk (for example, from 1 TB to 2 TB).

16 Deploying DDVE
5. Click OK.
6. To increase the size of other metadata disks, repeat Step 3 and Step 4.
7. Start the DDVE.
8. To confirm the disk size change, use the Disk show hardware or Storage show all command.
9. Disable the file system with the filesys disable command.
10. Expand metadata storage with the filesys expand command.
11. Enable file system with the filesys enable command, and check file system status with filesys status command.
12. To confirm the metadata storage expansion, use the filesys show space tier active local-metadata command.

Deploying DDVE 17
 4
Administering DDVE
This chapter includes the following topics:
Topics:
• Adding virtual storage
• Extensions to DDOS for DDVE
• DDVE-only commands
• Modified DDOS commands
• Unsupported DDOS commands
• Troubleshooting performance issues

Adding virtual storage

More virtual storage can be added to the DDVE using the GUI or the CLI.

Using the GUI

In DD SM, click Hardware > Storage > Configure Storage to add the additional devices to the DDVE active tier.

Using the CLI

When you add a new virtual data disk to an existing DDOS file system, use the filesys expand command instead of the
filesys create command.

Configuring spindle groups

DDVE 3.1 and above, support 16 spindle-groups. We recommend that virtual disks from the same storage be configured with
same spindle-group number. Virtual disks with different storage should be configured with a different spindle-group number. By
default, disks are assigned with different spindle-groups. The best practice is NOT to assign spindle-group manually.
NOTE: The storage add command does not support multiple devices in one command line. As a workaround you can use
one of the following:
● # storage add dev3,dev4,dev5
● # storage add dev3-5

Extensions to DDOS for DDVE

Several DDOS commands are supported on the DDVE platform only. This section describes these commands.

perf
Collect and show DDVE performance statistics.
perf disable trace event-regexp [module {default | ddfs}]
Disable tracing of specified events.
perf enable trace event-regexp [module {default | ddfs}]

18 Administering DDVE
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.
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 DDVE.
system vresource show [current | requirements]

# system vresource show requirements

Active Tier Cloud Tier Instance
Capacity (TB) Capacity (TB) Type
------------- ------------- ---------------------------------------------
16 n/a Standard_VMC_16
32 n/a Standard_VMC_32
96 n/a Standard_VMC_96
------------- ------------- ---------------------------------------------
** The maximum allowed system capacity for active tier on block storage is 16 TB

DDVE-only commands
The following commands only work on DDVE and are not supported on physical DD systems.

Table 6. DDVE-only commands

Command Description
elicense checkout feature-license <feature- Allows user to check out the features of licenses for License
name-list> Server installation
elicense checkout capacity-license <feature- Allows user to check out the capacity of licenses
name> value <n> {TB|GB} for License Server installation. Here is sample output:
sysadmin@localhost# elic checkout capacity-
license capacity value 10 TB Checking
out CAPACITY license willl also checkout
available feature licenses. An addition 10
TB CAPACITY license will be checked out.
10 TB additional CAPACITY license has been
checked out. License(s) have been checked
out for REPLICATION, DDBOOST, ENCRYPTION.
Total 10 TB CAPACITY license is now
available on this system.
elicense checkin {<feature-name-list>| all} Allows user to check in features for licenses for License
Server installation

Administering DDVE 19
Table 6. DDVE-only commands (continued)
Command Description
elicense license-server set server {<ipaddr>
| <hostname>} port <port-number>
elicense license-server reset Returns DDVE to factory license settings.
elicense license-server show
filesys show space tier active local- Displays the usage for the metadata storage.
metadata NOTE: Some portion of the disk space is reserved for
internal metadata, such as index. The amount of reserved
space is based on the maximum capacity of the platform
and not on licensed capacity.

net hosts add Two DDVEs in different regions cannot resolve each other's
hostname. Run this command to add a host list entry.
storage object-store enable Enables the object-store feature for DDVE.
storage object-store disable Disables the object-store feature for DDVE.
storage object-store profile set Configures the object-store access profile.
storage object-store profile show Displays the object-store access profile.
storage object-store profile status This CLI lists the object-store profile information set on the
DDVE.
system vresource show [requirements] Displays the file system capacity, the number of virtual CPUs,
and the amount of memory assigned to the virtual machine
running the DDVE instance. The requirements option
displays the physical storage requirements
for DDVE.

Modified DDOS commands

The behavior of the following commands is modified on the DDVE platform:

Table 7. Modified DDOS 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 DDVE 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-file- The tenant-unit parameter is not supported.
history
ddboost file-replication show file-history The tenant-unit parameter is not supported.
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.

20 Administering DDVE
Table 7. Modified DDOS commands (continued)
Command Changes
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 DDVE system disks show the System Dev state.
disk show stats The DDVE 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>] parameter is not supported.
filesys encryption keys show The [tier {active | archive} | archive-unit
<unit-name>] parameter is not supported.
filesys fastcopy The [retention-lock] parameter is supported with
DDVE.
Retention lock compliance mode is not supported for any
DDVE.

filesys show compression The [tier {active | archive} | archive-unit

<unit-name>] parameter is not supported.
filesys show space The [tier {active | archive} | archive-unit
<unit-name> | arcjove-unit {all | <unit-
name>] parameter 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 enclosure and disk parameters are not supported.
storage remove The enclosure and disk parameters are not supported.
storage show The archive option is not supported.
system show stats NVRAM statistics are not reported, because DDVE systems
do not have physical NVRAM.
quota The tenant-unit parameter is not supported.

Administering DDVE 21
Table 7. Modified DDOS commands (continued)
Command Changes
replication MTree replication is the only type of replication supported.
snapshot The tenant-unit parameter is not supported.

Unsupported DDOS commands

The following DDOS commands and command options are not supported on the DDVE platform.

Table 8. Unsupported commands and command options

Unsupported command or command option Notes
adminaccess https generate certificate Deprecated. Use adminaccess certificate generate
instead.
alerts add Deprecated. Use alerts notify-list add instead.
alerts del Deprecated. Use alerts notify-list del instead.
alerts notify-list option set group-name
tenant-alert-summary {enabled | disabled}
alerts notify-list option reset group-name
tenant-alert-summary
alerts reset Deprecated. Use alerts notify-list reset instead.
alerts show alerts-list Deprecated. Use alerts notify-list show instead.
alerts test Deprecated. Use alerts notify-list test 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 distributed-segment- Turning off distributed segment processing (DSP) with this
processing disabled DDBoost command is not supported for DDVE on DDOS
6.1.2.x.
ddboost option show Turning off DSP with this DDBoost command is not supported
for DDVE on DDOS 6.1.2.x.
ddboost option show fc
ddboost show image-duplication Deprecated. Use ddboost file-replication show
instead.

22 Administering DDVE
Table 8. Unsupported commands and command options (continued)
Unsupported command or command option Notes
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 benchmark start Not supported by DDVE in cloud
disk benchmark show Not supported by DDVE in cloud
disk benchmark stop Not supported by DDVE in cloud
disk benchmark watch Not supported by DDVE in cloud
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 performance Not supported by DDVE in cloud
disk show raid-info Deprecated. Use disk show state and storage show
instead.
disk show reliability-data
disk disk show stats Not supported by DDVE in cloud
disk unfail
enclosure beacon
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

Administering DDVE 23
Table 8. Unsupported commands and command options (continued)
Unsupported command or command option Notes
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.
ha create Not supported by DDVE in cloud
ha destroy Not supported by DDVE in cloud
ha status Not supported by DDVE in cloud
ha failover Not supported by DDVE in cloud
ha online Not supported by DDVE in cloud
ha offline Not supported by DDVE in cloud
license The license commands are not supported because DDVE
uses new elicense commands.
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
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 report-
writable replica-as-writable instead.
nfs option enable report-replica-as-writable Deprecated. Use filesys option enable report-
replica-as-writable instead.
nfs option reset report-replica-as-writable Deprecated. Use filesys option reset report-
replica-as-writable instead.

24 Administering DDVE
Table 8. Unsupported commands and command options (continued)
Unsupported command or command option Notes
nfs option show report-replica-as-writable Deprecated. Use filesys option show report-
replica-as-writable instead.
perf * module vtl
san
shelf migration start Not supported by DDVE in cloud
shelf migration status Not supported by DDVE in cloud
shelf migration suspend Not supported by DDVE in cloud
shelf migration resume Not supported by DDVE in cloud
shelf migration precheck Not supported by DDVE in cloud
shelf migration option Not supported by DDVE in cloud
shelf migration finalize Not supported by DDVE in cloud
shelf migration show history Not supported by DDVE in cloud
snapshot add schedule name [days days] time Deprecated. Use snapshot schedule create instead.
time [,time...] [retention period]
snapshot add schedule name [days days] time Deprecated. Use snapshot schedule create instead.
time every mins [retention period]
snapshot add schedule name [days days] time Deprecated. Use snapshot schedule create instead.
time-time [every hrs | mins] [retention
period]
snapshot del schedule {name | all} Deprecated. Use snapshot schedule destroy instead.
snapshot modify schedule name {[days days] | Deprecated. Use snapshot schedule modify instead.
time time [,time...] | [retention period]}
snapshot modify schedule name {[days days] | Deprecated. Use snapshot schedule modify instead.
time time every {mins | none} | [retention
period]}
snapshot modify schedule name {[days days] | Deprecated. Use snapshot schedule modify instead.
time time-time [every {hrs | mins | none}] |
[retention period]}
snapshot reset schedule Deprecated. Use snapshot schedule reset instead.
snapshot show schedule Deprecated. Use snapshot schedule show instead.
storage add enclosure enclosure-id
storage add disk enclosure-id.disk-id
storage remove enclosure enclosure-id
storage remove disk enclosure_id.disk-id
system firmware
system option set console
system retention-lock
system sanitize
system show anaconda
system show controller-inventory
system show nvram

Administering DDVE 25
Table 8. Unsupported commands and command options (continued)
Unsupported command or command option Notes
system show nvram-detailed
system show oemid
system upgrade continue
user
user change priv Deprecated, with no replacement.
vserver config set host Not supported by DDVE in cloud
vserver config reset Not supported by DDVE in cloud
vserver config show Not supported by DDVE in cloud
vserver config perf-stats start Not supported by DDVE in cloud
vserver config perf-stats stop Not supported by DDVE in cloud
vserver config perf-stats status Not supported by DDVE in cloud
vtl lunmask Deprecated. Use vtl group instead.
vtl lunmask add Deprecated. Use vtl group add instead.
vtl lunmask del Deprecated.
vtl lunmask show Deprecated. Use vtl group show instead.

Troubleshooting performance issues

You can check DDVE performance statistics as follows:
● With native tools in VMC
You can also use the following to monitor benchmark performance:
● perf
Extensions to DDOS for DDVE on page 18 provides more information about commands.

CPU Performance
The two key statistics for CPU performance are:
● CPU usage—CPU usage as a percentage during the interval
● CPU ready—The percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical
CPU. This counter might not be displayed by default.
If these counters are high, there may be a performance problem on the hypervisor host.

Memory Performance
● Memory swapping—The key statistic for memory performance, which is the current amount of guest physical memory
swapped out to the virtual machine’s swap file.

Virtual Disk Performance

The key statistics for virtual disk performance are:
● I/O throughput—A decrease in these values indicates a performance issue.
● I/O latency—An increase in read and write latency values indicates a performance problem.

26 Administering DDVE
Failed commands—An increase in the average number of outstanding read and write requests indicates a performance problem.

Administering DDVE 27