Dell VNXe3200 Upgrading the VNXe Software - Page 11

Time needed to complete an upgrade, I/O activities during an upgrade

Get Dell VNXe3200 PDF manuals and user guides View all Dell VNXe3200 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 11 highlights

Plan the upgrade It is recommended that you always verify that the software update file is valid and not corrupt using the MD5 checksum. l Large and complex configurations The pre-upgrade health check may fail if the system exceeds the total number of allowed file systems and snapshots. Refer to the Unisphere Online Help for more information on such limitations. When this occurs, the system will recommend that users delete some of the snapshots to enable the upgrade. Time needed to complete an upgrade The total estimated time for an upgrade is around 1 hour and 15 minutes. It may change based on the I/O activities and other factors specific to your environment. Do not take actions, such as closing and opening the Web browser or power cycling the SPs in the middle of an upgrade. The upgrade retains your existing configuration settings. This includes the IP addresses you configured for the system (static or dynamic). Note OE software updates sometimes include disk firmware updates. In such cases, the upgrade may take a bit longer to complete. I/O activities during an upgrade Unisphere may be temporarily disconnected during the upgrade. Once the upgrade is complete, it will automatically be reconnected. It is recommended that you quiesce all IO activity before you proceed with the upgrade. The upgrade may be disruptive in the following scenario. For the following cases, perform the upgrades during maintenance windows: l Major software updates may include changes to the VNXe high availability and cluster services. When upgrading to such software versions, there may be some downtime required. l In the case of large and complex configurations, the pre-upgrade health check may fail if the system exceeds the total number of allowed file systems and snapshots. When this occurs, the system will recommend that users delete some of the snapshots to enable the upgrade. l In some cases, the ESX servers may require manual refreshes to reconnect to the datastores. Note Disk firmware and language pack upgrades are not disruptive. Time needed to complete an upgrade 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
It is recommended that you always verify that the software update file is valid
and not corrupt using the MD5 checksum.
l
Large and complex configurations
The pre-upgrade health check may fail if the system exceeds the total number of
allowed file systems and snapshots. Refer to the Unisphere Online Help for more
information on such limitations.
When this occurs, the system will recommend that users delete some of the
snapshots to enable the upgrade.
Time needed to complete an upgrade
The total estimated time for an upgrade is around 1 hour and 15 minutes. It may change
based on the I/O activities and other factors specific to your environment. Do not take
actions, such as closing and opening the Web browser or power cycling the SPs in the
middle of an upgrade.
The upgrade retains your existing configuration settings. This includes the IP addresses
you configured for the system (static or dynamic).
Note
OE software updates sometimes include disk firmware updates. In such cases, the
upgrade may take a bit longer to complete.
I/O activities during an upgrade
Unisphere may be temporarily disconnected during the upgrade. Once the upgrade is
complete, it will automatically be reconnected.
It is recommended that you quiesce all IO activity before you proceed with the upgrade.
The upgrade may be disruptive in the following scenario. For the following cases, perform
the upgrades during maintenance windows:
l
Major software updates may include changes to the VNXe high availability and
cluster services. When upgrading to such software versions, there may be some
downtime required.
l
In the case of large and complex configurations, the pre-upgrade health check may
fail if the system exceeds the total number of allowed file systems and snapshots.
When this occurs, the system will recommend that users delete some of the
snapshots to enable the upgrade.
l
In some cases, the ESX servers may require manual refreshes to reconnect to the
datastores.
Note
Disk firmware and language pack upgrades are not disruptive.
Plan the upgrade
Time needed to complete an upgrade
11