Migrate from a (dv) 2.0 to a new (dv) 3.5 server
This article is to help guide customers in migrating from a (dv) 2.0 server to the new (dv) 3.5 server.
To start the migration you will need to have both servers active at the same time. Start by ordering your new (dv) 3.5 server via the (mt) AccountCenter. You can also contact our Sales Department at (877) 578-4000 x403.
NOTE:
You will want to activate your new (dv) server using a different domain name. Do not use the same Domain Name as your current (dv) 2.0 server. If you wish you can use a temporary fake domain, such as tempyourdomain.com. Once the migration is completed you can easily change the primary domain.
Now that both servers are active you can start moving your data to the new server. Most customers will want to move their domains using the Plesk Migration Manager. If you have errors using the migration manager you can also migrate your data manually.
You should preview your sites on the new server before updating DNS, to ensure they are working correctly. You can do this by visiting the IP address of your (dv) 3.5 directly. To set the site that will appear when you visit your IP address in a web browser, click on Server > IP Addresses in the Plesk Control Panel. Then click on the number in the Hosting column all the way to the right of the IP address for which you would like to set the Default Domain.
Once you have tested a site on the new server, you can update the DNS Zone file for that domain on the (mt) Media Temple name servers by logging into your (mt) Account Center. Once logged in, choose your domain from the Domains tab, and then click on the 'Point to Another Server' link to set your new Server/IP address.
NOTE:
DNS propagation to move your website to the new server normally takes 12-24 hours. If you want to reduce this time, go into the 'Edit Zone File' page for a domain in the (mt) AccountCenter, and click the 'Lower TTL Value' button. You should do this 12 hours prior to moving the domain, so DNS propagation will be reduced to just a few minutes. We recommend you do this prior to beginning the transfer of data to ensure a smooth transition to your new server.
WARNING:
If you have upgraded any domains to PHP5 on your (dv) 2.0 server, you will need to remove the relevant lines in your vhost.conf file for all of those domains. Plesk will not update your apache configuration to include newly added Domains until this is done.
FAQs
Why would I want to migrate?
There may be many reasons you want to migrate to the (dv) 3.5. The most common reason is customers may want to use newer software, such as Plesk 8.6, PHP5, MySQL5, and Centos5.
Will I see a performance increase by migrating to the (dv) 3.5?
Yes. Our newer servers come with double the memory so it's very likely you will see an improvement, especially when running multiple sites.
How long will it take to migrate my domains to the new server?
This is really up to you, since you are moving over the data. Migrations using the Plesk Migration Manager usually are completed within hours. Keep in mind that there are many variables involved.
How much does it cost to migrate?
There is no cost to migrate. You will however need to pay for both servers while they remain active. For this reason migrating your domains quickly would result in the least amount of cost to you.
Do I need to pay for both (dv) servers?
Yes, you will need to pay for both (dv) servers while they remain open. Once you finish the migration you can close your (dv) 2.0 server. Click here for instructions.
Notes/Supplemental Resources:
- (dv) Migration Overview and Preliminary Steps
- Migrating your websites to the (dv) Dedicated-Virtual Server
- (dv) HOWTO: Using the Plesk Migration Manager
Revisions:
06-26-2009: Added link to KB article for pointing DNS to another server.
06-24-2009: Article Creation
Fields marked with an asterisk(*) are required. Comment on this article