Help, my disk array has one dead member

Kevin O'Gorman kogorman at gmail.com
Mon Apr 3 18:58:36 UTC 2017


On Mon, Apr 3, 2017 at 10:03 AM, william drescher <william at techservsys.com>
wrote:

> On 4/3/2017 11:41 AM, Kevin O'Gorman wrote:
>
>>
>>
>> On Sun, Apr 2, 2017 at 4:34 AM, william drescher
>> <william at techservsys.com <mailto:william at techservsys.com>> wrote:
>>
>>     On 4/1/2017 11:56 PM, Kevin O'Gorman wrote:
>>
>>         That's not going to work for me.  Most of the data is in
>>         a single
>>         SQLite database.  It's all or nothing and rsync doesn't help.
>>         Moreover, remember this is a hobby project, and I have no
>>         "offsite" to use.  I can and do back up the individual
>>         contributions to the database, or the algorithms and commands
>>         used, so restoring from those would be  possible but ugly.
>>
>>
>>     I may be completely off base for you, but we have found that
>>      using mySQL replication is our solution.
>>     The slave server is off site connected via a hardware based VPN.
>>     This gives us a hot backup of our data and the ability to
>>     switch to the backup server if the primary dies.
>>
>>     In your case it would give you the safety of continuous
>>     backup of your data.  You could have the backup server at the
>>     same location (Our "obsolete" windows machines become fully
>>     functional linux servers.)
>>
>>     of course the conversion from SQLite to mySQL would be a big job.
>>     --bill
>>
>> Not to mention arranging for an off-site repository.  It's a bit
>> beyond my personal budget.
>>
> Ignoring disaster recovery, you can do the replication in a 2nd server,
> right next to the main server. Or you can put the replication server in the
> basement and be able to recover from a tornado...
>
> As to provisioning a replication server: you can buy "old" computers for
> under $100 and you don't need a RAID setup, just a disk that is big enough
> for the OS and the database.
>
> --bill
>

Well, here in coastal California I've never seen a basement and never heard
of any tornadoes much closer than 1,000 miles.

And yeah the computer's cheap enough, but I'm already cramped with 2 of
them and anyway the disks cost more than the computer.  It's all 4TB disks,
and I've stretched the budget already with one thing and another.

As it is, I'm slowly learning what I need to make RAID work for me.  The
latest thing turned out to be power distribution inside the chassis.  All
the disks were on one of the power strings from the power supply, and when
I split the load to another one a great many problems just disappeared.  It
even appears that the title of this thread was a mistake.  That problem too
went away.

I hadn't been able to test the disks well because I couldn't get my CD of
Seagate Seatools to boot on this machine (it would encounter an illegal op
code).  I finally got the Windows version and ran that.  Individual disks
ran fine.  Testing them all together was a disaster.  I changed the power
arrangement and now all 6 drives run in parallel just fine.

Now I'm on to tuning filesystems.

-- 
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20170403/1e8eaac9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 441 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20170403/1e8eaac9/attachment.gif>


More information about the ubuntu-users mailing list