Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.
Version: 2.15.0

Upgrade Guide for Disaster Recovery for Dell

Introduction​

This page covers what to confirm and review before upgrading Superna Disaster Recovery (DR) Edition — release and platform compatibility, support entitlement considerations for planned failovers, and general upgrade precautions. For the initial deployment process, which shares underlying appliance mechanics with an upgrade, see the Installation Guide.

Coordinated upgrades

If your upgrade needs to be sequenced with other components (for example, ECA/Core Agent components) within a single maintenance window, confirm the correct sequencing with Superna Support before you begin — particularly when the target release introduces new required service-account privileges or changes to PowerScale OneFS support boundaries.

Before You Upgrade​

Confirm Release and Platform Compatibility​

Before upgrading, confirm the target Superna release supports the PowerScale OneFS (or ECS/VAST/Qumulo) release running on your clusters. See the Platform Support page for the first Superna release to support each PowerScale/ECS version.

Support Entitlement for Planned Failovers​

Superna's support policy ties your support entitlement for a planned failover event to how current your release is (this does not apply to unplanned/real DR failovers):

  • Superna adds enhancements in every release specifically to prevent or document conditions that could block a failover. Running an outdated release can affect your support entitlement for a planned event.
  • If you are not on the latest GA release when you open a planned-failover case, you are assumed to have read and accepted the risks documented in that release's Release Notes page before proceeding.

See Failover Process and Customer Role for the complete case-classification and planning-process policy.

Review the Failover Planning Checklist​

The Failover Planning checklist lists "upgrade Eyeglass to the latest version" as one of the pre-failover-day planning tasks, alongside reviewing best practices and release notes, before a planned failover. If you are upgrading specifically to prepare for a planned failover, complete the upgrade with enough lead time to also complete DR readiness validation and rehearsal testing afterward.

Take a Backup / Snapshot Before You Begin​

tip

Eyeglass provides appliance backup and restore capability (for example, igls app pull-config for migrating configuration to a new appliance). As a general precaution, take a VM-level snapshot of the appliance and confirm a recent Eyeglass backup exists before starting any upgrade.

If you are upgrading a very old environment (pre-2.6.1) directly to 2.15.0 in a single step, contact Superna Support before you begin to confirm there are no version-specific conditions affecting your upgrade path.

The following general requirements and considerations apply when upgrading:

  • Disk usage requirement: An Eyeglass upgrade requires appliance disk usage to be below 80% before it will proceed. Free up space (for example, remove old backup files — see Appliance Check) before starting the upgrade if you are close to this threshold.
  • Script Editor is disabled by default: As a security hardening measure, the Script Editor (used for pre/post-failover scripts) ships disabled by default. If your environment relies on custom pre/post-failover scripts and they stop running after an upgrade, this is the most likely cause — contact Superna Support for the current re-enablement procedure.
  • New or changed service-account privileges: Some releases require additional eyeglass service-account privileges on PowerScale OneFS after upgrade. Review the Installation Guide service-account section and compare against the Release Notes for the release you are upgrading to.
Upgrading PowerScale OneFS itself

The steps above cover upgrading the Eyeglass appliance. If you are instead upgrading the PowerScale OneFS release on clusters managed by Eyeglass, see the OneFS Upgrade Procedure for the major/minor release upgrade paths, mixed-mode behavior, and post-upgrade validation steps for Ransomware Defender, Easy Auditor, and Performance Auditor.

note

Consult the Release Notes page for the complete, current-release list of fixes and known limitations before and after upgrading.

Post-Upgrade Validation​

As a baseline, and consistent with the general system checks described in the Installation Guide, confirm the following after any upgrade:

  • Confirm the appliance reports the expected version after upgrade.
  • Confirm all managed clusters still show healthy inventory and job status in the Eyeglass UI.
  • If the upgrade changed required service-account privileges or the supported-platform boundary, re-check DR Dashboard / Failover Readiness results for new errors or warnings before relying on the environment for a planned failover.

See Also​