Insights /Backup, NAS and business continuity

Should TrueNAS use hardware RAID, or should ZFS manage the disks directly?

ZFS needs direct visibility of disks, SMART data, and error states. An HBA or JBOD mode is usually preferred, followed by vdev design based on performance, capacity, and rebuild windows.

Should TrueNAS use hardware RAID, or should ZFS manage the disks directly?
Key assessment

Establish a factual baseline with “HBA/JBOD passthrough” and “direct disk visibility to ZFS”, then move to “SMART and error visibility”. Use backup chain, repository state and recovery results as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking HBA/JBOD passthrough, direct disk visibility to ZFS and SMART and error visibility independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · HBA/JBOD passthroughChecking HBA/JBOD passthrough helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline.Record the actual state of HBA/JBOD passthrough. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first.
02 · direct disk visibility to ZFSChecking direct disk visibility to ZFS helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline.Record the actual state of direct disk visibility to ZFS. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first.
03 · SMART and error visibilityChecking SMART and error visibility helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline.Record the actual state of SMART and error visibility. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first.
04 · vdev fault-tolerance designChecking vdev fault-tolerance design helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline.Record the actual state of vdev fault-tolerance design. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first.
05 · rebuild duration and URE riskChecking rebuild duration and URE risk helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline.Record the actual state of rebuild duration and URE risk. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first.
06 · cache and power-loss protectionChecking cache and power-loss protection helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline.Record the actual state of cache and power-loss protection. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first.

Investigation and change sequence

  1. Capture a baseline for HBA/JBOD passthrough and direct disk visibility to ZFS and compare it with a known-good system.
  2. Correlate evidence from SMART and error visibility and vdev fault-tolerance design to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to rebuild duration and URE risk, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check cache and power-loss protection and the real business workflow. Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.

Validation and rollback evidence

  • Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
  • Recheck rebuild duration and URE risk and cache and power-loss protection against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming HBA/JBOD passthrough is sufficient while overlooking direct disk visibility to ZFS and dependent checks.
  • Changing several settings before preserving the original evidence for SMART and error visibility.
  • A healthy RAID, snapshot or successful backup job is not proof of a recoverable workload.

Common questions and acceptance criteria

What should be checked first?

Begin with HBA/JBOD passthrough and direct disk visibility to ZFS. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousCan duplicate hostnames across virtual desktops cause domain trust, DNS, Group Policy, and sign-in problems?NextIf ransomware encrypts a shared file server, how can backups be protected from deletion or encryption at the same time?

Need an assessment based on your actual environment?