NetWorker 19.3 Data Domain Boost Integration Guide
NetWorker 19.3 Data Domain Boost Integration Guide
NetWorker 19.3 Data Domain Boost Integration Guide
June 2020
Rev. 01
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2001 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.
Contents
List of Figures..........................................................................................................................................................7
List of Tables......................................................................................................................................................... 10
Preface.........................................................................................................................................................................................11
Contents 3
Firewall requirements.................................................................................................................................................... 28
Deduplication efficiency......................................................................................................................................................29
Retention periods.......................................................................................................................................................... 29
Types of data backed up.............................................................................................................................................. 29
Change rate....................................................................................................................................................................30
Frequency of full backups............................................................................................................................................ 30
Host naming guidelines....................................................................................................................................................... 30
Example name formats.................................................................................................................................................. 31
IP addresses.................................................................................................................................................................... 31
Example topologies.............................................................................................................................................................. 31
Client Direct deduplication environment..................................................................................................................... 31
Disaster recovery environment....................................................................................................................................32
Cascaded replication environment.............................................................................................................................. 33
Shared datazones environment...................................................................................................................................35
Dedicated storage node environment.........................................................................................................................36
3 Software Configuration.............................................................................................................. 38
DD Boost and Cloud Tier configuration road map...........................................................................................................38
Configuring DDVE system settings...................................................................................................................................38
Configuring DD Boost on the Data Domain system........................................................................................................39
Configuring the Data Domain system for DD Boost or Cloud Tier by using the Data Domain System
Manager......................................................................................................................................................................39
Configuring the Data Domain system for DD Boost by using the CLI.................................................................... 40
Configuring SMT on the Data Domain system.................................................................................................................41
Configuring DD Cloud Tier devices................................................................................................................................... 42
Adding DD Cloud Tier storage to a Data Domain System........................................................................................ 42
Import the cloud certificate..........................................................................................................................................43
Create the cloud profile and the cloud unit................................................................................................................ 44
Create the data movement schedule......................................................................................................................... 45
Configuring a Highly Available Data Domain system.......................................................................................................46
Configuring NetWorker for DD Boost devices.................................................................................................................47
DD Boost device performance considerations...........................................................................................................47
Configuring DD Boost devices with the NMC Device Configuration wizard.........................................................48
Configuring DD Boost devices with nsradmin .......................................................................................................... 55
Configuring NetWorker for Cloud Tier devices............................................................................................................... 56
Configuring NetWorker devices for DD Cloud Tier...................................................................................................56
Configuring a Cloud Tier device manually...................................................................................................................63
Configuring DD Cloud Tier devices with nsradmin....................................................................................................65
Configuring clients to back up to DD Boost devices...................................................................................................... 68
Configuring a backup client with the wizard..............................................................................................................68
Configuring a backup client with NMC property windows...................................................................................... 69
Manually creating or modifying NetWorker resources for DD Boost........................................................................... 70
Configuring DD Boost devices manually......................................................................................................................71
Deactivating and removing DD Boost devices.................................................................................................................76
Converting a device to read-only.................................................................................................................................77
Disabling a device...........................................................................................................................................................77
Deleting an AFTD or a DD Boost device..................................................................................................................... 77
4 Contents
Overview of protection policies......................................................................................................................................... 78
Default data protection policies in NMC's NetWorker Administration window...........................................................79
Strategies for traditional backups..................................................................................................................................... 80
Overview of configuring a new data protection policy.............................................................................................80
Creating a policy............................................................................................................................................................. 81
Create a workflow for a new policy in NetWorker Administration..........................................................................82
Protection groups for traditional backups.................................................................................................................. 83
Supported actions in traditional backup workflows.................................................................................................. 84
Actions sequences in traditional backup workflows..................................................................................................85
Visual representation of workflows.............................................................................................................................96
Cloning with Data Domain (DD Boost)............................................................................................................................. 97
Clone formats.................................................................................................................................................................97
CCR requirements......................................................................................................................................................... 97
Cloning by pools.............................................................................................................................................................98
DD Boost clone and replication support........................................................................................................................... 98
Clone formats.................................................................................................................................................................98
Native Data Domain replication considerations......................................................................................................... 99
Data Domain Automated Multi-streaming (AMS)...........................................................................................................99
Configuring the Data Domain CCR environment...........................................................................................................100
Strategies for cloning........................................................................................................................................................ 100
Road map for configuring a new cloning data protection policy............................................................................102
Road map to add a clone workflow to an existing policy.........................................................................................110
Clone reports....................................................................................................................................................................... 117
Monitoring the status of Cloud Tier save sets................................................................................................................ 117
Cloning with nsrclone......................................................................................................................................................... 118
Staging data from DD Cloud Tier devices....................................................................................................................... 118
Contents 5
Types of backup reports............................................................................................................................................. 128
Data Domain statistic reports.....................................................................................................................................130
Advanced reporting..................................................................................................................................................... 130
Replacing a failed or old storage node............................................................................................................................ 130
Troubleshooting.................................................................................................................................................................. 131
Data Domain system log files.......................................................................................................................................131
Troubleshooting DD Cloud Tier data movement issues.......................................................................................... 132
Too many streams........................................................................................................................................................134
Name resolution issues................................................................................................................................................ 134
Network connection issues.........................................................................................................................................134
Device access errors....................................................................................................................................................134
Backup fails for older NetWorker application modules........................................................................................... 135
Multiple recovery fails on AIX clients with less than 2 GB RAM............................................................................135
Backing up streams from NetWorker to Apollo DD is rejected..............................................................................135
Glossary................................................................................................................................................................143
6 Contents
List of Figures
Figure 1. DD Cloud Tier solution ......................................................................................................................... 16
Figure 6. Single datazone with dedicated storage nodes and one high-bandwidth link..............................37
List of Figures 7
Figure 22. Enabling the hidden attribute........................................................................................................... 56
Figure 26. Select the Folders to use as DD Cloud Tier Device page............................................................. 59
Figure 27. Configure a Pool for the DD Cloud Tier Device page....................................................................60
Figure 28. Select the Storage Nodes for the DD Cloud Tier Device page....................................................60
Figure 33. Example of the General tab configuration properties for a Cloud Tier device...........................64
Figure 39. Example of the device name and the access information for a DD Boost device.....................73
8 List of Figures
Figure 44. Workflow path from a traditional backup action............................................................................85
Figure 49. Example of a policy with separate workflows for backup and cloning........................................111
Figure 50. mminfo output for Cloud Tier save set ......................................................................................... 117
Figure 55. Migration from conventional storage to DD Boost devices on a different storage node.......140
Figure 56. Migration from conventional storage to DD Boost devices on the same storage node..........141
Figure 57. Migration from VTL to DD Boost devices on a different storage node.................................... 142
Figure 58. Migration from VTL to DD Boost devices on the same storage node...................................... 142
List of Figures 9
List of Tables
Table 1. Revision history........................................................................................................................................ 11
10 List of Tables
Preface
As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the
software or hardware currently in use might not support some functions that are described in this document. The product release notes
provide the most up-to-date information on product features.
If a product does not function correctly or does not function as described in this document, contact a technical support professional.
NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this
document, go to the Support website https://www.dell.com/support.
Purpose
This document provides planning, practices, and configuration information for the use of DD Boost devices within a NetWorker backup
and storage management environment.
Audience
This document is intended for system administrators. Readers of this document must be familiar with the following tasks:
• Identifying the different hardware and software components that make up the NetWorker datazone.
• Following procedures to configure storage management operations.
• Following guidelines to locate problems and implement solutions.
Revision history
The following table presents the revision history of this document.
Related documentation
The NetWorker documentation set includes the following publications, available on the Support website:
• NetWorker E-LAB Navigator
Provides compatibility information, including specific software and hardware configurations that NetWorker supports. To access E-
LAB Navigator, go to https://elabnavigator.emc.com/eln/elnhome.
• NetWorker Administration Guide
Describes how to configure and maintain the NetWorker software.
• NetWorker Network Data Management Protocol (NDMP) User Guide
Describes how to use the NetWorker software to provide data protection for NDMP filers.
• NetWorker Cluster Integration Guide
Contains information related to configuring NetWorker software on cluster servers and clients.
• NetWorker Installation Guide
Provides information on how to install, uninstall, and update the NetWorker software for clients, storage nodes, and servers on all
supported operating systems.
• NetWorker Updating from a Previous Release Guide
Describes how to update the NetWorker software from a previously installed release.
• NetWorker Release Notes
Contains information on new features and changes, fixed problems, known limitations, environment and system requirements for the
latest NetWorker software release.
Preface 11
• NetWorker Command Reference Guide
Provides reference information for NetWorker commands and options.
• NetWorker Data Domain Boost Integration Guide
Provides planning and configuration information on the use of Data Domain devices for data deduplication backup and storage in a
NetWorker environment.
• NetWorker Performance Optimization Planning Guide
Contains basic performance tuning information for NetWorker.
• NetWorker Server Disaster Recovery and Availability Best Practices Guide
Describes how to design, plan for, and perform a step-by-step NetWorker disaster recovery.
• NetWorker Snapshot Management Integration Guide
Describes the ability to catalog and manage snapshot copies of production data that are created by using mirror technologies on
storage arrays.
• NetWorkerSnapshot Management for NAS Devices Integration Guide
Describes how to catalog and manage snapshot copies of production data that are created by using replication technologies on NAS
devices.
• NetWorker Security Configuration Guide
Provides an overview of security configuration settings available in NetWorker, secure deployment, and physical security controls
needed to ensure the secure operation of the product.
• NetWorker VMware Integration Guide
Provides planning and configuration information on the use of VMware in a NetWorker environment.
• NetWorker Error Message Guide
Provides information on common NetWorker error messages.
• NetWorker Licensing Guide
Provides information about licensing NetWorker products and features.
• NetWorker REST API Getting Started Guide
Describes how to configure and use the NetWorker REST API to create programmatic interfaces to the NetWorker server.
• NetWorker REST API Reference Guide
Provides the NetWorker REST API specification used to create programmatic interfaces to the NetWorker server.
• NetWorker 19.3 with CloudBoost 19.3 Integration Guide
Describes the integration of NetWorker with CloudBoost.
• NetWorker 19.3 with CloudBoost 19.3 Security Configuration Guide
Provides an overview of security configuration settings available in NetWorker and Cloud Boost, secure deployment, and physical
security controls needed to ensure the secure operation of the product.
• NetWorker Management Console Online Help
Describes the day-to-day administration tasks performed in the NetWorker Management Console and the NetWorker Administration
window. To view the online help, click Help in the main menu.
• NetWorker User Online Help
Describes how to use the NetWorker User program, which is the Windows client interface, to connect to a NetWorker server to back
up, recover, archive, and retrieve files over a network.
NOTE: Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the
UI, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the
UI has not yet been updated to reflect this change.
• Data Domain Boost Compatibility Guide
Provides compatibility information for DellEMC and third party applications, and Fibre Channel hardware solutions, that interoperate
with Data Domain Boost (DD Boost) technology.
Typographical conventions
The following type style conventions are used in this document:
12 Preface
Table 2. Style conventions
Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons,
fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area
with title, table label, and window.
Italic Used for full titles of publications that are referenced in text.
Monospace Used for:
• System code
• System output, such as an error message or script
• Pathnames, file names, file name extensions, prompts, and syntax
• Commands and options
You can use the following resources to find more information about this product, obtain support, and provide feedback.
Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by
keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Knowledge Base.
3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by typing a
product name in the search box, and then selecting the product from the list that appears.
Live chat
To participate in a live interactive chat with a support agent:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Contact Support.
3. On the Contact Information page, click the relevant support, and then proceed.
Preface 13
Service requests
To obtain in-depth help from Licensing, submit a service request. To submit a service request:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests.
NOTE: To create a service request, you must have a valid support agreement. For details about either an account or
obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the
Service Request Number field, type the service request number, and then click the right arrow.
Online communities
For peer contacts, conversations, and content on product support and solutions, go to the Community Network https://www.dell.com/
community. Interactively engage with customers, partners, and certified professionals online.
14 Preface
1
DD Boost Features and Environment
This chapter includes the following topics:
Topics:
• DD Boost integration features
• Data Domain network environment
• Licensing for Data Domain systems
Secure multi-tenancy
NetWorker supports DD Boost devices in secure multi-tenancy (SMT) storage on Data Domain systems. SMT enables service providers to
isolate tenant users on a Data Domain system. A global storage administrator assigns or creates a tenant unit (TU) for each tenant user.
Tenant users (for example, backup administrators) must use a DD Boost username and password to create the secure storage units (SUs)
that the DD Boost devices use to store data.
DD Retention Lock
The Data Domain Retention Lock (DD Retention Lock) feature within NetWorker allows you to efficiently manage and store different
types of data backed up by NetWorker to a single Data Domain system by securely locking the data on that system, preventing accidental
deletion of save sets.
When you enable a device with DD Retention lock and DD Retention lock period is set in data protection policy action, the save sets
backed up by the NetWorker policy cannot be overwritten, modified, or deleted for the duration of the retention period, up to a maximum
of 70 years. Additionally, the device cannot be removed or relabeled at any time during the retention period, though the device that
contains the Retention Lock save sets can be mounted and unmounted. The secure locking of data occurs at an individual file level, and
locked files can co-exist with unlocked files on the same Data Domain system.
With DD Retention Lock, you can set the retention time to meet the requirements driven by governance policies. The DD Retention Lock
Time specified at the save set level must fall within the range of the minimum and maximum retention times configured on the DD Boost
Mtree during device creation. The Retention lock modes are Compliance lock mode and Governance lock mode. Governance mode is
supported from NetWorker 9.2 onwards. Compliance mode is supported from NetWorker 18.1 onwards.
You can enable DD Retention Lock on the DD Boost Mtree during device configuration, as described in the section Configuring DD Boost
devices with the NMC Device Configuration wizard, or by modifying the device properties after configuration, as described in the section
Configuring a DD Boost device manually. If using the NMC Device Configuration wizard for the first instance of Data Domain device
configuration, ensure that you populate the Data Domain device management credentials (Management host, Management user name,
management password and management port).
When you enable DD Retention Lock at the device level, you must additionally set Retention Lock period to the data protection policy
action so that data is backed up with Retention Lock set. The section Creating a traditional backup action provides more information.
After successful backup, save set queries in the Media window of NetWorker Administration displays DD Retention Lock Period and
DD Retention Lock Type columns to indicate which save sets have Retention Lock enabled and provide the Retention Lock expiry date
and time. If these columns are not initially visible, you can customize the view to include this information. This information is also available
within the NMC Enterprise Reports window, under Policy Statistics > Save Set Details. Similarly, if these columns are not initially
visible, you can customize the view to include this information.
Requirements
Review the following requirements for enabling DD Retention Lock:
• The NetWorker Server and storage node version must be NetWorker 19.3.
• The minimum DDOS version required when using the DD Retention Lock feature is DDOS 6.0. The minimum DD Boost version is 3.4.
• Workflows that contain Data Domain Retention Lock enabled save sets require a separate destination pool. The pool cannot contain a
mixture of Retention Lock and non-Retention Lock enabled Data Domain devices.
• The Data Domain devices storing primary and cloned backups with DD Retention Lock enabled cannot be labelled or deleted. Disk
space utilization issues will result on the Data Domain system.
NetWorker client
A NetWorker client is a supported host whose data requires protection. The NetWorker client software includes an integrated DD Boost
plug-in. The NMC server, NetWorker server, and NetWorker storage nodes are also NetWorker clients.
NetWorker clients that use Client Direct deduplication must have direct network access to the Data Domain system, which stores the
data. By default, NetWorker enables Client Direct in the properties of the Client resource.
Client Direct with FC connectivity to DD Boost devices requires NetWorker client 8.1 or later.
The NetWorker E-LAB Navigator provides information on supported releases.
NetWorker Server
The NetWorker Server is a collection of processes and programs that are installed on a host that performs NetWorker services. The
NetWorker Server also acts as a storage node and can control multiple remote storage nodes.
NMC Server
The NetWorker Management Console (NMC) server or Console server is a Java-based application and database server. The NMC Server
manages all NetWorker Servers and Clients. The NMC Server provides reporting and monitoring capabilities for all NetWorker Servers and
Clients in the environment. The NMC Server relies on the NetWorker Authentication Service for user account authentication.
SMT structure
For SMT storage, a global storage administrator isolates DD Boost users, for example backup administrators, by assigning them to tenant
units (TUs). A TU cannot span Data Domain systems. You can assign a DD Boost user to only one TU, but you can assign multiple DD
Boost users to the same TU. Each DD Boost user can create SUs within the assigned TU only. Security is enforced at the TU level by the
DD Boost user assignment on the Data Domain system, and at the SU level by the DD Boost credentials.
For example:
Tenant 1: bob, tu1, su1
Tenant 2: joe, tu2, su2
Tenant 3: sue, tu2, su3
DD Boost performance
DD Boost devices use multiple concurrent nsrmmd (media mover) processes per device and each nsrmmd process uses multiple
concurrent save sessions (streams or threads). This reduces the performance and maintenance impacts on the Data Domain system.
Balance the session load among the available DD Boost devices so that new sessions attach to devices with the least load. To enable best
performance, you can adjust the Target Sessions, Max Sessions, and Max nsrmmd Count attributes assigned to the Device resource
on the NetWorker server.
Configuring a DD Boost device manually on page 72 provides details on session settings.
The Data Domain documentation provides additional details on save sessions and performance.
Network requirements
DD Boost devices support data transport over both Ethernet IP networks and FC SAN environments for both data backup and data
recovery operations.
The NetWorker server requires Ethernet IP connections to control all hosts involved in the DD Boost operations.
Ethernet IP support
DD Boost devices do not distinguish between different TCP/IP network types (LAN, WAN, or MAN) and can successfully operate in a
network where packet loss is strictly 0% and latency is less than 20ms. Variations of IP network connections can improve data
throughput, depending on the Data Domain system model.
It is recommended to use a minimum of two separate IP network connections to the Data Domain system. One is used for administration
and the other is used for data backup.
Aggregated multiple connections can further improve data throughput for the Data Domain system. For example, you can use multiple 1
GbE connections for dedicated storage nodes and storage devices. Connections for 10 GbE are also available and you can use these
instead of or with 1 GbE links.
You can configure two basic IP interfaces:
• Dedicated 1 GbE data connection from the storage node directly to the Data Domain system. This connection provides a private, high-
bandwidth data connection and avoids the latency and complexity of a shared IP connection. You also require a separate conventional
IP connection for administration and NetWorker Console access.
The Data Domain Operating System Administration Guide provides details on network support.
• Two or more NICs on the Data Domain system with 1 GbE or 10 GbE connections, which are aggregated together by using the Data
Domain ifgroup command. This grouping provides increased data capacity and can improve resiliency. The Data Domain system
provides automatic Advanced Load Balancing and Link Failover for NIC connections.
NOTE: NetWorker supports ifgroups for replication. Do not use aggregated connections for replication operations.
The Data Domain Boost for Open Storage Administration Guide describes the benefits, limitations, and examples of using ifgroups,
which apply to NetWorker.
• Windows, Linux, HP-UX, AIX, and Solaris client environments are supported.
• Beginning with DD Boost 3.3 and DD OS 6.0, you do not need a device driver; you can enable DD Boost-over-FC by
creating a ddboost fc group; see Step 3 in the following procedure.
• To enable DD Boost-over-FC on clients running AIX, you can also install the AIX DDdfc device driver.
Ensure that the client's HBA ports and the Data Domain system's endpoints are defined and that appropriate zoning has been done if you
are connecting through a Fibre Channel switch.
1. Enable the DD Boost-over-FC service:
NOTE: Similar to IP hostnames, the dfc-server-name is not case-sensitive. Multiple Data Domain sytems
accessible by the same clients using DDBoost-over-FC should be configured without case-sensitive dfc-server-
name.
NOTE: The disk option in the previous example is optional and supported only if the client is AIX.
Example:
The number of DFC devices advertised to the initiator is controlled by configuring the device-set of the scsitarget access group:
The maximum number of supported DFC devices per protection system is 64. You can have the same devices in multiple groups, but each
group is limited to 64 devices.
NOTE: AIX DDdfc drivers support 128 devices. However, if you use the disk option with the ddboost fc add
command, this limitation is removed.
Because the DFC client sees each path to the protection system as a separate device, more paths and more DFC devices mean better
performance for constrained clients such as AIX, Windows, and Solaris.
So, how many DFC devices should be advertised to initiators on a given backup server? The answer depends upon several factors:
1. Is the backup server queue-depth constrained?
Windows platforms are considered "queue-depth constrained," because the Windows SCSI Pass-Through Interface mechanism will
only conduct 1 SCSI request at a time through each of its generic SCSI devices. This impacts the performance of the DD Boost-over
FC solution, if multiple connections (for example, backup jobs) are trying to use the same generic SCSI device. So, for Windows
platforms running more than one job, it is useful to advertise multiple DFC devices.
Contrast this with the behavior of the Linux SCSI Generic driver, which imposes no such restriction. Linux is not considered "queue-
depth constrained," so it is sufficient to simply advertise one DFC device to initiators on Linux systems.
2. Number of physical paths between backup server and protection system
For each advertised DFC device, the backup server operating system will create n generic SCSI devices, one for each physical path
through which the backup server OS can access the device.
For example, if:
• Backup server has 2 initiator HBA ports (A and B)
• Protection System has 2 FC target endpoints (C and D)
• Fibre Channel Fabric zoning is configured such that both initiator HBA ports can access both FC target endpoints
then the backup server OS will see each device through four physical paths:
A -> C
A -> D
Sizing calculation
The following calculation may be used to determine the number of DFC devices to advertise on the Data Domain system and to the
initiators on a given media server. Dell EMC recommends that the same number of DFC devices be advertised to all initiators on the same
media server.
The following calculation may be used to determine the number of DFC devices to advertise on the Data Domain system and to the
initiators on a given backup server. It is recommended that the same number of DFC devices be advertised to all initiators on the same
storage nodes.
Example:
To calculate the max simultaneous connections to the Data Domain system by using DFC from ALL media servers, assume:
• 8 media/master servers, single Data Domain systems, each server running a maximum of 50 jobs at any given time.
Therefore, J = 8 * 50 = 400
C = 1 (single Data Domain system)
S= J * C
S= 400 * 1
S= 400
• 8 storage nodes, single Data Domain systems, each server running a maximum of 50 jobs at any given time.
Therefore, J = 8 * 50 = 400
C = 1 (single Data Domain system)
S = J * C = 400
D = 2 * 400 / 128 = 6.25. Round up to 7.
• Therefore, all DFC groups on the Data Domain system must be configured with 7 devices.
Linux
The number of DFC devices advertised on the Data Domain system using the calculations listed above in On the Data Domain System is
sufficient for Linux backup servers. No additional configuration is required. Linux storage nodes are not queue-depth constrained, so many
connections can share the same DFC generic SCSI device with no performance impact.
Windows
The Data Domain server path management logic spreads out connections across available logical paths (Initiator, Target Endpoint, DFC
Device). We want to configure enough DFC devices such that each connection uses its own generic SCSI device (logical path) on the
backup server, with a max DFC device count of 64.
Let X = the number of DFC devices configured on the Data Domain system (from On the Data Domain System). Let P = number of
physical paths between backup server and Data Domain system. Let J = maximum number of simultaneous jobs, and let C = maximum
number of connections per job:
– 3 for DD Extended Retention systems – 1 for other types of Data Domain systems
Calculate:
• Maximum simultaneous connections from storage node S = J * C, DFC device count D = minimum((S/P), X), round up, up to a
maximum of 64.
Note that if the value of D is greater than X, then it is sufficient to configure D devices, but only for the access group(s) with Windows
clients.
Examples:
Assume:
• 4 physical paths between the storage node and Data Domain system, 30 maximum jobs, DD Extended Retention system
• In this case, X = 25, P = 4, J = 30, and C = 3
• Maximum simultaneous connections from backup server S = (J * C) = 90
• DFC device count D = (90/4, 25) = 25
So, the Data Domain system should be configured to advertise 25 devices to each initiator on the storage node.
Assume:
• 2 physical paths between the backup server and Data Domain system, 50 maximum jobs, single Data Domain system
• In this case, X=18, P = 2, J = 40, C = 1
• Maximum simultaneous connections from backup server S = (J * C) = 40
• DFC device count D = max(40/2, 18) = 20
So, the Data Domain system should be configured to advertise 20 devices to each initiator on the storage node.
Note that since the value of D (20) is greater than the value of X (18), it is sufficient to configure two devices only for the DFC access
group with Windows clients.
Firewall requirements
Regardless of the network connections that are used, communication through a firewall requires the use of specific ports and specific
protocols to perform backup, monitoring, and replication operations across sites.
The following table lists the required firewall ports, which you must open between the Data Domain system, the NetWorker server, and
the NMC server.
162 TCP SNMPTRAP for • NMC Server • Data Domain backup target
the NMC server • Data Domain Replication target
to monitor status
and events
The Data Domain system provides functionality to review the network configuration and network capabilities and provides SSH Telnet to
help diagnose issues.
Deduplication efficiency
The deduplication ratio measures the efficiency of reduction in storage space that results from the data deduplication and compression
technology. Ratios of 20:1 are broadly achievable and reductions of even 5:1 are extremely valuable.
Several factors can contribute to the deduplication ratio:
• Retention periods
• Types of data backed up
• Change rates
• Frequency of full backups
• Use of encryption and compression
For the best use of storage space, consider the factors in the following sections, along with the periodic clearing of expired storage space,
and the removal of unused pools.
Retention periods
The deduplication ratio increases with longer data retention periods. The longer you retain the stored save sets, the greater the chance
that identical data will exist on the storage that NetWorker uses to deduplicate each subsequent backup, and the greater is the efficiency
of the storage usage.
When you define longer retention periods, the data remains on the Data Domain device for a longer period of time. This enables
NetWorker to use the retained data to deduplicate subsequent backups, and results in a more efficient use of storage.
DD Boost devices
Format: Data_Domain_system_name-device_name
For example: dd-tenendo-device01
IP addresses
Avoid IP addresses because numbers are more difficult to identify and troubleshoot than descriptive names. However, there are
exceptions:
• The Data Domain system requires the use of IP addresses to interface with an ifgroup for Advanced Load Balancing and Link Failover
features.
• For CCRs, the hosts file on the source Data Domain system must list the IP address of the target Data Domain system. Otherwise, the
CCR will use the same network access that the backup and restore operations use.
The Data Domain documentation provides details.
Example topologies
This section provides some examples of how you can deploy the Data Domain integration in NetWorker backup environments. Dell EMC
recommends that you use two interfaces in Ethernet IP networks, 1 GbE for administration and 10 GbE for data. For FC environments, use
IP interfaces for administration and clone operations, and a SAN interface for backup operations. Use the following examples to plan your
environment.
1. The NetWorker server starts the backup of the client groups within the datazone.
2. Two storage nodes in the datazone write the backup data to media pools, which target specific DD Boost devices on the primary
system. The pool that is associated with the data protection policy defines which storage devices receive the data.
3. The storage nodes communicate with the primary Data Domain system over a dedicated 10 GbE network connection, and store
deduplicated backup data on the devices.
NOTE: An ifgroup configuration of 1 GbE or 10 GbE NICs on the Data Domain system enables multiple storage nodes
to use the same network identity. This bandwidth aggregation can improve performance for DD Boost devices. The
Data Domain documentation provides details.
4. You can use CCR to store optimized clone copies of backups from the primary Data Domain system over a network to a geographically
distant secondary Data Domain system for disaster recovery.
5. An additional option enables a further clone to conventional disk or conventional tape media. A NetWorker storage node, which is
attached to the secondary Data Domain system, creates an additional NetWorker clone copy of the data for one of the backup groups,
which NetWorker stores on conventional media. NetWorker reverts the data in this copy to the native non-deduplicated format, which
is necessary for storage on conventional media.
NOTE: The Client Direct (DFA) feature can provide similar benefits without the need for storage node licenses.
The figure in this section illustrates a mixed environment of shared and dedicated storage nodes.
1. The NetWorker server starts a backup of file system and module data on a dedicated storage node.
2. The storage nodes write the deduplicated backup data to the DD Boost storage devices on the Data Domain system. The pool that is
associated with the data protection policy defines which storage devices receive the data.
NOTE: An ifgroup configuration of 1 GbE or 10 GbE NICs on the Data Domain system enables multiple storage nodes
to use the same identify on an IP network. This aggregation of bandwidth can improve performance for DD Boost
devices. The Data Domain documentation provides details.
3. A high-volume storage node uses an additional dedicated 10 GbE direct connection.
NetWorker E-LAB Navigator provides information on NetWorker application modules compatible with Data Domain systems.
38 Software Configuration
Configuring DD Boost on the Data Domain system
Use the Data Domain System Manager or the CLI to configure DD Boost on the Data Domain system.
13. In the Summary tab, Protocols pane, select NFS export > create export.
The Create NFS Exports window appears.
14. In the Create NFS Exports window:
a. In the Export Name field, specify the name of the DD MTree.
b. In the Directory path field, specify the full directory path for DD MTree that you created. Ensure that you use the same name for
the directory.
Software Configuration 39
c. In the Clients table, select the NetWorker server, if the NetWorker server does not appear, and then click the + (Add) button. In
the Client field, specify the FQDN of the NetWorker server, and then click OK.
d. Click OK, and then click Close.
NOTE: For DD Boost functionality, you must enable NFS services on the Data Domain system, even if you do not
configure users or shares. You do not need to enable NFS on the NetWorker server, NetWorker storage nodes, or
NetWorker clients.
For example:
ddboost user assign bob, joe, sue
NOTE: To unassign one of more users from the DD Boost user list, type the following command:
ddboost enable
8. To configure the system to receive and generate SNMP traps, type the following command.
snmp add ro-community community_name
snmp enable
where community_name is typically “public”, which allows all users to monitor events.
SNMP traps enable users to monitor backup events that are captured by SNMP traps.
9. To configure Distributed Segment Processing (DSP), type the following commands:
40 Software Configuration
a. To enable DSP, type: ddboost option set distributed-segment-processing enabled
b. To confirm that DSP is enabled, type: ddboost option show.
NetWorker storage nodes and NetWorker clients require DSP to support deduplication operations.
10. (Optional) To enable Fibre Channel (FC) connectivity on DD Boost devices, use the ddboost fc command to obtain the DD Boost
over FC (DFC) server name:
ddboost fc dfc-server-name show
NOTE: You will specify the DFC server name in the NetWorker device configuration procedure. FC-enabled clients
can back up only to FC-enabled devices. IP-enabled clients can back up only to IP-enabled devices.
For example, in the following output, the DFC server name is dd-tenendo:
ddboost fc dfc-server-name show
DDBoost dfc-server-name: dd-tenendo
Configure clients to use "DFC-dd-tenendo" for DDBoost FC
NOTE: Do not use the "DFC-" prefix on the DFC server name, as suggested in the output of the ddboost fc dfc-
server-name show command. This prefix is intended for use with other vendors only and will cause NetWorker
communications to the DFC server to fail.
To create DD Boost devices and the Data Domain SU folders that contain the devices, use the NetWorker Device Configuration Wizard.
1. Log in to the Data Domain system console with a user account that has the Global Storage Administrator role.
2. Use the user add command to create one or more new user account, and assign the none role to the user:
user add username password password [role role]
For example, to create three SMT user accounts named bob, joe and sue, type the following commands:
user add bob password mypwbob role none
To assign TU tu2 to DD Boost users joe and sue, type the following commands:
ddboost user option set joe default-tenant-unit tu2
Software Configuration 41
Because you assign a default TU to each DD Boost user, NetWorker automatically associates any storage unit (SU) created by a DD
Boost user to their default TU. NetWorker does not expose the TUs.
• (Optional) To unassign a DD Boost user from its default TU, or to reassign the user to a different default TU, type the following
command:
ddboost user option reset username [default-tenant-unit]
NOTE: Avoid changing the owners of DD Boost SUs. A new owner cannot use the DD Boost devices from a
previous owner. Create a device for the new owner instead.
• (Optional) To list the DD Boost users and their default TUs, or the DD Boost users within a specific default TU, type the following
command:
ddboost user show [default-tenant-unit tenant-unit]
NOTE: You can use the CLI to review tenant space usage and the performance data at both the TU and SU levels.
As the global storage administrator, you can enable tenants to use the Data Domain CLI to review the space usage
and the performance data of their TU and SUs. The Data Domain documentation provides details.
42 Software Configuration
Adding a DD Cloud Tier by using Data Domain System Manager
Perform the following steps to add DD Cloud Tier storage to an existing Data Domain system.
The DD Cloud Tier feature requires a Cloud Tier Capacity license.
1. Use a web browser to log in to the DD System Manager as the system administrator.
2. In the left navigation pane, select Hardware > Storage.
3. Click Configure, located above the Cloud Tier table.
4. From the Addable Tier table:
a. Select an available disk.
b. Click Add to Tier.
c. Click Next.
NOTE: If a device does not appear in the Addable Storage table, add a new disk to the virtual machine.
Software Configuration 43
Create the cloud profile and the cloud unit
Create the cloud profile and the cloud unit on the Data Domain system or DDVE by using the CLI or the DD System Manager.
Creating the Cloud Profile and Cloud Unit by using the CLI
Data Domain supports a maximum of two Cloud Units.
Perform the following steps on the Data Domain system or DDVE to create the Cloud Profile and Cloud Unit.
1. Log in to the Data Domain system or DDVE as the sysadmin user.
2. Type the following command to create the Cloud Profile:
cloud profile add profile_name
where profile_name is a descriptive name for the profile.
3. At the Enter provider name prompt, type the name of the provider:
• Dell EMC Elastic Cloud Storage (ECS)—ecs
• Virtustream Cloud Storage—virtustream
• Amazon Web Services S3—aws
4. For the Virtustream Storage Cloud provider only, at the Enter Storage Class prompt, type the storage class.
5. For the Virtustream Storage Cloud and Amazon Web Service S3 providers only, at the Enter Storage Region prompt, type the
storage region.
6. At the Enter the access key prompt, type the cloud provider access key.
7. At the Enter the secret key prompt, type the cloud provider secret key.
8. For Dell EMC Elastic Cloud Storage (ECS) only, at the Enter the endpoint prompt, type the load balancer endpoint address for the
cloud provider.
For example: http://172.21.21.10:9020
Load balancer is mandatory for all ECS Cloud Tier deployments.
9. At the Do you want to enter proxy details prompt, press Enter to accept the default value, no.
10. Type the following command to add a new Cloud Unit:
cloud unit add unit_name profile profile_name
where:
• unit_name is a descriptive name for the Cloud Unit, for example cloud-unit-1.
• profile_name is the name of the cloud profile that you created.
For example:
Creating the Cloud Profile and Cloud Unit by using Data Domain
System Manager
Data Domain supports a maximum of 2 Cloud Units.
Perform the following steps to create the Cloud Profile and Cloud Unit.
1. Use a web browser to log in to the DD System Manager as the system administrator.
2. In the left navigation pane, select Data Management > File System.
3. On the Cloud Units tab, click Add.
4. In the Name field, provide a descriptive name for the Cloud Unit.
5. In the Cloud Provider list, select the cloud provider.
6. For the Virtustream Storage Cloud provider only, in the Storage Class field, type the storage class.
7. For the Virtustream Storage Cloud and Amazon Web Service S3 providers only, in the Storage Region field, type the storage region.
8. In the Access key field, specify the cloud provider access key.
9. In the Secret key field, specify the cloud provider secret key.
10. For Dell EMC Elastic Cloud Storage (ECS) only, in the Endpoint field, specify the load balancer endpoint address for the cloud provider.
11. Click OK.
The Cloud Units page displays information about the Cloud Unit, and the status of the unit is Enabled.
44 Software Configuration
Create the data movement schedule
The data movement schedule determines the frequency in which data moves from the DD Cloud Tier device to the cloud provider.
Before you configure the data movement operation to the cloud for long term storage, consider the day of the week, time of day, and
frequency in which you will schedule the movement operation. The data movement command moves all data that is available on the DD
Cloud Tier device to the Cloud provider. Ensure that you define a frequency that allows you to move the data over a period of time that
does not impact your network. Define a day of the week and time when network bandwidth and the cost of moving the data is low.
Create the data movement schedule on the Data Domain system or DDVE by using the CLI or the Data Domain System Manager.
For example, to schedule the data movement operation to run every two weeks at 11 pm on a Thursday, type:
data-movement schedule set to-tier cloud days "Thursday" time "23:00" every 2 wks
Software Configuration 45
a. In the Every field, type the number of weeks in which to run the schedule. For example, to run the movement operation bi-
monthly, type 2.
b. From each At box, select the hour, minute, and AM or PM.
c. In the On field, select the day of the week in which to run the schedule.
The following figure provides an example of a bi-monthly movement schedule that occurs every Saturday at 8 P.M.
46 Software Configuration
• For the highly available Data Domain system, specify the floating IP.
• For node 1, specify the hostname with the correct community string.
• For node 2, specify the hostname with the correct community string.
b. Click Next.
5. In the Select Host Type page:
a. Select DataDomain.
b. Click Next.
6. In the Manage DataDomain page:
a. Review the configuration details.
b. Click Next.
c. Leave the Capture Events option selected.
7. (Optional) In the Configure SNMP Monitoring page, perform the following steps:
a. In the SNMP Community String field, type the name of the SNMP community string.
NOTE: If you do not know the name of the community, leave this field blank.
b. With the Receive SNMP trap events option selected, specify the SNMP Process port that is used by the Data Domain system
and select the events in which to monitor. Use the Reset to defaults option to reset the events in which to monitor back to the
default settings.
NOTE: The default SNMP process port is 162.
c. Click Next.
SNMP monitoring enables NMC to display the Data Domain system status and to list the backup and the recovery events. The
monitoring feature also provides a launcher link for the Data Domain interface.
d. Click Finish.
8. Configure alerts for Data Domain High Availability events:
a. Click the Devices button on the taskbar.
b. In the left navigation pane, right-click Data Domain Systems and select New Device Wizard.
c. Open the SNMP Monitoring Options page and select the following options:
• HA Setup Degraded
• HA Setup Offline
• HA Setup Out-of-Sync
Software Configuration 47
Configuring DD Boost devices with the NMC Device
Configuration wizard
Use the NMC NetWorker Administration Device Configuration wizard to create or modify Data Domain devices, and to define the Data
Domain system on the NetWorker server.
1. Log in to the NMC GUI as an administrator of the NetWorker server.
2. On the taskbar, click the Enterprise icon .
3. In the navigation tree, highlight a host:
a. Right-click NetWorker.
b. Select Launch Application. The NetWorker Administration window appears.
4. On the taskbar, click the Devices button .
5. In the left navigation pane:
a. Right-click Data Domain Systems.
b. Select New Device Wizard.
NOTE: To modify completed wizard pages, click the links in the steps panel. The number of steps may vary according
to the type of configuration chosen.
6. In the Select the Device Type page, select the Data Domain device type, and then click Next.
The following figure provides an example of the Select the Device Type page.
7. In the Data Domain Preconfiguration Checklist page, review the requirements, and then click Next.
The following figure provides an example of the Data Domain Preconfiguration Checklist page.
48 Software Configuration
Figure 11. Data Domain Preconfiguration Checklist page
8. In the Specify the Data Domain Configuration Options page, configure the following fields:
a. In the Data Domain System section, select one of the following options:
• To use a Data Domain system on which you have previously created devices or configured as a managed host, select Use an
existing Data Domain System, and then select the host.
• To use a new Data Domain system, select Add a new Data Domain System, and then type the FQDN or IP address of the
Data Domain system or DDVE.
NOTE: If you use DFC connectivity, Do not use the "DFC-" prefix on the DFC server name, as suggested in the
output of the ddboost fc dfc-server-name show command. This prefix is intended for use with other
vendors only and will cause NetWorker communications to the DFC server to fail.
b. In the DD Boost Credentials section, type the username for the DD Boost user in the DD Boost Username field.
c. In the Secure Multi-Tenancy section, to use only DD Boost devices in secure Storage Units (SUs), select Configure Secure
Multi-Tenancy (SMT), and then perform one of the following tasks:
• To use an existing storage unit (SU), select Use an existing secure storage unit, and then select the SU.
• To create a SU, select Create a new secure storage unit, and then specify the name of the SU.
NOTE: SMT restricts access of each SU to one owner according to the provided DD Boost credentials.
d. (Optional) In the DD Management Credentials section, configure the management credentials that are required to perform
VMware Instant Access and FLR recoveries:
• To not specify the management credentials, leave the default selection Don't configure Management Credentials now.
• To instruct NetWorker to use the DD Boost user credentials that you specified in the DD Boost Credentials section, select
Use the DDBoost Credentials from above.
• To specify a different sysadmin user, select Enter Management Credentials, and then specify the username and password
of a sysadmin user.
NOTE: If you plan to use the REST API for features such as DD Cloud Tier policy creation and DD Retention Lock,
you must additionally update the NSR Data Domain RAP resource with the Management username, password,
port, and host. If these credentials and details are not specified in the RAP resource, then a validation error
occurs.
e. In the Configuration Method field, select Browse and Select, and then click Next.
NOTE: If you do not configure the SMT option, the wizard will create an SU for you on the Data Domain system,
and name the SU after the shortname of the NetWorker server.
The following figure provides an example of the Specify the Data Domain Configuration Options page.
Software Configuration 49
Figure 12. Specify the Data Domain Configuration Options page
9. In the Select Folders to use as Devices page, to create a DD Boost device, perform the following steps:
a. Select the Data Domain system, and then click New Folder.
A new folder appears in the navigation tree. This folder is the new device.
NOTE: The navigation tree does not show the SU folder under the Data Domain system folder. However, the SU
folder is verifiable in the final Review Configurations Settings wizard page. The wizard names the SU folder after
the short hostname of the NetWorker server and places the devices that you create into this SU folder.
b. Type a name for the new folder, and then select the checkbox next to the folder or device name.
The Device table displays the full NetWorker device name, the storage pathname, and details about the device.
NOTE: The device name refers to the subfolder created within the SU. The folder path must not contain other
folders deeper than these device folders.
c. (Optional) To rename a DD Boost device as it appears in NMC, select the device in the table, and type a new name in the
NetWorker Device Name field. Do not use special characters other than dot (.) and underscore (_). The Storage Path field
remains unchanged.
NOTE: Implicit in the SU folder pathname on the Data Domain system is the hidden mount point folders/data/
col1. Do not modify this folder structure, which all NetWorker server hosts use. The final wizard page, Review
Configurations Settings, shows the complete location.
The /backup folder stores NFS service data. The clients that are configured for NFS access can view, change,
and delete the /data/col1 directory that contains the DD Boost devices. If you use NFS devices, you can avoid
the risk of potential interference by using alternative path names.
d. Click Next.
The following figure provides an example of the Select the Folders to use as Devices page.
50 Software Configuration
Figure 13. Select the Folders to use as Devices page
10. On the Configure Pool Information page, perform the following steps:
a. Select Configure Media Pools for Devices.
b. In the Pool Type section, select the type of data to send to the Data Domain device, either Backup for backups or Backup
Clone for cloning or staging operation.
c. In the Pool section, select Create and use a new Pool to create a pool to receive the data, or select Use an existing Pool to
select a pool that exists on NetWorker server.
NetWorker provides a preconfigured Data Domain pool that you can select, named Data Domain Default.
d. Leave the Label and Mount device after creation option selected.
e. Click Next.
The following figure provides as example of the Configure Pool Information page.
11. On the Select Storage Nodes page, perform the following steps:
a. In the Storage Node Options section, specify the storage node that manages the device.
• To use an existing storage node on the NetWorker server, select Use an existing storage node.
Software Configuration 51
• To use a new storage node, select Create a new storage node, and then type the hostname of a storage node host.
If the new Storage Node is also a Dedicated Storage Node, select Dedicated Storage Node.
b. (Optional) To enable FC data transport for this device, perform the following steps:
• Select Enable Fibre Channel.
• In the Fibre Channel Host Name field, type the hostname that the Data Domain system uses to identify itself for FC
operations. By default, this hostname is the same name used for IP operations, but the hostnames can be different. The
hostname must match the Server Name displayed on the Data Domain system in the Data Management > DD Boost > Fibre
Channel tab of the Data Domain Enterprise Manager. The name is case-sensitive.
NOTE: All NetWorker clients that use an FC-enabled DD Boost device must be enabled for FC in the Data
Domain Interface field.
The following figure provides an example of the Select Storage Nodes page.
12. In the Select SNMP Monitoring Options page perform the following steps:
a. In the Data Domain SNMP Community String field, type the name of the SNMP community string.
52 Software Configuration
NOTE: If you do not know the name of the community, then clear the Gather Usage Information selection.
b. With the Receive SNMP trap events option selected, specify the SNMP Process port used by the Data Domain system and
select the events in which to monitor. Use the Reset to defaults option to reset the events in which to monitor back to the
default settings.
NOTE: The default SNMP process port is 162.
c. Click Next.
SNMP monitoring enables NMC to display the Data Domain system status and to list the backup and the recovery events. The
monitoring feature also provides a launcher link for the Data Domain interface. The following figure provides an example of the Select
SNMP Monitoring Options page.
13. On the Review the Device Configuration Settings page, review the configuration information and then click Configure.
NOTE: The name that is listed as the SU is really the pathname for the device folder. The format is: SU/
device_name, where SU is the short hostname of the NetWorker server.
The following figure provides an example of the Review the Device Configuration Settings page.
Software Configuration 53
Figure 17. Review the Device Configuration Settings page
NetWorker configures, mounts, and labels the DD Boost device for the specified pool.
14. On the Device Configuration Results page, review the information, and then click Finish.
The following figure provides an example of the Device Configuration Results page.
After the wizard successfully creates the device, the following changes appear in NMC:
• The Data Domain Systems window displays the new Data Domain device and the name of the volume. The following figure provides
an example of the Data Domain System window with the new Data Domain device.
54 Software Configuration
• If you configured a device for a Data Domain system that does not have previously configured NetWorker devices, NetWorker adds
the Data Domain system as a managed host. The NMC Enterprise window provides you details about the Data Domain system.
3. Provide the device name, device access information, username for the DD boost user (username filed) and password for the account .
These are mandatory attributes to create a device resource.
Device access information must be in the following form:
<DD IP>:<StorageUnitName>/<DeviceName> where Device Name refers to the subfolder to be created within the storage
unit.
NOTE:
• Device access information is parsed to get the storage unit and the device name.
• If device with Mtree exists, then the nsradmin command displays the error device already exist.
9. Click on the Select option which displays the types of resources available. Select the option NSR Device. It lists out all the devices
that has been created and is available. Browse through the list using Next and Previous, once you find the device that you want to
configure, click on the Edit option.
10. Selecting the pool in Volume Pool field. If you want to create a new Pool, select the pool using NSR Pool resource and select the
Create option. Once it is complete revert back to the current device Window (follow Step 9) and select the new pool that has just
been created.
Software Configuration 55
Figure 21. Configuring the media pool information
11. In order to configure the volume operations, enable the hidden attribute in Options section (If it is disabled).
12. Select options available in Volume operation field in order to label, mount and perform other volume operations on the device.
Operations have to be performed one at a time. Labeling and mounting of the device can also be performed by running the command.
nsrmm -s <server_name> -v -y -m -b <pool_name> -l -f <device_name>.
13. In order to permanently erase all data and remove media and index information erase volume operation has to be performed.
14. Select Delete from the menu to delete the device RAP resource. Delete operation would also need device to be unmounted and
removed as a target device from the corresponding NSR Pool resource.
NOTE: To use Data Domain with NetWorker, the NetWorker server hostname should be in lower case. Data Domain
functions with lowercase and DD Cloud tier operations fails if it is mixed case.
56 Software Configuration
2. On the taskbar, click the Enterprise icon .
3. In the navigation tree, highlight a host:
a. Right-click NetWorker.
b. Select Launch Application. The NetWorker Administration window appears.
4. On the taskbar, click the Devices button .
5. In the left navigation pane:
a. Right-click Data Domain Systems.
b. Select New Device Wizard.
NOTE: To modify completed wizard pages, click the links in the steps panel. The number of steps may vary according
to the type of configuration chosen.
6. In the Select the Device Type page, select the DD Cloud Tier device type, and then click Next.
The following figure provides an example of the Select the Device Type page.
7. In the DD Cloud Tier Configuration Options page, perform the following steps:
a. From the Select an existing Data Domain list, select the Data Domain host.
b. In the DD Boost Credentials section, type the username for the DD Boost user in the DD Boost Username field.
c. In the Secure Multi-Tenancy section, to use only DD Boost devices in secure Storage Units (SUs), select Configure Secure
Multi-Tenancy (SMT), and then perform one of the following tasks:
• To use an existing storage unit (SU), select Use an existing secure storage unit, and then select the SU.
• To create a SU, select Create a new secure storage unit, and then specify the name of the SU.
NOTE: SMT restricts access of each SU to one owner according to the provided DD Boost credentials.
d. In the Configuration Method field, select Browse and Select, and then click Next.
NOTE: If you do not configure the SMT option, the wizard will create an SU for you on the Data Domain system,
and name the SU after the shortname of the NetWorker server.
The following figure provides an example of the DD Cloud Tier Configuration Options page.
Software Configuration 57
Figure 25. DD Cloud Tier Configuration Options page
8. In the Select the Folders to use as DD Cloud Tier Device page, configure a device in the same mtree as the Data Domain backup
device:
a. Select the Data Domain system, and then click New Folder.
A new folder appears in the navigation tree. This folder is the new device.
NOTE: The navigation tree does not show the SU folder under the Data Domain system folder. However, the SU
folder is verifiable in the final Review Configurations Settings wizard page. The wizard names the SU folder after
the short hostname of the NetWorker server and places the devices that you create into this SU folder.
b. Type a name for the new folder, and then select the checkbox next to the folder or device name.
The Device table displays the full NetWorker device name, the storage pathname, and details about the device.
NOTE: The device name refers to the subfolder created within the SU. The folder path must not contain other
folders deeper than these device folders.
NOTE: Implicit in the SU folder pathname on the Data Domain system is the hidden mount point folders/data/
col1. Do not modify this folder structure, which all NetWorker server hosts use. The final wizard page, Review
Configurations Settings, shows the complete location.
The /backup folder stores NFS service data. The clients that are configured for NFS access can view, change,
and delete the /data/col1 directory that contains the DD Boost devices. If you use NFS devices, you can avoid
the risk of potential interference by using alternative path names.
d. Click Next.
The following figure provides an example of the Select the Folders to use as DD Cloud Tier Device page.
58 Software Configuration
Figure 26. Select the Folders to use as DD Cloud Tier Device page
9. In the Configure a Pool for the DD Cloud Tier Device page, perform the following steps:
a. Select Configure Media Pools for Devices.
b. In the Pool section, perform either of the following steps:
NOTE: The pool that you select or create must contain only Cloud Tier devices. NMC lists pools of the type
Backup Clone that contain only DD Cloud Tier devices.
c. Leave the Label and Mount device after creation option selected.
d. Click Next.
The following figure provides an example of theConfigure a Pool for the DD Cloud Tier Device page.
Software Configuration 59
Figure 27. Configure a Pool for the DD Cloud Tier Device page
10. In the Select the Storage Nodes for the DD Cloud Tier Device page, perform the following steps:
a. In the Storage Node Options section, select the storage node that manages the device.
• To use an existing storage node on the NetWorker server, select Use an existing storage node.
• To use a new storage node:
i. Select Create a new storage node.
ii. Type the hostname of a storage node host.
iii. If the new Storage Node is also a Dedicated Storage Node, select Dedicated Storage Node.
b. Click Next.
The following figure provides an example of the Select the Storage Nodes for the DD Cloud Tier Device page.
Figure 28. Select the Storage Nodes for the DD Cloud Tier Device page
11. In the Configure the Data Domain Management Policy page, perform the following steps:
60 Software Configuration
a. In the Data Domain Host field, specify the host name of the Data Domain system.
b. In the Admin User field, specify the username for a Data Domain user that has admin access. For example, sysadmin.
c. In the Admin Password field, specify the password of the management user.
d. In the Port field, specify the management port. By default, the port is 3009.
e. In the CA Certificate field, click Pull Certificate.
The Device wizard contacts the Data Domain system and displays the certificate in the Certificate field.
The Management Certificates window appears.
f. From the Select Certificate list, select the certificate.
g. In the Certificate Details field, review the certificate, and if the certificate is correct, click I Trust.
The CA Certificate field on the Configure the Data Domain Management Policy window displays the certificate.
h. In the Cloud Unit Name field, specify the name of the cloud unit that you created on the Data Domain system.
NOTE: To view a list of cloud units that are configured on a Data Domain system, from the Data Domain CLI, type
cloud unit list.
i. Click Next.
j. On the confirmation window, review the details, and then click OK.
The following figure provides an example of the Configure the Data Domain Management Policy page.
Software Configuration 61
Figure 30. Review the Device Configuration page
62 Software Configuration
a. Review whether the devices were successfully configured or if any messages appeared.
b. Click Finish.
c. To change any of the settings, click Back to the correct wizard page.
The Device Configuration wizard performs the following tasks:
• Deletes existing time-based policies on the Data Domain system.
• Creates the app-based policy on the Data Domain system during the device label operation.
• Creates the new NetWorker device for the DD Cloud Tier device.
The following figure provides a example of the Data Domain devices window with a DD Cloud Tier device.
f. In the Management Certificate field, paste the management certificate, from the Data Domain system.
g. Click OK.
NetWorker updates the Data Domain resource but does not validate the values with the Data Domain system to ensure accuracy.
2. In the left navigation pane, right-click Devices, and then and select New Device Properties.
3. On the General tab, identify the Cloud Tier device by typing its name and access information:
NOTE: Multiple devices can share a single volume. Configuring volume sharing on multiple devices provides details.
a. In the Name field, type a name for the Cloud Tier device.
For example:
ct_1
If you configure the device on a separate storage node host that is not the NetWorker server host, it is a remote device. Specify
the Name field in the following format:
Software Configuration 63
rd=remote_storagenode_hostname:device_name
For example:
rd=dzone1_sn2:ct_1
b. In the Device access information field, type the Data Domain hostname followed by a colon and the path to the device folder.
If you are configuring a device with secure multi-tenancy (SMT) protection, the device folder must reside in a password-protected
tenant unit on the Data Domain.
Use the following format:
DD_hostname:/DD_storage_unit_name/device_name
where, as a best practice, DD_storage_unit_name is the NetWorker server name, and device_name is a name for the device,
which appears as a folder.
For example, the following figure uses the following name:
ddr1:/dzone1/ct_1
NetWorker does not limit the number device folders that you can create, but the Device access information field accepts one
device folder only. Do not create any folders within a device folder.
NOTE: Implicit in this pathname is the hidden mount point folder /data/col1. Do not modify this folder
structure, which all NetWorker servers use.
Figure 33. Example of the General tab configuration properties for a Cloud Tier device
4. On the Configuration tab, in the Save Sessions area, in the Remote user and Password fields, type the DD Boost username and
password, respectively.
You can only define one DD Boost (OST) user. All NetWorker storage nodes and servers that access the Data Domain system must
use the same username and password.
64 Software Configuration
NOTE: Avoid changing the user of an existing device with a labeled volume. The new user will not have write
permission to the files and directories that are created by the previous user and cannot re-label the volume. Create a
device for the new user.
c. From the Label template list, select DD Cloud Tier Default Clone.
5. On the Selection Criteria tab, perform the following configuration tasks:
a. (Optional) To restrict the devices associated with the pool, from the Device box, select the Cloud Tier devices.
NOTE: Select devices that reside on the same mtree as the Data Domain devices that contain the source backup
data.
b. From the Media type required drop down, select DD Cloud Tier.
6. Click OK.
Software Configuration 65
Figure 34. Attributes to be configured for new data domain resource
Management User Username for a Data Domain user that has admin access. For
example, sysadmin
Cloud Unit Name Specify the name of the cloud unit that you created on the Data
Domain system
4. Select the Create option in the menu and select the type as NSR device. The following full screen appears with list of attributes to be
configured for new device resource.
66 Software Configuration
Figure 35. Attributes to be configured for new device resource
5. Provide Device name, Device access information, username for the DD boost user (username filed), and password for the account (all
four are mandatory attributes to create a device resource.)
Device access information must be of the following form:
<DD IP>:<StorageUnitName>/<DeviceName> where Device Name refers to the subfolder to be created within the storage
unit.
NOTE:
• Device access information is parsed to get the storage unit and the device name.
• If device with Mtree exists, then the nsradmin command displays the error device already exist.
9. Click on the Select option which displays the types of resources available. Select the option NSR Device. It lists out all the devices
that has been created and is available. Browse through the list using Next and Previous, once you find the device that you want to
configure, click on the Edit option.
10. Selecting the pool in Volume Pool field. If you want to create a new pool, select the pool using NSR Pool resource and select the
Create option. Once it is complete revert back to the current device Window (follow Step 9) and select the new pool that has just
been created.
11. In order to configure the volume operations, enable the hidden attribute in Options section (If it is disabled).
Software Configuration 67
Figure 37. Enabling hidden attribute
12. Select options available in Volume operation field in order to label, mount and perform other volume operations on the device.
Operations have to be performed one at a time. Labeling and mounting of the device can also be performed by running the command
nsrmm -s <server_name> -v -y -m -b <pool_name> -l -f <device_name>.
13. In order to permanently erase all data and remove media and index information erase volume operation has to be performed.
14. Select Delete from the menu to delete the device RAP resource. Delete operation would also need device to be unmounted and
removed as a target device from the corresponding NSR Pool resource.
NOTE: If you want to redirect existing client backups to new DD Boost devices, Redirecting backups from other devices
to DD Boost provides details.
The details for the settings referred to in this simplified wizard procedure are found in the next procedure Configuring a
backup client with NMC property windows.
1. Use NMC to connect to the NetWorker server, and then click Protection.
2. In the left navigation pane, right-click Clients and select Client Backup Configuration > New.
3. Complete the fields on the following wizard pages:
• Show the Client Name.
• Specify the Backup Configuration Type.
• Specify the Backup Options:
○ In the Deduplication settings, select Data Domain Backup, if applicable.
This setting ensures that the client backs up only to DD Boost devices if the pool used also contains other types of devices
such as AFTDs. It is best not to have mixed devices in pools.
○ Set Target Pool to a pool associated with DD Boost devices.
An alternative way to configure a client to use a pool is to specify the client or its group in the Data Source field of the Pool
resource. Creating pools to target DD Boost devices provides details.
68 Software Configuration
NOTE: Current versions of NetWorker application modules support backup to DD Boost devices. Some earlier
versions of modules do not support the client fields for Data Domain backup and Pool. In these cases, do not
set these fields. Backup fails for older NetWorker application modules on page 135 provides details.
• Select Files to Back Up.
• Select the Client Properties.
• Select the Backup Group.
• Specify the Storage Node Options.
4. Complete the wizard.
The NetWorker Administration Guide provides details on NetWorker Client resource configurations.
You can complete the following steps to configure a NetWorker client for scheduled backups to a DD Boost device.
1. Use NMC to connect to the NetWorker server and click Protection.
2. In the left navigation pane, select Clients:
• To create a Client resource, from the File menu, select New.
• To edit an existing Client resource, select the client name from the list in the right panel, and from the File menu, select
Properties.
a. On the General tab, in the Name field, type the hostname for the client and, optionally, type a comment in the Comment field.
b. Optional, select Block based backup.
c. In the Save Sets field, click the Browse button to open the Choose Directory window. Browse to and select the volumes or
individual file systems that you want to back up. When finished selecting, click OK.
Type each item on a separate line. For example:
E:\
F:\
To back up all client data, type All in the Save Sets field.
NOTE: For Microsoft Windows systems, back up the SYSTEM or Volume Shadow Copy Service (VSS) SYSTEM on
a periodic basis to prepare for disaster recovery of the client system.
3. On the General tab, in the Backup area, complete the following steps:
a. To enable deduplicated backup data from this client to bypass the NetWorker storage node and be sent directly to the Data
Domain system, select Client Direct. Review the following requirements:
• Ensure that you have not selected the Checkpoint restart field. If selected, backups revert to traditional storage node
backups.
• Ensure that the client interface configuration, whether FC or IP, matches the DD Boost device interface configuration. If the
interfaces do not match, then the storage node performs the backup and restore operations.
• Ensure that you have configured the Data Domain system to use the DD Boost devices. Configuring the Data Domain system
for DD Boost by using the CLI on page 40 provides details.
• Ensure that you have configured the NetWorker Device resource for the Data Domain system with a Remote User field that
specifies a DD Boost username. Configuring a DD Boost device manually on page 72 provides details.
NOTE: Client Direct access from a Linux host to a Data Domain system requires a glibc 2.3.4 or later library on
the Linux system.
b. (Optional) In the Protection group list field, select the group in which to add the Client resource. If you have not created the
protection group, you can create one later and add the client to the group.
4. On the Apps & Modules tab, perform the following tasks:
Software Configuration 69
a. In the Deduplication area, select Data Domain backup. This ensures that NetWorker backs up the client data only to DD Boost
devices, even if the selected pool contains DD Boost and other types of devices. It is best not to include different device types in a
single pool.
NOTE: Current versions of NetWorker application modules support backup to DD Boost devices. Some of the
earlier module versions do not support the client fields for Data Domain backup and Pool. In this case, do not set
these fields. Backup fails for older NetWorker application modules on page 135 provides details.
b. In the Data Domain Interface field, select the type of connectivity the client uses for DD Boost devices:
• Select IP for TCP/IP connectivity only.
Do not select IP if the Enable fibre channel attribute is enabled on the Configuration tab of the DD Boost Device resource.
This conflict in settings could cause backups to fail and restores to operate only through the storage node.
• Select Fibre Channel for FC connectivity only.
You cannot select the FC-only setting when you create a Client resource for the NetWorker server resource because the
NetWorker server requires IP connectivity to send control information to the hosts within the datazone.
• Select Fibre Channel for FC connectivity only.
You cannot select the FC-only setting when you create a Client resource for the NetWorker server resource because the
NetWorker server requires IP connectivity to send control information to the hosts within the datazone.
• To enable both FC and IP connectivity to the devices, select Any.
If the NetWorker server contains multiple definitions of this Client resource, any changes to this field propagate to the other
instances of the client.
c. To redirect an NDMP client from a tape backup to a DD Boost backup, change the Backup fields as follows:
i. Select the NDMP option.
ii. In the Backup Command field, type the following command:
nsrndmp -T backup_type -M
5. On the Globals (2 of 2) tab, in the Configuration area, configure the following settings:
a. In the Storage Nodes field, type the hostnames of the remote storage nodes that receive the client backup data.
b. In the Recover Storage Nodes field, type the hostnames of the storage nodes that you use to restore the client data.
c. (Optional), In the Backup target disks field, specify an ordered list of AFTD and Data Domain disk devices that will receive data
for this client. When you specify a value in this attribute, NetWorker ignores the values that you specify in the Storage nodes
attribute. This attribute does not apply to the client resource of the NetWorker server, and applies to each instance of the client
resource. You can specify devices that are local or remote to the NetWorker server.
6. When you have completed the client configuration, click OK.
The NetWorker server window shows a check mark in the Scheduled backup column of clients that are enabled for scheduled backup.
70 Software Configuration
Configuring DD Boost devices manually
Dell EMC recommends that you use the Device Configuration Wizard to manually add a Data Domain system to the NetWorker datazone.
and create DD Boost devices. You can modify the Device resource that the wizard creates to modify the devices, and perform the tasks in
the following sections.
b. Click Next.
5. In the Select Host Type page:
a. Select DataDomain.
b. Click Next.
6. In the Manage DataDomain page:
a. Review the configuration details.
b. Click Next.
c. Leave the Capture Events option selected.
7. (Optional) In the Configure SNMP Monitoring page, perform the following steps:
a. In the SNMP Community String field, type the name of the SNMP community string.
NOTE: If you do not know the name of the community, leave this field blank.
b. With the Receive SNMP trap events option selected, specify the SNMP Process port used by the Data Domain system and
select the events in which to monitor. Use the Reset to defaults option to reset the events in which to monitor back to the
default settings.
NOTE: The default SNMP process port is 162.
c. Click Next.
SNMP monitoring enables NMC to display the Data Domain system status and to list the backup and the recovery events. The
monitoring feature also provides a launcher link for the Data Domain interface.
8. Click Finish.
The Data Domain system or DDVE appears in the Enterprise window.
Software Configuration 71
• Type a value for the SNMP Process Port. By default, NMC uses the value that is configured on the Data Domain system with
the snmp add trap-hosthostname[:port] command. This configuration must agree with the firewall configuration on the
Data Domain system.
• Select the SNMP Traps that you want to monitor.
a. In the Name field, type a name for the Data Domain device.
For example:
dd_1
Configuring a DD Boost device manually on page 72 uses the following example values:
• NetWorker server short hostname = dzone1
• NetWorker remote storage node hostname = dzone1_sn2
• Data Domain hostname = ddr1
• DD Boost device name = dd_1
If you configure the device on a separate storage node host that is not the NetWorker server host as shown in Configuring a DD
Boost device manually on page 72, it is a remote device. Specify the Name field in the following format:
rd=remote_storagenode_hostname:device_name
For example:
rd=dzone1_sn2:dd_1
b. In the Device access information field, type the Data Domain hostname followed by a colon and the path to the device folder.
If you are configuring a device with secure multi-tenancy (SMT) protection, the device folder must reside in a password-protected
tenant unit on the Data Domain. Configuring the Data Domain system for DD Boost by using the CLI on page 40 provides details.
Use the following format:
DD_hostname:/DD_storage_unit_name/device_name
where, as a best practice, DD_storage_unit_name is the short hostname of the NetWorker server and device_name is a name for
the device, which appears as a folder.
For example, the following figure uses the following name:
ddr1:/dzone1/dd_1
NetWorker does not limit the number device folders that you can create, but the Device access information field accepts one
device folder only. Do not create any folders within a device folder.
NOTE: Implicit in this pathname is the hidden mount point folder /data/col1. Do not modify this folder
structure, which all NetWorker servers use.
72 Software Configuration
Figure 39. Example of the device name and the access information for a DD Boost device
c. In the Media type field, select Data Domain from the list.
5. On the Configuration tab, in the Save Sessions area, set the number of concurrent save sessions (streams) and the number of
nsrmmd (media storage) processes that the device can handle:
• In the Target sessions field, specify the number of save sessions that a nsrmmd process on the device handles before another
device on the Data Domain host takes the additional sessions. If another device is not available, then another nsrmmd process on
the same device takes the additional sessions. Use this setting to balance the sessions load among nsrmmd processes.
It is recommended that you set this field to a low value. The default value is 20. The maximum value is 60.
• In the Max sessions field, specify the maximum number of save sessions that the device can handle. At the maximum limit, if no
additional devices are available on the host, then another available Data Domain system takes the additional sessions. If no other
Data Domain hosts are available, then the system retries the save sessions until a nsrmmd process become available.
The default value is 60. The maximum value is 60.
NOTE: The Max sessions setting does not apply to concurrent recovery sessions.
• In the Max nsrmmd count field, specify the maximum number of nsrmmd processes that can run on the device. Use this setting
to balance the nsrmmd load among devices.
If you enabled Dynamic nsrmmds on the storage node, NetWorker automatically adjusts this value by using the formula max/
target +4, with the default value being 14. Otherwise, the default value is 4.
To modify this value, first adjust the two sessions fields, apply and monitor the effects, and then tweak the Max nsrmmd count
value.
NOTE: NetWorker reserves at least one nsrmmd process for restore and clone operations.
6. In the Remote user and Password fields, type the DD Boost username and password, respectively.
You can only define one DD Boost (OST) user. All NetWorker storage nodes and servers that access the Data Domain system must
use the same username and password.
NOTE: Avoid changing the user of an existing device with a labeled volume. The new user will not have write
permission to the files and directories that are created by the previous user and cannot re-label the volume. Create a
device for the new user.
7. If you want the DD Boost device to use FC connectivity, complete the following steps:
a. Select the Enable fibre channel field.
b. In the Fibre Channel Host Name field, type the hostname that the Data Domain system uses to identify itself for FC operations.
By default, this hostname is the same name used for IP operations, but the hostnames can be different. The hostname must match
the Server Name displayed on the Data Domain system in the Data Management > DD Boost > Fibre Channel tab of the Data
Domain Enterprise Manager. The name is case-sensitive.
NOTE: All NetWorker clients that use an FC-enabled DD Boost device must be enabled for FC in the Data Domain
Interface field.
8. If you want to enable DD Retention Lock on the Data Domain device, select Governance mode or Compliance mode from the DD
Retention Lock Mode drop-down. If you do not want to use DD Retention Lock on this device, select None.
Software Configuration 73
Figure 40. Data Domain Device Properties Configuration tab
9. If you want to enable Compliance mode on the device, manually enable compliance mode on the device Mtree before enabling it on
the NetWorker device.
10. To save the device settings click OK.
The NetWorker Administration window displays the Data Domain system and details of the device.
11. Ensure that the device is associated with a NetWorker storage volume before you try to use the device. Otherwise, an error appears.
Labeling and mounting devices on the storage node provides the procedure.
rd=dzone1_sn2:dd_1b
rd=dzone1_sn3:dd_1c
The Device access information field would specify the same single directory as a valid complete path for each alias.
For example, for a directory named dd_1 on the Data Domain storage host named ddr1, specify the correct pathname:
• If the storage node uses an automounter, you can specify the following pathname:
/net/ddr1/dzone1/dd_1
• If the storage node uses an explicit system mount point, you can specify one of the following pathnames:
/mnt/ddr1/dzone1/dd_1
/mnt/dzone1/dd_1
74 Software Configuration
Creating a volume label template for DD Boost devices
When you use the Device Configuration Wizard, the wizard automatically creates a label template for the volumes that a new device will
use.
NOTE: The Device Configuration Wizard automatically creates a label template for the volumes, and this procedure does
not apply if you use the wizard.
Each DD Boost device is associated with a single volume. The label template that is assigned to the pool determines the volume name.
NetWorker mounts each volume in a DD Boost device. A label template provides a DD Boost device with a volume name and numbering to
all storage volumes that belong to the same pool.
A label template defines the components of a volume label, which includes the volume name, a separator, and volume number. All the
volumes in the same pool will have the same label name, for example, dd_myvol, but different volume numbers, for example, .001.003.
For example, a Data Domain system may have three devices, each of which is mounted with a storage volume (Volume Name). If each
device/volume is associated with the same pool, the volume names would be as follows:
• dd_myvol.001
• dd_myvol.002
• dd_myvol.003
To create a label template, perform the following steps:
1. In the NetWorker Administration window, click Media.
2. In the browser tree, select Label Templates, and from the File menu, click New.
The Create Label Template window appears.
3. In the Name and Comment fields, type a name and description for the label template. The label will associate a storage pool to a
device.
4. In the Fields field, type the components of the label. Place each label component on a separate line. The template must include at
least one volume number range component. NetWorker applies the label template to the volumes mounted on DD Boost devices in a
Data Domain system.
For example:
dd_myvol
001-999
NOTE: Dynamic Drive sharing (DDS) is not supported for DD Boost devices.
Complete the following steps to manually create a pool for Data Domain backups:
1. Ensure that the devices that you assign to the pool were created in NetWorker.
2. Ensure that a label template has been created for the pool. Creating a volume label template for DD Boost devices on page 75
provides details.
3. From the NetWorker Administration window, click Media.
4. In the left navigation pane, select Media Pools, and from the File menu, select New to open the Create Media Pool window with
the Basic tab selected.
5. In the Name field, type a name for each pool. Create names that clearly indicate whether the pool is for a Data Domain backup or a
Data Domain clone operation.
For example:
Software Configuration 75
DDsite1
DDCLsite2
A pool name that starts with DD would be a Data Domain pool, and a pool name that starts with DDCL would be a Data Domain clone
pool. The pool name can also include the physical location where NetWorker stores the backup data. These conventions make the
name easier to use for scripting and reporting.
NOTE: You cannot modify the Pool type value after you create the device.
9. In the Label Template field, select a label template to associate with the pool.
You can later apply the pool to DD Boost devices. Labeling and mounting devices on the Data Domain device on page 76 provides
details.
10. On the Selection Criteria tab, under Target Devices, select all the DD Boost devices that this pool may use for storage. The pool
may store data on any of these devices. Use the following practices:
• Select only DD Boost devices for the pool. Do not mix DD Boost devices with other types of storage devices. If you modify a pool
in this step, ensure that the pool excludes all devices that are not DD Boost devices.
• Select only DD Boost devices that reside on the same Data Domain system. To add DD Boost devices that reside on other Data
Domain systems, first save the pool configuration, and then modify the pool and add the DD Boost devices.
• Do not select devices that reside on more than one Data Domain system. Backups from a single NetWorker client can target any of
these Data Domain systems. This behavior impairs the backup window and deduplication ratio.
NOTE: Backups from a single NetWorker client can target any of these Data Domain systems. This behavior impairs
the backup window and deduplication ratio.
11. Under Media type required, if you intend to use the pool for a Data Domain backup only, set this field to Data Domain. This setting
ensures that only Data Domain devices use this pool.
NOTE: It is recommended that you do not include different media types in a single pool. Backup fails for older
NetWorker application modules on page 135 provides further details.
76 Software Configuration
Converting a device to read-only
When you convert a DD Boost device to read-only mode, NetWorker cannot use of the device for backup operations. You can continue to
use the device for read operations (for example, restore operations) and as the read device for clone operations.
1. Use NMC to connect to the NetWorker server, and select the Devices view. In the navigation pane, select the Data Domain
Systems folder.
2. In the Devices table, right-click the device that you want to convert to read-only, and select Unmount.
3. Right-click this unmounted device, and select Modify Device Properties.
4. On the General tab, select Read Only, and click OK.
5. Right-click the device, and select Mount.
Disabling a device
When you disable a DD Boost device, NetWorker does not use the device for backup, recovery, or clone operations. You can reenable the
device to restore old data that is retained on the device.
1. Use NMC to connect to the NetWorker server, select the Devices view. In the left navigation pane, select the Data Domain
Systems folder.
2. In the Data Domain Systems table, right-click the device that you want to disable, and select Unmount.
3. Right-click the device, and select Enable/Disable.
4. Confirm that the Enabled column of the table contains No, which indicates that you have disabled the device.
Software Configuration 77
4
Data Protection Policies
This chapter includes the following topics:
Topics:
• Performing clone and replicate operations
• Overview of protection policies
• Default data protection policies in NMC's NetWorker Administration window
• Strategies for traditional backups
• Cloning with Data Domain (DD Boost)
• DD Boost clone and replication support
• Data Domain Automated Multi-streaming (AMS)
• Configuring the Data Domain CCR environment
• Strategies for cloning
• Clone reports
• Monitoring the status of Cloud Tier save sets
• Cloning with nsrclone
• Staging data from DD Cloud Tier devices
Policies
Policies provide you with a service-catalog approach to the configuration of a NetWorker datazone. Policies enable you to manage all data
protection tasks and the data protection lifecycle from a central location.
Policies provide an organizational container for the workflows, actions, and groups that support and define the backup, clone,
management, and system maintenance actions that you want to perform.
Workflows
The policy workflow defines a list of actions to perform sequentially or concurrently, a schedule window during which the workflow can
run, and the protection group to which the workflow applies. You can create a workflow when you create a new policy, or you can create
a workflow for an existing policy.
A workflow can be as simple as a single action that applies to a finite list of Client resources, or a complex chain of actions that apply to a
dynamically changing list of resources. In a workflow, some actions can be set to occur sequentially, and others can occur concurrently.
You can create multiple workflows in a single policy. However, each workflow can belong to only one policy. When you add multiple
workflows to the same policy, you can logically group data protection activities with similar service level provisions together, to provide
easier configuration, access, and task execution.
Actions
Actions are the key resources in a workflow for a data protection policy and define a specific task (for example, a backup or clone) that
occurs on the client resources in the group assigned to the workflow. NetWorker uses a work list to define the task. A work list is
composed of one or several work items. Work items include client resources, virtual machines, save sets, or tags. You can chain multiple
actions together to occur sequentially or concurrently in a workflow. All chained actions use the same work list.
When you configure an action, you define the days on which to perform the action, as well as other settings specific to the action. For
example, you can specify a destination pool, a retention period, and a target storage node for the backup action, which can differ from the
subsequent action that clones the data.
When you create an action for a policy that is associated with the virtual machine backup, you can select one of the following data
protection action types:
• Backup — Performs a backup of virtual machines in vCenter to a Data Domain system. You can only perform one VMware backup
action per workflow. The VMware backup action must occur before clone actions.
• Clone — Performs a clone of the VMware backup on a Data Domain system to any clone device that NetWorker supports (including
Data Domain system or tape targets). You can specify multiple clone actions. Clone actions must occur after the Backup action.
You can create multiple actions for a single workflow. However, each action applies to a single workflow and policy.
The following figure provides a high level overview of the components that make up a data protection policy in a datazone.
Gold policy
The Gold policy provides an example of a data protection policy for an environment that contains virtual machines and requires backup
data redundancy.
Silver policy
The Silver policy provides an example of a data protection policy for an environment that contains machines where file systems or
applications are running and requires backup data redundancy.
Bronze policy
The Bronze policy provides an example of a data protection policy for an environment that contains machines where file systems or
applications are running.
NOTE: For more information on configuring a new data protection policy using the NetWorker Management Web UI, see
the NetWorker Management Web User Interface Online Help.
Creating a policy
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Policies, and then select New.
The Create Policy dialog box appears.
3. On the General tab, in the Name field, type a name for the policy.
The maximum number of characters for the policy name is 64.
• Legal Characters: _ : - + = # , . % @
• Illegal Characters: /\*?[]()$!^;'"`~><&|{}
nsrlog -f policy_notifications.log
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
7. To specify the Restricted Data Zone (RDZ) for the policy, select the Restricted Data Zones tab, and then select the RDZ from the
list.
8. Click OK.
Create the workflows and actions for the policy.
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• For NetWorker Virtual Edition (NVE), to send an email notification, type the following command:
/usr/sbin/sendmail -v recipient_email "subject_text"
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
8. In the Running section, perform the following steps to specify when and how often the workflow runs:
a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, in the Enabled box, leave
the option selected. To prevent the actions in the workflow from running when the policy or workflow that contains the action
starts, clear this option.
b. To start the workflow at the time that is specified in the Start time attribute, on the days that are defined in the action resource,
in the AutoStart Enabled box, leave the option selected. To prevent the workflow from starting at the time that is specified in
the Start time attribute, clear this option.
c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.
The default value is 9:00 PM.
d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute
spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for
this attribute in order for incremental transaction log backup of SQL databases to occur.
The default Interval attribute value is 24 hours, or once a day. When you select a value that is less than 24 hours, the Interval
End attribute appears. To specify the last start time in a defined interval period, use the spin boxes.
e. To specify the duration of time in which NetWorker can manually or automatically restart a failed or canceled workflow, in the
Restart Window attribute, use the spin boxes.
If the restart window has elapsed, NetWorker considers the restart as a new run of the workflow. NetWorker calculates the
restart window from the start of the last incomplete workflow. The default value is 24 hours.
For example, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow
automatically starts every hour beginning at 7:00 PM. and the last start time is 11:00 PM.
4. From the Group Type list, leave the default selection of Clients.
5. In the Comment field, type a description of the group.
6. From the Policy-Workflow list, select the workflow that you want to assign the group to.
NOTE: You can also assign the group to a workflow when you create or edit a workflow.
7. (Optional) To specify the Restricted Datazone (RDZ) for the group, on the Restricted Datazones tab, select the RDZ from the list.
8. Click OK.
Create Client resources. Assign clients to a protection group, by using the Client Configuration wizard or the General tab on the Client
Properties page.
4. From the Group Type list, select Dynamic Clients. For steps 5 to 8, follow the instructions given in Creating a client group.
Probe
A probe action runs a user-defined script on a NetWorker client before the start of a backup. A user-defined script is any program that
passes a return code. If the return code is 0 (zero), then a client backup is required. If the return code is 1, then a client backup is not
required.
Only a backup action can follow a probe action.
Check connectivity
A check connectivity action tests the connectivity between the clients and the NetWorker server before the start of a probe or backup
action occurs. If the connectivity test fails, then the probe action and backup action does not start for the client.
Traditional backup
A traditional backup is a scheduled backup of the save sets defined for the Client resources in the assigned group. You must specify the
destination storage node, destination pool, the schedule (period and activity), and the retention period for the backup.
Clone
A clone action creates a copy of one or more save sets. Cloning enables secure offsite storage, the transfer of data from one location to
another, and the verification of backups.
You can configure a clone action to occur after a backup in a single workflow, or concurrently with a backup action in a single workflow.
You can use save set and query groups to define a specific list of save sets to clone, in a separate workflow.
NOTE: The clone action clones the scheduled backup save sets only, and it does not clone the manual backup save sets.
Some NetWorker module backups might appear to be scheduled backups that are initiated by a policy backup action,
but they are manual backups because they are initiated or converted by a database or application. The NetWorker
Module for Databases and Applications Administration Guide and the NetWorker Module for SAP Administration Guide
provides more details.
14. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is
implemented at an action level.
15. From the Failure Impact list, specify what to do when a job fails:
• To continue the workflow when there are job failures, select Continue.
• To abort the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow, select
Abort action.
NOTE: The Abort action option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types.
NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or cancelled.
NetWorker reports the workflow status as failed.
16. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0
(zero) indicates no amount of time.
17. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero)
indicates no amount of time.
18. (Optional) In Start Time specify the time to start the action.
Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:
• Disabled—Do not enforce an action start time. The action will start at the time defined by the workflow.
• Absolute—Start the action at the time specified by the values in the spin boxes.
• Relative—Start the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.
19. (Optional) Configure overrides for the task that is scheduled on a specific day.
To specify the month, use the navigation buttons and the month list box. To specify the year, use the spin boxes. You can set an
override in the following ways:
• Select the day in the calendar, which changes the action task for the specific day.
• Use the action task list to select the task, and then perform one of the following steps:
○ To define an override that occurs on a specific day of the week, every week, select Specified day, and then use the lists. Click
Add Rules based override.
○ To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules
based override.
NOTE:
14. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed probe or backup action. When the Retry Delay
value is 0, NetWorker retries the failed probe or backup action immediately.
NOTE: The Retry Delay option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types. When you specify a value for this option in other actions, NetWorker ignores the values.
15. In the Inactivity Timeout field, specify the maximum number of minutes that a job run by an action can try to respond to the server.
16. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is
implemented at an action level.
17. From the Failure Impact list, specify what to do when a job fails:
• To continue the workflow when there are job failures, select Continue.
• To abort the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow, select
Abort action.
NOTE: The Abort action option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types.
• To abort the entire workflow if there is a failure with one of the jobs in the action, select Abort workflow.
NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or cancelled.
NetWorker reports the workflow status as failed.
18. Do not change the default selections for the Notification group box. NetWorker does not support notifications for probe actions and
ignores and specified values.
19. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0
(zero) indicates no amount of time.
20. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero)
indicates no amount of time.
21. (Optional) In Start Time specify the time to start the action.
Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:
• Disabled—Do not enforce an action start time. The action will start at the time defined by the workflow.
• Absolute—Start the action at the time specified by the values in the spin boxes.
• Relative—Start the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.
22. (Optional) Configure overrides for the task that is scheduled on a specific day.
To specify the month, use the navigation buttons and the month list box. To specify the year, use the spin boxes. You can set an
override in the following ways:
• Select the day in the calendar, which changes the action task for the specific day.
• Use the action task list to select the task, and then perform one of the following steps:
○ To define an override that occurs on a specific day of the week, every week, select Specified day, and then use the lists. Click
Add Rules based override.
○ To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules
based override.
NOTE:
To perform the same type of backup on each day, select the backup type from the list and click Make All.
16. Select the Apply DD Retention Lock checkbox to enable retention lock for the save sets included in this backup action. Note that
the device used for backing up these save sets must also have DD Retention lock enabled in the Device Properties window or during
device creation.
17. In the DD Retention Lock Time box, specify the duration the save sets will remain on the Data Domain device before the retention
lock expires. During this time, these save sets cannot be overwritten, modified, or deleted for the duration of the retention period,
although the backups can be mounted and unmounted. The retention time period set here must fall within the minimum and maximum
values set for the Data Domain Mtree, and should be lower than or equal to the NetWorker Retention Period.
18. Click Next.
The Specify the Advanced Options page appears.
19. In the Retries field, specify the number of times that NetWorker should retry a failed probe or backup action, before NetWorker
considers the action as failed. When the Retries value is 0, NetWorker does not retry a failed probe or backup action.
NOTE: The Retries option applies to probe actions, and the backup actions for the Traditional and Snapshot action
types. If you specify a value for this option for other actions, NetWorker ignores the values.
20. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed probe or backup action. When the Retry Delay
value is 0, NetWorker retries the failed probe or backup action immediately.
NOTE: The Retry Delay option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types. When you specify a value for this option in other actions, NetWorker ignores the values.
21. In the Inactivity Timeout field, specify the maximum number of minutes that a job run by an action can try to respond to the server.
22. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is
implemented at an action level.
23. From the Failure Impact list, specify what to do when a job fails:
• To continue the workflow when there are job failures, select Continue.
• To abort the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow, select
Abort action.
NOTE: The Abort action option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types.
• To abort the entire workflow if there is a failure with one of the jobs in the action, select Abort workflow.
NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or cancelled.
NetWorker reports the workflow status as failed.
24. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0
(zero) indicates no amount of time.
25. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero)
indicates no amount of time.
26. Optional, in Start Time specify the time to start the action.
Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:
• Disabled—Do not enforce an action start time. The action will start at the time defined by the workflow.
• Absolute—Start the action at the time specified by the values in the spin boxes.
• Relative—Start the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.
27. (Optional) Configure overrides for the task that is scheduled on a specific day.
To specify the month, use the navigation buttons and the month list box. To specify the year, use the spin boxes. You can set an
override in the following ways:
• Select the day in the calendar, which changes the action task for the specific day.
• Use the action task list to select the task, and then perform one of the following steps:
○ To define an override that occurs on a specific day of the week, every week, select Specified day, and then use the lists. Click
Add Rules based override.
○ To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules
based override.
NOTE:
28. From the Send Notifications list box, select whether to send notifications for the action:
• To use the notification configuration that is defined in the Policy resource to send the notification, select Set at policy level.
• To send a notification on completion of the action, select On Completion.
• To send a notification only if the action fails to complete, select On Failure.
29. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears.
Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a
log file or you can send an email notification.
The default notification action is to send the information to the policy_notifications.log file. By default, the
policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows.
Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
c. In the Delete source save sets after clone completes box, select the option to instruct NetWorker to move the data from the
source volume to the destination volume after clone operation completes. This is equivalent to staging the save sets.
d. From the Destination pool list, select a clone pool.
To clone to a DD Cloud Tier device, select a Cloud Tier pool.
e. From the Retention list, specify the amount of time to retain the cloned save sets.
After the retention period expires, the save sets are marked as recyclable during an expiration server maintenance task.
12. Select the Apply DD Retention Lock checkbox to enable Retention Lock for the save sets included in this clone action. Note that
the device used for cloning these save sets must also have DD Retention lock enabled in the Device Properties window or during
device creation.
13. In the DD Retention Lock Time box, specify the duration the save sets will remain on the Data Domain device before the Retention
Lock expires. During this time, these save sets cannot be overwritten, modified, or deleted for the duration of the retention period,
although the device with the cloned backup can be mounted and unmounted. The retention time period set here must fall within the
minimum and maximum values set for the Data Domain Mtree, and should be lower than or equal to the NetWorker Retention Period.
14. In the Filters section, define the criteria that NetWorker uses to create the list of eligible save sets to clone. The eligible save sets
must match the requirements that are defined in each filter. NetWorker provides the following filter options:
a. Time filter—In the Time section, specify the time range in which NetWorker searches for eligible save sets to clone in the media
database. Use the spin boxes to specify the start time and the end time. The Time filter list includes the following options to define
how NetWorker determines save set eligibility, based on the time criteria:
•Do Not Filter—NetWorker inspects the save sets in the media database to create a clone save set list that meets the time
filter criteria.
• Accept—The clone save set list includes save sets that are saved within the time range and meet all the other defined filter
criteria.
• Reject—The clone save set list does not include save sets that are saved within the time range and meet all the other defined
filter criteria.
b. Save Set filter—In the Save Set section, specify whether to include or exclude ProtectPoint and Snapshot save sets, when
NetWorker searches for eligible save sets to clone in the media database. The Save Set filter list includes to the following options
define how NetWorker determines save set eligibility, based on the save set filter criteria:
• Do Not Filter—NetWorker inspects the save sets in the media database to create a clone save set list that meets the save
set filter criteria.
• Accept—The clone save set list includes eligible ProtectPoint save sets or Snapshot save sets, when you also enable the
ProtectPoint checkbox or Snapshot checkbox.
• Reject—The clone save set list does not include eligible ProtectPoint save sets and Snapshot save sets when you also enable
the ProtectPoint checkbox or Snapshot checkbox.
17. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is
implemented at an action level.
18. From the Failure Impact list, specify what to do when a job fails:
• To continue the workflow when there are job failures, select Continue.
• To abort the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow, select
Abort action.
NOTE: The Abort action option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types.
• To abort the entire workflow if there is a failure with one of the jobs in the action, select Abort workflow.
NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or cancelled.
NetWorker reports the workflow status as failed.
19. From the Send Notifications list box, select whether to send notifications for the action:
• To use the notification configuration that is defined in the Policy resource to send the notification, select Set at policy level.
• To send a notification on completion of the action, select On Completion.
• To send a notification only if the action fails to complete, select On Failure.
20. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears.
Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a
log file or you can send an email notification.
The default notification action is to send the information to the policy_notifications.log file. By default, the
policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows.
Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:
• To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• On Windows, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...
where:
21. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0
(zero) indicates no amount of time.
22. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero)
indicates no amount of time.
23. Optional, in Start Time specify the time to start the action.
Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:
• Disabled—Do not enforce an action start time. The action will start at the time defined by the workflow.
• Absolute—Start the action at the time specified by the values in the spin boxes.
• Relative—Start the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.
24. (Optional) Configure overrides for the task that is scheduled on a specific day.
To specify the month, use the navigation buttons and the month list box. To specify the year, use the spin boxes. You can set an
override in the following ways:
• Select the day in the calendar, which changes the action task for the specific day.
• Use the action task list to select the task, and then perform one of the following steps:
○ To define an override that occurs on a specific day of the week, every week, select Specified day, and then use the lists. Click
Add Rules based override.
○ To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules
based override.
NOTE:
The oval icon specifies the group to which the workflow applies. The rounded rectangle icons identify actions. The parallelogram icons
identify the destination pool for the action.
• You can adjust the display of the visual representation by right-clicking and selecting one of the following options:
○ Zoom In—Increase the size of the visual representation.
○ Zoom Out—Decrease the size of the visual representation.
○ Zoom Area—Limit the display to a single section of the visual representation.
Clone formats
Yo can clone data that is stored on a Data Domain device in one of two formats, which depend on the target media device:
• CCR format
• Regular clone format
Immediate cloning
NetWorker supports immediate cloning with CCR. Immediate cloning means that you can clone each save set when the backup completes
instead of waiting until the backup completes for all save sets in the action. Cloning operations can complete sooner because they can
now run in parallel instead of sequentially. Performance gains are most noticeable when there are many backup save sets in the backup
queue or when there are many save sets of different sizes.
You can set up immediate cloning by specifying the clone action as concurrent to the previous backup action in a policy workflow.
CCR requirements
Before you use CCR to clone data, ensure that following requirements are met.
1. Ensure that both the source and target storage nodes are clients of the same NetWorker server.
2. Ensure that the Data Domain systems are properly licensed, including a replication license, which is required to create optimized
clones.
Cloning by pools
To copy save sets from Data Domain storage to a Data Domain device, you must specify a pool. This pool is known as a "clone pool." A
clone pool must be assigned to a device on the target Data Domain system, where it will be available for use.
There are two main purposes for a clone pool:
• To copy existing deduplicated VTL or CIFS/NFS AFTD save sets to a Data Domain device.
• To copy the existing save sets from one Data Domain device to another Data Domain device, typically at a remote location for disaster
recovery purposes.
Clone formats
The type of NetWorker clone you produce depends on the type of storage media you use for the clone. NetWorker will use either CCR
when cloning to DD Boost devices or a normal clone when cloning to conventional storage media.
CCR format
When NetWorker clones data from a source DD Boost device to a target DD Boost device, usually at a geographically distant location, the
operation uses CCR, also known as optimized clone or DD format clone. CCR is a fast process that uses low bandwidth, multiple parallel
sessions, and low storage capacity. You can use CCR clones for data recovery or to create additional copies with minimal impact on the
primary operations of production, backup, or recovery.
CCR operations use only IP connectivity between DD Boost devices on separate Data Domain systems, whether you have configured the
participating devices for FC or IP.
NOTE: Do not use the Default Clone Pool. You cannot change the Media type required setting.
Complete the following steps to configure the network environment for CCR:
1. Ensure that you have enabled valid licenses to the Data Domain systems that you will use for CCR operations, including a Replication
license.
2. Ensure that the source and destination storage nodes are within the same datazone. A single NetWorker server must manage the
clone operations and maintain the retention policies for all cloned copies. The server also monitors and reports on the storage
operations.
3. Ensure Ethernet IP connectivity between the source and destination Data Domain systems. CCR occurs only over TCP/IP
connectivity. If a DD Boost device participating in the CCR also has an FC connection, ensure IP access to the DD Boost device.
4. Ensure that you map the Data Domain FC server name to the IP address, if the Domain FC and IP hostnames differ.
NOTE: Do not use connections with ifgroup links for clone operations.
Data Domain FC and IP hostnames are the same by default but they can be different. If they are different you must map the host Data
Domain FC server name to its own IP address as follows:
a. Open the Data Domain Enterprise Manager, and navigate to the Data Management > DD Boost. The Data Domain Server
Name appears on the Fibre Channel tab.
Alternatively, type the following command:
ddboost fc dfc-server-name show
b. Associate this server name to the IP address in the /etc/hosts file with the following command:
net hosts add fc_server_name IP_address
For example, if the Data Domain system has the IP address 10.99.99.99 and the IP hostname dd555-5.lss.mcm.com, and the DFC
server name is dd-tenendo, then type the following command:
net hosts add dd-tenendo 10.99.99.99
5. Mount the source DD Boost device on the source storage node.
6. Mount the target DD Boost device on the target storage node. The pool for the device must specify Backup Clone pool type.
7. Ensure that the target clone pool is properly specified for the clone method you use. Clone save sets will be written to this pool. You
may need to use multiple or mixed approaches for control and flexibility.
The following example use myccrpool as the name of a clone pool you created:
• For CLI clone operations, type the command nsrclone -b myccrpool.
ams_slice_size_factor 31 Allows you to change the slice size factor value. The slice size
factor corresponds to the size of the slices desired, specified by
a number of bits. For example, if the slice size factor is 28, the
ams_force_multithreaded No Force AMS to use threads even when the DDRs support multi-
file copies. Because the multi-file workflow is faster, this is only
useful for explicitly testing the multithreaded workflow. The
value can be Yes or No.
Debug 9
NOTE: The Backup Data Management chapter describes how you can clone save sets manually by using the nsrclone
command.
To specify the current date and time as the end date for the range, select Up to now.
Backup level In the Filter save sets by level section, next to the backup level for the save set, select the full
checkbox.
NOTE: Only the full backup level is applicable for network-attached storage (NAS)
devices.
Limit the number of clones Specify the number for the limit in the Limit number of clones list. The clone limit is the
maximum number of clone instances that can be created for the save set. By default, the value is
set to 1, and cannot be changed for NAS or Block.
NOTE: When this criteria is set to 1, which is the default value, you may experience
volume outage issues with Data Domain and advanced file type devices.
Client Next to one or more client resources that are associated with the save set in the Client list, select
the checkbox.
Policy Next to the policy used to generate the save set in the Policy list, select the checkbox.
Workflow Next to the workflow used to generate the save set in the Workflow list, select the checkbox.
Action Next to the action used to generate the save set in the Action list, select the checkbox.
Group Next to the group associated with the save set in the Group list, select the checkbox.
Pools Next to the media pool on which the save set is stored in the Pools list, select the checkbox.
NOTE: You cannot select Pools for NAS.
Name In the Filter save sets by name field, specify the name of the save set.
NOTE: You cannot use wildcards to specify the save set name.
If you specify multiple criteria, the save set must match all the criteria to belong to the group.
8. To specify the Restricted Data Zone (RDZ) for the group, select the Restricted Data Zones tab, and then select the RDZ from the
list.
9. Click OK.
Creating a policy
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Policies, and then select New.
The Create Policy dialog box appears.
3. On the General tab, in the Name field, type a name for the policy.
The maximum number of characters for the policy name is 64.
• Legal Characters: _ : - + = # , . % @
• Illegal Characters: /\*?[]()$!^;'"`~><&|{}
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• For NetWorker Virtual Edition (NVE), to send an email notification, type the following command:
/usr/sbin/sendmail -v recipient_email "subject_text"
• On Windows, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
7. To specify the Restricted Data Zone (RDZ) for the policy, select the Restricted Data Zones tab, and then select the RDZ from the
list.
8. Click OK.
Create the workflows and actions for the policy.
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• For NetWorker Virtual Edition (NVE), to send an email notification, type the following command:
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
8. In the Running section, perform the following steps to specify when and how often the workflow runs:
a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, in the Enabled box, leave
the option selected. To prevent the actions in the workflow from running when the policy or workflow that contains the action
starts, clear this option.
b. To start the workflow at the time that is specified in the Start time attribute, on the days that are defined in the action resource,
in the AutoStart Enabled box, leave the option selected. To prevent the workflow from starting at the time that is specified in
the Start time attribute, clear this option.
c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.
The default value is 9:00 PM.
d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute
spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for
this attribute in order for incremental transaction log backup of SQL databases to occur.
The default Interval attribute value is 24 hours, or once a day. When you select a value that is less than 24 hours, the Interval
End attribute appears. To specify the last start time in a defined interval period, use the spin boxes.
e. To specify the duration of time in which NetWorker can manually or automatically restart a failed or canceled workflow, in the
Restart Window attribute, use the spin boxes.
If the restart window has elapsed, NetWorker considers the restart as a new run of the workflow. NetWorker calculates the
restart window from the start of the last incomplete workflow. The default value is 24 hours.
For example, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow
automatically starts every hour beginning at 7:00 PM. and the last start time is 11:00 PM.
c. In the Delete source save sets after clone completes box, select the option to instruct NetWorker to move the data from the
source volume to the destination volume after clone operation completes. This is equivalent to staging the save sets.
d. From the Destination pool list, select a clone pool.
To clone to a DD Cloud Tier device, select a Cloud Tier pool.
e. From the Retention list, specify the amount of time to retain the cloned save sets.
After the retention period expires, the save sets are marked as recyclable during an expiration server maintenance task.
17. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is
implemented at an action level.
18. From the Failure Impact list, specify what to do when a job fails:
• To continue the workflow when there are job failures, select Continue.
• To abort the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow, select
Abort action.
NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or cancelled.
NetWorker reports the workflow status as failed.
19. From the Send Notifications list box, select whether to send notifications for the action:
• To use the notification configuration that is defined in the Policy resource to send the notification, select Set at policy level.
• To send a notification on completion of the action, select On Completion.
• To send a notification only if the action fails to complete, select On Failure.
20. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears.
Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a
log file or you can send an email notification.
The default notification action is to send the information to the policy_notifications.log file. By default, the
policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows.
Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:
• To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• On Windows, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
21. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0
(zero) indicates no amount of time.
22. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero)
indicates no amount of time.
23. Optional, in Start Time specify the time to start the action.
Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:
• Disabled—Do not enforce an action start time. The action will start at the time defined by the workflow.
• Absolute—Start the action at the time specified by the values in the spin boxes.
• Relative—Start the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.
24. (Optional) Configure overrides for the task that is scheduled on a specific day.
To specify the month, use the navigation buttons and the month list box. To specify the year, use the spin boxes. You can set an
override in the following ways:
• Select the day in the calendar, which changes the action task for the specific day.
• Use the action task list to select the task, and then perform one of the following steps:
○ To define an override that occurs on a specific day of the week, every week, select Specified day, and then use the lists. Click
Add Rules based override.
○ To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules
based override.
NOTE:
The oval icon specifies the group to which the workflow applies. The rounded rectangle icons identify actions. The parallelogram icons
identify the destination pool for the action.
You can work directly in the visual representation of a workflow to perform the following tasks:
• You can adjust the display of the visual representation by right-clicking and selecting one of the following options:
○ Zoom In—Increase the size of the visual representation.
○ Zoom Out—Decrease the size of the visual representation.
○ Zoom Area—Limit the display to a single section of the visual representation.
○ Fit Content—Fit the visual representation to the window area.
○ Reset—Reset the visual representation to the default settings.
○ Overview—View a separate dialog box with a high-level view of the visual representation and a legend of the icons.
• You can view and edit the properties for the group, action, or destination pool by right-clicking the icon for the item, and then select
Properties.
• You can create a group, action, or destination pool by right-clicking the icon for the item, and then select New.
Figure 49. Example of a policy with separate workflows for backup and cloning
NOTE: The amount of data and length of time that is required to complete the backup can impact the ability to clone
data when the backup and clone workflows are in the same policy. For example, if the clone action starts before the
backup action completes, there might not be any data yet to clone, or in other cases, only the save sets that completed
at the start time of the workflow is taken into account. In both cases, NetWorker marks the Clone Workflow as
successful, but there is no guarantee that all the data from the backup workflow was cloned.
To specify the current date and time as the end date for the range, select Up to now.
Backup level In the Filter save sets by level section, next to the backup level for the save set, select the full
checkbox.
NOTE: Only the full backup level is applicable for network-attached storage (NAS)
devices.
Limit the number of clones Specify the number for the limit in the Limit number of clones list. The clone limit is the
maximum number of clone instances that can be created for the save set. By default, the value is
set to 1, and cannot be changed for NAS or Block.
NOTE: When this criteria is set to 1, which is the default value, you may experience
volume outage issues with Data Domain and advanced file type devices.
Policy Next to the policy used to generate the save set in the Policy list, select the checkbox.
Workflow Next to the workflow used to generate the save set in the Workflow list, select the checkbox.
Action Next to the action used to generate the save set in the Action list, select the checkbox.
Group Next to the group associated with the save set in the Group list, select the checkbox.
Pools Next to the media pool on which the save set is stored in the Pools list, select the checkbox.
NOTE: You cannot select Pools for NAS.
Name In the Filter save sets by name field, specify the name of the save set.
NOTE: You cannot use wildcards to specify the save set name.
If you specify multiple criteria, the save set must match all the criteria to belong to the group.
8. To specify the Restricted Data Zone (RDZ) for the group, select the Restricted Data Zones tab, and then select the RDZ from the
list.
9. Click OK.
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
8. In the Running section, perform the following steps to specify when and how often the workflow runs:
a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, in the Enabled box, leave
the option selected. To prevent the actions in the workflow from running when the policy or workflow that contains the action
starts, clear this option.
b. To start the workflow at the time that is specified in the Start time attribute, on the days that are defined in the action resource,
in the AutoStart Enabled box, leave the option selected. To prevent the workflow from starting at the time that is specified in
the Start time attribute, clear this option.
c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.
The default value is 9:00 PM.
d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute
spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for
this attribute in order for incremental transaction log backup of SQL databases to occur.
The default Interval attribute value is 24 hours, or once a day. When you select a value that is less than 24 hours, the Interval
End attribute appears. To specify the last start time in a defined interval period, use the spin boxes.
e. To specify the duration of time in which NetWorker can manually or automatically restart a failed or canceled workflow, in the
Restart Window attribute, use the spin boxes.
If the restart window has elapsed, NetWorker considers the restart as a new run of the workflow. NetWorker calculates the
restart window from the start of the last incomplete workflow. The default value is 24 hours.
For example, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow
automatically starts every hour beginning at 7:00 PM. and the last start time is 11:00 PM.
9. In the Groups group box, specify the protection group to which the workflow applies.
To use a group, select a protection group from the Groups list. To create a protection group, click the + button that is located to the
right of the Groups list.
10. Click Add.
The Policy Action Wizard appears.
11. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
• Legal Characters: _ : - + = # , . % @
• Illegal Characters: /\*?[]()$!^;'"`~><&|{}
23. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is
implemented at an action level.
24. From the Failure Impact list, specify what to do when a job fails:
• To continue the workflow when there are job failures, select Continue.
• To abort the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow, select
Abort action.
NOTE: The Abort action option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types.
• To abort the entire workflow if there is a failure with one of the jobs in the action, select Abort workflow.
NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or cancelled.
NetWorker reports the workflow status as failed.
25. From the Send Notifications list box, select whether to send notifications for the action:
• To use the notification configuration that is defined in the Policy resource to send the notification, select Set at policy level.
• To send a notification on completion of the action, select On Completion.
• To send a notification only if the action fails to complete, select On Failure.
26. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears.
Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a
log file or you can send an email notification.
The default notification action is to send the information to the policy_notifications.log file. By default, the
policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows.
Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:
• To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:
nsrlog -f policy_notifications.log
• On Linux, to send an email notification, type the following command:
mail -s subject recipient
• On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header. Without this
option, the smtpmail program assumes that the message contains a correctly formatted email header and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.
○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are separated by a
space.
27. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0
(zero) indicates no amount of time.
Clone reports
You can use the NMC Reports view to access reports of NetWorker clone operations on a Data Domain system. Generating reports on
page 127 provides details.
The following figure provides an example of the mminfo output for a save set that resides on a Cloud Tier device and does not yet reside
in the public cloud.
NOTE: When RPS is enabled, each workflow reserves 30 sessions on a target DDBoost device
High water mark (%)—Defines the upper used disk space limit. When the percentage of used
disk space reaches the value that is defined in the High water
mark (%) attribute, NetWorker starts the stage operation to move save sets from the source disk.
Low water mark (%)—Defines the lower used disk space limit. When the
percentage of used disk space reaches the value that is defined in the Lower water mark (%)
attribute, NetWorker stops moving save
sets from the source disk.
NOTE: When staging and backup operations occur concurrently on the source disk
device, NetWorker does not accurately display the disk volume usage total in the
Written column in output of the mminfo -mv command or in the Used column on the
Media window of the NetWorker Administration application.
Save set selection Use this option to rank the order in which NetWorker stages the save sets, based on save set size
or age. Available values include:
• largest save set—Stage the save sets in order of largest save set size to smallest save set
size.
• oldest save set —Stage the save sets in order of oldest save set to most recent save set.
• smallest save set—Stage the save sets in order of smallest save set size to largest save set
size.
• youngest save set—Stage the save sets in order of most recent save set to least recent save
set.
Max storage period Use this option to start the stage operation based on the amount of time that a save set has
resided on the volume.
Max storage period unit
• Max storage period—Defines the number of hours or days that a save set can reside on a
volume before the stage process considers the save eligible to move to a different volume.
• Max storage period unit—Defines the unit of measurement for the value in the max storage
period attribute. Available values are Hours and Days.
The maximum storage period setting is used along with the file system check interval. Once the
maximum storage period is reached, staging does not begin until the next file system check.
Recover space interval Use this option to determine when the stage operation removes the successfully staged save set
from the source volume.
Recover space unit
• Recover space interval—Defines the frequency in which NetWorker starts of the recover
space operation, which removes successfully stage data from the source volume.
• Recover space unit—Defines the unit of measurement for the value in the recover space
interval attribute. Available values are Hours and Days.
File system check interval Use this option to define when NetWorker automatically starts the staging process.
• File System Check Interval—Defines the frequency in which NetWorker starts the staging
process. At every file system check interval, if either the high water mark or the maximum
storage period has been reached, then staging begins.
• File system check unit—Defines the unit of measurement for the value in the file system
check interval attribute. Available values are Hours and Days.
NOTE:
NOTE: Data Domain Boost Compressed restore is not supported for Vproxy restores.
Data Domain Compressed restore can be disabled by creating the file disable_compressed_restore at the /nsr/debug location.
3. Modify the Client resource for the client that will receive the restored data.
• Configure this client for Client Direct and IP connectivity.
• On the Globals (2 of 2) tab, in the Recovery storage nodes field, specify the storage node that you associated with the IP-
enabled DD Boost device.
NOTE: This option is now only available in the Diagnostic Mode view.
Disaster recovery
A disaster is defined as the loss of data where the computing environment required to restore that data is not available. Disaster recovery
is necessary when ordinary data recovery procedures are not sufficient to recover the computing environment and its data to normal day-
to-day operations.
Causes of disaster
A disaster can result from any of the following situations:
Potential losses
Disaster recovery of the primary site must cover the potential loss of one of more of the following systems at the primary site:
• The Data Domain server that stores the deduplicated client backups
• The NetWorker storage node that stores the deduplication metadata for the backups
• The NetWorker server that stores the metadata for the backups in the media database and client file indexes
○ The Devices area shows the following device and usage information:
▪ Pre-Compression—If the data had not been deduplicated and compressed, indicates the amount of space that the backup
would have used. NetWorker tracks this value as the size of backups.
▪ Compression (Reduction)—Represents the data compression with the pre-compression and post-compression used
values. Data compression is calculated with:
[(1 - Post-comp Used) ÷ Pre-Compression] x 100%
▪ /backup: post-comp—Indicates the total capacity of the Data Domain system, the amount of disk space already in use,
and the amount of space that is available.
▪ /ddvar—Indicates the amount of log file space that is in use on the Data Domain file system.
○ The Status area lists the connectivity usage.
○ The Log table shows a chronological list of events that occur during NetWorker server operations.
○ The Alerts table lists the messages for operational issues that can require administrative attention. Data Domain alerts are
available only if SNMP traps are configured.
NOTE: To delete individual messages from the Alerts table, open the NMC Events view, select the messages,
right-click, and select Dismiss.
NOTE: The same alert messages also appear in the NetWorker Alerts table.
4. On the Configure SNMP monitoring tab, type a value for SNMP Community String. The typical setting is public, which allows
all users to monitor events.
5. In the SNMP Process Port field, type a value for the port that the Data Domain system uses for SNMP traps. Firewall requirements
provides details.
6. In the SNMP Traps section, select the SNMP traps that you want to monitor. Some traps are pre-selected. The following figure
shows an example for Data Domain 5 alerts. Other versions might differ.
7. Click OK.
Generating reports
You can use the NetWorker Management Console (NMC) Reports view to create statistical reports of NetWorker with Data Domain
backup, recovery, and cloning activities.
Configuring a report
You can configure and display a Data Domain report for backup or clone activities in the NetWorker Management Console (NMC).
1. In the NetWorker Management Console window, click Reports.
2. Expand the Reports folder, expand the Legacy Reports folder, and then the Data Domain Statistics folder. Select the report that
you want to view.
NOTE: The types of reports include summary, statement, and details.
The Configure tab for the selected report type appears in the right panel.
3. In the Configure tab, configure the items that you want to include in the report. Select the item parameters and click the Remove,
Add, Remove All , or Add All buttons as required. The specific parameters that are available depend on the type of report that you
select.
If you do not specify Save Time values, the report displays all the available data. The following table lists details of report configuration
parameters.
Save Set Name Specifies one or more save sets. Values Selected save set names
are case-sensitive and you cannot use
wildcard characters.
NOTE: Monthly report does not
include the Save Set Name
parameter.
Save Time Limits the report to a specified time range. Save time (within a range)
Basic reports
A basic report displays statistics for a specific datazone component, a time span, or a field. You can view reports within the NetWorker
Management Console (NMC) Enterprise Reports window, and also modify the scope of a basic report by adjusting the parameters.
The following table describes the basic reports that are available for Data Domain statistics.
Save Set Summary For all or specified save sets, displays the following deduplication statistics:
• Amount of data—Amount of the data that NetWorker would have moved by using a
conventional backup.
• Target size—Size of the data after deduplication has taken place on the Data Domain
system.
• Deduplication ratio—Percentage of disk space that is saved by using deduplication.
• Number of save sets—Number of save sets in the backup.
• Number of files—Number of files in the save set.
Save Set Details Displays details about each save set, including backup duration and the following statistics:
• Server Name
• Save Set Name and ID
• DD Retention Lock Type
• DD Retention Locked Till
• Action Type
• Policy Name
• Workflow and Workflow Start Time
• Status
• Save Set size—Protected data size
• Target size—Size of the data after deduplication has taken place on the Data Domain
system (stored data size).
• Deduplication ratio—Percentage of savings by using deduplication.
• Number of files—Number of files in the save set.
Drill-down reports
A drill-down report consists of multiple basic reports, which are connected as layers and all configured with the same parameters that the
top layer uses.
You can run reports for groups, clients, or save sets. You can view reports within the NetWorker Management Console (NMC) Enterprise
Reports window, and also modify the scope of a report by adjusting the parameters.
The following table lists the drill-down reports that are available for Data Domain statistics.
Monthly Client Statement Reports backup statistics of individual clients 1. Client Summary
on a month-to-month and day-to-day basis, 2. Monthly Summary
down to individual save sets details.
3. Daily Summary
4. Save Set Details
Advanced reporting
The NetWorker Management Console (NMC) provides reports for only the recent backup history in a specific datazone. The optional Data
Protection Advisor (DPA) software can provide extended reports of backups, trends, and analysis for one or multiple datazones, including
reports of Data Domain systems. DPA is best for larger environments where you require additional analysis with forecasts and trends.
d. On the Configure Pool Information page, specify the media pool for the devices, and clear the Label and Mount selection. You
must manually mount the devices on the new storage node later in this procedure.
NOTE: If you enable Label and Mount at this point, NetWorker relabels the volume and you lose all the data. You
cannot undo this action.
e. On the Select the Storage Nodes page, select a storage node to handle the new devices by doing one of the following.
• Select an existing storage node.
• Create a replacement storage node.
• Use the NetWorker server’s storage node.
The storage node must be running on the correct network and its hostname must be resolvable by DNS.
Troubleshooting
The following sections will help you identify and resolve common issues of configuration and operation.
Support Bundles
The Data Domain system provides a mechanism to create a Support Bundle, which is a zipped file that contains a number of log files that
Support uses to troubleshoot issues.
You can create a Support Bundle by using Data Domain System Manager, or from the system console:
• Data Domain System Manager—Browse to Maintenance > Support > Support Bundles > Generate Support Bundle. To
download the bundle, click the GZ file, and then select Save.
• CLI—Log in to the Data Domain system console as the sysadmin user, and then type the following command:
support bundle create default
Core dumps
The Data Domain system generates core dump files that provide detailed information about process crashes.
To display a list of core dumps on the Data Domain system, log in to the Data Domain system console as the sysadmin user, and then type
the following command: support coredump list
NOTE: Each mtree can have only one data movement policy.
2. Determine when the status of the last data movement operation, by typing the following command:
data-movement status
3. Determine the data movement schedule, by typing the following command:
data-movement policy show
The following output displays the status of a data movement operation that successfully moves 4 files:
Data-movement: phase 1 of 3 (copying)
100% complete; time: phase 0:02:20, total 0:02:31
Copied (post-comp): None, (pre-comp): 6.63 KiB,
Files copied: 4, Files verified: 0, Files installed: 0
Data-movement: phase 2 of 3 (verifying)
100% complete; time: phase 0:00:02, total 0:02:41
Copied (post-comp): None, (pre-comp): 6.63 KiB,
Files copied: 4, Files verified: 0, Files installed: 0
Data-movement: phase 3 of 3 (installing files)
100% complete; time: phase 0:00:31, total 0:03:21
Copied (post-comp): None, (pre-comp): 6.63 KiB,
Files copied: 4, Files verified: 0, Files installed: 0
Data-movement was started on Nov 28 2016 15:08 and completed on Nov 28 2016 15:11
Copied (post-comp): None, (pre-comp): 6.63 KiB,
Files copied: 4, Files verified: 4, Files installed: 4
NOTE: If the data-movement watch command displays the following line: Files copied: 0, Files verified:
0, Files installed: 0., then the operation did not move any files. This can happen for one of the following
reasons:
• The DD Cloud Tier devices does not contain data that is eligible for movement. In this case, confirm that you
cloned data to the DD Cloud Tier device.
• Cloud connectivity issues or other issues exist.
6. Display system alerts that might indicate why a data movement operation failed to copy files, by typing the following command:
alert show current
To avoid this error, export the following environment variable on the client shell.
LDR_CNTRL=MAXDATA=0x70000000
3. Configure the Data Domain Interface field of the NetWorker clients for FC.
Configuring a backup client with NMC property windows provides details.
2. Configure the Data Domain system for use with NetWorker. Configuring the Data Domain system for DD Boost provides details.
c. Select or create a NetWorker storage node on which to label and mount the new devices.
d. Complete the wizard pages.
Configuring DD Boost devices with the NMC Device Configuration wizard on page 48 provides details.
5. Test the backup environment to ensure that the new configuration operates correctly and that existing backups, that will not use DD
Boost devices, continue to run as expected. For backups to new devices, test a restore from those devices.
6. Start the redirection with a full backup to the new devices. This practice avoids a dependency on the last full backup that is stored
with the legacy storage environment and the potential need to restore from two different environments.
7. Monitor backup performance, and adjust the backup schedule to optimize the configuration for maximum throughput or additional
clients. Monitoring Data Domain events, statistics, and logs on page 124 provides details.
3. Create a clone pool for the DD Boost devices to be used for the migration:
• In the Data Source field, select groups for the migration.
Typically, you migrate the same groups that you selected for the redirection of backups. Redirecting backups from other devices
to DD Boost on page 137 provides details.
• In the Target Devices field, select the DD Boost devices to store the migrated data.
Creating pools to target DD Boost devices on page 75 provides details.
4. Configure a clone task with the Write Clone Data to Pool field that is selected for the clone pool.
Road map for configuring a new cloning data protection policy on page 102 provides details about the scheduled clone option.
5. Run the clone action, either according to its schedule or by a manual start.
To manually start the clone action, right-click the workflow that contains the clone action, and select Start.
6. After the clone operation is completed, verify that the cloned data appears on the target devices.
DD Boost Conversion and Upgrade on page 137 provides details about the verification of NetWorker operations.
7. After you have verified the cloned save sets, remove the original save sets, as required.
8. If you remove the original save sets, remove unused devices and pools, as required. You cannot delete a pool until you delete or relabel
in other pools all the volumes that belong to that pool.
9. To ensure that adequate storage capacity is available, monitor the Data Domain system. Monitor a complete backup cycle of all clients,
including save set expirations.
DD Boost Conversion and Upgrade on page 137 provides details.
Migration scenarios
You can migrate existing backup data from legacy devices or file systems to DD Boost devices. The best scenario for your situation
depends on the storage environment configuration and the available capacities and bandwidth.
Figure 55. Migration from conventional storage to DD Boost devices on a different storage node
Figure 56. Migration from conventional storage to DD Boost devices on the same storage node
Figure 58. Migration from VTL to DD Boost devices on the same storage node