Professional Documents
Culture Documents
Dell+PowerProtect+DD+System+Upgrade+-+Participant+Guide
Dell+PowerProtect+DD+System+Upgrade+-+Participant+Guide
Dell+PowerProtect+DD+System+Upgrade+-+Participant+Guide
DD SYSTEM UPGRADE
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Dell PowerProtect DD System Upgrade
Only DDOS 6.2 and later supports MTree and managed file replication.
Dell Technologies recommends that systems that are paired in a
replication configuration should have the same version of DDOS.
• Upgrading the DDOS ensures better compatibility with backup host
software. Administrators upgrading backup host software should
always check the minimum DDOS version that Dell Technologies
recommends for your backup software. Go to the Dell Support website
and view the current DDOS Release Notes to learn more about the
supported backup host software.
• You can correct unexpected system behavior by upgrading to a more
current DDOS. No software is free of flaws, and Dell Technologies
works continuously to improve the functionality of DDOS. Each version
release has complete release notes that identify issue fixes by number.
DDOS provides the agility, security, and reliability that enables the
platform to deliver scalable, high-speed, and cloud-enabled protection
storage for backup and archive.
By upgrading to the latest release, you ensure that you are running the
version of DDOS with the highest reliability status.
Only those services that depend on the component that the MDU
upgrades are disrupted. The MDU feature can prevent significant
downtime while performing other operations during certain software
upgrades.
You can also check the currently running version using the command-line
interface command, system show version.
Once you verify the DDOS compatibility with the various software
applications and hardware devices that your protection system uses, you
can prepare to upgrade.
Preparing to Upgrade
If you determine that you must update your system with an MDU, do the
following:
• Upload the MDU bundle mdu-update-bundle--
releases.rpm according to the version running on the system,
update mdu-bundle-x.x-releases.rpm. Upload the RPM to the
same location as a system RPM, /ddvar/releases/.
• Perform a system update with the MDU RPM, which should take a few
minutes.
• After you complete the MDU update, you can move on to complete the
update to the target version of DDOS.
Pre-Upgrade Considerations
− Confirm that the file system is enabled after the preupgrade reboot.
− Ensure that no new alerts appear after the preupgrade reboot.
Verify the compatibility of the target DDOS with the various software
applications, and hardware devices that are related to your system. When
you verify compatibility, you can prepare to upgrade.
Upgrade Precheck
Begin the system upgrade. Go to Maintenance > System and perform the
UPGRADE PRECHECK.
The aim of the precheck is to detect potential problems early and cancel
the upgrade. If you perform the upgrade without a precheck, you might
place the system in an unusable state after an upgrade attempt.
To perform the upgrade from the DD System manager, ensure that the
system is idle. Confirm that all replication initialization and
resynchronization operations are complete and that no backup operations
are running. The alert show current CLI command is a useful
command to assess the readiness of the system.
Overview
Download the DDOS update package1 from the Dell Support website.
1Download the DDOS update package with the prefix x.x.rpm, for
example, 7.11.0.0-1035502.rpm.
When the update package uploads to the DDMC inventory, you can
update one or more systems.
4. From the Select Systems page, select a system from the Available
Systems list and then click Add.
5. Click Next.
6. From the Select Package page, select the update package to apply to
the previously selected system or systems. Click Next.
− If the update package exists in the system, continue to the next
step.
7. The Schedule page depends on the option that is selected on step
number three:
− When you select Download Package Only,choose when to
download the package and then click Next.
− When you select Install Update Only, choose when to install the
update and then click Next.
− When you select Download Package and Install Update, choose
when to download the package and when to install the update and
then click Next.
8. From the Summary page, review the summary, and if applicable,
select Reboot before installation. Click Finish.
− Rebooting the system lets the update continue without any conflicts
from background processes.
• The partition size check verifies that the /ddr and /(root) partitions
are correct.
• The system performs a check on the redundant array of independent
disks (RAID) to ensure the core operating system disks are available
on the head unit.
• The precheck also determines whether the file system is enabled and
verifies that the numbers of MTrees and Virtual Tape Library (VTL)
pools are less than 100.
• An operations check ensures that the system is not performing file
system cleaning, cloud cleaning, and data movement operations.
You can view the status of an upgrade using the DDOS command,
system upgrade status. Log messages for the upgrade are
stored in /ddvar/log/debug/platform/upgrade-error.log
and /ddvar/log/ debug/platform/upgrade-info.log.
You can review and capture the file content using the log view
debug/platform/upgrade-err.log log view
debug/platform/upgrade-info.log command.
Upgrade Preparation
There are various methods to upload the DDOS upgrade package to the
PowerProtect DD System:
− The rpm file name is the DDOS upgrade file, for instance
7.13.0.0-1076200.rpm.
Use the commands below to perform a system health check and ensure
that there are not alerts on the system:
The precheck does not upgrade or modify the system, and it does not
impact system performance. The precheck evaluates a set of
parameters and indicates whether or not there are any issues that
might prevent an upgrade.
4. Upgrade the system using the system upgrade start <rpm
file name> command.
a. The rpm file name is the DDOS upgrade file, for instance
7.13.0.0-1076200.rpm.
System Reboot
When the upgrade is nearly complete, the system shuts down the file
system and reboots.
Use the commands below to perform a system health check and validate
that the DDOS upgrade is completed and the system is up and running:
5. Run the ha status command to verify that the node 1 is the active
9. Run the ha status command to verify that the node 0 is the active
Upgrade Phases
Upgrade Timeout
A short message service (SMS) task controls the pre-reboot phase of the
DDOS upgrade. The task regularly examines the progress of the upgrade
to confirm that the upgrade proceeds as it should. In some circumstances,
the pre-reboot stage of the upgrade may take longer than the timeout set
by the SMS task. At the timeout, usually 20 minutes, the SMS task
terminates without warning. The system does not attempt any further
If you suspect that the upgrade process stalls or stops due to a timeout,
you can review SMS logs during the timeframe of the upgrade. The SMS
logs are in /ddr/var/log/debug/sm/sms.info.
Running Tasks
The following circumstances could cause the upgrade to fail when some
tasks are running:
Configuration Issues
The following circumstances could cause the upgrade to fail when the
system is configured incorrectly:
Space Issues