Вы находитесь на странице: 1из 4

KNOWLEDGE BASE

Restricted View

Knowledge Base Article: 000468625


General Data Domain Operating System Upgrade Instructions (000468625)

Version: 2 Article Type: Break Fix Audience: Level 30 = Customers Last Published: Sun Feb 21 02:20:16 GMT 2016

Summary: Steps to upgrade or perform an upgrade.


Issue: The purpose of this KB article is to cover the general steps on how to perform an upgrade on a Data Domain system. For
exceptions and known issues on a specific DD OS, please refer to the release notes for the relevant release at DD OS
Support Page.

This is general DD OS upgrade instructions.The Data Domain operating system requires an upgrade.

Cause: The Data Domain system is required to upgrade to resolve any known issues or to utilize new features.

Resolution:
Typically when upgrading the DD OS, we only support the ability to upgrade two release families at a time (e.g., 4.9 to
5.1 or 5.0 to 5.2). An exception to this rule is target release family 5.4 that can be upgrade up to three family releases at
a time (i.e., from DD OS 5.1, 5.2 and 5.3). For all others, in order to upgrade from a release that is earlier than two
families you will need to upgrade in steps.

Please see the latest code family (e.g. 4.9, 5.0, 5.1, 5.2, etc.) Release Notes for upgrade instructions as appropriate for
the version your system is currently running for exact upgrade steps. The most current release notes for all versions can
be found online at https://support.emc.com/products/32697_DD-OS after selecting the appropriate target DD OS release.

Make sure to review the specific release notes for the exact DD OS you are upgrading to. Please pay particular attention
to,

Data Domain model compatibility (see "Supported Systems" section)


Any known issues or exceptions (see "Known Issues and Workarounds" section)

For out-of-family upgrades (e.g. 4.9.x.x to 5.1.x.x; 5.0.x.x.to 5.1.x.x, etc.) please review the following documents:

1. Backup Compatibility Guide (under Documentation per DD OS on support.emc.com)

2. Data Domain Archive Compatibility Matrix (only for Archiver-enabled DD systems)

3. Data Domain Boost Version Compatibility Guide (if DDBOOST is licensed)

4. Data Domain Storage Array Compatibility Guide (if the DD system is connected to a SAN)

Note: After the completion of each upgrade to a new release family, it is recommended that you perform a spot check of
the upgraded system by verifying the expected files are present and readable from either a CIFS, VTL, or an NFS client.

5.2 upgrade notes: On some systems upgrading to 5.2 it could potentially take up to four hours for the upgrade to
complete. This is due to container index updates to prepare for ICV (Inline Container Verification). To avoid an extended
upgrade time it is recommended to upgrade to either 5.2.3.1 or 5.2.4.0. For more details, please review the below
articles:

New Procedures for Upgrade Process for DD OS 5.2


Upgrade to DD OS 5.2 is slow

Upgrade Steps

Note: If you are using Avamar Server to backup the Data Domain device, please make sure to set the server in a known
good controlled state before proceeding with the Data Domain upgrade. To perform this follow the instructions in article
187179 - How to Set Avamar Server into a Known Good Controlled State
1. Before beginning the upgrade process, reboot the Data Domain system. Once the system has restarted, verify that the
system is running in a clean state (i.e. no hardware failures or active alerts). Note: If any alerts or failures are
encountered, contact Data Domain support before proceeding.
2. Make sure that the system is idle. All replication initialization must be complete and no backups should be running.
3. Open a web browser and log into DD OS Support Page.
4. Under Products in the center column, click on the DD OS family release you wish to download (e.g. DD OS 5.4).
5. Under Downloads in the center column, click on Data Domain DD OS x.x.x.x Software Installation, where 'x.x.x.x' is
the code release you are planning to upgrade to. The download should begin automatically. Note: If the download does
not start, check your browser's security policies and try again.
6.
6. Store the .rpm file on the Data Domain system in the directory /ddvar/releases
For directions on how to transfer the .rpm file to the /ddvar/releases folder follow the steps outlined in the articles
below:
Copying the .rpm File via CIFS
Copying the .rpm File via NFS
Copying the .rpm File via FTP

Note: When downloading a Data Domain system software upgrade image using Internet Explorer, the browser may add
bracket and numeric characters to the upgrade image name. Remove the added characters before running the system
upgrade command. Do not make any other modifications to the software package name as upgrade processes and
procedures rely on the package names as they are.

1. For systems that are already part of a replication pair before the upgrade, do not disable replication on either system in
the pair.
For one direction replication pair upgrade the destination (replica) before upgrading the source
(originator).
For pairs replicating both directions the upgrade order is irrelevant.
1. If you are upgrading from DD OS 5.4.0.0 or later, after uploading the RPM to the required path, run the below pre-check
command and make sure it gets successful before proceeding for upgrade.

# system upgrade precheck <RPM File Name>

Note: This command should be run only in DD OS 5.4.0.0 or later. Running it in 5.2 or 5.3 could result in actual upgrade
instead of only pre-check.

It is by default a verbose command that gives a descriptive output. If it fails, it displays at which step and the reason
because of which it has failed helping to diagnose for that specific issue. Below are KB articles that indicate a few of
such issues.
https://support.emc.com/kb/184707 (Level-40 EMC internal article for Employees and Partners only)
http://support.emc.com/kb/182194 (Level-40 EMC internal article for Employees and Partners only)

2. If the system is NOT running DHCP, check the registry to ensure that the default gateway matches current config. "reg
show config.net.default_gateway" and "route show gateway"
3. Stop (log out from) all Data Domain Enterprise Manager sessions on the Data Domain system.
4. Stop any active CIFS client connections before starting the upgrade. Use the cifs show active command to check for
CIFS activity. Disconnect any client that is active. On the client, enter the command net use \\dd\backup /delete
5. Upgrade the system:
To upgrade issue the command:

# system upgrade <filename.rpm>

For Example:

# system upgrade 5.0.3.0-279000.rpm

Note: During the upgrade process the system will perform a reboot. It can take up to 20 minutes before the system boots
back up. It will take roughly 30 minutes or more after the upgrade for the file system to come back online. If it is checked
before then you may see errors like:

The filesystem has encountered a problem.


Please remain patient as this error only means the file system is not up yet. Eventually you will see this message when
checking the file system just before it becomes available:

The filesystem is enabled and starting up. Please wait.


**** The filesystem is not responding.

If you have upgraded to DD OS version 5.2 or higher you can utilize the following command to verify the status of the
upgrade:

# system upgrade status

If you are not upgrading to DD OS 5.2 and the filesystem does not come back up after 1 hour or if the Data Domain
system fails to boot up please Create a service request.
1. (Optional for customers with the OST plug-in) After upgrading, enter:

# nfs show clients


If the output is,

path = /backup/ost option = ( , , ,secure)


enter the commands,

# ost disable

# ost enable
After disabling and re-enabling OST, re-enter the nfs show client command and you should see the
output as shown in the following example:
# nfs show clients
path = /backup/ost option = ( , , ,insecure)

Other Notes:

When upgrading, the following error may display:

[UPGRADE]: Find DDOS rpm at /ddr/var/releases/<filename.rpm>

[UPGRADE]: Check DDOS rpm .........[failed]

DDOS upgrade failed with error!


If you see this error, the .rpm file you downloaded to your Data Domain system was probably corrupted during the
download. Make sure to set the transfer mode to binary (the default is byte) when downloading the .rpm file from the
website.

With collection replication, no files are visible on the destination if replication was not finished before starting the
upgrade. After the upgrade, wait until replication completes to see files on the destination.
If you are performing an upgrade on a Global Deduplication Array (GDA) make sure to run the system upgrade
command on the master controller. This action will upgrade and reboot all controllers.

What To Do if the Upgrade Fails

Here are a list of scenarios that might denote the upgrade has failed:

The system does not come back up after the upgrade reboot in over an hour.
The system is up, but the filesystem has failed to come back online in over an hour.
The system is up, but commands are not working and have been that way for over an hour.

In either of the above scenarios, do not attempt to reboot the system again. Background processes may be running for
the upgrade which would be interrupted if a reboot occurs. If you suspect that the upgrade has failed for reasons outside
of the above scenarios, please refer to the Confirm DDOS Upgrade Has Failed Document for directions on how to
proceed. Otherwise, Create a service request to get immediate assistance.

Note: Currently, there are no methods to "roll back" an upgrade to the previous version if there are difficulties. In the
instance a case must be opened on a problem with the upgrade; support will work to make sure the upgrade is
successful and that the system comes back up on the new intended version.

Upgrade Using the Enterprise Manager

Data Domain devices running DD OS version 5.0 or higher have the ability to perform the upgrade using the Enterprise
Manager.

1. View and upload the upgrade package.


On the Navigational pane click Maintenance > System
Here you will be able to view the list of upgrade images ( .rpm files) currently stored on the Data
Domain controller under section Upgrade Packages Available on Data Domain System.
To upload an upgrade package click Upload Upgrade Package located in the same area.
Click Browse and use the file navigator to locate the rpm file you have previously downloaded, select
this file and click Open.
Click OK.
1. Perform the upgrade.
Under section Upgrade Packages Available on Data Domain System, click in the checkbox of the
image to use for the upgrade.
Click Perform System Upgrade. The Upgrade System dialog box will appear.
Verify the version of the target image (the upgrade image) and click OK.

A progress dialog box will appear and when full it will advise that the system is going to
reboot in order to complete the upgrade. During the reboot, the connection with the system
will be lost.

Once the reboot completes, log back into the system to verify the upgrade completed
successfully.

Note: Maximum of five upgrade packages can be uploaded using the Enterprise Manager. To remove an upgrade image
click Remove Upgrade Package after clicking the checkbox of one or more images listed in the Upgrade Packages
Available on Data Domain System section.

Upgrade Using a USB Key

On the USB key, create the directory /upgrade.


Log into Feedback central at https://feedbackcentral.emc.com/login.html
Download the target release onto the USB key.
Make sure that the RPM file is under the /upgrade directory.
Plug in the USB key to any one of the USB ports on the back of the restorer.
On the restorer, run the system upgrade command with the name of the RPM that is on the USB key.
The upgrade process automatically looks at the USB ports if it does not find the RPM name elsewhere.
Notes:
REFERENCE:

Confirm DDOS Upgrade Has Failed


Monitoring your upgrade to 5.2 and later releases
Upgrade to DD OS 5.2 is slow

Notes (Restricted):
INTERNAL NOTES

If the customer is upgrading to address a specific bug, make sure to link the release notes containing the bug and any
other documentation that addresses the bug to the case.

Product: Data Domain,

Problem Code: Upgrade

Shared: Yes

Core SFDC ID: 000181889

Legacy Solution ID: dd85200

Article Properties: Validation Status: Approved Original Create Date: Mon Jan 02 00:00:00 GMT 2012

Channels: Customer , Internal App First Published: Fri Feb 05 16:52:02 GMT 2016

Originally Created By: Ryan Montgomery Last Modified: Sun Feb 21 02:20:16 GMT 2016

Вам также может понравиться