Compilado PowerProtect DES-DD23
Compilado PowerProtect DES-DD23
CONCEPTS AND
FEATURES
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Internal Use - Confidential
Table of Contents
Appendix ................................................................................................. 49
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 1
Introduction to PowerProtect DD
Introduction to PowerProtect DD
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 3
Introduction to PowerProtect DD
7 Tapes are physically transported and stored offsite for archival and disaster
recovery purposes. If there is a negative event in the data center, moving tapes
offsite prevents the loss of backup data.
8Data recovery requires a manual process of transporting the tapes back to the
primary storage device in the data center.
Primary
Storage
Speed
Restore
Process
Capacity Backup
Servers Management
Server
Tape
Cost
Transport
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 5
Introduction to PowerProtect DD
10 Sends only deduplicated data across the network to reduce bandwidth required
15If clients do not back up directly to the PowerProtect DD appliance using Avamar
or Networker, the backup servers preserve the data on the PowerProtect DD
appliance. Deduplication greatly reduces the data footprint before the data is
backed up. Global compression technology combines an exceptionally efficient
high-performance inline deduplication technology with a local compression
technique. The reduced data footprint allows data to be retained on-site for longer
periods and allows transfer across the network for archival. If regulatory or
corporate policies require tape backups, tape backups can be incorporated into a
PowerProtect DD environment.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 7
Introduction to PowerProtect DD
Archive Applications
Servers
Enterprise Applications WA
N
Backup
Management
Server
Current Models
3 5
2 4
DDVE is agile, it is 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.
2: The DD3300 is a small and robust protection storage platform, ideal for both
SMBs, and branch or departmental data protection for larger enterprises. The
DD3300 with Cloud Tier can back up a logical capacity up to 4.8 PB in the cloud
with extensive API support.
3: The DD6900 offers 1.3 times greater system scale than its predecessors and
can backup up to 288 TB usable capacity. That usable capacity is expanded to up
to 576 TB with Cloud Tier.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 9
Introduction to PowerProtect DD
4: The DD9400 has a throughput up to 57 TB per hour and delivers scalability 2.5
times greater than previous generations. It can backup up to 768 TB of usable
capacity, with up to 1.54 PB usable with Cloud Tier.
Expansion Shelves
Listed are the capacities and compatibilities of the options for the expansion
shelves.
1. ES40
2. DS60
The DS60 (Dense Storage) shelf supports 3 TB, 4 TB, or 8 TB SAS drives in
15 drive increments, up to 60 drives per shelf. DS60 supports DD6900,
DD9400, and DD9900 systems. 8 TB SAS drives are only supported on the
DD9400 and DD9900.
3. FS25
The FS25 (Flash Storage) SSD shelf is a solid-state expansion shelf that is
used exclusively for the metadata cache in a PowerProtect DD system. The
FS25 is supported on the DD6900, DD9400, and DD9900. The FS25 is only
supported on the DD6900 and DD9400 in a DD high availability (DD HA)
configuration.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 11
Introduction to PowerProtect DD
Hardware Features
Documents for specific hardware models are published on the Dell EMC support
site.
DDVE Evaluation18
18 Dell EMC offers a DDVE evaluation license for a limited 500 GB capacity. The
evaluation license includes DD Boost, Replication, and Encryption with no set
expiration. This license can be replaced with larger capacity licenses if needed – up
to a maximum of 96 TB. Other limited time evaluation licenses are also available.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 13
Introduction to PowerProtect DD
DDOS has a wide range of features to protect sensitive data. Most of the features
that are listed are covered in more detail later in the course.
4. BoostFS
19 Features that are supported only on DDVE are the deployment assessment tool,
virtual resource monitoring, and RAID-On-LUN.
20Features that are optimized for use with DDVE are stream counts, MTree counts,
the DD System Manager, IPv4, and IPv6.
21Features that are supported on DDVE include DD Boost, CIFS, NFS, Encryption,
and Replication.
The Cloud Tier feature enables the movement of inactive data from the active
tier to a low-cost and a high-capacity object storage like a public, private, or
hybrid cloud. This mechanism is highly efficient for long-term data retention.
During the process of data movement, only the unique and deduplicated data
is sent from the PowerProtect DD system to the cloud. This process ensures
that the data being sent to the cloud occupies as little space as possible. Using
less space in the cloud results in a lower TCO over time for long-term storage.
6. DD Replicator
7. DD Boost
8. Encryption
Encryption software option encrypts all data on the system using an internally
generated encryption key. Optionally, an external key manager may be used.
9. DD Retention Lock
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 15
Introduction to PowerProtect DD
If there is a system failure, the DD HA feature lets you configure two protection
systems as an Active-Standby pair, providing redundancy. DD HA keeps the
NVRAM of the active and standby systems synchronized. If the active node
were to fail due to hardware or software issues, the standby node can take
over services and continue where the failing node left off.
Electronic Licensing
Management
System
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 17
Architecture and Technology Overview
Backup
Management
Administration
Server
Clients
Servers LAN
or
WAN
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 19
Architecture and Technology Overview
The DDOS has a file system for system and administrative files and another for
storing backup data. System files are stored in the /ddvar directory, and backup
data is stored in an MTree in the /data/col1 folder.
/data
/ddvar
/col1
/core
/backup
/log
/HR
/support
/Sales
/releases
/Support
DDOS Deduplication
2: The stream is divided into variable-length segments, and each is given a unique
ID or fingerprint.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 21
Architecture and Technology Overview
3: Filter: Summary vector and segment locality techniques in RAM (inline) are
used to identify 99% of the duplicate segments before storing to disk. If a segment
is a duplicate, it is referenced and discarded. If a segment is new, the data is
grouped and compressed.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 23
Architecture and Technology Overview
DIA is an important DDOS technology that provides safe and reliable storage. It
protects data from loss due to hardware and software failures.
DDOS is built to ensure that you can reliably recover your data with confidence. Its
elements consist of an architectural design which provides data invulnerability.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 25
DD Operating System Features and Capabilities
DD Boost
Avam NetWork NetBack Backup vRang NetVa Veea VDP Data Greenpl RMA SAP SAP DB2 SQL
Exec Advance Protect HAN
App
Server
Supported over
Dell EMC Avamar and NetWorker support DD Boost over LAN, SAN, and WAN. Other leading
backup and enterprise applications support DD Boost over LAN or SAN.
22 DD Boost is a private protocol that is more efficient than CIFS or NFS. DD Boost
distributes parts of the deduplication process out of the PowerProtect DD system
and into the backup or application server enabling client-side deduplication. DD
Boost can speed backups by up to 50% and enables more efficient resource
utilization, including reducing the impact on the server by 20% to 40%. DD Boost
also reduces the impact on the network by 80% to 99%.
23PowerProtect App Direct provides application owners control and visibility of their
own backups to PowerProtect DD systems using their native utilities.
24DD Boost for backup applications allows the application to control the replication
process with full catalog awareness of both the local and remote copies of the
backup.
Replication
Replication
Destination
Source PowerProtect
PowerProtect DD
DD
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 27
DD Operating System Features and Capabilities
Cloud Tier
What is Cloud
Tier?
DD Retention
Lock Support
Encryption
with Cloud
Tier
Replication
Support
Supported
Cloud
Providers
BoostFS
What is BoostFS?25
Application Support26
Boost FS Profiler27
26Third-party backup applications can avoid the cost and effort of integration with
the DD Boost APIs by directly accessing the mount points. This method allows the
customers to use the DD Boost feature without integrating their applications with
DD Boost APIs. The third-party applications that are supported in this release are:
CommVault, MySQL, and MongoDB.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 29
DD Operating System Features and Capabilities
PowerProtect DD High Availability (DD HA) uses dual Dell EMC PowerProtect DD
nodes that are loosely coupled into a single highly available system. When there
are software or hardware failures on individual nodes, the overall system and its
services remain available to external applications. DD HA reduces (and sometimes
eliminates) down time in the event of a failure.
DD HA uses:
• Dual head units.
• A single set of shared storage.
• Both head units and nodes that are configured in an active/passive setup.
One of the nodes is active and running an instance of DD File System (DDFS)
handling all ingests, restores, replication, and cleaning. The second node is a
standby and in normal operation remains almost idle. If the active node
experiences a fault, such as a DDFS panic, failover occurs automatically, to the
standby node.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 31
DD Operating System Features and Capabilities
DD Retention Lock
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 33
DD Operating System Features and Capabilities
The SMT feature for the DD Operating System allows enterprises and service
providers to deliver data protection-as-a-service.
DD VTL software eliminates the challenges of physical tape storage. DD VTL can
emulate up to 60 or more virtual tape libraries with up to 1080 virtual tape drives,
and unlimited tape cartridges.
Dell EMC has qualified DD VTL with leading open systems and IBM enterprise
backup applications. It integrates without disrupting existing Fibre Channel storage
area network (SAN) backup environments.
Any Dell EMC PowerProtect DD system running VTL protocol can also run other
backup operations simultaneously using NAS, NDMP, and DD Boost protocols.
Using PowerProtect Data Domain Replication software that you can vault virtual
tape cartridges over a wide area network (WAN). Replicate your data to a remote
site for disaster recovery, remote office backup and recovery, or multisite tape
consolidation.
Disk-based network storage provides a shorter RTO by eliminating the need for
handling, loading, and accessing tapes from a remote location.
DD VTL Tape Out to Cloud feature offers the ability to store offsite and retrieve
tapes for long-term retention (LTR) use cases.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 35
DD Operating System Features and Capabilities
Data Security
PowerProtect DD systems can keep data secure using data encryption, data
sanitization, and Cyber Recovery solution.
DDOS can be configured for user access to the system for administrative tasks.
Access can be configured to use the FTP, FTPS, HTTP, HTTPS, SSH, SCP, and
Telnet protocols. Only SSH and HTTPS are active by default.
There are six different user access roles in DDOS. To learn more, click each user.
1 2 3 6
4 5
1: The Admin role is used to administer the entire PowerProtect DD system. The
Admin role is designed so you can create and destroy data that is stored on Dell
EMC PowerProtect DD systems. This design does not include any function to
recover data that was removed through the Admin role.
2: Users with the Security role can monitor the system, set up security officer
configurations, and manage other security officer operators.
4: All administrative privileges except the ability to perform data delete operations
are included with the Limited-Admin role. This exception prevents a potentially
malicious administrator from deleting any data from Dell EMC PowerProtect DD
systems.
5: Users assigned the Backup Operator role can monitor Dell EMC PowerProtect
DD systems and create snapshots. Backup Operator role can import and export
tapes to a VTL library, and move tapes within a VTL library.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 37
DD Operating System Features and Capabilities
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 39
DD Operating System Features and Capabilities
Storage Migration
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 41
DD Operating System Features and Capabilities
29The minimally disruptive upgrade (MDU) feature lets you upgrade specific
software components or apply issue fixes without a system reboot. Only those
services that depend on the component being upgraded are disrupted, so the MDU
feature can prevent significant downtime during certain software upgrades. Not all
software components qualify for a minimally disruptive upgrade; such components
must be upgraded as part of a regular DDOS software upgrade. A DDOS software
upgrade uses a large Red-hat Package Manager (RPM) upgrade bundle, which
performs upgrade actions for all DDOS components. MDU uses smaller component
bundles, which upgrade specific software components individually.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 43
PowerProtect DD Management Overview
Direct Access
The initial installation and configuration of the DDOS is done using direct access to
the hardware. Access the system through a serial connection or directly attaching a
keyboard and monitor to the system.
More Support
Remote Access
After the initial configuration is done, you can use the SSH or Telnet (if enabled),
IPMI, or SOL utilities to access the system using remote CLI commands.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 45
PowerProtect DD Management Overview
Movie:
System administrators use sophisticated tools like DDSM to configure and manage
Data Domain systems.
What is DDSM?32
You can access the System Manager from many popular web browsers 34.
34 You can use web browsers such as Google Chrome™, and Mozilla Firefox™.
Movie:
Avamar Server
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 47
Appendix
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 49
Appendix
Connectivity
Connectivity features include USB ports for connecting a keyboard and mouse, a
VGA port for connecting a monitor, and serial and Ethernet connectivity. Many
systems include mini-SAS ports to connect expansion shelves to increase capacity
and Fibre Channel for SAN connections.
For repairs in the field, access to the command line interface to shut down, restart,
and run diagnostics is usually through the serial port.
6
1 3 4 5 2
5: USB ports - This ports are 9 pins and 3.0 complaint and enable you to connect
USB devices to the system.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 51
Appendix
Redundancy
Components under high mechanical or electrical stress such as spinning drives,
fans, and power supplies are provided with N+1 redundant configuration. N+1
redundancy is a system configuration where certain components have at least one
backup component so that the system functionality continues if a part fails. This
configuration allows for uninterrupted operation at full capacity and operational
status if one component fails. For data, RAID 6 technology provides additional
protection of data integrity when up to two disks fail.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 53
Appendix
ELMS
Electronic Licensing Management System (ELMS) electronically represents feature
and capacity licenses.
ELMS on PowerProtect DD appliances, both physical and virtual, use one license
file per system. The license file contains entries for all purchased features and
capacities.
There are two categories of licenses: served and unserved. Served licenses are on
a license server, and the PowerProtect DD appliance has to check in with the
server to verify which features are licensed. Served licenses are supported only
with DDVE. Unserved licenses are the licenses that are applied directly to a
PowerProtect DD appliance.
The following are some of the features that require additional licensing:
• DD Boost
• PowerProtect DD VTL
• Encryption
• DD Retention lock
• Dell EMC Cloud Tier
The new PPDD "HIGH_DENSITY CAPACITY ACTIVE" requires a license for 8TB
drives DS60 / ES40.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 55
Appendix
Administrative Access
PowerProtect DD appliances can be administered remotely over Ethernet using
various protocols.
• SSH and Telnet can be used to run CLI commands for management and setup.
Telnet is disabled by default.
• HTTPS and HTTP can be used to access the Data Domain System Manager to
perform management and setup tasks. HTTP access is disabled by default.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 57
Appendix
Client Direct
Some backup appliances and applications, such as Dell EMC NetWorker and
Avamar, have a client direct feature allowing direct access to the PowerProtect DD
appliance over Ethernet. Both NetWorker and Avamar use the DD Boost protocol
with their client direct feature.
Backup and archive media servers can use the following protocols to send data to
a PowerProtect DD appliance over Ethernet:
• CIFS
• NFS
• DD Boost
• NDMP
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 59
Appendix
Fibre Channel
If a supported FC HBA is installed on the PowerProtect DD appliance, the system
can be connected to a vDisk (Virtual Disk Device) for Storage Direct solution or a
Fibre Channel system attached network and use the PowerProtect DD VTL and DD
Boost protocols for backup operations.
If the DD VTL option is licensed, the backup or archive server sees the
PowerProtect DD appliance as one or multiple DD VTLs.
Replication
The data is written to the backup file system on the PowerProtect DD appliance.
Physical separation of the replication traffic from backup traffic can be achieved by
using two separate Ethernet interfaces on the PowerProtect DD appliance. This
separation allows backups and replication to run simultaneously without network
conflicts.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 61
Appendix
ddvar
The /ddvar file system is a ext3 (Third Extended file system) which stores
administrative files, core and log files, generated support upload bundles,
compressed core files, and .rpm (Red Hat package manager) upgrade package
files.
The /ddvar file system keeps the administrative files that are separated from data
storage files.
• Stores core files, logfiles, support upload bundles, and upgrade packages.
• Cannot be renamed or deleted.
• Does not provide access to all subdirectories.
MTree
The Managed Tree (MTree) file structure is the destination to store user data. It
provides a root directory for user data. You can configure your backup application
to a specific MTree and organize backup files. MTree provides more granular
space management and reporting. MTrees simplify management of several
features including replication, snapshots, quotas, and retention lock. These
operations can be performed on a specific MTree rather than on the entire file
system.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 63
Appendix
Replication Features
Replication
Destination
Source PowerProtect
PowerProtect DD
DD
When replicating over untrusted networks, Replication can encrypt sensitive data.
This encryption can be enabled on all or for only a selected portion of the replicated
dataset.
You can also consolidate data from up to 270 remote sites by simultaneously
replicating data to a single, large PowerProtect DD system.
You can set up a PowerProtect DD system for managed file, directory, MTree, or
collection replication. DDVE supports only managed file and MTree replication.
Dell EMC PowerProtect DD systems and DDVE support managed file replication.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 65
Appendix
Directory Replication
Directory replication transfers deduplicated data within a Data Domain file system
directory that is configured as a replication source. Data is copied to a directory
configured as a replication destination on a different PowerProtect DD system.
MTree Replication
MTree replication is used to replicate MTrees between PowerProtect DD systems.
Periodic snapshots are created on the source. The differences between the
snapshots are transferred to the destination by using the same cross-site
deduplication mechanism used for directory replication.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 67
Appendix
Collection Replication
Collection replication performs whole-system mirroring in a one-to-one topology.
Collection replication continuously transfers changes in the underlying collection,
including all logical directories and files of the file system.
Collection replication does not have the flexibility of the other replication types.
Collection replication can provide higher throughput and support more objects with
less overhead, which may work better for high-scale enterprise cases.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 69
Appendix
DD Retention Lock
The Cloud Tier feature supports the DD Retention Lock feature, and meets all the
regulatory and compliance policies.
Encryption at the active tier level is applicable only if encryption is enabled at the
system level. The system level encryption is a licensed feature.
The cloud units have separate controls for enabling encryption. The encryption of
Data at Rest is enabled by default in the cloud. If needed, users can disable
encryption.
Once the data is in the cloud tier, the encryption status cannot be changed. So the
decision to encrypt the data or not to encrypt must be made before sending any
data to the cloud.
The complete process of data transfer between a PowerProtect DD system and the
cloud is done over a secure HTTP connection.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 71
Appendix
Replication Support
Cloud tier can be enabled on both source and target PowerProtect DD systems. If
the source system is cloud tier-enabled and the data is migrated to the cloud, then
data must be read from the cloud for replication. A replicated file is always written
on the active tier on the destination system even if cloud tier is enabled.
Managed file replication and MTree replication can be implemented on cloud tier-
enabled systems with latest DDOS. Directory replication works only on the
/backup MTree, thus the cloud tier feature does not effect directory replication.
Collection replication is not supported on cloud tier-enabled PowerProtect DD
systems.
The Replication to Cloud feature supports DDVE instances set up in the cloud
replicate from one DDVE system to another.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 73
Appendix
1 2
3 4
2: Delete an archive file using an archiving application after the retention period
expires.
Locked files cannot be modified on the PowerProtect DD system even after the
retention period for the file expires. Archive data that is retained on the
PowerProtect DD system is not deleted automatically when the retention period
expires. An archiving application must delete the file.
3: Update the default values of minimum and maximum retention periods per
MTree. The default values of minimum and maximum retention periods are 12
hours and 5 years respectively.
With Retention Lock Governance edition, IT administrators can meet secure data
retention requirements. If corporate governance policies change, administrators
keep the ability to update the retention period. For example, an administrator could
revert the locked state of a file on a specified path name inside an MTree. They
could also delete an MTree enabled with Retention Lock Governance.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 75
Appendix
2 3 4
1
Use dual sign-on to extend the retention periods for an MTree, rename the MTree.
You can also use dual sign-on to delete the Retention Lock Compliance license
from the PowerProtect DD system. Use dual sign-on to secure the system clock
from illegal updates.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 77
Appendix
Overview
SMT for the DDOS is a software feature that enables secure isolation of many
users and workloads on a shared system. As a result, the activities of one tenant
are not visible or apparent to other tenants. This capability improves cost
efficiencies through a shared infrastructure. SMT provides each tenant with the
same visibility, isolation, and control that they would have with their own stand-
alone Dell EMC PowerProtect DD system.
A tenant may be one or more business units, or departments hosted onsite for an
enterprise or large enterprise. For example, Finance and Human Resources
sharing PowerProtect DD system. Each department would be unaware of the
presence of the other.
SMT features:
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 79
Appendix
Terminology
In SMT terms, the landlord is the storage admin or the DD Administrator. The
landlord is responsible for managing the PowerProtect DD system. The landlord
sets up the file systems, storage, networking, replication, and protocols. They are
also responsible for monitoring overall system health and replace any failed
hardware as necessary.
A tenant is responsible for scheduling and running the backup application for the
tenant customer. A tenant also manages their own tenant-units including
configuring backup protocols and monitoring resources and stats within their
tenant-unit.
Tenant-units are logical containers for MTrees. They also contain important
information, such as users, notification groups, and other configuration elements.
Other tenants cannon view or detect tenant-units not belonging to them. This type
of privacy ensures security and isolation of the control path, when running multiple
tenants simultaneously on the shared infrastructure.
Architecture
This example shows two companies Red and Blue share the same PowerProtect
DD system. Tenant units and individual data paths are logically and securely
isolated from each other and are managed independently. Tenant users can
backup using their application servers to Data Domain storage in secure isolation
from other tenants on the PowerProtect DD system.
Tenant administrators can perform self-service fast copy operations within their
tenant units for data restores as needed. Tenant administrators can monitor data
capacity and associated alerts for capacity and stream use.
The landlord responsible for the system monitors and manages all tenants in the
system, and has visibility across the entire system. They set capacity and stream
quotas on the system for the different tenant units, and report on tenant unit data.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 81
Appendix
Benefits
Logical data isolation allows providers to spread the capital expenditure and
operational expenditure of a protection storage infrastructure across multiple
tenants. Data isolation is achieved by using separate DD Boost users for different
MTrees or by using the access mechanisms of NFS, CIFS, and DD VTL.
Metering and Reporting enable a provider to ensure that they are running a
sustainable business model. Reporting is important in a multitenant environment so
the provider can track usage on the shared PowerProtect DD system.
Similarly, for other protocols such as CIFS, NFS, and DD VTL, the native protocol
level access control mechanisms can be used to provide isolation.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 83
Appendix
Encryption
The Encryption software option encrypts all data on the system using an internally
generated encryption key. This encryption key is static, and the user cannot change
it.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 85
Appendix
Data Sanitization
The Cyber Recovery software runs in a secure, air-gapped 'vault' environment. The
Cyber Recovery Vault (CR Vault) is physically isolated from an unsecure system or
network. It provides management tools and technology to automate the creation of
restore points that are used for recovery or security analytics. The software is built
on a secure microservices architecture.
A primary storage system replicates its data over an air-gapped link to the Cyber
Recovery environment. The data that is in the CR Vault can be analyzed and
checked for signs of tampering. If the copied data is deemed to be good, it is saved
as an independent full backup copy that can be restored if needed. If this data must
be restored, data can be sent out of the Cyber Recovery environment and back to
the production environment.
With the Cyber Recovery software, you can create, run, and monitor policies that
protect your data.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 87
Appendix
Overview
Customer Environment Dell EMC Backend Environment
Support Analyst
Public
Internet
(https)
Dell EMC Secure Remote Services, is a two-way remote connection between Dell
Customer Service and Dell products. This connection enables remote monitoring,
diagnosis, and repair. Secure Remote Services assures availability and
optimization of the Dell EMC infrastructure, and is a key component of Dell EMC
industry-leading Customer Service. The connection is secure, high speed, and
operates 24x7.
Secure Remote Services is the remote service solution application that is installed
on one or more customer-supplied dedicated servers. For devices associated with
a particular service, Secure Remote Services is the single point of entry and exit for
all IP-based remote service activities.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 89
Appendix
ConnectEMC
In general, the system sends Autosupport alerts and alert-summaries to Dell EMC
Support. An e-License is required if the system is a physical Dell EMC
PowerProtect DD system or DDVE.
Configure network security only for Secure Remote Services gateway instead of
multiple systems.
The Secure Remote Services GUI supports DD HA. The configuration is similar to
the non-HA systems with the addition of the HA Peer IP which is a required field.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 91
Appendix
When migrating storage to new storage, system processes such as data access,
expansion, cleaning, and replication are unaffected.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 93
Appendix
More Support
The DDOS Command Reference Guide provides information for using the
commands to accomplish specific administration tasks. Each command also has an
online help page that gives the complete command syntax. Help pages are
available at the CLI using the help command.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 95
Appendix
Some of the capabilities of remote power management that are supported through
iDRAC are:
• Running diagnostics
• Installing, upgrading, or reconfiguring the DDOS
• Accessing the BIOS
• Viewing valuable POST and boot messages
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 97
Appendix
In contrast, the DDSM is primarily a single system management tool. DDSM does
not aggregate storage or performance data from multiple systems, as provided by
DDMC.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 99
Glossary
iDRAC
Dell Remote Access Controller
RAID
Redundant Array of Independent Disks
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 101
PowerProtect DD Concepts and Features
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 102
POWERPROTECT DD
HARDWARE
INSTALLATION
PARTICIPANT GUIDE
PARTICIPANT GUIDE
PowerProtect DD Hardware Installation-Participant Guide
Preparing to Install
Systems Overview
5
2 3 4
DDVE is agile, it is 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 16
TB.
2: The DD3300 is a small and robust protection storage platform, ideal for both
SMBs, and branch or departmental data protection for larger enterprises. The
DD3300 with DD Cloud Tier can back up a logical capacity up to 4.8 PB in the
cloud with extensive API support.
3: The DD6900 offers 1.3 times greater system scale than its predecessors and
can backup up to 288 TB usable capacity. That usable capacity is expanded to up
to 864 TB with DD Cloud Tier.
4: The DD9400 has a throughput up to 57 TB per hour and delivers scalability 2.5
times greater than previous generations. It can backup up to 768 TB of usable
capacity, with up to 2.3 PB usable with DD Cloud Tier.
Basic Topology
Topology
Expansion Shelf
Racked Units
Fibre Channel
SAS
PowerProtect DD
Controller
Serial
Management
Third-Party Switches
Installation Checklist
VGA Cable
There are various tools, supplies, and cables that you must use to install the
PowerProtect DD hardware.
For initial network connectivity, an Ethernet cable is required. Use a null modem
cable or USB-to-DB9 serial male connector for initial connection.
Log in to the system and run DDOS CLI commands with your laptop. The
recommended terminal emulation program is SecureCRT®, configured with a
5,000 line or larger buffer. Any version of SecureCRT works. If SecureCRT is not
available, use PuTTY version 0.58 or later. A 2 GB or greater USB flash memory
drive is also recommended.
• Tie wraps
• Cable wraps
Site Requirements
1. Rack
If necessary, installation may be split across more than one rack, but requires
advance site-specific planning to determine appropriate SAS or interconnect
cable lengths. Whenever possible, grouping shelves in logical sets within
contiguous rack spaces simplify the shelf-to-shelf SAS cabling.
The logical shelf spacing is divided into three or more shelf sets, labeled 1, 2,
and 3, and so forth.
2. Cables
3. Space
Plan ahead by leaving space in the rack for additional shelves based on the
maximum amount of expected storage. Leaving space enables simple,
predictable upgrades, if the site expects further expansion of storage capacity
in the future,
Safety Precautions
Documentation Resources
All documentation for PowerProtect DD appliances is on the Dell EMC support site.
Installing Hardware
PowerProtect preconfigured racks are available for most currently shipping models.
Depending on the model, the preconfigured rack can contain ES40, or DS60, and
FS25 shelves. See the Dell EMC PowerProtect DD Hardware Features and
Specifications Guide for detailed information, including performance, capacity, and
physical specifications about preconfigured systems.
See the Dell EMC PowerProtect DD Rail Kit documentation for further rail kit
information. For specific model information, see the System Mounting Procedures
Guide and the Dell EMC PowerProtect DD System Install Guide available on the
Dell EMC support page.
AC Power Distribution
Ensure the racked systems and not overload the power distribution system as the
breakers would trip. Doing so would shut down all the systems that are connected
to the power distribution system.
Preconfigured racks are shipped with one set of Power Distribution Panels (PDPs)
supporting four Power Distribution Units (PDUs). The second PDP set must be
used when power exceeds the power capacity of a single PDP. Also, an additional
Power Cord kit must be ordered and connected to building AC circuits. Using the
second set of PDPs doubles the power available to the rack.
To determine the amount of power that a rack requires, check the Dell EMC power
calculator.
When you open the box containing the PowerProtect DD appliance you will see a
screwdriver, product documentation, power cables, and a null modem cable.
You should also see an accessory kit box, and the controller or expansion shelf.
Once onsite, verify the received equipment against the order. Ask the customer for
the purchase order, if it is not in the shipping box.
An accessory kit box includes several items that are required to install the
PowerProtect DD hardware:
• Various cables
• Rail adapters
• Keys
• Bezel
• Bezel clips
• Velcro strips
An additional, extended length screwdriver may also be included for some specific
screw locations. A console null modem serial cable is included for serial console
connection.
Open and compare the components in the box with the P.O.
• System model
• Cards (HBA, NICs)
• System Cables
• Power Cables
• Licenses
In a shipment with multiple appliances, each appliance may have different licenses.
Install the correctly licensed appliance for its function. If for any reason the
equipment is not correct, immediately contact Dell EMC Support.
Types of Mounts
There are
three types of
possible
racks; a
round, a
square, or a
tapped hole
rack. The
screws that
you use to fasten the outer rails to the rack will depend on which type of rack is
used.
Each screw type is clearly labeled with the equipment kit. Use the labeled screws
provided with the appropriate rack. Use the correct mount based on the unit size,
provided rail types (sliding or nonsliding), and chassis release mechanisms.
Cage
nuts
are
only
require
d when
fasteni
ng a rail to a square holed rack. Cage nuts are not required when using a round or
tapped hole rack. Use a cage nut tool to attach the cage nut to the rack post.
To help with the rack mounting process, some systems have red D-shaped pull
handles1.
1
D-shaped pull handles are low profile, flip-down handles used for sliding the
system in and out of the rack. The handles retract against the face of the fan tray.
Expansion Shelves
PowerProtect DD appliances can use ES40, and DS60 expansion shelves to add
capacity.
The ES40 can accommodate 15 four or eight TB drives, and supports the DD6900,
DD9400, and DD9900.
The FS25 is a solid-state expansion shelf. The FS25 is used exclusively for the
metadata cache in the active or extended retention tiers of a PowerProtect DD
appliance. The FS25 contains either 10, or 15 four TB SSD drives and is used only
for metadata. On the DD6900 and DD9400, the FS25 is only supported with a high
availability configuration.
2
The DS60 ships with 60 drives installed. Depending on the capacity license
applied to the PowerProtect DD system either 15, 30, 45, or 60 drives will be
accessible.
ES40 Cables
Expansion shelves are connected to each other and to the controller with SAS
(serial-attached SCSI) cables.
• An ES40 has the same type of connector at both ends and is used to connect
ES40s to each other. The same cable is also used to connect ES40s to
controllers with SAS HBAs.
• The other type of cable has a different connector on one end and is used to
connect ES40s to controllers that have SAS I/O modules.
The connector on the ES40 is called mini-SAS. The I/O module connector is called
HD-mini-SAS. The cables with HD-mini-SAS at one end are available in 2M, 3M,
and 5M lengths. The cables with mini-SAS connectors at both ends are available in
1M, 2M, 3M, and 5M lengths.
The mini-SAS connectors are keyed and labeled with an identifying symbol: a dot
for the host port and a diamond for the expansion port.
1: ES40 Cables
DS60 Cables
The DS60 shelves use cables with HD-mini-SAS connectors at both ends to
connect the shelves to the controllers.
• Use the 3M cable in the same rack either to connect to a controller or shelf-to-
shelf.
• Use a 3M, 4M, or 5M cable when connecting a DS60 from one rack to another.
• Use the 3M shelf-to-shelf cables to connect shelves to other shelves within a
shelf set in the same rack.
• Use a 3M, 4M, or 5M cable to connect shelves to other shelves when the set
spans racks.
• Special cables must be used when attaching an ES40 to a chain with a DS60.
3
1
2 4
1: DS60 Cables
2: SAS Ports
3: DS60 backpanel
4: SAS Ports
FS25 Cables
The cable used to include the FS25 in a SAS chain is the mini-SAS type. The cable
is keyed and labeled with different host and expansion connectors in the SAS
chain. These cables are available in 1M, 2M, 3M, and 5M lengths.
The connectors are keyed and labeled with an identifying symbol: a dot for the host
port and a diamond for the expansion port. The expansion shelves are 3U in size
and the controllers that support the FS25 shelf are either 2U or 4U. When a 2U
controller is mounted in a 4U gap, it can be mounted in any of the three positions in
that gap. For more information, see the PowerProtect DD System Hardware Guide
for your specific model.
1: FS25 Cables
Shelf Cabling
PowerProtect DD
Cabling Basics
PowerProtect DD controller
Here is an example of A controller with two expansion shelves. There are some
general cabling rules for connecting expansion shelves to a PowerProtect DD
controller:
• The controller HBA port should always connect to the host port of an expansion
shelf. In other words, the host port on the expansion shelf connects upstream to
the Controller.
• The expansion port on the expansion shelf is used to connect downstream to
another expansion shelf.
• The expansion port on the last shelf should be empty. It does not connect back
to the controller.
In this example:
• Cable 1 (C1) connects from Port A on the SAS controller in Slot 7 (right) to Port
A of storage controller S-B on the first shelf.
• Cable 2 (C2) connects from Port A on the SAS controller in Slot 3 (left) to Port A
of shelf controller S-A on the last shelf.
• Cable 3 (C3) connects from Port B of S-B on the first shelf to Port A of S-B on
the last shelf.
• Cable 4 (C4) connects from Port B of S-A on the last shelf connects to port A of
S-A on the first shelf.
For more information, see the PowerProtect DD System Hardware Guide for your
specific model.
Cabling Order
This installation
order runs as
shown:
• In steps 1, 2, 3,
and 4 in this
example,
establish the
first expansion
shelf at the
bottom of each
shelf set.
Positioning
each shelf in
the rack according to the diagram shipped with the specific system. This
positioning establishes the full range of space in the racks that are required for
future expansion of capacity as needs require. It also allows for easy installation
of extra shelves into any shelf set. Install the shelf and recable so that the B
side cable from the controller is connected to the host port on the new shelf.
Interconnect cables are also added between the two shelves.
• In steps 5, 6, 7, and 8 add additional shelves from the bottom up in each shelf
set.
• Continue to add shelves in step 9, 10, and so forth, up to the maximum capacity
of the system. In this example, the system supports a maximum of 18 shelves
that are installed and positioned in two racks as shown.
When you unlock and remove the snap-on bezel from the front panel, the 15 disks
are visible. Disk numbers range from 1 to 15 as reported by system commands.
When facing the front of the panel, disk 1 is the leftmost disk and 15 is the far right
disk.
Indicators on the appliance will show disk slot numbering from 0 to 14, but the
software uses logical numbering of 1 to 15.
1 2
1: Disk 1
2: Disk 15
The following diagram is a top view diagram of the DS60 labeled drive locations.
Drives installed in the DS60 are only visible when the enclosure is pulled out of the
rack. To access the drives, pull the chassis forward from the rack, and remove the
top cover. The drives are installed in packs of 15. Packs are color coded within the
enclosure. Purple is Pack 1, yellow is Pack 2, green is Pack 3, and pink is Pack 4.
Slots are identified in columns of 12 (0 through 11) and rows of five (A through E).
There is room in the DS60 for 60 drives or 4 packs, total. A pack must contain the
same drive size. Packs of different drive sizes can be mixed within the DS60. For
example, Pack 1 may contain 15, 4 TB drives while Pack 2 may contain 15, 3 TB
drives.
Initial Configuration
You can create a system setup worksheet to document the minimum configuration
information necessary to complete the initial configuration of the PowerProtect DD
appliance.
Once the network information has been saved, you can provide additional
information in the CLI or the DD System Manager (DDSM).
Installation professionals
are strongly encouraged
to use the Pre-
Engagement
Questionnaire (PEQ).
This is a comprehensive
spreadsheet available to
all field personnel and
internal Dell EMC
employees from the Dell
EMC Global Services
Tools Information
website under the
Licensed Tools tab.
It serves as a shared document between Dell EMC and authorized customers and
partners. The spreadsheet is available for download from the internal Dell EMC
website: https://psapps.emc.com/central/solution/PEQ.
The PEQ also contains important reference charts and deliverable checklists to
help in managing the installation.
Some PowerProtect DD systems have a PSNT tag located on the rear of the
system, attached to the arm in the center of the chassis. If this tag is not present,
the product serial number is always available from the service tag located on the
front of the system.
The SN is the 14 digit alphanumeric string that accompanies the part number. This
serial number is the default system password for serial console, system manager,
and iDRAC access.
Emulator Settings
When the PowerProtect DD system boots up for the first time, the CLI configuration
wizard script starts automatically. You can also start the script manually using the
config setup command.
The first prompt asks if you want to use the GUI wizard. This is to determine if the
shortened version of the CLI wizard will be started, followed by the System
Manager Configuration wizard, or the complete CLI wizard will be used.
If the choice is yes, as shown here, the bare minimum configuration data is
collected to configure network access. The shortened CLI wizard prompts you for
the data collected in the system setup worksheet. At the end of the section, a
prompt to accept or reject the changes appears.
Once the configuration data is saved, the wizard requests the user launch the
System Manager Configuration Wizard to finalize the setup.
If you
choose not
to use the
GUI wizard
as shown
here, the
CLI wizard
starts with
the section
for license
configuration and continues to network, file system, and system configuration.
Each section will display a summary and prompt to either accept or reject the
changes just as it would in the shortened version.
The DD System Manager (DDSM) can be used to configure the same information.
The DDSM is used once the initial configuration is completed from the CLI. Using a
web browser, open the DDSM and find the wizard by selecting Maintenance >
System > Configure System.
The individual sections are listed on the left and the details of the sections are on
the right. You may skip sections if you want, with the exception of the License
Configuration section. Both configuration wizards will suggest a reboot when
complete. If the time zone is changed during the configuration, then the reboot is
mandatory.
For each expansion shelf installed in the rack, such as the DS60, you must apply a
shelf capacity license.
ELMS on PowerProtect DD systems use one license file per system. The license
file contains a single license for all purchased features.
Addi
tiona
l
stora
ge
requi
res
the
appr
opria
te
licen
ses
and sufficient memory to support the new storage capacity. The system generates
error messages if more licenses or memory is needed.
When the licenses are added, the expansion shelf enclosures must be added and
licensed with a DD Expansion Storage license. This procedure is performed in the
System Manager GUI.
From the home screen navigate to Hardware > Storage > Overview and click
Configure. Recently installed shelves will appear in the Addable Storage section
where they can be added to the appropriate tier.
In the CLI, use the storage add enclosure command to add storage to either
the active or cloud tier. For additional information read the Dell EMC DDOS
Administration Guide.
From the command line, display the RAID group information for the active tier of
each shelf by entering the storage show all command. The rest of the disks
should report that they are either available or spare disks.
In order for the file system to make use of all of the available space in the active
tier, enter the command filesys expand. Begin the file system operations with
the filesys enable command.
Verify the state of the file system and disks by entering the filesys status
command. It should show as available and running.
After a shelf is added to the file system, enter the filesys show space
command to view the total size, amount of space used, and available space for
each file system resource, such as data, metadata, and index.
Once the expansion shelf is installed and online, perform a few steps to verify the
state of the file system and disks. Check the status of the SAS HBA cards by
entering the disk port show summary command.
command displays the connected enclosure IDs for each port, such as 2 and 3,
and the status changes to online.
After adding expansion shelves, verify the state of the disks with the command
disk show state. See the legend in the command output for disk state
definitions. Some disk states include spare, available, unknown, and
reconstructing. The progress and time remaining will also be displayed for disks
that are in a reconstructing state.
For disks labeled unknown instead of spare in the output of the disk show
state command, enter the disk unfail command for each unknown disk. For
example, if disk 2.1 is labeled unknown, enter the command: disk unfail 2.1
Other Configuration
iDRAC
iDRAC gives system administrators the ability to configure a system as if they were
at the local console.
To access one PowerProtect DD appliance from another, you can use the DD
System Manager. Go to Maintenance > IPMI and select Login to Remote
System. Enter the IPMI IP address or DNS name, username, and password for an
IPMI user and click Connect.
When connected, you can use an HTML web interface to go to the default iDRAC
IP address 192.168.0.120.
The dedicated Ethernet port is configured with any available IPMI IP address.
Configure IPMI on a separate management network in case the data LAN goes
down. The separate management network should be used only for IPMI and SOL
access3. The dedicated Ethernet port name is bmc0a. The other Ethernet ports like
eth0 and eth1 on the system are used only for data and normal operations.
3
Enabling SOL disables the serial console.
Add IPMI users by clicking the Add button in the IPMI Users section. The IPMI
users are independent of other users on the appliance. Usernames and passwords
that are used for IPMI users can be different from any other users who are created
on the system.
You can also configure the target PowerProtect DD appliance using the CLI with
the ipmi config and ipmi user commands. See the Dell EMC DDOS
Command Reference Guide for complete information about using these
commands.
Configure iDRAC
To access iDRAC, ensure that you connect the Ethernet cable to the iDRAC
dedicated network port on the back panel of the system to your network.
To configure iDRAC, use web browser to connect to the default iDRAC IP address
192.168.0.120. Alternatively, you can connect directly to the iDRAC direct USB port
with a USB cable and a laptop.
Configure iDRAC
Login
Log in with the default username: admin. The default password is the system serial
number that is printed on the product serial number tag (PSNT).
Change IP Settings
You can change the iDRAC IP address in iDRAC Settings | Connectivity | IPv4
Settings.
Dashboard
Power the system off with iDRAC by selecting Dashboard > Graceful Shutdown
or by using one of these selections:
• Power Off System
• Reset System (warm boot)
• Power Cycle System (cold boot)
Note: The NM (Non-Masking Interrupt) menu item is not supported on the DD3300
appliance.
DDOS Configuration
Autosupport reports
and alert messages
help identify and solve
PowerProtect DD
system problems.
Autosupport reports
and alerts provide
timely notification of
significant issues.
Autosupport sends
system administrators,
and Dell EMC Support
a daily report of system information and consolidated status output. Information is
gathered from various system commands and entries from various logfiles. The
autosupport report contains extensive and detailed internal statistics and log
information to aid Dell EMC Support in identifying and debugging system problems.
Autosupport reports are simple text logs sent by email. Autosupport report
distribution can be scheduled, with the default time being 6:00 a.m.
Hardware Verification
Hardware Verification
Verify Hardware
After your PowerProtect DD system is installed, you should verify that you have the
correct model number, DDOS version, and serial number to ensure that they match
what you ordered.
To verify other hardware using the DD System Manager, navigate to the Hardware
section. There you can view and modify settings for the system’s storage, Ethernet,
Fibre Channel, and chassis.
Click Chassis to verify the system number, chassis number, and enclosure status.
These settings can also be monitored through the CLI.
For details on using DDOS CLI commands, see the DDOS Command Reference
Guide found on the Dell EMC Support site.
Disk Verification
You can also expand the summaries for Active Tier, Addable Storage,
Failed/Foreign/Absent Disks, and System Disks
Active Tier
When you expand the Active Tier item in the Overview tab, it displays the
information about disks in use and disks not in use.
Addable Storage
Also in the Overview tab, expand Addable Storage to see details about optional
enclosures that are available to add to the system.
The Hardware Storage section under the Enclosures tab displays a table
summarizing the details of the enclosures connected to the system.
The Disks tab displays the Disk State table with information about each of the
system disks. You can filter the disks viewed to display all disks, disks in a specific
tier, or disks in a specific group.
If you have trouble determining which physical disk corresponds to a disk displayed
in the table, you can use the beacon feature to flash an LED on the physical disk.
Disk fail functionality allows you to manually set a disk to a failed state to force
reconstruction of the data stored on the disk. Disk Unfail functionality allows you to
take a disk in a failed state and return it to operation.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
Appendix ................................................................................................. 33
Dell EMC Cloud Tier enables the movement of data from the active tier of a
PowerProtect DD appliance to low-cost, high-capacity object storage in the public,
private, or hybrid cloud. Data is moved to the cloud for long-term data retention.
Only unique, deduplicated data1 is sent from the PowerProtect DD appliance to the
cloud or retrieved from the cloud.
Backup Data
Cloud storage in the public, private,
Cloud Tier Architecture
or hybrid cloud for long-term data
retention.
Cloud Tier
Cloud Tier
Cloud Unit 1
Considerations
Cloud Unit 2
1Sending only deduplicated data ensures that the data being sent to the cloud
occupies as little space as possible.
Model Sizing
Here the supported physical memory and storage requirements for each
PowerProtect DD model.
DD3300 48 16
(8 TB
Capacity)
DD3300 48 32
(16 TB
Capacity)
DD3300 64 64
(32 TB
Capacity)
DDVE* 60 128
(64 TB
Capacity)
DDVE* 80 192
(96 TB
Capacity)
* Dell EMC Cloud Tier is supported on DDVE for on-premises implementations only.
2The minimum metadata size is a hard limit. Dell Technologies recommends that
you start with 1 TB for metadata storage and expand in 1 TB increments. The
DDVE Installation and Administration Guide provides more details about using
Cloud Tier with DDVE.
Active Tier
Data Movement
Policy Cloud Tier
Cloud Unit 1
The Dell EMC Cloud Tier is managed through a single namespace. There is no
separate cloud gateway or virtual appliance required. The native PowerProtect DD
policy management framework supports the data movement.
Cloud storage supports Dell EMC Elastic Cloud Storage (ECS), Alibaba, Amazon
Web Services S3, Google Cloud Provider, S3 Flexible provider cloud unit, and
Microsoft Azure. Extra storage is required to hold metadata associated with the
data in the cloud tier. Deduplication, cleaning, and replication operations use
metadata.
Extra metadata storage is required to support the cloud tier. The amount of
required metadata storage is based on the PowerProtect DD model.
Active Tier
Data Movement
Policy Cloud Tier
Cloud Unit 1
Cloud Unit 2
Dell EMC Cloud Tier supports one or two cloud units on each PowerProtect DD
appliance.
• Each cloud unit has the maximum capacity of the active tier3.
• Each cloud unit maps to a cloud provider4.
• Metadata shelves5 store metadata for both cloud units.
This example shows a system with an active tier and two cloud units. Each cloud
unit has a capacity equal to that of the active tier. Data that is stored on the active
tier provides local access to data and can be used for operational recoveries. The
cloud tier provides long-term retention for data that is stored in the cloud.
3You can scale the cloud tier to maximum capacity without scaling the active tier
any larger.
5The number of metadata shelves you need depends on the cloud unit physical
capacity.
The NFS, CIFS, and DD Boost protocols are supported for data movement to and
from the cloud tier.
PowerProtect DD VTL Tape Out to Cloud is supported with DDOS version 6.1 and
later. DD VTL Tape Out to Cloud supports storing the VTL vault on Cloud Tier
storage.
There is no support for vDisk pools as used with Dell EMC ProtectPoint.
PowerProtect DD Appliance
Cloud Tier
Cloud units each have their own
deduplication pools.
Cloud Unit 1
• Each cloud unit has its own segment index and metadata and thus each cloud
is a deduplication unit by itself6.
• The cloud tier uses the same compression algorithm7 as the active tier.
• Cloud deduplication does not do the packing phase.
• Cloud tier cleaning can be schedule-based or on demand8.
• The schedule for cloud tier cleaning is set relative to active tier cleaning9.
8 Cleaning of the active tier and the cloud tier cannot take place simultaneously.
9 The schedule specifies to run cloud tier cleaning after every Nth run of active tier
cleaning. By default, cloud tier cleaning runs after every 4th scheduled active tier
cleaning.
10 On-demand cleaning can be run from either the DD System Manager or CLI.
11 When all segments within a region are dead, the entire object is deleted.
12 The cloud storage is accessed to delete objects in the cloud with no live data and
to perform some copy forward of container metadata-related activities.
Secure HTTP (HTTPS) is used for the transfer of data between a PowerProtect
DD appliance and the cloud.
Active tier encryption is not required to enable encryption on the cloud tier.
13You are prompted for the security officer username and password to enable
encryption.
14Encryption of the active tier is only applicable if encryption is enabled for the
system.
Replication
You can enable Dell EMC Cloud Tier on one or both systems in a replication pair.
If the source system is Cloud Tier-enabled, data may be read from the cloud if the
file was already migrated to the cloud tier from the active tier. A replicated file is
always placed first in the active tier on the destination system even when Cloud
Tier is enabled.
17
Before sending any data to the cloud the decision to encrypt data or not must be
made.
It is possible to migrate the system data from and older appliance that is configured
with Dell EMC Cloud Tier to a newer appliance. Migrating to a newer appliance can
improve performance, add additional capacity, and provide access to new features.
The migration process migrates the active tier storage, and the locally stored cloud
tier metadata from the existing system to a new system. During the migration, the
source system operates in a restricted mode.
The procedure to initiate the Cloud Tier migration is only available through the CLI.
See the Dell EMC DDOS Administration Guide, available on the Dell EMC Support
site for more information about migrating Cloud Tier.
Configure Storage
With Dell EMC Cloud Tier storage, the PowerProtect DD appliance holds the
metadata for the files residing in the cloud18.
The cloud tier requires a local store for a local copy of the cloud metadata. To
configure Cloud Tier, you must meet the storage requirement for the licensed
capacity.
If creating a file system, the cloud tier can be enabled at the time that the new file
system is created. To create a file system, select Create File System and then
configure the active tier of the system.
In Data Management > File System, the main panel displays statistics for the
active and cloud tiers.
The statistics viewable in the DD System Manager for both the active and cloud tier
are:
• Size
• Used
• Available
• Pre-Compression
• Total Compression Factor (Reduction %)
• Cleanable
• Space Usage
To provide more information to the user, the DD System Manager displays the
reasons why the cloud storage is in error state.
19You must have Port 443 or Port 80 open to the cloud provider networks for both
endpoint IPs and provider authentication IP for bi-directional traffic. Remote cloud
provider destination IP and access authentication IP address ranges must be
enabled through the firewall.
20 Downloaded certificate files have a .crt extension. Use OpenSSL to convert the
file from .crt format to .pem. For additional information, see that the Dell EMC
DDOS System Administration Guide on the Dell EMC support site.
The links on
this page
contain
configuration
information
Alibaba Cloud Amazon Web Services Flexible Cloud
and the
S3 Tier Provider
procedure to
Framework for
create cloud
S3
units on
supported
cloud
platforms.
Overview
All interactions with cloud providers are authenticated with a signature protocol.
Support for S3 flexible cloud providers that support S3 authentication with signature
V4 is now part of DDOS.
A new field S3 Signature Version is added to display the cloud profile version.
In the output of cloud profile show, DDOS displays two possible values: s3v2
or s3v4.
Once set, the signature version of the cloud profile cannot be modified.
Movie:
Data Movement
21Used for all files older than a set number of days. For example, all files older than
90 days.
22All files older than X days, but younger than Y days. For example, all files older
than 30 days but younger than 365 days.
Agent
Recall is the act of bringing data from the cloud to the active tier. Restore is the act
of recovering data from the active tier and making it available to the client.
Data can be recalled from the cloud tier using the DD System Manager (DDSM) or
the CLI.
Tape Out to cloud storage offers the ability to store offsite and retrieve tapes for
long-term retention (LTR) use cases.
Movie:
Architecture
Metadata
Data
Active Unit Cloud Unit
Active CP Cloud CP
(metadata)
Index, container metadata,
directory manager
Metadata to support the cloud is maintained in the cloud tier shelf of the local
storage. This metadata is used in operations such as deduplication, cleaning, and
replication. Using local storage for metadata minimizes writes to the cloud. The
metadata includes the index, the Directory Manager (DM) for managing the
namespace and container metadata. Some metadata, including container
metadata, is also stored with the data in the cloud for disaster recovery purposes.
Benefits
Cloud Tier provides a scalable
solution for long-term data
storage. With Cloud Tier, users
can store up to two times the
maximum active tier capacity in
the cloud for long-term
retention of data. With cloud
tiering policies, data is in the
right place at the right time.
Data is scheduled to be moved
to the cloud using policies
based on the age of the data.
Considerations
Here are a few considerations when deciding to implement Cloud Tier:
• A cloud capacity license is required for Cloud Tier. Use the Dell EMC Electronic
License Management System (ELMS) file to apply the license.
• The Cloud Tier feature may consume all available bandwidth in a shared WAN
link, especially in a low-bandwidth configuration (1 Gbps). The Cloud Tier
feature may impact other applications sharing the WAN link.
• On systems with a dedicated management interface, reserve that interface for
system management traffic (using protocols such as HTTP and SSH). Backup
and cloud tier data traffic should be directed to other interfaces, such as eth1a.
Prerequisites
Complete the following tasks on the new system before beginning the migration
operation:
1. Verify both the source and destination systems are running DDOS 7.3.0.5 or
higher. Cloud Tier migration is not supported on DDVE instances.
2. Add a Cloud Tier license on the new system.
3. Add other feature licenses as required on the new system.
4. If a passphrase is configured on the existing system, set the same passphrase
on the new system. The passphrase store-on-disk setting should not be less
secure on the destination than on the source.
5. If encryption is configured on the existing system, set the same encryption
values including key manager settings and FIPS compliance on the new
system.
6. If automatic key rotation is configured on the existing system, disable it before
starting the migration. Reenable it on the new system after the migration.
7. If encryption is configured on the existing system, back up the key export files
from the existing system.
8. If Retention Lock Compliance is enabled on the existing system, enable RLC on
the new system.
9. Record the cloud profile and cloud unit information from the existing system.
10. Create the file system on the new system, but do not enable it.
Restricted Mode
While the PowerProtect DD appliance is in restricted mode, the active tier storage
is available for backup operations, but I/O on the cloud tier storage is not permitted.
The following operations are not permitted while the migration is in progress:
• Sending active tier data to cloud tier storage.
• Recalling data from cloud tier storage.
• Cleaning the cloud tier storage.
• Restoring files directly or reading from the cloud tier storage.
• File system cleaning on the source system.
• System sanitization cannot be performed on the source system.
• Enabling or disabling file system encryption.
• Enabling, disabling, or setting the embedded key manager or an external key
manager.
• Creating, destroying, deleting, or syncing keys from the embedded key manager
or an external key manager.
24For AWS and Azure cloud providers, download the Baltimore CyberTrust root
certificate.
Adding a Certificate
After downloading a certificate file, add the CA Certificate:
1. Go to Data Management > File System > Cloud Units.
2. Click Manage Certificates from the tool bar.
3. Click Add, and select one of the options from the Add CA Certificate for Cloud
screen.
4. Click Add.
Configuration
Regions are configured at the bucket level instead of the object level. All objects
that are contained in a bucket are stored in the same region. A region is specified
when a bucket is created, and cannot be changed once it is created.
The Alibaba Cloud user credentials must have permissions to create and delete
buckets and to add, modify, and delete files within the buckets they create.
Procedure
Configuration
AWS offers a range of storage classes. The Cloud Providers Compatibility Matrix,
available from https://elabnavigator.emc.com/eln/elnhome provides up-to-date
information about the supported storage classes.
For enhanced security, the Cloud Tier feature uses Signature Version 4 for all AWS
requests. Signature Version 4 signing is enabled by default.
The AWS user credentials must have permissions to create and delete buckets and
to add, modify, and delete files within the buckets they create.
Procedure
Configuration
The Cloud Tier feature supports qualified S3 cloud providers under an S3 Flexible
provider configuration option.
Procedure
Configuration
The Google Cloud Provider user credentials must have permissions to create and
delete buckets and to add, modify, and delete files within the buckets they create.
Procedure
Configuration
Microsoft Azure offers a range of storage account types. The Cloud Providers
Compatibility Matrix, available from
http://compatibilityguide.emc.com:8080/CompGuideApp/ provides up-to-date
information about the supported storage classes.
Procedure
The schedule can be viewed at Data Management > File System > Summary.
The data movement schedule is set at Data Management > File System > Cloud
Units > Settings > Data Movement.
If a cloud unit is inaccessible when cloud tier data movement runs, the cloud unit is
skipped in that run. Data movement on that cloud unit occurs in the next run if the
cloud unit becomes available. The data movement schedule determines the
duration between two runs. If the cloud unit becomes available and you cannot wait
for the next scheduled run, you can start the data movement manually.
For nonintegrated backup applications, you must recall the data to the active tier
before you can restore it. Backup administrators must trigger a recall or backup
applications must perform a recall before cloud-based backups can be restored.
Once a file is recalled, aging is reset and starts again from 0, and the file is eligible
based on the age policy set. A file can be recalled on the source MTree only.
Integrated applications can recall a file directly.
Recall fails if there is no space in the active tier to move the file. This decision is
made before any movement is started. Recall is per file. Dell EMC Cloud Tier
checks for existing data segments on the active tier. Only segments not present in
the active tier are invoked for recall from the cloud.
Select Data Management > File System > Summary. In the Cloud Tier section of
the Space Usage panel, click Recall, or expand the File System status panel at
the bottom of the screen. Click Recall.
The Recall link is available only if a cloud unit is created and has
data. The Recall File from Cloud dialog is displayed.
In the Recall File from Cloud dialog, enter the exact file name (no wildcards) and
full path of the file, for example: /data/col1/mt11/ file1.txt. Click Recall to
start the recall process.
Only four recall jobs are active at any given time. uUp to 1,000 recall jobs can be
queued up to run automatically as previous jobs complete. The recall queue is
automatically regenerated, so if the system is restarted during a recall the recall
continues when the system is back up.
Once the file has been recalled to the active tier, you can restore the data.
The path-name can be a file or directory; if it is a directory, all files in the directory
are listed.
Monitor the status of the recall using the data-movement status [path
{pathname | all | [queued] [running] [completed] [failed]} |
to-tier cloud | all}] command.
If the status shows that the recall is not running for a given path, the recall may
have finished, or it may have failed.
Verify the location of the file using the filesys report generate file-
location [path {<path-name> | all}] [output-file <filename>]
command.
Once the file has been recalled to the active tier, you can restore the data.
Requirements
The Dell EMC Cloud Tier feature must be licensed and enabled on either a physical
or virtual PowerProtect DD appliance. A cloud profile and cloud unit name should
be configured before using the DD VTL Tape Out to Cloud feature.
Both DD VTL and Cloud Tier Capacity licenses are required to use the DD VTL
Tape Out to Cloud feature.
The workflow for backing up and restoring data using the PowerProtect DD VTL
Tape Out to Cloud feature is as follows:
1. Perform the backup server or client configuration and user application setup.
2. Back up to primary disk storage pools
3. During backup, the data is copied while the backup server maintains the
necessary backup catalog and tracking metadata.
4. Data replicates to the DD VTL vault.
5. This replication can be onsite or geographically separated sites. The backup
server tracks the tapes in a “mountable” state.
6. Once the tapes are ready for long-term retention, they are ejected from the tape
storage pool.
7. The backup server tracks tapes in the “nonmountable” state.
8. The backup server continues to monitor the tape while the Long-Term Retention
to Cloud functionality moves the tapes to the cloud tier.
9. Once in the cloud tier vault, the backup server maintains the tape status to be
“Offsite.”
10. Restore process: The PowerProtect DD appliance recalls the tapes from the
cloud tier vault and places them in the DD VTL vault. Once the tapes are in the
vault, they can be moved to the library where the backup application can use
them.
You can manage a DD VTL using the DD System Manager (DDSM) or the
command-line interface (CLI).
End-to-End Workflow
The DD VTL Tape Out to Cloud feature uses these components in the
PowerProtect DD appliance. The user interacts with the system using the DDSM or
CLI. The DD VTL service uses the Tape Out to Cloud functionality built on the DD
file system Long-Term Retention service.
The DD file system uses NFS v3 APIs to access the DD VTL tape pool and send
the virtual tapes in the vault to the cloud tier.
The Tape selection policy is applied at the pool level and sets the age threshold for
data moving to the cloud. The minimum setting is 14 days. If the policy is set to
user-managed, the user uses a command to select one or more tapes to move at
the next scheduled data movement. If the setting is set to none, no tapes are
moved to the cloud.
The cloud data movement schedule defines how frequently vaulted tapes are
moved to the cloud. The cloud data movement schedule can be set to never, to any
number of days/weeks, or run manually.
You can find specific commands that are used to set the tape selection policy, and
cloud data movement schedule in the DDOS Command Reference Guide on the
Dell EMC Support site.
Data movement for VTL occurs at the tape volume level. Individual tape volumes or
collections of tape volumes can be moved to the cloud tier but only from the vault
location. Tapes in other elements of a VTL cannot be moved.
Use the backup application verify the tape volumes that will move to the cloud are
marked and inventoried according to the backup application requirements.
Manually select tapes for migration to the cloud tier (immediately or at the next
scheduled data migration), or manually remove tapes from the migration schedule.
After the next scheduled data migration, the tapes are recalled from the cloud unit
to the vault. From the vault, the tapes can be returned to a library.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
PowerProtect DD Implementation with Application Software-Participant Guide
Implementation Concepts
The following table is an overview of several supported backup applications and the protocols they
support for backup and recovery operations. They combine backup software solutions that support
backups over Ethernet and Fibre Channel. The table shows the protocols that are supported on
PowerProtect DD appliances for each backup application.
For a complete listing of all backup applications PowerProtect DD supports, consult the Dell
Technologies e-Lab Interoperability Navigator.
PowerProtect DD
Metadata
Backup Server
Backup Data
PowerProtect DD
Storage Node
Backup Clients
Data Center
The diagram provides a brief review of basic terminology that is associated with the backup
environment. In all configurations, there are clients, backup management servers, and a read/write
server. In some environments, the backup management and read/write functions are performed on
a single server. Networking connectivity can be Ethernet LAN or Fibre Channel SAN.
• Backup clients1
• Backup server2
• Storage node3
• PowerProtect DD4
1A node within a backup process that holds data to be backed up. A backup client
can be desktop, laptop, application server, file server, or a storage device in a
backup environment.
2The backup server is an application that schedules, manages, and operates data
backup processes on a backup client.
3The storage node is used with the backup manager in obtaining and storing
backup data. In some environments, the backup server and storage node functions
are performed on a single system.
Avamar Clients
Backup Data
Avamar Data
Metadata Store
Avamar PowerProtect DD
Server
Backup Clients
Data Center
Avamar clients5 are the machines that contain the data to be backed up to the Avamar server.
Avamar Client software is installed and running on each client. Avamar provides client software for
various computing platforms.
Avamar Administrator is a user management console software application that is used to remotely
administer an Avamar system.
5Avamar clients backup clients accessing the Avamar server through an Ethernet
connection. Avamar clients are usually file servers and database servers in an IT
environment, or employee desktops and laptops.
The Avamar Server stores backup metadata for restores and activity reporting, and provides
services that are required for client access and remote system administration.
NetWorker Clients
Client-Direct
NetWorker
Server
Metadata
Backup Server
NetWorker
Storage Node
Backup Data
Read/
PowerProtect DD
Storage Node
Backup Clients
Data Center
A NetWorker Data Zone is composed of a single NetWorker server, its storage nodes, and clients.
In a NetWorker Data Zone the NetWorker server, storage nodes, and clients can write backups to a
PowerProtect DD appliance. When a client writes backup data directly do a PowerProtect DD
appliance, bypassing the storage node, it is known as a Client-Direct backup.
Multiple NetWorker servers might back up the same NetWorker client. Clients may belong to
multiple data zones. NetWorker servers and storage nodes may belong to only one data zone.
Master Server
Metadata
Backup Server
Media Server
Backup Clients
Data Center
In Veritas NetBackup and Backup Exec environments, the server managing backups is called the
Master Server, and Media Servers write to and read from backup targets.
Metadata
Backup Server
Media
Agent
Storage Pool
Backup
Data
PowerProtect DD
Storage Nodes
Backup Clients
Data Center
The diagram shows some product-specific terms that apply to IBM Spectrum Protect
implementations.
The main function of the Spectrum Protect server is to coordinate movement of the backup data
from the Client Nodes to the PowerProtect DD appliance.
The Spectrum Protect server holds the Spectrum Protect database. This database tracks each new
transaction in its recovery logs. If there was a sudden outage of the Spectrum Protect server,
recovery logs help revert changes to an operational state.
Increasing the storage speed and capacity for the data that is generated along with the cost-
effectiveness is a perpetual challenge. One of the most expensive and resource-intensive tasks are
gathering, storing, and protecting data backups. Writing data to tapes and shipping them offsite for
storage is one of the largest financial and labor resource challenge in a conventional tape-centric
environment. The diagram illustrates the conventional tape-based process of handling backups.
Backup Clients
Tape Transport
1. The conventional process of handling backups is through backup servers. The backup servers
preserve the data from backup clients on the media server then copying it to disk-based storage
or a tape library.
2. Tapes are physically transported and stored offsite for archival and disaster recovery purposes.
If there is a negative event in the data center, moving tapes offsite prevents the loss of backup
data.
3. Data recovery requires a manual process of transporting the tapes back to the data center.
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
1. When a PowerProtect DD appliance is added to a backup environment, backup clients may still
store data on the storage node. However, if NetWorker or Avamar are used to backup clients,
the clients may also back up data directly to the PowerProtect DD appliance.
2. If clients do not back up directly to the PowerProtect DD appliance, the backup servers store the
data on the PowerProtect DD appliance.
3. Deduplication greatly reduces the data footprint before the data is backed up.
4. The PowerProtect DD replication feature transfers only the unique changes6 across any IP
network.
5. The elimination of time-consuming handling of tape transforms the data recovery process. If
regulatory or corporate policies require tape backups, tape backups can be performed in parallel
to backups to a PowerProtect DD appliance.
Consider replacing some or all reliance on tape backups with deduplicated storage of data on disk.
By doing so, you reduce cost, complexity, and the risks associated with tape.
DD Boost
Data Replication
Backup Server
DD Boost DD Boost
DD Boost
Data Recovery
Storage Node
Backup Clients
• Reducing the number of tracked copies, reducing backup server database sizes while
increasing performance
• Reducing the overall size and scope of the backup and recovery infrastructure
• Elimination or reduction of the time and resources that are associated with physical tape
PowerProtect DD
Data Replication
Backup Server
Data Recovery
Backup Clients
Data Center Disaster Recovery Site
PowerProtect DD appliances can perform backups over both Ethernet and Fibre Channel
concurrently. Flexibility in configuring a PowerProtect DD appliance affords a great number of
integration scenarios.
Over Ethernet, the backup software addresses the PowerProtect DD appliance through native NFS
mounts or CIFS shares.
Over Fibre Channel, prior investments in backup and recovery systems have been in tape.
Administrators familiar with Fibre Channel administration can adopt the PowerProtect DD appliance
as a Virtual Tape Library, or perform backups using DD Boost over Fibre Channel.
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
In NetWorker, administrators already using NetWorker Advanced File Type Devices (AFTDs) can
adopt the PowerProtect DD appliance as a file system. Adopting the PowerProtect DD file system
can be done without significant infrastructure or mindset change. NetWorker AFTDs accept
concurrent streams, writing the streams into separate files in the directory structure of the AFTD.
For VTL implementations, use the NetWorker Device Manager drivers to interface with the VTL
library changer with minor changes.
Basic Device
Data Replication
Backup Server
Data Recovery
Storage Node
RESTORER-L180 emulation DDVTL drive
emulation Minor policy change
Backup Clients
Data Center Disaster Recovery Site
For VTL implementations, use the RESTORER-L180 or DDVTL drive emulation. Drive emulation
enables the backup software to interface with the VTL Library changer. There are few policy and
procedural changes if the PowerProtect DD appliance is used to replace a physical tape library.
Data Replication
Backup Server
Data Recovery
Storage Node
RESTORER-L180 emulation Primary or copy
pool target Minor policy change
Backup Clients
For NAS configuration of IBM Spectrum Protect, configure FILE CLASS DEVICE through NFS
exports of CIFS shares from the PowerProtect DD appliance. You cannot use the DISK device class
type in Spectrum Protect with a PowerProtect DD appliance. Use FILE device class type.
In a VTL configuration, the PowerProtect DD appliance can be a primary or copy pool target and
uses L180 emulation.
This table shows trade-offs when the PowerProtect DD appliance is configured as a NAS compared
to SAN.
Ethernet (CIFS, NFS, and DD Boost) Fibre Channel (VTL and DD Boost)
The backup server does not require changer and Install and load a tested and supported changer
tape driver installation and loading. driver and tape driver on the backup server.
A Fibre Channel HBA is not required. Install a tested and supported Fibre Channel
HBA on the storage node.
Tape mounts, loads, labeling and other tape In the VTL environment, the backup software
emulation tasks are not needed. must perform tape mounts, loads, labeling and
other tape-emulation tasks.
Expired backup images are cleaned up on the In the VTL environment, expired backup images
PowerProtect DD appliance: are not cleaned up on the PowerProtect DD
Pro: Expired disk space recycles immediately appliance:
when garbage collection and cleaning kicks off. Pro: Backup software can start its tape import
Con: Backup software is not able to recover and procedure to quickly recover and restore backup
restore backup images as quickly. images.
Con: Expired disk space may not be reclaimed
when file system cleaning is performed.
On the backup server, configure CIFS or NFS There is no need to configure CIFS access or
mounts of the PowerProtect DD with the proper NFS access to the backup-to-disk (B2D) folder.
mount options.
Implementation Workflows
Administrative Console
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
• DD Boost implementation
• BoostFS implementation
• VTL implementation
Administrative Console
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
Administrative Console
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
After the installation and initial configuration tasks are complete, you can begin administering the
implementation. Start by validating the implementation by creating, running, and verifying a backup
job.
1. Create a backup job using the administrative console in your backup system.
2. Run and monitor the backup job from the administrative console.
3. From the administrative console, you can recover backups and test a recovery to a client.
4. Monitor space usage and throughput on the PowerProtect DD appliance using the DD System
Manager (DDSM), command-line interface, or PowerProtect DD Management Center (DDMC).
DD Boost Implementation
Administrative Console
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
To implement DD Boost, prepare the PowerProtect DD appliances, and the backup application.
1. Enable DD Boost on both the local and the disaster recovery PowerProtect DD appliances.
a. Set the DD Boost user for each system.
b. Create any storage units that might be needed7.
2. Using the administrative console, configure the backup software to use the PowerProtect DD
appliances as backup targets.
3. From the administrative console, configure backup and clone operations.
4. Perform and monitor backup and clone activity.
7When configuring them for DD Boost, Dell EMC Avamar and NetWorker will, by
default, create their own storage units on PowerProtect DD appliances.
5. Check that the backup data on the local PowerProtect DD appliance is also available on the
disaster recovery PowerProtect DD appliance.
6. When needed, restore files using the administrative console from the disaster recovery
PowerProtect DD appliance.
BoostFS Implementation
DD Boost Filesystem (BoostFS) provides a general file-system interface to the DD Boost library.
BoostFS enables backup applications that do not natively support DD Boost to take advantage of
DD Boost features.
Administrative Console
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
The BoostFS plug-in resides on the storage node, presenting a standard file system mount point to
the backup clients. With direct access to a BoostFS mount point, the application can leverage the
storage and network efficiencies of the DD Boost protocol for backup. By using DD Boost
technology, BoostFS helps reduce bandwidth, can improve backup times, offers load-balancing, and
in-flight encryption.
BoostFS is supported on both Windows and Linux platforms. BoostFS supports physical
PowerProtect DD appliances, high-availability (HA) systems, and PowerProtect DD Virtual Edition.
Consult the Dell EMC BoostFS for Windows Configuration Guide or Dell EMC BoostFS for Linux
Configuration Guide for supported platforms and applications, and installation and configuration
instructions.
VTL Implementation
Administrative Console
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
1. If it has not already been completed, install and configure and HBA card in the PowerProtect DD
appliance.
2. Configure Fibre Channel zoning for use with the PowerProtect DD appliance. Configure zoning
on the FC switch so that each initiator is configured for the needed Fibre Channel ports.
3. Configure the PowerProtect DD appliance for VTL.
a. License and enable the VTL service.
b. Create a VTL with its components and virtual tapes using the DD System Manager or
command-line interface.
4. Use the administrative console to discover the VTL on the PowerProtect DD appliance. Create
the configuration for the tape library, slots, and tapes.
5. Initiate a backup, monitor, and verify VTL backup jobs using the administrative console.
Data Replication
Backup Server
Data Recovery
Storage Node
Backup Clients
Start by installing the backup management server component. Optionally install any media server
that you may want to use. Lastly, install all the required backup client components.
1. All backup application software should have previously been installed. If necessary, complete all
installations. Install the backup server component first.
2. Install any required backup software on the read/write server.
3. Install any required backup client software on the client machines.
Verify that the CIFS configuration of the PowerProtect DD appliance meets the basic requirements
enabling proper access. For example, backup systems could map a network drive to the
PowerProtect DD backup directory or an MTree.
• The PowerProtect DD appliance must use either Active Directory (AD) or Workgroup in
authentication mode.
• The PowerProtect DD appliance must have a valid CIFS user account that is configured as a
domain backup operator. If the account is part of a domain or Active Directory, it should have
local administrator permissions. If the account is in a workgroup, it must have at least, backup
operation group permissions.
• Assign a group or user and backup server name when setting the permissions to ensure that
CIFS is only accessed through backup server for security.
Verify communication between the backup environment and the PowerProtect DD appliance.
Validate the implementation in the following steps:
1. From the administrative console, create a configuration for your backup. Create a backup job
that can be run manually or automatically.
2. Run and monitor the backup job.
3. Recover from a backup for a client system.
4. Validate and analyze the backups within the DD System Manager, where you can view statistics
and reports.
Clients
Backup Management
WAN
Servers
Read/Write Server
Establish communication between the PowerProtect DD appliance and the backup server in an NFS
environment.
1. If needed, install all application software and configure the PowerProtect DD appliance with an
initial configuration.
2. Establish communication between the PowerProtect DD appliance and the backup
management server in an NFS environment.
3. Configure the PowerProtect DD appliance for networking with NFS.
4. Configure the backup management server with NFS mounts. Create, configure, and mount the
backup directory or custom MTree.
The listed steps are tasks for configuring the PowerProtect DD appliance for network connectivity
and enabling the backup transport protocol for NFS.
1. Establish an SSH session to the PowerProtect DD appliance.
2. Run config setup to launch the installation wizard.
The following is an overview of creating a mount on a backup server and copying a test file to the
PowerProtect DD appliance.
Once the NFS Mount procedure is completed, create and copy a file from the media server to the
PowerProtect DD appliance to validate functionality.
8 Setting a wildcard (*) enables any host on the network to connect to the
PowerProtect DD appliance using NFS. To restrict access to specific hosts, replace
the asterisk with a specific hostname or an IP Address.
Specific commands differ depending on the platform you are using. Look up
documentation for the specific commands for each platform.
1
1
PowerProtect DD
Media Agent (Storage
Node)
The goal is to integrate the PowerProtect DD appliance using the NFS protocol to IBM Spectrum
Protect on a Linux server. To successfully integrate the PowerProtect DD appliance into the backup
environment, install and configure the IBM Spectrum Protect as explained.
IBM Spectrum Protect enables disk type device classes to be defined as either FILE or DISK type.
FILE device classes are commonly used in IBM Spectrum Protect for virtual volume management.
Most IBM Spectrum Protect administrators define disk storage pools using DISK device class
definitions and associate formatted *.dsm files as storage pool volumes.
FILE type device classes are recommended for use with a PowerProtect DD appliance. FILE device
classes enable IBM Spectrum Protect to perform sequential read/write activity to files within a file
system. The system writes incoming backup data to a file. When a file is filled, Spectrum Protect
creates a scratch file and fills the file with more incoming backup data.
Capacity planning and measurement ensure that the PowerProtect DD capacity is adequate for
each folder.
The default IBM Spectrum Protect MaxCapacity value for a FILE device class is 2 GB. Depending
on the operating system of the IBM Spectrum Protect server, maximum capacity parameters vary.
This parameter is sized from 200 GB to 400 GB for PowerProtect DD implementations. The default
Mount Limit value is 20 and the maximum value for this parameter is 4096. Up to 4096 individual
files can be opened at a single time. Each PowerProtect DD instance supports up to 20 concurrent
I/O threads, so the default Mount Limit value is recommended.
Directory Create a separate folder for each Spectrum Protect device class
(FILE TYPE).
Create a separate file system mount point or folder for each
Spectrum Protect instance using the same PowerProtect DD
instance.
Mount Limit The default Mount Limit value is 20 and is the recommended
value for PowerProtect DD instances.
Once the communication between the backup environment and the PowerProtect DD appliance is
established, you can validate the implementation by performing operations.
2
3
PowerProtect DD
Media Agent (Storage
Node)
1. Create a policy using the backup management software. For Spectrum Protect, do the following:
a. Define a FILE device class.
b. Define a primary pool.
c. Define a domain and policy.
d. Validate and activate the policy.
e. Register the new node (client).
2. Configure backup clients, and verify the node name for correct access.
3. Run and monitor a backup job from the Spectrum Protect administrative console.
4. You can also perform a data recovery for a client system. You can also validate and analyze the
backups using statistics and reports in the DD System Manager.
Policies
IBM Spectrum Protect policies are rules that determine how the client data is stored and managed.
The rules include where the data is initially stored, how many backup versions are kept, how long
archive copies are kept and so on.
1. A client initiates a backup, archive, or migration operation. The file in the operation is bound to a
management class. The management class is either the default or one specified for the file in
client options (the client's include-exclude list).
2. If the management class of the policy indicates that the file is a candidate for backup, the client
sends the file and metadata to the server.
3. The server checks the management class that is bound to the file. The check is to determine the
destination, and the name of the IBM Spectrum Protect storage pool where the server initially
stores the file. For backed-up and archived files, destinations are assigned in the backup and
archive copy groups, which are within management classes. For space-managed files,
destinations are assigned in the management class itself.
4. The server stores the file in the storage pool that is identified as the storage destination.
Spectrum Protect
Server
Storage Pools
Client Data
Backup Clients
Database
Policy Domain
Policy Set
Management Class
Copy Group
Session Timeout
Certain internal activities on a PowerProtect DD appliance can take longer than the default CIFS
timeout on the servers. Longer times can cause error messages during a backup.
To avoid a timeout, Dell Technologies recommends changing the SESSTIMEOUT value from the
default 45 to 3600 seconds.
Tuning TCP/IP
If you are having problems with poor network performance and link utilization is under 100%, you
can increase the TCP window size on your server. Using the Registry Editor, create two new
registry entries, DefaultSendWindow and DefaultReceiveWindow. Also, create a
TCPWindowSize entry for the active network interface.
For more information about configuring and managing CIFS on a PowerProtect DD appliance, see
the Dell EMC DDOS Administration Guide available from Dell EMC Support.
CIFS Troubleshooting
Kerberos
Authentication
Backup Server/
Storage Node
Domain (AD)
In a CIFS Active Directory (AD) environment, a common issue occurs when the PowerProtect DD
appliance has trouble joining the AD domain. Another issue occurs when the backup server or
storage node are unable to access the PowerProtect DD appliance to perform a backup.
1. To troubleshoot issues with joining the AD domain, check physical and transport connectivity
between the two components. On the PowerProtect DD appliance, check to ensure that the
clock on the PowerProtect DD appliance is within 300 seconds (five minutes) of the AD server.
Verify that the backup user who is specified on the PowerProtect DD appliance is a valid user
on the AD domain with, at minimum, operator privileges.
The command, cifs troubleshooting list-users helps narrow down user validation.
2. To troubleshoot client access issues, check physical and transport connectivity between the
PowerProtect DD appliance and the backup server, mainly TCP connectivity.
On the PowerProtect DD appliance, check to ensure that the media server host is enabled as a
backup client. Also check to ensure that there are no stale Kerberos tickets.
Server tuning is recommended for new PowerProtect DD appliance implementations using NFS.
NFS mounting configurations depend on the NFS server type whether in an HP, Linux, AIX, or
Solaris environment. Also, Dell Technologies recommends hard-mounts to ensure availability of the
server after reboots or outages.
The following examples describe NFS tuning for Dell EMC NetWorker. For general about
configuring and managing NFS on a PowerProtect DD appliance, read the current Dell EMC DDOS
Administration Guide found at Dell EMC Support.
When mounting an NFS share on AIX 5.2 and later, use the nfso -o
nfs_use_reserved_ports=1mount –o timeo=600 {nfs_server}:/{export path}
/{mountpoint} command. This mount command does not persist across AIX reboots. For AIX 5.2
or later, use the -p option to mount the share permanently.
To show the list of file systems that PowerProtect DD appliance exports, use the nfs show
clients command.
To optimize TCP/IP performance on the AIX host, set large_send to no for each NIC interface.
• no -p -o sack=1
• no -p -o tcp_newreno=0
• nfso –p -o nfs_rfc1323=1
HP-UX 11i
To show the list of file systems exported by the PowerProtect DD appliance, use the nfs show
clients command.
• Stop and restart the NFS daemons with the /sbin/init.d/nfs.client stop and
/sbin/init.d/nfs.client start commands.
Set the TCP send and receive sizes for HP-UX 11.0 and 11i backup servers. To make the changes
persistent over system reboots, create a startup script that runs before the NFS automount. The
numbering in the script name and location depends on how startup scripts are set up on your
system.
The following is only an example of creating a file: /sbin/rc3.d/S99dd ndd -set /dev/tcp
tcp_recv_hiwater_def 262144ndd -set /dev/tcp tcp_xmit_hiwater_def 262144
Linux
To show the list of file systems exported by the PowerProtect DD appliance, use the nfs show
clients command.
Solaris
To show the list of file systems that are exported by the PowerProtect DD appliance use the nfs
show clients command.
• Create the file /etc/rc3.d/S90ddr and enter the following two lines:
1. set nfs:nfs3_max_threads=16
2. set nfs:nfs3_async_clusters=4
3. set nfs:nfs3_nra=16
4. set rpcmod:clnt_max_conns=1
5. set fastscan=131072
6. set handspreadpages=131072
7. set maxpgio=65536
The SUN T-processors, which are known as "coolthreads" servers have poor NFS performance.
The only adequate resolution is to use jumbo frames.
DD Boost Implementation
DD Boost
DD Boost DD Boost
DD Boost
Backup Server
Backup Clients
DD Boost
Storage Node
This topic covers options and procedures for PowerProtect DD implementation with the DD Boost
option in environments using several common backup applications.
1. Use the command line or the DD System Manager to enable the PowerProtect DD system for
storage operations with DD Boost devices. 9
2. Use the backup application console to configure the backup application for use with the
PowerProtect DD system10.
9 On the PowerProtect DD system, enable DD Boost, set the DD Boost user, and
storage unit.
Data
DD Boost DD Boost
DD Boost
Local PowerProtect DD Disaster Recovery PowerProtect DD
DD Boost
Backup Clients
Metadata
Data
Avamar Disaster
Avamar Data Store
Recovery Data Store
Avamar clients send most data directly to the PowerProtect DD appliance. Some datatypes are sent
to the Avamar data store.12
1. During a backup, the Avamar server sends a backup request to the Avamar client.
2. If the backup request includes the option to use a PowerProtect DD system as the target, the
Avamar client sends the backup data directly to the PowerProtect DD system. 13
11When the DD Boost library is integrated in Avamar clients, the client sends
unique data segments directly to the PowerProtect DD system.
3. Metadata for the backup is sent from the backup client to the Avamar server 14.
4. The backup data is sent to and stored on the PowerProtect DD system.
5. Datatypes that are not suited for DD Boost processing, are sent to the Avamar data store.
Verification
Local
Disaster Recovery PowerProtect DD
PowerProtect DD
Backup Server
Clients
Storage Node
Follow these steps to verify DD Boost implementation by verifying backup and clone functionality.
13The backup data is not staged on the Avamar server before it is sent to the
PowerProtect DD system.
14Sending and storing metadata to the Avamar server allows Avamar to manage
the backup even though the data is stored on a PowerProtect DD system.
3. When the backup is complete, verify the presences of backed-up files on the PowerProtect DD
appliances.
4. Using the backup server console, restore files from the disaster recovery PowerProtect DD to
the client.
VTL Implementation
Administrative Console
Backup
Fibre Channel
Switch
Storage
Node
In most environments, Fibre Channel zoning and HBA card installation and configuration are
already completed. These steps include configuration of the PowerProtect DD system, device
discovery, and configuration on the administrative console. The system administrator completes the
backup, monitoring, and validation operations.
1. Install and configure the HBA card. Installation and configuration are completed before system
operation.
2. Configure Fibre Channel zoning on the FC switch. FC zoning is also completed before system
operation.
3. Configure the PowerProtect DD and NetWorker for DD VTL. The local PowerProtect DD can be
linked to a second PowerProtect DD over WAN for archiving and disaster recovery.
4. From the administrative console, locate the FC zone that connects to the PowerProtect DD and
configure it in DD VTL.
5. From the administrative console, run, monitor, and validate the backup job.
The main steps required to prepare the FC network and the DD VTL for use with NetWorker on a
backup server (host) system are:
16Use a single backup host or filler HBA port in a zone with a single PowerProtect
DD system port. This technique is called the single-initiator single-target zoning. It
can reduce message traffic around the switch when configuration changes occur.
PowerProtect DD Appliance
Backup
Management
Backup Clients
Read/Write Server
1. Make certain that all installations have occurred, including all application software on the backup
clients, backup management server, and read/write server.
2. Configure the PowerProtect DD appliance as a virtual tape library. This includes creating a
backup user, verifying all networking and FC settings, and creating all the necessary VTL
resources on the PowerProtect DD appliance.
3. Configure the backup management server with the necessary credentials and other settings
necessary to perform tape backups to the PowerProtect DD appliance.
When the backup management server and PowerProtect DD appliance establish communication,
operations can begin. Run backup and recovery operations with the PowerProtect DD system:
Administrative Console
Backup
Server
Backup Switch
Clients
Storage Node
VTL Multiplexing
Multiplexing ensures that none of the clients sending save sets wait for the other
clients to finish. Multiplexing allows multiple data streams simultaneously to the same storage
device. It is often more efficient for the NetWorker server to multiplex multiple save sets to the same
device.
Use the target sessions, max sessions, and pool parallelism attributes to limit the number of data
streams that NetWorker writes to a PowerProtect DD appliance to a single stream.
20The multiplexing process writes a portion of save set 1, and then a portion of
save set 2, and so on.
21Multiple backup streams interfere with the deduplication process from efficiently
identifying blocks of common data.
PowerProtect DD systems can be configured with two, or four 16-gigabit Fibre Channel (FC) ports.
All connections to these ports are made using a Fibre Channel switch. PowerProtect DD systems
also support direct attachment of devices to these ports. The following recommendations apply
when connecting the PowerProtect DD system to a backup server through a Fibre Channel switch.
Three hops through fabric Limit Fibre Channel extended fabric (ISL link)
configurations to three hops between the backup
server/storage node and the PowerProtect DD
system.
Adsministrative Console
Local PowerProtect DD
FC Switch System
Backup Server
Backup Clients
Storage Node
The following describes implementation as SAN or VTL with IBM Spectrum Protect™.
Backup Server
Backup
Clients
Storage Node
1. Install the Spectrum Protect application on the clients, the backup server, and the read/write
server.
2. Configure the PowerProtect DD appliance as a virtual tape library (VTL). This configuration
includes creating a backup user, verifying all networking and FC settings. It creates all the
necessary VTL resources and access groups on the PowerProtect DD appliance.
3. Configure the backup server with the necessary credentials and other settings necessary to
perform tape backups to the PowerProtect DD appliance.
Administrative Console
Local PowerProtect DD
Backup Management System
Clients
Read/Write Server
Migration
Backup or Archive
Database
Policy Domain
Policy Set
Management Class
Copy Group
1. A client initiates a backup, archive, or migration operation. The file that is involved in the
operation is bound to a management class. The management class is either the default or one
specified for the file in the client's include-exclude list.
2. The system checks the file against information in the management class. If the file is a
candidate for backup, archive, or migration, the client copies the file and file information to the
server.
3. The server checks the management class that is bound to the file to determine the destination.
The server also checks the name of the Spectrum Protect storage pool where the server initially
stores the file.
• For backed-up and archived files, destinations are assigned in the backup and archive copy
groups within management classes.
• For space-managed files, destinations are assigned in the management class itself.
4. The server stores the file in the storage pool that is identified as the storage destination.
The following table describes considerations for configuring device classes when implementing IBM
Spectrum Protect with PowerProtect DD systems:
Directory • Create a separate folder for each Spectrum Protect device class
(FILE type).
• Create a separate file system mount point or folder for each Spectrum
Protect instance using the same PowerProtect DD system instance.
Maximum Capacity The Spectrum Protect MaxCapacity parameter should be sized 200 GB–
400 GB for PowerProtect DD implementations (default value is 2 GB).
Mount Limit The default mount limit value is 20. The default mount limit is the
recommended value for PowerProtect DD system instances.
Spectrum Protect enables disk type device classes to be defined as either FILE or DISK type 22.
FILE type device classes are recommended for use with a PowerProtect DD system.23
22FILE device classes are commonly used in Spectrum Protect for virtual volume
management. Most Spectrum Protect administrators define disk storage pools
using DISK device class definitions and associate formatted *.dsm files as storage
pool volumes.
To ensure that the PowerProtect DD system capacity is adequate for each folder, plan appropriate
capacity24.
The default mount limit value is 20 and the maximum value for this parameter is 4096. 25
the file is filled, a new scratch file is automatically created and is filled with more
incoming backup data.
24The default Spectrum Protect MaxCapacity value for a FILE device class is 2
GB. Depending on the operating system of the Spectrum Protect server, maximum
capacity parameters vary. This parameter is sized from 200 GB to 400 GB for
PowerProtect DD implementations.
25 The maximum value means that up to 4096 individual files can be opened at a
single time. Each PowerProtect DD system instance supports up to 20 concurrent
I/O threads, so the default mount limit value is recommended.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
Appendix ................................................................................................. 57
Administration Interfaces
DD System PowerProtect DD
Command Line
Manager Management
Interface (CLI)
(DDSM) Center (DDMC)
Dell EMC also offers the Integrated Data Protection Appliance (IDPA) which uses a
PowerProtect DD appliance as part of a converged, all-in-one data appliance that
combines complete backup, replication, recovery, instant access and restore,
search and analytics, and seamless VMware integration – plus, cloud readiness
with disaster recovery and long-term retention to the cloud.
Through the IDPA interface, you can access and control PowerProtect DD
functions within the overall system. For more information about IDPA, refer to the
Integrated Data Protection Appliance (IDPA) documents through Dell Technologies
Support.
Movie:
Password Policy
Description
At least one Disabled Enabled The local user password must have at
lowercase character least one lowercase character.
At least one Disabled Enabled The local user password must have at
uppercase character least one uppercase character.
At least one digit Disabled Enabled The local user password must have at
least one digit.
At least one special Disabled Enabled The local user must have at least one
character special character.
Configuration Options
You cannot change the minimum length for a password to be fewer than nine
characters long. The minimum length can be set from 9 to 31 characters long.
Default Passwords
PowerProtect DD
DDVE
System Description
AWS and GCP The default password for sysadmin is the Instance-ID.
On the first login, you are forced to set a new password,
which must comply with the new password strength
policy.
The default strength policy is applied automatically with upgrades as follows for
DDOS version 7.6 and later:
• The system upgrade status displays a precheck warning about this change to
the default password strength policy.
• After the upgrade, there is an unmanaged alert for the password policy change.
• If you log in using a password that does not meet the password strength policy,
the following message appears: "Password for sysadmin does not comply with
minimum requirements for passwords. Change your password to comply with
current requirements".
• If the customer is using a password that meets or exceeds the password
strength policy, the values are retained.
Hardware Verification
• DDSM
• CLI
• DDSM
• CLI
Movie:
System Access
List of
Assigned
Current
Roles
Users
You manage local users under Administration > Access > Local Users. Here
you can name the user, grant user privileges, make users active, disabled, or
locked. You can learn the user's management role, and current status. You can
also learn a user's last login date, time, and location.
LDAP
LDAP can be configured for both the DD System Manager (DDSM) and
PowerProtect DD Management Center (DDMC).
AD over LDAP
6When this is enabled, the AD and Kerberos authentication cannot be used for
CIFS access. If the type active-directory parameter is not specified, the system
defaults to open LDAP, which allows AD or Kerberos authentication for CIFS
access.
This command will not work when LDAP authentication is configured for AD.
Common Issues
7UidNumber or UID, along with the group identifier (GID or GidNumber) and other
access control criteria, is used to determine which system resources an entity can
access.
Managing administration access protocols enables you to view and manage how
administrators and users access a PowerProtect DD system.
Read a description of the protocols that are available in the Services list.
You can also manage administration access using the command line.
Movie:
System Monitoring
Log Files
The file system logs system status messages hourly11. Log files can be bundled
and sent to Dell EMC Support to provide the detailed system information to aid with
troubleshooting system issues.
9Only a sample of the logfiles and folders is listed on this slide. The /ddvar folder
contains other logfiles that you cannot view.
11The system logfile entries contain messages from the alerts feature, autosupport
reports, and general system messages. The log directory is /ddvar/log.
Autosupport Reports
13An ASUP is generated as scheduled, usually once per day. An ASUP is also
generated every time the file system is started.
An ASUP is designed to aid Dell EMC Support engineers identify and debug
possible system problems.
You can configure email addresses to receive the daily ASUP reports 15.
15The default time for sending the daily ASUP is 06:00 a.m. and it is configurable.
When sending ASUPs to Dell EMC, you can select the legacy unsecure method or
the ConnectEMC method, which encrypts the information before transmission.
Alert Messages
Configure
Add Alert
Severity
Subscribers
Level
The Alert feature generates event and summary reports that are distributed to
configurable email lists and to Dell Technologies Support.
Event reports are sent immediately and provide detailed information about a
system event. Event reports are generated using notification groups.16
Summary reports are sent daily and provide a summary of the events18 that
occurred during the last 24 hours.
17For example, one group can receive emails about all network events and another
group to receive messages that are related to storage issues.
Movie:
Support Bundles
When troubleshooting, Dell EMC Support may ask for a support bundle. A support
bundle is a tar-g-zipped selection of log files with a README file that includes
identifying autosupport headers.
1. Select Generate Support Bundle. It may take a few minutes to create bundle.
2. Right-click the link to download the bundle to your personal computer.
3. Email the file to Dell Technologies Support.
If the bundle is too large to be emailed, use the online support site to
upload the bundle.
You can also generate support bundles from the command line.
If the support bundle is too large, DDOS provides the option to create a mini bundle
that is smaller in size.
SNMP
SNMP status
Configure SNMP
properties
Must be compatible
with the SNMP
manager used
The SNMP manager needs an SNMP agent21 to monitor and respond to queries.
Regarding SNMP V3, V2c, Configurations: The SNMP agent accepts queries for
PowerProtect DD-specific information from management systems using SNMP v1,
v2c, and v3. SNMP V3 provides a greater degree of security23 than v2c and v1.
22An SNMP system location is a text entry describing where the PowerProtect DD
system is located and a contact.
23 This added security is done by replacing clear text community strings (used for
authentication) with user-based authentication using either MD5 or SHA1. SNMP
v3 user authentication packets can be encrypted and their integrity is verified with
either DES or AES.
Remote Logging
You can configure the PowerProtect DD system to send system log events to a
remote server.
System Messages
Remote logging with syslog sends system messages to a syslog server using UDP
Port 514.
Remote logging with syslog is only configured using the CLI. Use the
log host enable command to enable remote logging.
Movie:
Licensed Features
Licensing
The customer decides which feature they need to license. The ELMS creates a
license authorization code (LAC) email25.
The locking ID26 on the license is a unique identifier that links your license file27 to
your PowerProtect DD Virtual Edition system.
25 The LAC contains a link to the ELMS portal where you can redeem you LAC for
license keys to activate the system features.
27
The license can be added onto the DDVE using either the CLI or the DD System
Manager.
From the CLI, the following commands can be used to manage licenses with
ELMS:
• elicense show [all | license | locking-id]
• elicense update [check-only] [filename]
• elicense reset
Feature licenses allow you to purchase only those features you intend to use.
Some examples of features that require licenses are DD Boost, and DD Capacity
on Demand (storage capacity increases).
28Licenses systems for archive use, such as file and email archiving, file tiering,
and content and database archiving.
29Enables the use of a system with qualified backup software. The Data Domain
Boost 7.3 for Partner Integration Administration Guide explains the how to
configure and use DD Boost with partner applications. The managed file replication
(MFR) feature of DD Boost also requires the DD Replicator license.
31Enables a system to move data from the active tier to low-cost, high capacity
object storage in the public, private, or hybrid cloud for long-term retention.
33Allows system storage to be expanded beyond the level provided in the base
system.
34 An I/OS license is required when DD VTL is used to backup systems in the IBM i
operating environment. Apply this license before creating virtual tape drives to
libraries because the tape drives are created as part of this process, not separately.
35Adds DD Replicator for replication of data from one protection system to another.
A license is required on each system.
36Meets the strictest data retention requirements from regulatory standards such
as SEC17a-4.
37Protects selected files from modification and deletion before a specified retention
period expires.
40Enables the use of a protection system as a virtual tape library over a Fibre
Channel network. This license also includes the NDMP Tape Server feature and
the I/OS license for IBM i systems, which previously required separate licenses.
42Enables the SSD cache feature on some legacy models. This license is not
required to use the SSD cache feature on DD3300, DD6900, DD9400, and
DD9900 systems.
System Upgrades
The following image shows downloads available44 for your appliance based on
search criteria.
Dell EMC recommends that you track DDOS releases deployed in your backup
environment. It is important that the backup environment run the most current,
supported releases46.
In some cases you can upgrade specific features within the DDOS using a
minimally disruptive upgrade.
Keep all PowerProtect DD appliances running the most current DDOS version47,
when possible.
44Any upgrade packages that are available for your organization can be
downloaded from Dell EMC support regardless of where they are in the release
cycle.
46 As a rule, you should upgrade to the latest release for your system model. This
ensures that you are running the latest version that has achieved the highest
reliability status.
47Be sure to minimize the number of different deployed release versions in the
same environment.
Why Upgrade?
53 If you are ever more than two release versions behind, contact Dell EMC Support
for advice on the intermediate versions to use for your stepped upgrade.
55 The time to run an upgrade should take no longer than 45 minutes. Adding the
time to shut down processes and to check the upgraded system, might take 90
minutes or more to complete a single version upgrade. Double this time if you are
upgrading two release versions at once.
Compatibility Check
• Refer to PowerProtect DD
Compatibility Guides available from
Dell Technologies Support.
• Read the release notes for the version
of DDOS you are upgrading and check
for possible compatibility issues with
your device and software57.
• DD Boost Version Compatibility Guide
• For specific details about compatibility
with third-party software, access the E-Lab Navigator website.
56Do not disable replication on either side of the replication pair. When the
appliance file system reenables, replication automatically resumes service.
57 Check for compatibility between the upgrade version of DDOS, the backup
software version, and any DDOS feature software you are using. You can find this
information in the "Preparing to upgrade" section of the release notes.
When you have verified compatibility with your PowerProtect DD appliance and the
correct version of DDOS to upgrade, you are ready to perform a system upgrade.
Begin the system upgrade by navigating to the Maintenance > System and
performing the upgrade precheck.
Movie:
• See the list of managed systems and the current schedule status.
• Schedule an update operation58 for a selected list of available systems.
• Edit an updated schedule.59
60This action does not affect the update that started or is in progress. For updates
that have not started yet, the update schedule is deleted.
– SSH
– Serial Console
– Telnet
– Serial Over LAN (SOL)
– Keyboard and Monitor
After the initial configuration, use the SSH or Telnet (if enabled) utilities to access
the system remotely and issue CLI commands.
DD System Manager
Management
Options
DDMC Supports
You can access a DDMC by using a supported browser64 with network access to
the DDMC instance.
63
A maximum of 100 DD systems can be added to a DDMC. It also supports
multiple simultaneous users.
64For Windows use Internet Explorer™, Edge™, Mozilla Firefox™, and Google
Chrome™.For Mac OX use Mozilla Firefox™, and Google Chrome™.
You can view this information in the DDSM by selecting Maintenance > System to
display:
• Model number
• DDOS version
• System uptime
• Serial numbers for the system and chassis
The command line interface (CLI) can be used to verify basic information about a
PowerProtect DD system. The following commands can be useful:
• system show modelno - Displays the hardware model number of a
PowerProtect DD system.
• system show detailed-version - Shows the version number and release
information.
• system show serialno [detailed] - Displays the system serial number
and also shows whether encryption is enabled.
• system show uptime - Displays the file system uptime, the time since the
last reboot, the number of users, and the average load.
Verify Storage
1 2 3
If you have trouble determining which hard drive corresponds to a disk displayed in
the table, you can use the beacon feature65 (4).
65Select a single disk from the Disks table and click Beacon. You can only select
one disk at a time.
The beacon feature flashes an LED on the drive until you click Stop in the DDSM
window.
The CLI can be used to verify system storage. The following commands can be
used:
• storage show {all | summary | tier {active | archive |
cache | cloud}} - Displays information about the disk groups, disks, and
storage capacity of the file system.
• enclosure show all [enclosure] - Displays detailed information about
the installed components and component status for all enclosures.
• disk show hardware - Displays disk hardware information, the output
includes a column for slot identification.
The system serial number is independent of the chassis serial number and remains
the same during many types of maintenance events, including chassis
replacements.
Chassis view shows top view, back view, and enclosures. Shown here in the rear
view, a mouse rolls over Power Supply 1. The Details pane shows the description
and status of Power Supply 1.
From the CLI the following commands can be issued to view similar information
found in the chassis view:
• enclosure show chassis [enclosure] - Show part numbers, serial
numbers, and component version numbers for one or all enclosures
• enclosure show summary - List enclosures, model and serial numbers,
state, OEM names and values, and capacity (number of disks in the enclosure)
Consult the DDOS 7.6 Command Reference Guide on the Dell EMC Support
site for more detailed information and specific command syntax.
68 A user with the admin role can configure and monitor the entire PowerProtect DD
system. Most configuration features and commands are available only to admin
role users.
69The limited-admin role can configure and monitor the PowerProtect DD system
with some limitations. Users who are assigned this role cannot perform data
deletion operations, edit the registry, or enter bash or SE mode.
70The user role can monitor the system, change their own password and view
system status. A user assigned the user role cannot change the system
configuration.
71 The user assigned the security role is for a security officer who can manage
other security officers, authorize procedures, and perform tasks that are supported
for user-role users. Only the sysadmin user can create the first security officer and
that first account cannot be deleted. After the first security officer is created, only
security officers can create or modify other security officers. Before destroying the
file system, a security officer must provide authorization.
72The Backup-operator role can perform all tasks that are permitted for user-role
users. These tasks include creating snapshots for MTrees, importing, exporting,
and moving tapes between elements in a virtual tape library and copying tapes
across pools.
73 The role of None is used for DD Boost authentication. A user assigned the None
role can log in to a PowerProtect DD system and can change their password but
cannot monitor or configure the primary system.
74The Tenant Admin role can be appended to the None role when the Secure
Multi-Tenancy (SMT) feature is enabled. A tenant admin user can configure and
monitor a specific tenant unit as well as schedule and run backup operations for the
Tenant.
75The Tenant User role can be appended to the None role when the secure multi-
tenancy (SMT) feature is enabled. The Tenant User role enables a user to monitor
a specific tenant unit and change the user password.
The CLI can be used to manage local users. The following commands can be used:
You can use the command line to manage NFS exports. Use the following
commands:
• nfs export add - Adds a client or list of clients to one or more exports.
• nfs export del - Removes a client or a list of clients from existing exports.
• nfs export create - Creates a named export and adds a path.
• nfs export destroy - Destroys one or multiple NFS exports.
• nfs export modify - Updates an existing client or clients to an export or set
of exports.
The minimum role required for these commands is admin. Consult the DDOS
Command Reference Guide for more detailed information and specific syntax.
You can also generate support bundles from the command line:
• support bundle create {files-only <file-list> | traces-
only} [and-upload [transport {http|https}]]
Compresses listed files into a bundle and uploads if specified
• support bundle create default [with-files <file-list>]
[and-upload [transport {http|https}]]
Compresses default and listed files into a bundle and uploads if specified
If the bundle is too large to be emailed, use the online support site to
upload the bundle.
76Only those services that depend on the component being upgraded are
disrupted, so the MDU feature can prevent significant downtime during certain
software upgrades. MDU uses smaller component bundles, which upgrade specific
software components individually.
77An MDU is similar to the Linux atomic upgrade, but is made of stand-alone
component RPMs like ddsh.rpm or vtl.rpm. These stand-alone components come in
smaller packages to facilitate faster delivery to the system.
78The effect of the new component takes place as in an atomic upgrade, but only
the processes relating to the specific component restarts. The overall PowerProtect
DD system remains unaffected by the upgrade.
Release Notes
DDOS release notes are the most
informative document to check
compatibility for your backup
environment. Release notes
documents contain environmental
and system requirements specific to
the target software version in these
sections:
Upgrade Precheck
The DDOS upgrade precheck is found in the Maintenance > System > UPGRADE
PRECHECK tab in the DD System Manager. Upgrade precheck is part of the
upgrade process which determines whether the system is in an upgradable state79.
79The aim of the precheck is to detect potential problems early and halt the
upgrade. Allowing the upgrade without a precheck might place the system in an
unusable state after an upgrade attempt.
Schedule Updates
To schedule a DDOS update from PowerProtect DD Management Center (DDMC):
12. In the Summary page, review the summary, and if applicable, select Reboot
before installation.
A system reboot allows the update to continue without any conflicts with
background running processes and may be required for some updates.
13. Click Finish.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
You can manage the configuration of the networking components through the
PowerProtect DD System Manager or the Command Line Interface (CLI).
• Hostname
• Local host file
• Search domains
• Dynamic DNS
With an admin or limited-admin role, here are some CLI commands that provide
most of the relevant information that is associated with network interfaces. Use the
help net show command to obtain more information about these commands.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
Step One
Navigate to Hardware > Ethernet > Interfaces tab and select an interface from the
interface table. Then click Configure.
Step Two
Go to the IP settings section of the panel. If you are using DHCP to assign an IP
address, click Obtain using DHCP and identify if the DHCP server provides an
IPv4 or IPv6 address.
IPv6
IPv4
Step Three
If the Maximum Transmission Unit (MTU) size must be changed, go to the MTU
Settings section of the panel and enter the MTU value2.
Step Four
Enable or Disable the Dynamic DNS Registration (DDNS) for Windows mode by
selecting or clearing the checkbox. Click NEXT.
2The minimum value for the MTU setting is 600 for IPv4 and 1280 for IPv6, the
maximum value is 9000, and the default value is 1500.
Step Five
The SETTINGS view, shows you the Host Settings3, Search Domains4, Hosts
Mapping5, and DNS List6.
You can also use the Command Line Interface to view IP Name settings and
configure IP name settings.
3The Host Settings section displays the PowerProtect DD system hostname. The
hostname is shown as a Fully Qualified Domain Name (FQDN), which means the
hostname and domain name are displayed as a single string.
4 The Search Domain section displays the search domains that are used by the
PowerProtect DD. When a hostname is entered without a domain, the system
attempts to determine the correct domain to associate with the provided hostname
by appending each of the listed search domains to the hostname. If it is discovered,
the system uses the fully qualified domain name. If no domain names yield the
correct fully qualified domain name, the system returns an error.
5The Host Mappings section shows local name to IP address mappings. Unlike the
mappings from the DNS server, these name mappings only apply to this system.
6 The DNS List displays the IP addresses of the DNS servers that are used by this
system. An asterisk (*) indicates that the DNS server addresses were assigned
through DHCP.
Refer to the Dell EMC DDOS Command Reference Guide for more information
about these commands.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
Refer to the Dell EMC DDOS Command Reference Guide for more information
about these commands.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
Static routes define the data path to destination hosts or networks. You can create
static routes from the PowerProtect DD System Manager (DDSM) or the Command
Line Interface (CLI).
7The internal route table is where the administrator may define a specific network
or subnet that is used by a physical interface (or interface group).
Step One
To configure a static route using the DDSM, navigate to Hardware > Ethernet >
Interfaces and click on the ROUTES tab.
Step Two
In the Create Routes dialog box, select an interface that you want to host the static
route. Click NEXT.
Step Three
In the Create Routes dialog box, specify the Destination network, and enter the
Network address and Netmask or prefix for IPv6 addresses. To specify a
destination host, select Host and enter the hostname or IP address of the
destination host.
Optionally, you can add the Gateway to use to connect to the destination network
or host. Click NEXT.
This is not the IP of any interface. The interface is selected in the initial dialog, and it is used for
routing traffic.
Step Four
Review the Summary and click FINISH. After the process is completed, click OK.
The new route specification is listed in the Route Spec table.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
Link aggregation and link failover are two types of bonding that most PowerProtect
DD systems support.
Bonding8 modes define the methods and protocols that are used to control the
physical links between systems. The bonding hash defines the methods that are
used to balance transmissions over the physical links. Balancing is typically done to
obtain better physical link utilization.
8 Bonding is a term the Linux community uses to describe the grouping of interface
together to act as one interface to the outside world.
11 This is how transmissions are balanced over the physical links to obtain better
utilization.
Components
12The bonded interface operation is the component that performs the functions that
are defined by the bonded interface type (bonding mode). This component
processes data according to the rules associated with the interface type.
13These components are responsible for transmitting and receiving data over the
network. There are physical interfaces on the connected devices as well. If
configuring link failover, the interfaces on the connected device do not require any
special configuration other than normal Ethernet network configuration. If
configuring link aggregation, the interfaces on the connected device must be set up
with a compatible bonding type, mode, and hash.
When using link failover or link aggregation, remember that links are controlled
point-to-point. Whichever protocol is used to control the operation of the links, it
only operates from the PowerProtect DD system to the directly connected device.
This directly connected device can be a switch, a server, or even a network
gateway or router.
Link control does not extend beyond the directly connected device. If the media or
application server is not directly connected to the PowerProtect DD system, the
operations of the physical links are not managed by the failover or aggregation
functions. Higher-level protocols detect any loss of connectivity.
Supported Topologies
Topologies provide a map of the network and essentially define its terrain. With a
map of the topology, you can see how devices are physically or logically
interconnected.
In the context of link failover and link aggregation, three common topologies are
Direct connect14, LAN connect, and Remote connect. Click on each term for more
information.
14 The direct connect topology may be used for any type of bonding mode, but is
most often used with round robin. Round robin provides the most fair traffic
distribution between the two links. Round robin is more susceptible to out-of-order
packet transmission. The fact that traffic that is destined for other devices is not
going to be contending for the resources these links provide minimizes the problem
of out-of-order packet transmission.
17In a remote connect topology, the server, or client is in a different subnet than the
PowerProtect DD system. All traffic to and from the server must go through a
gateway. Because of this, all packets contain the MAC addresses of the gateway
and PowerProtect DD.
Link failover provides link redundancy by identifying backup interfaces that can
support network traffic when the primary interface is not operating. This ensures
that the PowerProtect DD system remains connected to the network.
3: If the carrier signal is lost, the active interface is changed to another standby
interface. An Address Resolution Protocol (ARP) is sent to indicate that the data
must flow to the new interface. The interface can be on the same switch, on a
different switch, or directly connected.
Create a bonded interface for link failover to serve as a container to associate the
links that participate in failover. The failover-enabled bonded interface represents a
group of secondary interfaces, one of which can be specified as the primary. The
system makes the primary interface the active interface whenever the primary
interface is operational. A configurable Down Delay failover option allows you to
configure a failover delay18 in 900-millisecond intervals.
Step One
Select Hardware > Ethernet > Interfaces. In the interfaces table, disable the
physical interface19 to which the bonded interface is to be added by clicking No in
the Enabled section.
If an error is displayed warning about the dangers of disabling the interface, verify
that the interface is not in use and click OK.
18 The failover delay guards against multiple failovers when a network is unstable.
Step Two
Step Three
In the Create Virtual Interface dialog box, specify a bonded interface name in the
veth box20. In the Bonding Type list, select Failover as the bonding type.
Click NEXT.
Step Four
Specify and IP address and Netmask. Specify MTU setting. The default setting is
1500. Enter a different setting22 if needed.
22Ensure that all of your network path components support the size set with this
option.
Click Next.
Step Five
In the IP settings, enter an IP address and netmask for the virtual interface. If
necessary, configure the MTU Settings. Verify the MTU settings with the network
administrator before modifying the configuration. Click Next.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
veth 1
eth1a Port
eth2a Port 2
eth3a Port 3
Connected
Link Aggregation
Devices
Bundle
A bonded network interface must be created in order for link aggregation to work.
The system uses this bonded interface25 as an access point for the link aggregation
bundle.
24Link aggregation also provides link failover. If one of the physical network links in
the bundle should fail, the other links continue to service the network connection.
25When you create the bonded network interface, you identify how the bonded
(bundled) links are used. In this case, the bonded interface is used to aggregate
Link aggregation performance is impacted by link and switch speed, the amount of
information the system can process, out-of-order packets, the number of clients,
and the number of streams.
multiple physical links and make them appear as a single network connection. You
can create as many bonded interfaces as there are physical interfaces.
26The network switch can handle the speed of each connected link. If all packets
are coming from several ports that are concentrated on one uplink running at
maximum speed, it may lose some packets. Usually, this means you can use only
one switch for port aggregation coming out of a PowerProtect DD system. Some
network topologies support link aggregation across multiple switches.
27The receiving device must reorder the data stream. This adds overhead that may
impact the throughput speed enough that the link aggregation mode causing the
out-of-order packets should not be used.
• The number of clients can also impact performance. Usually, either the physical
or operating system resources cannot drive data at multiple Gbps.28
• Enable aggregation on an existing bonded interface by specifying the physical
interfaces and mode.
• The number of streams (connections) per client can impact link utilization
depending on the hashing used.
• Make interface changes29 only during scheduled maintenance downtime
because routing rules and gateways are reapplied after interface changes.
• Enable aggregation on an existing bonded interface by specifying the physical
interfaces and mode.
• Bring up the bonded interface and make sure an IP address is on the interface
or an associated interface. The bonded interface may have VLANs and or
aliases on it, each with an IP address, and therefore does not need an IP
address directly on it to be fully
functional.
28
Due to hashing limits, you may need multiple clients to push data at multiple
Gbps.
29 Verify the routing configuration is still correct after making interface changes.
30The speed of the network switch or network link impacts performance when the
amount of data has exceeded the capacity of the switch. Usually, a network switch
can handle the speed of each connected link. If all packets are coming from several
ports that are concentrated on one uplink running at maximum speed, it may lose
some packets. Usually, this means you can use only one switch for port
aggregation coming out of a PowerProtect DD system.
Out-of-order packets.31
32The number of clients can also impact performance. Usually, either the physical
or operating system resources cannot drive data at multiple Gbps. Also, due to
hashing limits, you need multiple clients to push data at multiple Gbps.
33The number of streams (connections) per client can impact link utilization
depending on the hashing used.
34 Verify the routing configuration is still correct after making interface changes.
35 Bring up the bonded interface and make sure an IP address is on the interface or
an associated interface. The bonded interface may have VLANs and or aliases on
it, each with an IP address, and therefore does not need an IP address directly on it
to be fully functional.
Step One
Disable the physical Ethernet interfaces36 that you want to add to the aggregation
link by selecting the interfaces and choosing No from the Enabled menu.
If an error is displayed warning about the dangers of disabling the interface, verify
that the interface is not in use and click OK.
Step Two
From the Create menu, select the Virtual Interface option. The Create Virtual
Interface dialog box is displayed. Specify a virtual interface name in the veth text
box.
From the General tab, select Aggregate as the bonding type. Specify the bonding
Mode. The bonding mode must be compatible with the link aggregation method
that is supported by the system that is directly connected to the physical interfaces
in the bundle. The available bonding modes are Round-robin37, Balanced38, and
Link Aggregation Control protocol (LACP).39
If the Bonding mode is LACP or Balanced, choose the bonding hash algorithm.
37 Round robin bonding mode is often used by Linux systems. It transmits packets
in sequential order from the first available link through the last link in the bundle.
Round Robin provides the best distribution across the bonded interfaces. Often,
this is the best bonding mode to use, but throughput can suffer because of packet
ordering.
38Balanced bonding mode sends data over the interfaces as determined by the
selected hash method. All associated interfaces on the switch must be grouped into
an EtherChannel (trunk). EtherChannel is the bonding method that is defined by
Cisco systems.
39LACP bonding mode is similar to Balanced, except for the control protocol that
communicates with the other end and coordinates which links in the bond are
available. It provides heartbeat failover. LACP was originally defined in IEEE
802.3ad. 802.3ad was incorporated into the IEEE 802.1AX-2008 specification
which was in turn superseded by IEEE 802.1AX-2014.
Step Three
If the Bonding mode is LACP or Balanced, choose the bonding Hash algorithm.
The options are XOR-L2, XOR-L2L3, or XOR-L3L4
Bonding Hash
Physical Interfaces
Step Four
Enter an IP address and netmask for the virtual interface. If necessary, configure
the MTU. Verify the MTU settings with the network administrator before modifying
the configuration. Click Next. A panel with the summary of the configuration is
displayed, review the summary and click Finish. Once the interface is created,
click OK.
If there are any errors, review them and reconfigure the interface.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
40Choose the mode compatible with the specifications of the system to which the
ports are attached. Balanced and LACP modes require a hash selection.
Administrators can control traffic patterns and react quickly to relocation using
VLANs. VLANs provide the flexibility to adapt to changes in network requirements
and simplify administration.
• VLANs provide the segmentation services that are normally provided by routers
in LAN configurations.
• VLANs address issues such as scalability, security, and network management,
• Routers in VLAN topologies provide broadcast filtering, security, address
summarization, and traffic-flow management.
• Switches may not bridge IP traffic between VLANs.42
eth1 / 1.1.0.1/24
VLAN ID 200 Switch Port
Physical Configuration
Network Interface Virtual
Interface
Assign untagged
(eth 1) frames to VLAN 200
eth1.1/1.1.1.1/24
VLAN ID 1
VLAN Tag frames
destined for VLAN
1
Tag frames
eth1.2/1.1.2.1/24 destined for VLAN 2
VLAN ID 2
VLAN
Untagged Tagged
Mixed
43If frames are tagged with the appropriate VLAN ID, any frames that are received
by the physical interface are directed to the VLAN interface.
Step One
Navigate to the Hardware > Ethernet > Interfaces tab. In the interfaces table,
select the interface to which you want to add the VLAN.
Step Two
In the Create VLAN panel, specify a VLAN ID by entering a number in the VLAN Id
field. The VLAN ID can be any number from 1 to 4094. Specify an IPv4 or IPv6
address along with the netmask or prefix. If needed, specify the MTU setting44 as
well.
44The VLAN MTU must be less than or equal to the MTU defined for the physical
or virtual interface to which it is assigned.
Click NEXT.
If the MTU defined for the supporting physical or virtual interface is reduced below
the configured VLAN value, the VLAN value is automatically reduced to match the
supporting interface.
Step Three
The Create VLAN summary page appears. Review all configurations settings and
click FINISH.
IP Aliases Overview
DD Operating System,
does not generate
statistics46 for the IP
alias. The name of an IP
alias interface name is
derived from the base
interface and the IP
alias ID47, which the
system administrator
assigns.
45 The only function of an alias interface is to add multiple IP addresses to the base
interface.
Configuring IP Aliases
1. Navigate to the Hardware > Ethernet > Interfaces tab, and select the interface
to add the IP alias48. Click Create.
2. From the Create menu, select the IP Alias option.
3. Specify an IP alias ID49 by entering a number in the IP Alias Id box.
4. Enter an IPv4 and subnet mask or IPv6 address and prefix.
49 The IP alias ID must be a number from 1-4094. You cannot use the same IP
alias ID that already exist on this base interface. The CLI allows 1 to 9999.
IP alias name is eth0a:1 and this is a combination of base interface and IP alias
and alias ID.
The Command Line Interface (CLI) can also be use to create an IP alias.
With an admin or limited-admin role, you can create an IP alias. The base-ifname
parameter expects a physical, VLAN, or virtual interface name. The net config
command supports alias-id values from 1 to 9999. The alias-ID cannot be in use by
another alias. The net config command can be used to assign an IP alias to
physical, VLAN, and virtual interfaces. To destroy or delete an IP alias using the
net config command, assign it an IP address of 0.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
51 Specify an IPv6 address for the interface. The dhcp option must be set to no to
support manual IP address configuration. The dhcp option is automatically set to no
if a static address is set.
Before you can start to configure a Fibre Channel connection for the PowerProtect
DD system, you must verify some things.
Fibre Channel
Switch
Server
PowerProtect DD
✓ Is the FC switch properly zoned and communicating with the FC server and the
PowerProtect DD?
✓ What name or alias must be applied to the server? This name is mapped to the
WWPN.
✓ What is the WWPN, IP address and FC slot and port?
Fibre Channel services, such as VTL and DD Boost, require the support of
underlying components. These components are grouped in the DD System
Manager (DDSM) under the hardware configuration section.
Initiators
Endpoints
NPIV
Ports
HBA
52With the PowerProtect DD system, Dell EMC VMAX3/VMAX All Flash arrays
encapsulate PowerProtect DD storage devices and prepares them to be used as
the native VMAX storage devices for data protection solutions (for example,
ProtectPoint).
Fibre Channel services require support from many Fibre Channel hardware
components.
• HBA
• FC Ports
• NPIV (Optional)
• Endpoints
• Initiators
• Access groups
To check on the status of the Fibre Channel, from the DDSM go to Hardware >
Fibre Channel page. Then you can review the Fibre Channel status that is shown
at the top of the page.
The Fibre Channel status can only be changed through the Command Line
Interface (CLI).
Here are CLI commands that enable or disables the Fibre Channel status.
scsitarget enable Enables the SCSI target subsystem. Role required: admin,
limited-admin.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
Ports53 are discovered and a single endpoint is automatically created for each port,
at startup. The properties of the base port depend on whether NPIV is enabled.
In non-NPIV mode, ports use the same properties as the endpoint, that is, the
WWPN for the base port and the endpoint are the same. In NPIV mode, the base
port properties are derived from default values. A new WWPN is generated for the
base port and is preserved to enable consistent switching between NPIV modes54.
When you enable an FC port, any endpoints using that port are also enabled. If the
failback-endpoints feature is used, any Failover endpoints that use this port for their
primary system address may be failed-back to the primary port from the secondary
port.
Disabling one or more SCSI target ports also disables any endpoints using that
port. If specified, the failover configured endpoints55 that use one or more target
ports as their primary system address are failed-over if the secondary port is
available.
Step One
To review the configuration of Fibre Channel (FC) ports, go to the Hardware >
Fibre Channel > Resources tab. Review the configuration summary table56 then
select a port. From the port that is selected review the configuration details57 in
Port Details.
56The summary information includes the System Address, WWPN, WWNN, and
enabled status. Also included are the NPIV status, the Fibre Channel Link status,
operation status, and the number of endpoints configured on the system.
57 The detailed information section shows the Fibre Channel HBA Model, installed
firmware version number, port id, link speed, topology, and connection type.
Step Two
To enable a FC port, navigate to the Hardware > Fibre Channel page, select
More Tasks > Ports > Enable to select the target ports58.
Select one or more ports from the list and select Next. Click Enable to enable the
port(s). Once complete, select Close59 to dismiss the Enable Ports Status dialog
box.
Step Three
The DD System Manager (DDSM) provides two methods to select and disable FC
ports. Navigate to the Hardware > Fibre Channel > Resources tab, and select
58If all ports are already enabled, a message to that effect is displayed otherwise
the Enable ports dialog box is displayed.
59Click Close if you do not wish to wait for the port enable process to complete.
The dialog box eventually displays a completion message
More Tasks > Ports > Disable to select the target ports. If all ports are already
disabled, a message to that effect is displayed otherwise the Disable Ports dialog
box is displayed.
Select one or more ports from the list and click Next. Wait for the disable process
to complete and select Close to dismiss the Disable Ports Status dialog box.
The Command Line Interface (CLI) command scsitarget port disable can
also be used. Refer to the Dell EMC DD OS Command Reference Guide for more
details.
Step Four
Navigate to Hardware > Fibre Channel > Resources tab, and select the port to
configure. Then select the pencil icon, show here as a pencil.
In the Topology, select Default, Loop Only, Point to Point, or Loop Preferred.
For the Speed select 1,2,4,8, or 16 Gbps, or auto. Click OK.
The Command Line Interface (CLI) command, scsitarget port modify can
also be used. Refer to the Dell EMC DD OS Command Reference Guide for more
details.
To enable NPIV60:
To disable NPIV:
Warning: Before you can disable NPIV, you must not have any ports
with multiple endpoints.
Reviewing FC Endpoints
1. Go to the Hardware > Fibre Channel > Resources tab. Click the (>) to expand
the endpoint configuration summary table.
2. Review the configuration summary table. Select an endpoint to view the
summary details61.
Endpoint configuration
summary
61 The summary information includes the endpoint name, WWPN, WWNN, system
address in use, enabled status, and link status. The detailed information section
shows the primary system address, secondary system address and if FCP2 Retry
is enabled.
Enabling/Disabling FC Endpoints
1. On the Hardware > Fibre Channel page, select More Tasks > Endpoints >
Enable.
2. In the Enable Endpoints dialog box, select one or more endpoints from the list,
then click Next.
3. Confirm all endpoints are correct and click Next. The Enable Endpoint Status
box is displayed. Select Close when the process completes.
1. Navigate to Hardware > Fibre Channel page, select More Tasks > Endpoints
> Disable. If all endpoints are already disabled, a message to that effect is
displayed.
2. In the Disable Endpoints dialog, select one or more endpoints from the list,
click Next.
3. Confirm the endpoints are correct. If the endpoint is associated with an active
service, a warning is displayed. Select Disable and the Disable Endpoint
Status dialog box appears.
4. Monitor the status of the Disable Endpoint process and select Close when the
process completes.
Configure FC Endpoints
To configure a FC Endpoint:
1. Navigate to the Hardware > Fibre Channel > Resources tab and select the
plus sign (+) to expand the endpoint configuration summary table.
2. Click the green plus icon to open the Add endpoint dialog box62.
3. For Endpoint Status, select Enabled or Disabled.
4. If NPIV is enabled, select a Primary system address from the drop-down list.
The primary system address must be different from any secondary system
address63.
5. If the endpoint cannot be created, an error is displayed. If there are no errors,
the system proceeds with the endpoint creation process.
Monitor the system as the endpoint is created. The system notifies you when
the endpoint creation process has completed.
62 In the Add Endpoint dialog, enter a Name for the endpoint. The endpoint name
can be from 1 to 128 characters in length. The field cannot be empty or be the word
"all,” and cannot contain the characters asterisk (*), question mark (?), front or back
slashes (/, \), or right or left parentheses (,).
Add
Endpoint
Deleting an Endpoint
1. Navigate to the Hardware > Fibre Channel > Resources tab and select the
plus sign (+) to expand the endpoint configuration summary table.
2. Select the endpoint(s) you wish to delete from the system.
3. Select the delete icon represented by a red X. This icon is not active unless an
endpoint is selected. The Delete Endpoint dialog box is displayed. If an
endpoint is in use, you are warned that deleting it might disrupt the system.
4. Verify the endpoints listed in the Delete Endpoint dialog box are correct. Click
Delete.
Delete an
Endpoint
A Fibre Channel (FC) initiator64 is the device that starts a SCSI session and sends
SCSI commands. The initiator is usually a backup server.
The worldwide port name (WWPN) assigned to an initiator's HBA port is needed to
identify an initiator to the PowerProtect DD system.
An initiator can be configured to support DD Boost over FC or VTL, but not both. A
maximum of 1024 initiators can be configured for a PowerProtect DD system.
64 On the PowerProtect DD system, you must identify the initiators that are allowed
to control the system through SCSI commands.
65 The PowerProtect DD system uses the initiator name to interface with the
initiator for VTL activity.
66Initiator aliases are useful because it is easier to reference a name than an eight-
pair WWPN number when configuring the system, including access groups.
Reviewing FC Initiators
To review the configuration of the Fibre Channel initiators, follow this process:
Add A FC Initiator
To add an initiator to provide a Fibre Channel backup client with the ability to
connect to the PowerProtect DD system:
1. Navigate to Hardware > Fibre Channel > Resources tab, begin the Initiator
Add process by selecting the (>) to expand the Initiators configuration
summary table if necessary.
Add an initiator
Deleting an FC Initiator
To delete a FC initiator:
1. Navigate to the Hardware > Fibre Channel > Resources tab and select the (>)
to expand the initiator configuration summary table.
2. Verify the target initiator if offline and not a part of any access group. Otherwise,
you will get an error message and the initiator will not be deleted. 68
67 Auto is used for standard addressing. Volume Set Addressing (VSA) is used
primarily for addressing virtual buses, targets, and LUNs.
3. Select the target initiator from the initiator configuration summary table.
4. Click the trash can icon.
A warning is provided in the Initiator Delete dialog box. Read the warning and Click
OK if you wish to proceed. Otherwise, click Cancel. After the process complete,
click OK.
Delete an Initiator
68You must delete all initiators in an access group before you can delete the
access group. If an initiator remains visible, it may be automatically rediscovered.
With an admin or limited-admin role, you can import tapes using the following
command:
• scsitarget initiator show list
• scsitarget initiator show detail
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters.
Access groups identify initiator and drives, changers, and LUNs they are permitted
to use.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
CIFS Status
In the DD System Manager, the Protocols > CIFS > Configuration page indicates
CIFS status. It can be enabled or disabled. Users with administrative privileges can
perform major CIFS operations such as enabling and disabling CIFS, setting
authentication, managing shares, and viewing configuration and share information.
CIFS clients write data to a share.
Backup servers that perform backup and restore operations using the CIFS
protocol need access to /data/col1/backup directory if no other backup
locations are created.
For administrative tasks, such as retrieving core and logfiles, the /ddvar directory
is used as a CIFS share.
The Protocols > CIFS > Configuration page enables you to perform CIFS
operations such as enabling and disabling CIFS, setting authentication, managing
shares, and viewing configuration and share information.
You can also manage CIFS backup and restores using the command line interface
(CLI). The cifs command contains all the options to manage CIFS backup and
restores between Windows clients and PowerProtect DD systems. Among other
functions, the cifs command can enable, disable, restart, and show the status of
CIFS. For complete information about the cifs command, see the DDOS
Command Reference Guide.
• cifs enable - The CIFS server starts listening on port 445. Role required:
admin, limited-admin
• cifs disable - The CIFS server starts listening on port 445. Role required:
admin, limited-admin
• cifs restart - Restarts all CIFS services. Role required: admin, limited-
admin.
• cifs status - Show status of CIFS: enabled or disabled. Role required:
admin, limited-admin, user, backup-operator, security, none.
Managing Shares
Using the DD System Manager, navigate to Protocols > CIFS > Shares page you
can create, modify, delete, enable, and disable CIFS shares. Using these
commands require admin or limited-admin roles.
The /data/col1/backup directory is not the only location for backup data.
However, it is the only backup location that exists on a system by default.
You can view detailed share information within the Shares tab.
You can also create, modify, enable, or disable shares by using the command line
interface..
Creating a Share
To create a CIFS share in the DD System Manager, go to Protocols > CIFS >
Shares > Create.
1 Characters included cannot contain any spaces or special characters like / ? “ <> ;
, = or extended ASCII characters.
2 To make a share available to all clients, use the wildcard *. To make the Share
available to only specific clients, use the client name or IP address. It is not
required to use both the name and the IP address.
3 When an * is present in the list, any other client entries are not used.
You can also create CIFS shares using the command line interface.
You can also create CIFS shares using the command line interface (CLI). The
cifs share command contains all the options to manage CIFS shares. Among
other functions, the cifs share command can create, destroy, enable, disable,
modify, and show the configurations of CIFS shares. For complete information
about the cifs share command, see the DDOS Command Reference Guide
located at dell.com/support.
• cifs share create - Creates a new share. Role required: admin, limited-
admin.
• cifs share destroy - Deletes a share. Role required: admin, limited-admin.
4A value of zero entered in the adjacent option would have the same effect as
Unlimited. Remember that there is a limit of up to 600 simultaneous connections,
depending on the specific PowerProtect DD system memory.
Wildcard access
Detailed information is displayed in the DDSM under Protocols > CIFS > Shares
and selecting a share5.
5In this example, the share ADMIN is selected and the Detailed Information is
displayed.
The share name does not need to match the directory name.8
You can also manage CIFS shares using the command line interface. The cifs
command contains all the options to manage CIFS backup and restores between
Windows clients and PowerProtect DD systems. Among other functions, the cifs
command can create and modify a share, and show the status of CIFS. For
complete information about the cifs command, see the DDOS Command
Reference Guide located at support.emc.com.
• cifs share create - Creates a new share. Role required: admin, limited-
admin.
8 Here, the share backup is the same name as the directory backup. It does not
need to be the same name if there is a preference. For example, you may create a
path /data/col1/backup2 but prefer to call the share that points to backup2 as HR
for easier identification of the specific share assignment.
CIFS Configuration
Default CIFS
authentication settings
In the DD System Manager, the Protocols > CIFS > Configuration page enables
you to view or modify the default CIFS authentication settings. If the settings must
be changed, click the Configure Options button.
The Configure Options dialog box enables you to modify three areas:
• Log Level 10
• Server Signing11
10Options are 1 through 5. One is the default system level that sends the least-
detailed level of CIFS-related log messages, five results in the most detail. Log
messages are stored in the file /ddvar/log/debug/CIFS/CIFS.log. The higher the
log level, the more likely it is to degrade system performance. Click Default to set
the level back to 1.
11The options are Enabled, Disabled, and Required. The default is Disabled.
This feature is disabled by default because it degrades performance. When
enabled, it can cause a 29 percent (reads) to 50 percent (writes) throughput
performance drop, although individual system performance varies.
12 Server Signing improves the security of the CIFS protocol by having the
communication that is digitally signed at the packet level. This enables the recipient
of the packets to confirm their point of origin and authenticity. This security
mechanism in the CIFS protocol helps avoid issues like tampering of packets. If the
packet is changed from the original packet that was sent by a CIFS client, the
system marks it as invalid.
15
In the DD System Manager, go to Protocols > CIFS. Click Configure in the
Configuration tab. The system navigates to the Administration > Access >
Authentication where you can configure authentication for Active Directory.
A Windows key distribution server requires the realm name and credentials for
Active Directory authentication.
Monitoring CIFS
In the Protocols > CIFS page you can monitor CIFS connection information
regarding the number of open connections, open files, connection limit, and open
files limit per connection.
In the Sessions area of the Connection Details dialog box, you can view several
statistics for CIFS connections.
• Computer displays the IP address or computer name that is connected with the
PowerProtect DD system for the session.
• User indicates the user operating the computer and connected with the
PowerProtect DD system.
• Open Files shows the number of open files for each session.
• Connection Time shows the connection length in minutes.
• Idle Time is the time since last activity of the user.
The Open Files area of the Connection Details window contains additional
information about CIFS connections.
• User shows the name of the computer and the user on that computer.
• Mode, displays the following values and each value has a corresponding
permission: 0 – No permission, 1 – Execute, 2 – Write, 3 – Execute and Write, 4
– Read, 5 – Read and Execute, 6 – Read and Write, and 7 – All Permissions.
• Locks displays the number of file locks, if any.
• Files displays the file location.
The CLI can be used to monitor CIFS activity. The following commands can be
used:
NFS Overview
The Network File System (NFS)16 is a distributed file system protocol. NFS enables
a user on a client computer to access files over a network in a manner similar to
how local storage is accessed. NFS, like many other protocols, builds on the Open
Network Computing Remote Procedure Call (ONC RPC) system.
Network File System (NFS) clients can have access to the system directories or
MTrees on the PowerProtect DD system17.
For administrative tasks, such as retrieving core and logfiles, /ddvar should be
available as an NFS mount point.
16The Network File System is an open standard that is defined in RFCs, enabling
anyone to implement the protocol.
18Backup servers using the NFS protocol need access to this directory if no other
backup locations have been created on the PowerProtect DD system
NFS Status
You can also check status, enable, and disable NFS using CLI commands.
In the CLI, the command nfs status indicates whether NFS is enabled or
disabled. If it is not active, nfs enable starts the NFS server.
• nfs status -
Indicates whether the NFS system is
operational. Role required: admin,
limited-admin, user, backup-operator,
security.
• nfs enable - Allows
all NFS-defined clients to access the
protection system. Role required:
admin, limited-admin
• nfs disable - Disables the NFS server, effectively disabling access from the
clients. Role required: admin, limited-admin.
NFS Exports
An export must be created and must specify the path (directory)19 that NFS clients
can access.
Client access to each export is assigned and removed from each export
separately20.
20For example, a client can be removed from /ddvar can still have access to
/data/col1/backup.
21 • A single asterisk (*) as a wildcard indicates that all backup servers are used as
clients.
You can use the command line to manage NFS exports. Use the following
commands:
• nfs export add - Adds a client or list of clients to one or more exports.
• nfs export del - Removes a client or a list of clients from existing exports.
• nfs export create - Creates a named export and adds a path.
• nfs export destroy - Destroys one or multiple NFS exports.
• nfs export modify - Updates an existing client or clients to an export or set
of exports.
The minimum role required for these commands is admin. Consult the DDOS
Command Reference Guide for more detailed information and specific syntax.
Kerberos Configuration
Kerberos tickets prove their identity in a secure manner. Both the client and the
server verify the identity of each other.
Kerberos Authentication
The authentication screen displays after selecting Kerberos Mode Configure from
the NFS screen in the DD System Manager.
• If you select Disabled, NFS clients do not use Kerberos authentication and
CIFS clients default to Workgroup authentication.
• If you select Windows/Active Directory, both NFS and CIFS clients use
Kerberos authentication.
• If you select UNIX, only NFS clients use Kerberos authentication. CIFS clients
default to Workgroup authentication.
Monitoring NFS
In the DD System Manager, the Protocols > NFS > Active Clients tab, displays
any configured NFS clients and the related mount paths that have been connected
in the past 15 minutes. NFS clients and related mount paths connected longer than
15 minutes are not displayed.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
Fast Copy.................................................................................................................. 33
Fast Copy .......................................................................................................................... 34
Perform a Fastcopy............................................................................................................ 36
Fastcopy Operations .......................................................................................................... 37
MTree Definition
MTrees
Subdirectories inherit the
same permissions, policies,
and reporting as the parent
directory
Management Trees (MTrees) are specific directories that are used to provide more
granular management of data so data from different sources can be managed and
reported on separately. Various backup operations are directed to individual
MTrees1.
Select the links below to learn more about MTrees and their function within DDOS.
1For example, you can configure directory export levels and quotas to separate
and manage backup files by department such as HR or Sales.
MTree Structure
Default MTree
/data/col1/backup
User-created MTrees
Subdirectories can be created within all MTrees, including the default MTree. The
DDOS recognizes and reports on the cumulative data contained within the entire
MTree.
MTree Benefits
Increased granular reporting Each department, Retention lock can be applied Logical, pre-compression
of space and deduplication geography, or customer at the MTree level space can be limited through
rates is a benefit. could have their own quotas
independent storage location.
3 Snapshot is a common industry term denoting the ability to record the state of a
storage device or a portion of the data being stored on the device, at any given
moment and to preserve that snapshot as a guide for restoring the storage device,
or portion thereof. Snapshots are used extensively as a part of the PowerProtect
DD data restoration process.
4DD Retention lock is an optional feature that the PowerProtect DD system uses to
securely retain saved data for a given length of time. DD Retention lock protects
data from accidental or malicious deletion.
5Another major benefit is to limit the logical, precomp, space the specific MTree
uses through quotas. Quotas can be set for MTrees used by CIFS, NFS, VTL, or
DD Boost data.
MTree Limits
MTree Quotas
Soft Limit
Hard Limit
MTree quotas allow you to set limits on the amount of logical, precomp space.
Quotas can only be set on user-created MTrees and not on default MTrees,
Quotas can be set on user-created MTrees, but not the default MTree, /backup.
Quotas are independent of protocol. They can be set for MTrees used by CIFS,
NFS, PowerProtect DD VTL, or DD Boost data.
There are two types of quotas: soft limits6 and hard limits7.
6When a soft limit is reached, the system generates an alert, but operations
continue as normal.
7When the hard limit is reached, any data backing up to this MTree fails. The
system generates an alert and an out of space error (EMOSP for VTL) is reported
You may set soft, hard, or both soft and hard limits8.
to the backup app. To resume backup operations after data within an MTree
reaches a hard limit quota, you must either delete sufficient content in the MTree,
increase the hard limit quota, or disable quotas for the MTree.
8If you set both limits, the soft limit must be less than the hard limit. The smallest
quota that can be set is 1 MiB.
An administrator can set the storage space restriction for an MTree to prevent it
from consuming excess space.
Creating MTrees
To create an MTree in the System Manager, go to Data Management > MTree >
Create. In the Create MTree dialog, type the name of the MTree in the MTree
name field. Names are case-sensitive.
You can also set both pre-comp soft limits, hard limit and combined limits for the
MTree you create in this window.
With an admin or limited-admin role, use the DD System Manager and select either
the MTree tab or Quota tab.
• When setting quotas from the Quota tab, select Data Management > Quota.
• Make sure Quota Enforcement is Enabled.
• Select one or more MTrees.
• Click the Configure Quota button and set your quota configuration.
You can also configure MTree quotas using the command line interface.
When configuring quotas for MTrees you can set a specific value for pre-comp soft
or hard limits or both hard and soft limits. Click OK when you are finished.
With an admin or limited-admin role, you can disable/enable quotas using the
following commands:
• quota capacity set – Sets quota for named MTrees, and storage units.
Use this command to set hard and soft limits.
• quota capacity enable – Enables MTree capacity quota limits. Use this
command after you have set quotas.
• quota capacity disable – Disables MTree quota limits and restores the
limits to the default, unlimited, state.
• quota capacity status – Shows status for quota function.
Data Management
Select an MTree and the Summary pane presents current information about the
selected MTree.
You can also monitor MTrees and quotas using the command line interface.
10The selected MTree displays any quota limits, pre- and postcomp usage, as well
as compression ratios for the last 24 hours, the last seven days, and current weekly
average compression.
For real-time monitoring of MTrees and quotas, the following commands can be
used from the command line interface:
• mtree show compression <mtree_path> [tier {active |
archive}] [summary | daily | daily-detailed] {[last <n> {
hours | days | weeks | months } | [start <date> [end
<date>]]} - Show MTree compression statistics
• quota capacity show {all | mtrees <mtree-list> | storage-
units <storage-unit-list> | tenant-unit <tenant-unit>} - List
quotas for MTrees and storage-units
Alerts
In the DD System Manager, the Health > Alerts displays MTree quota alerts. They
are displayed in all of the tabs – Current Alerts, Alerts History, Notification, and
Daily Alert Summary.
Soft limit: When this limit is reached, an alert is generated through the system, but
operations continue as normal. The Severity level is Warning.
Hard limit: When a hard limit is set and the limit is reached, data cannot be written
to the MTree and all write operations fail until data is deleted from the MTree. You
can also increse the hard limit or disable quotas for that MTree. A critical hard limit
alert is also generated through the system and an out of space error is reported to
the backup app.
These alerts are also reported in the Home > Dashboard > Alerts pane.
Network File System (NFS) and Common Internet File System (CIFS) can access
the MTrees within the /data/col1 directory by configuring CIFS shares and NFS
exports.
• /data/col1/<MTreeName>
• /data/col1/<MTreeName>/arbitrary/subdirectory/path
Other protocols have special storage requirements within the MTree structure and
are discussed in their respective modules.
CIFS shares are configured in the DD System Manager in the Protocols > CIFS >
Shares tab.
Click the Create button to create a CIFS share. This is where you specify the share
name, which can be name appropriate for the share. In this example the share is
ADMIN for the data backed-up for the HR administrative staff. Do not confuse the
name of this share with the notion that these shares might be used as user shares
which they definitely are not.
You also specify the directory path and clients for the MTree you want to use.
When the share is complete, view it in the CIFS tab by share name. The Directory
Path Status verifies whether the path to the share exists.
Snapshot Description
What is a snapshot?11
11A snapshot is a common industry term denoting the ability to record the state of a
storage device or a portion of the data being stored on the device, at any given
moment and to preserve that snapshot as a guide for restoring the storage device,
or portion thereof.
Snapshot Benefits
12 A snapshot copy is made instantly and is available for use by other applications
for data protection, data analysis, and reporting and data replication. The original
copy of the data remains available to the applications without interruption, while the
snapshot copy is used to perform other functions on the data.
14Snapshots continue to place a hold on the original data they reference even
when the backups have expired.
15Snapshots are useful for saving a copy of MTrees at specific points in time. One
example is before a DDOS upgrade. The snapshot can later be used as a restore
point if files must be restored from that specific point in time.
Restore Point
Backup of a production
Snapshot
file
Snapshot copies only the metadata pointers to the production data for a specific
point in time. In this case, 22:24 GMT. The copy is quick and places minimal load
on the production systems. If needed, the snapshot can be later used as a restore
point.
Snapshots are a point-in-time view of a file system. They can be used to recover
previous versions of files and also to recover from an accidental deletion of files.
When changes occur to the production data (in this case segments 1 and 2 are no
longer part of the file) and more data is written (segments 5 and 6), the file system
removes the pointers to the original data no longer in use and adds pointers to the
new data. The original data segments (1 and 2) are still stored, enabling the
snapshot metadata pointers to continue to point to the data as saved at the specific
point in time. Data is not overwritten, but changed data is added to the system and
new pointers are written.
When changed production data is backed up, more blocks are written and pointers
are changed to access the changed data. The snapshot maintains pointers to the
original, point-in-time data. All data remains on the system provided pointers
reference the data.
Snapshot Operations
As an example, snapshots for the MTree named, “backup” are created in the
system directory /data/col1/backup/.snapshot. Each directory under
/data/col1/backup also has a .snapshot directory with the name of each
snapshot that includes the directory. Each MTree has the same type of structure,
so an MTree named HR would have a system directory
/data/col1/HR/.snapshot and each subdirectory in /data/col1/HR would
have a .snapshot directory.
Creating a Snapshot
You can create a snapshot in the DD System Manager or using the command line
interface. Snapshots can be managed with schedules
With an admin or limited-admin role, you can create and expire snapshots using
the following command line commands:
• snapshot create snapshot mtree mtree-path [retention {date
| period}] – Creates a snapshot.
• snapshot expire snapshot mtree mtree-path [retention {date
| period | forever}] – Sets or resets the retention time of a snapshot.
To expire a snapshot immediately, use the snapshot expire operation with
no options.
• snapshot rename snapshotnew-name mtree mtree-path – Renames
a snapshot for a specific MTree.
You can create a snapshot in the DD System Manager or using the command line
interface.
Schedules View
You can create a weekly or monthly snapshot schedule using the DD System
Manager.
• Select Data Management > Snapshots > Schedules to open the Schedules
view.
• Click Create.
Details
In the Name text field, enter the name you want to call the schedule.
Enter a string of characters and variables that translates to a snapshot name (for
example, scheduled-%Y-%m-%d-%H- %m, translates to "scheduled-2012-04-12-
17-33"). Use alphabetic characters, numbers, _, -, and variables that translate into
current values.
Click Next.
Execution
Execution
1. At Specific Times—Click Add and in the Time dialog that appears, enter the
time in the format hh:mm, and click OK.
2. In Intervals—Click the drop-down arrows to select the start and end time hh:mm
and AM or PM. Click the Interval dropdown arrows to select a number and then
the hours or minutes of the interval.
Click Next.
Associate MTrees
Identify and move the MTrees you want to associate with this schedule to the
Selected MTrees column.
Click Next.
Summary
Review the Summary window and click Finish to add the schedule.
With an admin or limited-admin role, you can create and manage snapshot
schedules using the following command line command:
In the MTree summary page, there is a section that is called MTree Replications
and that section contains snapshot information.
The Snapshots pane in the MTree summary page enables you to see the total
number of snapshots that are collected, expired, and unexpired, as well as the
oldest, newest, and next scheduled snapshot.
You can associate configured snapshot schedules with a selected MTree name.
Click Assign Schedules, select a schedule from the list of snapshot schedules and
assign it. You can also create more snapshot schedules.
Fast Copy
Fast Copy
/data/col1/backup/Recovery
10-31-2020
/data/col1/HR/.snapshot/10-31-2020
10-31-2020
10-15-2020
19The difference between snapshots and fast copied data is that the fast copy
duplicate is not a point-in-time duplicate. Any changes that are made during the
Fastcopy makes a copy of the pointers to data segments and structure of a source
to a target directory on the same PowerProtect DD system.
You can use the fastcopy operation to retrieve data stored in snapshots.20
data copy, in either the source or the target directories, is not duplicated.
Fast copy is a read/write copy of a point-in-time instance at the time it was made,
and a snapshot is read-only.
20 In this example, the /HR MTree contains two snapshots in the /.snapshot
directory. One of these snapshots, 10-31-2020, is fast copied to /backup/Recovery.
Only pointers to the data are copied, adding a 1% to 2% increase in used data
space. All referenced data is readable and writable. If the /HR MTree or any of its
contents is deleted, none of the data that is referenced in the Fast Copy is deleted
from the system.
Perform a Fastcopy
1. Select Data Managment > File System > Summary > Fast Copy.
2. In the Source text box, enter the pathname of the directory where the data to
be copied resides. For example, /data/
col1/backup/.snapshot/snapshot-name/dir1 is an approptiate path.
3. In the Destination text box, enter the pathname of the directory where the data
will be copied to. For example, /data/ col1/backup/dir2is an approptiate
path. This destination directory must be empty, or the operation fails.
4. If the Destination directory already exists, you can click the checkbox Overwrite
existing destination if it exists.
5. Click OK. The contents of dir1 will now also be found under dir2.
Fastcopy Operations
This data must be manually identified and deleted to free up space. Then, space
reclamation23 must be run to regain the data space held by the fastcopy24
21 Snapshot content is not viewable from a CIFS share or NFS mount, but a fast
copy of the snapshot is fully viewable. From a fast copy on a share or a mount, you
can recover lost data without disturbing normal backup operations and production
files.
22The source and destination may not be equal if either is changed during the copy
operation.
24When backup data expires, a fast copy directory prevents the PowerProtect DD
system from recovering the space that is held by the expired data because it is
marked by the fast copy directory as in-use.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
Appendix ................................................................................................. 49
Replication Description
WAN/LAN
PowerProtect DD
Replication Source
PowerProtect DD
Replication Destination
1The replication process only copies information that does not exist on the
destination system. This technique reduces network demands during replication
because only unique data segments are sent over the network.
• Data recovery2
• Multi-site backup 3
• Archive consolidation4
3 Multi-site replication can replicate the state between different deployed sites to a
single replication destination.
4 The replication process only copies and consolidates data from remote systems
that does not exist on the destination system. This technique reduces network
demands during replication because only unique data segments are sent over the
network.
Collection Replication
Head of source Head of source Head of source Head of source
collection log collection log collection log collection log
With collection replication, all user accounts and passwords are replicated10 from
the source to the destination.
7 Transferring data in this way means comparing the heads of the source and
destination logs and catching-up, one container at a time. If collection replication
lags behind, it continues until it catches up.
8 Collection replication uses the logging file system structure to track replication.
11 Because there is only one collection per PowerProtect DD, collection replication
is an approach to system mirroring. Collection replication is the only form of
replication that is used for true disaster recovery. The destination system cannot be
shared for other roles. It is read-only and shows data only from one source. After
the data is on the destination, it is immediately visible for recovery.
12After replication is configured, this system is dedicated to receive data from the
source system. The destination immediately offers all backed up data, as a read-
only mirror, after it is replicated from the source.
13 The destination system can only accept data from the replication process. No
data, including snapshots and files, can be written to the destination system except
through the replication process. If you must write data to the destination, you must
first disable replication by breaking the replication context. Unfortunately, if the
context has been broken, a resync cannot be performed. Collection replication
supports Retention Lock Compliance.
14DD Replicator software can be used with the optional Encryption of Data at Rest
feature, enabling encrypted data to be replicated using collection replication.
Collection replication requires the source and target to have the exact same
encryption configuration because the target is an exact replica of the source data.
In particular, the encryption feature must be turned on or off at both source and
target. If the feature is turned on, the encryption algorithm and the system
passphrases must match. Encryption parameters are checked during the
replication association phase. During collection replication, the source system
transmits the encrypted user data along with the encrypted system encryption key.
The data can be recovered at the target, because the target machine has the same
passphrase and the same system encryption key.
Directory Replication
16The source and destination directories can be on different levels under the
/backup directory.
Directory replication operates based on file system activity. When activity occurs on
the system, such as a new directory, change of permissions, or file rename the
source system communicates the update to the destination.17
17 In cases where file closures are infrequent, the PowerProtect DD source system
forces the data transfer periodically.
19 If there is new data, the source system, A, first creates a list of file segment IDs
in the file. The source sends this list to the destination system, B. The destination
system examines the list of segment IDs to determine which are missing. The
destination sends a list of the missing segments to the source. The source now
sends the missing segments to the destination. In this way, bandwidth between the
source and destination system is used more efficiently.
20Directory replication can receive backups from both CIFS and NFS, clients
provided separate directories are used for each. Do not mix CIFS and NFS data in
the same directory. The directory replication source cannot be the parent or the
child of a directory that is already being replicated.
Directory replication contexts will reach end of life in a future DDOS release.
MTree Replication
The MTree replication source creates periodic snapshots24. The source creates a
delta list of segment IDs that were not in the last snapshot. The source transmits
this delta list to the destination. The destination examines the delta list and sends
back a list of what it still needs. The source transmits the needed data segments to
the destination.
23This means that all metadata, file data, and everything else that is related to the
MTree is replicated. MTree replication uses snapshots to determine what to send to
the destination.
24The source compares the latest snapshot against the snapshot that was used for
the last replication transfer.
The destination PowerProtect DD system does not expose the replicated data until all data
for that snapshot has been received25. Because the directory tree structure is part of the
data in the snapshot26, files do not show out of order at the destination.
MTree replication uses the same WAN deduplication mechanism as directory replication.27
27This way MTree replication avoids sending redundant data across the network.
MTree replication also supports the same topologies that directory replication
supports.
28MTree structure provides the greatest control and flexibility over its data being
replicated. Careful planning of your data layout provides the greatest flexibility
when managing data under an MTree structure.
29If you want to implement MTree replication, you must move any data from the
existing directory structure within the /backup directory to a new or existing MTree.
A replication pair using that MTree must be created.
Replication Initialization
Source Destination
High-speed low-latency link
Initialization is the process of transferring the initial replication data from the source
system to the target system.30
Consider the following when you plan to initialize your replication destination:
When data is successfully replicated to the destination system, you can move
the system back to its intended location31.
30If the source PowerProtect DD system has a high volume of data before
configuring replication, the initial replication can take some time over a slow link. To
expedite the initial data transfer to the destination system, you can bring the
destination system to the same location as the source system to use a high-speed,
low-latency link.
31Once data is initially replicated to the destination system, the source system
sends only new data from that point onwards.
Configuring Replication
The hostname portion of the URL the same as the output of the net show
hostname command. The path is the logical path to the target directory or MTree.
The path for a directory URL must start with the hostname, followed by
/data/col1/backup and ends with the name of the target directory.
The path for an MTree URL starts with the hostname, followed by /data/col1
and ends with the name of the target MTree.
For collection URLs, a path is not identified since a collection is the entire data set
belonging to a particular PowerProtect DD host.
Review Configuration
Select a context from the list in the replication summary table to see detailed
information pertaining to the selected context.33
32Selecting a context causes the system to display detailed information about that
context in the Detailed Information section of the screen.
You can also review the configuration of the replication feature through the
command line.
33Since collection, MTree, and directory contexts have different requirements, the
detailed information shown changes depending on the context type.
Add a New
System
Before you can configure replication between two systems, you must first configure
the destination PowerProtect DD system to let the source system manage it. This
process is called adding a system.
1. Verify the source and destination systems are running compatible DDOS
versions.
2. In the Replication > Automatic > Summary tab, select Manage Systems.
3. Click the plus sign (+). The Add System dialog box appears.
4. Enter the partner system hostname and the password that is assigned to the
sysadmin user.
5. Select OK when the information for the partner system is complete. Select OK.
The Verify Certificate dialog box appears.
6. If the system is successfully added, the DD System Manager returns to the
Manage Systems dialog box and the newly added partner system appears in
the list.
If the partner system is unreachable after adding it to the Manage Systems list.34
34 Ensure that there is a route from the managing system to the system being
added. If a hostname (either a fully qualified domain name (FQDN) or non-FQDN)
is entered, ensure it is resolvable by both systems. Configure a hostname for the
source and destination replication system. Ensure that a DNS entry for the system
exists, or ensure that an IP address to hostname mapping is defined.
35If the device being configured is the source for the context, select Outbound. If
the device being configured is the destination in the context, select Inbound.
Select a link below to view creation instructions specific to the replication type.
You can also create replication contexts using the command line interface.
The listen port36 is the TCP port the replication destination system monitors for
incoming connections. You can change the value of the listen port.37
The three replication source systems should connect38 to the single replication
destination.
36The listen port is a global setting. All contexts for which this system is a
destination monitor this port. All replication source systems must be configured to
connect to this particular port value.
37If a firewall configuration or other network issues interfere with the default
connections between the replication and source, you can modify the listen port.
The connection port39 is the TCP port the source system uses to communicate to
the replication destination.
Because the replication destination has a default listen port value of 2051, each
replication source needs a corresponding connection port value of 2051.40
39The connection port is configured per context. It is not a global setting. The
default value for the connection port is 2051.
40 The first two systems are configured with the correct connection port, but the
third system is using incorrect connection port value, 3030, that prevents a
replication connection with the destination.
When using the DD System Manager, you can specify a non-default listen port
value by first going to the Replication > Automatic > Advanced Settings tab on
the system.
From the Network Settings pane, you can verify the current listen port value and
change the port value as needed.
When using DD System Manager, you can specify a non-default connection port
value when you create the context. The value can be modified after the context is
created.
1. Navigate to the Replication > Automatic > Summary tab on the source
system.
2. Select a context from the context summary table.
3. Select Modify Settings to modify an existing replication pair.
4. Select the checkbox Use Nondefault Connection Host.
5. Change the Connection Port to a new value.
6. Click Next to continue the context modification process.
Low-Bandwidth Optimization
Destination sends a
Source sends a list of LBO eligible
new segment list segments
Delta (difference)
Determines S16 is sent from source to
similar to S1. The destination
delta is +6
Do not use LBO if the system requires maximum file system write performance.41
LBO is enabled on a per-context basis to all file replications jobs on a system. LBO
must be enabled on both the source and destination PowerProtect DD
appliances.42
41Only enable LBO for replication contexts that are configured over WAN links with
less than 6 Mb per second of available bandwidth.
42If the source and destination have incompatible LBO settings, LBO is inactive for
that context.
You might need to further tune your system to improve LBO functionality43.
When using DD System Manager, you can enable LBO when you create a
replication context, or the LBO setting can be modified after the context is created.
43Use bandwidth and network-delay settings together to calculate the proper TCP
buffer size and set replication bandwidth for replication for greater compatibility with
LBO.
45Delta comparison reduces the amount of data that is replicated over a low-
bandwidth WAN by eliminating the transfer of redundant data that is found with
replicated, deduplicated data. This feature is typically beneficial to remote sites with
lower-performance PowerProtect DD models.
When you enable the encryption over wire option on a replication context47, the
system must first process the data that it reads from the disk.48
The replication source encrypts the data49 using the encryption over wire algorithm
before the system transmits the data to the destination system.50
You can also modify the encryption over wire setting after the context is created:
46Enable encryption over wire if you are concerned about the security of your
network link.
47Encryption over wire must be enabled on both the source and destination
systems. If there is a mismatch, the context is disabled.
48If you have the data at rest encryption feature enabled, the source system must
decrypt the data before it can be processed for replication. Otherwise, the data is
read from the source system.
49If the data at rest encryption feature is enabled on the destination PowerProtect
DD system, the data must be encrypted using the method that is specified by the
data at rest encryption feature. If the data at rest encryption feature is not enabled,
the destination system writes the data to the disk using normal processes.
50When the replication destination system receives the replication traffic, it must
decrypt it using the encryption method that is employed by the replication feature.
When using the DD System Manager, you can enable the encryption over wire
feature when you create the context:51
1. Navigate to the Replication > Automatic > Summary tab on the source
system.
2. Select Create Pair to create a replication pair.
3. Complete the configuration of the Create Pair > Create tab.
4. Select the Advanced tab.
5. Select the checkbox Enable Encryption Over Wire.
6. Click OK when finished.
51 You can also modify the encryption over wire setting after the context is created.
To modify the amount of bandwidth used for replication, you can set replication
throttle for replication traffic.
The Throttle Settings52 area shows the current settings for any temporary
overrides. If you configure an override, this section shows the throttle rate, or 0
which means all replication traffic is stopped.
To add throttle settings from the Add Throttle Settings window, do the
following:
1. Click the checkboxes to set the days of the week that throttling is active.
2. Set the throttling start time.
3. Set the throttling rate53. Be sure to select Bps54, Kbps, etc., then click OK.
52The throttle settings area also shows the configured schedule. You should see
the time for days of the week on which scheduled throttling occurs.
These alerts are also reported in the Home > Dashboard > Alerts pane.
54 You can disable all replication traffic when you select the 0 Bps (disabled) option.
55
If you do not select this option, the override throttle stays in effect until you
manually clear it.
Replication Scheduler
This functionality was introduced because there are issues with some vendor
backups where it reopens the files, overwrites file metadata at the start of the file,
and appends to the files in batches.
Because of this, the workloads cannot take advantage of the Automated Multi-
Streaming (AMS)56 functionality or synthetic replication.
Some customers already had a workaround in place. They used two cron jobs57:
• One cron job to disable the replication during the backup window.
• Another cron job to reenable the replication for the context after the backup is
done.
57 A "cron job" or cron is a process or task that runs periodically on a UNIX system.
Displays all scheduled enable and disable times for all replication contexts on
the system.
Replication Output
The output in DDOS now includes the following message when adding or
displaying directory replication contexts:
• Support for directory replication will be removed from a future DDOS release.
Use migration of directory replication to MTree replication. Contact your
contracted support provider or visit us online at https://support.emc.com.
Monitoring Replication
Replication Reports
There are two types of replication reports available for PowerProtect DD: the
replication status report58 and the replication summary report59.
58The replication status report displays three charts describing the status of the
current replication job running on the system. This report provides a snapshot of all
replication contexts to help understand the overall replication status.
Data Recovery
In the case of a disaster destroying onsite data, the offsite replica is used to restore
operations.62
60With collection, directory and pool replication, the system uses the term "data
recovery." With MTrees, data recovery is termed, "data resynchronization."
61 Lost or corrupted files are recovered from the onsite PowerProtect DD system
since files are easy to locate and read at any time.
62Data on the replica or target system is immediately available for use by recovery
systems. When a PowerProtect DD system at the main site is repaired or replaced,
the data can be recovered using a few simple recovery commands. During
collection replication, the destination context must be fully initialized for the recover
process to be successful.
Data Recovery
Data Resynchronization
63Resynchronization is the process of recovering (or bringing back into sync) the
data between a source and a destination replication pair after a manual break. The
replication pair is resynchronized so both systems contain the same data.
Resynchronization is available for MTree, directory and pool replication, but not for
collection replication.
This process adds the context back to both the source and destination systems and
starts the resync process. The resync process can take between several hours and
several days, depending on the size of the system and current load factors.
Movie:
Managing Replication
Replication Guidelines
PowerProtect DD A and
B make up the
replication pair.
Context #1
A is the source
B is the destination
Context #2
B is the source
A is the destination
Together, the replication source and destination appliances are called a pair. The
connection that is defined between the replication source and destination is a
context65.
Replication Streams
Replication source
(read) streams
Replication
destination (write)
streams
Replication source
(read) streams
Replication
destination (write)
streams
A replication context can support multiple replication streams. The stream resource
utilization within a PowerProtect DD appliance is equivalent to a read stream
(source context) or a write stream (destination context).
Replication Types
DD Replicator software offers four replication types.
66 This type of replication is simple and requires fewer resources than other types.
It can provide higher throughput and support more objects with less overhead.
67This process transfers only the deduplicated changes of any file or subdirectory
within the selected PowerProtect DD file system directory.
69By default, MTrees which can be replicated, are used when a media pool is
created. It uses the same WAN deduplication mechanism as directory replication to
avoid sending redundant data across the network.
70 Snapshots also reduce replication churn, making WAN use more efficient.
Replication Topologies
• One-to-one replication71
• Bi-directional replication72
• One-to-many replication73
• Many-to-one replication74
• Cascaded replication75
76To avoid this situation, you must disable Retention Lock on the MTree. If you
enable retention lock in a replication context, the replicated destination context
contains data that is retention locked.
Collection replication
• col://<hostname>
• col://ddsys
MTree replication
• mtree://<hostname>/data/col1/<mtree-name>
• mtree://ddsys/data/col1/engineering
Directory replication
• dir://<hostname>/data/col1/backup/<dir-path>
• dir://ddsys/data/col1/backup/corp/finance
With an admin or limited-admin role, you can configure a replication context using
the replication add command. Following are example commands for
collection, directory, and MTree context creation:
• replication add source col://system-dd1.chaos.local
destination col://systemdd2.chaos.local - to add a collection
replication context
• replication add source mtree://system-
dd1.chaos.local/data/col1/mtree1 destination
mtree://system-dd2.chaos.local/data/col1/dstmtree1 max-
repl-streams 6 destination-tenantunit tu1 - to add a directory
replication context
• replication add source dir://system-
dd1.chaos.local/backup/dir1 destination
dir://systemdd2.chaos.local/backup/dir1 - to add an MTree
replication context
Create a replication status report when you want to evaluate file system or
replication data that is collected in the past:
1. In the PowerProtect DD Management Center, select Reports > Management.
2. Click Add.
3. Select System Reports.
4. The schedule is shown with the default settings.
5. Provide email addresses to contact when the report is finished or if an error
occurs.
6. A summary screen shows the completed configuration.
The replication status report generates a summary of the report configurations.
7. If the configurations are correct, click Finish.
8. The Replication Report is available in Reports > Management.
9. Double-clicking the Report icon opens the details.
10. This replication report contains 10 pages and each report has three sections,
Status Overview, System Pairs, and System Details.
To open the report, launch the DDMC and double-click the Report icon.
A typical report contains several pages and presents three sections: Replication
Status Overview77, Replication Pairs78, and System Details79.
On-Demand Replications status shows that the system with failed outbound on-
demand replications ranked by percentage.
78The Replication Pairs section reports errors, warnings, or unknown status for
automatic and on-demand replications.
79The System Details section reports on both source and destination systems. It
provides inbound and outbound statistics and displays a trend analysis over the
last 30 days.
More details show system details for source and destination systems that include
replications with lags over thresholds, on-demand replications by highest
percentage of failed transfers, inbound automatic replications, and inbound on-
demain replications.
The last section provides details about outbound and cascaded automatic
replications and outbound on-demand replications.
On-Demand Replications status shows that the system with failed outbound on-
demand replications ranked by percentage.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
DD Boost Features
Backup Hosts
Clients
DD Boost DD Boost
Library Library
Server
DD Boost
DD Boost is a proprietary Dell EMC protocol that is more efficient than CIFS or NFS
for transferring data to a PowerProtect DD appliance. DD Boost is an efficient data
transfer protocol with options to increase efficiencies.
1To improve data transfer performance and increase reliability, you can create a
group interface using the advanced load balancing and link failover feature.
2The application host is aware of, and manages replication of backups that are
created with DD Boost.
3DD Boost security options include setting the DD Boost authentication mode and
encryption strength. The PowerProtect DD appliance compares the global
authentication mode and encryption strength against the per-client authentication
mode and encryption strength to calculate the effective authentication mode and
authentication encryption strength.
The system does not use the highest authentication mode from one entry, and the
highest encryption settings from a different entry. The effective authentication mode
and encryption strength come from the single entry that provides the highest
authentication mode.
4 You can encrypt the data replication stream by enabling the file replication DD
Encryption option. If DD Boost file replication encryption is used on systems without
the data at rest option, it must be set to on for both systems.
The second full backup is synthesized using pointers to existing segments on the
PowerProtect DD appliance. This optimization reduces the frequency of full
backups, thus improving recovery point objectives (RPO) and enabling single-step
recovery to improve recovery time objectives (RTO).
Also, optimized synthetic backups further reduce the load on the LAN and
application host.
6 If you use file replication over a low-bandwidth network, you can increase
replication network efficiency by using low-bandwidth optimization. This feature
provides extra compression during data transfer. Low-bandwidth compression is
available to PowerProtect DD appliances with an installed Replication license.
Technology Interoperability
PowerProtect Data
Backup Exec VDP Advanced Data Protector SAP HANA
Avamar NetWorker Manager NetBackup vRanger NetVault Veeam Greenplum RMAN SAP DB2 SQL
App
Server
Storage Units
The PowerProtect DD appliance exposes user-created disk volumes that are called
storage units (SUs) to a DD Boost-enabled application host. Access to the SU is
operating system independent. Multiple application hosts, when configured with DD
Boost, can use the same SU on a PowerProtect DD appliance as a storage server.
Storage units can be monitored and controlled the same as any data managed
within an MTree. You can set hard and soft quota limits and receive reports about
the contents of any MTree, includeing a DD Boost storage unit.
Server
DD Boost
Distributed Segment Processing (DSP) shares deduplication duties with the backup host.
With DSP enabled, the With DSP enabled, the DSP has several benefits,
backup host performs PowerProtect DD including:
these functions: appliance performs these • More efficient CPU
functions:
• Segments the data utilization
• Filters the fingerprints
• Creates fingerprints of • Reduced utilization of
segment data and • Requests data not network bandwidth7
previously stored
• Sends fingerprints to • Less time to restart
the PowerProtect DD • Records references to failed backup jobs8
appliance previously stored data • Distribution of the
and writes new data
• Compresses data workload
• Sends only unique data
segments to the
PowerProtect DD
appliance
DD Boost can operate with DSP either enabled or disabled. DSP must be enabled
or disabled on a per-system basis. Individual backup clients cannot be configured
differently than the PowerProtect DD appliance.
7The network bandwidth requirements are reduced because only unique data is
sent over the LAN to the PowerProtect DD appliance. DSP enables use of existing
1-GbE infrastructure to achieve higher throughput than is physically possible over
1-GbE links with traditional backups without DSP.
8 If a job fails, the data that is already sent to the PowerProtect DD appliance does
not need to be sent a second time. This reduces the load on the network and
improves the overall throughput for the failed backups upon retry.
DD Boost
Clients Backup Host
DD Boost Library
File replication done at the
request of DD Boost-
aware backup software
LAN
DD Boost
Server WAN
9The process can be optimized for WANs, reducing the overall load on the WAN
bandwidth required for creating a duplicate copy.
10Managed file replication can be used only with MTrees established with DD
Boost storage units.
11The MTree limit is a count of both standard MTrees, and MTrees created as DD
Boost storage units. The limit depends on the PowerProtect DD appliance and the
DDOS version. See the DDOS Administration Guide for detailed information about
the number of supported MTrees for a specific model.
Backup Hosts
Application
layer
4-port interface
aggregation
group
NIC NIC
You can manage the physical interfaces that connect the system to a network and
create logical interfaces to support load balancing and link failover.
The advanced load balancing and link failover feature supports combining multiple
Ethernet links into an interface group.
• Only one of the interfaces on the PowerProtect DD appliance is registered with
the backup application12.
• Load balancing provides higher physical throughput to the PowerProtect DD
appliance compared to configuring the interfaces into a virtual interface using
Ethernet-level aggregation.
The links connecting the backup hosts and the switch that connects to the
PowerProtect DD appliance are placed in an aggregated failover mode13.
Advanced load balancing and link failover work with interfaces of different speeds
in the same interface group16.
12DD Boost negotiates with the PowerProtect DD appliance on the interface that is
registered with the backup application to obtain an interface to send the data.
14Any of the available aggregation technologies can be used between the backup
servers and the switch.
15 If an interface fails, all in-flight jobs to that interface transparently fail over to a
healthy interface in the interface group. Any jobs started after the failure are routed
to the healthy interfaces. You can add public or private IP addresses for data
transfer connections.
During a traditional full backup, all files are copied from the client to a backup host
and the resulting image set is sent to the PowerProtect DD appliance. The files are
transferred even though those files may not have changed since the last
incremental or differential backup. Copying data that has not changed since the last
full backup results in more bandwidth and time used to perform a backup operation.
In contrast, during a synthetic full backup, the previous full backup and the
subsequent incremental backups on the PowerProtect DD appliance are combined
to form a new full backup. The new full synthetic backup is an accurate
representation of the client file system at the time of the most recent full backup.
Synthetic backups require less time to perform a backup, and system restore times
and costs are reduced.
What are virtual synthetic When to use virtual When not to use virtual
backups? synthetic backups. synthetic backups.
18 The virtual synthetic backup is timestamped as occurring one second after the
latest incremental. It does not include any changes to the backup selection since
the latest incremental.
19A client can use the synthesized backup to restore files and directories in the
same way that a client restores from a traditional backup.
21 The virtual synthetic full backup is a scalable solution for backing up remote
offices with manageable data volumes and low levels of daily change. If the clients
experience a high rate of change daily, the incremental or differential backups are
too large.
In this case, a virtual synthetic backup is no more helpful than a traditional full
backup. To ensure good restore performance, Dell Technologies recommends that
you create a traditional full backup every two months, presuming a normal weekly
full and daily incremental backup policy.
25 Synthetic backups can reduce the load on an application server and the data
traffic between an application server and a backup hosts. Synthetic backups can
reduce the traffic between the backup hosts and the PowerProtect DD appliance by
performing the Virtual Synthetic Backup assembly on the PowerProtect DD
appliance.
27 Such as databases
28The incremental forever or synthetic full backups need to ensure that the files
remain in the Active Tier if they will be used in virtual synthesis of new backups.
Using Fibre Channel (FC) instead of Ethernet as the transport is transparent to the
backup application. DD Boost over FC presents Logical storage units (LSUs) to the
backup application and removes several limitations inherent to tape and VTL. DD
Boost over FC permits concurrent read and write, which is not supported with
virtual tape. The backup image is the smallest unit of replication or expiration vs.
virtual tape cartridge, which results in efficient space management.
FC SAN
Managed File Replication
DD Boost DD Boost
WAN
DD Boost Library
Local Data Center Disaster Recovery Site
FC SAN
Backup Server
30
- A DD Boost library installed on backup hosts and DDOS perform path
management, load balancing, and failover.
Configuring DD Boost
DD Boost Configuration
For the backup host you will follow On each of the PowerProtect DD
these steps: appliances you will follow these
steps:
1. License the backup software for
DD Boost if required by the 1. License DD Boost31 on all
software manufacturer. PowerProtect DD appliances.
2. Create devices and pools 2. Enable DD Boost on all
through the management PowerProtect DD appliances.
console interface. 3. Define a local user as the DD
3. Configure backup policies and Boost User, and set a backup
groups to use the PowerProtect host as a client by hostname.
DD appliance for backups with 4. Create storage units as needed.
DD Boost.
5. Optionally, set any DD Boost
4. Configure clone or duplicate Options.
operations to use managed file
replication between As needed, storage units can be
PowerProtect DD appliances. renamed, deleted, and restored.
31If the managed file replication feature of DD Boost is used, a replication license is
required on all systems.
Open the following ports if you plan to use any of the related features
through a network firewall:
• UDP 2049 (enables NFS communication)
• TCP 2051 (enables file replication communication)
• TCP 111 (enables RPC portmapper services comms)
Enabling DD Boost
DD Boost
Library
Backup Host
DD Boost
Source
DD Boost
Destination
The DD Boost feature is built-into DDOS. Unlock the DD Boost feature on each
PowerProtect DD appliance with a license. If you are planning not to use Managed
File Replication, the destination PowerProtect DD appliance does not require a DD
Boost license.
For Dell EMC NetWorker, Dell EMC Avamar and some third-party backup
applications, the DD Boost library is already included. Some third-party backup
applications require a special plug-in that you must download and install on the
backup host before enabling DD Boost. The plug-in contains the appropriate DD
Boost library for use with compatible products. To verify compatibility with your
specific software, consult the E-Lab Navigator for PowerProtect DD products.
All PowerProtect DD systems running DD Boost must also enable NFS on their
systems before enabling DD Boost.
You can also enable DD Boost from the command line using the ddboost
enable command. You can use the ddboost status command to verify
whether DD Boost is enabled or disabled on your system.
Using the DD System Manager, you can add DD Boost clients and Users by going
to Protocols > DD Boost > Settings.
In the Allowed Clients area, click the plus button to enable access to a new client
using the DD Boost protocol on the system. Add the client name as a host name or
fully qualified domain name since IP addresses are not supported. An asterisk (*)
can be added to the Client field to enable access to all clients. You can also set the
Encryption Strength and Authentication Mode when setting up clients.
To add a DD Boost user for the system, click the plus button in the Users with DD
Boost Access section. In the Add User window, select from the list of existing
users, or add a new user.
Users and clients can also be added using the command line interface.
Consult the DDOS Command Reference Guide, available through the Dell EMC
Support portal, for more detailed information about using the ddboost commands
to administer DD Boost.
Create a storage unit by going to Protocols > DD Boost > Storage Units. To
open the Create Storage Unit dialog box, click the plus sign. Name the storage
unit, select a DD Boost user and optionally set quotas. Under the Storage Unit tab,
you can view information about a storage unit such as the file count, full path,
status, quotas, and capacity measurements.
Storage units can also be created using the command line interface.
Consult the DDOS Command Reference Guide, available through the Dell EMC
Support portal, for more detailed information about using the ddboost commands
to administer DD Boost.
To set various DD Boost options go to Protocols > DD Boost > Settings, click
More Tasks, and select Set Options. Other DD Boost options include DSP, Virtual
Synthetics, Low-Bandwidth Optimization, and File Replication Encryption.
You can also set DD Boost options from the command line interface.
Consult the DDOS Command Reference Guide, available through the Dell EMC
Support portal, for more detailed information about using the ddboost commands
to administer DD Boost.
You can rename, delete, and undelete storage units in the DD System Manager by
going to Protocols > DD Boost > Storage Units. To rename or modify a storage
unit, click the pencil icon. This opens the Modify Storage Unit dialog box enabling
you to change the name, the DD Boost User, and the quota settings.
You can delete one or more storage units by selecting them from the list and
clicking the red X icon. Any deleted storage units can be retrieved using the
Undelete Storage Unit item under the More Tasks button. Deleted storage units
can only be retrieved if file system cleaning has not taken place.
You can also rename, delete, and undelete storage units from the command line
interface.
Consult the DDOS Command Reference Guide, available through the Dell EMC
Support portal, for more detailed information about using the ddboost commands
to administer DD Boost.
DD Boost over Fibre Channel can be configured in the DD System Manager from
Protocols > DD Boost > Fibre Channel. Here you can enable DD Boost over
Fibre Channel, edit the server name, and add DD Boost Access Groups.
DD Boost access groups, called scsitarget groups in the CLI, identify initiators
and devices they can access. Initiators can read and write to devices in its access
group, but not to devices in other DD Boost access groups. Initiators can only
belong to one access group. Initiators assigned to DD Boost access groups cannot
be assigned to DD VTL access groups on the same appliance.
Using the DD System Manager you can review or create DD Boost access groups.
Review DD Boost
Access Groups by
following these steps:
1. To review the
configuration of the
DD Boost Access
Groups, select the
Hardware > Fibre
Channel > Access
Group tab.
2. A table appears
containing summary information about the DD Boost access groups and the
VTL access groups.
The information includes the name of the group, the type of service the group
supports, the endpoint associated with the group, the names of the initiators in
the group, and the number of devices (disks, changers, LUNs) in the group.
Note the groups that contain initiators and devices.
3. The DD Boost and VTL access groups are distinguished from one another by
the Service type.
4. The total number of groups that are configured on the system is shown at the
bottom of this section.
5. Select the View DD Boosts Groups hyperlink to go to the Protocol > DD
Boost page where there is more information and configuration tools.
6. Verify that the system went to the Protocols > DD Boost > Fibre Channel tab
in system manager.
7. Review the configuration of the DD Boost Access Groups.
Create a DD Boost
access group by
following these
steps:
1. Go to the
Protocols > DD
Boost page.
2. Select the Fibre
Channel tab.
3. To create a
group, click the
plus icon.
4. Enter the group name in the Group Name field of the Create Access Group
dialog box.
The group name can be up to 128 characters in length. The name must be
unique. Duplicate names are not permitted.
5. From the Initiator list, select the Initiators that you want to add to this access
group.
You may add your initiator later, as you are not required to add one now.
6. Select Next.
The Create Access Group > Devices dialog box now is displayed.
7. Enter the number of devices (the range is from 1 to 64).
8. Select which endpoints to include.
9. Click Next.
The Create Access Group > Summary dialog box now is displayed.
10. Review the contents of the dialog box.
11. Once you are satisfied, select Finish to create the DD Boost Access Group.
12. When the system indicates that the DD Boost Access Group creation process
has completed, click OK.
You can also configure and manage DD Boost over Fibre Channel from the
command line.
• ddboost option set fc {enabled | disabled} - Enable or disable
Fibre Channel for DD Boost. Role required: admin, limited-admin.
• ddboost fc dfc-server-name set <server-name> - DDBoost Fibre
Channel set Server Name. Role required: admin, limited-admin.
• ddboost fc dfc-server-name show - Show DDBoost Fibre Channel
Server Name. Role required: admin, limited-admin.
• ddboost fc group add <group-name> initiator <initiator-
spec> - Add initiators or DDBoost devices to a DDBoost FC group. Role
required: admin, limited-admin.
• ddboost fc group add <group-name> device-set - Add one or more
DD Boost devices to a DD Boost Fibre Channel group. Role required: admin,
limited-admin.
• ddboost fc group create <group-name> - Create a DDBoost FC group.
Role required: admin, limited-admin.
• ddboost fc group show list [<group-spec>] [initiator
<initiator-spec>] - List configured DDBoost FC groups. Role required:
admin, limited-admin.
• ddboost fc status - DDBoost Fibre Channel Status. Role required:
admin,limited-admin, security, user, backup-operator, none.
Consult the DDOS Command Reference Guide, available through the Dell EMC
Support portal, for more detailed information about using the ddboost commands
to administer DD Boost.
Backup Management
WAN
NetWorker Clients
Client Direct
DD Boost provides NetWorker with visibility into the properties of the PowerProtect
DD appliance, control of the backup images, and efficient wide area network
replication.
32A unique NetWorker volume label identifies each device and associates the
device with a pool.
• NetWorker uses the pools to direct the backups or clones of backups to specific
local or remote devices.
• NetWorker uses data protection policy resources33 to specify the backup and
cloning schedules for member clients.
The client direct feature34 enables clients that have a direct network connection or a
DD Boost over Fibre Channel (DFC) connection to the PowerProtect DD system to
send and receive data directly to Data Domain AFTD and DD Boost devices.
Dell Technologies recommends that you use the Device Configuration Wizard,
which is part of the NetWorker Administration GUI, to create and modify DD Boost
devices. The wizard can also create and modify volume labels and the storage
pools for DD Boost devices.
33 Dell Technologies recommends that you create policies that are dedicated solely
to DD Boost backups.
34Client Direct supports multiple concurrent backup and restore operations that
bypass the NetWorker storage node, which eliminates a potential bottleneck. The
storage node manages the devices that the clients use but does not handle the
backup data. The clients backup directly to the PowerProtect DD system and
deduplicate (DSP) directly from the client instead of going through the backup
server or storage nodes.
Data
WAN
Avamar Clients
Metadata
35 This approach enables users to deploy the optimal approach to deduplication for
different datatypes and manage the entire infrastructure from a single interface.
During a backup, the Avamar server sends a backup request to the Avamar client.
If the backup request includes the option to use a PowerProtect DD appliance as
the target, the Avamar client sends the backup data directly to the PowerProtect
DD appliance36. Metadata for the backup is sent from the Avamar client to the
Avamar server. The metadata enables Avamar to manage the backup even though
the data is stored on a PowerProtect DD appliance.
36 The backup data is not staged on the Avamar server before it is sent to the
PowerProtect DD appliance. The storage node manages the devices that the
clients use but does not handle the backup data. The clients backup directly to the
PowerProtect DD system and deduplicate (DSP) directly from the client instead of
going through the backup server or storage nodes.
PowerProtect PowerProtect
DD DD
Application Hosts
Application Agents
PowerProtect
Data Manager
Dell EMC PowerProtect Data Manager offers DBA self-service data protection and
recovery through Application Direct (formerly DD Boost for Enterprise Applications).
To verify compatibility with your specific software, consult the Dell EMC DD Boost
for Partner Integration Administration Guide available on the Dell EMC Support
site.
BoostFS
BoostFS
37By using DD Boost technology, BoostFS helps reduce bandwidth, can improve
backup times, offers load-balancing, in-flight encryption, and supports Secure Multi-
Tenancy.
38As a file server system implementation, the BoostFS workflow is similar to CIFS
or NFS but uses the DD Boost protocol. Also, BoostFS improves backup times
compared to CIFS, NFS, and various copy-based solutions.
BoostFS for Windows can be installed on Windows Server 2012, Windows Server
2012 R2, or Windows Server 2016, and supports several backup and enterprise
applications.
Install BoostFS for Windows by using the MSI installer that can be downloaded
from the Dell EMC Support site. Do not change the default settings. The MSI
installer includes several binary files and a device driver from EldoS Corporation.
BoostFS for Windows uses CBFS39. This functionality is similar to that of FUSE on
UNIX operating systems. To install BoostFS for Windows, you must install the
CBFS driver from EldoS Corporation40.
See the Dell EMC DD BoostFS for Windows Configuration Guide, available on the
Dell EMC Support site, for more information about installing and configuring
BoostFS for Windows.
39CBFS is a software interface from EldoS that enables file systems to exist in user
space and not only within a driver in kernel space.
40 If another program on the system previously installed the CBFS driver, the driver
that BoostFS installs is installed alongside it. The BoostFS CBFS driver does not
affect the operation of the other program.
BoostFS for Windows can be installed on several Linux distributions, and supports
several backup and enterprise applications.
There is a single RPM installation package for BoostFS for Linux that both
enterprise and small-scale users can download from the Dell EMC Support site. It
is available in both RPM and .deb formats. The RPM package includes the
BoostFS executable.
Before beginning the process, verify that the FUSE version on the client is 2.8 or
higher.
See the Dell EMC DD Boost BoostFS for Linux Configuration Guide, available on
the Dell EMC Support site, for more information about installing and configuring
BoostFS for Linux.
NetBackup Server
WAN or LAN
Media Server
Servers
Read/Write Server
DD Boost for NetBackup has two components. The DD Boost Library is embedded
in the OpenStorage plug-in that runs on the NetBackup Media servers. The DD
Boost server is built into DDOS and runs on the PowerProtect DD appliance.
With Veritas Backup Exec, the plug-in software must be installed on media servers
that access the PowerProtect DD appliance during backups. Backup Exec is not
supported for use with DD Boost over Fibre Channel.
See the Dell EMC DD Boost for OpenStorage Administration Guide, available on
the Dell EMC Support site, for more information about using DD Boost with Veritas
NetBackup and Backup Exec.
DD Boost works with many popular backup applications. Consult the DD Boost
Compatibility Guide, available on the Dell EMC Support site, for the latest
information about the backup applications that support DD Boost.
Many third-party backup applications do not natively support DD Boost, but require
the DD Boost plug-in to install the DD Boost library. Install the plug-in software on
each media server and configure the backup software as documented by the
manufacturer.
Before installing either the DD Boost plug-in or DDOS, consult the Dell
Technologies eLab Navigator. You can select from the various DD Boost guides to
learn which DD Boost client to download and use for your backup software version,
DDOS version, and client operating system version.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
DD VTL Overview
DD VTL Description
•
Tape Appliance
DD VTL Feature Library
1The PowerProtect DD Virtual Tape Library (DD VTL) feature provides a disk-
based backup system that emulates the use of physical tapes. This feature enables
backup applications to connect to and manage system storage using functionality
almost identical to a physical tape library.
− Manages replication6
3Once virtual drives are created, they appear to the backup software as SCSI tape
drives.
4The DD VTL feature provides a network interface to the file system. The VTL
protocol can be active along side CIFS, NFS and DD Boost, providing network
access to the file system.
5 PowerProtect DD appliances support backups over the SAN using Fibre Channel.
The backup application on the backup host manages all data movement to and
from the appliance. An FC switch is not needed when a direct connection from the
backup host to the appliance is used.
DD VTL Benefits
7Tapes can be locked using the DD Retention Lock feature to protect data from
modification.
8 DD VTL offers a simple integration, using existing backup policies. DD VTL can
use existing backup policies in a backup system using a strategy of physical tape
libraries.
10DD VTL eliminates the use of tape and the accompanying tape-related issues for
most restores. Compared to normal tape technology, DD VTL provides resilience in
storage through the benefits of Data Invulnerability Architecture (DIA).
DD VTL Terminology
Different tape library products package some components in different ways, and
the names of elements may differ, but the fundamental function is the same.
Slots
Barcode
Changer Cartridge
Access
Port (CAP) Library
Tape
Tape Drive
Tape
Tape Pool Devices Drives Vault
11PowerProtect DD appliances that are configured for VTL reduce storage space
requirements by using deduplication technology.
• Barcode13
• Tape14
• Pool15
• Tape Drive16
• Changer17
13A barcode is a unique ID for a virtual tape. Barcodes are assigned when the user
creates the virtual tape cartridge. A unique ID for a virtual tape that is assigned
when the user creates the virtual tape cartridge.
14 A tape is a cartridge holding magnetic tape that is used to store data long term.
The backup software creates virtual tapes which to act the same as physical tape
media. Tapes are represented in a system as grouped datafiles. Tapes can be
moved between a long-term retention vault to a library. They can also move within
a library across drives, slots, and CAPs. A tape is also called a cartridge.
16 A tape drive is the device that records backed-up data to a tape cartridge. In the
virtual tape world, this drive still uses the same Linear Tape-Open (LTO)
technology standards as physical tape drives. Depending on the multiplex setting of
the backup application, each drive operates as a device that can support one or
more data streams.
17A changer (Tape Backup Medium Changer) is the device that handles the tape
between a tape library and the tape drive. In the virtual tape world, the system
creates an emulation of a specific type of changer.
Although no tapes are physically moved, the virtual tape backup medium changer
must emulate the messages that your backup software expects when tapes are
moved. Selecting and using the incorrect changer model in your configuration
causes the system to send incorrect messages to the backup software. These
incorrect messages can cause the VTL system to fail.
18 A cartridge access port (CAP) enables the user to deposit and withdraw tape
cartridges (volumes) in an autochanger without opening its door. In a VTL, a CAP
is the emulated tape enter and eject point for moving tapes to or from a library. The
CAP is also called a mail slot.
19 A slot is a storage location within a library. For example, a tape library has one
slot for each tape that the library can hold.
20A library is a collection of magnetic tape cartridges that are used for long-term
data backup. A VTL emulates a physical tape library with tape drives, changer,
CAPs, and slots (cartridge slots). A library is also called an autoloader, tape silo,
tape mount, or tape jukebox.
21A tape vault is a holding place for tapes not in any library. Tapes in the vault
eventually have to be moved into the tape library before they can be used.
• Initiator22
• Access Group23
22An initiator is the device that starts a SCSI session and sends SCSI commands.
The initiator is usually a backup server. On the PowerProtect DD appliance, you
must identify the initiators that are permitted to control the system through SCSI
commands. The PowerProtect DD appliance needs the WWPN to determine which
Fibre Channel traffic is from an authorized initiator. When you identify the initiator,
you can also provide a name, or alias, that maps to the initiators WWPN. The name
makes it easier to manage the initiator through the DDOS user interface.
23 An access Group, or VTL Group, is a collection of initiators and the drives and
changers they can access. An access group may contain multiple initiators, but an
initiator can exist in only one access group.
VTL Planning
For further information about the definitions and capacities of specific systems,
consult the DDOS System Administration Guide and the VTL Best Practices Guide.
Both are available through the Dell EMC Support Portal.
24 See your backup host software support for correct sizing to fit your software.
DD VTL Capacity
Depending on your backup application, if you change the size after the initial
configuration, data that is written with the original size might become unreadable.
Multiplexing
Multiplexing is not
Client recommended
Client Server
VTL Enabled PowerProtect DD
Appliance
Client
Multiplexing was useful for clients with slow throughput since a single client could
not send data fast enough to keep the tape drive busy.
If you are using NetWorker with DD VTL, you should take the following steps to
mitigate any data compression loss:
• Set the NetWorker tape block size on the Media Server to 256 KB. This value is
safe for all operating systems and drivers.
• To avoid low deduplication rates due to multiplexing of multiple backup streams,
Dell Technologies recommends setting NetWorker device properties "target
sessions" and "maximum sessions" to 1. For further options on multiplexed
backups to DD VTL, see the NetWorker documentation.
FC Switch
Initiator
VTL 1
VTL 2
VTL Zone
Upgrade initiator HBA to the latest supported version of firmware and software.
Verify the speed of each FC port on the switch to confirm that the port is configured
for the required rate.
Consider spreading the backup load across multiple FC ports and switches to avoid
bottlenecks on a single port and provide increased resiliency.
If the VTL communication between the backup server and the PowerProtect DD
appliance is through NDMP, no FC interface card is required. However, you must
configure the tape server access group.
FC Switch
Initiator
VTL 1
VTL 2
VTL-Enabled PowerProtect DD
Appliance
VTL Zone
When you establish fabric zones through FC switches, the best way to avoid
problems with VTL configurations is to include only one initiator and one target port
in one zone.
Avoid having any other targets or initiators in any zones that contain a gateway
target FC port.
Only initiators that communicate with a particular set of VTL target ports should be
zoned with that PowerProtect DD appliance.
See the current DDOS Administration Guide, available from the Dell EMC Support
site, for details.
29An admin login is required to enable and configure VTL services, and perform
other configuration tasks. For basic tape operations a backup-operator login is
required. For basic monitoring a user login is required.
30DD VTL supports a maximum of 32,000 slots per library and 64,000 slots per DD
system. The system automatically adds slots to keep the number of slots equal to,
or greater than, the number of drives.
A preconfigured VTL access group32 lets you add devices that support NDMP-
based backup applications.
31An access group may contain multiple initiators, but an initiator can exist in only
one access group.
33A change may cause an active job to fail. The impact of changes during active
jobs depends on a combination of backup software and host configurations.
Tape Management
• When choosing a tape size34: All data segments identified as part of the VTL
tape are treated as a complete set of data. File
− Use larger tapes for large single system cleaning cannot run on a tape until all
datafiles35.
− Use smaller tapes for smaller datasets36.
• Target multiple drives to write multiple streams.
• Set retention periods to no more than are required.
34Larger capacity tapes pose a risk to system full conditions. It is more difficult to
expire and reclaim the space on data being held on a larger tape than on smaller
tapes. A larger tape can have more backups on it, making it potentially harder to
expire because it might contain a current backup.
35If the data you are backing up is large, you may want larger-sized tapes since
some backup applications are not able to span across multiple tapes.
36Using smaller tapes across many drives gives the system greater throughput by
using more data streams between the backup host and the PowerProtect DD
appliance.
37 All backups on a tape must be expired, by policy or manually, before the space in
the cartridge can be relabeled and made available for reuse. If backups with
different retention policies exist on a single piece of media, the youngest image
prevents file system cleaning and reuse of the tape. You can avoid this condition by
initially creating and using smaller tape cartridges.
38 Expired tapes are not deleted and the space that is used by that tape is not
reclaimed until it is relabeled, overwritten, or deleted. Consider a situation in which
30% of your data is being held on a 1TB tape. You could delete half of that data,
and still not be able to reclaim any of the space because the tape is still holding
unexpired data. Backing up smaller files to larger-sized tapes contributes to this
issue by taking longer to fill a cartridge with data. Using a larger number of smaller-
sized tapes can reduce the chances of a few young files preventing cleaning older
data on a larger tape.
39When deciding how many tapes to create for your VTL configuration, remember,
that creating more tapes than you need might cause the system to fill up
prematurely. Usually, backup software uses blank tapes before recycling tapes. It is
a good idea to start with a tape count less than twice the available space on the
PowerProtect DD appliance.
Barcode Definitions
A good practice is to use either two or three of the first characters as the identifier
of the group or pool in which the tapes belong. If you use two characters as the
identifier41, you can and then use four numbers in sequence to number up to
10,000 tapes. If you use three characters42, you can sequence only 1,000 tapes.
The barcode ends with a two-character tag for the supported tape types.
If you specify the tape capacity when you create a tape through
the PowerProtect DD System Manager, you override the two-
character tag capacity specification.
LTO-1 30 GiB LB
LTO-1 10 GiB LC
LTO-7 6 TiB L7
43For Tivoli Storage Manager (TSM), use the L2 tape code if the LA code is
ignored.
NDMP Support
VTL 1
Backup servers that are configured only with Ethernet can back up to a
PowerProtect DD VTL when used with an NDMP tape server44.
When a backup is initiated, the host tells the server to send its backup data45 to the
VTL tape server.
44 The backup host must be running NDMP client software to route the server data
to the related tape server on the PowerProtect DD appliance.
IBM i Support
IBM i virtual libraries are not managed any differently from other operating systems.
46 This license supports other VTL configurations as well, but the standard DD VTL
license does not directly support IBM i configurations. Add the i/OS license to the
PowerProtect DD appliance before creating a VTL to have the correct IBM i
configuration.
47 IBM uses LIC Program Temporary Fixes (PTFs) as the method of updating and
activating the drivers that are used. Usually, hardware configuration settings cannot
be manually configured, as only IBM, or equipment that emulates IBM equipment is
attached, requiring only fixed configuration settings.
48 The library configuration that is supported is an IBM TS3500 configured with IBM
LT0-3, LTO-4, or LTO-5 virtual tape drives. Virtual library management is done
from the Virtual Tape Libraries tab. From Virtual Tape Libraries > More Tasks >
Library > Create, you can set the number of virtual drives and the number of slots.
Fibre Channel devices can be connected directly to host (direct attach) through
arbitrated loop (FC-AL) topology or through a switched fabric (FC-SW) topology49.
See the Virtual Tape Library for IBM System i Integration Guide, available on the
Dell EMC Support page, for current configuration instructions when using VTL in an
IBM i environment.
49Direct Connect is not supported on Power5 hardware, Virtual I/O Server, and
5761/5704 IOAs. The Fibre Channel host bus adapters, or IOAs, can negotiate at
speeds of 2 Gbps to 16 Gbps in an FC-SW environment without any configuration
on the operating system. An IBM business partner installs Fibre Channel IOPs and
IOAs.
Configuring VTL
Creating a VTL
Provide
Slots quantity (1-
32,000
Provide
quantity (0-
Cartridge Access
100
Port (CAP)
Changer
Provide
model and
Identify model - Only quantity (64 -
one changer in VTL 1,080
Tape Drives
When you create the VTL, you can only have one changer, and you must identify
the model of the changer.
50 They are the changer, slots, cartridge access ports (CAPs), and tape drives.
The quantity and model of the tape drives53 must be provided in the VTL.
Even though the VTL uses the tapes, they are not an integral part of the VTL54.
A VTL can be created using the DD System Manager (DDSM) or the command-line
interface (CLI).
53The number of tape drives can range from 64 to up to 1,080 depending on the
PowerProtect DD model used.
With an admin or limited-admin role, you can create a VTL using the following
commands:
• vtl add vtl [model model] [slots num-slots] [caps num-caps]
- Add a tape library.
• vtl drive add vtl [count num-drives] [model model] - Add
drives to a VTL.
• vtl show config [vtl] - Show the library name and model and tape drive
model for a single VTL or all VTLs. This command is also available to users with
the security, user, backup-operator, and none roles, in addition to the admin
and limited-admin roles.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the commands listed on this page.
Click to enable
the DD VTL
service.
If the DD VTL
service is enabled,
click to disable the
service.
DD VTL controls the operation of the Virtual Tape Library. It must be licensed and
enabled to use DD VTL.
DD VTL provides the environment for virtual devices to exist. You may think of it as
a virtual data center.
VTL can also be enabled and disabled using the command-line interface.
With an admin or limited-admin role, you can enable and disable VTL using the
following commands:
• vtl enable - Enable the DD VTL subsystem. Before DD VTL can be enabled:
− You must have at least one Fibre Channel (FC) interface card that is
installed on your PowerProtect DD appliance. VTL communicates between a
backup server and a PowerProtect DD appliance through an FC interface.
− You must have previously enabled the file system and scsitarget features.
− You must have set the record (block) size for the backup software on the
application host; the minimum is 64 KiB or larger.
Changing the block size after the initial configuration may render unreadable
any data that was written in the original size.
• vtl disable - Close all libraries and shut down the DD VTL subsystem.
• vtl status - Show the status of DD VTL.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the commands listed here.
Managing a VTL
The DD VTL pane is subdivided into sections: DD Virtual Tape Libraries, Access
Groups, Resources, and Pools.
• The options under the DD Virtual Tape Libraries section enable you to
manage the VTLs and their associated devices.
• The options under the Access Groups section enable you to define the devices
that an individual initiator can access.
• The Resources section enables you to view the configuration of endpoints and
initiators. To configure these devices, you must go to the Hardware > Fibre
Channel menu.
• The Pools section displays information for the default pool and any other
existing pools.
The DD System Manager enables you to review the configuration of the VTL and
its components. The Protocols > DD VTL page provides details about the VTL
contents.
Select the DD Virtual Tape Libraries > VTL Service > Libraries menu item to
view summary information relating to all VTLs.
Select the DD Virtual Tape Libraries > VTL Service > Libraries > {library-name}
menu item to view summary information about the selected VTL55.
55The number and disposition of tapes in the VTL is also shown. If no tapes are
associated with the VTL, there is nothing in the Tapes section.
Selecting the Drives item in a VTL provides detailed related information for all
drives57.
56 Including the vendor, product ID, revision number, and serial number of the
changer. These are all attributes that you would expect to find with a physical tape
drive.
57Including the drive number, vendor, product ID, revision number, serial number,
and status. If a tape is in the drive, the barcode is displayed along with the name of
the tape pool to which the tape belongs.
Create a VTL access group in the DD System Manager, by following these steps:
1. Select Access Groups > Groups.
2. Select More Tasks > Group > Create.
3. In the Create Access Group dialog, enter a name, from 1 to 128 characters,
and select Next.
4. Add devices, and select Next.
5. Review the summary, and select Finish or Back, as appropriate.
1. Select the Hardware > Fibre Channel > Access Groups tab.
2. The Access Groups tab contains summary information about any DD Boost
Access Groups and VTL access groups. The information includes the name of
the group, the type of service, the endpoint associated with the group, the
names of the initiators in the group, and the number of devices in the group.
Note the groups that contain initiators and devices.
3. The total number of groups that are configured on the system is shown at the
bottom of this section.
4. Select the View DD VTL Groups hyperlink to go to the DD System Manager
Protocol > DD VTL page where there is more information and configuration
tools.
1. You can select the View VTL Groups hyperlink on the Hardware > Fibre
Channel > Access Groups tab. You can also go to Protocols > DD VTL page
directly.
2. Select the Access Group menu item. To expand the list, click the plus sign (+)
and select an access group from the Access Groups list.
3. Select the LUNs tab.
4. Review a summary of the various LUNs in the selected access group.
1. You can select the View DD VTL Groups hyperlink on the Hardware > Fibre
Channel > Access Groups tab. Or you can go to Protocols > DD VTL page
directly.
2. Select the Access Group menu item. To expand the list, click the plus sign (+)
next to the Groups item.
3. Select an access group from the Groups list.
4. Select the Initiators tab.
5. Review a summary of any initiators in the selected access group.
To delete a VTL Access Group, you must first ensure that the access group is
empty and contains no initiators or devices. Use the configure (modify) process to
delete these objects from an access group.
1. Select Protocols > VTL > Access Groups > Groups > group.
2. Select More Tasks > Group > Configure.
3. In the Modify Access Group dialog, enter or modify the Group Name.
4. To configure initiators to the access group, check the box next to the initiator.
You can add initiators to the group later.
5. Select Next.
6. Select a device, and select the edit (pencil) icon to display the Modify Devices
dialog. Then, follow steps a-e. If you simply want to
delete the device, select the delete (X) icon, and skip to step e.
a. Verify that the correct library is selected in the Library drop-down list, or
select another library.
b. In the Devices to Modify area, select the checkboxes of the devices
(Changer and drives) to be modified.
c. Optionally, modify the starting LUN (logical unit number) in the LUN Start
Address box.
This is the LUN that the PowerProtect DD appliance returns to the initiator.
Each device is uniquely identified by the library and the device name. (For
example, it is possible to have drive 1 in Library 1 and drive 1 in Library 2).
Therefore, a LUN is associated with a device, which is identified by its library
and device name.
The initiators in the access group interact with the LUN devices that are
added to the group.
The maximum LUN accepted when creating an access group is 16,383.
A LUN can be used only once for an individual group. The same LUN can be
used with multiple groups.
Some initiators (clients) have specific rules for target LUN numbering; for
example, requiring LUN 0 or requiring contiguous LUNs. If these rules are
not followed, an initiator may not be able to access some or all of the LUNs
assigned to a DD VTL target port.
Check your initiator documentation for special rules, and if necessary, alter
the device LUNs on the DD VTL target port to follow the rules. For example,
if an initiator requires LUN 0 to be assigned on the DD VTL target port,
check the LUNs for devices assigned to ports, and if there is no device
assigned to LUN 0, change the LUN of a device so it is assigned to LUN 0.
d. In the Primary and Secondary Ports area, change the option that determines
the ports from which the selected device is seen. The following conditions
apply for designated ports:
i. all – The checked device is seen from all ports.
ii. none – The checked device is not seen from any port.
iii. select – The checked device is seen from selected ports. Select the
checkboxes of the ports from which it will be seen.
If only primary ports are selected, the checked device is visible only from
primary ports.
If only secondary ports are selected, the checked device is visible only
from secondary ports. Secondary ports can be used ifprimary ports
become unavailable.
The switchover to a secondary port is not an automatic operation. You must
manually switch the DD VTL device to the secondary ports if the primary
ports become unavailable.
The port list is a list of physical port numbers. A port number denotes the
PCI slot, and a letter denotes the port on a PCI card. Examples are 1a, 1b,
or 2a, 2b.
A drive appears with the same LUN on all ports that you have configured.
e. Select OK.
The PowerProtect DD system provides the tools that you would expect to manage
tapes. They include the ability to create and delete tapes. The VTL service also
provides the ability to import and export tapes from and to the vault. If needed, you
can move tapes within the VTL between the slots, drives, and CAPs. You can
search for specific tapes using various criteria, such as location, pool, or barcode to
search for a tape.
Tape Management
• Create
• Delete
• Import
• Export
Tapes
• Move
• Search
• Review
Create Tapes
You can also create tapes using the command-line interface (CLI).
With an admin or limited-admin role, you can create tapes using the following
command:
• vtl tape add barcode [capacity capacity] [count count]
[pool <pool>] - Add one or more virtual tapes and insert them into the vault.
Optionally, add the tapes to the specified pool.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters for the vtl tape add command.
Delete Tapes
You can delete tapes from either a library or a pool. If initiated from a library, the
system first exports the tapes, then deletes them. The tapes must be in the vault,
not in a library. On a Replication destination system, deleting a tape is not
permitted.
1. Select Virtual Tape Libraries > DD VTL Service > Libraries > library or
Vault.
2. Select More Tasks > Tapes > Delete.
3. In the Delete Tapes dialog, enter search information about the tapes to delete,
and select Search.
4. Select the checkbox of the tape that should be deleted or the checkbox on the
heading column to delete all tapes, and select Next.
5. Select Submit in the confirmation window, and select Close.
After a tape is removed, the disk space that is used for the tape is
not reclaimed until after a file system cleaning operation.
You can also delete tapes using the command line interface.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl tape del command.
Import Tapes
When tapes are created, they can be added directly to a VTL or to the vault. From
the vault, tapes can be imported, exported, moved, searched, and removed.
Importing moves existing tapes from the vault to a library slot, drive, or CAP. The
number empty slots in the library limit the number of tapes you can import at one
time.
With an admin or limited-admin role, you can import tapes using the following
command:
• vtl import vtl barcode barcode [count count] [pool pool]
[element {drive | cap | slot}] [address addr] - This command is
used to move tapes from the vault into a slot, drive, or CAP.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl import command.
Export Tapes
Exporting a tape removes that tape from a slot, drive, or cartridge-access port
(CAP) and sends it to the vault.
a. Select Virtual Tape Libraries > DD VTL Service > Libraries > library.
Then, select More Tasks > Tapes > Export. In the Export Tapes dialog,
enter search information about the tapes to export, and select Search.
b. Select Virtual Tape Libraries > VTL Service > Libraries > library >
Changer > Drives > drive > Tapes. Select tapes to export by selecting
the checkbox next to:
• An individual tape, or
• The Barcode column to select all tapes on the current page, or
• The Select all pages checkbox to select all tapes returned by the search
query.
Only tapes with a library name in the Location column can be exported.
Select Next.
2. Select Submit.
3. Select Close in the status window.
You can also export tapes using the command line interface.
With an admin or limited-admin role, you can also export tapes using the following
command:
• vtl export vtl {slot | drive | cap} address [count count] -
Remove tapes from a slot, drive, or cartridge-access port (CAP) and send them
to the vault.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl export command.
Tapes can be moved between physical devices within a library to mimic backup
software procedures for physical tape libraries (which move a tape in a library from
a slot to a drive, a slot to a CAP, a CAP to a drive, and the reverse). In a physical
tape library, backup software never moves a tape outside the library.
1. Select Virtual Tape Libraries > DD VTL Service > Libraries > library.
When started from a library, the Tapes panel allows tapes to be moved only
between devices.
2. Select More Tasks > Tapes > Move.
3. In the Move Tape dialog, enter search information about the tapes to move,
and select Search.
4. From the search results list, select the tape or tapes to move.
5. Do one of the following:
a. Select the device from the Device list (for example, a slot, drive, or CAP),
and enter a beginning address using sequential numbers for the second and
subsequent tapes. For each tape to be moved, if the specified address is
occupied, the next available address is used.
b. Leave the address blank if the tape in a drive originally came from a slot and
is to be returned to that slot; or if the tape is to be moved to the next
available slot.
6. Select Next.
7. In the Move Tape dialog, verify the summary information and the tape listing,
and select Submit.
8. Select Close in the status window.
59Select the name of the pool in which to search for the tape. If no pools have been
created, use the Default pool.
• Barcode60
• Count61
5. Select Search.
60 Specify a unique barcode, or leave the default '*' to return a group of tapes.
Barcode allows the wildcards '?' and '*', where '?' matches any single character and
'*' matches zero or more characters.
61 Enter the maximum number of tapes you want to be returned to you. If you leave
this blank, the barcode default '*' is used.
Review Tapes
Select the Tape menu item associated with the VTL to review the tapes that are
assigned to it. The tapes are in a slot, drive, or CAP.
You can also review tapes using the command line interface.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl tape show command.
To create a tape pool using the DD System Manager, follow this process.
1. Go to Data Management > DD VTL, and expand the Pools menu on the left
side of the screen.
2. Select the Pools menu item from the list.
3. Now, select More Tasks > Pool > Create to open the Create Pool dialog box.
4. Provide a name for the Pool. Use a name that identifies the type of data that is
on the tape. For example, you could name the pool EngBkupPool to signify that
it contains tapes relevant to engineering backups.
5. Click the backwards compatibility check box to create the older-style tape
pool under /data/col1/backup. If you do not check this box, the system
creates a newer style tape pool that uses the MTree structure.
6. Select OK when you are ready to create the tape pool.
Tape pools can also be imported using the command-line interface (CLI).
With an admin or limited-admin role, you can create tape pools using the following
command:
• vtl pool add pool - Create a VTL pool.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl pool add command.
Tape pools can also be deleted using the command-line interface (CLI).
You can also delete tape pools using the following command:
• vtl pool del pool - Delete a VTL pool. You must run vtl tape del to
remove all tapes from a pool, or use vtl tape move to move all tapes to
another pool.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl pool del command.
Tape pools can also be renamed using the command-line interface (CLI).
You can also rename tape pools using the following command:
• vtl pool rename src-pool dst-pool - Rename a VTL pool. A pool can
be renamed only if none of its tapes is in a library.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
support site, for specific parameters for the vtl pool rename command.
When you create a tape pool, either an MTree is created under /data/col1 or a
directory is created under /data/col1/backup.
You can examine the list of MTrees on the system to view the MTrees associated
with VTL.
When you enable VTL, the Default MTree-based tape pool is created.
NDMP
VTL 1
• NDMP-enabled software must be installed on the client system for access to the
VTL.
• NDMP clients must log in to the PowerProtect DD appliance using a standard
DDOS user account64 or an NDMP user account65.
• To make DD VTL devices accessible to the NDMP clients, the devices must be
members of the TapeServer access group.
− Only devices in the TapeServer access group are available through NDMP.
− Devices in the TapeServer access group cannot be in other VTL access
groups.
− Initiators cannot be added to the TapeServer access group.
For more information about NDMP, see http://ndmp.org.
64If a standard DDOS user account is employed, the password is sent over the
network as plain text.
65The NDMP feature on the appliance enables you to add a user for NDMP
access. Password encryption can be added to the NDMP user for added security.
• Set the ndmpd service authentication to MD5 using the ndmpd option set
authentication md5 command.
• Verify that the service authentication was correctly set using the ndmpd
option show all command.
See the Dell EMC DDOS Command Reference Guide, available on the Dell EMC
Support site, for specific parameters for the commands listed on this page.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
Appendix ................................................................................................. 33
Dell EMC Cloud Tier enables the movement of data from the active tier of a
PowerProtect DD appliance to low-cost, high-capacity object storage in the public,
private, or hybrid cloud. Data is moved to the cloud for long-term data retention.
Only unique, deduplicated data1 is sent from the PowerProtect DD appliance to the
cloud or retrieved from the cloud.
Backup Data
Cloud storage in the public, private,
Cloud Tier Architecture
or hybrid cloud for long-term data
retention.
Cloud Tier
Cloud Tier
Cloud Unit 1
Considerations
Cloud Unit 2
1Sending only deduplicated data ensures that the data being sent to the cloud
occupies as little space as possible.
Model Sizing
Here the supported physical memory and storage requirements for each
PowerProtect DD model.
DD3300 48 16
(8 TB
Capacity)
DD3300 48 32
(16 TB
Capacity)
DD3300 64 64
(32 TB
Capacity)
DDVE* 60 128
(64 TB
Capacity)
DDVE* 80 192
(96 TB
Capacity)
* Dell EMC Cloud Tier is supported on DDVE for on-premises implementations only.
2The minimum metadata size is a hard limit. Dell Technologies recommends that
you start with 1 TB for metadata storage and expand in 1 TB increments. The
DDVE Installation and Administration Guide provides more details about using
Cloud Tier with DDVE.
Active Tier
Data Movement
Policy Cloud Tier
Cloud Unit 1
The Dell EMC Cloud Tier is managed through a single namespace. There is no
separate cloud gateway or virtual appliance required. The native PowerProtect DD
policy management framework supports the data movement.
Cloud storage supports Dell EMC Elastic Cloud Storage (ECS), Alibaba, Amazon
Web Services S3, Google Cloud Provider, S3 Flexible provider cloud unit, and
Microsoft Azure. Extra storage is required to hold metadata associated with the
data in the cloud tier. Deduplication, cleaning, and replication operations use
metadata.
Extra metadata storage is required to support the cloud tier. The amount of
required metadata storage is based on the PowerProtect DD model.
Active Tier
Data Movement
Policy Cloud Tier
Cloud Unit 1
Cloud Unit 2
Dell EMC Cloud Tier supports one or two cloud units on each PowerProtect DD
appliance.
• Each cloud unit has the maximum capacity of the active tier3.
• Each cloud unit maps to a cloud provider4.
• Metadata shelves5 store metadata for both cloud units.
This example shows a system with an active tier and two cloud units. Each cloud
unit has a capacity equal to that of the active tier. Data that is stored on the active
tier provides local access to data and can be used for operational recoveries. The
cloud tier provides long-term retention for data that is stored in the cloud.
3You can scale the cloud tier to maximum capacity without scaling the active tier
any larger.
5The number of metadata shelves you need depends on the cloud unit physical
capacity.
The NFS, CIFS, and DD Boost protocols are supported for data movement to and
from the cloud tier.
PowerProtect DD VTL Tape Out to Cloud is supported with DDOS version 6.1 and
later. DD VTL Tape Out to Cloud supports storing the VTL vault on Cloud Tier
storage.
There is no support for vDisk pools as used with Dell EMC ProtectPoint.
PowerProtect DD Appliance
Cloud Tier
Cloud units each have their own
deduplication pools.
Cloud Unit 1
• Each cloud unit has its own segment index and metadata and thus each cloud
is a deduplication unit by itself6.
• The cloud tier uses the same compression algorithm7 as the active tier.
• Cloud deduplication does not do the packing phase.
• Cloud tier cleaning can be schedule-based or on demand8.
• The schedule for cloud tier cleaning is set relative to active tier cleaning9.
8 Cleaning of the active tier and the cloud tier cannot take place simultaneously.
9 The schedule specifies to run cloud tier cleaning after every Nth run of active tier
cleaning. By default, cloud tier cleaning runs after every 4th scheduled active tier
cleaning.
10 On-demand cleaning can be run from either the DD System Manager or CLI.
11 When all segments within a region are dead, the entire object is deleted.
12 The cloud storage is accessed to delete objects in the cloud with no live data and
to perform some copy forward of container metadata-related activities.
Secure HTTP (HTTPS) is used for the transfer of data between a PowerProtect
DD appliance and the cloud.
Active tier encryption is not required to enable encryption on the cloud tier.
13You are prompted for the security officer username and password to enable
encryption.
14Encryption of the active tier is only applicable if encryption is enabled for the
system.
Replication
You can enable Dell EMC Cloud Tier on one or both systems in a replication pair.
If the source system is Cloud Tier-enabled, data may be read from the cloud if the
file was already migrated to the cloud tier from the active tier. A replicated file is
always placed first in the active tier on the destination system even when Cloud
Tier is enabled.
17
Before sending any data to the cloud the decision to encrypt data or not must be
made.
It is possible to migrate the system data from and older appliance that is configured
with Dell EMC Cloud Tier to a newer appliance. Migrating to a newer appliance can
improve performance, add additional capacity, and provide access to new features.
The migration process migrates the active tier storage, and the locally stored cloud
tier metadata from the existing system to a new system. During the migration, the
source system operates in a restricted mode.
The procedure to initiate the Cloud Tier migration is only available through the CLI.
See the Dell EMC DDOS Administration Guide, available on the Dell EMC Support
site for more information about migrating Cloud Tier.
Configure Storage
With Dell EMC Cloud Tier storage, the PowerProtect DD appliance holds the
metadata for the files residing in the cloud18.
The cloud tier requires a local store for a local copy of the cloud metadata. To
configure Cloud Tier, you must meet the storage requirement for the licensed
capacity.
If creating a file system, the cloud tier can be enabled at the time that the new file
system is created. To create a file system, select Create File System and then
configure the active tier of the system.
In Data Management > File System, the main panel displays statistics for the
active and cloud tiers.
The statistics viewable in the DD System Manager for both the active and cloud tier
are:
• Size
• Used
• Available
• Pre-Compression
• Total Compression Factor (Reduction %)
• Cleanable
• Space Usage
To provide more information to the user, the DD System Manager displays the
reasons why the cloud storage is in error state.
19You must have Port 443 or Port 80 open to the cloud provider networks for both
endpoint IPs and provider authentication IP for bi-directional traffic. Remote cloud
provider destination IP and access authentication IP address ranges must be
enabled through the firewall.
20 Downloaded certificate files have a .crt extension. Use OpenSSL to convert the
file from .crt format to .pem. For additional information, see that the Dell EMC
DDOS System Administration Guide on the Dell EMC support site.
The links on
this page
contain
configuration
information
Alibaba Cloud Amazon Web Services Flexible Cloud
and the
S3 Tier Provider
procedure to
Framework for
create cloud
S3
units on
supported
cloud
platforms.
Overview
All interactions with cloud providers are authenticated with a signature protocol.
Support for S3 flexible cloud providers that support S3 authentication with signature
V4 is now part of DDOS.
A new field S3 Signature Version is added to display the cloud profile version.
In the output of cloud profile show, DDOS displays two possible values: s3v2
or s3v4.
Once set, the signature version of the cloud profile cannot be modified.
Movie:
Data Movement
21Used for all files older than a set number of days. For example, all files older than
90 days.
22All files older than X days, but younger than Y days. For example, all files older
than 30 days but younger than 365 days.
Agent
Recall is the act of bringing data from the cloud to the active tier. Restore is the act
of recovering data from the active tier and making it available to the client.
Data can be recalled from the cloud tier using the DD System Manager (DDSM) or
the CLI.
Tape Out to cloud storage offers the ability to store offsite and retrieve tapes for
long-term retention (LTR) use cases.
Movie:
Architecture
Metadata
Data
Active Unit Cloud Unit
Active CP Cloud CP
(metadata)
Index, container metadata,
directory manager
Metadata to support the cloud is maintained in the cloud tier shelf of the local
storage. This metadata is used in operations such as deduplication, cleaning, and
replication. Using local storage for metadata minimizes writes to the cloud. The
metadata includes the index, the Directory Manager (DM) for managing the
namespace and container metadata. Some metadata, including container
metadata, is also stored with the data in the cloud for disaster recovery purposes.
Benefits
Cloud Tier provides a scalable
solution for long-term data
storage. With Cloud Tier, users
can store up to two times the
maximum active tier capacity in
the cloud for long-term
retention of data. With cloud
tiering policies, data is in the
right place at the right time.
Data is scheduled to be moved
to the cloud using policies
based on the age of the data.
Considerations
Here are a few considerations when deciding to implement Cloud Tier:
• A cloud capacity license is required for Cloud Tier. Use the Dell EMC Electronic
License Management System (ELMS) file to apply the license.
• The Cloud Tier feature may consume all available bandwidth in a shared WAN
link, especially in a low-bandwidth configuration (1 Gbps). The Cloud Tier
feature may impact other applications sharing the WAN link.
• On systems with a dedicated management interface, reserve that interface for
system management traffic (using protocols such as HTTP and SSH). Backup
and cloud tier data traffic should be directed to other interfaces, such as eth1a.
Prerequisites
Complete the following tasks on the new system before beginning the migration
operation:
1. Verify both the source and destination systems are running DDOS 7.3.0.5 or
higher. Cloud Tier migration is not supported on DDVE instances.
2. Add a Cloud Tier license on the new system.
3. Add other feature licenses as required on the new system.
4. If a passphrase is configured on the existing system, set the same passphrase
on the new system. The passphrase store-on-disk setting should not be less
secure on the destination than on the source.
5. If encryption is configured on the existing system, set the same encryption
values including key manager settings and FIPS compliance on the new
system.
6. If automatic key rotation is configured on the existing system, disable it before
starting the migration. Reenable it on the new system after the migration.
7. If encryption is configured on the existing system, back up the key export files
from the existing system.
8. If Retention Lock Compliance is enabled on the existing system, enable RLC on
the new system.
9. Record the cloud profile and cloud unit information from the existing system.
10. Create the file system on the new system, but do not enable it.
Restricted Mode
While the PowerProtect DD appliance is in restricted mode, the active tier storage
is available for backup operations, but I/O on the cloud tier storage is not permitted.
The following operations are not permitted while the migration is in progress:
• Sending active tier data to cloud tier storage.
• Recalling data from cloud tier storage.
• Cleaning the cloud tier storage.
• Restoring files directly or reading from the cloud tier storage.
• File system cleaning on the source system.
• System sanitization cannot be performed on the source system.
• Enabling or disabling file system encryption.
• Enabling, disabling, or setting the embedded key manager or an external key
manager.
• Creating, destroying, deleting, or syncing keys from the embedded key manager
or an external key manager.
24For AWS and Azure cloud providers, download the Baltimore CyberTrust root
certificate.
Adding a Certificate
After downloading a certificate file, add the CA Certificate:
1. Go to Data Management > File System > Cloud Units.
2. Click Manage Certificates from the tool bar.
3. Click Add, and select one of the options from the Add CA Certificate for Cloud
screen.
4. Click Add.
Configuration
Regions are configured at the bucket level instead of the object level. All objects
that are contained in a bucket are stored in the same region. A region is specified
when a bucket is created, and cannot be changed once it is created.
The Alibaba Cloud user credentials must have permissions to create and delete
buckets and to add, modify, and delete files within the buckets they create.
Procedure
Configuration
AWS offers a range of storage classes. The Cloud Providers Compatibility Matrix,
available from https://elabnavigator.emc.com/eln/elnhome provides up-to-date
information about the supported storage classes.
For enhanced security, the Cloud Tier feature uses Signature Version 4 for all AWS
requests. Signature Version 4 signing is enabled by default.
The AWS user credentials must have permissions to create and delete buckets and
to add, modify, and delete files within the buckets they create.
Procedure
Configuration
The Cloud Tier feature supports qualified S3 cloud providers under an S3 Flexible
provider configuration option.
Procedure
Configuration
The Google Cloud Provider user credentials must have permissions to create and
delete buckets and to add, modify, and delete files within the buckets they create.
Procedure
Configuration
Microsoft Azure offers a range of storage account types. The Cloud Providers
Compatibility Matrix, available from
http://compatibilityguide.emc.com:8080/CompGuideApp/ provides up-to-date
information about the supported storage classes.
Procedure
The schedule can be viewed at Data Management > File System > Summary.
The data movement schedule is set at Data Management > File System > Cloud
Units > Settings > Data Movement.
If a cloud unit is inaccessible when cloud tier data movement runs, the cloud unit is
skipped in that run. Data movement on that cloud unit occurs in the next run if the
cloud unit becomes available. The data movement schedule determines the
duration between two runs. If the cloud unit becomes available and you cannot wait
for the next scheduled run, you can start the data movement manually.
For nonintegrated backup applications, you must recall the data to the active tier
before you can restore it. Backup administrators must trigger a recall or backup
applications must perform a recall before cloud-based backups can be restored.
Once a file is recalled, aging is reset and starts again from 0, and the file is eligible
based on the age policy set. A file can be recalled on the source MTree only.
Integrated applications can recall a file directly.
Recall fails if there is no space in the active tier to move the file. This decision is
made before any movement is started. Recall is per file. Dell EMC Cloud Tier
checks for existing data segments on the active tier. Only segments not present in
the active tier are invoked for recall from the cloud.
Select Data Management > File System > Summary. In the Cloud Tier section of
the Space Usage panel, click Recall, or expand the File System status panel at
the bottom of the screen. Click Recall.
The Recall link is available only if a cloud unit is created and has
data. The Recall File from Cloud dialog is displayed.
In the Recall File from Cloud dialog, enter the exact file name (no wildcards) and
full path of the file, for example: /data/col1/mt11/ file1.txt. Click Recall to
start the recall process.
Only four recall jobs are active at any given time. uUp to 1,000 recall jobs can be
queued up to run automatically as previous jobs complete. The recall queue is
automatically regenerated, so if the system is restarted during a recall the recall
continues when the system is back up.
Once the file has been recalled to the active tier, you can restore the data.
The path-name can be a file or directory; if it is a directory, all files in the directory
are listed.
Monitor the status of the recall using the data-movement status [path
{pathname | all | [queued] [running] [completed] [failed]} |
to-tier cloud | all}] command.
If the status shows that the recall is not running for a given path, the recall may
have finished, or it may have failed.
Verify the location of the file using the filesys report generate file-
location [path {<path-name> | all}] [output-file <filename>]
command.
Once the file has been recalled to the active tier, you can restore the data.
Requirements
The Dell EMC Cloud Tier feature must be licensed and enabled on either a physical
or virtual PowerProtect DD appliance. A cloud profile and cloud unit name should
be configured before using the DD VTL Tape Out to Cloud feature.
Both DD VTL and Cloud Tier Capacity licenses are required to use the DD VTL
Tape Out to Cloud feature.
The workflow for backing up and restoring data using the PowerProtect DD VTL
Tape Out to Cloud feature is as follows:
1. Perform the backup server or client configuration and user application setup.
2. Back up to primary disk storage pools
3. During backup, the data is copied while the backup server maintains the
necessary backup catalog and tracking metadata.
4. Data replicates to the DD VTL vault.
5. This replication can be onsite or geographically separated sites. The backup
server tracks the tapes in a “mountable” state.
6. Once the tapes are ready for long-term retention, they are ejected from the tape
storage pool.
7. The backup server tracks tapes in the “nonmountable” state.
8. The backup server continues to monitor the tape while the Long-Term Retention
to Cloud functionality moves the tapes to the cloud tier.
9. Once in the cloud tier vault, the backup server maintains the tape status to be
“Offsite.”
10. Restore process: The PowerProtect DD appliance recalls the tapes from the
cloud tier vault and places them in the DD VTL vault. Once the tapes are in the
vault, they can be moved to the library where the backup application can use
them.
You can manage a DD VTL using the DD System Manager (DDSM) or the
command-line interface (CLI).
End-to-End Workflow
The DD VTL Tape Out to Cloud feature uses these components in the
PowerProtect DD appliance. The user interacts with the system using the DDSM or
CLI. The DD VTL service uses the Tape Out to Cloud functionality built on the DD
file system Long-Term Retention service.
The DD file system uses NFS v3 APIs to access the DD VTL tape pool and send
the virtual tapes in the vault to the cloud tier.
The Tape selection policy is applied at the pool level and sets the age threshold for
data moving to the cloud. The minimum setting is 14 days. If the policy is set to
user-managed, the user uses a command to select one or more tapes to move at
the next scheduled data movement. If the setting is set to none, no tapes are
moved to the cloud.
The cloud data movement schedule defines how frequently vaulted tapes are
moved to the cloud. The cloud data movement schedule can be set to never, to any
number of days/weeks, or run manually.
You can find specific commands that are used to set the tape selection policy, and
cloud data movement schedule in the DDOS Command Reference Guide on the
Dell EMC Support site.
Data movement for VTL occurs at the tape volume level. Individual tape volumes or
collections of tape volumes can be moved to the cloud tier but only from the vault
location. Tapes in other elements of a VTL cannot be moved.
Use the backup application verify the tape volumes that will move to the cloud are
marked and inventoried according to the backup application requirements.
Manually select tapes for migration to the cloud tier (immediately or at the next
scheduled data migration), or manually remove tapes from the migration schedule.
After the next scheduled data migration, the tapes are recalled from the cloud unit
to the vault. From the vault, the tapes can be returned to a library.
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
DD Encryption .......................................................................................................... 16
Encryption at Rest.............................................................................................................. 17
Key Management ............................................................................................................... 19
Inline Encryption ................................................................................................................ 20
Authorization Workflow ...................................................................................................... 22
Configuring Encryption ....................................................................................................... 23
File System Locking ........................................................................................................... 25
Appendix ................................................................................................. 29
Retention Lock
1For files committed to be retained, DD Retention Lock works with the retention
policy set by the application to prevent locked files from being modified, or deleted
during the retention period. The retention period can be set for up to 70 years.
2 DD Retention Lock protects against data management accidents, user errors, and
any malicious activity that might compromise the integrity of the retained data. The
retention period of a retention-locked file can be extended, but not reduced.
4 DD Retention Lock Governance edition maintains the integrity of the archive data.
The DD Retention Lock Governance Edition does not require a security officer and
provides a higher degree of flexibility for archive data retention.
Commission.
A user assigned the security privilege is called a security officer. The security
officer can establish or modify runtime authorization policy. To do this, the security
officer applies authorization CLI commands.
Updating or extending retention periods and renaming MTrees, requires the use of
the runtime authorization policy7.
When enabled, runtime authorization policy is invoked on the system for the length
of time the security officer is logged in to the current session.
The security officer is the only user that is permitted to change the
security officer password. Contact Dell Technologies Support if the
password is lost or forgotten.
To perform retention locking on a file, change the last access time9 (atime) of the
file to the desired retention time10 of the file, that is, the time when the file can be
deleted.
The future atime you specify must respect the minimum and maximum retention
periods of the file’s MTree, as offsets from the current time, as shown in the
diagram.
You cannot modify locked files on the PowerProtect DD system even after the
retention period for the file expires. You can copy files to another system and then
modify them. Data that you archive and retain on the PowerProtect DD system
after the retention period expires remains on the system. You can delete the
remaining files using an archiving application, or remove them manually.
9The archiving application must set the atime value, and DD Retention Lock must
enforce it, to avoid any modification or deletion of locked files.
10This action is usually performed using the archive application, and all the archive
applications that are qualified on the protection system today, per the DD Security
Configuration Guide. Follow the basic locking protocol outlined here.
You can configure DD Retention Lock Governance using the DD System Manager
(DDSM) or by using CLI commands. DDSM provides the capability to modify the
minimum and maximum retention period for selected MTrees.
To configure retention lock using the DDSM, navigate to Data Management >
MTree, then:
1. Select the MTree you want to edit with DD Retention Lock.
2. Click the Summary tab, and scroll to the Retention Lock area
3. Click Edit.
4. Enable retention lock in the Modify DD Retention Lock dialog box.
5. Enter the retention period, or select Default. You can also place an indefinite
retention hold on the selected MTree from the selected MTree. Indefinite
retention hold can be set as long as Retention Lock is enabled.
6. Click OK.
• Disabling various avenues of access where locked data or the state of retention
attributes might be compormised.
You configure and enable the system to use DD Retention Lock Compliance
software, and then enable DD Retention Lock Compliance on one or more MTrees.
Data Sanitization
Normal file deletion leaves behind residual data that makes it possible to recover
the data. Sanitization removes any trace of deleted files with no residual remains.
Note: Sanitization is not supported when used with SSD cache tier.
Use the storage remove and storage add commands to
remove the logical to physical mapping. This action ensures that
physical pages do not return previously written data. However, the
previously written data may still be on SSD.
14For more information, refer to the KB article, 545871, available from Dell
Technologies Support.
DD Encryption
Encryption at Rest
15• Can encrypt data on the PowerProtect DD appliance and is saved and locked
before moving the appliance to another location.
. Data that was in the system before encryption was enabled can be encrypted by
enabling an option to encrypt existing data.
Key Management
18When using Embedded Key Manager, key rotation can be enabled or disabled. if
enabled, type a rotation interval between 1 and 12 months. External key managers
rotate keys on a normal basis, depending on the key class.
Inline Encryption
With the encryption software option licensed and enabled, all incoming data is
encrypted inline before it is written to disk. This software-based approach requires
no additional hardware. It includes software encryption19. It also includes
confidentiality20 or message authenticity.21 You can also use both confidentiality
and message authenticity.
Encryption and decryption to and from the disk is transparent to all access
protocols.22
For the Data Security Manager (DSM), the system admin can select a 128-bit or
256-bit Advanced Encryption Standard (AES)23 algorithm for encrypting all data
within the system.
22DD Boost, NFS, CIFS, NDMP tape server, and VTL (no administrative action is
required for decryption)
Authorization Workflow
1. The security officer25 logs in through command line interface (CLI) and issues
the runtime authorization policy, authorization policy set security-
officer enabled.
2. The administrator role issues the command to enable encryption using the DD
System Manager (DDSM).
3. The DDSM prompts the security officer for their credentials26.
4. With system-accepted security credentials27, encryption is enabled.
24For example, when you want to set encryption, the admin enables the feature
and the security officer enables runtime authorization.
25To enable the authorization policy, a security officer must log in and enable the
authorization policy.
26The security officer must enter their credentials on the same console at which the
command option was run.
27If the security credentials are not accepted, a security alert is generated, and the
authorization log records the details of each transaction.
Configuring Encryption
The DD Encryption tab within the File System section of the DD System Manager
(DDSM) shows the status of system encryption of data at rest.
To configure DD Encryption:
1. Click Configure
You are prompted for a passphrase28.
2. Enter a passphrase, and then click Next
3. Choose the encryption algorithm29, and then click Next.
4. Select whether you obtain the encryption key from the PowerProtect DD system
or an external RSA Data Protection Manager.
5. Click Finish.
You must restart the system for the new configuration to start.
You can change the DD Encryption passphrase from the Administration >
Access window in DDSM.
You can disable encryption from the same window in the DDSM.
28The system generates an encryption key and uses the passphrase to encrypt the
key. One key is used to encrypt all data that is written to the system.
When encryption is enabled, administrators use the passphrase only when locking
or unlocking the file system, or when disabling encryption.
You can optionally apply encryption to data that existed on the system before
encryption was enabled.
Without the encryption that file system locking provides30, a thief with forensic tools
could recover the data—especially if local compression is turned off.
When you are ready, you can unlock the file system using a similar procedure.
Unless you can reenter the correct passphrase, you cannot unlock
the file system and access the data. The data will be irretrievably
lost.
The file system destroy option is removed from the DD System Manager (DDSM) in
DDOS as a security enhancement.
The user must log in from the CLI to perform any file system destroy operation.
File System Destroy option is present in older DDOS versions of the DDSM
The following table describes the capabilities of both DD Retention Lock editions:
Security officers can establish or modify runtime authorization policy using the
command line interface (CLI). Command options enable security-based functions
such as managing filesystem encryption and enabling or disabling authorization
policy. For complete information about the authorization command, see the
Dell EMC DD OS Command Reference Guide.
• authorization policy set security-officer {enabled |
disabled} - Enables or disables runtime authorization policy. Disabling
authorization policy is not allowed on Retention Lock Compliance systems. Role
required: security.
• authorization policy reset security-officer - Resets runtime
authorization policy to defaults. Resetting authorization policy is not allowed on
Retention Lock Compliance systems. Role required: security
• authorization policy set security-officer enabled - Shows the
current authorization policy configuration. Role required: security.
• authorization show history [last n { hours | days | weeks
}] - View or audit past authorizations according to the interval specified. Role
required: security.
You can also manage Retention Lock using the command line interface (CLI). The
mtree retention-lock command contains all the options to enable and disable
Retention Lock on PowerProtect DD systems. Among other functions, the mtree
retention-lock command can also place an indefinite hold on MTrees. For
complete information about the mtree retention-lock command, see the Data
Domain Operating System Command Reference Guide.
• mtree retention-lock enable mode {compliance | governance}
mtree mtree-path - Enables Retention Lock and edition for the specified
MTree. Enabling Retention Lock Compliance requires security officer
authorization. Role required: admin, limited-admin.
• mtree retention-lock disable mtree mtree-path - Disables
Retention Lock for the specified MTree. This command option is allowed on
Retention Lock Governance MTrees only. It is not allowed on Retention Lock
Compliance MTrees. See the DDOS Administration Guide for details on
Retention Lock Compliance and Governance. Role required: admin, limited-
admin.
• mtree retention-lock set {min-retention-period | max-
retention-period | automaticretention-period | automatic-
lock-delay} period mtree mtree-path - Sets the minimum or
maximum retention period for the specified MTree. This command option
requires security officer authorization if Retention Lock Compliance is enabled
on the MTree. Role required: admin, limited-admin.
1. Check for the presence of the DD Retention Lock Compliance license on the
system using the elicense show command.
If it is not present, install the license using the elicense update
command providing the license-file.
2. Set up one or more security officer users accounts according to Role-Base
Access Control (RBAC) rules. As system administrator, add a security officer
account: user add user role security.
3. Enable the security officer authorization authorization policy set
security-officer enabled
4. Configure the system to use DD Retention Lock Compliance. system
retention-lock compliance configure
The system automatically reboots.
5. After the restart process completes, create iDRAC users. user idrac
create
6. Enable DD Retention Lock Compliance on the system. system retention-
lock compliance enable
7. Enable compliance on and MTree that will contain retention-locked files. mtree
retention-lock enable mode compliance mtree mtree-path
8. You can configure the automatic retention period and automatic lock delay
using the following commands:
During sanitization, the system runs through five phases: merge, analysis,
enumeration, copy and zero.
Enumeration: Reviews all the files in the logical space and remembers what data
is active.
Copy: Copies live data forward and clears the space that it used to occupy.
You can view the progress of these five phases by running the system sanitize
watch command.
You can change the encryption passphrase without having to manipulate the
encryption keys. Changing the passphrase indirectly changes the encryption of the
keys, but does not affect user data or the encryption key.
Disabling Encryption
To disable DD Encryption you must have security authorization set and a security
officer login and password.
• Select Apply to existing data and click OK. Existing data decrypts during
the first cleaning cycle after the file system restarts.
• Select Restart the file system now and click OK. DD Encryption is disabled
after the file system restarts.
1. In the text fields of the Lock File System dialog box, provide:
• The username and password of a security officer account.
• The current passphrase.
• The new passphrase.
2. Click OK.
The system re-encrypts the encryption keys with the new passphrase. It also
destroys the cached copy of the current passphrase in-memory and on-disk.
3. Shut down the system using the system poweroff command in a terminal
window connected to the PowerProtect DD appliance.
1. Select Data Management > File System > Encryption and click Unlock File
System.
2. In the text fields, type the passphrase that was used to lock the file system.
3. Click OK.
4. Click Close to exit.
If the passphrase is incorrect, the file system does not start and the system
reports the error. Type the correct passphrase, as directed in the previous step.