tr1stan
Perch
Although this applies to a million current threads at the moment, I felt that it was important enough to have its own.
I can?t believe that JH does not have any form of disaster recovery, and if you do?..you certainly cannot implement it very well!
I am the webmaster for a University here in the UK, and have the responsibility of looking after about 15 separate web servers ? Now that doesn?t make me a guru, but I do have experience in hosting important websites, and keeping the customers happy.
It is every Webmaster?s nightmare, getting that call from the helpdesk telling you that a certain web application cannot be seen, or a number of websites are currently down. Suddenly you think to yourself, ?I hope it?s not a corrupt file system? or ?Wouldn?t it be great if our new raid array has decided to fall over again?. But none of this is hugely detrimental as we have DR procedures in place that reduces the amount of possible downtime by a large amount.
Why is it JH that you do not have an unused server, for each platform you run, that is just sitting around with the OS and web services installed, waiting for a particular disaster to occur. Wouldn?t it have been great for you to have been able to do a restore to the DR box the moment you new that there was even a hint of excessive downtime, run them parallel for a moment ? giving you a chance to make sure everything was 100% on the new box - and then make the switch. The only major downtime that is experienced is the time it takes to switch the servers?.which if done correctly should be no where near 15 minutes, let alone 2 ? 3 hours, or what ever you guys ?estimated?.
I was lucky in the fact that my sites are not hosted on WIN5, but that doesn?t make me any less uneasy about the whole situation.
I understand JH might try and use the excuse ?But that would cost us too much in hardware? but I really think you need to have a look at how many of your customers and your customers customers are losing patience with your level of service. It?s not like you have to buy a new server per disaster, as the server that was causing the problem in the first place, gets turned into a DR server after it has been swapped out and sorted.
I also haven?t mentioned the amount of overtime you might have to pay your staff (assuming that technicians stay on a job until it?s finished) or the amount of compensation heading in your customers direction.
It?s about being prepared for the worst and planning ahead?..try it, it might stop you going grey too early!
T
I can?t believe that JH does not have any form of disaster recovery, and if you do?..you certainly cannot implement it very well!
I am the webmaster for a University here in the UK, and have the responsibility of looking after about 15 separate web servers ? Now that doesn?t make me a guru, but I do have experience in hosting important websites, and keeping the customers happy.
It is every Webmaster?s nightmare, getting that call from the helpdesk telling you that a certain web application cannot be seen, or a number of websites are currently down. Suddenly you think to yourself, ?I hope it?s not a corrupt file system? or ?Wouldn?t it be great if our new raid array has decided to fall over again?. But none of this is hugely detrimental as we have DR procedures in place that reduces the amount of possible downtime by a large amount.
Why is it JH that you do not have an unused server, for each platform you run, that is just sitting around with the OS and web services installed, waiting for a particular disaster to occur. Wouldn?t it have been great for you to have been able to do a restore to the DR box the moment you new that there was even a hint of excessive downtime, run them parallel for a moment ? giving you a chance to make sure everything was 100% on the new box - and then make the switch. The only major downtime that is experienced is the time it takes to switch the servers?.which if done correctly should be no where near 15 minutes, let alone 2 ? 3 hours, or what ever you guys ?estimated?.
I was lucky in the fact that my sites are not hosted on WIN5, but that doesn?t make me any less uneasy about the whole situation.
I understand JH might try and use the excuse ?But that would cost us too much in hardware? but I really think you need to have a look at how many of your customers and your customers customers are losing patience with your level of service. It?s not like you have to buy a new server per disaster, as the server that was causing the problem in the first place, gets turned into a DR server after it has been swapped out and sorted.
I also haven?t mentioned the amount of overtime you might have to pay your staff (assuming that technicians stay on a job until it?s finished) or the amount of compensation heading in your customers direction.
It?s about being prepared for the worst and planning ahead?..try it, it might stop you going grey too early!
T