SM-BC holding snapmirror snapshots

[median spindle]

We have setup SM-BC with 2 volumes in a CG mirroring from one A250 to another.

These are ISCSI LUNS for VMware.

The volume snapshots seem to be filling up and it appears there is a snapmirror snapshot which is being held.

When does this snapshot get removed ?

When i try to manually remove them it tells me

Error: command failed: This Snapshot copy is currently used as a reference Snapshot copy by one or more SnapMirror relationships. Deleting the Snapshot copy can cause future SnapMirror operations to fail.

[strange tundra]

The naming (without the "CG") implies this being a snapshot from another relationship. Or an older one before you configured the CG.
Check with the following commands if another relationship exists:
vserver peer show
snapmirror show
snapmirror list-destinations

[median spindle]

This is where its a bit weird.. it was always setup as a CG for SM-BC. I even chose the SM-BC option in the system manager GUI

here are the outputs

as you can see its just the 2 SM-BC relationships going in each direction

[strange tundra]

What does the following tell you on your volumes?
snapshot show -fields owners,busy

[median spindle]

@strange tundra not much this is just on one the volumes.. time to log a case ?

[strange tundra]

Deleting the snapshot with -ignore-owners true -force true should work.