From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 15CBA1EFAA8; Sat, 12 May 2018 12:45:58 -0400 (EDT) Received: from lothlorien.nfbcal.org (ns.NFBCAL.ORG [157.22.230.125]) by befuddled.reisers.ca (Postfix) with ESMTPS id 9F3661EF9CB for ; Sat, 12 May 2018 12:45:54 -0400 (EDT) Received: from lothlorien.nfbcal.org (localhost [127.0.0.1]) by lothlorien.nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id w4CGjXro008533 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 12 May 2018 09:45:33 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.3 at lothlorien.nfbcal.org Received: (from buhrow@localhost) by lothlorien.nfbcal.org (8.15.2/8.12.11) id w4CGjVbY023825; Sat, 12 May 2018 09:45:31 -0700 (PDT) Message-Id: <201805121645.w4CGjVbY023825@lothlorien.nfbcal.org> From: Brian Buhrow Date: Sat, 12 May 2018 09:45:31 -0700 In-Reply-To: X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: "Speakup is a screen review system for Linux." , covici@ccs.covici.com Subject: Re: Unraid, freeNAS Cc: buhrow@nfbcal.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (lothlorien.nfbcal.org [127.0.0.1]); Sat, 12 May 2018 09:45:34 -0700 (PDT) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.24 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2018 16:45:58 -0000 hello. chiming in on this thread. Another approach to backing up large amounts of data is one I've been using for over 10 years. My main server has 4 disks on it, raided together with a raid5 configuration. At the time I built it I used 768GB disks, giving me a total storage of just over 2.3TB of storage capacity (768 X 3 disks). I then allocated half of that space for backups, and partitioned the remainder for normal use. I then run backups of the data to the backup area, to cover human errors or to restore old copies of files. And, because I'm using raid5, as disks died, I was able to replace them without a loss of data or even much down time. This approach is scalable using larger and larger disks, or, if you hav more physical space, more and more disks. I like raid5 because you only lose one disk worth of space for the parity disk and you can lose any one disk and still be ok. The down side is that you need to be ready to replace any disk at a moment's notice, since you don't want to run in degraded mode for any length of time. If you're paranoid, you can run raid6, which means you only need to spend 2 disks worth of storage, but can lose up to 2 disks simultaneously without losing any data. The raid5 and raid6 configurations are a bit more complicated to set up, but they let you use your total storage capacity more efficiently and are more resilient to different kinds of disk failures. Another approach, which might be easier to set up and operate, is to use raid1 and raid5/6 simultaneously. Use raid1 (mirroring) on some relatively small boot disks, so you can boot from either disk and still be good to go. Then, use larger disks in the raid5/6 sets for data and backups. All of this can be done with off the shelf consumer hardware, using standard linux tools, without paying too much money. Just my 2 cents. -thanks -Brian