HN user

0kto

8 karma
Posts0
Comments12
View on HN
No posts found.

I recently converted all my Linux boxes to use BTRFS filesystems. That allows for snapshots of each sub volume, and you can even send them (incrementally) to another btrfs drive. Last weekend I also set up btrbk, which gives you an environment to automate the process. It let's you snapshot any subvolume to a schedule you configure, and then send backups to any destination you specify via ssh, or even USB drives. Since these are incremental it uses very little bandwidth. It even has an archive function for long term storage, and just like the other backups you can define individual retention policies for each location. Did I mention it also supports non-btrfs support, encryption, and both host/server initiated backups? Awesome. Next weekend I'll set up encrypted archives to the cloud...

I use a small SoC (X10SBA from supermicro) in a mini-ITX case that fits 6 HDD drives (currently 3x3TB raid6) running Arch Linux. The Intel celeron J1900 is more than up to the task, and you get a low powered device with which you can serve a website, have a NAS, media center, headless server, syncthing, etc. Great experience so far and quite inexpensive device that runs 24/7.

Well, only the DataFrames.jl package comes to my mind. However, there exist a few packages that extend this package (DataFramesMeta.jl or Query.jl; these overlap to some extend, but the newer Query package seems to go beyond DataFrames and offers some piping capabilities to interface with plotting packages). In general: During the three years of my PhD some language / package upgrades broke some of my scripts (during 0.4 -> 0.5 and -> 0.6), but the language (and its extensive documentation, online and from the source code of the packages) is very pleasant to use - the deprecation warnings usually help you to adjust your code in time. I have been relaying heavily on said DataFrame package, and am quite happy - the community is usually responsive and helpful in case of problems or questions.