Restarting an HCP node causes it to reboot. While the node is in the process of restarting, clients have no access to it.
![]() |
Note: When you restart a node in a system with zero-copy failover enabled, the storage managed by the node fails over to the paired node during the shutdown part of the restart. The failover process always finishes before the restarted node completes its shutdown process. Therefore, the data outage caused by the failover lasts less than three minutes. When the node comes back up, the failback process extends the reboot by 15 to 30 seconds. The data outage caused by the failback lasts less than five minutes. For more information about failover and failback, see Zero-copy failover behavior. |
To restart a node:
1.Take one of these actions:
oOn the Hardware ► Nodes page, click the restart icon for the node.
oOn the Storage Node page for the node, click Restart Node.
The Restart Node window appears.
2.In the Reason field, type the reason why you’re restarting the node. This text can be up to 1,024 characters long and can contain any valid UTF-8 characters, including white space.
3.Click Restart Node.
The node reboots. When the node has finished rebooting, it is again available for client access.
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.