First we see the scene on which post was based this: In the previous servant, 2 vestibules with several subdominions were handled, which receive several tens of thousands of daily visits. As much the present servant as the previous one, uses Linux, with Web server basic Apache and of MySQL data? The update of content in average is every 15 minutes, except from the 8:30 that is practically null. The sites require a high availability, that is to say the migration practically must be transparent for the visitors. Now we see that we would have to do before the migration: First it is to know that it handled to the servant anteiro for it we must: To list dominions and subdominions that work in the servant. To register active directions DNS. List of crones with its frequency and path of scripts that is executed. Listing of additional bookstores of PHP.
Registry of accounts of electronic mail in addition its mailbox to mail, adjustments, email forwards, car replies etc? Registry of accounts FTP? Endorsement of configuration files of the servant mainly php.ini and httpd.conf? To register path of each site. With this information we will have a clear idea than we must migrate for being able: To install the new serividor? To form the servant based on listing of bookstores additions, the configuration files php.ini and httpd.conf? To create the virtual servants for each site registered in step 1? To create the accounts of electronic mail and to form them. To create accounts FTP and to form them. And what it goes to us to save several headaches in creating the connections, of path previous towards the new ones. We say in the previous servant the physical route of site this in /var/www/xxx in the new servant will be in /home/xxx/www for it from console with access root digitamos: ln – s /home/xxx/www/ /var/www/xxx This for all the sites that will be migrated? To notify to all the possible ones affected that the migration this by realizarce. Now already we have ready the new servant with an atmosphere similar to the previous one.
During the migration: If it is possible to deshabilitar the sites, case in opposition to less deshabilitar registry of users, commentaries, generally the creation, modification or elimination of content. To compress the archives of the sites. To pass the archives to the new servant to its corresponding path, we can use wget. To migrate the data bases? To update registries DNS so that they aim at the new servant After the migration? To qualify the sites? To review log of errors? To be patient before any Ready eventuality we have migrated successful of servant.