Oracle ZFS Storage Appliance: Clone of a Snapshot Fails with "The action could not be completed because the target <PROJECT

Asset ID:	1-72-2101086.1
Update Date:	2016-03-22
Keywords:

Solution Type Problem Resolution Sure

Solution 2101086.1 : Oracle ZFS Storage Appliance: Clone of a Snapshot Fails with "The action could not be completed because the target no longer exists".

Applies to:

Oracle ZFS Storage ZS4-4 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-2 - 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 7420 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

A successful replication of a Project from a source appliance to a target appliance has completed.

On the target system, one of the replicated shares will be cloned for further administrative work.

While attempting the clone of the share from the BUI, it fails with the following error:

The action could not be completed because the target 'Dbase' no longer exists on
the system. It may have been destroyed or renamed by another user, or the current
bookmark may be stale

From the BUI, it will look like this.

clone-of-snapshot

The command line interface also fails to create the clone, but prints a slightly different error message.

s7320-2:> shares replication sources select source-000 select package-000 select Dbase select t2000 snapshots>

s7320-2:> select .rr-1fc296a5-d016-43d2-8686-91bf3c995550-170

s7320-2:shares replication source-000 package-000 Dbase/t2000@.rr-1fc296a5-d016-43d2-8686-91bf3c995550-170> show
Properties:
creation = Thu Feb 25 2016 13:48:42 GMT+0000 (UTC)
numclones = 0
isauto = false
pool = pool2
canonical_name = pool2/nas-rr-1fc296a5-d016-43d2-8686-91bf3c995550/Dbase/t2000@.rr-1fc296a5-d016-43d2-8686-91bf3c995550-170
shadowsnap = false
space_unique = 1K
space_data = 25.0G

fc296a5-d016-43d2-8686-91bf3c995550-170> clone backupclone
error: must specify local project to clone

Cause

The error is being generated because the default behavior for the clone operation is to put the clone into the project it was originally in.

That project was called "Dbase" on the source system. There is no such project on the target.

Solution

There are two ways to workaround the error.

1. You can create an empty project named Dbase followed by your clone operation. The clone command will specify the project first, followed by the name you use for the clone.

7320-2:> shares project Dbase
7320-2: shares Dbase (uncommitted)> commit

7320-2:> shares replication sources select source-000 select package-000 select Dbase select t2000 snapshots
7320-2:shares replication source-000 package-000 Dbase/t2000 snapshots> select .rr-1e1c1aba-7992-edb8-99d6-b5e3c6cb17f4-1

7320-2:shares replication source-000 package-000 Dbase/t2000@.rr-1e1c1aba-7992-edb8-99d6-b5e3c6cb17f4-1> clone Dbase backup-t2000
7320-2:shares Dbase/backup-t2000 (uncommitted clone)> commit
7320-2:shares replication source-000 package-000 Dbase/t2000@.rr-1e1c1aba-7992-edb8-99d6-b5e3c6cb17f4-1> show
Properties:
creation = Mon Mar 21 2016 14:39:01 GMT+0000 (UTC)
numclones = 1
..........

7320-2:shares replication source-000 package-000 Dbase/t2000@.rr-1e1c1aba-7992-edb8-99d6-b5e3c6cb17f4-1> cd /
7320-2:> shares select Dbase select backup-t2000
7320-2:shares Dbase/backup-t2000>

2. You can clone the snapshot to any project on the target appliance including the default project. From the BUI, it would look like this.

successful-clone

Attachments

This solution has no attachment