Purity//FA Upgrade Guidelines and Overview

Summary
This document is designed to provide an understanding of the Purity software upgrade process from beginning to end
while outlining the critical milestones.
Please see the critical milestones chart and detailed summaries below.

Legend

Indicates a change on the array; no

Informational
impact expected.

A vital step in the upgrade process

Imperative to ensure a successful Non-
Disruptive Upgrade.

A critical event will occur and may

Critical
have an impact.

©2020 Copyright Pure Storage. All rights reserved.

1
Milestones

For the best availability, customers should log a request

with Pure Support a minimum of 2 days in advance of
the preferred upgrade maintenance window

1. Engagement Expectations A maintenance window will be booked with the Pure

Upgrade team. Availability is based on the upgrade
path, estimated time duration and availability of the
Upgrade team at that date/time

Confirming the customer's communication preference

and requesting for Remote Assist on the array.

Staging of code and upgrade scripts, provide health

check outcome and request the customer to confirm
2. Staging of Code and Health Checks environmental Best Practices and Caveats are being
followed.

Please note: The maintenance window booked with Pure

Upgrades team is dependent on the successful
completion of these pre-upgrade health checks

3. Pre-Upgrade Tasks
Confirm Remote Assist on the array is open and obtain
explicit permission to execute the upgrade.

Run live health checks, install new Purity version, reboot

the controller, then run live health checks again.

4. Purity//FA Install - Secondary Controller

 Critical: This step may be impactful to front
end IO as the secondary controller is
rebooted.

5. Purity//FA Install - Primary Controller Run live health checks, install new Purity version, reboot
the controller, then run live health checks again.

©2020 Copyright Pure Storage. All rights reserved.

2
  Critical: This step may be impactful to front
end IO as the primary controller is
rebooted and failover will occur.

6. Final Upgrade Review Final live health checks are executed, review if firmware
updates are needed and final closure of the case.

Detailed Phases

Phase 1: Engagement Expectations

A maintenance window
will be booked with the
Pure Upgrade team.
Availability is based on the
upgrade path, estimated
time duration
1.1 and availability of the
Upgrade team at that date/
time

Confirming the customer's

communication preference
and requesting for Remote
Assist on the array.

©2020 Copyright Pure Storage. All rights reserved.

3
 Please note: The
maintenance window
booked with Pure
Upgrades team is
dependent on
the successful completion
of pre-upgrade health
checks defined in Phase 2
below.

Support will confirm with

the customer on their
1.2
preferred communication
methods

Support will confirm the

customer to open a
1.3
remote assist session
(RA) on the array(s)

Phase 2: Staging of Code and Health Checks

Two business days prior to the upgrade window, a Technical Support Engineer will communicate with the
customer to do the following

Stages code on the array

reviewing pre-upgrade
health checks. This
includes the new Purity
installation package(s),
and an upgrade health-
2.1 check script. The staging
timeframe depends on the
connection speed. It
averages between one
and two hours, but at
some sites, it can
take longer.

Connects to the array and

runs the health-check
2.2 scripts. These health
checks help to determine if
there are any current

©2020 Copyright Pure Storage. All rights reserved.

4
 upgrade blockers and
verify host I/O balance,
SAS cabling, and
hardware health.

Report to the customer

results of the health
checks, how to address
2.3 issues if there are any,
and communication
methods during the
upgrade.

Request the customer to

confirm they are following
2.4
our Best Practices and
Caveats.

Phase 3: Pre-Upgrade
Approximately 1-2 hours prior to the upgrade window, the Technical Support Engineer will perform the
following:

If the RA session was

opened over 48 hours
3.1 before the upgrade
window, it will time out,
requiring re-opening.

©2020 Copyright Pure Storage. All rights reserved.

5
 The engineer will re-stage
and run health checks
3.2
confirming the array is
ready to upgrade.

The engineer will re-stage

and run health checks
confirming the array is
ready to upgrade.

Obtain explicit
permission to execute the
upgrade from the
3.3 customer based on
communication
expectations during Phase
1.

Phase 4: Purity Install on the Secondary Controller

At the start of the upgrade window, the Technical Support Engineer will perform the following:

The engineer connects to

the primary controller and
runs the upgrade script.
4.1
This script runs health
checks on the array, which
also include:

a. Checking for balanced

IO from the connected
hosts.

b. Confirming host
connections remain

©2020 Copyright Pure Storage. All rights reserved.

6
 connected to at least a
single controller through
the process.

Confirm all live health

4.3
checks are successful.

Await for the Secondary

4.4 boot partition to be
created.

Reboot the Secondary

4.5
controller.

Once the Secondary is

4.6 back up, Pure will run live
health checks again.

Phase 5: Purity Install on the Primary Controller

After the Secondary Controller has come back online, the Technical Support Engineer will perform the
following:

The engineer connects to

the Primary Controller and
runs the upgrade script.
5.1
This script runs health
checks on the array, which
also include:

a. Checking for balanced

IO from the connected
hosts.

b. Confirming host
connections remain
connected to at least a
single controller through
the process.

Confirm all live health

5.2
checks are successful.

©2020 Copyright Pure Storage. All rights reserved.

7
 Await for the Primary
5.3 Controller boot partition to
be created.

Failover will be issued to

5.4 promote the Secondary
Controller to Primary.

The new Secondary

Controller will be rebooted
5.5
to the new Purity boot
partition.

Once the Secondary

Controller is back up, Pure
5.6
will run live health
checks again.

If the Purity//FA Upgrade consists of going through multiple code levels, Phase 4 and Phase 5 will be repeated.

Phase 6: Post-Upgrade Tasks and Health Verification with

Customer
The Technical Support Engineer will perform the final verification:

After the final health

checks are done, there is
6.1
a possibility the array may
need firmware updates.

a. Firmware updates are

designed to be non-
disruptive.

b. Updates may include

NVRAM, FlashModules,
DFS and/or shelf IOM/
controllers.

©2020 Copyright Pure Storage. All rights reserved.

8
 c. The expected time can
range from 10 minutes to
several hours.

d. The engineer will

monitor and communicate
all updates, along with the
completion of firmware
updates.

Final confirmation with the

customer their
6.2
environment is still
healthy.

Final closure of the

6.3
support case.

Disclaimer: The timeframe of the Purity upgrade depends on the health of the customer environment and if it is a single-
hop or a multi-hop upgrade. If we run into health concerns during the upgrade, we will ask the customer to confirm or
correct the issue before moving forward. Single hop upgrades require one reboot of each controller for a total of two
reboots, which may take approximately 60 minutes. If it is a two or three-hop upgrade, it requires four or six reboots
respectively, (for approximately 120 or 180 minutes respectively).

©2020 Copyright Pure Storage. All rights reserved.

9