Data Domain: Comprehensive System Health Check

Prerequisites

• Access to the Data Domain system CLI using SSH or direct console connection
• An admin role account
• Verify the DDOS version to determine which command is available (see the Command Support Matrix below)

Command Support Matrix

How to Run a Comprehensive Health Check (DDOS 8.4.0 and Later)

The system health check command evaluates both hardware and software components in a single operation.

Hardware components checked: Storage disks, power supply units (PSUs), fans, SAS controllers, QAT, NVRAM, DIMMs, I/O cards, and CPUs

Software components checked: SMS health, file system, ATOS Cloud FS availability, capacity, garbage collection, certificates, user interfaces, DNS, user configuration, replication, logical volume, and QAT registry

1. Log in to the Data Domain system CLI as an admin or user using SSH or a direct console connection.
2. Run one of the following commands based on the desired scope:
   • Full health check (hardware and software):
     • # system health check
   • Hardware components only:
     • # system health check hardware
   • Software components only:
     • # system health check software
3. Wait for the health check to complete. The process may take a few minutes depending on the size of the installed system.
4. Review the component-wise summary table displayed in the CLI output. Each component shows a PASS or FAIL status.
5. If any component reports a FAIL status, review the detailed remediation steps in the remedy field of the CLI output and follow any linked KB articles.
6. To view the full report, run the log view command. Reports are saved to: /ddr/var/log/healthcheck/
   • For example: # log view healthcheck.log

Run a Hardware-Only Health Check (DDOS 7.10.1.40 to 8.3.x)

Use the support healthcheck hardware command on systems running supported DDOS versions that do not yet support the system health check command, or when only hardware diagnostics are needed.

Hardware components checked: Storage disks, PSUs, fans, SAS controllers, QAT, NVRAM, DIMMs, I/O cards, and CPUs

Supported hardware platforms: DD6300, DD6400, DD6410, DD6800, DD6900, DD9300, DD9400, DD9410, DD9800, DD9900, DD9910, and DD9910F

Supported software platforms: DDVE and ATOS (all platforms)

1. Log in to the Data Domain system CLI as an admin user using SSH or a direct console connection.
2. Run the following command:
   # support healthcheck hardware
3. Wait for the health check to complete. The process may take up to one minute.
4. Review the component-wise summary table. Example output:

   HARDWARE Health Check Summary:
   +-------------------+--------+
   | Component         | Status |
   +-------------------+--------+
   | Storage Disk      | PASS   |
   | Power-Supply Unit | PASS   |
   | FAN               | PASS   |
   | SAS Controller    | PASS   |
   | NvRAM             | PASS   |
   | DIMMs             | PASS   |
   | IO Cards          | PASS   |
   | CPU               | PASS   |
   | NIC H/W Errors    | PASS   |
   +-------------------+--------+
   

5. If any component reports a FAIL status, follow the remediation steps provided in the remedy field and any referenced KB articles.
6. To view the full report, run the log view command with the file path displayed in the CLI output. Reports are saved to: /ddr/var/log/healthcheck/
   • For example: # log view healthcheck.log

Further Assistance:

• If the health check identifies failures that cannot be resolved using the provided remediation steps, generate a complete Support Bundle and reach out to your contracted Support Provider.

Manage the Proactive Health Check Schedule (DDOS 8.4.0 and Later)

The system health check runs automatically on a daily schedule. By default, it runs at 0500 hours each day.

1. View the current schedule:

   # system health check show schedule

2. Modify the schedule:

   # system set schedule {daily | day(s)} time

   • Replace {daily | day(s)} with the desired frequency and time with the preferred execution time.
   • Note: Scheduling a system health check to run after the autosupport scheduled time is not permitted.
3. Disable the scheduled health check:

   # system set schedule never

4. Reset the schedule to the default (daily at 0500 hours):

   # system health check reset schedule