Backups broken/not broken

I did a package upgrade on my NAS last week. Not even a DSM upgrade, just a couple of packages (HyperBackup and node.js). Unfortunately the HyperBackup upgrade broke the overnight backup process. No amount of fiddling and farting about (it’s a technical term) could get the process reinstated. In the end I removed everything from HyperBackup and set a new global all-user backup. On completing the process and the new mapping, HyperBackup asked me if I’d like to kick off a process right now? Sure, I said. I’m here for that. This is the reporting screenshot from that first backup:

I had forgotten that the first global all-user backup not only packs and transfers the target files and directories, it also has to create metadata and then map all files/directories to that metadata as it creates a mirror (which it can use as a point of reference for the next – and all future – backups). Der. Anyway, the second backup process reported this:

Much better!

Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *