Celerra NS120: NDMP service - Enabled, Pending Reboot

rebooting the datamover every operations will pass to the other datamover without interrupting anything, correct?

Thanks,

Fabio.

Reboot the data mover or failover/failback to the standby DM

No – reboot doesnt cause a failover

If you want a failover you need to do a failover

Please see the VNX configuring standbys manual for the details

i would failover/failback instead of reboot.

if network connectivity configured properly on the standby datamover, then when you failover and failover should have very little impact to end users.  NFS clients will "pause" while it's failing over/back, CIFS clients will lose connection and will need to reconnect.  Failover/Failback is relatively fast process but it depends on how many file systems (including checkpoints) you have. In my experience it has taken from 40 seconds to 2 minutes.

Thanks Dynamox,

so I'll reboot it during the night so that having lower impact to end users.

Thanks,

Fabio

Sorry I made a wrong in writing reboot instead of failover. How can I do a failover?

Thanks,

Fabio.

My primary datamover is server_2 the standby is server_3.

So is it your command the right one to failover?

Thanks,

Fabio.

Yes, the command is correct.  You issue all commands to server_2.  You tell server_2 to fail over, and then tell server_2 to fail back.

Your servers currently look like this:

[nasadmin@PopRocks ~]$ nas_server -l
id      type  acl  slot groupID  state  name
1        1    0     2              0    server_2
2        4    0     3              0    server_3

You will issue the command to server_2 to fail over:

[nasadmin@PopRocks ~]$ server_standby server_2 -a mover

When you fail over they will look like this:

[nasadmin@PopRocks ~]$ 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

Notice that server_3 is gone, and has been renamed server_2.  Also notice that the mover in slot_2 is in "state 2".  This indicates that it was a primary that is now failed over.  Technically, it is the new standby for server_2, but the failover policy is manual.  It will not fail back on its own; you have to initiate it:

[nasadmin@PopRocks ~]$ server_standby server_2 -r mover

When the failback is completed, the system view will return to normal:

[nasadmin@PopRocks ~]$ nas_server -l
id      type  acl  slot groupID  state  name
1        1    0     2              0    server_2
2        4    0     3              0    server_3

https://support.emc.com/servicecenter/createSR/

Data unavailable

failover completed.

Unfortunately now I can't reach a CIFS server. I can ping it but I can't view its shares using Windows browser. Inside the properties of it I can't change the interfaces, they are not selectable while the interfaces appear UP.

what does it mean DU?

server_cpu server_2 -reboot -monitor now