[olug] OT: shoot me

[William Langford]

If it was a solo guy going into a little manual transmission old car,  
wasn't me but a coworker.

Sent from my iPhone

On Jul 24, 2009, at 1:10 AM, charles.bird at powerdnn.com wrote:

> Was that u that just left?
>
>
> -----Original Message-----
> From: William Langford <unfies at gmail.com>
>
> Date: Fri, 24 Jul 2009 01:07:29
> To: Omaha Linux User Group<olug at olug.org>
> Subject: Re: [olug] OT: shoot me
>
>
> It's severely looking like it'll be a nasty hack to make this happen.
> We pride ourselves on dirt cheap setups that do what's needed and are
> rock solid - and it's looking like high availability on the windows
> side of things is gonna involve expensive hardware for microsoft
> clustering, or expensive software to do the highavailabilty automation
> without ms clustering.
>
> So I'm seeing two Linux boxes with a windows server virtual machine
> and NLB configured on each - along with SQL express or ancient ms SQL
> installed. Those just act as a connection front end and pass queries
> on to a Linux based HA backend. Or possibly a windows OSS backend that
> has it's own HA stuff (skipping the VM stuff).
>
> Mysql's clustering backend has lots of Linux love, but is listed for
> development only under windows. Postgres's SLony stuff looks to handle
> replication fine under windows, but doesn't supply automagical
> failover/heartbeat stuff. Either backend plus heartbeat under linux
> offers what's wanted, and brute forcing the matter with DRBD under
> Linux is possible as well.
>
> So, developer status mysql cluster engine under windows, or virtual
> machine windows to a linux postgres/mysql back end. I have much more
> postgres experience.... Sooo.... Leaning that way.
>
> I'm open to suggestions, but keep in mind my resources for the project
> will make most any admin cringe :)
>
> Linux for the win!
>
> Sent from my iPhone
>
> On Jul 23, 2009, at 8:17 PM, "Charles.Bird"
> <charles.bird at powerdnn.com> wrote:
>
>> I agree with Chris, if you can hookup with a msdn subscription/
>> bizspark or
>> whatever, I'd go with 2008, R2 just came out by the way.
>> I know we've had some issues with DFS on 2003 Ent., thats why we use
>> 2008
>> for webfarms, it works well.
>> I'll dig up some documentation whenever i get back to the office, I
>> have to
>> restore a server from a backup and provision a few servers at the DC
>> asap.
>>
>>
>>
>>
>> On Thu, Jul 23, 2009 at 8:08 PM, Christopher Cashell <topher-olug at zyp.org
>>> wrote:
>>
>>> On Thu, Jul 23, 2009 at 8:01 PM, Will Langford<unfies at gmail.com>
>>> wrote:
>>>> Going through the DFS wizard on 2kas, it offers an initial two
>>>> option
>>> thing
>>>> for the DFS root... something as part of a domain with automatic
>>> replication
>>>> stuff, and a 'standard' that doesn't use active directory for file
>>>> replication blah blah blah.
>>>
>>> Just a warning. . . having setup DFS and MSCS based services on
>>> multiple variants of Windows Server, Windows 2000's support for
>>> either
>>> was. . . well, rudimentary doesn't even begin to describe it.  A  
>>> "sad
>>> joke" would probably be fairly accurate.  It will probably cost you
>>> more in time, effort, pain, and emotional anguish counseling than it
>>> would to go with a newer OS release.
>>>
>>> If it's important enough to need clustering, I'd suggest it's
>>> important enough to look at alternative options (be it different DB,
>>> different OS, different OS version, or different solution entirely).
>>>
>>> Just my thoughts, having been through that pain before. ;-)
>>>
>>>> -Will
>>>
>>> --
>>> Christopher
>>> _______________________________________________
>>> OLUG mailing list
>>> OLUG at olug.org
>>> https://lists.olug.org/mailman/listinfo/olug
>>>
>> _______________________________________________
>> OLUG mailing list
>> OLUG at olug.org
>> https://lists.olug.org/mailman/listinfo/olug
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug