OPERATIONAL DEFECT DATABASE
...
...
After SRM/SRA failover, both sides of replication claim to be the sourceBoth source and destination RCG status show Read‑Only with a Disaster Recovery flagDestination volume was never mapped to any SDCsCannot make any changes to the RCGs until reverted Query RCG command output: scli --query_replication_consistency_group --replication_consistency_group_name TEST | grep -Ei 'Access mode|Direction|Disaster recovery' Target volume access mode: READ_ONLY Direction: LOCAL_TO_REMOTE Disaster recovery flow: FAILOVER Disaster recovery state: Done MDM Events: 2025-07-23 13:59:26.389 MDM_CLI_CONF_COMMAND_RECEIVED INFO Command failover_replication_consistency_group received, User: 'block-legacy-gateway'. [162777072] Failover Replication Consistency Group ID: 6acd604b00000004 2025-07-23 13:59:26.389 RPL_CG_FAILOVER_STARTED INFO Replication Consistency Group ID 6acd604b00000004 DST: Failover started 2025-07-23 13:59:26.396 CLI_COMMAND_SUCCEEDED INFO Command failover_replication_consistency_group succeeded. Return code: Success (65) [162777072] Failover Replication Consistency Group completed. rc: SUCCESS inactivateSrcMappingRc: SUCCESS 2025-07-23 13:59:26.397 RPL_CG_REACHED_NEUTRAL INFO Replication Consistency Group ID 6acd604b00000004 reached Neutral mode state 2025-07-23 13:59:27.494 RPL_CG_FAILOVER_DONE INFO Replication Consistency Group ID 6acd604b00000004 DST: Failover completed The system reports failover as 'completed' but leaves RCG in an unusable NEUTRAL state. Impact Production system remains offline, causing complete service interruptionBoth sites become unusable with volumes in a read‑only stateThe environment remains in a disaster‑recovery state, preventing further replication
UI gap in PFMP 4.5.x and 4.6.x - The auto‑provisioning wizard lacks the 'Map Volumes' step for target volumes. When destination volumes are not mapped to SDCs, SRM/SRA failover causes the system to enter NEUTRAL mode instead of completing the failover, leaving both source and target RCGs in read‑only disaster recovery state.
RECOVERY STEPS: Step 1 - Revert the RCG to exit disaster‑recovery state. scli --reverse_replication_consistency_group --replication_consistency_group_name <RCG Name> This brings the RCG out of Failover State/Disaster Recovery, but both sides remain read‑only. Ensure to perform this on the source to target RCG. Run the following command to validate the RCG location, source, or target: scli --query_replication_consistency_group --replication_consistency_group_name TEST | grep -i "Direction" Direction: LOCAL_TO_REMOTE Step 2 - Create a snapshot of the RCG to enable read/write access. scli --create_replication_consistency_group_snapshots --replication_consistency_group_name <RCG Name> After creating a snapshot, the RCG mode changes to read/write. Note the Snapshot Volume ID for step 3. Step 3 - Map the snapshot volume to hosts scli --map_volume_to_host --volume_id <Snapshot Volume ID> --host_id This allows VM access and registration. Step 4 - Migrate VMs to permanent storage.User should migrate VMs from a snapshot volume to another permanent volume. Impacted Versions PFMP 4.6.x Fixed In Version TBD
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
