Server OUT OF ORDER - VW Hosting

Dear Sir,

One of our server is down.

No connection at all during the past 20 hours. The company is losing
the main part of its clients.

The hosting company is Val uew eb.

C:\Users\amin6>tracert 207 36 196 211

Détermination de l'itinéraire vers 207 36 196 211
avec un maximum de 30 sauts :

1 1 ms <1 ms <1 ms WANADOO-6120 [192.168.1.1]
2 42 ms 42 ms 42 ms
rv11lo2.lnaub151.Aubervilliers.francetelecom.net
[193.253.160.3]
3 41 ms 42 ms 40 ms 80.10.215.197
4 42 ms 42 ms 41 ms 81.253.129.209
5 42 ms 41 ms 42 ms
pos0-7-0-0.auvtr1.Aubervilliers.opentransit.net
[193.251.243.29]
6 68 ms 42 ms 42 ms
tengige0-3-0-7.pastr1.Paris.opentransit.net [193
..251.251.213]
7 42 ms 41 ms 42 ms level3-2.GW.opentransit.net
[193.251.251.214]
8 45 ms 53 ms 54 ms ae-31-53.ebr1.Paris1.Level3.net
[4.68.109.94]
9 42 ms 50 ms 53 ms ae-1-100.ebr2.Paris1.Level3.net
[4.69.133.82]
10 132 ms 125 ms 125 ms ae-5.ebr2.Washington1.Level3.net
[4.69.132.113]

11 134 ms 125 ms 125 ms ae-92-92.csw4.Washington1.Level3.net
[4.69.134.1
58]
12 124 ms 126 ms 125 ms ae-91-91.ebr1.Washington1.Level3.net
[4.69.134.1
41]
13 149 ms 144 ms 143 ms ae-2.ebr3.Atlanta2.Level3.net
[4.69.132.85]
14 * 147 ms * ae-78.ebr2.Atlanta2.Level3.net
[4.69.134.53]
15 164 ms 164 ms 164 ms ae-5-5.car1.Tampa1.Level3.net
[4.69.133.49]
16 156 ms 156 ms 155 ms ae-14-14.car4.Tampa1.Level3.net
[4.69.133.58]
17 157 ms 156 ms 156 ms HOSTWAY-COR.car4.Tampa1.Level3.net
[4.71.2.14]
18 * * * Délai d'attente de la demande dépassé.
19 157 ms 156 ms 157 ms 66.230.227.170
20 * * * Délai d'attente de la demande dépassé.
21 * * * Délai d'attente de la demande dépassé.
22 * * * Délai d'attente de la demande dépassé.
23 * * * Délai d'attente de la demande dépassé.
24 * * * Délai d'attente de la demande dépassé.
25 * * * Délai d'attente de la demande dépassé.
26 * * * Délai d'attente de la demande dépassé.
27 * * * Délai d'attente de la demande dépassé.
28 * * * Délai d'attente de la demande dépassé.
29 * * * Délai d'attente de la demande dépassé.
30 * * * Délai d'attente de la demande dépassé.

Server 66.230.227.170 is not our server. We do not have any control of
that particular server. This server is an internal server VW.

Saturday night and Sunday : Admin-People from the hosting Company are
partially working during these times.
Consequences are important for us : losing money, clients, and
credibility.
That is a loss of USD 31.000 in Net.Sales over the next 24 months
period.

Hosting customer server says "they gonna have a look at it" : always
cool and quiet.

What sort of thing we may do to avoid such critical situations ?

Many Thanks for any operational advise.

Bob

On Sun, 11 Nov 2007 02:02:39 -0800, 2401 members, members can post
rearranged some electrons to say:

> Dear Sir,
>
> One of our server is down.
>

> What sort of thing we may do to avoid such critical situations ?
>
Use a different hosting company, if you don't like the service you're
getting.

2401 members, members can post wrote:

> One of our server is down.
>
> No connection at all during the past 20 hours. The company is losing
> the main part of its clients.

<snipped irrelevancies>

> Hosting customer server says "they gonna have a look at it" : always
> cool and quiet.
>
> What sort of thing we may do to avoid such critical situations ?
>
> Many Thanks for any operational advise.
>
> Bob

Hello again, "Bob".

It's quite simple: buy more servers, and implement High Availability.

If you need a Linux newsgroup to tell you this, then you, sir, are not
sysadmin material.

J.

On Nov 11, 2:02 am, "2401 members, members can post"
<Paul_Me...@2cuk.co.uk> wrote:

> That is a loss of USD 31.000 in Net.Sales over the next 24 months
> period.
>
> Hosting customer server says "they gonna have a look at it" : always
> cool and quiet.
>
> What sort of thing we may do to avoid such critical situations ?

Immediately implement your company's emergency continuation of
business plans. If you didn't bother to create such a plan and didn't
negotiate a recovery procedure with your hosting provider, there's
really not a whole lot you can do now.

1) Make sure you have your data and that it's secure.

2) Make sure you have control over your domain name and that you can
point it to whatever name servers you need to.

And damn it, do that *before* you have a disaster. You don't try to
figure out what to take and where to meet *while* your house is on
fire.

DS