302-001-639 Rev 01 EMC Data Domain System Controller Upgrade Guide 5.6

Upgrade Guide
EMC® Data Domain® Operating System

Release number 5.6
System Controller Upgrade Guide

302-001-639
REVISION 01
April, 2015
This document provides instructions for replacing the controller unit in a Data Domain
system with a newer model. This document covers the following topics:
l Revision history......................................................................................................... 2
l Related documentation..............................................................................................2
l Tools and supplies needed........................................................................................ 2
l Upgrade options........................................................................................................ 2
l Upgrade planning considerations...............................................................................4
l Source controller preparation...................................................................................12
l Preparing the destination controller......................................................................... 16
l System controller upgrade....................................................................................... 18
Upgrade Guide
Revision history
Table 1 Document revision history
Revision Date Description

01 April 2015 Added information on the new DD9500 system.
Related documentation
EMC provides a variety of document types to support our products. End-user documents
include user guides, hardware installation guides, administrator guides, software guides,
part replacement guides, release notes, and others. Integration documents describe how
to integrate EMC systems with third party backup applications, and compatibility
matrices show which components are compatible with each other.
This document refers to other EMC documents by title. To locate a referenced document,
go to the EMC Online Support website at https://support.emc.com, enter the document
title in the search box, and click the search button.
Note
Hard copies of a document may be out of date. Always check for the current version of a
document before you start an upgrade or begin a significant configuration change.
Tools and supplies needed

For a list of recommended tools and supplies for field work, see the document titled FE
Toolkit Inventory and Common Procedures for FRU Tasks at https://support.emc.com.
Upgrade options
The Data Domain system upgrade options that are available are listed in this table.
Table 2 Data Domain system upgrade options
Existing Memory Upgrade to Memory Comments

System New System
DD690 16-24 GB DD860 36 GB or 72 GB Cannot support
ES20-8TB
DD690 16-24 GB DD890 96 GB Cannot support

ES20-8TB

ES20-8TB

ES20-8TB
2 EMC Data Domain Operating System 5.6 Upgrade Guide

Table 2 Data Domain system upgrade options (continued)

System New System
ES20-8TB

ES20-8TB
DD860 36 GB or 72 GB DD890 96 GB
DD860 36 GB or 72 GB DD990 128 GB or 256 GB
DD860 36 GB or 72 GB DD4200 128 GB
DD860 36 GB or 72 GB DD4500 192 GB
DD860 36 GB or 72 GB DD7200 128 GB or 256 GB
DD860 with 36 GB or 72 GB DD990 with 256 GB

Extended Extended
Retention Retention
(formerly (formerly
named DD860 named DD990
Archiver) Archiver)
DD860 with 72 GB DD4200 with 128 GB

Extended Extended
Retention Retention

Extended Extended
Retention Retention

Extended Extended
Retention Retention
DD880 48 GB or 64 GB DD890 96 GB Cannot support

ES20-8TB
DD880 48 GB or 64 GB DD990 128 GB or 256 GB Cannot support

ES20-8TB

ES20-8TB;
maximum capacity
supported is 192
TB usable

ES20-8TB
DD880 48 GB or 64 GB DD7200 128 GB or 256 GB Cannot support

ES20-8TB
DD890 96 GB DD990 128 GB or 256 GB
DD890 96 GB DD4200 128 GB Maximum capacity

supported is 189
TB usable
Upgrade options 3
Upgrade Guide
Table 2 Data Domain system upgrade options (continued)

System New System
DD890 96 GB DD4500 192 GB
DD890 96 GB DD7200 128 GB or 256 GB
DD990 128 GB or 256 GB DD9500 256 GB for up to 864 ES20 Expansion

TB capacity for the shelves are not
active tier tested and not
512 GB for up to 864 approved for use
TB capacity in the with DD9500
active tier and 864 TB systems.
capacity in the archive
tier (requires the
Extended Retention
license).
DD4200 128 GB DD4500 192 GB
DD4200 128 GB DD7200 128 GB or 256 GB

Extended Extended
Retention Retention

Extended Extended
Retention Retention

Extended Extended
Retention Retention
DD7200 128 GB or 256 GB DD9500 256 GB for up to 864 ES20 Expansion

TB capacity for the shelves are not
active tier tested and not
512 GB for up to 864 approved for use
TB capacity in the with DD9500
active tier and 864 TB systems.
capacity in the archive
tier (requires the
Extended Retention
license).
Upgrade planning considerations

The following topics describe guidelines that you should consider before starting a
controller upgrade.
General considerations
The controller upgrade procedure requires the following tasks.
1. Prepare the source controller and capture the current system configuration.

2. Prepare the destination controller.

3. Shut down the source controller.
4. Remove the source controller.
5. Install the destination controller.
6. Review the configuration on the destination controller and verify proper system
operation.
It is very important that no configuration, feature, or hardware changes are made
between the start and finish of this procedure. If any changes are made before the
procedure is complete and the configuration saved in the storage shelves does not match
the new system configuration, the system may become unreliable or fail.
Note
EMC recommends that you read this entire document before you start a controller
upgrade. All the information is important; do not review only the highlighted text.
l Any failed disks must be replaced and reconstructed before the upgrade procedure
starts.
l This version of DD OS does not support more than one archive unit on a DD9500
system. If the source controller has multiple archive units, contract EMC Support for
assistance in merging them to a single archive unit before the upgrade.
l Space utilization, system alerts, cleaning, and replication statistics are reset after a
controller upgrade. In many cases, this is the desired behavior after upgrading the
chassis. If this information must be retained, contact EMC support prior to starting
the upgrade process.
l Download and review the Release Notes of the DD OS you are upgrading to as part of
the controller upgrade process. Download Release Notes from the EMC Support Portal
at https://support.emc.com.
l For releases prior to DD OS 5.4, the source and destination controller must use the
same DD OS major version but may have different minor versions. For DD OS 5.4 and
later, the same release (major and minor version) must be installed on the source
and destination controller before you start to remove the source controller.
l The source file system usage must be 95% or less (free space 5% or more) to support
a controller upgrade. The additional space is required to store temporary files during
the upgrade.
l If your upgrade plan includes adding software features such as Extended Retention or
Replication, make the changes before you start the controller upgrade or after the
controller upgrade is complete. Do not change software features while a controller
upgrade is in progress.
l EMC does not support migration of PCI and I/O option cards from a source system to
a destination system in the controller upgrade procedure. New PCI and I/O option
cards must be purchased for the new system.
l Data Domain systems are heavy. To avoid personnel injury or equipment damage,
plan to use two people or a mechanical lift when moving a chassis or shelf.
l The system controller upgrade process preserves the configuration settings for CIFS,
NFS, and DD Boost communication.
l For WWN migration on systems configured for Fibre Channel, the same DD OS version,
which must be version 5.3 or later, is required on the source and destination DDRs.
The upgrade process will preserve the VTL and DDBoost over Fibre Channel
configuration from the original system. However, the Fibre Channel ports can differ
between the source and destination systems, which requires the migration of the
General considerations 5
Upgrade Guide
Fibre Channel configuration to the appropriate ports on the destination system. The
FC migration procedure is covered later in this document.
l After WWN migration and if the source system will be redeployed, the Fibre Channel
configuration on the source system must be removed or changed to avoid conflicts
with the destination system.
l The WWN configuration for DD OS version 5.3 or later is persistent across system
reboot, DD OS upgrade, and controller upgrade. However, the WWN configuration is
reset to the default values after a DD OS reinstall.
l The network configurations of the system controller being replaced may not be
applicable to the new upgraded system controller since the network slots/names will
change. All network configuration settings of the replaced system controller must be
recorded carefully to recreate the network configuration on the new system controller.
l If the file system is encrypted, make sure to acquire the required passwords or
passphrase before beginning the upgrade.
l If VTL is used on the source system and if the source system is redeployed, there is a
possibility of VTL drive serial number collisions if the same backup software accesses
the target system and the redeployed system.
l Record the replication configuration.
l If DD Boost is supported on the source system and you are planning to upgrade DD
OS, determine if the installed DD Boost plug-in software is compatible with the target
DD OS version. You might need to upgrade the DD Boost plug-in software when you
upgrade DD OS.
Note
The controller upgrade procedure requires one or more reboots of the system.
Safety considerations
l Always use two people or a mechanical lift when moving any Data Domain system.
l Power remains for some time after you remove power cords. Do not remove hardware
components until all of the LEDs are dark.
Rack considerations
l Ensure the target system rail kit will work with the target rack, as the distance
between front and rear posts of racks can vary. Some systems are 2U (2 rack units)
height (for example, the DD690 and DD890), while other systems are 4U (for example
the DD990 and DD4500 systems).
l The rack mount kits for most Data Domain systems work in the Data Domain Rack
(EMC Titan C rack). The exception is the DD690, which requires the rail kit, X-600-
SHELF.
l When performing a controller upgrade from a PCI-based legacy system to a newer
system having I/O Modules, you may need to order additional controller-to-shelf SAS
cables for shelves being brought forward.
l If the new system controller is installed in a different location than the original system
controller, make sure that the existing shelf SAS cables will reach the new location. If
not, order longer cables.
l Cables 3 meters and longer are generally intended for rack-to-rack connections. The
"U" spanning distance is not applicable in that case.

l The following are ES20 cabling guidelines.

n Vertical span assumes a straight vertical run with the recommended 2.5"
(100mm) minimum bend radius.
n If a cable must skip over a controller (Data Domain system), the vertical span will
be reduced by 4 RU from what is shown.
l The following are ES30 cabling guidelines.
n Vertical Span assumes the cables are routed to the side to allow for service
access and has the recommended 2.5" (100mm) minimum bend radius.
n If a cable must skip over a Data Domain controller, the Vertical Span will be
reduced by 7 RU from what is shown.
l Cable options are shown in the following figures and tables.
Figure 1 Mini-SAS cable for SAS HBA to ES30 and ES30 to ES30 connections
Table 3 Controller with SAS HBA to ES30 cable options
Cable Part Number Cable Length Vertical Span, RU

Mini-SAS cable, SFF-8088 connectors on both ends, one end keyed for host ports and the other
keyed for expansion ports
Controllers: DD565, DD640, DD660, DD670, DD690, DD860, DD880, DD890, DD990
X-SAS-MSMS1 1 m. (39 in.) 9
X-SAS-MSMS2 2 m. (79 in.) 31
X-SAS-MSMS3 3 m. (118 in.) 53
X-SAS-MSMS5 5 m. (196 in.) 97
Rack considerations 7
Upgrade Guide
Table 4 ES30 to ES30 cable options
Model Code Cable Length Vertical Span (RU)a

Mini-SAS cable, SFF-8088 connectors on both ends, one end keyed for host ports and the other
keyed for expansion ports
X-SAS-MSMS1 1 m (39 in.) 9
X-SAS-MSMS2 2 m (79 in.) 31
X-SAS-MSMS3 3 m (118 in.) 66
X-SAS-MSMS5 5 m (196 in.) 97
a. RU distances are approximate measurements and may require adjustment for your environment.
Figure 2 Mini-SAS cable for SAS HBA to ES20 connections
Table 5 Controller with SAS HBA to ES20 cable options

Mini-SAS cable, SFF-8088 connector on controller (keyed for host or expansion ports), SFF-8470
on ES20
Controllers: DD565, DD640, DD660, DD670, DD690, DD860, DD880, DD890, DD990
X-SAS-MSIB1 1 m. (39 in.) 16
X-SAS-MSIB2 2 m. (79 in.) 39
X-SAS-MSIB5 5 m. (196 in.) 106

Figure 3 Mini-SAS cable for ES20 to ES20 connections
Table 6 ES20 to ES20 cable options
Model Code Cable Length Vertical Span (RU)a

Mini-SAS cable, SFF-8470 connectors on both ends
X-SAS-0.5M 0.5 m (19 in.) 5
X-SAS-1M 1 m (39 in.) 16
X-SAS-2M 2 m (79 in.) 39
X-SAS-5M 5 m (196 in.) 106
a. RU distances are approximate measurements and may require adjustment for your environment.
Figure 4 HD-mini-SAS cable for SAS I/O module to ES30 connections
Rack considerations 9
Upgrade Guide
Table 7 Controller with SAS I/O module to ES30 cable options

HD-mini-SAS connector on controller, SFF-8088 connector keyed for host port on ES30
Controllers: DD4200, DD4500, DD7200, DD9500
X-SAS-HDMS1 1 m. (39 in.) 9
X-SAS-HDMS2 2 m. (79 in.) 31
X-SAS-HDMS3 3 m. (118 in.) 53
X-SAS-HDMS5 5 m. (196 in.) 97
Figure 5 HD-mini-SAS cable for SAS I/O module to ES20 connections
Table 8 Controller with SAS I/O module to ES20 cable options

HD-mini-SAS connector on controller, SFF-8470 on ES20
Controllers: DD4200, DD4500, DD7200
X-SAS-HDIB1 1 m. (39 in.) 16
X-SAS-HDIB2 2 m. (79 in.) 39
X-SAS-HDIB5 5 m. (196 in.) 106
Time considerations
The system controller upgrade process will take time. Plan accordingly so time is
maximized between starting the controller upgrade procedure and the next scheduled
backup. Consider the following time-related issues before you start your upgrade.
l The upgrade may require rebuilding of the index. Re-indexing may take 4-6 hours to
complete.
l The controllers must be using the slot-based Ethernet port naming convention as
described later in this document. If an upgrade to this convention is needed, EMC
Support assistance is required and must be scheduled before the controller upgrade.

l If a DD OS upgrade is required on the source or destination controller, the DD OS

upgrade may require over an hour, depending on the amount of data on the system.
For instructions on how to upgrade DD OS, refer to the upgrade instructions section of
the Release Notes for the target DD OS version.
l The file system must be enabled. The amount of time required to enable the file
system depends on the system changes that are required.
l Restoring the Fibre Channel configuration, re-zoning the SAN, and re-mapping
WWNNs and WWPNs on the new controller may take additional time, depending on
the size, complexity, and manual effort required to redefine the mappings. Tape
device configuration on the systems performing backups may also be required, as
some systems use the WWNN and WWPN to identify devices.
l Although executing the system headswap command can take less than 30
minutes, the entire controller upgrade procedure may take up to three hours or more.
The upgrade process takes longer when the NVRAM batteries on the new system
require charging or when the file system index must be rebuilt.
l Charging the NVRAM batteries on a new system can add three hours to the upgrade
procedure. EMC recommends that you apply power to the destination controller on a
day prior to the day you plan to perform the upgrade.
l If you are unsure of the time required for this upgrade, contact your account team.
Note
After executing the headswap command, the system is rebooted automatically.
Hardware considerations
l Ensure that the power requirements for the new system have been met. Some Data
Domain systems operate on either 100-120V or 200-240V whereas other systems
require a 200-240V power source.
l Some Data Domain systems are 2U while others are 4U. If the new controller is
installed in a different location, make sure that the existing shelf SAS cables will
reach the new location. If not, order longer cables as needed.
l Purchase new optional I/O cards for the target system (either PCI cards for legacy
systems or I/O Modules for new systems). EMC Data Domain does not support
transferring any PCI cards.
l If your upgrade plan includes adding enclosures, add the enclosures before you start
the controller upgrade or after the controller upgrade is complete. Do not change the
enclosure configuration while a controller upgrade is in progress.
l Before upgrading a controller, verify that the destination controller supports the
enclosure configuration on the source controller. You might need to upgrade the
enclosure configuration before updating the controller. Consider the following
information when evaluating the enclosure configuration.
n DD9500 systems require a minimum of 4 enclosures.
n ES20 Expansion shelves are not tested and not approved for use with DD9500
systems. Controller upgrades for systems with ES20 shelves are not supported in
this release. However, data migration to a newly-installed Apollo system is
supported.
n DD9500 systems do not support both SATA and SAS shelves on the same chain of
enclosures.
Hardware considerations 11
Upgrade Guide
n See the EMC Data Domain ES30 Expansion Shelf Hardware Guide for information on
which combinations of enclosures are supported on a particular system.
Source controller preparation

The following topics describe how to prepare the source controller for the upgrade.
Because these tasks can be time consuming, it is a good practice to complete these tasks
prior to the day of the upgrade.
Examining and updating the port naming method

If the source controller is not already using the slot-based Ethernet port naming system,
the controller must be upgraded to use slot-based port naming before the controller
upgrade.
To determine if slot-based port naming is in use, connect a console to the system, log in,
and enter the command net show hardware. Ethernet port names of ethMa, eth0a,
or eth0b, for example, indicate slot-based port naming. Ethernet port names of eth0 or
eth1, however, indicate legacy port naming, which was the default naming used on
systems before DD OS 4.9.
To upgrade the system to the slot-based naming convention, contact EMC Support at
https://support.emc.com.
Examining and updating DD OS on the source controller

The controller upgrade requires that the source and destination controllers must be
running the same DD OS version as defined earlier in this document.
Procedure
1. Connect a console to the system and log in.
2. Enter system show version.
3. Make a note of the version.
If the version matches the version of the destination controller as described earlier in
this document, you do not need to update DD OS on the source controller. You can
skip steps 4 and 5 of this procedure.
4. If the source controller requires an upgrade, download the appropriate version of the
EMC Data Domain Operating System Release Notes from the EMC Support Portal at
https://support.emc.com.
5. Follow the instructions in the release notes, and upgrade DD OS with the
system upgrade command.
Note
If your upgrade plan calls for mulitple sucessive upgrades (for example, 4.9->5.1-
>5.2.3), use the filesys show space command to verify that the file system is
available before you start the next upgrade. If the filesys show space command
does not display the Active Tier Resource information, or if it displays The
filesystem is unavailable at this time, the system is not ready for the
next upgrade.

Recording the source controller configuration

Due to differences in network and fibre channel port numbers in the source and
destination controllers, you will probably need to make some configuration changes after
the destination controller is installed. While most configuration information is retained
during the upgrade, VTL configuration information might be lost. EMC Data Domain
recommends that you record the complete configuration of the existing system before
beginning the upgrade procedure so that you can review and repair any configuration
issues on the destination controller.
Procedure
1. If the existing system is configured with a passphrase, verify that you will have access
to the passphrase when you install the new controller.
You cannot use the system to display the passphrase. After the headswap, you or the
passphrase owner must reenter this passphrase.
2. Execute the command #system show alert. If there are alerts or issues, resolve
them before you continue this procedure.
3. Send an autosupport email message to yourself.
# autosupport send username@yourcompany.com
The autosupport message records key system configuration features and serves as
another information source if you need to access the source controller configuration.
4. Configure your terminal emulation program to record the session.
Most of this procedure captures the source controller configuration using CLI
commands. Recording the session captures the configuration for future reference.
5. For a system enabled with DD Extended Retention software (formerly known as Data
Domain Archiver), ensure there is no data movement.
# archive data-movement status
# archive data-movement stop
6. Check if space reclamation is running, and if so, suspend it.
# archive space-reclamation status
# archive space-reclamation suspend
7. Display the license keys.
# license show
8. If used, record the VTL configuration.
# vtl port show summary
# vtl port show hardware
# vtl port option show
# vtl show config
# vtl option show all
9. If either VTL or DDBoost-over-FC is present, record the scsitarget configuration.
# scsitarget group show detailed
# scsitarget endpoint show detailed
# scsitarget initiator show detailed
# scsitarget transport option show all
# scsitarget endpoint show list
Recording the source controller configuration 13

Upgrade Guide
Note
WWN migration requires the WWN information displayed by the scsitarget

endpoint show detailed command. To view this information in the autosupport
file, search for SCSITARGET Endpoint Show Detailed or Enclosure Show All. To view
this information in DD System Manager, select Hardware > Fibre Channel > Physical
Resources.
10.Create a table to map the endpoints to the correct ports on the destination controller
as described in the following procedure.
The endpoint name, WWPN, and WWNN are transferred to the destination controller
during the upgrade. When the destination controller starts, however, new endpoints
are created for each port. After the destination controller starts, you will use the table
you create here to delete the new endpoints and reassign the migrated endpoints to
the correct ports.
a. In the first column of each row, record an endpoint name.

b. In the second and third columns for each row, enter the WWPN and WWNN for the
endpoint.
c. In the fourth column, enter the source controller port number that hosts the
endpoint.
d. In the fifth column, enter the destination controller port number that you want to
host the endpoint.
If you do not have the destination port number, you can get it later after the
destination system starts. The endpoints appear in the output of the scsitarget
endpoint show list command.
The following is an example mapping table. Notice that this table calls for source
ports 4a and 4b to migrate to ports 4a and 4b on the destination system, and source
ports 5a and 5b map to slot 6 on the destination system. Because new endpoints with
WWPN and WWNN addresses will automatically be created for the destination ports,
all new endpoints for the ports listed in the table will need to be deleted and each
migrated endpoint assigned to the correct port.
Table 9 Example: Endpoint to port mapping table
Endpoint WWPN WWNN Source Port Destination Port

endpoint-fc-0 24:00:00:21:88:2d:e8:a0 20:00:00:21:88:2d:e8:a0 4a 4a
endpoint-fc-1 24:10:00:21:88:2d:e8:a0 20:00:00:21:88:2d:e8:a0 4b 4b
endpoint-fc-2 25:00:00:21:88:2d:e8:a0 20:00:00:21:88:2d:e8:a0 5a 6a
endpoint-fc-3 25:10:00:21:88:2d:e8:a0 20:00:00:21:88:2d:e8:a0 5b 6b
Note
To prevent service interruption, there must be a corresponding port on the destination

system for every port on the source system.
11.Record the replication configuration.

# replication show config

12.If used, record the NFS and DD Boost configurations.

Although it should not be necessary to manually reconfigure NFS or DD Boost, it is
recommended that you record those configuration settings. When you run these
commands before and after the controller upgrade, the output should be the same.
# nfs show clients

# net hosts show
# net show hardware
# ddboost show user-name
# ddboost storage-unit show
# ddboost fc status
# ddboost fc dfc-server-name show
# ddboost fc group show list
13.If used, record the CIFS configuration and share definitions.
# cifs share show
# cifs show config
14.Record the file system configuration.
# disk show state
# disk status
# disk show hardware
# system show ports
# disk multipath status
# filesys show space
# enclosure show topology
# mtree list
# mtree retention-lock status mtree mtree-path
# filesys encryption show
# mtree list
# snapshot list mtree mtree-path
15.For systems with the DD Extended Retention software option, record the file system
configuration.
# storage show all
# filesys archive unit list all
# archive show config
# archive data-movement policy show
16.Record external network card configuration including card slot, card vendor and
model, speed, and number of ports.
# system show hardware
# system show port
# net show hardware
17.Record network services on the controller including failover, aggregation, VLANs, and
IP aliases.
# net show settings
# net show config
18.Save the output of your terminal emulation program with an appropriate file name.
19.Develop a port mapping table that includes identification of the ports on the source
controller, the correlation of the ports on the destination controller, and the IP
addresses.
In the rear of the system, I/O slots are numbered in varying ways. Consult your
system's documentation for details. When facing the rear of the system, ports are
numbered left to right, and/or top to bottom. Platforms with DD OS 5.4 and later have
slot numbering that begins with "0" as opposed to older legacy platforms in which
numbering began with "1". For example, a legacy system mapped to slot1 would be
mapped to slot0 on newer platforms. Additionally, a legacy system onboard port was
named with "0" (for example, eth0a/0b), while newer platforms use "M" (for example,
ethMa/Mb).
Recording the source controller configuration 15

Upgrade Guide
Consider the following guidelines when working with DD4200, DD4500, and DD7200
systems:
l There is only one on-board ethernet interface (ethMa). Therefore, migrating the
onboard settings from a legacy system would be applicable to only one interface
(eth0a in legacy systems).
l Network features such as bonding and aggregation will not work for ethMa.
Therefore, if the legacy system has any of these features for eth0a, these features
will not be applicable.
Assume the source controller has eth3a and eth3b bonded to veth0 (which means the
NIC card is in slot 3). To collect the network port settings and IP address information,
use the net show settings command as shown in the following example.
Figure 6 Output: net show settings
If the NIC card in the destination controller is in slot1, the same settings should be
applied for eth1a and eth1b in the new system. The mapping will be slot3->slot1 and
the new settings should be as shown in the following example.
20.Develop a service mapping table to include information for services on the existing
controller and the correlation of these services on the new controller.
Include services such as link failover, link aggregation, VLAN, and IP aliases. It may be
preferable that the ports for failover or aggregation group are on different cards but
connected to the same subnet.
Figure 7 Output: net show settings
21.Record IPMI remote access configuration on the controller.

a. Enter these two commands: ipmi show config and ipmi user list.
b. Write down the configuration and user names. The user password will not be
carried over to the new controller.
Preparing the destination controller

Because some of the steps in this procedure are time consuming, It is a good practice to
perform this procedure on a day prior to the upgrade day.
Procedure
1. If the destination controller is a new system, write down the serial number on the back
of the new system.
The serial number is the default password for the sysadmin account on a new
system.

2. If possible, set up the new system on a workbench and connect the power cables.
Otherwise, refer to the instructions in the rack mounting kit and install the system in
either a temporary or permanent location in a rack.
Leave the power on until the NVRAM batteries are fully charged. It can take up to 3
hours to fully charge the batteries.
Note
Do not remove the source controller to make room for the destination controller until
instructed to remove the source controller. For this procedure, the connection of SAS
cables to shelves is not necessary and not recommended.
3. Connect a console to the system.

4. Power up the system.
5. When the login prompt appears, log in using the sysadmin user name and the
configured password.
Note
The default password for new system is the serial number on the back of the system.
6. When the configuration utility starts up, enter Ctrl-C to exit the utility. Do not change
the sysadmin account password now.
The initial message in the configuration utility is the welcome message.
Welcome to Data Domain OS 5.3.0.0-138618
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) [yes]:
no
7. Enter license show.
8. Record the license key codes.
You will need to add these license keys after the upgrade.
9. When the configuration utility finishes, enter the system show version
command.
10.Make a note of the version.
11.If the destination controller has a newer major version of DD OS than the source
controller, do the following.
a. Enter system show nvram.
b. When the NVRAM batteries are fully charged (80% minimum), use the system
poweroff command to shut down the destination controller.
Note
Never shut down the system by pressing the power button (if present on your
system). The NVRAM batteries in an improperly shut down system can drain
quickly. Recharging those batteries can add two to three hours to this upgrade
procedure.
c. Stop this procedure because the DD OS versions do not match.
Preparing the destination controller 17

Upgrade Guide
You must either upgrade the source controller to the same DD OS version used on
the destination controller, or you must replace the DD OS on the destination
controller with the version used on the source controller.
12.If the destination controller DD OS version is older than that on the source controller,
do the following.
a. If the destination controller you are installing already has DD OS software
installed, follow the upgrade instructions in the release notes, and upgrade DD OS
with the system upgrade command.
Note
If your upgrade plan calls for mulitple sucessive upgrades (for example, 4.9->5.1-
>5.2.3), use the filesys show space command to verify that the file system is
available before you start the next upgrade. If the filesys show space
command does not display the Active Tier Resource information, or if it displays
The filesystem is unavailable at this time, the system is not
ready for the next upgrade.
b. When the NVRAM batteries are fully charged (80% minimum), use the system
poweroff command to shut down the destination controller.
Note
Never shut down the system by pressing the power button (if present on your
system). The NVRAM batteries in an improperly shut down system can drain
quickly. Recharging those batteries can add two to three hours to this upgrade
procedure.
c. Skip the rest of this procedure.

13.If the destination controller does not have DD OS installed, install it from a USB device
or DVD as described in the EMC Data Domain Operating System USB Installation Guide or
EMC Data Domain Operating System DVD Installation Guide.
System controller upgrade

The following topics describe the tasks required to perform the controller upgrade.
Taking the source controller out of service

Before you begin
Before taking the source controller out of service, shut down all backup applications that
are writing to data the system using the guidelines for those applications.
Procedure
1. Check for unresolved alerts. If there are alerts or issues, resolve them before you
continue this procedure.
# system show alert
2. Check for multiple archive units. If there are multiple archive units, contact EMC
Support for assistance in merging them into one archive unit.

3. For a Data Domain system with the Extended Retention software option, ensure there
is no data-movement or space-reclamation running.
# archive data-movement status
# archive data-movement stop
# archive space-reclamation suspend
4. Check for any active CIFS client connections and stop them. To check for CIFS activity,
enter:
# cifs show active
5. If there are active CIFS clients, disconnect them and disable CIFS by running:
# cifs disable
6. Disable VTL:
a. Determine whether VTL is enabled. To determine if VTL is enabled, enter:
# vtl status
b. If VTL is enabled, disable VTL:

# vtl disable
7. If SCSI Target is enabled (scsitarget status), disable SCSI Target:
# scsitarget disable
8. Determine whether there are NFS connections and unmount the file systems on the
remote systems. To identify the remote systems that have mounted the Data Domain
storage, enter:
# nfs show active
9. Use the umount command on those remote systems to dismount the NFS file
systems.
10.If there are DD Boost connections, stop the backup applications on the connected
systems. To identify those systems, enter:
# ddboost show connections
11.Determine whether replication is enabled, and disable replication if it is enabled.
a. To check replication status, enter:
# replication status
b. If replication is enabled, disable it. Enter:

# replication disable all
c. Verify replication is disabled on all contexts. Enter:

# replication status
Note
Do not proceed until all replication contexts are disabled. This may take up to 15
minutes.
12.Verify there is no traffic on the Ethernet NICs. Enter:

# iostat 2
Run for approximately 60 seconds before exiting.
Taking the source controller out of service 19

Upgrade Guide
13.A reboot is recommended, if possible, before performing the upgrade procedure. This
ensures all hardware is in working order.
# system reboot
Changing controllers
CAUTION
Once the new system controller has been installed and booted, the upgrade process
cannot be stopped. If this happens, the integrity of the data can be affected.
Procedure
1. Before powering off the system, entering the command filesys disable is
recommended.
2. Power off the existing system by using the system poweroff command. Do not
power off the shelves.
3. Label all cables on the source controller, and then disconnect them.
CAUTION
l Power remains for some time after you remove the power cords. Wait until all of
the LEDs are dark.
l Always use two people or a mechanical lift when moving any Data Domain system.
4. Remove the existing system controller.
Note
The IP and Fibre Channel configurations remain on the source system and will cause
conflicts if that system is later reconnected to the same LAN or SAN to which the
destination system is connected. Before reconnecting the removed system to the
original LAN or SAN, remove the configuration from all ports that can be connected to
a LAN or SAN.
5. Install the replacement system controller in the rack.

6. Excluding the cables for the Fibre Channel ports, connect all system interface cables
and any KVM switch for the system console.
Refer to the map tables that you created when preparing for the upgrade. If you did
not create configuration tables, stop now and create them using information in the
Autosupport report you generated on the source controller.
7. Connect the SAS cables to all storage shelves, ensuring that the shelves are cabled
appropriately. For more information, refer to Expansion Shelf Hardware Guide and the
installation and setup guide for the new system.
8. Power on the new controller.
The power for attached shelves should have remained on.
9. When the login prompt appears, log in using the serial number as the password for
the sysadmin account.
10.Verify the status of the NVRAM batteries by entering the system show nvram
command.

If the batteries are charged 60% or less, allow them to charge as described in the
chassis replacement or upgrade guide for the new system. Recharging the NVRAM
batteries can take up to three hours.
If the NVRAM batteries have been partially discharged, an error light (amber in color)
located at the back of the NVRAM card begins blinking when the system is powered
on, and an error message similar to the following is appears on the console.
NVRAM0: Size 5224288 KB, Battery 1 Enabled (FAILURE),

Battery 2 Enabled (FAILURE)
Let the batteries charge before continuing.
11.Use the config setup or net config command to reconfigure the network
settings according to the map tables recorded earlier.
For information on using the config setup command to launch the utility that
helps you configure a system, refer to the EMC Data Domain Operating System Initial
Configuration Guide.
For information on using the net config command to add and remove interface
configurations, refer to the EMC Data Domain Command Reference Guide.
Note
All network interface connections that are no longer valid (such as configurations for
unused slots or slots with a different type of card) must be removed.
Configuring the destination controller

Many steps in the following procedure require that you compare command output from
the destination controller with command output from the source controller to verify that
all hardware and features are available on the destination controller. This information
should have been recorded as described earlier in this guide. You can also find this
information in the ASUP that you were instructed to create.
Procedure
1. Verify that the destination controller lists all the enclosures and disks that were
installed on the source controller.
The output should indicate that the data storage is not configured and is foreign
storage.
Note
User data becomes available in the final steps of the procedure.
Configuring the destination controller 21

Upgrade Guide
# storage show all

Active tier details:
Disk Disks Count Disk Additional
Group Size Information
------- ----- ----- --------- -----------
(spare) 2.1 1 931.5 GiB
(spare) 3.15 1 931.5 GiB
------- ----- ----- --------- -----------
Current active tier size: 21.8 TiB
Active tier maximum capacity: 261.9 TiB
Storage addable disks:
Disk Disks Count Disk Enclosure Shelf Capacity Additional
Type Size Model License Needed Information
--------- -------- ----- ---------- --------- -------------- ---------
(foreign) 2.2-2.15 14 931.5 GiB ES30 N/A Host SN:
0F41722499
(foreign) 3.1-3.14 14 931.5 GiB ES30 N/A Host SN:
0F41722499
--------- -------- ----- ---------- --------- -------------- ---------
# disk show state
Enclosure Disk
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
--------- ---------------------------------------------
1 . . . s
2 s O O O O O O O O O O O O O O
3 O O O O O O O O O O O O O O s
--------- ---------------------------------------------
Legend State Count
------ ------------- -----
. In Use Disks 3
s Spare Disks 3
O Foreign Disks 28
------ ------------- -----
Total 34 disks
2. After verifying that the disks are visible to the destination system as foreign devices,
enter the following command.
# system headswap
The system responds:
This command returns the system back to its prior operational

conditions. The system will be rebooted before resuming normal
operations.
** If system passphrase was set on the old head, you will

need to do one of the following after headswap completes:
- unlock the filesystem if you have encrypted data,
or
- set the system passphrase if you don't have encrypted
data
Are you sure? (yes|no|?) [no]: yes
ok, proceeding.
Please enter sysadmin password to confirm 'system headswap':
This command may take several minutes to complete; please wait.

Restoring the system configuration . . .
Success
deployment chassis replacement..........[start]
Reassemble external shelf...............[OK]
Save external storage UUID to Head .....[OK]
Save head serial to external storage ...[OK]
Mount management volume.................[OK]
deployment chassis replacement..........[done]
This command might take 30 minutes or longer to complete, depending on the

number of shelves and the amount of data on the shelves. The system should reboot
automatically.

3. Log in with the original source system password (not the serial number).
4. Verify the health of the file system by entering the following command.
# filesys status
If the file system is encrypted and locked, the system prints the following message.
The filesystem is locked: Use 'filesys encryption unlock'

to enter the passphrase.
Do the following to unlock the encrypted file system.
a. Contact the customer security officer and, when that person arrives, enter the
following command.
# filesys encryption unlock
b. Have the security officer enter the passphrase.

5. Reboot the system. A reboot is necessary to ensure initiation and completion of an
index rebuild. Wait until the indexing process is complete before proceeding.
Note
The index rebuild process can take up to 4 hours. Do not power off the system during
this process.
6. To check on the status of the upgrade and the index rebuild, enter the system
upgrade status command, which shows the estimated time remaining for the
upgrade.
sysadmin@sif# system upgrade status
Thu May 2 15:22:50 PDT 2013
Current upgrade status: upgrading file system
Time remaining: 240 minutes Start: 14:20:54
Stage: index_rebuild Status: running
Reason: none
7. When the upgrade is complete, enter the filesys status command.
8. If the filesys status output shows that the file system is disabled or locked,
enter the following command.
# filesys enable
9. Use the following command to confirm that the correct amount of storage is
connected.
The output of this command should show approximately the original amount of
storage space. The output from a filesys show space command may vary from
original source system as there will be minor differences in the space needed for DD
OS from release to release.
10.If it is necessary to change the hostname, do so now. Also make the necessary
configuration changes in the backup applications that use the old hostname.
You might want to change the hostname if the existing host name contains the model
number of the old controller. The hostname may be defined in DHCP or with net set
hostname.
Configuring the destination controller 23

Upgrade Guide
Note
Some backup applications do not tolerate hostname changes. Verify that all backup
applications will tolerate the update before changing the hostname.
11.Reset the system passphrase using the following steps.

a. Run the command system passphrase set to reset the passphrase to the
same passphrase as before the headswap.
b. To use the imported host certificate, restart the web server using the following
commands.
# adminaccess disable http/https
# adminaccess enable http/https
12.Verify that all licenses installed on the source controller migrated to the destination
controller.
# license show
Verifying the DD Extended Retention configuration

If the DD Extended Retention option was configured on the source controller, use this
procedure to verify that it is properly configured on the destination controller.
Procedure
1. Check that the following matches the original settings recorded while preparing for
the upgrade.
# storage show all
# archive show config
# archive data-movement policy show
2. If space-reclamation was suspended earlier, it can be resumed here.
# archive space-reclamation resume
3. Confirm that space-reclamation has resumed and is now running with:
Restoring and verifying the SCSI Target configuration

If VTL or DDBoost over Fibre Channel services were configured on the source controller,
use this procedure to restore and verify the configuration on the destination controller.
Procedure
1. Enable SCSITARGET.
a. Determine if SCSITARGET is enabled.
# scsitarget status
b. If SCSITARGET is not enabled, enable SCSITARGET.

# scsitarget enable
2. If VTL was used on the source system, enable VTL.
a. Determine if VTL is enabled.
# vtl status
b. If VTL is not enabled, enable VTL.

# vtl enable

3. Display the Fibre Channel port information on the destination system.

# vtl port show hardware
To view this information in the autosupport file, search for SCSITARGET Endpoint Show
Detailed or Enclosure Show All. To view this information in DD System Manager, select
Hardware > Fibre Channel > Physical Resources.
4. If you did not complete the Fibre Channel port mapping table when you collected
information from the source system, use the information from the source system
autosupport file to complete the table.
To view this information in the autosupport file, search for SCSITARGET Endpoint Show
Detailed or Enclosure Show All.
5. Update the endpoints on the destination controller as follows:
a. Display the current endpoint list.
b. Disable all endpoints.

# scsitarget endpoint disable all
c. Delete each automatically created endpoint.

# scsitarget endpoint del ep-new
The command syntax is scsitarget endpoint del endpoint-spec. Repeat

this command using the name of each automatically created endpoint.
d. Reassign each of the migrated endpoints to the correct port.

# scsitarget endpoint modify endpointfc-0 system-address 4a
The command syntax is scsitarget endpoint modify endpoint-spec

system-address address. Replace endpoint-spec with the endpoint name and
address with the new port number.
e. Verify that the endpoints match the table.

f. Enable the updated endpoints.

# scsitarget endpoint enable all
6. Connect the SAN cables to the Fibre Channel ports on the destination system.
To avoid switch zoning and initiator configuration issues, the best practice is to
reconnect newly mapped ports in the destination system to the same SAN port based
on the Fibre Channel port mapping. For example, if source port 5a is mapped to
destination port 6a, connect 6a to the same switch port (assuming it is in a fabric
configuration) to which port 5a was connected.
7. Verify that all of the devices are visible in the group with the new port numbers.
# vtl group show groupname
8. Verify that all VTL option settings are set correctly.
# vtl option show all
9. Update access groups.
# scsitarget group modify
# vtl group modify
Restoring and verifying the SCSI Target configuration 25

Upgrade Guide
Use the commands listed above to update the primary and secondary port configured
for all access groups based on the Fibre Channel port mapping.
Verifying the network configuration and connectivity

Network connectivity is required for system access and for alert and autosupport report
forwarding. It is a good practice to verify the configuration and network connectivity after
a controller upgrade.
Procedure
1. To view the current network configuration, use the following commands.
# net show settings
# net show config
2. Compare the current network configuration to the map tables recorded earlier. As
needed, refer to the specific DD OS Initial Configuration Guide for information on
network configuration.
Note
The replacement system has a different host and BMC MAC address, so it might
receive a different IP address from a DHCP server.
3. Use the net ping command to verify connectivity to the default gateway.
If the net ping command is unsuccessful, resolve the problem before continuing to the
next task.
Verifying CIFS, NFS, and DD Boost connectivity

Follow the steps that apply to the communication protocols that the system uses.
Procedure
1. If CIFS is configured in active-directory authentication mode, check for domain
connectivity by running:
# cifs troubleshooting domaininfo
2. Examine the command output. If lsa-activedirectory-provider status is
unknown, rejoin the domain by running the command:
# cifs set authentication active-directory realm
Note
An extra step is required if CIFS was in Workgroup mode prior to headswap. In this
case, to join an Active Directory domain after the headswap, run the cifs reset
authentication command prior to joining the domain.
3. Verify CIFS connectivity by remounting any CIFS shares and verifying the operation of
the backup application. Run these commands:
# cifs status
# cifs show active
If you are not able to reestablish CIFS connectivity, contact EMC Support for
assistance.

4. Verify NFS connectivity by remounting any NFS shares and verifying the operation of
the backup application. Also run this command:
# nfs show clients
5. Verify DD Boost connectivity by running these commands:
# ddboost show user-name
# ddboost storage-unit show
# ddboost status
# ddboost fc status
Verifying the file system status

The file system should be enabled at least once with all the external shelves attached to
complete the upgrade.
Procedure
1. Run the following commands again and compare their output with the output prior to
the head swap. The outputs should be identical, except for cases where port numbers
have changed (the system show ports command, for example). If other aspects
of the output do not match, contact customer support.
# disk show state
# disk status
# disk show hardware
# system show ports
# disk multipath status
# enclosure show topology
2. Check that the encryption, snapshot, and retention lock settings match the original
configuration.
Verifying the Replication status

Procedure
1. Enable replication.
# replication enable
2. Run the following command and compare the output with the output prior to the head
swap. Verify that the number of contexts and the configuration is the same as before.
3. Run the following command, verify the active status of each context, and make sure
all contexts are enabled and connected. This verification requires that all replica
systems are in an active state. If a replica system is not active at the time, re-verify
when it is.
# replication status all
Updating IPMI remote access

Procedure
1. Enter the following commands.
# ipmi show config
# ipmi config port {dhcp | ipaddress ipaddr netmask mask
gateway ipaddr}
2. Add users back with the following command.
# ipmi user add user {password password}
Verifying the file system status 27

Upgrade Guide
Generating an Autosupport report

When the upgrade and the destination controller configuration are complete, it is a good
practice to generate and save an autosupport report with the complete system
configuration.
Before you begin
Verify the network configuration and connectivity to the default gateway before starting
this procedure.
Procedure
1. To verify that the system can send email messages, use the autosupport test
email youremail command to send a message to yourself and verify that you received
the email.
If the test email is unsuccessful, resolve the problem before continuing to the next
step.
2. To capture the destination controller configuration, generate an autosupport report
and send it in an email message to yourself.
# autosupport send username@yourcompany.com

Copyright © 2015 EMC Corporation. All rights reserved. Published in USA.
Published April, 2015
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
Generating an Autosupport report 29

302-001-639 Rev 01 EMC Data Domain System Controller Upgrade Guide 5.6

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

302-001-639 Rev 01 EMC Data Domain System Controller Upgrade Guide 5.6

Hochgeladen von

Copyright:

Verfügbare Formate

Upgrade Guide

EMC® Data Domain® Operating System

System Controller Upgrade Guide

Revision Date Description

Tools and supplies needed

Table 2 Data Domain system upgrade options

Existing Memory Upgrade to Memory Comments

DD690 16-24 GB DD890 96 GB Cannot support

DD690 16-24 GB DD990 128 GB or 256 GB Cannot support

DD690 16-24 GB DD4200 128 GB Cannot support

2 EMC Data Domain Operating System 5.6 Upgrade Guide

Table 2 Data Domain system upgrade options (continued)

Existing Memory Upgrade to Memory Comments

DD690 16-24 GB DD7200 128 GB or 256 GB Cannot support

DD860 36 GB or 72 GB DD990 128 GB or 256 GB

DD860 36 GB or 72 GB DD4200 128 GB

DD860 36 GB or 72 GB DD4500 192 GB

DD860 36 GB or 72 GB DD7200 128 GB or 256 GB

DD860 with 36 GB or 72 GB DD990 with 256 GB

DD860 with 72 GB DD4200 with 128 GB

DD860 with 72 GB DD4500 with 192 GB

DD860 with 72 GB DD7200 with 256 GB

DD880 48 GB or 64 GB DD890 96 GB Cannot support

DD880 48 GB or 64 GB DD990 128 GB or 256 GB Cannot support

DD880 48 GB or 64 GB DD4200 128 GB Cannot support

DD880 48 GB or 64 GB DD4500 192 GB Cannot support

DD880 48 GB or 64 GB DD7200 128 GB or 256 GB Cannot support

DD890 96 GB DD990 128 GB or 256 GB

DD890 96 GB DD4200 128 GB Maximum capacity

Table 2 Data Domain system upgrade options (continued)

Existing Memory Upgrade to Memory Comments

DD890 96 GB DD7200 128 GB or 256 GB

DD990 128 GB or 256 GB DD9500 256 GB for up to 864 ES20 Expansion

DD4200 128 GB DD4500 192 GB

DD4200 128 GB DD7200 128 GB or 256 GB

DD4200 with 128 GB DD4500 with 192 GB

DD4200 with 128 GB DD7200 with 256 GB

DD4500 with 192 GB DD7200 with 256 GB

DD7200 128 GB or 256 GB DD9500 256 GB for up to 864 ES20 Expansion

Upgrade planning considerations

4 EMC Data Domain Operating System 5.6 Upgrade Guide

2. Prepare the destination controller.

6 EMC Data Domain Operating System 5.6 Upgrade Guide

l The following are ES20 cabling guidelines.

Table 3 Controller with SAS HBA to ES30 cable options

Cable Part Number Cable Length Vertical Span, RU

X-SAS-MSMS1 1 m. (39 in.) 9

X-SAS-MSMS2 2 m. (79 in.) 31

X-SAS-MSMS3 3 m. (118 in.) 53

X-SAS-MSMS5 5 m. (196 in.) 97

Table 4 ES30 to ES30 cable options

Model Code Cable Length Vertical Span (RU)a

X-SAS-MSMS1 1 m (39 in.) 9

X-SAS-MSMS2 2 m (79 in.) 31

X-SAS-MSMS3 3 m (118 in.) 66

X-SAS-MSMS5 5 m (196 in.) 97

Table 5 Controller with SAS HBA to ES20 cable options

Cable Part Number Cable Length Vertical Span, RU

X-SAS-MSIB1 1 m. (39 in.) 16

X-SAS-MSIB2 2 m. (79 in.) 39

X-SAS-MSIB5 5 m. (196 in.) 106

8 EMC Data Domain Operating System 5.6 Upgrade Guide

Figure 3 Mini-SAS cable for ES20 to ES20 connections

Table 6 ES20 to ES20 cable options