Hi,  to test the blade ( aka Data Mover ) failover, simply run the following command :  # server_standby server_2 -a mover  To fail it back ( or restore ) to slot_2, use the following command :  # server_standby server_2 -r mover  This operation can usually take from 30 seconds up to 4 minutes, depending on the size of the environment ( # of filesystems, # of checkpoins, # of tree quotas ) and the DART version - the latest versions have some improvements that minimize this times.  Make sure the network infrastructure is setup properly on both Data Movers.  Regarding the impact, it depends on the environment also.  In a NFS environment, if the clients are using 'hard' mount option, you should not see any impact. In a CIFS environment, the connections will be closed, and reopened after the activity. In a iSCSI environment, it depends on the initiators configuration. There are some timeout settings that can make the failover/failback operations transparent.  Once you are not on production yet, this is the perfect time to test it, and see what's the impact on your environment.   Regards,  Gustavo Barreto.
before going in production enviroment, i need to test my primary standby configuracion, doing this in an controlled event, step by step, to check if all components are working,  i want to simulate, a fail in datamover2, to activate datamover3(standby mode) to primary mode, then return the good state of datamover2, to a primary mode again, and deactivate the datamover3 and return it  to its original mode (standbymode)  how much time does this takes. and what steps to follows  what is the impact, with all the share folders, there will be any disrruptions?  any one had do this. what do a need to know it, before doing this, please any idea i will be apreciate  Maynor
nx4 - need test my primary standby datamover configuration step by step