Ive looked for a long time now trying to find the perfect tutorial to migrate my clients (on cPanel) to my VPS without downtime. Every tutorial i found doesnt tell you how to make it so you dont have any downtime at all.
I know you can point the DNS from the old server to the new server by editing it through cpanel but i have more than 100 clients and it would be DAMN annoying to edit every single one of them one by one. Is there a faster way? Anyone have a tutorial that i can follow?
to migrate domains to another server with zero downtime. There is a panel (but its webminish) and I have full root access to everything so this will be a hands on job.
The thread I recalled seeing was about someone hosting shoutcast servers and they wanted to migrate and there was a way they did this without any downtime.
I can't remember the details but it had a way to redirect all traffic to the new machines. This would be great, as I also want to direct all traffic including mails (not just HTTP).
Can someone show me a tutorial on exactly how to point a domain name to my VPS? Not just a simple masked forwarding, I want it to actually point to my VPS so that basically [url]is the same as [url]
Does anyone know if the VPS tutorial thread (the one that told you exactly how to do everything) was distributed anywhere else apart from WHT? Because of the recent site problems, that thread was one of the lost ones.
How do I add a domain name to my vps account? Where is the vps detail tutorial? I brought a vps plan so I could learn at least 100 things about managing my own vps through hypervm and webmin.
If you have a thing or two to teach about managing it, please reply with how to do so and so.
I am at school now. I will get home later and then I can get back to my hobby of teaching myself how to manage a vps. I have a lot of time on my hand to learn how to manage a vps.
I'd like to have the ability to offer hosting in two geographical and network diverse locations for both Apache and MySQL. Two entirely different instances, with different everything. ie: high avail to the max. Obviously the MySQL part is harder due to the dynamic nature.
I can appreciate the technical aspects of the question - such as data needing to replicate to 2 locations, dealing with static versus dynamic data, etc. In short, there's a few ways this could be done.
I've not been able to find a guide in my Google searches, but I'm sure this is something that has been setup before.
If you're someone with experience in having had set this up, perhaps it would be easiest if we just speak directly and work something out, either via payment or giving you a dedicated server on my network. My AIM name is IGSOBEHELPER.
Please note that I am hoping to start a technical discussion about this, hence I am not posting the message in the employment section. I hope this is not off topic because of this.
Is there a Windows GUI software for remote Admining servers that run on Red Hat Linux?
FYI: Currently I use Putty for remotely managing our servers.
So if you can recommend a GUI like Windows desktop software for remotely Admining servers running Red Hat Enterprise, I would very much appreciate that.
FYI: we have like 10 dedicated severs, so a desktop GUI that would allow one to monitor/manage multiple servers would be best. But if the GUI that you think is best can only remotely connect/manage one server at a time, requiring disconnecting to connect to the other server to Admin it, that is fine.
Also, I would love to hear what you think is the best book, best tutorial and reference guide for remotely Admining servers running RHEL? I am not looking for one of those books that are 1000 pages, but something that is a few 100 pages and can be read in 1 month assuming a few hours per day of reading.
write a tutorial how to set up a server without a control panel. A step by step guide how to set up the dns, add doamins. create accounts, create ftp users, create databases, create db
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 was wondering, since I know their are tools to automate transfering services from one cpanel server to another, is there any automated one to transfer from godaddy to another host? Im refering to all my files, mysql database, ssl, etc. All but the name servers? Its from a linux godaddy
I have 2 servers on LT SAVVIS data center (through Server4Sale).
Today I received mails from them that LT is migrating out of Savvis and so my servers need to be transported/built(!) at the DataBank facility. And the server IPs will get changed.
If the servers requires a build, that will mean ill have to configure/reinstall everything again. Thats apart from moving the client accounts from the old server.
Where trying to migrate customers on one of our server to another one, We lowered our TTL on our domain and ns a couple of weeks ago and managed to switch our main site over instantly will our clients experiance any downtime?,
What will be the best method for moving the sites over, i know whm has a built in transfer section, but this seems to fail for us as we have minimul disk space left
I read in another post about creating a cluster between the serer how will this help?
I am in the process (or my server manager is) of migrating my server from one provider to another. Once all the files have been migrated and everything is "set" on the new server, what do I need to do with respect to the name servers? I currently have 2 name servers NS1.Mymainwebsite.com and NS2.Mymainwebsite.com. Each registered with an IP address from my current server host. Once I migrate, do I only need to re-register the name servers under my main website with their new IPs? Or does every person with a web site domain on my server need to "re-register" the IP address of the name servers.
We are migrating all of our users from one box to another. We were planning on changing the TTL settings in DNS so the move would be a little more transparent to the users but we can't seem to find a option to change the TTL for all of the accounts on the box.
Is there an option to do this? If not, is there a better way to handle this?
I'm currently running various sites on a single server but cause the requirements are no longer satisfied by the current configuration i started renting a more powerful server in a different provider. Both servers are running CPANEL/WHM. I have migrated sites from WHM servers before but the problem i had was having to update all domains to point to the dns servers of the new server - which is harder than it sounds when the sites (and domains) belong to clients. Is is possible to move to the new server without having to update the domain registrars?
Anyone know the correct way to do this? I've been on here looking at a few threads and on lxlabs forum but my solution can't be resolved. I'm sure its something easy.
Here goes,
I'm migrating from an lxadmin VPS to another lxadmin VPS.
The problem I have is that my IP's for the HOME>DNS TEMPLATE and HOME>IP ADDRESSES are the same as my old VPS.
Now I can change the IP in the DNS template, however under HOME>DNS TEMPLAES>CREATE NEW it doesn't have my NEW VPS IP's listed in the drop-down menu. I read somewhere in an LxAdmin tutorial to update LxAdmin to get your current IP's assoicated with your new VPS. I did this and nothing changed.
In addition to the DNS Templates not being correct, In HOME>IP ADDRESSES it also lists the same OLD VPS IP's. Saw a thread in LxLabs forum with someone that had the same problem. Their help stated to just change the IP ADDRESS to your new one. I would do that but there is no option to allow me to ADD a new IP. Again i'm in HOME>IP ADDRESSES here.
Basically I have one website hosted (add-on domain) on a shared server. Now this domain has to moved to another server on its own. I have no doubt backing up the database from the current server and restoring it but is there an easy way to move the website, mailbox contents? Both servers are cPanel plans, I would just use copy account in WHM if it was not an add-on domain.
am moving to a new VPS (replacement) and know there's some way to copy over the list of packages to the new server. the whm migrate tool does not copy the actual packages. i recall somewhere on these forums where a user had mentioned some file that could be transferred to the new server which contains all the package data?
I'm running into some troubles moving my Webalizer installation. I want to keep all my stats, so what I did was to copy all the files to my new host, checked permissions as well.
Each website outputs their logs to a separate log file, and that log file is pointed to in the respective webalizer.conf.
My problem is that when I try to run webalizer -c /path to conf file/ it tells me that it found x new records (good!), but then it ignores all of them. Every single time it'll tell me it found so and so many records, and says, "(number of new records) ignored".
So I'm not sure what I've missed in the config, and why it can't update.
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).
