Upgrading a Virtual Private Server to a
Managed Private Server
To help Customers better understand the steps involved upgrading from a VPS to an MPS we have outlined
the basic steps to follow. When they are used properly these guidelines will facilitate a smooth and
seamless upgrade to the new MPS account. Customer's Actions:
- Place MPS Order
- Place MPS order via the Backroom Order Wizard
- During order in the “Special Instructions” field include the following:
Upgrade for VPS "account ID" to MPS “account ID”
- Once your order has been submitted please send an email to
service@alpineweb.com to expedite the upgrade process or
wait for a initial contact email from AlpineWeb
- Wait for Notification of Content Copy
- NOTE: content will only be copied for upgrades to similar platforms (i.e. - VPS v1 to
MPS v1 or VPS v2 to MPS v2). Any upgrades from unlike platforms (VPS v1 to MPS v2) require the
content and configuration to be done by the reseller
- After an initial confirmation email has been sent by AlpineWeb and confirmed by the Customer,
AlpineWeb will copy the content from the VPS account to the new MPS account and notify the Customer
upon completion
- Inspect Initial Content Copy on New MPS
- After receiving the email confirmation of copy completion please do the following:
- Verify that all the content has been moved
- Insure that any configuration and scripts are properly working
- To help check the copied content Customers can use the new IP address and temporary domain
name that are assigned to the MPS account to help test the copied content
- Request to Go Live and Final Re-Sync
- If there were no problems encountered in previous step (Step #3), Customers can proceed to
request that a final re-sync of the content be completed and the DNS moved to the new MPS
account. This action will cause your new MPS server to “go live” with the most
recent version of all the VPS content. An email will be sent out upon completion of this step
copy.
- Reply to Technical Support's email request that a final re-sync of content be made and the
DNS moved over
- If this request needs to be scheduled for a particular time please include this in your
request. Please give advance notice of at least 24 hours for all scheduled requests
- Allow a minimum of 24 hours after final copy and DNS move for propagation to the new MPS
IP. The TTL settings that had previously been “set down” help resolve most
propagation issues that would have normally occurred
- Terminate Old VPS Account
- Normally we recommend allowing a day or two for the old VPS account to stay active
until the MPS has been verified to be working correctly and all DNS moved over. Customers can
proceed to terminate the old VPS account in the Customers' Backroom
AlpineWeb's Actions:
- DNS TTL Change
- Once we receive the email from step #1 AlpineWeb will change the time-to-live (TTL)
settings for the domain name(s) assigned to your VPS down to 10 seconds from the default
of 24 hours. This change will help with the propagation period that is normally experienced
on DNS changes. This change requires at least 24 hours to take effect.
- Content Copy
- The Customer's email from Step #1 will also initiate the content copying from your VPS
to your new MPS account. Upon completion of the copying process an email notification will
be sent out to the Customer.
- Final Content Re-Sync DNS Switch
- Once AlpineWeb receives the Reseller's email request in Step #4 we will proceed to do
a final re-sync of the VPS content to the new MPS account. This will copy over any changes
that might have been made to your VPS account between the first copy and DNS switch. Upon
successful completion an email will be sent to the Reseller.
If you have questions, concerns, or wondering if you should upgrade a VPS accounts contact your
Account Manager by email at: service@alpineweb.com
or by phone 603-356-8797.
|
|
