Backup Strategy for a Private Cloud: Applying 3-2-1 in a Self-Hosted Setup
The most common mistake in a self-hosted cloud is treating “we have RAID” as “we have backups”. The two solve entirely different problems, and many people only learn the distinction after losing data.
RAID is not backup
RAID addresses availability when a drive physically fails: if one disk dies, the system keeps running. It does not protect against accidental deletion, ransomware, fire, flood or a failed chassis. With only one RAID array, a single mistaken delete command can wipe the data on every drive at once.
Applying 3-2-1
The classic rule: at least 3 copies of your data, on 2 different media types, with 1 copy off-site. In a self-hosted setting that maps out like this.
Copy one is the working set on the SATA array of a 04A NAS-RK3588 network storage board — it carries 4× SATA 3.0 for 2.5″/3.5″ drives, an M.2 NVMe for system and cache, and 2× 2.5GbE delivering above 280MB/s per port, so backup jobs do not slow down daily use.
Copy two is a local snapshot or external drive, on a different medium. Copy three goes off-site: object storage, another machine, or a drive you rotate out periodically. The key to off-site is not technology but automation — manual backups eventually get forgotten.
Rehearse the restore
More important than the backup strategy is verifying recovery. Whether the backup restores, how long it takes and what it depends on are questions only a rehearsal answers. Run a restore test at least quarterly, even if it only covers a handful of files.
The extra value of RK3588 here
NAS-RK3588 includes a 6 TOPS NPU with RKNN and TensorFlow Lite support. Where it earns its place in a backup setup is content indexing: face clustering in photo libraries, duplicate detection and video structuring can all be offloaded from the CPU. Anyone who has built a photo server knows the first index pass over tens of thousands of images can pin the CPU for hours.
If you previously ran a lightweight NAS on something like RK3528, moving to RK3588 is mainly about drive bays, network ports and compute headroom. Specifications are on the NAS-RK3588 product page.
