No, No, No... You have it all wrong.
We just know more than you!
easyhostmedia,
As mentioned before, it's not about your reports/software says. Your software does what it's told to do by programmers. I believe the real meaning of "100% uptime" is for the clients service/site to never go offline EVER. It's okay that you reboot but as long as you can keep the site live using a backup/secondary server while you update/reboot then your okay.
Thanks,
Logan Falletta
I wasn't trying to prove anything really. Simply trying to have easyhostmedia look at differently rather then turning back to his reports. The logs can say whatever but if a client logs on or is working late hours an all sudden the site is offline. The client is not going to care that you say "Oh, well my reports say it was never down" - The client will take his file and db to another provider instantly. All an all don't ever advertise 100% uptime. End of discussion
I have to side with the theory that any downtime, whether it is a restart or not, is downtime. As a customer, I don't care what the reason behind my server being down for 5 minutes is. If I cannot connect to the site in 5 minutes, that means I lose visitors.
On the other hand, I don't yet know of any provider with a streamline offering like shared, reseller, VPS or a dedicated hosting that guarantees 100% uptime.
i dont and have never advertised 100% uptime
Sounds like a good service they have there!
I've read through this thread with interest. It seems the issue here is what the definition of "uptime" is.
A server that is rebooting will rarely show any downtime via some monitoring services as they simply ping the server to see if it responds (yes, some will do tests on port 80, 143, 110 25 etc too but they are normally "premium" services).
Rebooting a server is downtime - albeit maybe only a couple of minutes - but it would be noticeable to anyone using a service such as browsing a website or downloading email on the server at the time.
The reason monitoring tools may not detect it as downtime is because the pings during a reboot may only stop for a few seconds whilst the server runs through POST and the NIC becomes available again.
So whilst the server may ping, the webserver, mail server, DNS, MySQL etc could all be down. You cant say to a client "I'm sorry your website isn't working but we do have 100% uptime" when at the same time Apache hasn't restarted after the reboot! You cannot reboot a server without causing downtime unless you have a HA (high availability) cluster in place (and even then that particular server still had downtime, just it's effects are not noticable)
It's for this reason some hosts use Ksplice to install kernel updates etc so they can update without rebooting and causing downtime.
In essence, yes you can make stats and pretty graphs show that you have 100% uptime depending on how often they check services, but in reality you can't have 100% uptime if you reboot.
Steve
20 years on the internet starting in 1992 with a 2400/9600bps modem and Spry Mosaic browser
15 years in the IT/Hosting industry
they confirmed that all servers they provide are linked to a secondary server and even that has a backup so that during reboots/updates etc. any sites/services still remain online so offering a 100% uptime rate, then only thing they cant forsee would be a hardware issue
ive been able to use the RMS service at the same time as rebooting which backs up what my server provider states