JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle® ZFS Storage Appliance Customer Service Manual

For ZS3-x, 7x20 Controllers, and DE2-24, Sun Disk Shelves

Oracle Technology Network
Library
PDF
Print View
Feedback
search filter icon
search icon

Document Information

Using This Documentation

Chapter 1 Introduction

Chapter 2 Hardware Maintenance

Chapter 3 System Maintenance

System

Introduction

System Disks

Support Bundles

Managing Support Bundles Using the BUI

Generating and Uploading a Support Bundle Using the BUI

Support Bundle Options

Managing Support Bundles Using the CLI

Initial Setup

Factory Reset

Updates

System Updates

Software Update Notification

Scheduling Software Notification Using the BUI

Scheduling Software Notification Using the CLI

Checking for Updates Using the BUI

Checking for Updates Using the CLI

System Update Overview

Preconditions

Update Health Checks

BUI

CLI

Troubleshooting Update Health Check Failures

Actions to Take to Resolve Health Check Alerts

Resolution Steps

Steps for Resolving Health Check Alerts

Deferred Updates

Reboot After an Update

Hardware Firmware Updates

Rollback

Fail-safe Rollback

Cluster Upgrade

Performing the Cluster Upgrade

Cluster States During Upgrade

Updating via the BUI

Unpacking and Verifying Media

Beginning the Upgrade

Rolling Back

Removing Update Media

Applying Deferred Updates

Updating via the CLI

Unpacking and Verifying Media

Beginning an Upgrade

Rolling Back

Removing Update Media

Applying Deferred Updates (CLI)

Passthrough x

Passthrough-x Deferred Update

User Quotas

User Quotas Deferred Update

COMSTAR

COMSTAR Deferred Update

Triple Parity RAID

Triple-Parity RAID Deferred Update

Dedup

Data Deduplication Deferred Update

Replication

Replication Deferred Update

Received Properties

Received Properties Deferred Update

Slim ZIL

Introduction

Snapshot Deletion

Snapshot Deletion Deferred Update

Recursive Snapshots

Recursive Snapshots Deferred Update

Multi Replace

Multi Replace Deferred Update

RAIDZ Mirror

RAIDZ/Mirror Deferred Update

Optional Child Dir

Introduction

Multiple Initiator Groups per LUN

Introduction

Support for Large Block Sizes

Support for Large Block Sizes

Sequential Resilvering

Sequential Resilvering

ConfigurationBackup

Configuration Backup

Backup Contents

Restore Impact

Security Considerations

Managing Configuration Backups Using the BUI

Create a Configuration Backup

Restore from a Saved Configuration

Delete a Saved Configuration

Export a Saved Configuration

Import a Saved Configuration

Managing Configuration Backups Using the CLI

Listing Configurations

Create a Configuration Backup

Restore from a Saved Configuration

Delete a Saved Configuration

Export a Saved Configuration

Import a Saved Configuration

Problems

Problems

Active Problems Display

Repairing problems

Related features

Logs

Logs

Alerts

Faults

System

Audit

Phone Home

BUI

Viewing Logs

Exporting Logs

CLI

Listing Logs

Viewing a Log

Viewing All Log Entries

Viewing Groups of Log Entries

Viewing Entry Details

Exporting Logs

Maintenance Workflows

Using Workflows

Workflow Execution Context

Workflow Parameters

Constrained Parameters

Optional Parameters

Workflow Error Handling

Workflow Input Validation

Workflow Execution Auditing

Workflow Execution Reporting

Versioning

Appliance Versioning

Workflow Versioning

Workflows as Alert Actions

Alert Action Execution Context

Auditing Alert Actions

Using Scheduled Workflows

Using the CLI

Coding the Schedule

Example: Device Type Selection

BUI

CLI

Downloading Workflows

Viewing Workflows

Executing Workflows

Cluster Upgrade

In a clustered system, a rolling upgrade can be performed, eliminating downtime while the upgrade is performed. This section assumes familiarity with the Oracle ZFS Storage Appliance clustering model: if you are not familiar with the clustering concepts and terminology, please first read Chapter 10, Cluster Configuration, in Oracle ZFS Storage Appliance Administration Guide . To describe the rolling upgrade procedure, this document refers to the two clustered storage controllers as A and B, where A is the controller that will be updated first, and B is the controller that will be updated second. A key best practice in rolling upgrades is that each controller should be upgraded at a time when it is not providing service to clients. The procedure described here meets this requirement. In addition, all general upgrade best practices described earlier also apply to rolling upgrades.

Performing the Cluster Upgrade

Important: Do not perform a takeover operation while an upgrade is in progress.

  1. Use the CLI or BUI to upload the software update image to both storage controllers.
  2. Select which controller to update first. If a controller has no storage pools, update that controller first. In the following steps, controller A is updated first so if any clients are using controller A's storage pool(s), they experience a takeover-induced availability delay first.
  3. Log in to controller A and use the CLI maintenance system reboot command or the BUI power icon image: in the masthead and select the reboot option to reboot controller A. Controller B takes over resources from controller A.
  4. Log in to controller A and use the CLI or BUI to apply the software update to controller A. At the end of the upgrade, controller A reboots again and runs the new software version.

    Note -  Do not perform an upgrade on a controller while it is providing service.
  5. Log in to controller B and use the CLI maintenance system reboot command or the BUI power icon image: in the masthead and select the reboot option to reboot controller B. Controller A takes over all resources and provides service using the new software version.
  6. Validate the new software version on controller A and ensure that all services work correctly on the client systems.
  7. If a serious problem appears, roll back controller A. Controller A reboots and controller B takes over and runs the previous software version. When controller A recovers, it also runs the previous software version.
  8. If no serious problem appears, log in to controller B and use the CLI or BUI to apply the software update to controller B. Controller B reboots and runs the new software version.
  9. Verify that all firmware updates complete.

    Note -  Controller firmware updates cannot proceed if the controllers are running different system software versions.
  10. To restore normal operation and return resources to their respective assigned controllers, log in to controller A and use the CLI or BUI to perform a failback on controller A. For information on the failback operation, see Cluster Takeover and Failback in Oracle ZFS Storage Appliance Administration Guide .

Cluster States During Upgrade

The following table describes the state of the cluster after each step of the previous procedure.

Table 3-4  Cluster States During Upgrade
Step
Controller A State
Controller A Version
Controller B State
Controller B Version
1,2
CLUSTERED
V
CLUSTERED
V
3
STRIPPED
V
OWNER
V
4
STRIPPED
V+1
OWNER
V
5, 6, 7
OWNER
V+1
STRIPPED
V
8, 9
OWNER
V+1
STRIPPED
V+1
10
CLUSTERED
V+1
CLUSTERED
V+1


Note -  Do not make configuration changes to either storage controller while an upgrade is in progress. While controllers are running different software versions, configuration changes made to one controller are not propagated to its peer controller.

Accessing the BUI or logging into the CLI while the controllers are running different software versions generates a warning that your configuration changes will not be propagated. You can configure the appliance to generate alerts when the cluster controllers are running different software versions (events "Cluster rejoin mismatch" and "Cluster rejoin mismatch on peer").

If you change the root password during an upgrade and then rollback the cluster, the nodes are not able to re-join after the rollback.