I`m running a large vps, with several dozen clients. I`m extremely happy with the service, but I`m in a situation where I have all my eggs in one basket.
I haven`t been there yet, but one day I`m going to suffer the embarassment of my vps going down including my main website where my clients would go for support etc.
Just wondering what easy options I have to try and eliminate this dilemna. I was considering a small shared account off-server and with my main domain, point the second nameserver to this shared account where I would host a backup of my site? Or am I way off here?
i have my selling website on another web host so that way if my servers go down i am able to give help and support - on the ads boards atm there is a 90% reeduction offer.....thats probably worth a look
Well it all depends on what billing system you have I suppose. I deal with gameservers so everything bar the game servers runs on the web-site, obviously its best to inform your host your just using them as a selling platform your not actually trying to run a 64 slot counter strike server from them, and then once the orders are confirmed etc etc i just set-up the game slots on my dedicated servers and away they go!
I would suppose in the world of virtual hosting that you would have to either get a new domain/nameservers for each hosting platform. I don't know if its possible but can you attach multiple IP addresses to each namesever?
You will have to ask somebody else on that - Its definately possible...My old hosting company used to do it...and they have like noname.com and noid.com and things like that.....that way you can offer private nameservers to your clients and turn a little more profit.
That post was all complete guess work so feel free to tell me to shut up ^^
it is certainly possible.. and we have dedicated customer taken a small VPS on another box.. so that the main function of their site.. (i.e. shopping cart etc) is not totally off if their main box is going. Depends on how the dedicated is setup.. if you can have the db not on the same box, then there is no problem in connecting to keep the db in tact.. so lets look at this scenario:
you have a dedicated and all the content and db is on the box. you set up your own name servers on the dedicated and also setup 2 for the VPS. Each night you mirror any changes to the VPS with db. when the box goes down. you need to go into the VPS, make a copy of the db.. and if possible to have a script on that box that will "log" all the transaction to db (i.e. customer table change, transaction etc)... then go to registrar to change the name server. The VPS then is live.
When the dedicated is back, check everything is ok.. stop the vps function, get the log file, get that imported into the db of dedicated.. then switch name server. Then syn the db between the 2. you are back in business.
the change of nameserver should not take more than 5 min.. so it is relatively quick.. TTL should not be matter in this case.. so the trick is to setup name servers in reserve.
Also, if you are already running VPS, you might be able to have a word with your host to have backup copy made and run it on another box for you to aid recovery... but certainly it is good idea to have a Plan B.
Is this possible to setup with a reseller package?
For example I have clients on a reseller account using my private nameservers. I would like to host the main business domain on a different network however. So if the reseller server goes down, my clients can still reach me as the main site is hosted elsewhere.
My issue is with the private namesevers. If the shared account on the other network went down, those private nameservers would not resolve mean those resold accounts on the reseller package would be dead too?