+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Migration (/forum-35.html)
+--- Thread: Moving (/thread-7093.html)
Moving - krzd - 07-01-2009 05:57 AM
Hello,
i have got a server running, but I want to change to ispcp. So i want to set up ispcp in an virtual machine on my pc and then reinstall my vserver with the same os and then transfer my virtual machine data to my vserver.
What do I have to transfer to the vserver and how exactly.
Thanks in advance
//edit:
I want to do this that way, to reduce the server downtime. Currently I am using SysCP but migrating is too complicated because almost all config files will change and the php mode, too.
RE: Moving - MasterTH - 07-01-2009 06:00 AM
am i right, u want to change from one controlpanel to ispcp? If thats what u want u have to transfer one domain after the other.
RE: Moving - krzd - 07-01-2009 06:09 AM
No, I actually want to migrate from SysCP to ispCP, but that does not work because of some config files (edit: and the different php mode). My solution is then: I create here at home a virtual machine with Debian Lenny and set up ispCP with all configuration and settings I need. Then I reinstall my remote vServer with exactly the same Debian Lenny. Then I want to transfer all the data from my local virtual machine to my remote vServer, so I can reduce the downtime on the remote vServer. After all that I have got a running and configured Debian Lenny with ispCP on my remote vServer.
But how exactly and what do I have to transfer from my local virtual machine to my remote vServer.
I hope, that you could understand, I'm just a German learning English ;-).
edit: I have found this HowTo http://www.isp-control.net/documentation/howto/miscellaneous/migrate_from_one_to_another_ispcp_server but what has changed untill ispCP 1.0.0 and what will probably change untill 1.0.1 or the current trunk (I think I will do that procedure after the release of 1.0.1, which should be near as I can see).
RE: Moving - MasterTH - 07-01-2009 02:31 PM
hier gibts auch nen deutschen teil
RE: Moving - krzd - 07-01-2009 02:50 PM
(07-01-2009 02:31 PM)MasterTH Wrote: hier gibts auch nen deutschen teil
Aber der englische ist meist mehr gelesen, zu mal auch die Deutschen da rein schauen.
--
But the english one is normally more read, even the Germans are looking in that one.
RE: Moving - MasterTH - 07-01-2009 03:06 PM
in your case i would do it this way:
1. Install the new server and make him work
2. Transfer one Domain which has now priority
3. Change the DNS-Settings for that domain
4. Check if everything is working.
5. Create the other domains
6. Transfer everything thats on that domains (mail-addresses ...)
7. Change the DNS-Settings for each domain
8. Copy the Mail-Files into the right folder on the new Server.
9. Check if everything is running well, if not turn back to the old server
RE: Moving - krzd - 07-01-2009 07:12 PM
OK, i will try it, thanks.
RE: Moving - grisu - 07-25-2009 09:08 AM
(07-01-2009 03:06 PM)MasterTH Wrote: in your case i would do it this way:
1. Install the new server and make him work
2. Transfer one Domain which has now priority
3. Change the DNS-Settings for that domain
4. Check if everything is working.
5. Create the other domains
6. Transfer everything thats on that domains (mail-addresses ...)
7. Change the DNS-Settings for each domain
8. Copy the Mail-Files into the right folder on the new Server.
9. Check if everything is running well, if not turn back to the old server
That's exactly what I've done with my system (a Insel-Lösung based System ^^) - it IS some work to do, but after the first domain, it works easyly and using 'rsync' is not a problem to repeat those steps for the next domains.
Btw a little hint to #3 (change DNS servers)... You MAY want to change the first line of your Zone-files of all the other domains in advance. This reduces the TTL (time to live) to a value like 3600 (means 1h).
If you migrate the stuff and change THEN the DNS finally it will take the changes much faster because many default settings are set to 84000 or something (which means a whole day). This MAY work and it DOES work mostly... but it's not a warranty that coresponding DNS taking the changes faster...