An option for the cash flow issue... outsource your server hosting to
somebody like Rackspace, Amazon, etc. Let them pay for the bandwidth.
Then with the reduced requirements internally, you can reduce your
Internet service enough to cover the the costs of the remote servers
(which are really cheap in the big picture...)
I've recently done this. Between moving my hosted websites to my
new(ish) virtual server, and not needing static IP's for my own
connection anymore, I'll be making money once I reduce the Internet
service from business class.
Food for thought.
Shawn
On 14-04-20 07:56 PM, TekBudda wrote:
Basically I do not see the point of using the 323 in this case as it
will only teach bad storage habits. Instead I would focus on a killer
CentOS configuration. You can get disk redundancy with mdadm or btrfs
(pretty much all the RAID levels are supported with a bunch of stuff
that RAID arrays cannot do). If you are looking for inspiration I would
check out this article
http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/
For an advanced setup get a second Linux machine and do replication or
better still, play with clustered file systems (gluster, ceph, swift,
gpfs and many more).
*** This is part of the problem. Don't have extra cash floating around.
In fact the server is an old 2.8 Ghz box with 2-3 GB in it. I am
basically trying to use the tech I do have until I am at a point where I
can justify the extra expense. Yes...will be a little bit more of a
challenge but you can only do what you can with what you have.
I have heard about gluster & have thought about using it. One step at a
time.
The take away is that a NAS like the DNS323 or the simply incredible
Synology boxes, hide all of the details that you actually want to learn
and eventually use as marketable skills.
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
