Data Domain: How to Power Off and Power On to Reboot Data Domain

Sometimes it is required to shut down or reboot the Data Domain. The purpose can be for a DDOS upgrade, applied workaround, time zone change, disaster situation, or any other. It is important to follow the correct procedure.

To shut down the system or to perform a system reboot, examine the following:

• Verify that I/O on the system is stopped.

# iostat 5

sysadmin# iostat 5

2019-12-18 18:18:16
INTERVAL: 5 secs
"-" indicates that system is busy and unable to get recent data.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CPU      |State     |Protocol Aggr                       |CIFS                 |Net                                                                                                                                                        |Disk                |NVRAM          |Repl
aggr aggr|          |                                    |                     |ethMa eth1a eth1b eth1c eth1d eth3a eth3b eth3c eth3d eth4a eth4b eth4c eth4d ethMa eth1a eth1b eth1c eth1d eth3a eth3b eth3c eth3d eth4a eth4b eth4c eth4d|                    |   aggr    aggr|
busy  max|          |        ops/s  load data in data out|ops/s      in     out|   in    in    in    in    in    in    in    in    in    in    in    in    in   out   out   out   out   out   out   out   out   out   out   out   out   out|   read   write busy|   read   write|     in     out
   %    %|CDPVMSFIRL|                  %    MB/s     MB/s|         MB/s    MB/s| MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s  MB/s|  KiB/s   KiB/s   ms|  KiB/s   KiB/s|   KB/s    KB/s
---- ---- ---------- ------------- ----- ------- -------- ----- ------- ------- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ------- ------- ---- ------- ------- ------- -------
   0    0                        0    19       0        0     0       0       0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0       0     508  607       -       -       0       0
   0    0                        0    19       0        0     0       0       0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0       0     747  758       -       -       0       0
   0    0                        0    19       0        0     0       0       0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0       0     576  514       -       -       0       0
   0    0                        0    19       0        0     0       0       0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0     0       0     282  421       -       -       0       0

• No backup or ddboost replication should be running during that period, as it will be affected.

# ddboost file-replication show active

sysadmin# ddboost file-replication show active

File-replication active:  There are no file replication operations in progress.

• For the HA system, verify the health of the HA configuration, run the following command in CLI:

# ha status

• For HA systems, run the # ha offline command if the system is in a highly available state with both nodes online. Skip this step if the HA status is degraded.

1. Power off Data Domain.

# system poweroff

sysadmin# system poweroff

The system poweroff command shuts down the system and turns off the power.
Are you sure? (yes|no) [no]: yes
Once powered off, you can remove power cables from the Head unit/Controller or expansion shelves if needed.

2. Power on the system.

• Power on all expansion shelves before powering on the Data Domain controller. Wait approximately three minutes after all expansion shelves are turned on.
• Plug in the power cable for your head unit/controller, for HA systems, power on the active node first, and then the standby node.
• For HA systems, verify the health of the HA configuration, run the following command: # ha status
• For HA systems, if one of the nodes displays as offline, run the # ha online command on that node to restore the HA configuration.

3. Reboot the Data Domain using the user interface.
   1. Select Maintenance, System, and then Reboot System.
   2. Click OK to confirm.

Figure 1: Data Domain System Manager

4. Reboot or power off the DD3300 using the iDRAC.

Power cycling the DD3300 can be performed by using the iDRAC with this process:

1. Log in to the iDRAC 

Figure 2: Integrated Remote Access Controller interface

2. Once logged in, various graceful shutdowns can be performed, such as:
   • Power Off System
   • Non-Masking Interrupt
   • Warm Reboot
   • Cold Reboot

The complete reboot process used for any of the systems generally takes 30 minutes to 1 hour.

• Do not use the chassis power switch to power off the system. Doing so prevents remote power control using IPMI. Use the # system poweroff command instead. The system poweroff command shuts down the system and turns off the power.
• The IMPI Remote System Power Down feature does not perform an orderly shutdown of the DD OS. Use this feature only if the system poweroff command is unsuccessful.
• After reboot, if the system takes more than 1 hour to come up, contact your support team.