On Sun, Apr 20, 2014 at 9:24 PM, Anand Singh <an...@linizen.com> wrote:
> I chose iSCSI because it makes it easy to expand the available storage to > OwnCloud should the need arise. I can just throw another NAS at it. It also > lets me use a specific file system for different folders within OwnCloud. > Media can be XFS, while small files from industrial applications can be in > EXT2. It's probably doable in LVM, but could be messy. The reason I > prefer to use a NAS for file storage is that I can trunk/LAG the ports > easily. > > MPIO is not easy to get right, especially if you have never worked with it before. You do not want to do your link aggregation outside of iSCSI since the protocol is not very tolerant of out of order packets. This sort of thing will eat your data. It does not matter to the OP since the DNS323 is quite old at this point, and I don't remember it ever supporting iSCSI (I used to own one). LVM is also not great to work with. Now that btrfs is coming into it's own, it pretty much obsoletes LVM anyway. I am huge fan of btrfs btw. > LDAP integration didn't require any technical knowledge. You just need to > provide the bind dn, domain dn and manager password as far as I remember. > > If you plan to expose your installation, make sure you disable or block > webdav. I'll never understand why all these file storage projects still > support it. > Webdav is still a very useful protocol, especially since there are lots of clients that still support it. In addition, some of us like to interact with our remote file systems without using the abomination that is a modern browser. :) The browser is sort of useful for some things, acting as an interface for storage is not one them. I do not see the age of your hardware as an impediment here. You can still build a killer a "server" on that old hardware, and still teach yourself a ton of really useful and marketable skills. I did not mean to imply that you needed to spend money, only that you did not need to involve the DNS-323. My hosted server is actually built around a Core i3-2130, so you don't need a lot of CPU horsepower for most of this stuff. Generally speaking you will be bandwidth (especially if you are hosting this at home) and memory constrained before you bottleneck on the CPU. An owncloud instance built in a Linux container, sitting on top of btrfs that does hourly copy on write snapshots would be an amazing project that should be well within nearly everyone's reach. If I were to build my owncloud install over again this is how I would do it. You could skip the container step and still have a killer setup and gain a ton of experience along the way. Hth,
_______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
