I recently did the power down of a datacentre containing a 3PAR and wanted to quickly cover off the steps that I followed to power off and then back on. First of all I did a health check to check for any issues such as a failed disk :. All looked OK so I proceeded with the shutdown. No tasks can be running such as Adaptive Optimization.
Then follow the hardware steps in the following section. The order is the reverse of power off:. It would of course be sensible to do a checkhealth after power up to check everything looked OK.
If you found this useful you will be interested to see our selection of the best 3PAR posts selected from the posts written on the topic within this blog. View all posts by Richard Arnold. You can choose a pre-defined period or use a custom one. Anyone can tell me how to shut down a 3PAR environment with peer persistence and quorum witness with two nodes? Allow remote shutdown, wakeup, reboot up to 1, machines simultaneously at a scheduled time.
It has command line support, quick search for machines, log files, etc. Last update 21 Apr. Users rating: Editor's rating: Read the editor's review. Prof Shutdown Editor's Review Prof Shutdown is a simple and very useful tool which allows you to shutdown, reboot, or hibernate multiple machines simultaneously. If WOL Wake-On-Lan is supported by your motherboard, the application can also wake your computer from standby or hibernation. If you want to shutdown another computer from your network , you need to have a user account which is part of the administrators group on that PC.
The program's user interface is easy to use. You can schedule operations daily, weekly, monthly, at system startup, at logon, or when idle. Each task can have multiple schedules associated with it. By default, the program shows a dialog on the computer which is about to be shutdown or rebooted. You can customize this dialog or you can disable it entirely.
Forced system shutdown or reboot are also supported. Pluses: Prof Shutdown can display a 'Cancel' button for a couple of seconds before performing a shutdown or reboot. Read more. If you need help or have a question, contact us Would you like to update this product info? You can do this by disabling the client-facing services running on your cluster. Perform the following procedure to disable client-facing services:.
Document the services that are "enabled" on your cluster based on the output for each command. Highlighted in the example below, the SMB service is enabled whereas the NFS service is disabled: mycluster-4 isi services smb Service 'smb' is enabled. Disable client-facing services. After this step, all clients immediately lose connection to the cluster. Run the isi iscsi list command to confirm that all iSCSI clients are disconnected from the cluster. NOTE On a large cluster with a high number of outstanding writes, this step may take several minutes to complete.
If any node fails to flush, contact Dell Isilon Technical Support. All nodes must successfully flush before proceeding to the next step. If you remove a power source from a node that has not flushed data from its journal to the file system, the risk of data loss increases substantially. Contact Dell Isilon Technical Support if you need assistance with the shutdown procedure. Shut down each node in the cluster sequentially and monitor the output.
This approach is recommended because it enables you to identify and resolve any issues before shutting down the next node in the cluster. Shut down each node by performing the following steps:. Any node that panics or reboots at this step is a node that requires further investigation.
In particular, all nodes must flush data from the node journal to the file system before proceeding. NOTE If you do not have access to your nodes through a keyboard, video, mouse KVM switch and must use a laptop instead, this step may take hours to complete. Watch the console and look for hardware-related failure events.
Not saving. Shut down all nodes in the cluster simultaneously In case of an emergency, you can shut down all nodes in the cluster simultaneously. However, this method is not recommended because it does not enable you to monitor the status and output of each node in case an issue occurs.
If you choose to follow these steps, Dell strongly recommends following all the steps in Phase 3 to verify that all nodes have properly shutdown after performing the procedures below. To shut down all nodes in your cluster, use the OneFS command-line interface or the OneFS web administration interface. From the OneFS command-line interface.
Confirm that the nodes have properly shut down by looking at the power indicator light-emitting diode LED on the back of the node. This indicates that the node has successfully shutdown. If a node has not successfully shut down and you disconnect the power source to the node, the chance of data loss increases substantially.
Recovering data requires a lengthy recovery procedure, and sometimes a complete cluster rebuild. Contact Dell Isilon Technical Support if you have any doubts about the success of the shutdown operation. If the node does not shut down or the journal is not saved If the power indicator light on the back of the node is still illuminated, the node has not shut down. If the node has not shut down, or if you receive console output indicating that the node journal did not save properly from Phase 2, step 3c , you must manually save the journal to ensure that data is committed to disk before shutting down the node.
To manually save the journal and shut down the node, perform the following steps:. Attach a serial console to the node. Determine if the node is responsive to the command-line interface. If the node is not responsive to the command-line interface, manually reboot the node by pressing and holding the power button on the back of the node. This causes the node to power off. Wait 30 seconds and then press the power button once to boot the node back up again.
0コメント