Why i'm i leaving Jodohost...

Since the migration, the 4 client sites are crawling - client is angry, business is loosing money.

Support tried to help me on Sunday, but on Monday everything back to a standstill. I know what needs to be done, techns know what needs to be done, but i cant get even an estimate on when its going to be completed.

So after 5+ years everything comes down to this one small failure - unfortunately this is the last drop.

Can anybody recommend a GOOD reseller hosting service please?X(

ok, firstly I don’t know of any crawling issues unless there is hard coded SQL IPs of old IP.

Have you checked this? We’ve fixed this for 100’s of people already, emailed notices of it etc. it is the first thing to check

Hi Stephen

If you can please check ticket # QVY-80381-842 you will see what i’m saying

We moved sites, databases and it became worse than it ever been.

Thanks!

All the IPs updated to the new ones, seems like the problem is in one site which is connecting toa DB outside of Waco.

I submitted a ticket to move that DB to the new DC, but no luck: GRW-91089-422

I wish i could stay with you guys, but i need to resolve this ASAP. i didnt want want migrate the sites, you kind of made all of us do it - but not its impossible to navigate the sites…

Thanks!

ok yours started with mssql4 issue.

We moved you to same datacenter as mssql4 on a new server, and now you have some using mssql12 that are causing issue because it is back in other datacenter.

So what can I offer you?

  1. you have site and mssql4 already in new datacenter, the problem now is that mssql12 is remote and actually more important that the mssql4 you have moved to new server for.
  2. This is not a ‘migration’ issue as much as it is cross network because using way spread out servers.
  3. It is fixable.

What is fix?

We can setup DBs on mssql12 on a server here in Texas Datacenter, and all will be in the same place then.

just as a FYI

[email protected] is escalation email and would have come to me for escalation of matter :slight_smile:

btw, main issue is not having a sql 2005+ cluster1 server in waco, we’re making something special as an exception right now. I am on track to have a deployment one this week, but it isn’t in place yet. however, we have one that can be used for a special case as this. Since mssql4 upgrade failed to it is still on 2000 and can’t restore the much newer DB.

how quickly can we do this?

I’m open for any solutions now

We will work on taking backup of your MSSQL12 and import into another server, we just need a little time, I am working this CF issue as well :frowning:

I’ve given techs permissions to do it and they are capable.

Stephen,

As always you are my last resort.
Please keep me posted and let me know if there is anything i can do on my end to help you out.

I would really appreciate if it gets attended sometime before tomorrow start of business (EST). I’ll be online overnight and will be checking this tread as well as my tickets.

Thanks!

Aleksey

I really don’t have to be the last resort :slight_smile:
I am actively involve din all we do I just can’t check and know every ticket on every level. I appreciate being made aware when there is an issue, this is a unique situation that requires my attention due to the nature of it and what is available.

Ok seems like we are almost there. Replied to the ticket

A bit odd this one, all tables there, are you using a Mac? Otherwise MS tool will be best I think, and it’s all showing there.

well, the bigger problem is that my site is not connecting to the db through the connection string i provided in the ticket.

i’m getting this error on the site when i update the connection string: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

Got that resolved, this is as the name states a special SQL server, so it was limited to certain network ranges, I expanded the firewall rules to allow you to connect :slight_smile:

edit: and you just confirmed on chat :slight_smile:

In the same boat.

Took awhile, but finally figured out my problem is the same as yours.

To clarify for the other users…MySql Database is on one server, while the actual website that uses it is on another server.

When they’re in the same data center, they can communicate rapidly…

But what they did is move the MySql server to Waco, while the actual website is still in Fla…NOW you have a tremendous slowdown while they talk to each other.

It’s like our husbands have traveled ahead of us and we’re wives who are waiting for him to send for us, so we can be one happy family again…and that is taking days if not weeks. Meanwhile our sites are FUBAR.

Now the migration was actually like producing a clone of the server in Waco…while the original server was in Fla…

To solve MY problem, I had the bright idea to use the actual IP of the original MySql server in Fla, where my website still is.

Unfortunately, that server has already been killed…so now I’m forced to wait until my website server rejoins the MySql server.

I’d say there was some very poor planning for this migration…

If the MySql Servers were still in the same cluster as the Websites, we could temporarily hard code the IP in the connection string until both servers were in the same place…z

Just in case it helps, I have successfully moved clients to a new server AND MSSQL server, using the very handy database backup tools that Stephen set up a while ago. I only found out about it myself about a week ago, and they’re great.

You can create a new MSSQL db for the client in their control panel, which (I assume) should allocate a new MSSQL server in the same location (data centre). Then use the following page to backup the old db (using “mssql1” as an example):
Cluster 1: http://mssql1.jodoshared.com/mssql/Backup.aspx
Cluster 2: http://mssql1.go hsphere.com/mssql/Backup.aspx
(change “mssql1” to whatever yours is)
Then, to restore to your newly-created db, use the same links as above, but change “backup.aspx” to “restore.aspx”.

That’s it, your database has been moved to a new server. Then all you need to do is change your web app settings to look at the new db server. Hope that helps. I’ve used it very successfully a few times now.