XtremIO: How to solve error "obj_identifier_not_unique"
Resumo: How to solve error "obj_identifier_not_unique."
Este artigo aplica-se a
Este artigo não se aplica a
Este artigo não está vinculado a nenhum produto específico.
Nem todas as versões do produto estão identificadas neste artigo.
Sintomas
When attempting to create a snapshot, the XMS may give an error code stating "obj_identifier_not_unique." An example of this is shown below:
create-snapshot consistency-group-id="CG_name1" snapshot-set-name="SS_name1" snap-suffix="DB"
*** XMS Completion Code: obj_identifier_not_unique
*** XMS Completion Code: obj_identifier_not_unique
Causa
An object being created was trying to use the same identifier as an object that exists, such as an index number or name.
The example that is provided above shows a snapshot being created for a consistency group. In this example, review of the objects on the XMS discovered that the snapshot being created was attempting to create a snapshot that would have the same name as another snapshot existing on the array.
To verify if this is due to a volume name already in use, perform the following:
The example that is provided above shows a snapshot being created for a consistency group. In this example, review of the objects on the XMS discovered that the snapshot being created was attempting to create a snapshot that would have the same name as another snapshot existing on the array.
To verify if this is due to a volume name already in use, perform the following:
- Record the names of the volumes in the Consistency Group or Snapshot Set you are creating a snapshot from.
- Take note of the snapshot suffix name, as custom suffix names tend to lead into this issue.
- Log in to the array using XMCLI, run show-volumes, and copy the output to a text document. Search for the names of the volumes from the CG or SS you are creating a snapshot for.
For 6.x XMS versions, another option is to apply a filter to search for specific volume names (example: show-volumes filter=Volume-Name:like:test. This would return all volumes and snapshots with a name containing the string "test").
- Review the search results. If applying the intended suffix to any volumes in the CG or SS would create a snapshot that matches another volume or snapshot that is present on the array, this is the cause (or one of the causes) of the error occurring.
Resolução
To resolve, there are two options:
- The simplest option is to choose a different suffix that is not used anywhere else on the cluster. This can also be a quick way of determining the issue is present.
- If the volume name causing the issue have been identified, rename either the volume the snapshot would be created from, or the other volume or snapshot that exists on the array to a different name.
Mais informações
When attempting to perform this operation in the UI, some versions of the UI may give the message "Suffix creates existing names on CLUSTER_NAME" when attempting to set the suffix to a name that would create duplicate names.
Produtos afetados
XtremIO FamilyProdutos
XtremIO Family, XtremIO HW Gen2 400GB, XtremIO HW Gen2 400GB Encrypt Capbl, XtremIO HW Gen2 400GB Encrypt Disable, XtremIO HW Gen2 400GB Exp Encrypt Disable, XtremIO HW Gen2 400GB Expandable, XtremIO HW Gen2 800GB Encrypt Capbl
, XtremIO HW Gen2 800GB Encrypt Disable, XtremIO HW Gen3 40TB, XtremIO HW Gen3 40TB Encrypt Disable, XtremIO HW X2-R, XtremIO HW X2-R Encrypt Disable, XtremIO HW X2-S, XtremIO HW X2-S Encrypt Disable, XtremIO HW X2-T, XtremIO HW X2-T Encrypt Disable, XtremIO X1, XtremIO X2
...
Propriedades do artigo
Número do artigo: 000071475
Tipo de artigo: Solution
Último modificado: 05 set. 2025
Versão: 5
Encontre as respostas de outros usuários da Dell para suas perguntas.
Serviços de suporte
Verifique se o dispositivo está coberto pelos serviços de suporte.