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

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
 

In this Document

Symptoms

Cause

Solution

Created from <SR 3-12680823603>

Applies to:

Symptoms

Cloning a replicated LUN or a replicated project containing LUNs fails with:

error: The initiator group 'xxx' no longer exists. It may
have been destroyed or renamed by another administrator, or this LUN may
have been imported from another system.

Cause

When using non-default target groups and initiator groups, administrators must ensure that the target groups and initiator groups assigned to LUNs within the project also exist on the replication target before cloning can take place.

Failure to ensure this can result in failure to clone replicated LUNs.

It is only required that groups with the same name exist, not that they define the same configuration or even contain any elements.

Note: The above is documented in the online help under

Shares -> Replication -> Replicating iSCSI Configuration

but in fact it applies to all LUNs, iSCSI and Fibre Channel.

Solution

Create an empty initiator group (or target group) with the same name as that which is assigned to the LUN(s) on the source appliance.

Once the clone is done, the LUNs can be re-mapped to the correct initiator groups as required.

This solution has no attachment