It seems something has gone awry with choopa's recently planned migration. All but one of my servers returned to life, of course, the one that didnt is the database server that they all rely on. That server has been down going on 18 hours now, and of course no one answers the telephones, AIM, or support tickets. Of the one or two times that I've gotten through on the telephone, the tech has told me that they're putting hands on every machine that got migrated, and connecting a console. They also mentioned something about not sleeping for 24 hours. I think its time to make plans to move my equipment elsewhere... 18 hours of downtime for a 2 hour planned maintenance window seems a bit wonky to me.
I forgot to mention, each time I had gotten someone on the phone / aim, they said they would immediately go check the server and see whats wrong, and none of them updated any of my tickets or got back to me.
I've decided to move from LSN (review coming soon) to a new home, but I'm not quite sure where to put them. (To avoid any confusion from the title: My babies are my websites, not servers if someone would mistake this thread for being a co-lo ).
I've looked at choopa and gigenet as they have gotten good reviews and when looking at the outage reports forum here they don't seem to have had many reports.
For some reason my gut feeling says "go with Gigenet", considering all reviews I've read about them has been extremely good, not to mention the uptime they've had. I'm not sure how accurate these statistics are, so please correct me if wrong.
The things that makes me worried about choopa are:
* 12 Months contract
* "The May Incident" of Choopa from the link above. 833 minutes of downtime?? But an average uptime of 99.94% over 1114 days seems very good considering whatever happened in May 2008 killed the statistics.
* Haven't heard much about the company and google wasn't very helpful finding reviews. Seen gigenet here and there and heard great things about their ProxyShield. Hey, even WHT use it.
The only falling point I can see on Gigenet is the price. I'd have to pay $1,471 compared to $798 with the newest offer from Choopa ($673 more a month, $8076 more a year). The 100Mbit unlimited is $1000 compared to Choopas $500. If I'd want to upgrade in the future, I could get almost four servers at Choopa for the price of two at Gigenet.
Does any of you think $673 extra pr month with Gigenet is justified? Would the service be _that_ much better?
Searching for choopa.com on the forums there are a lot of threads by "Andy Choopa" with some insanely good deals on servers and bandwidth. However, out of the many many threads, I've yet to see a single person respond to one of them saying that they purchased a server, were happy/not happy with it, etc.
I was just wondering if anyone has purchased any of those deals and if so wouldn't mind sharing some insight on your experience re: the network, support, etc?
We are currently with Alpha Red hosting, and wondering about other services. What are the pros and cons of SoftLayer, Alpha Red, and Choopa and who is simply the best (in your opinion and why) and who is the worst.
I am considering getting high bandwidth hosting from either alphared, choopa, or leaseweb, but before I do I would like to ask you which one would give me the best speeds, globally. Any other info that you can provide would be useful too. Thanks!
Also, if you can suggest another host for high bandwidth that is very reliable and has great ping results for the us, europe, and asia, i'd be interested.
We have 2 servers SQL, Web & SM 4.x each with and have about 40 sites and we wish to migrate them to Virtual sever for the ease of management & some cost saving. We are thinking of taking good configuration box with Win2k8 server and planning to run VMs over Hyper-V.
I've been getting frustrated with my hosting provider, and after doing application development and sysadmin for a while now, I'm ready to have a go at doing it all myself on a VM. I plan on migrating my site to the new server and when everything is set up, pointing my domain to the new name servers...
My question is - what's the best order to do things to minimize downtime? Can I set up email, MySQL, Apache, DNS etc before I have the domain pointing at the new server, while still being able to test adequately? Would I just set up the services and test them using the IP, then once I'm happy with everything, setup DNS, point domain at new nameservers, then change all configs to use the domain name rather than the IP? In theory if it email etc works with the IP, then the name server change shouldn't matter because it will resolve to the IP...
I am migrating my website to Hostgator, and before I change the DNS entries, I want to make sure that everything displays properly. To do this, I have added an entry into my /etc/hosts file pointing the domain to the new host. If I then ping the domain, the reply comes from the correct IP address. However, if I try to view the website, it is still served by the old host.
I thought it might be a caching issue, but I have checked with wireshark and using curl, and it is definitely connecting to the new IP address, but the server that is returning the pages is still the old one. I've contacted hostgator support, but when they make the changes to their hosts file, it loads correctly. Is this a local problem (my system), or something with their server configuration?
I transfered my forum from one server to another. ips changed. Before the transfer, I closed the board and put an announcement. After the transfer I opened the board and started posting.
Now, there are other members who've posted after the transfer but I've noticed decrease in activity. One of the members emailed me and told me that the board is still closed for him with the announcement shown. That message is from the old and not the new server. So how is this happening? What should he or I do? I and some other members can access and post normally.
Its been a for a couple of hours that my VPS is down, I'm not complaining or anything, I really know that Navid left one hell of a mess for them to sort out but I just want to be sure that my VPS is down because of the migration process and not because of something I did.
Anyways I submitted 2 tickets, still no reply. The guys must be busy fixing and moving all these accounts
I will be migrating my VPS over to a new VPS (same provider) which has Fedora 6 instead of 4.
Anyhow, all of the IP addresses will change on the new VPS.... so while the migration process via. Plesk should be fairly straightforward, I'm a bit worried about the DNS. The DNS is managed by Plesk and will continue to be managed by Plesk, but again it's the IPs that I'm worried about.
All of the hosting accounts on the current VPS use the nameserver "ns1.citedata.net" and "ns2.citedata.net" as well as their associated IP addresses. Although the nameserver domains will remain the same, their IPs will change.
I wasn't sure where to post this so here goes, I need to migrate a MySQL DB, in the past I have just created an SQL file and used that method (sometimes having to split the SQL file up) but now the DB is about 50 meg and 733,233 records.
Is there an easier way to migrate the Database from one server to another?
I would like to inform you about the planned migration of your shared hosting account to a new hosting environment. This concerns the domain xx***********. The migration will start on: 29-10-2009 during business hours.
Due to a problem with the restoration of the backup on the newermachine, we did not succeed in the transfer of your domain. So for now it will stay on the 'older' webshared enviroment. Are you OK with us to give it another run tomorrow? Please indicate a No in case this is inconvinient to you, if there is noanswer we assume that there is not a problem and we will work on thetransder again tomorrow.
Dear Customer, The transfer of your webpackage to one of our new shared hosting servershas been completed.
Now my Oscommerce site is down: Parse error: syntax error, unexpected ';' in /vhosts/xxx***********/httpdocs/catalog/index.php on line 314
I checked line 314 of index.php does not have ';' My site admin side is working.