

Anything running on it that accesses the internet is encapsulated by docker. This is my internal NAS, which isn't accessible from the internet, and it only runs "internal" services. Too many layers with possibility for vulnerabilities. I use FreeBSD (with jails) for my internet facing servies, running on an Intel NUC. Sensitive data gets stored through Ecryptfs and synced. ZoneMinder for replacing Surveillance Station. Logwatch for a daily status mail (also includes S.M.A.R.T. Webmin for monitoring package updates/services/hardware.
#Jottacloud synology software#
I’ve considered FreeNAS/OMV but they seem like more trouble than just configuring the stuff by hand.Īny comments ? Obvious things I’m doing wrong ? Better alternatives ?Įdit: To elaborate on the software stack, here's what i plan on using I’ve worked as a Unix sysadm for many years, but it has been almost a decade since I last put a server together for home use that was more than a Raspberry Pi or Intel NUC. I plan on using Ext4 for the SnapRaid part, and Btrfs for the md raid. On the 2圆TB drives I plan on running md RAID1 for home directories, photo collection, etc. I plan on installing Debian 9 on the M.2 drive, and setup MergerFS and SnapRaid on the 4x4TB for media storage, timemachine backups, etc. I will add 4x4TB WD Red and 2圆TB Seagate IronWolf to it.įor the software setup I will be using this as a baseline Intel Core i5-8400 Coffee Lake CPU - 2.8 GHz - Int

The hardware has been ordered, and will be delivered next week.
#Jottacloud synology free#
There's a Macrium Reflect Free version and a very affordable Home version, and it looks better designed than Acronis apps.After having used Synology exclusively for years, I had a couple of boxes die on me within weeks of each other, and I finally ordered the parts for building a new NAS from scratch. Personally, I'm thinking of moving away from True Image and trying Macrium Reflect.
#Jottacloud synology how to#
The only problem here is that you need to know how to write that script and how to schedule it to run in the wee hours. It's the same as the backup file, only it takes more space on the backup drive (same space as the source). That script would only copy new/changed files. Just copy the images to your back-up drive with a script, which can be run on a schedule. IF YOU REALLY WANT ACCESS TO THOSE BACK UP FILES, don't use a back-up app at all. This is all as it should be, because you want the back-up app to compress the heck out of that file. You may find a back-up app that lets you look inside the backup, but you can only do so from the app itself (not the operating system). The back-up file that any back-up app creates (the TIL in this case) is always going to be unreadable. If you don't have the Option button there, look around for it.
