0x323000D Invalid Protected Group

Description

Protected group (name: {1}) is invalid. Consequently, objects in this protected group can no longer be protected.

Attribute

Impact on the System

The DR cannot be implemented.

Possible Causes

• The remote replication or the remote replication consistency group is deleted.
• The remote replication pair is not in the consistency group associated with the protected group.
• HyperMetro pairs or HyperMetro consistency groups are deleted.
• HyperMetro pairs are not included in the consistency group of the HyperMetro protected group.
• All the VMs in the protected group are deleted or no valid VMs are available.
• The networking does not meet the restriction conditions.

Procedure

1. On UltraVR, click Protection and select the required protected object. On the page that is displayed, click Protected Object. Check whether the data protection relationship created for storage resources used by protected objects is deleted.
   1. If the type of the protected group is replication, check whether the remote replication or consistency group used by the protected objects is deleted.
      • If yes=>the protected group cannot be rebuilt. Delete the protected group. If the alarm persists=>Step 5.
      • If no=>manually refresh the storage devices. If the alarm persists=>Step 2.
   2. If the type of the protected group is HyperMetro, check whether the HyperMetro pairs or consistency groups used by protected objects in the protected group are deleted.
      • If yes=>the protected group cannot be rebuilt. Delete the protected group. If the alarm persists=>Step 5.
      • If no=>manually refresh the storage devices. If the alarm persists=>Step 2.
   3. If other types of protected groups exist=>Step 3.

2. On UltraVR, click Protection and select the required protected object. On the page that is displayed, click Protected Object.Check whether storage resources used by the protected objects can meet data protection requirements.
   1. If the type of the protected group is replication and protected objects use multiple storage resources, check whether the storage resources belong to the same remote replication consistency group.
      • If no=>move all storage resources to the same remote replication consistency group. If the alarm persists=>Step 3.
      • If yes=>Step 3.
   2. If the type of the protected group is HyperMetro and protected objects use multiple storage resources, check whether the storage resources belong to the same HyperMetro consistency group.
      • If no=>move all storage resources to the same HyperMetro consistency group. If the alarm persists=>Step 3.
      • If yes=>Step 3.
   3. If other types of protected groups exist=>Step 3.

3. If the type of the protected group is VM, perform the following steps:
   1. Refer to section Restrictions and Limitations in the OceanStor BCManager eReplication User Guide.
      • If yes=>migrate the VMs to other datastores and refresh virtualization resources of the protected group. If the alarm persists=>Step 3.2.
      • If no=>Step 3.2.
   2. Check whether the VMs are in the invalid state.
      • If yes=>rebuild the data protection relationship for the VMs to meet the data protection requirements. Then, refresh the storage virtualization resources. If the alarm persists=>Step 3.3.
      • If no=>Step 3.3.
   3. Check whether all the VMs are removed.
      • If yes=>remove the protected group or add VMs to the protected group. If the alarm persists=>Step 5.
      • If no=>Step 4.

4. Check whether the DR environment meets the restrictions. For details, see section Restrictions in the User Guide.
   • If no=>resolve DR environment problems and refresh the protected group. If the alarm persists=>Step 5.
   • If yes=>Step 5.

5. Contact technical support engineers.

Related Information

None