Ask HN: What strategies should I consider for backing up my home NAS
I've recently acquired a NAS (QNAP, if that matters) to help manage the data my business generates - primarily video and audio files and projects. What strategies should I consider at the outset to make offsite backups reliably, affordably, and hopefully automated for this new device?
8 comments
[ 0.24 ms ] story [ 29.5 ms ] threadWith HashBackup (I'm the author) you would connect the Fireball to your network, setup the network shared directory as explained on Backblaze's site, and use a HashBackup "Dir" destination to create your backup. Then return it to Backblaze.
After the data is loaded into your B2 bucket, change the HashBackup destination type to a "B2" destination, add your B2 credentials, and you're done. The backup can now be accessed by HB as if it were uploaded directly to B2.
I'm not pretending a network drive is local, but actually mirror the important data from my NAS to a locally connected 14TB USB drive. It stays connected all the time.
I have some cron jobs that run rsync scripts, but the data that needs to be backed up rarely changes. This gives me 30TB on my NAS, of which, 14TB are backed up in backblaze for $60/year.
I can make this work in my situation because the items I want backed up are less than the working space I want on my NAS.
The GoDaddy of cloud backups for me.
There have been numerous vulnerabilities, back doors, default passwords etc in Qnap products; search HN.
In some cases devices have been attacked with ransomware even in private networks (no ports were opened to internet) through UPnP.