I currently have a Signature VPS with Servint and although I have found their customer service good and am getting concerned about my VPS's reliability. This is the only VPS I have experience with.
At the beginning of the year I was experiencing downtime at least once every couple of weeks and for at least 20 mins each time. Sometimes my VPS was down for over an hour. Most of the time the explanantion I received was a "Kernal Panic". Then for the last month and a half things have been good with no downtime, until today when my VPS went down again for about 50 mins.
So here I am asking what is normal downtime?
Is the downtime I am experiencing the norm and would I get the same reliability from any provider?
Would a dedicated server tend to be more reliable than a VPS?
I am considering moving to a dedicated server at LiquidWeb, not because I need the resources but I am wondering if reliability would improve. I am willing to pay for reliability! Any advice as to whether this would be a good move?
Do any of you know the best way to build a high reliability e-mail system?
I currently have Interworx as the default Control panel but are happy to change to Cpanel or otherwise. The iworx HA is not that good as if the cluster manager fails you loose everything.
I guess my only option is to do what most companies do and hope for the best - but have a good disaster recovery plan.
is it really worth the money nowadays to put in SCSI or SAS instead of SATAII (single disk, non-raid here), IF reliability is the only concern (i.e. NOT i/o performance) during the usual 3 year life time of a server?
Actually, I was pretty amazed by the sata reliability, in the past 3 years the only hdd failure was two sata on a mismatched mobo, which didn't support SATAII (a lot of read/write error, eventually died). Although we have 0% scsi and sas failure.
to colocate a 1U in the DC metro area for $100/month for a small non-profit I work with. The service necessary is pretty basic -- 1Mbps or so would do (preferably unmetered so we're not on the hook for overage charges), 1 or 2 IPs would be fine, and the only real service necessary (besides steady power and connectivity, of course) would be the occasional remote reboot and 24/7 facility access.
I've come close to settling on Crosslink Internet (web site at www dot crosslink net, silly system won't let me post the URL directly because I'm new), because they're the only place I've found that can meet that price point. Before I commit, though, I wanted to hear from you guys:
* Are they a reliable ISP? They sound sort of low-budget over the phone, and while that's not necessarily a valid indicator of reliability, it makes me nervous.
* Are there any other decent ISPs in the Northern VA vicinity that could meet this price point that you guys would suggest over Crosslink?
I would really like to know which hard drive brand you have had the best success with in regards to server hard drive reliability. Is it Seagate or Western Digital? Or is it one of the other brands? Please vote. This poll is specifically regarding SATA2 hard drive experiences in servers. Please do not factor in SCSI hard drives.
In order to increase the reliability of a audio streaming service I am thinking to take the action I describe below.
1. Buy two Windows VPSs with WMS installed.
2. Register a domain name (i.e audiostream.com) with 4 nameservers: ns1.ip1_vps1, ns2.ip2_vps1, ns3.ip1_vps2, ns4.ip2_vps2.
3. Create all publishing points (streams) on both servers.
Normaly VPS1 should serve all clients. In case VPS1 goes down, VPS2 should jump in and serve all clients-connections. As soon as VPS1 becomes available (ns1 & ns2 start responding again), VPS1 starts serving all new connections.
Load balancing or any other kind of advanced load, traffic, etc management is not important.
Then we have the following cases: 1. VPS1 is down , which means that VPS2 should take charge.
2. VPS1 is up (ns, http, ftp services), but WMS1 is down (crashed). Means that the playlist (asx) file should be built so that it also includes the IP, port & publishing points of VPS2. This should be done because ns1 & ns2 will answer without any problem, but WMS1 will be crashed and won't serve any media connections, thus ASX will look for the next available stream in the playlist.
Do you think that the above is possible. Is this gonna work?
Is there any conventional wisdom on WHT about which shared hosting providers have highly reliable email service?
The provider I have now has very good web hosting service but their email services tend to bitbucket far too much mail for comfort. Reliable delivery and reception for the half a dozen emails I might send/receive a day (it's a personal use site) is I hope not too much to ask without needing to pay and arm and a leg for the privilege.
1) Processor: Intel Core 2 Duo 2,2 GHz; 2) RAM: 2024 MB DDRAM; 3) Hard Drive: 2x 250 GB SATA (can be smaller); 4) Traffic: At least 1000 GB or unrestricted; 5) Port: 100 Mbit / sec. (ideally 1000 Mbit / sec.); 6) IP-Addresses: 2.
Mandatory conditions: 1) A great date-center; 2) Operational and anglophone support; 3) Ability to establish a panel, for example: ISPmanager.
Recommended requirements: 1) Protection against DDoS-attacks; 2) The ability to administer the server, a company that provides services to lease (regular updates, round-the-clock monitoring, etc.).
The server is designed for the site, which will:
1) Forum; 2) Video and audio materials (up to 20 spots, for up to 10 minutes each), which can be viewed directly on the site using flash-player or download. Clips will not be frequently changed or supplemented; 3) Downloading developed software, up to 0.5 Mb; 4) Download documentation formats: DOC and PDF, up to 2 Mb; All audio, video and documentation for its own production.
Additional information:
The number of visitors, initially to 10000 per month (probably much less or slightly more, not yet known) The audience will be visitors from the following countries: Ukraine, Russia, Poland, UK, Germany, France, USA and Canada.
Budget: up to $ 200 a month. But if such amount is not sufficient for the entry requirements, are ready to revise the budget.
Need a really high-quality channel of communication and operational support, etc. Perhaps for these tasks, you recommend other requirements to a server and placing the territory? Check your real council.
Also look in the direction of affordable rental server and utilization of services: Akamai Technologies. If someone has experience working with Akamai, I ask, share their views. Should I use it for such a project?
A lot of information has been revised to servers in Germany, UK and USA. But the single answer, yet to be found.
I'm completely torn on going the absolute budget route vs spending more for something that'll allow easy upgradeability in the future. I basically need lots of space but file sending-- media like mp3s, video, etc.
it'll be raid 5 and I'll need at least 2-3TB initially but the ability to expand would be nice.
option 1: nice chassis with plenty of hotswap bays with sas expanders expensive sas raid card
option 2: cheap chassis to serve "immediate" needs and go with more later. not sure what I'd use as a card? maybe even onboard?
regarding reliability: I once saw a database of failure rates of different models. raptor was the most reliable of the "desktop" drives. anyone have the link? I'm wondering of the seagate ES drives are worth the extra money vs the non-ES drives. they're supposedely more reliable and the "server versions" of sata drives.
In your opinion how much downtime is too much downtime?
1, 2, 5 hours over the course of a month? 99.8%, 98%, 95% total uptime too little?
I mean I can understand technical difficulties and I am willing to be patient with my host especially when the service (when it is up) is good but where exactly do you draw the line, start asking questions, or canceling that contract and demanding your refund?
i have 150 domains my server I wish it to migrate to a new server I can do restore domains, mail and users and data, stats to new server. I need minimum downtime so I need your's advice step by step which service need to restore first so my user get minimum downtime.
I had a client ask me earlier if there was any downsides to having his main site be SSL only ,not his billing his actual site.
For exmaple it would be https://www.yoursite.com rather than the normal http and having that redirect to the https.
Obviously he would need all his images being linked to https in order for it to be secure but apart from that, I couldn't think of any of the top of my head, I was wondering what you guys all thought.
I just uploaded a wordpress site and it already used up 300mb ram. The site receives very little traffic so I doubt the traffic is the cause of the ram usage. Is this normal? my control panel is webmin
Does that look normal to you? Because I read somewhere that you should allow no more then 30 connections per IP. But most are taking much more then that.
We've just started to use a VPS, and so far no problems I've been looking at the resources and they seem a little high considering it's pretty much out of the box, and I've only setup 4 sites which aren't even public yet. The only thing I've changed is the php.ini to increase the memory limit to 32mb. My main concern is that these sites don't suffer when they go live.
In the Plesk control panel the memory says: 3.8 GB of 3.8 GB used; 47.1 MB available The 47.1mb is pretty much average, although I've seen it go as low as 115mb.
In Virtuozzo the system usage (resource: capacity) is usually around 60-75%
Both of these seem a little high, but I'm not sure if these readings are for the whole physical server, or just my portion of it.
Also in the (Virtuozzo) QoS alerts I've had quite a few Yellow zone, black zone and one red zone reports, at around 5am - quite possibly the quietest time on a server which isn't hosting any live sites yet. These have both been on the numproc and the privvmpages services (the red zone was one the privvmpages). Is there anything I should be looking at or is this fairly normal operation for a VPS? I have nightly backups scheduled for around 1am. These were originally set for 4am, but reports were showing that they were running out of memory, so I’ve now staggered the times of these to see if that helps. I've haven't changed anything resource-wise other than the php, so I thought it would be good to go from the start, but maybe it needs some fine tuning.
i've recently been experiencing a lot of apache downtime on my eUKhost VPS. anyone else having this problem? it's driving me crazy and i'm thinking about moving.
Recently our provider has been having unplanned long outages (along with a complete server move that took several hours). This has turned out uptime statistic from exemplary to mediocre (100% to <99%).
As we are a hosting company and normally have an extremely good amount of uptime, when is it time to give up on the provider? I am extremely concerned this will become regular and our uptime will simply continue to go down the drain, however, they have been good and have been the main attribution to our 100% uptime (along with our great technicians and hardware).
It's not even been a month that I started subscribe a windows 2003 VPS hosting with them and now their website is gone and I am unable to access my VPS server
I am the webmaster for a high level court system. We run mainly .php and MySQL like most do. We are in the process of doing a transfer to 1 and 1. I want to be able to test everything (database wise) before I do the transfer. I thought the best way to do so would be to purchase another DNS name and server and transfer everything there first to test and then when that is fully operational have a redirect to there and do the DNS name transfer from the old site to 1 and 1, and when the DNS name is on 1 and 1 take the redirect off . I don’t want any downtime at all.
This might not be the most cost effective but for downtime I thought it would be the best way, especially when I can have a live test before the transfer.
In the forum here i put a story about when i was changed to vz45 from vz69 some months ago and the problem is growing. One month ago, around 1/oct, was a half day.
Yesterday i detect a problem at 08:40 am aprox, and they are working in that but something is AWFUL here.[url]
I have many domains and webservers. so it's hard to monitor everything usually. i heard there are some websites and softwares to do this.
does windows 2003 have anything default like this ? or can anyone suggest the application for my windows 2003 server? which sends alerts if any error is going on my server?
Also there any other websites which is doing this monitoring? because i have some shared accounts and i want to monitor it too.
I'm having a bit of a quabble with my current host because our server was unreachable for an extended period yesterday, and since I made a traceroute that arrived at their datacenter but not at our server, I was assuming it's a crystal clear network issue.
Today however they tell me that a traceroute means nothing. To quote them:
Quote:
Please note that having a traceroute end prematurely does not always indicate a problem with the network it ends at. Being that traffic is typically asynchronous, the return path back to you does not follow the same providers. Your traceroute can not fully take into account network connectivity issues on the return path nor will it show them. You would need a traceroute to and from the server at the time of the issue (while this may be impossible if the server is down, opening a ticket immediately and informing the technician you would like a traceroute to X.X.X.X IP would hopefully catch the return path issue).
What do I make of this? First time I've heard that, when the network is down, I need to contact my host to tell me. But without any polemic - is this what it boils down to?
It is probably acceptable for a site on shared hosting to have some downtime. However, how much is acceptable?
According to Pingdom one of my sites had a total downtime of 14 hrs for Feb. One time it was reportedly down for 4 hrs.
I had set it up to ping every 15 mts. Are these results trustworthy? And if it is should I move my host? Or at least tell them to move my site to another server?
The reason I ask is because I was wondering if this was the norm for shared hosting.
Probably been asked a million times but after spending 30 min searching since the limit is 130 seconds between searches... Anyway, i am VERY unhappy with ModVPS as my server keeps going on and off and on and off and they tell me its "fixed" but it keeps doing it to all of my staff even... anyway enough of that
I purchased a really nice dedicated server and need to know how to migrate all accounts over without having any downtime and allowing people to still use their website as normal. I have about 60 clients and would hate to see one of them upset because their data was lost during propagation when they connected to the old server instead of the new, exc.
Is the best method to setup a cluster through cpanel? Or is there a better way?
