Open an SSH session to the control station and see the output of /nas/sbin/getreason command. I believe the DM was already in failed over state and the drive replacement caused some interruption to the currently active DM.

Also I would recommend opening an SR in parallel.

If you look at the properties of the shared folder in the EMC Celerra Manager there are two warnings:

1. Query file systems All: All. Failed to get RDE information for file system ID 25. details ..
Severity: Warning Warning
Brief Description: Failed to get RDE information for file system ID 25.
Full Description: Redundant Data Elimination (RDE) information was not returned for the file system indicated. This occurs when the Data Mover, or blade, is not booted up.
Recommended Action: To check the Data Mover, or blade, status use the CLI command / nas / sbin / getreason. All active Data Movers, or blades, should return a reason code of 5 (contacted). If one, or more are missing or reports a different reason code it may need to be powered on or rebooted.
Message ID: 17986158625

2. Query VDMs server_2. Standby Data Mover server_2.faulted.server_3 is out of service. details ...
Severity: Warning Warning
Brief Description: Standby Data Mover server_2.faulted.server_3 is out of service.
Full Description: No additional information is available.
Recommended Action: No recommended action is available. Use the text from the error message's brief description or the message's ID to search the Knowledgebase on Powerlink. After logging in to Powerlink, go to Support> Knowledgebase Search> Support Solutions Search.
Message ID: 17985568837

The slot_2 failed over due to some reason (the support will be able to let you know the root cause). As you are facing issue in accessing the shares and as the DMs are in contacted state, you may try a failback by running

server_standby server_2 -restore mover

But it is recommended to wait for the support to get back to you, if you have an SR open for this.

Do will not prevent implement this command is that we have replaced the drive is still in the status Equalaizing?

Looks like the DMs are in good state. Please share the nas_server -l output also.

From the above error messages, the slot_2 is in failed over state to slot_3 (as error messages read 'Standby Data Mover server_2.faulted.server_3 ') If that is the case, you can try restoring the DM by running server_standby server_2 -restore mover command.

nas_server -l output will make this clear.

[nasadmin@rnpc-cs ~]$ nas_server -l

id      type  acl  slot groupID  state  name

1        4    0     2              2    server_2.faulted.server_3

2        1    0     3              0    server_2

[nasadmin@rnpc-cs ~]$ /nas/sbin/getreason

10 - slot_0 primary control station

5 - slot_2 contacted

5 - slot_3 contacted

It should not be causing an issue while failing back the DM. But if you can wait for the equalization to complete, will be better.