11–20 of 150 posts
Earlier quoted context omitted.
What's your power consumption like on this set up?
Sits at about 250W, goes up to ~300W when it's running a scrub or something.
[1]: http://www.rapidtables.com/calc/electric/electricity-calcula...
Earlier quoted context omitted.
Got to ask about the elephant in the room, but what do you use it for / host? Personally, I'm thinking of building a FreeNAS for photo storage / media, but unfortunately I've only got a four-drive array SuperMicro rack server (spare one I have from decomissioning a business). Other things I'm interested in is perhaps hosting a few gaming servers and such for friends/family (Minecraft, etc.) Hard to find uses for it o…
I do a lot of high resolution photography and videography work. I've got about ~15 years of raw images and video files that I could probably go through and delete, but I'd rather keep them around so I can pretend that maybe some day, someone will be interested in looking at them. I look at it as a modern version of the boxes full of pictures and slides my parents and grandparents kept in their basement for decades an…
My experience with the FreeNAS people was "build a second nas", but that always struck me as stupid for a home setup.
I originally posted this on reddit, but I'm happy to see it reposted elsewhere. Let me know if anyone has any questions.
One questions I have regarding NAS is backups of the NAS itself.
If I have a very simple NAS with 2 drives in Raid 1 (let's call it Drive A and B), and I want to make a physical backup of my NAS in a different location. How easy is it ? What is the best practice. Ideally you could just have a big rsync method that takes care of it, or rclone as described in the article, but what if you want to do it without any network transfer (because your connection is too slow/ you can't afford it)
Does the following protocol make sense: Removing Drive A , replacing it with an empty drive C. Wait for the NAS to synchronize drive C. Then remove Drive B, replace with drive D, wait for the NAS to synchronize drive D.
Taking Drive A and B to a different location, plug them, and have the backup working out of the box.
Is it that easy? What about more complicated RAID setups?
is there an easy "Prepare Backup -> Please insert First drive for your backup -> First drive filled up -> please insert second drive for your backup -> ... -> Please insert last drive for your backup" and then you take all those newly filled drives and shove them in a different box and they have all the data at the time of the backup, with either the right zfs and raid configuration, or at least a simple data dump in a non-raid configuration.
Earlier quoted context omitted.
What's your power consumption like on this set up?
Sits at about 250W, goes up to ~300W when it's running a scrub or something.
Has anyone taken a deep dive look into rclone crypto? I looked around but didn't find anything in a quick search. Only thing I've seen so far is https://rclone.org/crypt/
In other words, to my non-crypto-expert eyes, there is no glaring misuse of the "golang.org/x/crypto/nacl/secretbox" API that jumps out at me; I haven't looked at that package to see if it's okay.
[1] https://news.ycombinator.com/item?id=12398303#12398727 [2] https://godoc.org/golang.org/x/crypto/nacl/secretbox [3] https://github.com/ncw/rclone/blob/master/crypt/cipher.go
Earlier quoted context omitted.
Sits at about 250W, goes up to ~300W when it's running a scrub or something.
Did you consider a low power NAS approach? Spending somewhere around $20 per month on electricity for a home server seems like a lot to me. Maybe if it was hosting a handful of VMs for various purposes, but I suppose you don't want to run a NAS as a VM?
as a comparison, s3 for 60tb is $1600 a month.
I like the creative use of what appears to be an Ikea table for a rack.