Oracle ZFS Storage Appliance (ZFSSA): Remote Replication Action May Be Destroyed After Replication Reversal (Doc ID 2291209.1)

Last updated on AUGUST 02, 2017

Applies to:

Oracle ZFS Storage ZS4-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-BA - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

 This document describes in more detail the conditions and corrective action related to Service Alert
2286584.1 - ZFS Storage Appliance (ZFSSA) Replication Actions May Be Missing After Package
Reversal.

Conditions
For software versions OS8.7.0 through OS8.7.7, reversing a replication package may create a damaged
replication action that will be destroyed during the next software update, takeover, failback, reboot,
powerup, or restart of the management interface (that is, restart of the appliance kit daemon - akd).
Once the replication action is destroyed, the replication package that was being maintained by the lost
replication action will no longer receive updates.

This unintended destruction of the action can occur under the following circumstance:

• The source and/or target were updated to OS8.7.0 or higher from a software release prior to
OS8.7.0.

• The replication action is in a project/package replication pair that existed while the source
and/or target were at a software release prior to OS8.7.0.

• While running any of the software versions OS8.7.0 through OS8.7.7 the project/package
replication pair was reversed via one of the following methods:
◦ BUI (Browser User Interface) reverse operation
◦ CLI command pkgreverse
◦ RESTful API pkgreverse resource

This circumstance creates a damaged replication action in the project created by the reversal operation.
This damage will not become apparent until a subsequent pool import operation takes place. The
operations listed above: software update, takeover, failback, etc., perform a pool import operation that
destroys all damaged replication actions in the pool being imported.

Note in particular that once a replication action has been damaged due to the circumstance described
above, the act of installing a software update of any software version, older or newer, can destroy the
damaged replication action. Preventing the destruction of the replication action requires determining
that damaged action(s) have been created and carrying out an action repair process before proceeding
with the software update, takeover, failback, etc.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms