Sun Storage 7000 Unified Storage System: Duplicate Replication Action IDs result in "receive() XDR: bad status: 'exists'"

Asset ID:	1-72-1554806.1
Update Date:	2016-09-30
Keywords:

Solution Type Problem Resolution Sure

Solution 1554806.1 : Sun Storage 7000 Unified Storage System: Duplicate Replication Action IDs result in "receive() XDR: bad status: 'exists'"

Related Items


Sun ZFS Storage 7320
 Sun Storage 7210 Unified Storage System
 Oracle ZFS Storage ZS3-BA
 Oracle ZFS Storage Appliance Racked System ZS4-4
 Oracle ZFS Storage ZS3-2
 Sun Storage 7410 Unified Storage System
 Oracle ZFS Storage ZS3-4
 Sun ZFS Storage 7420
 Sun Storage 7310 Unified Storage System
 Oracle ZFS Storage ZS4-4
 Sun ZFS Storage 7120
 Sun Storage 7110 Unified Storage System

Related Categories


PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS

Replication updates fail if a snapshot of a share being replicated is cloned and "Retain Other Local Settings" was ticked when the clone was created.
This applies to the replication source.
It results in a replication action with the same ID being created for the clone.
An alert is generated for the failure on the "stage 'stream_setup' failed: failed to invoke receive() XDR: bad status: 'exists'"

The last_result is reported as: The most recent replication update failed because the target package contains data from a previous replication update that could not be  used for an incremental update. See the replication documentation for more details.

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-7067575241>

Applies to:

Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7110 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7210 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Disk Storage ZFS Storage Appliance

Replication failed with the following error on the source:

ak_errmsg = stage 'stream_setup' failed: failed to invoke receive() XDR: bad status: 'exists'

The replication action showed 'last_result':

The most recent replication update failed because the target package contains data from a previous replication update that could not be used for an incremental update. See the replication documentation for more details.

Changes

A snapshot was taken of the source share and a clone was created. When the clone was created, "Retain Other Local Settings" was checked.

Cause

Duplicate replication action ID's on the source. The duplicate was created by the system, in error when the share was cloned.

A check of the system turned up two replication actions using the same ID:

Here's the original share:

NASa:shares AUDI_ING/FMS-P action-000> show
Properties:
  id = e3cb288f-945b-4634-8fd4-f4933c97b2c8
  target = NAS2a_RZ-B
  enabled = true
  continuous = true
  include_snaps = true
  max_bandwidth = unlimited
  use_ssl = false
  state = idle
  state_description = Idle (no update pending)
  next_update = Mon Apr 15 2013 16:53:31 GMT+0000 (UTC)
  last_sync =
  last_try = Mon Apr 15 2013 16:23:31 GMT+0000 (UTC)
  last_result = The most recent replication update failed because the target package contains data from a previous replication update that could not be used for an incremental update. See the replication documentation for more details.

Here's the clone - note the ID is the same:

NAS2a:shares AUDI_ING/FMS-P01 action-000> show
Properties:
  id = e3cb288f-945b-4634-8fd4-f4933c97b2c8
  target = NAS2a_RZ-B
  enabled = true
  continuous = true
  include_snaps = true
  max_bandwidth = unlimited
  use_ssl = false
  state = idle
  state_description = Idle (no update pending)
  next_update = Mon Apr 15 2013 19:54:21 GMT+0000 (UTC)
  last_sync =
  last_try = Mon Apr 15 2013 19:24:21 GMT+0000 (UTC)
  last_result = The most recent replication update failed because the target package contains data from a previous replication update that could not be used for an incremental update. See the replication documentation for more details.

The ID is the unique element in snapshot name. If two actions use the same ID on the same share, the result is duplication snapshot names. This causes the "already exists" failure.

Solution

Complicating factors: Destroying the target replication package wasn't an option because there were dependent clones on the target that had to be retained. In addition the system had insufficient space to hold another full replication:

To protect the dependent clones, "Prevent Destruction" was checked on the target share.

The duplicate actions on the source were then disabled.

Storage was added and a new, unique replication action created.

Initial replication completed normally.

References

<BUG:16667589> - SHARE LEVEL REPLICATION FAILS AFTER CLONING WITH "RETAIN OTHER LOCAL SETTINGS"
<NOTE:1397959.1> - Sun Storage 7000 Unified Storage System: How to Troubleshoot Replication Issues

Attachments

This solution has no attachment