Hosting termination question
 

With your hosting, have you faced the case you raise the ticket to cancel the services and they just cut the shit down in an instant like they were expecting to do so, and then you ask for back up download they send you invoice for that?

That shit does happen.

You read about those stories from time to time.

Do your back up before you cancel.

I mean, they may shut it down figuring the reason you want to cancel is that
all 300 of your auto-submitted galleries to the hun were just approved. :1orglaugh

We give you the option of cancel at the end of the pay period or immediately. Immediately actually means at midnight when a cron job takes care of it.

Have never thought of charging for a backup, but again, DirectAdmin allows them to do that on their own.

I have plenty of design samples there. Of course I have latest on my PC but generally being a host I would ask if you have your stuff downloaded and require any support to do so. Usually they have been slow in tech issues and this case they shut me in a second, like their billing has nothing to do but cancel and quiclky raise money on that.

I was downloading via FTP when they did the cut.

I had 3 more addon domains and they didnt warn me they would be affected.

I can tell since their support started using Russians it went to shit.

Are you a web host?

what kind of question is that?
I usually ask if my clients want PSD I dont charge extra, should I?

name the host ;-)

I have never witnessed a painless contract termination for any host that isn't small/shared/throwaway. We're not talking the $100-200/mo stuff here.

I've worked both in the hosting industry, and (now) from the outside as an integrator/VAR sort of fella. You have so many things that come into play - it's amazing how childish techs and owners truly are.

Things I've witnessed (recently, within the last year or two):

• Host A and Host B have each other's bandwidth shaped down to 1mbit/s because they're fighting between each other.
• Host who has registered domains for client, in client's name, refuses to transfer from their self-branded eNom to new host at customer request.
• Host notices archival process on server, so "preemptively" locks account and holds hostage - when no bill is overdue, demanding a pre-payment for possible bandwidth commit overages.

At this point, I always make sure I have a (semi-)current snapshot of everything, and if possible, an external slave for every DB before I migrate shit.