S] 10 Year old IT Infrastructure
Morning,
On 10 Oct 2009, at 17:12, Brian Mathis wrote:
> The better solution would be to make sure you are prepared for when
> the hardware does fail. Inform the client that you understand that
> they don't want to upgrade the servers, and that hardware
R-Elists schrieb:
>> Specific arguments I can think of would be:
>> - Hard/Impossible to find replacement hardware
>> - Lack of support for both H/W and S/W
>> - Possibly unable to run current versions of CentOS
>> - Higher probability of hardware failures over time
>> - Performance bottlenecks
>>
Morning,
On 10 Oct 2009, at 17:12, Brian Mathis wrote:
> The better solution would be to make sure you are prepared for when
> the hardware does fail. Inform the client that you understand that
> they don't want to upgrade the servers, and that hardware failure is
> not a case of "if" but "when".
Approach him like this. Tell him if he plans on moving his business forward
within the next 5 years he should think accordingly.
On Sun, Oct 11, 2009 at 11:26 PM, R-Elists wrote:
>
> >
> > Specific arguments I can think of would be:
> > - Hard/Impossible to find replacement hardware
> > - Lack o
>
> Specific arguments I can think of would be:
> - Hard/Impossible to find replacement hardware
> - Lack of support for both H/W and S/W
> - Possibly unable to run current versions of CentOS
> - Higher probability of hardware failures over time
> - Performance bottlenecks
>
> Any other thoughts
Brian Mathis wrote:
> On Sat, Oct 10, 2009 at 2:14 PM, Giovanni P. Tirloni
> wrote:
>> On Oct 10, 2009, at 3:08 PM, Alan McKay wrote:
>>
The better solution would be to make sure you are prepared for when
the hardware does fail. Inform the client that you understand that
>>> This is b
Brian Mathis wrote:
> Also, when I say "describe what would happen", I'm not talking about
> how a board might blow a capacitor, I'm talking about how you will
> react and what the impact is on the business during that time
double or triple your support contract rates for systems deemed past
EOS
On Sat, Oct 10, 2009 at 2:14 PM, Giovanni P. Tirloni wrote:
>
> On Oct 10, 2009, at 3:08 PM, Alan McKay wrote:
>
>>> The better solution would be to make sure you are prepared for when
>>> the hardware does fail. Inform the client that you understand that
>>> they don't want to upgrade the server
On Sat, 2009-10-10 at 14:08 -0400, Alan McKay wrote:
> > The better solution would be to make sure you are prepared for when
> > the hardware does fail. Inform the client that you understand that
> > they don't want to upgrade the servers, and that hardware failure is
> > not a case of "if" but "w
Alan McKay wrote:
> On Sat, Oct 10, 2009 at 2:14 PM, Giovanni P. Tirloni
> wrote:
>
>> Can you get something like the average lifespan of the circuits in
>> hours ?
>>
>
> HDs and other components should have published "MTBF" - Mean Time
> Between Failure
>
which is just about meanin
At Sat, 10 Oct 2009 13:44:54 -0500 CentOS mailing list
wrote:
>
> Alan McKay wrote:
> > On Sat, Oct 10, 2009 at 2:14 PM, Giovanni P. Tirloni
> > wrote:
> >> Can you get something like the average lifespan of the circuits in
> >> hours ?
> >
> > HDs and other components should have published
Alan McKay wrote:
> On Sat, Oct 10, 2009 at 2:14 PM, Giovanni P. Tirloni
> wrote:
>> Can you get something like the average lifespan of the circuits in
>> hours ?
>
> HDs and other components should have published "MTBF" - Mean Time
> Between Failure
But they are never realistic in terms of act
On Sat, Oct 10, 2009 at 2:14 PM, Giovanni P. Tirloni wrote:
> Can you get something like the average lifespan of the circuits in
> hours ?
HDs and other components should have published "MTBF" - Mean Time
Between Failure
--
“Don't eat anything you've ever seen advertised on TV”
- Mich
At Sat, 10 Oct 2009 15:14:13 -0300 CentOS mailing list
wrote:
>
>
> On Oct 10, 2009, at 3:08 PM, Alan McKay wrote:
>
> >> The better solution would be to make sure you are prepared for when
> >> the hardware does fail. Inform the client that you understand that
> >> they don't want to upgrad
On Sat, 10 Oct 2009 15:14:13 -0300
Giovanni P. Tirloni wrote:
> Can you get something like the average lifespan of the circuits in
> hours ?
I always tell people that a computer is like a light bulb -- you can't tell by
looking at it how much life it has left in it. Just like a light bulb, eve
On Oct 10, 2009, at 3:08 PM, Alan McKay wrote:
>> The better solution would be to make sure you are prepared for when
>> the hardware does fail. Inform the client that you understand that
>> they don't want to upgrade the servers, and that hardware failure is
>> not a case of "if" but "when". L
> The better solution would be to make sure you are prepared for when
> the hardware does fail. Inform the client that you understand that
> they don't want to upgrade the servers, and that hardware failure is
> not a case of "if" but "when". Lay out a plan to them describing what
> would happen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thus Brian Mathis spake:
> On Fri, Oct 9, 2009 at 8:01 PM, Shawn Everett wrote:
>> Thanks to everyone for their comments so far.
>>
>> The "server" in question is a basic 2 node cluster connected to an MSA500.
>>
>> It runs a variety of applications i
Shawn Everett wrote:
> Thanks to everyone for their comments so far.
>
> The "server" in question is a basic 2 node cluster connected to an MSA500.
>
> It runs a variety of applications including Oracle, Apache, Samba, and a
> proprietary app built by another vendor.
>
> The hardware is monitore
On Fri, Oct 9, 2009 at 8:01 PM, Shawn Everett wrote:
> Thanks to everyone for their comments so far.
>
> The "server" in question is a basic 2 node cluster connected to an MSA500.
>
> It runs a variety of applications including Oracle, Apache, Samba, and a
> proprietary app built by another vendor
I'm in the position of having both the mission critical & regular servers.
Our mission critical machine, an app server that runs about 90% of our
business, we lease so it gets recycled every five years. For us, it's
worth the extra cost to have equipment under warranty with parts
guaranteed next b
2009/10/10 Gordon McLellan :
> The best part the vendors deal, the "upgrades" will cost us the same price
> if we buy the server from him or not - opting not to buy overpriced hardware
> causes the programming fee to inflate by an equal amount - how is that for
> service!
Sounds like a fantastic
On Fri, Oct 9, 2009 at 7:28 PM, Bill Campbell wrote:
> FWIW, that 12+ year old SCO system can probably run quite nicely
> under a VMware virtual machine, and be significantly faster than
> it is today. You won't get support for hardware like Specialix
> multi-port boards, so may have to replace a
Thanks to everyone for their comments so far.
The "server" in question is a basic 2 node cluster connected to an MSA500.
It runs a variety of applications including Oracle, Apache, Samba, and a
proprietary app built by another vendor.
The hardware is monitored, maintained and backed up regularly
On Fri, Oct 9, 2009 at 4:29 PM, Shawn Everett wrote:
> Hi Guys,
>
> I have a client who hopes to keep their server another 5 years making it
> 10 years old at that time.
>
> At this point there are no plans to add new infrastructure or a new server
> to the mix. Their business model is fairly sta
On Fri, Oct 09, 2009, Gordon McLellan wrote:
>On Fri, Oct 9, 2009 at 6:29 PM, Shawn Everett wrote:
>> Hi Guys,
>>
>> I have a client who hopes to keep their server another 5 years making it
>> 10 years old at that time.
>>
>> At this point there are no plans to add new infrastructure or a new serv
On Fri, Oct 9, 2009 at 6:29 PM, Shawn Everett wrote:
> Hi Guys,
>
> I have a client who hopes to keep their server another 5 years making it
> 10 years old at that time.
>
> At this point there are no plans to add new infrastructure or a new server
> to the mix. Their business model is fairly sta
On Fri, Oct 09, 2009, Shawn Everett wrote:
>Hi Guys,
>
>I have a client who hopes to keep their server another 5 years making it
>10 years old at that time.
>
>At this point there are no plans to add new infrastructure or a new server
>to the mix. Their business model is fairly static.
>
>I'd like
Good one.
I run into very similar situations.
Focus purely on cash cost of maintenance of older stuff vs newer stuff.
Quote reputable sources like Gartner Group, etc...
Get a little familiar with ITIL in terms of like cycle.
Its very daunting to convince companies to spend money but if you
f
Hi Guys,
I have a client who hopes to keep their server another 5 years making it
10 years old at that time.
At this point there are no plans to add new infrastructure or a new server
to the mix. Their business model is fairly static.
I'd like to see them upgrade. Can anyone suggest specific r
30 matches
Mail list logo
