Académique Documents
Professionnel Documents
Culture Documents
Topic
DDOS 5.4 Installation Procedures
Selections
Data Domain model selection: DD2500
Disk Count in Head: 12 Disks
Shelf Type: ES30 Only
Shelf Count Range: 1 to 12 Shelves
Select shelf count: 2 Shelves
Networking Options: Port Bonding
Networking Options: Link Aggregation Control Protocol
Networking Options: Interface Failover
Networking Options: VLANs and VLAN Tagging - 802.1q
Networking Options: IP Aliasing
Networking Options: Dynamic DNS
System Management: ESRS management request
System Management: IPMI/SOL
System Management: SNMP
System Management: Mtree Quotas
Deployment method: Configuration tool
Associated site deployment: Yes
Protocol: Configure VTL
Protocol: Configure Replication
Security: Configure Certificates
Security: Configure Retention Lock
Security: Configure Encryption
Backup application links: Tivoli Storage Manager
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@emc.com
1 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
2 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Contents
Requirements, Documents & Tools .................................................................................. 9
Tools.............................................................................................................................................................. 9
Installation Toolkit .................................................................................................................................... 9
Utilities & Documents ............................................................................................................................... 9
Pre-Engagement Preparation Documents .................................................................................................. 10
Pre-Engagement Questionnaire (PEQ) ................................................................................................. 10
As-Built Configuration ............................................................................................................................ 10
VTL Qualifier & Compatibility Matrices .................................................................................................. 10
Post Engagement Processes & Documentation ......................................................................................... 11
The DD Fast Pass ....................................................................................................................................... 11
3 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Mtrees ................................................................................................................................ 35
View, Create or Delete Mtrees .................................................................................................................... 36
CLI Equivalent ................................................................................................................................ 36
Mtrees Quotas (Optional) ................................................................................................. 36
CLI Equivalent ................................................................................................................................ 37
Simple Network Management Protocol (SNMP) ............................................................. 37
CLI Commands ........................................................................................................................................... 37
SNMP Version 2 .................................................................................................................................... 37
SNMP Version 3 .................................................................................................................................... 38
Certificates and Certificate Authorities ........................................................................... 39
Supported formats ....................................................................................................................................... 39
Generating a CSR ....................................................................................................................................... 39
Import a Host Certificate ............................................................................................................................. 39
Import a CA Certificate ................................................................................................................................ 40
SCSITarget ........................................................................................................................ 40
Supported SCSI Target Architectures ......................................................................................................... 41
VTL plus Boost-FC from different initiators is OK. ................................................................................. 41
VTL plus Boost-FC from one initiator to two different DD systems is OK. ............................................ 41
4 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
VTL plus Boost-FC from one initiator to same DD systems is not allowed. .......................................... 42
VTL Configuration ............................................................................................................ 42
VTL Process ................................................................................................................................................ 43
Verify VTL License is Installed ............................................................................................................... 44
VTL Setup ................................................................................................................................................... 45
Login to the Enterprise Manager or the CLI ........................................................................................... 45
CLI Equivalent ................................................................................................................................ 45
Enable the SCSI Target Daemon (CLI Only) ......................................................................................... 46
CLI Equivalent ................................................................................................................................ 46
Enable the VTL Process ........................................................................................................................ 47
CLI Equivalent ................................................................................................................................ 47
Select your VTL Libraries....................................................................................................................... 48
Create a New VTL Library ..................................................................................................................... 49
CLI Equivalent ................................................................................................................................ 49
Create a New Tape Pool........................................................................................................................ 50
CLI Equivalent ................................................................................................................................ 50
Select the New Tape Pool ..................................................................................................................... 50
Create Tapes within the New Pool ........................................................................................................ 51
CLI Equivalent ................................................................................................................................ 51
Tape Barcodes ............................................................................................................................... 51
Tape Count & Size Determination ................................................................................................. 52
Return to Library and Import New Tapes ............................................................................................... 53
CLI Equivalent ................................................................................................................................ 53
Verify Proper Tapes Imported into Pool ................................................................................................. 54
CLI Equivalent ................................................................................................................................ 54
Verify Initiators are Present.................................................................................................................... 55
CLI Equivalent ................................................................................................................................ 55
Endpoints are Present and Enabled ...................................................................................................... 56
CLI Equivalent ................................................................................................................................ 56
Select Configure Initiator and Assign an Alias to the Initiator ................................................................ 57
CLI Equivalent ................................................................................................................................ 57
Select Access Groups ............................................................................................................................ 58
Create a New Access Group ................................................................................................................. 59
CLI Equivalent ................................................................................................................................ 59
Modify Access Group to Add additional Initiators (if Nessecary) ........................................................... 60
CLI Equivalent ................................................................................................................................ 60
Set In-Use Endpoints to Add LUNs to the New Access Group and Associate with Physical Ports for
Fabric Presentation ................................................................................................................................ 61
CLI Equivalent ................................................................................................................................ 61
5 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Verify Access Group is created with the Proper Initiators an LUNs ...................................................... 62
CLI Equivalent ................................................................................................................................ 62
Replication ........................................................................................................................ 63
Replication Methodologies and Types ........................................................................................................ 64
Replication Setup ........................................................................................................................................ 66
Login to the Enterprise Manager or the CLI ........................................................................................... 66
CLI Equivalent ................................................................................................................................ 66
Add the Target System into Enterprise Manager .................................................................................. 67
Select Replication .................................................................................................................................. 68
Create Replication Pair .......................................................................................................................... 69
Input Source and Target Mtrees (or other replication type) to Replicate ............................................... 70
CLI Equivalent ................................................................................................................................ 70
Initialize a Replication Context ............................................................................................................... 71
CLI Equivalent ................................................................................................................................ 71
Verify That the Context is Properly Configured ..................................................................................... 72
CLI Equivalent ................................................................................................................................ 72
Disabling a Replication Context ............................................................................................................. 73
CLI Equivalent ................................................................................................................................ 73
Resuming a Replication Context .................................................................................................... 74
CLI Equivalent ................................................................................................................................ 74
Removing a Replication Context ........................................................................................................... 75
CLI Equivalent ................................................................................................................................ 75
Modifying a Replication Context ............................................................................................................ 76
CLI Equivalent ................................................................................................................................ 76
Creation Recommendations (Mtree Replication) ........................................................................................ 76
Folder Creation Recommendations (Directory Replication) ....................................................................... 76
Encryption (In-Flight) ................................................................................................................................... 77
Encryption ......................................................................................................................... 79
Embedded Key Manager .................................................................................................. 79
Retention Lock .................................................................................................................. 80
Retention Lock Governance........................................................................................................................ 80
Retention Lock Compliance ........................................................................................................................ 80
CLI Commands \ Activities .......................................................................................................................... 80
6 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
7 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
8 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Tools
Installation Toolkit
Every Implementation Resource will need the following tools:
A Laptop capable of making serial connectivity and installed with the following:
A terminal program such as Putty (download the putty.exe or tar.gz from here) (the windows
executable is included in this PG zip)
A Browser
USB to DB-9 male serial cable or a DB-9 to Micro-DB-9 serial cable
A Screwdriver (provided with each head unit)
DB-9 female-to-female serial cable (provided with each head unit)
CAT 5/6 Ethernet cable, it is suggested the cable be at least 10 feet long as physical proximity to the
units may be limited.
USB stick of at least 1 GB capacity, 2GB or larger is recommended
9 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
As-Built Configuration
Every installation will require the completion of an as-built configuration. This guide will detail the
configuration and design parameters that were applied during on-site implementation work. The tool to
generate the as-built configuration is available here. Please select As-Built Configuration Generator to
download the program.
10 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
11 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note: All racks should be 4 post racks and dual power circuits are recommended for redundancy
Note: Amperage values have been calculated based upon voltage values of 120V and 230V and provide
approximate amperage requirements
For the official and most current power statistics on Data Domain models please see the Power
Calculator: http://powercalculator.emc.com/frmDataDomain.aspx?pagename=frmDataDomain
12 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
13 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
IMPORTANT: The DD2500 does not support ES20 shelves or SATA drives.
14 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
15 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
IMPORTANT: Do not mix ES20 and ES30 disk shelves on the same SAS chain (Physical Loop).
IMPORTANT: Do not mix ES30 SAS and ES30 SATA disk shelves on the same SAS chain (Physical
Loop).
IMPORTANT: Do not exceed the maximum number of shelves per physical loop.
16 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Core Configuration
End User License Agreement (EULA)
The first time a user logs into a DD system the End User License Agreement (EULA) will be displayed, its
acceptance is required. The EMC representative should not accept the agreement. The customer should
accept the agreement. If the customer is not present to accept the EULA, press Ctrl-C to exit from the
EULA accept screen and continue the installation. Instruct the customer to accept the EULA in the GUI
or enter system show eula in the CLI.
CLI Configuration
The Core configuration of a data domain is most easily accomplished using a script that runs from the
command line. The configuration script runs the first time a Data Domain Appliance (DD) is booted and
can be run as needed by entering the command:
# config setup
For each configuration section, you are prompted to answer a series of questions. Default values will be
contained in brackets immediately preceding a command. The script is divided into sections with each
section capable of being run independently of the previous sections. Follow these procedures:
Type y to configure a section.
Type n to skip a section and go to the next one.
Type a question mark (?) at a prompt to display more information.
Press either the Enter or Return key to accept the given value, such as [mail], or type a new value.
To make multiple entries in the list, separate each entry with either a comma or a space.
When prompted for a hostname, enter either its IP address or its fully qualified hostname, such as
srvr22.company.com.
All commands in the script are representative of an individual command that can be run from the
command line.
At the end of each section, a summary of your entries is displayed. You can accept or reject your
changes and go to the next section, or return to the beginning of that section and change any of the
settings. When you select Retry, you are shown your previous entries for each prompt.
To exit the CLI, you have to configure or skip each of the sections, or enter Ctrl+C.
2. [ ] Log into the Data Domain system CLI as user sysadmin. The default password is the serial
number from the rear panel of the Data Domain system.
From a serial console or keyboard and monitor, log in to the Data Domain system at the login
prompt.
From a remote machine over an Ethernet connection, give the following command (with the
hostname you chose for the Data Domain system) and then give the default password.
# ssh -l sysadmin host-name
.
17 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
3. [ ] The first prompt after initial login requests that you change the sysadmin password.
The prompt appears only once. You can change the sysadmin password later with the user change
password command. To improve security, Data Domain recommends that you change the 'sysadmin'
password before continuing with the system configuration.
Change the 'sysadmin' password at this time? (yes|no) [no]:
Note: Do not change the password during an install unless specifically directed by the customer to do so.
4. [ ] The Data Domain system command config setup automatically starts next.
The configuration utility has eight sections: Licenses, Network, System, Filesystem, CIFS, NFS,
DDBoost and VTL. You can configure or skip any section. The command line interface automatically
moves from one section to the next.
5. [ ] The first configuration section is for licensing. Licenses that you ordered with the Data Domain
system are already installed. At the first prompt, type yes to configure or view licenses.
Enter the license characters, including dashes, for each license category.
Make no entry and press the Enter key for categories that you have not licensed.
Licenses Configuration
Configure Licenses at this time (yes|no) [no]: y
License Code
Enter your license code
: WH3G-RRB2-T2VP-5H5Y-D58B-CSXJ-8W
Note: A summary of your licenses appears. You can accept the settings (Save), reject the settings
and go to the next section (Cancel), or return to the beginning of the current section and change
settings (Retry). A Retry shows your previous choice for each prompt. Press Enter to accept the
displayed value or enter a new value.
Note: The above license keys do not represent all possible keys on a system
6. [ ] The second section is for network configuration. At the first prompt, type yes to configure network
parameters.
NETWORK Configuration
Configure NETWORK parameters at this time (yes|no) [no]:
18 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note: If DHCP is disabled for all interfaces and then later enabled for one or more interfaces, the
Data Domain system must be rebooted.
The first prompt is for a Data Domain system machine name. Enter a fully-qualified name that
includes the domain name. For example: rstr01.yourcompany.com.
Hostname
Enter the hostname for this system (fully-qualified domain name)[]:
Supply a domain name, such as yourcompany.com, for use by Data Domain system utilities, or
accept the display of the domain name used in the hostname.
Domainname
Enter your DNS domainname []:
Configure each Ethernet interface that has an active Ethernet connection. You can accept or decline
DHCP for each interface. If the port does not use DHCP, enter the DNS information for that port.
If you enter yes for DHCP and DHCP is not yet available to the interface, the Data Domain system
attempts to configure the interface with DHCP until DHCP is available. Use the net show settings
command to display which interfaces are configured for DHCP.
If you are on an Ethernet interface and you choose not to use DHCP for the interface, the
connection is lost when you complete the configuration.
At the last prompt, entering Cancel deletes all new values and goes to the next section.
Each interface is either a 1Gbe or a 10Gbe connection. The same set of prompts appears for each
interface.
The DDOS 5.x naming port naming convention uses the following method:
For on-board NIC vertical interfaces, the top interface is named either eth0a or Ma (on the DD2500)
and further interfaces increment as follows, either eth0b, eth0c, etc or Mb, Mc, etc.
For on-board NIC horizontial interfaces the left interface as viewed from the rear, is named eth0a
and further interfaces increment as follows, eth0b, eth0c, etc.
For horizontially installed interface cards with more than two ports, the left interface as viewed from
the rear, is named ethxa and further interfaces increment as follows, ethxb, ethxc, etc and so on
until the bottom of the card (where x is the slot number).
For optional cards when installed vertically (in models prior to the 4200, 4500 and 7200), the top
interface at the top of the card is ethxa, the next is ethxb, and so on until the bottom of the card
(where x is the slot number).
For optional cards when installed vertically (in models 4200, 4500 and 7200), the bottom interface at
the bottom of the card is ethxa, the next is ethxb, and so on until the bottom of the card (where x is
the slot number).
For optional cards when installed horizontially, The first port on the card is always the port nearest
the top of the PCI card or SLic That port is ethxa, the next is ethxb, and so on until the edge of the
card is reached (where x is the slot number).
Ethernet port eth0a:
Enable Ethernet port (yes|no) [ ]:
Use DHCP on Ethernet port eth0a (yes|no) [ ]:
Enter the IP address for eth0a [ ]:
19 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
When not using DHCP on any Ethernet port, you must specify an IP address for a default routing
gateway.
Default Gateway
Enter the default gateway IP address[]:
When not using DHCP to acquire DNS servers enter up to three DNS servers for a Data Domain
system to use for resolving hostnames into IP addresses. Use a comma- separated or space-
separated list. Enter a space for no DNS servers. With no DNS servers, you can use the net hosts
commands to inform the Data Domain system of IP addresses for relevant hostnames.
DNS Servers
Enter the DNS Server list (zero, one, two or three IP addresses)[]:
a. A listing of your choices appears. You can accept the settings (Save), reject the settings and go to
the next section (Cancel), or return to the beginning of the current section and change settings
(Retry). A Retry shows your previous choice for each prompt. Press Return to accept the
displayed value or enter a new value.
Pending Network Settings.
Hostname east1dd510.datadomain.com
Domain name datadomain.com
Default Gateway 10.3.3.1
DNS Server List 192.168.244.214
10.24.58.11
10.24.58.31
Port Enabled Cable DHCP IP Address Netmask
---- ------- ----- ---- ---------- -------------
eth0a yes no no 172.16.1.2 255.255.255.0
eth0b yes no no 10.3.3.249 255.255.255.0
---- ------- ----- ---- ---------- -------------
*** No connection on configured Ethernet ports
Do you want to save these settings (Save|Cancel|Retry):
Note: An information box also appears in the display if any interface is set up to use DHCP, but does
not have a live Ethernet connection. After troubleshooting and completing the Ethernet connection,
wait for up to two minutes for the Data Domain system to update the interface. The Cable column of
the net show hardware command displays whether or not the Ethernet connection is live for each
interface.
7. [ ] The third section is for filesystem parameters. At the first prompt, enter yes to configure system
parameters
Filesystem Configuration
Configure Filesystem at this time (yes|no) [no]: yes
Note: The following message indicating a file system does not exists will only be present in a
dataless appliance. If the appliance has data bearing disks in the chassis a file system will already be
present.
Filesystem Status
20 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Filesystem Creation
There is no storage available for filesystem creation.
a. To add expansion shelves to the newly installed unit answer “yes” to the following question.
Configure storage at this time (yes|no) [yes]: yes
b. Repeat the following setups below until each enclosure has been added to the appliance.
Storage Configuration
Add/Remove Storage at this time (add|remove|skip) [add]:
Add Storage
Select Enclosure id you want to add (2|3|4|5|6|7) [2]:
Adding enclosure 2 to the active tier...done
Updating system information...done
c. Once you have added all of the expansion shelves “skip” adding any further shelves and continue
to the filesystem creation / expansion process
Storage Configuration
Add/Remove Storage at this time (add|remove|skip) [add]: s
Filesystem Creation
A filesystem of approximate size 20.96 TiB will be created.
Do you want to continue? (yes|no) [yes]: yes
Provisioning storage...
########################################### [5%]
########################################### [100%]
Initializing filesystem...
########################################### [5%]
########################################### [100%]
Note: These parameters should retain their default settings unless the engineer configuring the
appliance as has advanced knowledge of the implications.
21 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
8. [ ] The fourth section is for system parameters. At the first prompt, enter yes to configure system
parameters.
SYSTEM Configuration
Configure SYSTEM Parameters at this time (yes|no) [no]:
a. Add a client host from which you will administer the Data Domain system. The default NFS options
are: rw, no_root_squash, no_all_squash, and secure. You can later use the commands
adminaccess add and nfs add /ddvar to add other administrative hosts.
Admin host
Enter the administrative host []:
b. You can add an email address so that someone at your site receives email for system alerts and
autosupport reports. For example, jsmith@yourcompany.com. By default, the Data Domain
system email lists include an address for the Data Domain support group. You can later use the
Data Domain system commands alerts and autosupport to add more addresses.
Admin email
Enter an email address for alerts and support emails[]:
c. You can enter a location description for ease of identifying the physical machine. For example,
Bldg4-rack10. The alerts and autosupport reports display the location.
System Location
Enter a physical location, to better identify this system[]:
d. Enter the name of a local SMTP (mail) server for Data Domain system emails. If the server is an
Exchange server, be sure that SMTP is enabled.
SMTP Server
Enter the hostname of a mail server to relay email alerts[]:
e. The default time zone for each Data Domain system is the factory time zone. For a complete list of
time zones, see “Time Zones” in the Data Domain Administrators Guide.
Timezone Name
Enter your timezone name:[US/Pacific]:
Additional Configuration
f. To allow the Data Domain system to use one or more Network Time Service (NTP) servers, you
can enter IP addresses or server names. The default is to enable NTP and to use multicast.
Configure NTP
Enable Network Time Service? (yes|no)|? [yes]:
Use multicast for NTP? (yes|no|?) [no]:
Enter the NTP Server list [ ]:
22 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
g. A listing of your choices appears. Accept the settings (Save), reject the settings and go to the next
section (Cancel), or return to the beginning of the current section and change settings (Retry). A
Retry shows your previous choice for each prompt. Press Return to accept the displayed value or
enter a new value.
Pending system Settings
--------------- -----------------
Admin host pls@yourcompany.com
system Location Server Room 52327
SMTP Server mail.yourcompany.com
Timezone name US/Pacific
NTP Servers 123.456.789.33
--------------- --------------------
Do you want to save these settings (Save|Cancel|Retry):
h. Configure the backup servers. For the most up-to-date information about setting up backup
servers for use with a Data Domain system, go to the Data Domain Support web site
(https://my.datadomain.com). See the Documentation section.
VTL Configuration
CLI Continued
The eight section is for VTL (Virtual Tape Library) configuration. At the first prompt, enter yes to configure
VTL parameters.
VTL Configuration
Configure VTL at this time (yes|no) [no]: yes
Selet the appropriate library emulation, The library model is determined by the backup application that
must user the resource.
Note: At this time, another changer model is supported the i2000, to configure that model you must use
the native CLI commands or the GUI
Changer Model
Enter changer model (L180|RESTORER-L180|TS3500) [L180]: L180
Number of Slots
Enter number of slots(1-32000)
: 100
Number of CAPS
Enter number of caps(0-100)
: 1
23 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note: At this time, three other LTO drives are supported. To configure these drive emulations you must
use the native CLI commands or the GUI. The additional models are the HP-LTO-3, HP-LTO-4 and the
IBM-LTO-4
Drive Model
Enter drive model (IBM-LTO-1|IBM-LTO-2|IBM-LTO-3) [IBM-LTO-3]: IBM-LTO-3
Number of Drives
Enter number of drives(1-120)
: 2
Tape Capacity
Enter tape capacity(1-4000 GiB, enter '0' to derive from barcode)
: 0
Continue to add initiators until all appropriate initaitors are included in the access group.
Do you want to add initiators (yes/no)?
[no]: no
24 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Barcode A99000LA
Capacity 0 (if 0, will be derived from barcode)
Group name HolyHandGrenade
Initiators
------------------
pe2950_hba_zone_01
------------------
Do you want to save these settings (Save|Cancel|Retry): c
This may be the conclusion of the CLI Configuration script. If this is the first time this script has been run
when asked to reboot the machine answers “Yes”
25 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Capacity License
A capacity license can be entered at any time but must be entered before logical capacity can be
recognized on the appliance. To display the license(s) on an appliance type:
# license add AAAA-BBBB-CCCC-DDDD-EEEE-FFFFF-GGGGG
To enter a capacity license type:
# license show
Feature : CAPACITY-ACTIVE
-------------------------------------
## License Key Model Capacity*
--------------------------------------------------------------------------------
1 ABCD-12EF-HI92-IJ78-KL90-MN21-YZ ES20 5.6 TiB
2 BS48-DJZ9-M123-NJEE-GEEF-49TJ-BC ES20 5.6 TiB
3 U9AR-F9SZ-0NFR-8RDC-M5NA-UUV3-JM ES20 5.6 TiB
4 URA8-IMED-8UFS-JACK0-LIZ1-VER9-M1 ES20 5.6 TiB
--------------------------------------------------------------------------------
Licensed Active Tier Capacity: 22.4 TiB*
Feature : CAPACITY-ARCHIVE
----------------------------------------
## License Key Model Capacity*
--------------------------------------------------------------------------------
1 ABCD-EFGH-1234-5678-IJLK-9012-WY ES20 5.6 TiB
2 09YY-KE12-ABCD-9876-5599-TUVW-YY ES20 5.6 TiB
--------------------------------------------------------------------------------
Licensed Archive Tier Capacity: 11.2 TiB*
* Depending on the hardware platform, usable filesystem capacities may vary.
26 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CAUTION: When upgrading from a previous version of DDOS to 5.1 where an ES30 or “new” ES20
has been attached be aware a license will be asked for at the time of the upgrade. Have the
capacity license(s) ready to be entered immediately following the upgrade.
27 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
In this example, we will be adding a route to 172.28.0.207 and want traffic bound for that address to
egress out Ethernet interface 2 (or Eth3a on a DD880 using 4.9 or later).
In the GUI it will look will see the route table as:
To add a route where a host uses a specific interface use either of the following commands (please note
the hostname is resolved before being inserted into the routing table):
# route add 172.28.0.207 eth2
# route add -host dd560a-data.se.local eth2
Destination Gateway Genmask Flags Metric Ref Use Iface
172.28.0.207 0.0.0.0 255.255.255.255 UH 0 0 0 eth2
10.25.200.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0
172.28.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
172.28.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.25.200.1 0.0.0.0 UG 0 0 0 eth0
28 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
If traffic is directed at the appropriate subnet, it will egress the proper port. In addition, at this point set up
a replication context as appropriate by DNS hostname and the traffic should egress the proper interface.
29 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
To verify that an interface has a configured IPv6 address present, type the following command:
# net config eth4c
eth4c Link encap:Ethernet HWaddr 00:1B:21:BB:12:9A
inet6 addr: fe80::21b:21ff:febb:129a/64 Scope:Link
inet6 addr: 2001:cdba::3257:9653/0 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:808 (808.0 b) TX bytes:1386 (1.3 KiB)
Configuring Failover
The procedure for configuring a virtual interface from physical Ethernet interfaces follows.
1. [ ] Disable each of the Ethernet ports that is to be part of the virtual interface by entering this
command for each port:
# net disable ethx
2. [ ] To create a virtual interface, use the net create command and choose a virtual interface. For
example:
# net create virtual veth1
3. [ ] Assign a failover virtual interface named veth1; using two of the physical Ethernet ports ethxy.
30 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note: In the case of 1 Gb failover, one virtual interface can have more than two physical interfaces.
For example, to assign a virtual interface named veth1 using the physical interfaces eth3a and eth3b,
enter:
# net failover add veth1 interfaces eth3a eth3b primary eth3b
The hardware address and configured interfaces (eth2a, eth2b) for the interface named veth1 are
displayed.
5. [ ] (Optional) To add another physical interface, such as eth2a, to the virtual interface, enter:
# net failover add veth1 interfaces eth2a
Note: When creating VLAN interfaces on an aggregated interface, do not assign an IP address at this
time. Assign an IP address at the time of VLAN configuration.
Note: It is very important to select the proper load balancing algorithm as the differing options can
significantly affect data transfer rates and they by, performance.
The net aggregate command creates a virtual interface with the specified physical interfaces and uses
one of three aggregation modes. Select the mode that is compatible with the switch:
xor-L2
Xor Layer 2 transmits packets based on static balanced mode aggregation with an XOR hash of Layer 2
(inbound and outbound MAC addresses).
31 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
xor-L3L4
Xor Layer 3\4 transmits packets based on static balanced mode aggregation with an XOR hash of Layer
3 (inbound and outbound IP address) and Layer 4 (inbound and outbound port numbers).
7. [ ] Disable each of the interfaces that you plan to use as aggregation interfaces, such as eth2a and
eth3, by entering:
# net disable eth3a
# net disable eth3b
8. [ ] Enter:
# net aggregate add <virtual-ifname> mode {roundrobin | lacp hash {xor-L2 |xor-L2L3
| xorL3L4}interfaces physical-ifnamelist
For example, to create a virtual interface veth1 from the two physical interfaces eth3a and eth3b,
using the mode xor-L2, enter:
# net aggregate add veth1 mode lacp hash xor-L2 interfaces eth3a eth3b
Note: Optional command variables can be added to this command, as needed by network conditions,
those options are rate {fast / slow}, up / down {time}
The output displays the name of the virtual interface, its hardware address, aggregation mode, and
the ports that comprise the virtual interface.
Note: When creating VLAN interfaces on an aggregated interface, do not assign an IP address at this
time. Assign an IP address at the time of VLAN configuration.
where ifname is the name of the interface, which is veth1 in this example, and ipaddr is the interface’s
IP address.
32 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
The net aggregate command creates a virtual interface with the specified physical interfaces and uses
one of three aggregation modes. Select the mode that is compatible with the switch:
roundrobin
Roundrobin transmits packets, in sequential order from the first available link through the last, in the
aggregated group.
xor-L2
Xor Layer 2 transmits packets based on static balanced mode aggregation with an XOR hash of Layer 2
(inbound and outbound MAC addresses).
xor-L2L3
Xor Layer 2 transmits packets based on static balanced mode aggregation with an XOR hash of Layer 2
(inbound and outbound MAC addresses) and with an XOR hash of Layer 3 (inbound and outbound IP
address).
xor-L3L4
Xor Layer 3\4 transmits packets based on static balanced mode aggregation with an XOR hash of Layer
3 (inbound and outbound IP address) and Layer 4 (inbound and outbound port numbers).
1. [ ] Disable each of the interfaces that you plan to use as aggregation interfaces, such as eth3a and
eth3b, by entering:
# net disable eth3a
# net disable eth3b
2. [ ] Enter:
# net aggregate add <virtual-ifname> mode {roundrobin | balanced hash {xor-L2 |xor-
L2L3 | xorL3L4}interfaces physical-ifnamelist
For example, to create a virtual interface veth1 from the two physical interfaces eth3a and eth3b,
using the mode xor-L2, enter:
# net aggregate add veth1 mode xor-L2 interfaces eth3a eth3b
Note: Optional command variables can be added to this command, as needed by network conditions,
those options are rate {fast / slow}, up / down {time}
The output displays the name of the virtual interface, its hardware address, aggregation mode, and
the ports that comprise the virtual interface.
Note: When creating VLAN interfaces on an aggregated interface, do not assign an IP address at this
time. Assign an IP address at the time of VLAN configuration.
33 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
where ifname is the name of the interface, which is veth1 in this example, and ipaddr is the interface’s
IP address.
# net config veth1 192.168.2.78
interface TenGigabitEthernet1/5
switchport
switchport access vlan xyz
switchport mode access
channel-group 116 mode active
interface TenGigabitEthernet1/6
switchport
switchport access vlan xyz
switchport mode access
channel-group 116 mode active
The statement below displays the load-balancing algorithm on the switch; note the method must match
the load-balancing algorithm set on the Data Domain system.
router-xyz123#show etherchannel load-balance src-dst-port
1. [ ] Configure the switch port that connects to the interface to receive and send VLAN traffic from the
Data Domain interface. See the switch documentation for details on the configuration.
2. [ ] On the Data Domain system, enable the interface that you plan to use as the VLAN interface,
such as eth5b, by entering:
# net config eth5b up
3. [ ] Create the VLAN interface using either a physical port or a configured virtual port The range for
vlan-id is between 1 and 4098:
34 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
The abridged output above shows the name of the VLAN interface (eth5b.1), whether or not it is
enabled.
IP Aliasing
IP aliasing is a configuration option that allows you to put more than one address on a single interface.
Physical or Virtual interfaces can accept an IP alias.
To create an IP alias (where basename is the physical interface and alias in the number of the alias):
# net create interface <basename> alias <number>
To configure an IP alias:
# net config eth0b:59 192.168.5.97 netmask 255.255.255.252
To destroy an IP alias on a configured interface:
# net destroy eth0b:159
To add an IP alias to an already configured interface:
# net config <basename>
Mtrees
An Mtree is a logical division of the filesystem that deduplicates and isolates pre-compresssed data.
From a user point of view all data contained within an mtree is logically segregated into that mtree and
does not comingle with other data. When possible, Mtrees should be configured to align data sets with
common aging and retention policies. Multiple Mtrees can exist on a single Data Domain system. An
Mtree can be replicated to another Data Domain. From a customer data management perspective, the
Mtrees that are created should be functionally grouped to match data sets (ex. Oracle, Exchange
backups, SharePoint, etc), organizational (ex. The accounting backups, HR, etc) or by retention policy
(ex. The weekly backups, the monthly backups, etc). Mtree creation is dependant upon the customer
environment.
35 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
To list all Mtrees, enter the following command:
# mtree list
To create an Mtree enter the following command:
# mtree create /data/col1/<name of mtree to create>
To delete an Mtree, enter the following command:
# mtree delete /data/col1/<name of mtree to delete>
36 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
To enable quotas globally, enter the following command:
# quota status
Quota is enabled
To create both a hard and soft quota on an mtree enter, the following command:
# quota set mtrees /data/col1/centos5 soft-limit 10000 MiB hard-limit 100000 MiB
/data/col1/centos5: Quota soft limit: 10000 MiB, hard limit: 100000 MiB
CLI Commands
SNMP Version 2
In SNMP version 2 when a DataDomain system administrator created a user-defined SNMP community,
the community string would be shared with all users in a network. With SNMP version 2C supported the
administrator can specify that the community string is only returned after a request from particular hosts.
37 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
A community string is a value that is similar to a password and defines the community in which a device is
resident. A common value for the read-only string is “public” and a common value for the read-write string
is “private”.
To add a read-write community string, enter the following command:
# snmp add rw-community comm-string
# snmp add rw-community private
A trap host is the machine that will receive alerts from a client.
Note: Do not add a trap host within the Avamar GUI when integrating a Data Domain appliance with an
Avamar appliance as it will prevent communication between the two devices.
SNMP Version 3
The SNMP version 3 support provides a greater degree of security than 2C by replacing clear text
community strings as a means of authentication with user-based authentication using either MD5 or
SHA1. Also with SNMP V3, user authentication packets can be encrypted and their integrity verified with
either DES or AES.
38 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
A data domain system allows the import of certification authority (CA) and host certificates for
communicating with the RSA Key Manager/Data Protection Manager, and for the HTTPS service
accessing the DD embedded key manager.
Supported formats
PEM (Privacy Enhanced Mail) Host public key and CA certficiate
PKCS12 (encrypted file) Host certificate (public and private key), password is required to decrupt
PKCS10 used for Certificate signing request (CSR)
Note: All ceritificate management work must occur within the CLI
Generating a CSR
# adminaccess certificate generate cert-signing-request
Certificate signing request (CSR) successfully generated at
/ddvar/certificates/CertificateSigningRequest.csr
With following parameters:
Key Strength : 2048
Country : US
State : California
City : San Jose
Organization Name : My Company Ltd
Organization Unit :
Common Name : ddbeta234.rdc.com
39 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
This will execute the command to import the certificate on the destination DD system You will be
prompted with "Password:" after entering the command. This password is the login password for
"sysadmin" on the DD system where you are installing the certificate.
Import a CA Certificate
Importing a CA certificate is a little easier, as there is no certificate password:
# adminaccess certificate import ca ca_cert.pem
Enter password:
Host certificate imported.
You will be prompted with "Password:" after entering the command. This password is the login password
for "sysadmin" on the DD system where you are installing the certificate. There is no need (or command)
to process certificate files copied to the DD system using CIFS, NFS, FTP or any other file transfer
process.
Note: When enabling DDNS the default value is auto. This indicates all interfaces will receive DDNS
updates.
SCSITarget
Scsitarget is a unified management daemon for all SCSI services and transports. It supports both VTL
and Boost over Fibre Channel (Boost-FC). It supports anything that has a target LUN on the DD System.
40 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note: VTL and Boost-FC can run on the same system but they cannot share the same HBA ports.
Note: DDBoost can service both Fibre Channel and IP clients simultaneously however; both transports
cannot share the same initiator.
Note: Only one initiator should be present per access group. Each access group is assigned a type, (VTL
or DFC).
Client 1 VTL
DDR A
Client 2 DFC
VTL
Client 3 DDR B
DFC
VTL plus Boost-FC from one initiator to two different DD systems is OK.
A single initiator MAY access 2 DIFFERENT DDRs using any service
41 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
DDR A
VTL
Client
DFC
DDR B
VTL plus Boost-FC from one initiator to same DD systems is not allowed.
A single initiator may not access the same DDR through different services
VTL
Client 1 DDR A
DFC
VTL
Client 2 DDR B
DFC
VTL Configuration
Virtual Tape libraries can be setup via either the GUI or the CLI. The process for setting up a VTL is the
same in both the CLI and the GUI, however the specific actions will differ.
42 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
VTL Process
The following are steps required to set up a VTL within a Data Domain. The following list will show the
constituent elements of connecting to a customer fabric and configuring a VTL, keep in mind that some
elements of this list may be the responsibly of both the customer as well as the delivery resource (ex.
Zoning). This section of the PG will focus on item level 3 below, logical configuration. For application and
server specifics please find the integration documentation at Data Domain Support.
6. [ ] Physical installation
i. Connect Data Domain HBA(s) to fabric / storage ports
a. Zone ports presenting Data Domain and backup servers for initiator discovery.
a. Verify or Add VTL license to Data Domain (should be included as part of factory config)
b. Create VTL w / proper parameters
43 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
If the license is not present, each unit comes with documentation, a quick install card, which will show the
licenses that have been purchased. Enter the following command to populate the license key.
# license add license-code
44 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
VTL Setup
The following section details the steps to setting up a VTL. Steps for both the GUI setup and their
equivalent CLI commands are detailed below.
CLI Equivalent
login as: sysadmin
Data Domain OS 5.1.0.3-173058
Using keyboard-interactive authentication.
Password:
45 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# scsitarget enable
Please wait...
SCSI Target subsystem is enabled.
46 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl enable
Starting VTL, please wait...............
VTL is enabled.
Note: The enablement of the VTL process is what broadcasts the WWN of the Data Domain HBA to the
customer fabric. If forwarding plan is required in the form of change control processes this process
should be enabled to facilitate zoning.
47 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
48 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl add NewVTL model L180 slots 50 caps 5
VTL added. Use 'vtl show config NewVTL' to view it.
Drives the numbers of drives to be created will correspond to the number of data streams that will write
to a VTL.
Drive Model, the Data Domain emulates the IBM LTO-1 (default), IBM LTO-2, IBM LTO-3, IBM LTO-4 ,
HP LTO-3 and HP LTO-4 drives.
Number of Slots, the number of slots must be equal to or greater than the number of drives created.
To avoid reconfiguring the VTL, and since up to 64,000 slots can be created (total, not per VTL), to
ease management overhead, and if possible, create enough slots so that tapes can remain in the VTL
and will never have to be exported to a vault. The maximum number of slots in a VTL is 32,000. In
addition, since many applications are licensed by number of slots this factor should also be considered.
As an example, with a standard 100-GB cartridge on a DD580 you may configure 5000 slots. This
would be enough for them to hold up tp 500-TB (assuming reasonably compressible data).
Number CAPS, to determine the usage Cartridge access points refer to the documentation related to
the backup software utilizing the VTL.
Changer Model, the Data Domain emulates the StorageTek L180, the Restorer L180, The IBM TS
3500 and the ADIC i2000 tape libraries. The L180 is the default value. The VTL support matrix, which
can be found with this PG distribution, will detail the compatibility of emulated libraries to supported
software.
Note: Do not mix drive types (LTO-1, LTO, etc) or media types in the same library. Doing otherwise can
create unexpected results and/or errors in the backup operation.
Note: The IBM TS3500 drive emulation model should be used with IBMi deployments.
49 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl pool add VTL_Pool
VTL pool added.
50 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl tape add A00000L1 capacity 100 count 5 pool VTL_Pool
... added 5 tape(s)...
Tape Barcodes
The 8-character barcode must start with six numeric or upper-case alphabetic characters (from the set {0-
9, A-Z}) and end in a two-character tag for the supported LT0 tape type, where:
L1 represents a tape of 100 GiB capacity.
L2 represents a tape of 200 GiB capacity.
L3 represents a tape of 400 GiB capacity.
LA represents a tape of 50 GiB capacity,
LB represents a tape of 30 GiB capacity,
LC represents a tape of 10 GiB capacity.
These capacities (L1, LA, LB, LC is LTO-1; L2 is LTO-2; and L3 is LTO-3) are the default sizes used if the
capacity option is not included when creating the tape cartridge. If capacity is included, then it overrides
the two-character tag. The numeric characters immediately to the left of L set the number for the first
tape created.
For example, a barcode of ABC100L1 starts numbering the tapes at 100.
A few representative sample barcodes:
000000L1 creates tapes of 100 GiB capacity and can accept a count of up to 1,000,000 tapes (from
000000 to 999999).
AA0000LA creates tapes of 50 GiB capacity and can accept a count of up to 10,000 tapes (from 0000
to 9999).
51 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
AAAA00LB creates tapes of 30 GiB capacity and can accept a count of up to 100 tapes (from 00 to 99).
Working with Tapes
AAAAAALC creates one tape of 10 GiB capacity. You can only create one tape with this name and not
increment.
AAA350L1 creates tapes of 100 GiB capacity and can accept a count of up to 650 tapes (from 350 to
999).
000AAALA creates one tape of 50 GiB capacity. You can only create one tape with this name and not
increment.
5M7Q3KLB creates one tape of 30 GiB capacity. You can only create one tape with this name and not
increment.
To make use of automatic incrementing of the barcode when creating more than one tape, Data Domain
starts at the sixth character position, just before L. If this is a digit, then it increments it, if an overflow
occurs, 9 to 0, and then it moves one position to the left. If it is a digit, then it is incremented. If the sixth
character is alphabetic, it stops. Data Domain recommends creating tapes with unique bar codes only.
Duplicate bar codes in the same tape pool create an error. Although no error is created for duplicate bar
codes in different pools, duplicate bar codes may cause unpredictable behavior in backup applications.
Note: These are general guidelines that may not accurately represent the environment
52 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Select the location and pool where the tapes will come from
Select the tapes that you need to import and the left hand side of the screen checkboxes
Select the destinations at the bottom of the screen
Click Submit at the verification screen to import the tapes
CLI Equivalent
# vtl tape show pool VTL_Pool
Processing tapes....
Barcode Pool Location State Size Used (%) Comp ModTime
-------- -------- -------- ----- ------- -------- ---- ------------------
A00000L3 VTL_Pool vault RW 100 GiB 0.0 GiB ( 0.00%) 0x 2010/07/16 09:50:41
A00001L3 VTL_Pool vault RW 100 GiB 0.0 GiB ( 0.00%) 0x 2010/07/16 09:50:41
A00002L3 VTL_Pool vault RW 100 GiB 0.0 GiB ( 0.00%) 0x 2010/07/16 09:50:41
A00003L3 VTL_Pool vault RW 100 GiB 0.0 GiB ( 0.00%) 0x 2010/07/16 09:50:41
A00004L3 VTL_Pool vault RW 100 GiB 0.0 GiB ( 0.00%) 0x 2010/07/16 09:50:41
-------- -------- -------- ----- ------- -------- ---- ------------------
VTL Tape Summary
----------------
Total number of tapes: 5
Total pools: 1
Total size of tapes: 500 GiB
Total space used by tapes: 0.0 GiB
Average Compression: 0.0x
53 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl tape show pool VTL_Pool
Processing tapes....
54 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl initiator show
Initiator Group Status WWNN WWPN Port
--------- --------- ------ ----------------------- ----------------------- ----
tsm6_p1 tsm3500_a Online 20:00:00:24:ff:31:ce:f8 21:00:00:24:ff:31:ce:f8 10b
--------- --------- ------ ----------------------- ----------------------- ----
Initiator Symbolic Port Name Address Method
----------- ------------------------------------------- --------------
tsm6_p1 QLE2562 FW:v5.06.03 DVR:v8.03.07.15.05.09-k auto
----------- ------------------------------------------- --------------
55 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl port show summary
Port Connection Link Port Enabled Status
Type Speed ID
---- ---------- ------ ---- ------- -------
6a Loop 4 Gbps e8 Yes Online
6b N-Port Yes Offline
---- ---------- ------ ---- ------- -------
56 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl initiator set alias NewAliasName wwpn 21:00:00:e0:8b:9d:0b:e8
# vtl initiator show
Initiator Group Status WWNN WWPN
Port
--------- ------- ------- ----------------------- ----------------------- ---
NewVTL aussie1 Online 20:00:00:e0:8b:9d:0b:e8 21:00:00:e0:8b:9d:0b:e8 6a
Offline 20:00:00:e0:8b:9d:0b:e8 21:00:00:e0:8b:9d:0b:e8 6b
--------- ------- ------- ----------------------- ----------------------- ---
Initiator Symbolic Port Name Address Method
--------- ------------------ --------------
NewVTL auto
--------- ------------------ --------------
It is strongly recommended that Initiator aliases be set to reduce confusion and human error during the
configuration process.
Note: As of DDOS 5.3, default inititator names will be assigned both when a new installation is performed
and when an upgrade is performed on a unit with existing initiators present. …
57 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
58 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl group create VTL_Group
Note: Create a new access group and do not use the default Tape Server Access group unless using the
NDMPd service.
59 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl group add VTL_Group initiator Initiator_Name
60 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Set In-Use Endpoints to Add LUNs to the New Access Group and Associate with Physical
Ports for Fabric Presentation
CLI Equivalent
# vtl group add VTL_Group vtl NewVTL changer lun 0 primary-port all
secondary-port all
# vtl group add VTL_Group vtl NewVTL drive 1 lun 1 primary-port all
secondary-port all
# vtl group add SetUp_Test vtl SetUp_Test drive 3 lun 3 primary-port
endpoint-fc-0 secondary-port endpoint-fc-1
When presenting LUNs via attached FC ports on VTL cards, ports can be designated as primary,
secondary or none. A Primary port for a set of LUNs is the port that is currently advertizing those LUNs to
a fabric. A secondary port is a port that will broadcast a set of LUNs in the event of primary path failure
(this requires manual intervention). A setting of none is used in the case where you do not wish to
advertize selected LUNs. The presentation of LUNs is dependant upon the SAN topology in question.
61 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# vtl group show Setup_Test
Group: SetUp_Test
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
tsm6_p23 21:00:00:24:ff:31:ce:f8
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
------------------ --- ------------- --------------- -------------
SetUp_Test changer 0 all all all
SetUp_Test drive 1 1 all all all
SetUp_Test drive 2 2 5a 5b 5a
SetUp_Test drive 3 3 endpoint-fc-0 endpoint-fc-1 endpoint-fc-0
------------------ --- ------------- --------------- -------------
62 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Replication
The Data Domain appliance can be set up for directory, collection or Mtree based replication.
Note: Media pools are replicated by Mtree as a default. A media pool can be created in backwards
compatibility mode and can then be replicated via directory-based replication. You cannot use the pool://
syntax to create replication contexts using the command line. When specifying pool based replication in
the GUI either directory or Mtree based replication will be created, based upon the media pool type.
Directory replication provides replication at the level of individual directories. Mtree based replication
replicates entire mtrees (i.e. virtual file structure that enables advanced management). Media pools can
also be replicated, and by default, in DDOS 5.3 an Mtree is created that will be replicated. A media pool
can also be created in backwards compatibility mode which, when replicated, will be a directory based
replication context.
Each replication type establishes a “context” associated with an existing directory or Mtree on a source
unit. The replicated context is created on the target unit when a context is established. The context
establishes a replication pair, is always active and any data landing in the source location will be copied
to the target location at the earliest opportunity. Replicating VTL tape cartridges (or pools) simply means
replicating mtrees or directories that contain VTL tape cartridges. Collection replication duplicates the
entire data store on an appliance and transfers that to the remote appliance, the replicated volume is
read-only.
Each Data Domain system can be the source and \ or the destination for replication contexts. During
replication, each Data Domain system can perform normal backup and restore operations.
With all replication:
A destination Data Domain system must have available storage capacity that is at least the size of the
expected maximum size of the source directory. Be sure that the destination Data Domain system has
enough network bandwidth and disk space to handle all traffic from replication sources.
The Data Domain appliance file system must be enabled or, based upon the replication type, will be
enabled as part of the replication initiliazation.
The source must exist
The target location must not exist
The target destination will be created when a context is built and initialized
After replication is initialized, ownership and permissions of the destination are always identical to
those of the source.
In the replication command options, a specific replication pair is always identified by the destination.
Both systems must have an active, visible route through the IP network so that each appliance can
resolve its partner’s hostname.
With Directory:
Do not mix CIFS and NFS data within the same directory. A single destination Data Domain system
can receive backups from both CIFS clients and NFS clients as long as separate directories are used
for CIFS and NFS.
Any directory can be in only one context at a time. A parent directory may not be used in a replication
context if a child directory of that parent is already being replicated.
Directory based replication only functions within the /data/col1/backup default Mtree
63 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
With Collection:
No granular replication control is possible. All data is copied from source to destination producing a
read only copy on the target appliance.
The target file system must be disabled prior to creating the replication context
Configuration information is not created at the destination, only data is copied to the destination
With Mtree:
Mtree destination contexts will be created as read-only mtrees
Snapshots must be created on source contexts
Snapshot cannot be created on a replication target
Snapshots are replicated with a fixed retention of one year however, the retention is adjustable on the
target appliance and must be adjusted there
Archive data movement policies cannot be run on a destination replica mtree
Replication contexts must be configured on both the target and the source unit.
Note: When replicating with DDBoost replication contexts need not be configured. The Lifecycle polices
control replication of information with no intervention from the user. DDBoost will build and tear down
contexts as needed on the fly.
Note: Paths configured in replication contexts are absolute references and do not change based upon the
unit in which they are configured.
Note: Archive teir data can now be replicated from extended retention to extended retention systems
Note: The default behavior of replicaition includes the propagation of retention lock. This behavior can be
altered per replication context. If retention lock is licensed on a source appliance, the target appliance
must also have a retention lock license applied or replication will fail. This behavior can be disabled or
modified by disabling propagate retention lock.
Note: If retention lock is enabled on an replicaition context a repliciated target context will always contain
data that is retention locked.
64 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Mixed Topologies
SN Dir -> Ex Mtree -> Ex Mtree SN Dir -> Ex Col -> Ex Col
SN Mtree -> SN Col -> SN Col SN Mtree -> Ex Col -> Ex Col
Note: Single node-to-Single node replication (SN->SN) works on all replication types
Note: Extended Retention archive data cannot be the source for directory replication
Note: Collection replication cannot be configured from either Single node to an Extended Retention nor
from Extended Retention to a single node
65 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Replication Setup
The following section details the steps to set up replication.
CLI Equivalent
login as: sysadmin
Data Domain OS 4.9.0.3-173058
Using keyboard-interactive authentication.
Password:
66 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
In the top left portion of the Enterprise Manager, press the Add button. Enter credentials for the target
system to add the system to Enterprise Manager.
67 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Select Replication
68 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Click the Create Pair button and the following box will be displayed
69 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Input Source and Target Mtrees (or other replication type) to Replicate
CLI Equivalent
# replication add source dir://ddsource.test.com/data/col1/directorytorep
destination dir://ddtarget.test.com/backup/directorytorep
# replication add source mtree://ddsource.test.com/data/col1/examplemtree
destination mtree://ddtarget.test.com/data/col1/examplemtree (Mtree example)
# replication add source dir://ddsource.test.com/data/col1/directorytorep
destination dir://ddtarget.test.com/backup/directorytorep ipversion ipv6
Note: Ensure your replication is transiting \ exiting the correct interface. When defining a replication
context the hostnames of the source and target DD units must resolve with forward and reverse lookups.
In order to make the data transit alternate interfaces on the appliance, other than the default resolving
interface, the replication context must be modified after creation. It may be necessary to set up host files
to ensure that contexts are defined on non-resolving (cross-over) interfaces.
Note: The last example specifies the version of IP that used as a replication transport
70 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
To start replication between a source and destination, use the replication initialize command on the
source. The command checks that the configuration and connections are correct and returns error
messages if any problems appear. If the source holds a large volume of data, the initialize operation can
take many hours.
Once configured to begin the process of replication enter the following command, in the CLI the
initialization must occur manually, on the source unit:
CLI Equivalent
# replication initialize mtree://host3.test.com/data/col1/mtree1/
71 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
To check that a context is properly configured view the contexts through Enterprise Manager.
CLI Equivalent
# replication show config all
CTX Source Destination Connection Host and PortEnabled
--- ------------ ----------- ------------------
1 dir://host2/backup/dir2 dir://host3/backup/dir3 host3.company.comYes
2 dir://host3/backup/dir3 dir://host2/backup/dir2 host3.company.com Yes
--- ------------ ----------- ------------------
When specifying a specific IP version, use the following command to check its setting:
# replication show config rctx://2
CTX: 2
Source: mtree://ddbeta1.dallasrdc.com/data/col1/EDM1
Destination: mtree://ddbeta2.dallasrdc.com/data/col1/EDM_ipv6
Connection Host: ddbeta2-ipv6.dallasrdc.com
Connection Port: (default)
Ipversion: ipv6
Low-bw-optim: disabled
Encryption: disabled
Enabled: yes
Propagate-retention-lock: enabled
72 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# replication disable {destination | all}
73 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# replication enable {destination | all}
74 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
# replication break {destination | all}
When running the above commands in the CLI, always run the filesys disable command before the
break operation and the filesys enable command after.
With replication, a destination must be empty to be used again (whether with the original source or with
a different source), or alternatively, replication resync must be used.
75 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
#replication modify <destination> connection-host <new-host-name> [port
<port>]
Note: If you wish to direct traffic out of a specific port modify a current context by altering the connection
host parameter using a hostname previously defined in the local hosts file to address the alternate
appliance. The hostname that will be used will correspond to the target data domain appliance. The host
entry will indicate an alternate destination address for that host. This may be required on both the source
and destination appliances.
76 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Prior to creating a directory structure, ensure you are creating the directories in the /backup Mtree. To
provide a granular separation of data users will then need to create, from a host machine, the other
directories (CommVault, Exchange, etc) within the /backup Mtree. Each directory will be based upon the
client’s environment and the desire to replicate those directories to another location. You will not replicate
the entire /backup Mtree but instead would setup replication contexts on each subdirectory underneath
/data/col1/backup/ (ex. /data/col1/backup/Oracle). The purpose of this threefold:
It allows control of the destination locations as oracle may go to one site and exchange may go to
another.
This level of granularity allows management, monitoring and fault isolation. Each replication context
can be paused, stopped, destroyed or reported upon.
Performance is limited on a single context. The creation of multiple contexts can improve aggregate
replication performance.
As a very general recommendation, approximately 5 – 10 contexts may be required to distribute
replication load across multiple replication streams. This must be validated against the site design and
the volume and composition of the data at the location.
CAUTION: Recommending a number of contexts is a design dependant issue and in some cases,
significant implications are attached to the choices made about segregating data for the purposes
of optimizing replication. Data is usually optimized for the manner in which it will rest not in
manner with which it will replicate keep this in mind when altering a backup environment.
Encryption (In-Flight)
Encryption in-flight is the ability to encrypt a replication context, using SSL and 256bit AES. Utilizing In-
flight encryption will have a performance impact that should be relatively minimal however; that is
dependent upon the characteristics of the WAN and the CPU utilization on the appliance. Be sure to
disable a currently configured replication context before applying encryption to it.
To encrypt a replication context as it is initially configured:
# replication add source dir://ddsource.test.com/backup/directorytorep
destination dir://ddtarget.test.com/backup/directorytorep encryption
[enable | disable]
To encrypt a replication context that has already been configured first disable the context that is to be
encrypted:
# replication disable rctx://X (where X is the number of the context to
disable):
Modify the context:
# replication modify source dir://ddsource.test.com/backup/directorytorep
destination dir://ddtarget.test.com/backup/directorytorep encryption
[enable | disable]
77 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Click the advanced tab and check the box Enable Encryption over wire:
78 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Encryption
The encryption Data at Rest feature encrypts all incoming (and optionally, existing) data to the Data
Domain system before it is written to the physical storage media. A passphrase must be entered when
encryption is enabled. The passphrase is requires both an administrator and a security officer to change
it.
To enable encryption enter the following command:
# filesys encryption enable
Enter new passphrase:
Re-enter new passphrase:
Passphrases matched.
The passphrase is set.
The encryption feature is now enabled.
The filesystem must be restarted to effect this change.
Note: To make changes to the embedded key manager you must be logged in using security officer
creditials
Note: Under normal conditions the security officer and the systems administrator are separate individuals
and both must be present to enable this process.
79 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Logout of the security officer account and login as the systems admin
(Optional) To create a new key, enter the following command:
# filesys encryption embedded-key-manager keys create
(Optional) To set up key rotation, enter the following command:
# filesys encryption embedded-key-manager set key-rotation-policy 1
Key-rotation-policy is set. Encryption key will be rotated every 1 months.
Retention Lock
The Data Domain offers two types of retention lock licenses, compliance and governance. It is possible
to have both options licensed on a single appliance.
To remove retention lock from an mtree please enter the following command(s):
# mtree retention-lock revert /data/col1/quota_test
The 'mtree retention-lock revert' command removes retention-lock on this path
thereby making it unprotected.
Are you sure? (yes|no|?) [no]: y
ok, proceeding.
To show which mtrees have retention lock enabled please enter the following command(s):
# mtree list
Name Pre-Comp (GiB) Status
------------------------------ -------------- -------
/data/col1/Default_from_Denver 575.5 RO/RD
/data/col1/backup 0.0 RW
/data/col1/fs_mark_A 475330.7 RW/RLGD
80 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
To show the status of an mtree on which retention lock is enabled enter the following command(s):
# mtree retention-lock status mtree /data/col1/quota_test
Option Value
----------------------------------- ---------------------------------
Retention-lock enabled
Retention-lock mode governance
Retention-lock-uuid 36fb0a0bd553d15b:b3f5ac716af7834a
Retention-lock-min-retention-period 720 minutes
Retention-lock-max-retention-period 1827 days
----------------------------------- ---------------------------------
To add email addresses to the default support list, use the following command:
# autosupport add alerts-summary emails test@test.com
Alerts summary email:
autosupport@autosupport.datadomain.com
east1dd510a@datadomain.com
test@test.com
To add email addresses to the default alerts notification list, use the following command:
# alerts notify-list add emails test@test.com
Alerts email:
autosupport-alert@autosupport.datadomain.com
east1dd510a@datadomain.com
test@test.com
81 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Customer external mail relays must be configured to allow the emails generated by the Data Domain
Appliance to exit the network from which it is currently attached. To test that external mail relays
allow the use the following command:
# autosupport test email jsmith@yourcompany.com
OK: Message sent.
If the result from the command is OK: message sent then the mail has been forwarded outside of the
current network and should be working. If an error message is generated ask the client to verify their
mail relay settings. In the field the best way to confirm this is to add yourself to the test line and verify
that the test email arrives at your email enabled mobile device.
82 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note:Some units have a dedicated port used for the ILO function. Other units must share a port with
other management or customer traffic.
CLI Equivalent
sysadmin@this-box3# ipmi show config
Console: serial
Port Enabled DHCP IP Address Netmask Gateway
----- ------- ---- ------------ ------------- -------------
bmc0a yes no 192.168.0.10 255.255.255.0 192.168.0.254
----- ------- ---- ------------ ------------- -------------
* Value from DHCP
83 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
CLI Equivalent
sysadmin@test-1# ipmi config bmc-eth0 ipaddress 192.168.0.10 netmask 255.255.0.0
gateway 192.168.0.254
Configuration of port bmc-eth0 is successful.
CLI Equivalent
sysadmin@ddtest-1# ipmi user add test password test
User test has been added.
84 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
The Serial-Over-LAN (SOL) feature of IPMI is used to view the serial output of a remote system’s boot
sequence.
Follow the steps below to set up an SOL connection.
1. [ ]Connect the LAN cable to LAN port (older models) or the management port (third single LAN port, for
DD890, DD860, and DD670).
Note:If the BIOS on your Data Domain controller is password protected, contact Data Domain Support for
assistance.
2. [ ]Run ipmi show config to obtain the port name (for example, bmc0a).
3. [ ]Run ipmi config bmc0a dhcp to config an IPMI port using DHCP or a static IP address.
4. [ ]If this is not the first time that IPMI is being used, run ipmi user reset to clear existing IPMI users
(they might be out of sync with the two ports and to disable default users).
5. [ ]Run ipmi user add sysadmin to add a new IPMI user.
6. [ ]Run system option set console lan.
7. [ ]Run ipmi remote console to activate the SOL connection.
8. [ ]To disconnect from an SOL session and return to the command line, use the symbol @.
On most supported Data Domain controllers, the SOL bit rate is 9600 bps.
Note:Following a BIOS upgrade, reset the BIOS setting for SOL usage.
For instructions on using the SOL feature, see the ipmi command in the DD OS 5.3 Command Reference
Guide.
85 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
IBM Tivoli Storage Manager and the Virtual Tape Library feature 9/20/06
IBM Tivoli Storage Manager Integration Guide 7/7/10
Informix 11.10 and Informix Storage Manager 2.20 Tech Note - VTL only 8/8/08
Integrating the Data Domain System VTL with a Storage Area Network 7/8/10
Integrating the Data Domain System VTL with a Storage Area Network (for Open Systems) 11/9/11
LTO Tape Migration for VTLs 1/21/09
Performance Tuning Guide IBM AIX Operating System 5/24/09
TSM and MS Cluster Tech Note - CIFS and VTL 4/3/08
The following is a partial list of resources available for integration work. For a complete and up to date
listing please go to https://my.datadomain.com/US/en/integration.jsp and select IBM in the drop down list.
Note: For the Data Domain systems, ESRS currently only provides ping monitoring and remote
connectivity from support.
All device management requests must be accepted within ServiceLink. Unapproved device management
requests will NOT be actively managed by the Gateway Client, and will remain listed in ServiceLink with a
Pending status until approved. Once the device management request has been approved and the
ServiceLink to Gateway client synchronization process completes, the client will begin monitoring the
device, and remote access sessions to the device can be routed through the client.
When deploying devices against a High Availability Gateway Cluster, the management process only
needs to be completed once. All Gateway Clients within the Cluster will receive a sync message with
updated device management, edits and/or removals.
For information regarding usage of the ServiceLink UI, refer to ESRS IP Solution ServiceLink Customer
Service Procedure 2102 (CSP-2102).
http://www.cs.isus.emc.com/Publishing/Content/Get.aspx?id=20258
Pre-deployment Checklist
The following checklist is provided to guide the user to a successful deployment of a Data Domain
Appliance running Data Domain DDOS 4.8 or later software. Failure to meet these minimum requirements
may result in a failed deployment.
ESRS Gateway Server version: Mandatory minimum version is 2.14
86 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
IMPORTANT: If the ESRS Gateway software version is less than 2.14, the gateway MUST be
upgraded prior to attempting to deploy the Data Domain device .Failure to be running this minimum
version may result in ESRS Gateway failure. For additional information, refer to EMC Primus
Knowledge Article: ETA emc266337: EMC Secure Remote Support Gateway: How to correct issues
created by deploying devices not supported on the installed Gateway code level.
IMPORTANT: ESRS is not supported for use with Data Domain Software Versions prior to v4.8. DO
NOT attempt to deploy a Data Domain Appliance running software versions prior to V4.8.
10. [ ] Once the Configuration Tool screen is active, locate the client version in the top left corner of the
screen.
Verify that the version listed is equal to or higher than v2.14. If the version is lower, it must be
upgraded prior to attempting to deploy the Data Domain Device.
IMPORTANT: If the ESRS Gateway software version is less than 2.14, the gateway MUST be
upgraded prior to attempting to deploy the Data Domain device .Failure to be running this minimum
version may result in ESRS Gateway failure. For additional information, refer to EMC Primus
Knowledge Article: ETA emc266337: EMC Secure Remote Support Gateway: How to correct issues
created by deploying devices not supported on the installed Gateway code level.
87 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
88 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
12. [ ] Within the Configuration Tool, select the Managed Devices tab.
Note: Newer generation Data Domain models will have an Asset Tag number AND a Serial Number.
When an Asset Tag is present, the Asset Tag number should be used in lieu of the Serial Number
Model Type
Suffix parameters display dependent upon Model selected
IP address
89 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
A connectivity test is run. If the Configuration Tool is unable to reach the device, users will receive a
warning but can continue with the management request. If you continue, without a valid connectivity
test, it is very important to make sure the connectivity issue is resolved.
90 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
15. [ ] The device will be listed in the Configuration Tool with a status.
16. [ ] Click Request Update to send the pending request to the EMC Enterprise. A pop-up will display
management requests being sent to ServiceLink. If the devices listed are incorrect, click No and edit
devices listed in the Configuration Tool. If the information is correct click Yes.
91 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
17. [ ] Requests have been sent to EMC for approval. Users must now log in to ServiceLink to approve
the request. Follow the steps outlined in Pending Management Requests.
92 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
21. [ ] The device management request will be listed with a Validation Error. Users can mouse over
the Validation Error to display error information.
22. [ ] Click Edit to correct invalid data and click Save when complete.
93 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
25. [ ] The device will remain in the Unmanaged state until the Client is synchronized.
The scheduled synchronization job will run. The scheduled job runs every ten minutes. As such it may
take up to ten minutes for the device to be fully managed. If you do not wish to wait for the automatic
synchronization process to run, click Sync Now to for an automatic synch. Accept the Sync Now pop
up.
94 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
26. [ ] The Device is listed in Managed (Unregistered) state until the Client pings ServiceLink
acknowledging management.
95 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
29. [ ] Click on the Gateway Client serial number or in the Action Column click on the Manage Devices
action.
30. [ ] The device will be listed in Pending Add status, click approve to complete add.
96 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
31. [ ] The device will remain in Managed (Unregistered) state until the Client is synched.
Click Sync Now to for an automatic synch.
Or allow the scheduled job to run. The scheduled job will run every ten minutes. As such it may
take ten minutes for the device to be fully managed.
The device’s status will not be displayed until the Client is synchronized.
32. [ ] Once the Client is synched, the device will be listed in Managed status and is fully deployed
against the Client.
97 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
37. [ ] Once you are on the Cluster page, click Add and you will be prompted to enter device
information.
98 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
Note: Newer generation Data Domain models will have an Asset Tag number AND a Serial Number.
When an Asset Tag is present, the Asset Tag number should be used in lieu of the Serial Number.
39. [ ] When finished click Save. If information entered is invalid, user will receive an error, you’ll then
need to make the appropriate corrections and click Save.
40. [ ] The device will be added to the Managed Device page in a Pending Add state.
41. [ ] The device request must be approved for the management process to continue. In the Action
column, next to the appropriate device, Click Approve and the device status will update to
Unmanaged.
Note: If more than one device is listed in Pending status, users can click Approve All to approve all
requests.
99 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
42. [ ] The device will remain in the Unmanaged state until the Client pings ServiceLink.
Click Sync Now to for an automatic synch. Accept the Sync Now pop up.
- or -
Allow the scheduled job to run. The scheduled job will run every ten minutes. As such it may take up
to ten minutes for the device to be fully managed.
43. [ ] The device is listed in the Managed (Unregistered) state until the Client pings ServiceLink to
acknowledge management.
The device state will then be displayed as Managed.
Device connectivity status will be displayed once the device is fully managed.
100 of 101
EMC® Data Domain ® SolVe Generator
Solution for Validating your engagement
INSTALLATION CHECKLIST
101 of 101