> If all you're doing is RAID 1 and budget is your
> primary concern, I
> think you're much better off using well-supported
> ATA controllers
> without RAID and then doing software RAID 1 using
> the Linux kernel's md
> stack. I use that a lot in production, and have been
> very satisfied with
> performance and reliability (on a budget).
>
Here's what I ended up doing:
1. I bought two (2) 160GB Seagate Drives. I went with
160GB instead of 300GB since 40-45GB of storage is
only my current needs. I figure another 110+GB should
be enough for my needs in the next 4-5 years. Plus,
the 160GB Seagate drives where on sale (less 70% after
rebate) :D
2. I bought one (1) PATA controller where the two (2)
ATA drives are connected, one on each channel.
3. Configuring my box for RAID wasn't as difficult as
I thought it would be. It took me all of two (2)
hours to attach the drives and have the RAID drives
ready for service.
4. I saved up to almost 50% of my original budget. Of
course, thanks to the suggestions from Ian, Jijo, and
Migs.
Next step for me is to write scripts to automatically
backup directories from a few boxes running Linux,
Windows, and MacOS X to my file server. For that I'm,
planning on using rsync over ssh on Linux and Windows
(cygwin), and RsyncX on MacOS X so resource forks are
also considered during synchronization.
I figure rsync should be enough for my needs, but I'm
interested to hear what software or process do you
guys use for backups.
Erm, yeah, there's also SVN Repositories and MySQL
catalogs to move to the RAID partition.
Thanks again,
jeff --
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
